Ship the thing that runs the thing.

One senior builder: web apps, workflow automation, and custom AI agents for small-to-medium businesses. Named method. Handover guaranteed. Manchester, UK.

Entry work from £2,200 — fixed tiers, published up front →

agent-log / scope-analysis (demo)
aremu-scope --analyze "claims intake workflow"
Parsing workflow description...
→ 7 manual touch-points identified
→ Candidate: n8n + Zoho CRM webhook
→ Generating written scope...
✓ scope-brief.md [438 words, 4 milestones]
✓ milestone-map.json [Discover→Scope→Build→Handover]
One person, no agency overhead· Named method· Handover guaranteed· Every build ships code + docs + tests
Services

Three service lines

I cover the whole build-to-automate journey myself, which keeps the price honest. Each line is custom-scope; every project runs through the same named method.

Website & App Build

A custom application that fits how your business actually works, not a template forced onto your process.

React/Next.js front-ends and PostgreSQL backends, developer-built, tested, and documented for portals, member systems, and internal tools.

See Services →

Workflow & CRM Automation

Stop copying data between systems. Connect Zoho, Google Workspace, and your CRM so leads, orders, and reports move themselves.

Custom n8n workflows, Deluge scripts, and webhooks that run your busywork automatically: no copy-paste, no missed steps.

See Services →

AI Agent Development

Autonomous AI workers trained on your own documents to qualify leads, triage inquiries around the clock, and log to your CRM with no human copy-paste.

Built for a named workflow on advanced harnesses (pi.dev, OpenClaw, Agent Zero), with guardrails and logged behaviour.

See Services →
Method

Discover → Scope → Milestones → Handover

The named delivery method, published so you can judge predictability before you commit. One “you receive” line per stage; the full spec is on the Approach page.

The named delivery method: Discover, Scope, Milestones, Handover Four drafting-sheet stages stacked on a vertical rail, each showing input, what happens, what you receive, and the handoff artifact. STAGE 01 · DISCOVER input: brief · current state Understand the problem before the first fix. WHAT HAPPENS A working session on the problem, constraints, and the systems you already run. YOU RECEIVE written problem statement · fit assessment HANDOFF scope brief STAGE 02 · SCOPE input: discovery outputs Scope frozen in writing. Changes priced before done. WHAT HAPPENS Deliverables, architecture direction, and explicit out-of-scope, written down and agreed. YOU RECEIVE written scope · milestone map · pricing shape HANDOFF signed scope STAGE 03 · MILESTONES input: signed scope Fixed-price milestones. Nothing drifts. WHAT HAPPENS The build is split into milestones with a defined done state and a review at every gate. YOU RECEIVE milestone plan · change-pricing policy HANDOFF accepted milestones STAGE 04 · HANDOVER input: accepted milestones Ships as a system, not a deliverable. WHAT HAPPENS Code, docs, tests and a handover session; maintenance offered at handover, not a squeeze. YOU RECEIVE code · docs · tests · handover session HANDOFF production + maintenance decision

→ scroll →

  1. Discover: you leave with a defined problem statement. Why it protects you: we agree what “done” means before any pricing.
  2. Scope: a written scope, milestone map, and pricing shape. Why it protects you: scope is frozen in writing, so costs don’t creep.
  3. Milestones: each stage gates the next. Why it protects you: you approve and pay in stages, never all up front.
  4. Handover: code, docs, tests, and a walkthrough. Why it protects you: you can run it without me; a care plan is optional.

See the full method on the Approach page →

Proof

Results, across three different operations

The same method, applied to three different industries. Full breakdowns (stack, trade-offs, and what the client runs today) are on the Projects page.

// case study — Accident Claims Intelligent Automator

Problem

A claims-management firm was losing the “golden hour”. Accident reports arrived as unstructured text, and by the time a person read and re-keyed each one, a competing insurer had already reached the claimant.

Architecture

A 24/7 automation reads every new report, runs liability triage against the firm’s criteria, and drafts the right first response for non-fault, at-fault, and third-party claimants. Registration numbers, accident notes, and contact details then sync into Zoho CRM automatically.

Trade-off

Anything with write access is model-drafted but routed through human review before it is sent. The guardrail costs a few minutes but keeps a person accountable for every message that leaves the firm.

Outcome

Reports are triaged in seconds rather than hours, the team works only the files that pass triage, and every record lands in the CRM complete — no manual re-keying.

Food operations

MealPrep.exe

Replaced spreadsheets, WhatsApp, and notebooks with one local-first app: menus, online ordering, batch counts, shopping lists, and delivery routes. Read the case study →

Contact centre

Connex-One Data Bridge

Watches the dialler inbox 24/7 and writes clean call, campaign, and agent data into one dashboard, reclaiming the 30–60 minutes supervisors lost each morning. Read the case study →

See all five project breakdowns →

Fit

Who Aremu is built for

If you want a churning dev shop with junior account managers, that's not us. If you want one senior builder who owns the architecture from end to end, let's talk.

Built for

  • Owners who want manual busywork turned into systems that run themselves.
  • Operations where spreadsheets and templates have stopped being enough.
  • Buyers who want one accountable person, not a hand-off chain.

Not a fit

  • A cheap template, fast. If that honestly covers it, that's the recommendation.
  • A 24/7 managed-service desk: work is handed over, not round-the-clock.
  • A full product squad: there's a ceiling to one builder.

Book a free fit call