How we work

Understand each delivery stage, what to expect, and the terms agreed before work begins.

Our process

A clear process, from first
conversation to ongoing support.

  1. Discovery

    We learn about your business, current process, users, and what you want to achieve.

  2. Proposal

    We agree in writing on scope, deliverables, timeline, price, and payment milestones.

  3. Development

    We build the agreed system or improvements, with progress updates and recorded decisions.

  4. Testing

    We check agreed features and user flows, and collect your feedback against acceptance criteria.

  5. Launch

    We deploy or hand over the agreed release after testing and approval.

  6. Support

    We provide 30 days of included in-scope bug fixes after launch. Further support is paid work.

Deliverables

What you can expect.

Clear scope and proposal

A written proposal setting out deliverables, exclusions, timeline, price, and payment milestones.

Milestone-based work

Development follows the approved scope, with agreed review points and written approval for changes.

Testing and handover

Agreed user flows are tested. Deployment, documentation, access, and walkthroughs are delivered as set out in your agreement.

30-day bug-fix support

For 30 days after launch, reproducible bugs within the agreed project scope are fixed at no additional service charge.

New features, changed requirements, third-party outages, and issues caused by unauthorized changes are excluded. After 30 days, further support and bug fixes are paid services under a separate quote or support arrangement. Support hours, contact channel, and response expectations are agreed for each project.

Frequently asked questions

Common questions.

What is the payment schedule?
40% to book the project and begin work; 40% when the agreed build is ready for client testing; 20% before production handover.
How is pricing determined?
Each project is quoted after discovery. Your proposal sets out the agreed scope, deliverables, exclusions, timeline, fee, and payment milestones. Invoice due dates, payment method, and applicable taxes are set in each proposal or agreement.
How long does a project take?
The schedule depends on the agreed scope, dependencies, and client approvals. Milestones and target dates are set out in the project proposal.
What does 30-day support cover?
For 30 days after launch, reproducible bugs within the agreed project scope are fixed at no additional service charge. New features, changed requirements, third-party outages, and issues caused by unauthorized changes are excluded. After 30 days, further support and bug fixes are paid services under a separate quote or support arrangement. Support hours, contact channel, and response expectations are agreed for each project.
What should I prepare?
A short description of your current process, who uses it, where work becomes difficult, and what you want to improve. Mention any existing systems, constraints, and target timeline.
View contact information →