# Customer onboarding for experimentation software > Help a new account reach a meaningful first outcome with experimentation software and an understood operating routine. A practical procedure with a worked scenario, category-specific checks and an editable worksheet. Source: https://saas-marketing.net/industries/experimentation/onboarding/ Topic: SaaS Customer Marketing Type: field-guide Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/industries/experimentation/onboarding/ ## Short answer For this example, a meaningful first checkpoint is to run a test allocation check and verify the primary outcome event. Account creation, a completed tour or a first login may precede that checkpoint, but none is an adequate substitute. ## Key takeaways - Define first value before writing a welcome sequence. - Separate customer work from vendor work. - Use a small real workflow before a broad rollout. - Onboarding is not complete merely because the account has purchased experimented user or event; the workflow still needs evidence of use. --- This field guide uses a product team with enough eligible exposure for a defined test as its working context. The buying conversation involves the growth experimentation lead, while the data scientist needs to assign treatments and analyze outcomes under a defensible design. Adapt the scope when those roles, dependencies or operating conditions differ. ## Define first value before writing a welcome sequence For this example, a meaningful first checkpoint is to run a test allocation check and verify the primary outcome event. Account creation, a completed tour or a first login may precede that checkpoint, but none is an adequate substitute. The data scientist should understand why the task matters and how to tell whether it worked. Document the difference between setup activity and evidence that the product is helping the customer assign treatments and analyze outcomes under a defensible design. ## Separate customer work from vendor work A new account may need to provide records, approve access or identify an owner for feature delivery and analytical data sources. The vendor may need to configure an environment, explain limitations or resolve an import problem. Put these responsibilities in a shared checklist with dependencies. Do not label an account unengaged when it is waiting on a vendor action. Likewise, a vendor completing every task can hide the fact that the customer has not learned the operating process. ## Use a small real workflow before a broad rollout Start with a permitted sample that resembles the customer's work. The exercise sample-ratio checks, a fixed decision rule and a reproducible result provides an observable path through the product. Include a review with the people who will use the result. A large migration or company-wide invitation should follow a verified small workflow, not substitute for it. Keep the initial scope narrow enough that a failure can be understood and corrected without disrupting the entire operation. ## Design help around the actual blocked step A customer worried that "A dashboard will encourage premature conclusions" needs more than another reminder to log in. Offer the specific explanation, implementation session or example that addresses the concern. Use product events carefully to identify possible blockage, then confirm the interpretation. Inactivity can mean a missing prerequisite, a seasonal work cycle or a poor fit. A generic urgency sequence may annoy a customer whose next action depends on someone else. ## Transfer ownership into a repeatable routine The desired ongoing condition is that teams make decisions using prespecified metrics and valid allocation. Identify the cadence, owner and evidence that support that routine. Training should cover the frequent task, the important exception and where to get help. Ask the customer to perform the task rather than merely watch a recording. A documented handoff should preserve configuration choices and limitations so the next administrator does not have to reconstruct the implementation. ## Review activation alongside support burden and fit Compare accounts with similar starting requirements and enough time to complete onboarding. Report the proportion reaching the agreed checkpoint, elapsed time, unresolved dependencies and the amount of assistance required. A faster average can hide a group of accounts that never finished. Keep incomplete accounts in the denominator when the definition requires them. If a segment repeatedly needs exceptional support, reconsider the promise, packaging or implementation offer rather than simply sending more reminders. ## Category-specific review Experiment results depend on assignment, exposure and outcome definitions. A user assigned to a treatment may never experience it, and exclusions can affect the comparison. Ask which analysis population the team intends to use and what stopping method the design supports. Use a synthetic allocation check and verify the outcome event before interpreting a treatment difference. Inspect missing data and unexpected group sizes. A statistical dashboard does not repair a biased assignment or establish that a small effect is worth implementing. ## Worked situation A constructed cohort contains 20 new accounts eligible to start the same workflow. Twelve can run a test allocation check and verify the primary outcome event within the chosen window, five are waiting on customer prerequisites and three are waiting on vendor work. The observed completion rate is 12/20, or 60%. The two blocked groups need different actions. Reporting only the 12 completed accounts hides the operating problem; sending all eight blocked accounts the same reminder ignores ownership. Use the cohort to decide which preparation, support or product step needs attention. ## Working worksheet | Working item | Category-specific starting point | Question to resolve | | --- | --- | --- | | First value | run a test allocation check and verify the primary outcome event | What demonstrates completion? | | Customer dependency | feature delivery and analytical data sources | Who owns access and preparation? | | Practice exercise | sample-ratio checks, a fixed decision rule and a reproducible result | Can the customer perform it? | | Blocked-step concern | A dashboard will encourage premature conclusions | What help resolves the actual obstacle? | | Operating routine | teams make decisions using prespecified metrics and valid allocation | Who maintains it after launch? | Add your evidence, owner and next action to each row. Read the [worksheet instructions](/resources/#using-worksheets) before completing the file. ## Run the review with the people who do the work Bring the data scientist into the review of sample-ratio checks, a fixed decision rule and a reproducible result. Ask them to identify the input they would actually have, the exception they expect to encounter and the person who receives the output. Then ask the growth experimentation lead which unresolved issue could change the decision. Keep the two answers separate until the team understands whether the obstacle is workflow fit, implementation readiness or commercial priority. Record any dependency on feature delivery and analytical data sources beside the affected worksheet row. A dependency should have an owner and an observable completion condition. If it changes the scope of the offer, revise the public description before the next campaign. This prevents a useful planning exercise from turning into a promise the delivery team cannot meet. ## When to change the plan Onboarding is not complete merely because the account has purchased experimented user or event; the workflow still needs evidence of use. Also check this category constraint: significance does not establish practical value or remove design bias. If new evidence changes the audience, required workflow or acceptance conditions, update the brief and explain why. Compare later results against the version of the plan that was actually used. ## Continue with the next decision Use the [lifecycle email guide](/industries/experimentation/lifecycle-email/) when that is the next unresolved task, or return to the [experimentation software marketing overview](/industries/experimentation/) to choose a different route. The [saas customer marketing hub](/saas-customer-marketing/) provides the broader method. ## Reference and scope The [primary category reference](https://docs.statsig.com/) is a starting point for checking product terminology and current capabilities. This page provides an original planning framework. It does not imply a vendor endorsement, firsthand product test, original market survey or guaranteed commercial result. ## Frequently asked questions ### Where should customer onboarding for experimentation software start? Help a new account reach a meaningful first outcome with experimentation software and an understood operating routine. Confirm the customer situation and the evidence needed for the next decision before selecting a channel, format or tool. ### What category-specific concern should the team investigate? The concern "A dashboard will encourage premature conclusions" needs an observable test or a clear limitation. Also account for the dependency on feature delivery and analytical data sources; do not assume it is already resolved. ### What does the worksheet include? It contains the working items and category-specific starting points shown on this page. Add your own evidence, owner, status and next review decision. The examples are constructed, not reported results or industry benchmarks. ### How does this connect to customer value? The customer needs to assign treatments and analyze outcomes under a defensible design. A meaningful first checkpoint is to run a test allocation check and verify the primary outcome event; the ongoing condition is that teams make decisions using prespecified metrics and valid allocation. Choose the stage appropriate to this piece of work rather than combining all three into one metric.