SDRs built ten-step sequences without ever seeing what a prospect receiving all ten would experience. Reply rates fell industry-wide and nobody's tool showed them why.
STUDY 06 / 30 · ANONYMISED · NDA · SALES AUTOMATION · US · SERIES C
SALES AUTOMATION · US A sequence builder that shows the human on the other end.
RoleLead designer
Timeline12 weeks
Team2 designers, 1 PM, 2 frontend
VerticalOutbound sequencing platform · 8,000 SDR seats
Added a recipient view - the full sequence rendered as an inbox, in order, at real intervals - as a mandatory step before activation.
Sequences got shorter and better. Reply rates rose while volume fell, which no customer had been willing to try before seeing their own sequence as a stranger would.
5 stepsMEDIAN SEQUENCE LENGTHfrom 11
4.8%REPLY RATEfrom 1.9%
-64%SPAM COMPLAINTSvs baseline
THE ARGUMENT
Why the obvious solution was wrong.
The study matters because the product problem was reframed before the interface was polished.
The sequence builder is a composer's view: steps, delays, branches, conditions. It is an excellent tool for constructing a machine and a terrible one for evaluating an experience. The SDR sees a flowchart; the prospect sees eleven emails from a stranger in nineteen days. No interface in the category rendered the second thing, so no user ever confronted it.
The recipient view renders the whole sequence as a threaded inbox with the real intervals shown, on the prospect's likely device. It is not a preview of one email. It is the experience of being on the receiving end, compressed into a scroll. We made it a required gate before activation. The first time an SDR sees their own sequence this way they cut it roughly in half, unprompted. Reply rates rose because the volume that was suppressing them was visible for the first time to the person creating it.
THE INTERFACE CRAFT
The interaction, rendered as a working product surface.
The specimen below is code-native and uses the study's own design logic. The client interface remains protected.
SALES AUTOMATION
BUYING GROUP
DESIGN DECISIONS
Positions we would defend.
Each decision names the principle and the product consequence, not a stylistic preference.
Show the receiving end
A builder that never renders the recipient's experience is optimising the wrong side of the exchange.
Make the gate mandatory
Optional previews are not used by the people who most need them. This one blocks activation.
Warnings live on the cause
A deliverability warning in a settings panel is a warning nobody reads. Put it on the step that triggered it.
PRODUCT LEADER READOUT
What transfers, and what should remain specific to this product.
A case study is useful when its operating principle travels without turning the original interface into a template.
Read the operating condition
For Outbound sequencing platform · 8,000 SDR seats, the transferable lesson is not a copied screen. It is the condition the interface had to make legible: The full sequence rendered as a threaded mobile inbox with true intervals, from the prospect's side. Required before activation. Rebuild that visibility for your own roles, risk, terminology, and operating cadence.
Protect the design rule
A builder that never renders the recipient's experience is optimising the wrong side of the exchange. Keep that rule in the acceptance criteria, component states, and production QA record so later visual cleanup cannot erase why the interaction exists.
Measure behaviour after ship
The evidence record is 5 steps for median sequence length, from 11. Recreate the baseline and outcome window before rollout, segment the result by role and context, and state clearly what the measure cannot prove.
RESEARCH RECORD
The work behind the interface.
These artefacts connect the final interaction back to the evidence and product model that produced it.
Recipient diary study
Recruited 24 people in target ICP roles to forward every cold sequence they received for six weeks, annotated with when they disengaged.
Sequence corpus analysis
Analysed 40,000 live sequences for length, interval and reply rate; the inflection was at step six, consistently.
Fatigue model
Built a fatigue curve from reply-rate decay by step position, validated against the diary study.
Gate friction test
Measured whether the mandatory recipient view reduced sequence creation. It did not; it reduced sequence length.
“I watched a rep look at her own sequence in the inbox view and delete six steps without saying a word.”
VP Sales Development, B2B SaaS · under NDA
NEXT STUDY · 07 / 30 · SALES AUTOMATION