Aremu Consulting Ltd · Manchester, UK Book a free fit call

A named method, published. Scope frozen in writing before a line of code.

Book a free fit call

Discover → Scope → Milestones → Handover. Changes are priced before they are done, milestones gate the build, and every project ships as a system: code, docs, tests, and a handover session.

Signature

Discover → Scope → Milestones → Handover

Four stages, each with a defined output and a handoff to the next. Discover is a separately-billed discovery/audit: £500-£2,500, credited back against a signed build of £3,000+. The drafting sheets below are the machinery of the work, published.

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 →

Guarantee

The handover guarantee

Every project ships with everything needed to run it without me.

  • Code: version-controlled, repository handed over.
  • Docs: architecture and run documentation written for your team.
  • Tests: automated tests that pass before handover.
  • Handover session: a walkthrough with whoever maintains it.

This is the standard offer on every build. Care plans are published at handover as a post-delivery option — never a consultation squeeze.

Objections

Three objections, answered up front

Will my team be able to maintain it?

What the site proves

Handover is designed into every project: code, docs, tests, and a session with your team. Care plans exist as an option, not a requirement.

What the consultation covers

Stack choices fitted to your team's skills, and a training plan for the parts they will run.

Will scope creep drag the timeline and budget?

What the site proves

Scope is frozen in writing at stage two; changes are priced before they are done; milestones gate the build.

What the consultation covers

Your specific timeline, dependencies, and a milestone map for your project.

Will it pay for itself?

What the site proves

Scoping includes naming the ROI metric, the starting baseline, and the target, so the investment is measured, not assumed.

What the consultation covers

Choosing the metric for your operation, agreeing the baseline, and agreeing how it gets measured after build.

About

About Andrew

Role
Solo builder — web and app builds, automation, AI agents
Location
Manchester, UK
Scope
Workflow automation, custom AI-agent development, software integration, bespoke web and app engineering

Andrew Aremu is a solo builder with an obsession for problem-solving — building tools, systems, and processes for small-to-medium businesses. Not an agency, not a template shop: hands-on work, a named method, and every project handed over with everything needed to run it.

Honest trade-offs: if a template or a low-code tool genuinely covers the case, that is the recommendation; a project only starts when a custom build is the right answer.