A SaaS customer journey crosses marketing pages, signup, onboarding, product prompts, sales and lifecycle messages. A local optimisation can move one metric while weakening another team’s outcome.
Shared decision history gives growth teams a common learning layer without replacing their product analytics or experimentation stack.
SaaS decision history links cross-functional growth changes to hypotheses, evidence and downstream outcomes so acquisition, product and lifecycle teams can reuse each other’s learning.
Organise around the customer journey
Record the affected audience and journey stage: discovery, evaluation, signup, activation, expansion or retention. This makes related changes discoverable even when separate teams use different campaign names.
Connect positioning to product behaviour
When a promise, use case or audience changes on the website, name the product behaviour and downstream outcome expected to improve. Preserve sales-quality or retention guardrails alongside signup conversion.
Keep pricing and packaging context durable
Record the old and new package, affected cohorts, migration policy, commercial hypothesis and review window. Pricing decisions have long tails and are especially dangerous to reconstruct from memory.
Surface related experiments before launch
Search by problem and audience before creating another test. A result from onboarding may change how a landing-page idea should be framed, while a sales objection may explain an acquisition result.
Preserve the difference between learning and rollout
A successful experiment supports a decision within tested conditions. Record whether the team rolled it out, where exceptions remain and which follow-up evidence is still required.
Clear answers
Frequently asked questions
Does this replace a product experiment repository?
It can reference that repository while bringing marketing, sales, lifecycle and operational decisions into the same searchable context.
Which SaaS metrics belong in a decision record?
Use the closest behavioural measure plus downstream guardrails appropriate to the journey stage: activation, qualified pipeline, retention, expansion or support burden.
How should teams treat a test winner?
Record the tested audience, conditions, effect, uncertainty and rollout decision. Avoid turning a bounded result into a universal best practice.
Make this part of the next decision.
Diffined keeps the change, reason, evidence and conclusion together in one private history.
Try the working prototype ↗