Learn
Test whether Cascand is helping, against a real control group.
You can test whether Cascand, or a change you make, is working. Choose the outcome that counts, such as replies, meetings or opportunities, add a guardrail such as opt-outs or bounces, set up a control group, and let Cascand compare the groups. It says how much the evidence can show, and refuses any verdict the numbers cannot support.
How it works
How an experiment runs.
- Step 1
Define the experiment and the outcome.
Name it, state the hypothesis, and choose what counts as success: a reply, a meeting booked or an opportunity created. Add a guardrail if you want one, such as opt-outs or bounces. Three kinds of test are built in: hold Cascand's recommendation back from the control group, give the treatment group's drafts a different style direction, or change the follow-up timing for the treatment group.
- Step 2
Assign groups at random.
Assign by hand or let Cascand randomize. There is a minimum size per group, so a result is never read from too little.
- Step 3
A guardrail watches.
If the treated group breaches the guardrail, the experiment stops there and its result can never be confirmed. Nothing is confirmed automatically.
- Step 4
Read what it found.
Each result says plainly what it can show, and anyone assigned to a group but never actually contacted is counted as unreached rather than as a result either way. Cascand confirms nothing from a breached guardrail, a lopsided split, too little exposure or too small a sample. A valid result becomes a proposal that an administrator on your team adopts or declines once, on the record.
In your hands
What you control.
- Who is in each group. Cascand never starts, reassigns or acts on an experiment; you do.
- What counts as success, and what counts as harm.
- What you conclude, and whether a result is adopted.
Enough people to randomize across, and time for outcomes to arrive.
Questions
Questions people ask.
Keep exploring
Where to go next.
Next
See it with your own work.
Tell Cascand about your business and see what it would build. A person on our team reviews every application.