FAQ
Common questions
The questions that come up before a call, answered directly. If yours is not here, ask it on the call.
What does a project cost?
It depends on the process, the tools involved, and how many edge cases it has. After we scope it, you get a fixed quote before anything is built. There is no hourly billing.
How long does a build take?
A focused automation can be running in one to two weeks. A system that connects several tools with review steps takes longer. You get a timeline with the quote.
Do I need to replace my current tools?
No. I build around the tools you already use. Replacing them is rarely the answer, and it usually adds cost without fixing the process.
Can you fix an automation someone else built?
Yes. I audit what exists, document how it works, and either harden it or rebuild the part that is not reliable.
What happens when my process has exceptions?
Exceptions are where most automation fails. I map them first and decide whether the system handles them, flags them, or routes them to a person.
Do I own the system?
Yes. It runs in your accounts and you own it. You get documentation and a walkthrough so your team can operate it.
Do you offer ongoing support?
Yes. After launch, ongoing support keeps the system current as your tools, data, and needs change.
Which tools do you build with?
n8n and Make for automation, AI models where judgment helps, and custom code when a tool cannot do the job cleanly. The choice follows the problem.
Is my data safe?
The system runs inside your tools and your accounts. Access is limited to what the workflow needs, and sensitive steps stay behind review where it matters.
How do we start?
Book a discovery call. You show me the process, and we decide together what is worth building first.
Still have a question?
Bring it to a call. Show me the process and we can work out what fits.
Book a discovery call