Our approach to projects

Every project benefits from clarity on scope, responsibilities, and expectations. 

Our approach is designed to reduce uncertainty early, so development time is spent solving the right problems rather than reacting to surprises.

Before estimating, we aim to understand what we’re building and why. For smaller projects, a call or meeting may be enough. For larger or more involved work, this becomes a short scoping or discovery phase.

During this stage we identify:

  • the outcomes the project needs to achieve
  • technical constraints and required integrations
  • dependencies such as design, content, or third-party systems
  • areas of uncertainty or risk

This phase doesn’t need to be long, but it does need to exist. A clear definition at the start prevents delays, rework, and scope creep later on.

Once discovery is complete, we produce a written scope and a short outline of how we’ll approach the work. This includes timelines, assumptions, and the deliverables you can expect. It becomes the shared point of reference for the project, and the basis for any future changes or additions.

A key part of shaping this specification is establishing clear acceptance criteria. These criteria define how the work will be tested and what 'done' looks like, ensuring we deliver a result that matches your requirements and behaves as expected.

Taking time to define the scope of a project is important.

Without a clear scope; scope creep and miscommunication can lead to trouble. Even a simple project can become complicated if a little time isn't taken to define exactly what needs to be delivered to satisfy project goals

Development follows the agreed scope. We work in focused blocks of time (typically full-day sessions) with clear milestones for review and feedback. 

Progress is visible throughout, with regular check-ins so any adjustments can be made early, before they become costly or disruptive.

We’re flexible in how we collaborate. If you need us embedded in an agile team, working independently, or operating somewhere in between, we can adapt to match your preferred process.

Once core development is complete, we move into structured testing and review. This phase covers fixes and refinements required to meet the agreed acceptance criteria, ensuring the work behaves as expected and is ready for use.

If needed, we also support user acceptance testing, with clear points for review and sign-off. 

Any further rounds of changes beyond the agreed scope can be planned separately so the project stays predictable and well-controlled.

After launch or delivery, we can provide documentation, training, or follow-up support to help your team make the most of the work. Support can be arranged on a time-based or retainer basis, depending on what you need and how involved you’d like us to be.

The projects that succeed are the ones that begin with alignment. A small investment in discovery and definition saves far more time (and cost) during build.

This approach means you always know what’s being delivered, what it costs, and when to expect it. No guesswork, no vague promises, no last-minute surprises.