Service

AI agent development that takes actions. not just produces text.

AI agent development for UK SaaS, fintech, and B2B teams. We build agentic AI on LangGraph and MCP that takes real actions on real systems: writes to your DB, posts to Slack, schedules jobs in HubSpot, sends invoices in Xero. State-machine architecture, eval gold sets, audit log on every action, human escalation where it matters. The kind of agent your team can defend in a Series A diligence call.

24hreply, from a senior
100+projects shipped since 2019
Senioronly, on the spine
(Why platforms sign with us)

Agents that survive past the demo. State-machine architecture. Audit-defensible by design.

A weekend agent is a beautiful demo that becomes a customer complaint in 72 hours. We build the state machine, the eval set, and the audit log that make it production-grade.

0

0%

0

The founder this page is forworked Monday · wrong NDA sent Wednesday

Anika built her first agent in a weekend. By Wednesday it was rolled back.

01

The agent was clever. It used GPT-5. It had tool access to her Gmail, HubSpot, and Notion. It was supposed to draft outreach emails for the sales team. On Wednesday it drafted an email, attached the wrong customer’s NDA, and sent it without review.

02

The architecture wasn’t the model’s fault. The agent had no state machine. No human-in-the-loop. No audit log of which tool it had called with which args. It was a beautiful demo that became a real customer complaint inside 72 hours.

03

This page is for founders who want agents that survive past the demo. The next sections show the state-machine discipline that makes them safe.

Audit-defensible since 2023
AI agent development · the state machine pattern

State machines, in plain English. This is what makes agents safe.

Raw LangChain lets agents do whatever the model decides next. LangGraph forces every step through a named node with a defined exit. That’s the difference between a research notebook and a production system.

Property 01

Named nodes

Every state is a function. Reading the graph tells you what happens at each step.

Property 02

Typed edges

Only valid transitions allowed. No “model decided to call function X that doesn’t exist”.

Property 03

Persisted state

Agent can pause for human input + resume hours later. State survives a server restart.

Property 04

Traceable runs

Every run is a chain of nodes with inputs and outputs. Replay any case in a sandbox.

UK AI agent studio · senior-only

Six things in-house and weekend-hack agents can’t hand you

The discipline that keeps an agent defensible in a Series A diligence call, and an FCA audit.

Architecture

LangGraph state machines

Every transition typed, every node named. No swarm chaos. Auditable in production.

Compliance

Audit log on every action

Actor + tenant + tool + args + result + timestamp. Exportable for any compliance review.

Safety

Human-in-the-loop gates

Confidence threshold + escalation. Refund over £X? A human approves. Always.

Quality

Eval gold set on every release

100-300 tasks, CI-gated. A regression over 5% blocks the deploy. 94% median pass at launch.

The eight agentic-AI pains we hear in every audit

The agent pain. The day-1 architecture answer.

Each one is the difference between an agent you can defend and one you roll back on Wednesday.

  1. 01
    The wrong attachmentDay-1 architecture

    “Our agent sent the wrong file to a customer. We had to apologise.”

    Human-in-the-loop for irreversible actions. Any send, charge, delete, or commit-to-customer action goes through a human approval gate. Drafts queue in a dashboard with the agent’s reasoning.

  2. 02
    Infinite loopsDay-1 architecture

    “The agent kept calling tools in a circle and burned £2K in an hour.”

    Step budget + cycle detection. Hard step cap per run. Cycle detection breaks loops. Token budget per run. Over budget escalate, not retry. Zero infinite-loop incidents in 18 months.

  3. 03
    Debugging agent decisionsDay-1 architecture

    “The agent made a weird call and we can’t figure out why.”

    Full trace per run, replay in sandbox. Every node logs input, output, tool calls. Replay any production run in a sandbox. Tweak the prompt, the tool, the routing.

  4. 04
    The demo agent that won’t scaleDay-1 architecture

    “Beautiful demo on one customer. Falls over with ten.”

    Production-shape architecture from week one. Multi-tenant from day one. State persisted in MongoDB. Queues. Per-tenant rate limits. The demo IS the production system.

  5. 05
    Tool sprawlDay-1 architecture

    “Every new tool requires a custom integration. We’ve written eight already.”

    MCP servers + tool registry. Tools defined once via Model Context Protocol. Any agent (or any model) can call any tool. 12 MCP servers built for clients in 2025.

  6. 06
    The compliance questionDay-1 architecture

    “How do we prove what the agent did when an auditor asks?”

    Append-only audit log on every action. Every tool call: actor, tenant, tool, args, result, timestamp. Exportable. Searchable. Read-only. Your auditor reads the log and asks no more questions.

  7. 07
    Quality regressionDay-1 architecture

    “We changed a prompt and the eval dropped 12 points. Now we’re scared to deploy.”

    Eval-gated CI + auto-block on regression. Gold set runs on every PR. Drop more than 5% and the deploy is blocked. Quality stops being scary.

  8. 08
    The model swap painDay-1 architecture

    “OpenAI deprecated a model. Now our agent needs a full rewrite.”

    Model-agnostic graph + gateway. The graph runs on any model. Swap Claude to GPT-5 to Llama in config. Re-run the gold set. Cut over. Done four times in 2025.

VERTICALS SHIPPED

Six markets, fourteen agents

The agent patterns we know cold.

4

Compliance + KYC

KYC triage, sanctions screening, anti-fraud, FCA-aware design.

3

Ops + customer-success

Onboarding, churn signals, internal helpdesk automation.

2

Document review

Contract triage, clause extraction, redline drafting.

2

Patient triage

Symptom intake, urgency triage, clinician hand-off.

2

Sales automation

Lead enrichment, outreach drafting, CRM updates.

1

Inbox triage

Letting inbox triage, maintenance booking, document chase.

AI agent tech stack · LangGraph + MCP + MERN + Python + AWS

The stack we ship every AI agent on.

LangGraph for the state machine, MCP for the tools, and the AWS layer that runs the agent fleet.

T1

What we ship every agent on

LangGraph + MCP
LangGraphMCPNode.js + ExpressPython (FastAPI)MongoDBClaude 4.6 SonnetClaude Haiku 4.5GPT-5MixpanelLangSmithSentryTypeScript
T2

When your agent brief calls for it

reach when needed
Llama / MixtralPinecone / WeaviatePostgreSQLCrewAIOpenAI AssistantsHuggingFace
T3

The cloud + infra

AWS-default
AWSAWS BedrockAWS LambdaAWS Step FunctionsKubernetes (EKS)DockerSQS / EventBridgeRedisApache KafkaTerraformDatadogWebSockets
PROOF

Agents in production, real outcomes

A Series A fintech onboards 4,000 merchants/month: 82% auto-approval, 0 sanctions breaches, FCA audit passed first time. What clients say after six months.

100% would refer us
Henry G. CTO · UK FinTech
82% auto-approval on KYC and zero sanctions breaches. The FCA auditor called it the cleanest agent trail he'd seen.
01 / 06
How we work with you

Three ways to start. Pricing in the email back.

Pick the shape that fits and Mohit will send your real number inside 24 hours.

AStart here

Audit week + scope

5 days. We map your agent ambition, surface what’s automatable, write the graph.

  • 5-day senior audit
  • Eval gold set built with you
  • Signed scope, line-item GBP
  • No commitment to build
BMost common

Single AI agent sprint

6 to 10 weeks. One LangGraph agent end-to-end: graph, tools, evals, audit log, dashboard.

  • LangGraph state machine
  • MCP tool layer
  • 30-day walk-away both ways
  • IP assigns on every commit
CMigration

LangChain LangGraph rebuild

7 to 10 weeks. Take your existing chain, rebuild as a state graph, cut over safely.

  • Audit existing chain
  • Eval gold set built
  • Rebuild + parity check
  • Behind-flag cutover
From £28K · 6-12 weeks · LangGraph + MCP

“82% auto-approval on KYC and zero sanctions breaches. The FCA auditor called it the cleanest agent trail he’d seen.”

— Henry G., CTO, UK FinTech
AI agent development · honest answers

What CTOs actually ask before signing

Pain-first, soft-second.

LangGraph is graph-structured: every state transition is explicit. Swarm frameworks let agents cycle without your knowledge. That’s fine in research, harder to defend in production. If you have a strong reason to prefer another framework, we’ll work in it, as long as the eval + observability discipline stays the same.

Every action that’s irreversible (send, charge, delete, commit-to-customer) goes through a human approval gate. Drafts queue in a reviewer dashboard. The reviewer sees the agent’s reasoning, approves, edits, or rejects. Agents do reversible work autonomously, escalate the rest.

Every run is traced. You replay the failure in a sandbox. Tweak the prompt, the tool, the routing. Add the case to the gold set. CI catches it forever. Bugs you fix once stay fixed.

Eval gold set of 100-300 real tasks with known correct answers. Built with your team in week one. Every PR runs against it. Pass rate is a number you both watch. Below threshold = deploy blocked.

The graph is model-agnostic. Swap Claude to GPT-5 to Llama in config. Re-run the gold set. Cut over. Done four times in 2025 for clients without customer impact.

30-day walk-away both ways. Milestone billing 25/25/25/25. UK VAT registered, listed on Companies House, shipping since 2019.

Every AI agent development project has two senior engineers paired. Every decision into an ADR same day. Mohit reviews every PR. Two handovers in seven years, both inside 48 hours.

Yes, with 14 days’ notice. Engineers move to other projects. Spend pauses. Resume with 14 days’ notice. No cancellation fee.

Ai agents — dashboard / app screen
In context

What it looks like shipped.

ai agents, in context — the dashboards, flows and components your team actually ships, reviews and maintains.

Build the agent that survives past the demo

One paragraph. That’s it.

Tell us the action the agent should take, the tools it needs, and what your team needs to defend. Mohit replies inside 24 hours: a clear yes, a clear no, or the one question that decides it.

Write to mohit@empyrealinfotech.com Replies in 24hLangGraph + MCPAudit-defensible
What happens after the email lands
  1. < 24h

    A personal reply.

    Yes, no, or the deciding question. Straight to your inbox.

  2. Week 1

    The graph + gold set.

    We map the state machine and build the eval set with your team.

  3. Wk 8

    An agent you can defend.

    Typed graph, audit log, human gates. Clean enough for an FCA review.