Modeled · method in the open
What a deployment looks like
Three deployment shapes we scope most often, each one built from the inputs of our ROI calculator. Every page shows the arithmetic behind its numbers, marks which figures are pilot targets, and names what it assumes we would connect.
These are models, not customer reports. No client, no logo, no measured result — read them as the shape of a pilot and the numbers it would run against.
Modeled scenarios
A 22-person B2B software company
target · +34% meetings booked
A digital SDR has the reply to every inbound lead written before anyone opens it, and the rep sends it.
Read the scenario and its arithmetic →
A 14-person marketing agency
target · 28 hrs/week handed off
Two AI employees draft the client-status and project-ops answers, and two account managers get their week back.
Read the scenario and its arithmetic →
An 8-person outpatient clinic
target · no-shows 18% → 11%
An AI front desk keeps the booking, reminder and reschedule loop running while one person covers the desk.
Read the scenario and its arithmetic →Methodology
Where these numbers come from
A number you cannot reproduce is decoration. Here is the whole method, so you can rebuild any figure on these pages yourself — or replace our assumptions with your own and see what comes out.
01 · Source
Four inputs, the same ones the calculator exposes
A scenario is fixed by the role, the hours a week that role spends in its routine loop, the share of that loop handed to the machine, and the loaded hourly cost of the person doing it today. Nothing else feeds the numbers.
02 · Arithmetic
Hours freed, then priced at your loaded rate
Baseline hours times headcount times the handoff share gives the hours a week that move. Those hours times the loaded rate times the weeks in a month gives what they cost today, and the platform fee sits opposite it. The detail page prints the multiplication for each scenario.
03 · Targets
Percentages are targets a pilot runs against
Uplift in booked meetings, share of tickets resolved, no-show rate: each one is agreed before a pilot starts, measured in your own systems, and reviewed at the end. A target is a commitment about what we aim at, and it stays a target until your data says otherwise.
04 · Assumed
Each scenario names the connections it assumes
A modeled deployment often needs a tool we do not ship a connector for yet. Rather than implying it exists, every scenario lists what it assumes we would connect, so the scoping conversation starts from the same picture you read here.
05 · Boundary
No client, no logo, no averaged result
These are archetypes drawn from the deployments we scope most often. No figure here comes from a customer account, and none of them is an average across accounts. When we have measured results to publish, they will arrive with the account that produced them.
The calculator holds the same four inputs and the same formula.
Want a scenario for your industry?
Send us the role and the volume it handles. We come back with the closest scenario, the arithmetic behind it, and the KPI a pilot would run against.