SplitTesting / Business overview
2021Recorded work
Systemized for sale.
Acquired by Acadia.
The operations behind it.
Systemizing a conversion-rate optimization agency before its successful sale. Noah built client and operating workflows to help prepare SplitTesting for the transition; Acadia announced the acquisition in January 2023.
Explore the four systems01 / Business context
Client commitments.
Team coordination.
Noah built many of SplitTesting’s systems to systemize the business ahead of its eventual successful sale. Acadia announced its acquisition of SplitTesting.com on January 10, 2023.
Read Acadia’s acquisition announcement ↗
The business needed client information, working resources and onboarding milestones to stay connected as customers moved from purchase into delivery. A signed agreement, completed intake form and booked call represented different steps in that process.
A shared client record connected agreements, intake forms, workspaces and booked calls, so each handoff could find the right customer context. Internal time-off requests followed a separate calendar and approval workflow.
02 / Inside the systems
Explore the systems.
Follow the handoffs.
Choose a system to follow its inputs, decisions and handoffs.
Select a system, then select any step for the detail.
- PandaDoc agreement event
Receive paid or signed/completed document activity. - Onboarding template matches?
Keep unrelated document events outside this onboarding workflow. - Paid, zero-total or unpaid?
Separate a paid document from a signed free agreement and a signed amount still due. - Qualifying onboarding event
Paid documents and signed zero-total agreements can start client onboarding. - Delayed payment recheck
For a signed nonzero agreement, wait fifteen minutes and retrieve its current state. - Monday client-directory item
Create the client record that subsequent intake steps can identify. - Outstanding-payment notification
Notify the team if the delayed check still finds payment outstanding. - Send client-linked intake form
Include the client identifier in the form link and record onboarding-email state. - Onboarding-channel handoff
Notify the team that the qualifying agreement has begun onboarding.
Explore the individual workstreams developed at different stages of the business.
03 / System directory
Explore the four
system studies.
Go inside the workflow, key records, implementation decisions, human handoffs, historical tests and known boundaries.
Client onboarding
Agreement and payment gates for client onboarding
Start onboarding after payment, or after a signed agreement with nothing to pay. Flag unpaid agreements for follow-up instead of treating a signature as a completed purchase.
Configured historical walkthroughs; related duplicate-trigger diagnosis is a separate white-label implementation.Explore the system System 02Client onboardingClient intake and workspace provisioning
Turn the client’s completed intake form into an organized workspace, ready-to-use delivery resources and a notification to the onboarding team.
Configured walkthroughs and a sample run; later intake version includes hidden item-ID matching.Explore the system System 03Client onboardingBooked calls and onboarding team handoffs
Bring a scheduled onboarding call into the client record and give the team the links needed to join or reschedule it.
Historical booking implementation walkthrough; no final adoption or exception-path verification.Explore the systemTeam availability
04 / Contribution & scope
The role behind
the system work.
Noah describes setting up client pipelines, onboarding and related operating processes. Recorded walkthroughs document the configuration, sample runs, revisions and handover explanations behind individual workflows.
The engagement combined client operations and internal coordination, with team-built workflows for intake, onboarding, booking and ongoing delivery.
Configured workflows linked agreement and payment state to onboarding, matched form submissions to client records, provisioned working resources and communicated booked calls.
Recorded time-off tests created a calendar event and reflected approval or denial changes. No measured efficiency, conversion or retention result is established.
These are historical configured workflows and recorded tests. Related white-label implementations are kept separate, and no acquisition, valuation or commercial growth outcome is attributed to the systems.