Common questions
What clients
actually ask.
Honest answers to the questions that come up on most discovery calls — pricing, ownership, what happens when things break, and what I won't take on.
01
I don't see testimonials — what's your background?
I built out a portfolio of complete, working reference systems before taking on paid clients — the five above. That was deliberate: I'd rather you watch the actual work than read a wall of logos. First-cohort engagements open in 2026, and early clients get fixed pricing, extra attention, and direct access throughout the build.
02
How much does a typical project cost?
Fixed-price builds start at $1,200 USD and scale with complexity. Most engagements fall between $1,500–$4,000 for a single workflow including discovery, build, documentation, and 30 days of support. First-cohort clients get founder pricing — lower than the rates I'll list publicly once there are testimonials in this section.
03
Who owns the workflow once it's built?
You do — completely. Workflows run on your n8n instance, against your credentials, in your accounts. I provide a full runbook and a Loom walkthrough at handoff so your team can run and modify the system without me.
04
What happens when something breaks at 2am?
Every workflow ships with three layers of resilience: continue-on-fail on every external API call, structured error logging to Airtable, and Slack alerts to a dedicated channel. Most failures are visible within 30 seconds and recoverable without my involvement.
05
What kind of projects do you turn down?
Anything that needs a frontend, anything that requires real-time machine learning training, and anything where "AI" is the goal rather than the solution. If a deterministic workflow would do the job better, I'll tell you on the call.
06
How does your AI not hallucinate?
Every AI call returns strict JSON validated by a Code node downstream. Parse failures route to a manual-review queue with sane defaults. For RAG workflows, answers must cite retrieved context — when context is missing, the system escalates rather than guesses.