Home / How we work
How a project runs
Four stages, a fixed quote after the first one, and a person in the loop wherever a mistake would be expensive.
Workflow audit
We start with the process, not the technology. We sit with the people who do the work, in person in the Houston area or over video, and map it step by step: where the information comes from, what decisions are made, which systems it touches and where it goes wrong. We count the hours it takes today. The audit usually takes one to two weeks.
Design and quote
You get a written design: what the system will do, step by step; where it hands off to a person; which of your tools it connects to; what happens when it is unsure; the setup price; the monthly support price; and the timeline. The quote is fixed. If you decide not to go ahead, you keep the document.
Build and test
We build the system inside your accounts and tools, so you own it. Then we run it on real cases alongside your team, compare its output to what a person would have done, and fix what the test turns up. Nothing goes live until your team has seen it work on your own data.
Go live, monitor, support
The system goes live with monitoring, so we know when something fails before you do. Under the support plan we handle exceptions, changes when your process or software changes, and improvements as you see what else could be automated.
Where a person stays in the loop
Automation that runs unattended is only appropriate where a mistake is cheap and easy to reverse. Everywhere else, we design in a review step. In practice that means:
- Low-confidence cases go to a person. If the system is not sure what a document says or what a customer wants, it asks instead of guessing.
- Costly actions need approval. Sending money, sending a contract, changing a price or deleting a record waits for a person to say yes.
- Everything is logged. You can see what the system did, when and why, for every case it handled.
- You can stop it. Every workflow has an off switch your team controls, and the manual process still works if you use it.
What we need from you
- Time with the people who do the work, usually two to four hours during the audit
- Access to the systems the process touches, set up as a named user so everything is traceable
- A decision-maker who can approve the design
- Real examples, such as past inquiries, documents and records, to test against
Start with a workflow audit
Tell us which process costs you the most hours. We map it, tell you what can be automated and what it will cost, in writing, before you commit to anything.