Process

From first call to supported product

Predictable stages, visible progress and commercial terms that match how UK clients actually buy software. No surprises, no disappearing acts between milestones.

Discover

A structured conversation — or series of them — to understand your goals, the users who will interact with the software, the constraints that matter (budget, timeline, integrations, compliance) and how success will be measured. Output is a written brief you can circulate internally before we proceed. No code is written at this stage.

Design

User flows, wireframes (low-fidelity for speed, higher-fidelity where decisions depend on layout), and a technical approach document covering architecture, data model, third-party dependencies and hosting strategy. This is signed off — in writing — before heavy engineering begins. Changes requested after sign-off are handled as documented change requests.

Build

Incremental development in two-week sprints. At the end of each sprint, working software is deployed to a staging environment and you are invited to review it. Feedback on working code is more precise than feedback on wireframes, which is why we invest in showing it early and often. You are never waiting more than two weeks to see progress.

Verify

Structured testing proportionate to risk: functional test plans covering agreed scope, regression checks when features interact, performance testing for load-sensitive paths, and a security review covering authentication, data handling and dependency vulnerabilities. Defects are triaged and resolved before sign-off. We do not hand over software we have not tested ourselves.

Launch

A go-live checklist covering deployment, DNS, SSL, backup confirmation, monitoring setup and access credential handover. User documentation and, where appropriate, recorded walkthroughs for common tasks. Training sessions for teams are included in the launch budget where scoped. A 30-day post-launch warranty on in-scope defects begins from this point.

Evolve

Optional ongoing support — retainer or ad-hoc — covering security patches, dependency updates, small configuration changes and planned feature additions. We also offer quarterly roadmap sessions to assess what to build next based on how the software is actually being used. See Technical Support for full details.

Commercial terms (typical)

Payment structure

Deposits & milestones: Typically 30% on contract signature to commence, with further payments tied to agreed deliverables (end of design, mid-build milestone, go-live acceptance). The balance is due on final sign-off. For larger projects we agree a phased schedule at the outset; nothing surprises you mid-project.

Change requests

Scope changes happen. When they do, we document the request, assess impact on time and cost, and agree the adjustment in writing before any work proceeds. We do not absorb changes silently and invoice you for them later, nor do we refuse to accommodate them. The process protects both sides.

Confidentiality

An NDA (mutual non-disclosure agreement) is available on request before you share commercially sensitive brief details. We treat all client information as confidential as a matter of practice regardless, but we understand some organisations require a signed document before the conversation starts.

Code ownership

Bespoke code written for your project transfers to you under contract on full payment. This is not conditional on ongoing relationship — you own what you paid for. Third-party libraries, open-source components and starter-product foundations remain under their respective licences, which we document in the handover pack so you understand exactly what you have received.

Fixed price vs time-and-materials

For well-scoped projects we offer a fixed-price contract, which removes financial uncertainty for you. For exploratory or evolving briefs we use time-and-materials with agreed monthly caps. We discuss which model fits your project during discovery and explain the trade-offs clearly.

Minimum project size

Our minimum engagement for a custom build is £2,500. Projects below this threshold are better served by our starter products or a consultation session, both of which we can arrange without commitment.

Common questions

How the process works in practice

It depends heavily on scope. A focused mobile utility or single-module desktop tool might reach launch in 6–10 weeks. A multi-module business platform typically runs 3–6 months for a first production release. We give a timeline estimate as part of the design sign-off, not before — anyone who quotes a delivery date before seeing a scoped brief is guessing.

Availability for sprint reviews (typically 30–60 minutes every two weeks), prompt feedback on staging releases, and a named point of contact who can make decisions about scope. Projects slow down when feedback loops stretch beyond a week — we flag this early if it happens.

We handle changes through a documented change request process. Small adjustments within the spirit of the original scope are often absorbed; larger additions or redirections are quoted and agreed before proceeding. We have never refused a sensible change — we just price and schedule it honestly.

Yes. We act as a white-label development partner for digital agencies and design studios on a case-by-case basis. The process is the same; the primary contact is the agency. Contact us to discuss referral or subcontract arrangements.

Yes — a scoped discovery session or a minimal viable first module is a common and sensible starting point. It lets both sides assess fit before a larger commitment. We can structure an engagement that begins small and expands based on what we learn together.

Ready to start?

A short email describing your situation is enough. We will suggest the right next step — discovery, a starter product, or a different approach entirely if that fits better.

Discuss your project