What problem are we solving?
The current process, the people using it and the outcome that makes the work worthwhile.
Every project starts with the job you need to get done. You receive the build, cost, responsibilities and intended timeline in writing before you commit.
We look at the current process, the people using it and where they get stuck.
You get the scope, cost, responsibilities and intended timeline in writing.
You see the build and test the important journeys before anything is published.
We check the public journey and agree support, monitoring and who handles exceptions.
The current process, the people using it and the outcome that makes the work worthwhile.
Agreed deliverables, supported connections, what you need to provide and what is outside the scope.
Hosting, monitoring, support, supplier subscriptions and ownership of day-to-day decisions.
50% up front and 50% on completion.
A six-month minimum, then rolling with 30 days’ notice.
A 30-day warranty from go-live.
Your own materials remain yours. Once paid for, the agreed build is supplied under a perpetual licence. Reusable underlying tools have separate terms.
The quote identifies applicable subscriptions, AI usage, messaging, payment fees, total payable and tax treatment.
The date depends on the agreed build, content, access and any integrations. Changes to scope are agreed before additional work.
Read the full terms alongside your written agreement.
Show me what happens now, where the work gets stuck and the software you already use. An anonymised example is often more useful than a long specification.
You can start with the free six-question roadmap, or simply describe the issue in an enquiry.
Tell me what happens now and what you want to improve. You do not need a technical brief.