Essay
What we chose not to automate
The moments we leave with people on purpose, and why that call matters more than anything we build.
Every diagnosis ends with two lists. The first is what a system should carry. The second is what it should never touch. Clients usually ask about the first list. The second one is where the judgment is.
The rule
If the relationship is the product, a person does it. A system can get the right person there faster, with the right context. It should not stand in for them.
What stays human
The showing. A buyer deciding on a home wants the agent, not a sequence. Our real estate flow answers the inquiry and offers times; the agent books the viewing and makes the call.
The quote conversation. A homeowner with a broken air conditioner wants to know someone competent is coming. The system texts back and drafts the quote from the price sheet; the office checks it and sends it.
The consultation. A med spa client is trusting the practice with their body. Reminders go out on schedule. The treatment plan, and the call to a client who has not rebooked, belong to the front desk.
The offer. A product brand's emails can send on their own, but a person approves every message and reads the weekly report before the next offer goes out.
Why it matters
Automation that replaces the relationship makes a business cheaper to run and easier to leave. Automation that protects the relationship gives people back the hours they were spending on retyping and chasing, so they can spend them on the conversations that win the work.
That is the trade we are making on every build: the system does the repetitive part, and a named person on your team decides.