Agentic AI & autonomous modules

What you get

The outcomes we hold ourselves to on this work. If we cannot commit to them for your project, we say so during scoping rather than after the invoice.

• A repetitive process that runs without a person driving it
• Every run traceable: inputs, tool calls, decisions, output
• Hard limits on spend, scope and blast radius
• Human approval required before anything irreversible

Deliverables

Everything on this list is handed over and documented. Anything outside it is quoted before it is built.

• Agent architecture with defined tools and permissions
• Task queue, retries, timeouts and dead-letter handling
• Full run tracing and replay for debugging
• Approval workflow for high-impact actions
• Evaluation harness for agent success rate
• Cost controls and per-run budgets

Typical timeline

Most engagements of this type run 4–12 weeks end to end. Step four absorbs the difference between the short and long end of that range.

1. Discovery call

   30 minutes, free

   We walk through what you are building, who it is for, and what has to be true for the project to count as a success. You leave with a rough scope, a rough number and an honest read on whether we are the right team.

   You receive: Written scope summary within 24 hours

2. Proposal & fixed scope

   2–3 days

   A written proposal: milestones, deliverables, timeline, price and explicit exclusions. No hourly surprises — you approve a scope, and changes to it are quoted before any work starts.

   You receive: Proposal, contract and milestone schedule

3. Architecture & design

   Week 1

   Data model, API contracts and infrastructure plan on paper before code. UI work starts in Figma so you approve screens rather than reviewing half-built pages.

   You receive: Architecture doc, ER diagram, approved designs

4. Build in weekly sprints

   Bulk of the project

   Working software every week on a staging URL you can click through. A short written update each Friday: what shipped, what is next, anything blocking. You are never guessing where the project stands.

   You receive: Staging environment, weekly demo and written update

5. Test, harden & launch

   Final 1–2 weeks

   Automated tests in CI, load and failure-path testing, security review, performance budgets, then a rehearsed deploy with a rollback plan. Launch day is uneventful by design.

   You receive: Test suite, CI pipeline, production deployment

6. Handover & support

   Ongoing

   Documentation, a recorded walkthrough and a 30-day warranty on everything we shipped. If you want us to keep operating it, a maintenance retainer picks up from there.

   You receive: Docs, walkthrough video, 30-day warranty

Questions we get asked

How do you stop an agent doing something stupid?

By not giving it the ability to. Tools are scoped narrowly, destructive actions sit behind an approval gate, every run has a spend and step budget, and the whole trace is recorded so a bad decision is diagnosable rather than mysterious.

Is an agent actually the right answer?

Often it is not. If the process is deterministic, a queue and a few rules will be cheaper, faster and easier to maintain. We will say so — agents earn their cost when the input is genuinely unstructured and the path varies per case.