Why the name is 12 hours.

Twelve hours is small on purpose. Small enough to reach without new headcount, large enough to spend on thinking, making, or simply finishing on time. It is a measure to work toward, not a slogan.

Who you'll work with

Aaron Taylor

Founder, 12hours.tech

I build and operate agentic systems every day.

5.04 reviews · Personal coaching

Usually replies within one working day.

Taking on new coaching clients. One or two engagements at a time.

  • Founder of 12hours.tech.
  • Builds and operates agentic systems every day.
  • Works hands-on: no account managers, no hand-offs.
  • Teaches the same methods on your material, not demo data.
  • FreeFirst sessionfirst 20 minutesFree first session — no card.
  • $8930-minute unstick30 minutes
  • $15060-minute working session60 minutes
  • $390Three-session packthree 60-minute sessions

Free first session, then pay per session. No subscription required.

Cancellations: Reschedule or cancel up to 24 hours before a session for a full refund. Project work is quoted once, fixed, and paid in stages.

The rules we hold ourselves to.

  • Start with the work

    We watch the job before we name a tool. The tool is the last decision, not the first.

  • Show the number

    If something saved time, we can point at how. If it didn't, we say so.

  • Hand it over

    Systems we build are yours to run, change, and extend without us.

  • Keep the judgement

    We remove labour, never the thinking that makes the business yours.

How the systems are built

What's actually running, and how we know it works.

We implement rather than advise. Every system is built in your stack and your accounts, with evaluations before it ships, and handed over with the code and the documentation.

  • Models and orchestration

    We pick the right model for each step and orchestrate between them, so you are not locked to one vendor or one chat window.

  • Evaluations before anything ships

    Every workflow gets a test set built from your real examples. Nothing reaches production until it passes on those.

  • Guardrails and human in the loop

    Steps that carry risk stop for a person. The system proposes the action; a human approves it before anything irreversible happens.

  • Monitoring and logs

    Every run is logged, so failures are visible and fixable instead of silent. Exceptions are surfaced, not buried.

  • Retrieval over your documents

    Search and extraction run over your own files and data, with your permissions respected, rather than a generic model guessing.

  • Your accounts, your code

    Systems run in your infrastructure. Handover includes the integration, the evaluations, and the documentation.

What handover includes

  • The integration, running in your accounts and your stack.
  • The evaluation set used to test it, so you can re-run it after any change.
  • A short runbook: what it does, what to watch, what to do when something looks wrong.
  • A session with your team, so the system outlives the project.

What twelve hours buys.

One and a half working days, every week. Enough to clear the backlog that never clears, to think instead of react, or to finish on time for once. It is the unit we use to ask whether any change was worth making.

That's the pitch. There isn't one.

If any of this matches how your week feels, tell us where the time goes.