How we build
How we build systems for manual work.
You point at one job the office still does by hand. We build the system that runs that job, and a person still says yes before a customer sees the words.
The steps
The plan, the build, and the week after.
-
The plan.
You tell us how the week actually goes. A few minutes later an email names the hand work that is worth a system, and which job should be first. That email is the Free Systems Plan. It is not a slide deck, and it is not a price.
-
The build.
When you want that system, we write the memory, the queue, the record, and the schedule around the one job you named. The lines a customer would read come back to you before they become the habit.
-
The week after.
Once it is running, the record lists what happened. A change to those lines comes back through the same queue. We will not quietly add a second job because a model could handle it.
Who it is for
People who can point at the pile.
-
A counter with several stores.
Dispensaries have harder limits on what a draft may say. We will take that work when the retailer runs more than one store. We will not take a brief that asks for a medical claim.
-
Crews, plus a desk.
Home services is the page for HVAC, plumbing, electrical, and roofing companies that already have someone in the office. Read that week first, then come back when you want the job built.
-
A restoration desk.
Restoration is the loss call, the photos, the estimate, and the status note, for water, fire, and mold companies that already have crews and someone at a desk.
What we turn down
A few briefs get a no.
-
A pile of tools.
If the note says to connect everything and see what happens, we will not start. Name the job. If you cannot name it yet, the plan is where that name shows up, and waiting is a fine answer.
-
A guaranteed outcome.
A note that asks for a guaranteed reply time, a recovered share of calls, or a doubled book is a note we turn down. The build is the job in front of you, whether that is the missed ring, the first reply, or the file.
-
A product you can already run.
Kyra, Botender, and Postwire already cover some jobs, so those jobs do not need a custom build. The products page says which one. Rebuilding a product you could turn on is a wasted week.
How a week starts
You approve the draft before it goes out.
-
Day one.
We read the offers, the hours, and the lines the office already uses. If those lines are only in someone's head, writing them down is the work, and it comes before any automation.
-
The queue.
Each draft has a person's name on it. Quiet is not a yes. If that person is out, the draft stays where it is. The wait is the point.
-
The record.
The list shows what came in, what was drafted, who said yes, and what went out. You can ask for the list. You do not have to ask us what it means.
The other doors
Other doors, when a custom build is the wrong start.
-
Run it yourself.
Kyra answers the phone, and we set her up inside a build. Botender is the dispensary chat, and Postwire is a month of posts. Botender and Postwire each have their own site.
-
See the job first.
The systems hub lists the builds and a status on each. Read the one that matches the pile before you ask us to shape a custom build.
-
What an engagement covers.
Work is the kinds of systems an engagement can cover, from the first note to a habit the office can see.
Questions
What hiring us does and does not include.
What do you actually build here?
One manual job, with a memory, an approval queue, a record, and a schedule. The first jobs we will name are missed calls, first replies, and photo quotes. We will not automate a whole department because the brief used the word automation. If the job is not repeated, and you cannot describe it, the plan will say so.
How much does it cost?
If a build follows the free plan, the price is in writing and it names the job. Ask for that number on the plan if you need it before a conversation. The reply says whether we can quote yet.
Do you replace my staff?
No. The system does the part that repeats. A person still approves anything a customer would read that commits the company. If the goal is to remove the estimator or the front desk, we will not take the job. Those people are the approval step.
How is this different from the products?
A product is something you can run without us, inside the limits written on its page. An engagement is a system built around your file, your queue, and your record. A lot of companies should start with the product. We would rather point you there than rebuild something that already runs. Tell us which one you have already tried.
How do I start?
Open the Free Systems Plan and name the job. The email shows up a few minutes after you send the note. Either way the next step is a named system, or a no. We do not start with a workshop that has no job attached.
Start
Tell us the job you want off the week.
The reply names the first system, the product that already does it, or a no.