Simulations and experimentsConcept
Test a change before your buyers do.
Simulations would estimate what a behavior change is worth before you coach it. Experiments would then run it on real calls with a comparison group, so the result is evidence and not a guess.
AnswersIf my team paused before answering objections, what would change?
Concept. Direction only. This is not in the product and has no release date. It is here so you can see where the system is going and tell us if it matters to you.
How it would work
- 01
Pick a change
Pause before you respond. Ask before you explain. A behavior Bylda already measures.
- 02
Simulate
Estimate the effect from patterns already observed, with the uncertainty shown as a range.
- 03
Run it
Coach one group, hold another, measure both the same way, and read the difference.
What you see
Read off the screen above. Every number is sample data from the app’s own prototypes, arranged in an illustrative layout.
- Hypothesis
- After an objection, pausing before responding is associated with more next steps booked.
- Groups
- A coached group and a comparison group, matched on segment and stage.
- Readout
- The same measures as behavior change results, with the confidence stated.
Who it’s for
Know which coaching is worth the team’s time before rolling it out.
Practice changes that have been shown to matter, not the flavor of the month.
Where it fits
Bylda is one loop. Simulations and experiments is the change step.
- EventsWhat happened on the call
- BehaviorsHow the rep acted
- PatternsWhat repeats, for whom
- OutcomesWhat it travels with
- ChangeOne focus, then measured
What it won’t claim
- Concept. Not in the product and no release date.
- Simulations would show ranges, not promises. Today the product measures change after coaching and labels association as association.
Also in Next
The whole product
What happened on the call, named as behavior.
Whether the behavior changed, with the confidence stated.
Where the system goes after V1. Not in the product yet.
