The things I get asked to build most, and three ways to work together. If your problem sits between two of them, that's normal. Most do.
Services
An agent that takes a goal, works out the steps, calls your tools and keeps going until the job is done or a person needs to step in.
More on this: What I measure before an agent goes anywhere near customers
You have an agent or an automation that half works, and nobody can move it forward. I find out what is broken, fix it, and leave you something you can run without watching it.
More on this: Your agent doesn't need a better prompt, it needs a tool that fails loudly
An agent that answers your phone, books the appointment, answers the usual questions and passes the call to a person when it should.
A system that finds the right companies, collects the contact details and checks them before anyone picks up the phone.
Posts written, scheduled and published across your accounts, with the comments and messages handled.
Every lead in one place with a clear next step, so nothing sits untouched for a week.
A fast marketing site that explains what you do and turns visitors into enquiries.
A blog that keeps publishing without you writing every post by hand.
Pictures and short clips made in your own style, at the volume a campaign or a catalogue actually needs.
One screen that shows what is working, without waiting for a monthly report.
The connections that make an agent useful: your CRM, inbox, helpdesk, spreadsheets and internal software.
A private assistant that answers from your own documents and shows where each answer came from.
For teams that tried something and it did not stick. I find out why and leave you with a plan you can build or hand over.
More on this: The expensive part of an agent is rarely the tokens
What a run looks like
A trimmed down example. The agent plans, calls your own tools, stops where a person should decide, then writes the result back. Every step is traced, so the reasoning and the running cost are both on the record afterwards.
$agent run --goal "qualify today's inbound leads"
Working together
Priced before anything begins. No retainer without a reason, and no scope that grows quietly in the background.
Fixed-scope build
One agent or pipeline, scoped in writing, delivered in two to six weeks with documentation. Priced per project before we start.
Monthly partnership
A set number of days each month for improving quality, controlling cost and adding capabilities as usage patterns show up.
Audit and plan
A short, focused review of what exists: prompts, retrieval, cost, failure modes. You leave with a prioritised plan and a straight answer on what to keep.
Process
01
Thirty minutes on what your team does by hand each week, what data exists and what would count as a win. If an agent is the wrong answer, I'll say so on the call.
02
You get the plan in writing: what gets built, which tools it touches, where approvals sit, what it costs to run and what it does when things go wrong.
03
Something ends up working in the first week or two. You see progress every Friday instead of waiting for a reveal at the end.
04
Rollout behind a flag on real traffic. We watch cost and quality, fix what the real world breaks, and only then talk about adding more.
Tooling
Included in every project
Written scope and acceptance criteria
Evaluation set and tracing from day one
Documentation and a recorded walkthrough
Cost limits and a rollback path
Handover to your team if you want it
A straight answer on what not to build
Money, scope and access
It depends on the scope, and I would rather not invent a number before I have seen the work. What you get is a written scope with a fixed price before anything starts, listing what is included and what is not. No hourly surprises halfway through.
A short call to understand the workflow, then a written scope for you to approve. Build starts after that. Nothing is billed before you have agreed to the scope in writing.
You do, on final payment. That includes the prompts, the tool definitions and the deployment setup. I keep no secret half of your system, and you are free to hand it to another developer or bring it in house.
Often that is the best arrangement. I have worked as the agent specialist inside an existing team, writing against their conventions and reviewing with them, and I have delivered whole systems end to end. Both are normal.
The least that lets the job be done. Usually a sandbox or staging account, scoped API keys rather than account-wide ones, and read access to sample data. Anything with write access is set up so it can be revoked in one place.
Then I say so, and I do not take the work. A rules engine, a form or simply fixing the process is sometimes the honest answer, and it is a much cheaper one. You are not paying me to be told that everything needs an agent.
Yes, and it is part of the scope. Model calls, hosting and any third party APIs get estimated up front with a spend cap in place, so a loop that goes wrong cannot quietly run up a bill overnight.
AgentCrafts services
Let's build
Tell me what your team does by hand every week. I'll tell you honestly whether an agent is the right answer, what it would take, and roughly what it costs to run.