Custom systems · delivered by milestone

Set the scope first,
then agree the milestones

Marketing sites, tool sites, back offices, site networks, mini-programs and dashboards differ, but follow one path: written scope, approved prototype, joint build, handover with docs. No price list; quotes follow scope and milestones.

Write the scope Freeze prototype Build and test Hand over docs

Five misreadings about custom work

All start with quoting before scoping, and all surface half way through.

What people say

  • Custom work is one person for a month
  • A written brief can start at once
  • Launching is the finish line
  • A template is cheaper
  • Our own team can do it

Reality

  • Schedule follows scope and interfaces, not a guessed month
  • A brief must be testable; what you exclude matters too
  • Launch needs a trial period and docs, or nobody dares edit
  • A template saves the first cheque, not the later pain
  • In-house means paying people and covering absence

Six common system types

All of them are systems; the hard part differs a lot.

Corporate marketing site

Brand, products, content and enquiries; speed and SEO structure decide.

Tool and query sites

Input in, answers out; a stable source and indexed results are the work.

Back office and admin

Roles, approvals, reports and reconciliation; process and consistency.

Site networks, multilingual

Many domains and languages in one place; template reuse and URL rules.

Mini-programs and booking

Booking, orders and notifications; payment and fulfilment close the loop.

Data dashboards

Scattered sheets into one view; consistent definitions and refresh cadence.

Four delivery steps

Every step produces something you can look at, not one reveal at the end.

01

Write the scope

What is built, what is not, and how acceptance is judged, all in writing.

Write the scope
02

Prototype and interfaces

Key screens as wireframes, third parties listed, then the build starts.

Prototype and interfaces
03

Build and test together

Clickable builds per module; front end, back end and data tested as one.

Build and test together
04

Handover and trial

Deployment and usage docs, then a trial period before closing the project.

Handover and trial

Three ways to build it

Templates, custom work and SaaS all get the job done; control and follow-up cost differ.

Feature
Template Fastest first release By scope
Recommended Custom build Fits your process By milestone
SaaS Ready out of the box Annual fee
First cost Low, per package Mid to high, by scope Low, annual fee
Control Capped by the template Code and data stay yours Capped by the vendor
Extending Plugins or theme edits Iterate freely, integrate APIs Depends on the vendor API
Timeline Days to two weeks Weeks to months by scope Live the same day
Best for Showcase, tight budget Unusual process, iteration Standard work, no hosting

No public price list: quotes split by scope and milestone. Each stage is priced and accepted before the next; scope changes go through a change note.

Before you start

Five things to accept first

Custom work fits because it is specific, and the cost is the talking and the acceptance. These are the real constraints we work under.

  • Blurrier scope, looser schedule: define what you will not build
  • Layout changes are cheap in prototype, costly after interfaces ship
  • Payment, SMS and maps need review time; schedule the wait
  • Trial run and docs take about a fifth of the total build
  • Migrating an old system is harder; data cleanup is the surprise
Send the scope

Tell us what to build

What the system does, who uses it, which process it replaces and which third parties it integrates. We will come back with a scope list and a milestone plan.

  • The more concrete the scope, the closer the quote. For a rebuild, include data volume, fields and the historical process: data cleanup is the usual underestimate.
CAPTCHA image