Services and pricing
One workflow at a time. Audit first, then build, then hand over the repo and runbook. If the audit says don’t build, you keep the ranked list.
Is your workflow a good candidate?
- Repeats weekly with clear inputs and outputs
- Costs hours of copy-paste, triage, or reporting time
- Runs inside tools with APIs (CRM, helpdesk, warehouse)
- Has a human who can confirm the correct outcome
Not sure? Bring it to a working session — we scope it or rule it out in 30 minutes. Team context: AI work for teams.
Workflow audit
Two weeks on one process. You get time costs per step and a ranked build list.
- One process mapped end to end
- Time cost per manual step
- Ranked list of automatable steps
- Build vs. skip recommendation
- 90-minute walkthrough call
Build engagement
I build the top-ranked workflow against your APIs, with logs and handoff.
- Everything in the workflow audit
- N8N or LangChain build
- Wired to your CRM, helpdesk, or warehouse
- Retries, logging, and a kill switch
- Weekly 30-minute review
- 30-day fix window after handoff
Retainer
For teams with a queue of workflows. We work it down, one system at a time.
- Named engineer (Matt)
- One active build at a time
- Shared backlog, re-ranked monthly
- Two team working sessions per build
- Runbook per system
- Email support on business days
What you receive (every build)
- Scoped workflow: documented path, success measures, exclusions
- Working automation against your APIs — N8N or LangChain, tested on real data
- Retries, logging, escalation, and a kill switch
- Repo, workflow JSON, credentials map, and runbook
- Two working sessions where your team runs the system
- 30-day fix window after handoff
How engagements run
- Find — map the process, attach time cost per step
- Design — architecture, integrations, acceptance criteria
- Build — implement, test, wire to your stack
- Handoff and improve — runbook, monitoring, next opportunity
See the approach in practice: selected work · AI readiness guide.
Frequently asked questions
What if the audit says don't build?
You keep the ranked list with time costs. No build is proposed and no further fee is due beyond the audit.
Do you replace our existing tools?
No. Builds wire into your CRM, helpdesk, and warehouse via API. Credentials stay in your vault.
Who owns the system after handoff?
You do — repo, workflow JSON, and runbook. Every run is logged so your team can operate it without us.
When is AI not the answer?
Deterministic steps stay deterministic. LLMs and retrieval are used only where judgment or language understanding changes the outcome — decided during the audit.
How I work
- One process per engagement — we finish the intake-to-filed path before starting the next one
- You keep the artifacts — repo, workflow JSON, credentials map, and runbook
- Logged runs — every automated run writes a log you can read without me
- Kill switch — every build ships with a way to turn it off
Not sure which tier fits?
Bring one workflow to a 30-minute call. We scope it or rule it out.