CASE STUDY
The system that never forgets a lead
Ataman Studio · design-build firm, Los Angeles
SEVEN CONNECTED SYSTEMS · 10,000+ PRODUCTION EXECUTIONS · RUNNING IN PRODUCTION
Every design-build firm loses the same way. Not to a better competitor — to a Tuesday.
01 — THE PROBLEM
It shows up as a quarter under plan
An enquiry arrives while the team is on site. A consultation happens and nobody writes up the notes. A promising client goes quiet and nobody follows up, because following up is everyone’s job in a week when everyone is busy. None of it feels like a loss at the time. It shows up later, as a quarter that came in under plan for reasons nobody can name.
Ataman Studio did not need better marketing. They needed the work between “someone enquired” and “someone signed” to stop depending on whether a human remembered.
02 — THE BUILD
What we built
Seven systems, each owning one stage of the lifecycle, all writing into the same record. Nobody at Ataman had to learn a new tool — the work happens inside the email and project tracking they already used.
1Nothing arrives unnoticed
Two entry points feed one pipeline. Booked consultations come from the scheduling system; everything else arrives by email. Both are read, structured, and turned into a tracked record with the details already extracted — service type, scope signals, timeline, context.
A deduplication layer sits in front. If the person has written before, the message attaches to their existing record instead of creating a second one. Nobody works the same lead twice, and nobody answers a returning client as a stranger.
2Every enquiry gets read and ranked
Each new message is classified before a human sees it: a real prospect, a maybe, or noise. Prospects surface immediately with the reasoning attached. Noise is filed without consuming anyone’s attention.
The point is not to replace judgment. It is that by the time someone looks, the ten enquiries in the inbox are already ordered by which one is worth answering first.
3Follow-up happens on schedule, not on memory
This is where firms lose the most money, and it stays invisible because nobody logs the follow-up that never happened.
Every morning the system reviews every open lead and works out where it stands. At two days, five days and ten days, a follow-up is drafted — written against the actual thread, referencing what was actually discussed, not a generic nudge. Leads that stay silent past the cadence are marked stalled and stop consuming attention.
The drafts are drafts. They land in the inbox for a human to read and send.
4The moment someone replies, the sequence stops
The failure mode of every follow-up system is the automated nudge that arrives after the client already said yes.
A separate system watches for replies on known threads, reads what the reply actually means — engaged, declining, or an out-of-office auto-response — and updates the record accordingly. An engaged reply stops the sequence instantly. A polite decline closes the lead. An auto-responder changes nothing, because it is not a person.
5Every meeting becomes a written record
Consultations get recorded. The recording flows in automatically, is parsed, matched back to the right lead, and attached to their record — without anyone renaming a file or remembering which client it belonged to. If it belongs to a lead nobody logged yet, a record is created.
6Every meeting becomes a drafted proposal
Once the transcript lands it is summarised into what matters: what the client asked for, what was agreed, what happens next.
Then the follow-up is drafted according to what kind of project it is — a feasibility conversation, a standard build, or a standard build on an expedited timeline. Three situations, three different letters, each drafted from what was said in the room. Again: drafted, then sent by a human.
7The record closes itself
When the reply is finally sent, the system sees it and updates the lead’s status without anyone touching the tracker. The record reflects reality because reality updates the record.
03 — DESIGN
Why it holds up
A human at every outbound point. The system reads, classifies, schedules, drafts and tracks. A person still presses send. Every design decision here keeps a human in the position where the firm’s reputation is on the line.
No new tools for the team. It runs behind the email and tracker they already had. There was no migration and no rollout — the difference appeared inside tools people were already opening every day.
Built to be handed over. Source code, credentials and documentation belong to the client. It runs on their accounts, not on a platform they rent from me.
Proven under load. Over 10,000 production executions across the seven systems since launch.
04 — OUTCOME
What changed
The firm stopped losing leads to timing.
Enquiries are answered while they are still warm rather than whenever someone reaches the inbox. Follow-up at two, five and ten days happens every time instead of when the week allows. Consultations turn into written proposals the same day instead of joining the pile of things to write up. And when a client replies, they get a person — not the next scheduled message from a machine that did not notice.
None of that required anyone at Ataman to change how they work. It required the work between the conversations to stop being manual.
05 — FOR YOU
Could this run for your firm?
Most of it transfers directly. The lifecycle is the same for any design-build, remodeling or specialty contractor: an enquiry arrives, a conversation happens, a proposal follows, and somebody has to keep track. What changes is which tools it plugs into, and which stage is costing you the most right now.
Start with one stage. A first system is typically two to four weeks and starts at $3,000 — fixed scope, written before anything is built.
Tell me where your leads go now.
Tell me where your leads go now and what happens when someone goes quiet, and I will tell you which stage is worth automating first, and whether it is worth it at all. If it is not, I will say so.