Methodology

How we ship AI agents that actually run in production.

Most AI projects fail at deployment, not at demo. theagency47's 5-phase methodology (Discover, Design, Build, Deploy, Optimize) exists to push the failure-prone moments forward, into the cheap-to-fix phases, so the expensive phases (build, deploy) carry only solved problems.

How does theagency47 deploy AI agents?

theagency47 deploys AI agents through five phases, Discover, Design, Build, Deploy and Optimize, each with explicit gate criteria. Discovery produces an agent shortlist, Design a signed one-page spec per agent, Build an agent that passes its eval suite, Deploy a period of human-in-the-loop monitoring, and Optimize weekly KPI tuning until performance is stable and the agent is handed over.

theagency47 · Updated November 2026
The 5 phases

Each phase has a gate. No phase starts until the previous one closes.

These phases run inside every project. For company-wide programmes, see the AI transformation roadmap and how we run AI transformation for mid-size and large companies.

Phase 1 · ~10% of timeline

1. Discover

Goal: Pick the right agents to build.

We walk through your processes, what you do, where the unbillable hours live, where errors cluster. Output is a shortlist of candidate agents, each scored on three dimensions: hours reclaimed, error rate reduction, throughput gain. We do not build agents that fail any of the three. You can simulate payback period for the "hours reclaimed" dimension before the call.

Gate: Client sign-off on the shortlist.

Phase 2 · ~5% of timeline

2. Design

Goal: Make the work specifiable.

A one-page spec sheet per agent: job-to-be-done, inputs, outputs, tools, autonomous decision boundaries, escalation rules, KPIs, eval cases. This is the single most under-rated phase in agent work. Specs prevent scope creep, anchor refunds, and force "vibes" into "verifiables."

Gate: Signed spec sheet per agent.

Phase 4 · ~15% of timeline

4. Deploy

Goal: Run safely in production.

Production cutover with human-in-the-loop monitoring for 14 days. Every agent action is reviewable by a human before downstream effects, through approvals in OS47. Team training session delivered. Monitoring and alerting wired before traffic flips.

Gate: high pass rate on real tasks during the 14-day review, with human oversight.

Phase 5 · ~10% of timeline

5. Optimize

Goal: Hand over a stable system.

KPI dashboard tuned. Weekly optimization until performance is stable across two consecutive reporting cycles. Agent moves from human-in-loop to autonomous-with-sampling. Documentation finalized. Handover ceremony.

Gate: Two consecutive stable reporting cycles. Client signs handover.

After handover

Retainer (optional)

Once handover closes, clients can opt into a monthly retainer for ongoing optimization, health checks, and new agent builds.

Why this methodology

Three things this methodology does that most don't.

1. Specs come before prompts

The default AI agency pattern is "let's try a prompt and see what happens." This produces demos but not deployments. We refuse to write a prompt until a one-page spec is signed. This shifts the riskiest decision (what is this agent actually for?) into the cheapest-to-revise phase.

2. Evals come before launch, not after

"We'll improve it in production" is how AI projects fail. We build the eval suite alongside the agent and gate launch on pass rate. The eval suite then re-runs automatically after every change in production. If an update breaks an eval, the update reverts. This is what "production-grade" actually means.

3. Handover is a hard gate, not a checkbox

The default agency pattern is "we'll deploy and then bill you forever for maintenance." We deploy, optimize until stable across two consecutive cycles, then hand over to your team with the source files. Clients can then opt into a retainer, but it is a choice, not a captivity. Full ownership transfers to you upon final payment at handover.

Tooling

The stack we standardize on.

theagency47 standardizes on a small, opinionated stack so we ship faster and clients can take ownership without a steep learning curve. For the broader frame of how this methodology maps to the three levels of AI in a business, and to why we built theagency47 as a delivery agency rather than a consultancy, see those pages.

  • Models: A mix of LLMs (Claude, GPT, Gemini and open-weight models): frontier reasoning models for executive-tier agents, balanced models for operational, fast low-cost models for high-volume task work. Model choice documented per agent.
  • Agent runtime: provider tool-use APIs behind a model gateway, so models can be swapped without a rebuild; LangGraph or custom orchestrators for multi-agent flows when warranted.
  • Knowledge bases: An AI company brain: plain-markdown files as the source, retrieval-augmented search over them once size requires it, versioned KB checkpoints.
  • Integrations: Direct API calls (no Zapier middleware in production paths). Standard catalog includes Gmail, Slack, HubSpot, Salesforce, Notion, QuickBooks, Xero, Google Workspace, Microsoft 365, Asana, Linear, Zendesk, Intercom, Stripe.
  • Eval framework: Custom test runner with JSON-based test cases and rubric-based scoring; integrates with Anthropic's evaluation tools where available.
  • Monitoring: Per-agent dashboards with throughput, accuracy, latency, cost, and escalation rate; alerts on threshold breaches.
  • Compliance: GDPR by default, Anthropic DPA signed, Anthropic API data kept for 7 days and never used for training.

The full stack is documented in the engagement contract. Clients receive the full source (prompts, configs, KB schemas, eval cases, integration code) upon final payment at handover.

Boundaries

What we deliberately do not do.

Methodology means what we exclude as much as what we include. Five things theagency47 does not do:

  1. We do not bill by the hour. Projects are fixed price. Retainers are flat monthly. Hourly billing creates the wrong incentive for everyone in the room.
  2. We do not deploy without an eval suite. If it cannot be tested, it cannot be deployed. No exceptions.
  3. We do not deploy without an escalation rule. Every agent has at least one ambiguity-handling path. Silent failure is the worst failure mode.
  4. We do not retain ownership of client work. Source files, prompts, configurations are all yours upon final payment at handover. If you part ways, you keep the agents.
  5. We do not take agent work outside our delivery competence. Real-time low-latency reasoning, physical perception, life-safety decisions, we say no and recommend specialists.
FAQ

Questions about how we work.

How long does an AI agent project take?

Spark = 14 days · Workforce Starter = 30 days · Workforce Pro = 60 days · Scale package = 90+ days. Each phase is gated. See pricing for tier details.

What is in an agent spec sheet?

One page, eight fields: job-to-be-done, inputs, outputs, tools available, autonomous decision boundaries, escalation rules, KPIs, eval cases. Client signs before any building.

What is an eval suite?

20–30 test cases per agent with known expected outputs. Split common-case (60%), edge-case (20%), adversarial (15%) and regression (5%, growing as production fixes are added). Must pass 90%+ of our internal eval (how we test) before go-live. Re-runs automatically after any production change.

What is human-in-the-loop monitoring?

For 14 days after deployment, every agent action is reviewed by a human before downstream effects. After 14 days, with a high pass rate on real tasks during the 14-day review, the agent moves to autonomous mode with sampling-based audit.

What happens if the agent fails an eval in production?

Automatic revert to the last passing version. The change that broke the eval is investigated. Production fixes go through the same eval gate as initial deployment.

How does the methodology change for retainer work?

Same five phases, smaller scope. New agents added under a retainer follow the full Discover → Optimize cycle, just compressed (typically 5–10 days for a task-tier agent under retainer).

Free · 30 minutes · No deck, no pitch

Find the 3 processes eating most of your team's hours.

In a 30-minute discovery call we map how your team's week actually goes, name the three processes that cost the most hours, and tell you honestly whether an AI agent is the right fix. If it isn't, we'll say so.

We reply within one business day with a calendar link. Want it in writing? The AI Audit adds a written report with ROI projections, and the €297 is credited in full if you start a project within 30 days.

Prefer to write it down? Describe your agent in 2 minutes →

Part of