Skip to main content

Start with a working model that fits the problem.

A defined delivery, ongoing engineering or focused technical advice. We agree the scope and responsibilities before the work begins.

Book a Free Consultation

No pressure, no hard sell.

Bring your current stage, constraints and intended outcome. We will recommend a useful starting model.

Three ways to work together

The model follows the work. We can discuss a different scope when your priorities change.

Fixed-scope project

Best for: A defined workflow, release or migration stage with clear acceptance criteria.
What is included
  • Discovery around the agreed problem and deliverable
  • Implementation and relevant acceptance checks
  • Working reviews and documented scope decisions
  • Source code, setup notes and the agreed handover
How it runs
We define the boundary, dependencies and acceptance examples before implementation. Reviews use working increments. If a requirement changes, we discuss its effect on the scope and release plan before accepting the change.
Typical timeline
A defined start, agreed milestones and a delivery review. Timing follows the size of the release and dependencies such as provider access or data preparation.
Request a scoping call

Dedicated monthly engineering

Best for: An existing product or system with an evolving backlog and continued engineering needs.
What is included
  • Priorities agreed against the current backlog
  • Development, integration and maintenance within the agreed scope
  • Working reviews and written progress updates
  • Decision notes and documentation as the system changes
How it runs
We agree the working arrangement and operating expectations, then choose the next priorities together. New findings can shape the backlog without hiding what changed. The scope covers agreed engineering work; support and incident-response responsibilities are stated separately.
Typical timeline
An ongoing arrangement reviewed as priorities evolve. Each working period has a clear set of priorities and review points; major releases still need their own scope and readiness decisions.
Request a scoping call

Hourly technical consulting

Best for: A focused technical question, code review or architecture decision before a larger commitment.
What is included
  • An agreed question and review boundary
  • Inspection of the relevant evidence available to you
  • A discussion of options, constraints and uncertainty
  • Findings or a decision note you can act on
How it runs
We agree the question, access and expected output first. The review follows the evidence needed for that decision. Findings distinguish observed issues from assumptions. Implementation is included only if explicitly part of the consulting scope.
Typical timeline
A focused review or a series of agreed sessions. Timing depends on the question, evidence and access needed; follow-up work is scoped after the findings are reviewed.
Request a scoping call
Request a scoping call for the model closest to your needs; we will review the fit together.

Clear expectations, whichever model you choose

Founder stays hands-on

You work directly with the engineer involved in the technical choices and implementation. Questions about the work have a clear person to go to.

Weekly written updates

You know what is ready, what needs a decision and what is planned next. Working reviews provide context for the written update.

Client owns source code and docs at delivery

The delivery includes the agreed source and documentation. Third-party products and services retain their own terms, which we identify during scoping.

We will record delivery, review and support responsibilities in the engagement scope.

What we need to scope the work

The problem
Describe what happens today, who it affects and the change you want to make. An example of current work is more useful than a long feature list alone.
The starting point
Share the existing application, relevant provider interfaces and the access constraints you know. We identify what evidence or preparation is still needed.
Timing
Typical project timeline: 6 to 14 weeks depending on scope. A consulting review or an ongoing monthly arrangement is planned around its own scope.
After delivery
Support: available after launch. We agree the scope and operating responsibilities; ongoing coverage is discussed explicitly.
We will use your answers to propose a scope, dependencies and the first review point.

Questions before we start

Do we need a finished specification?

No. Bring the problem, current workflow and constraints you know. We can turn that context into a scoped brief and acceptance examples. Decisions about priorities and business rules still need your input, and we will make those questions visible before building around them.

Can the model change later?

Yes. A fixed release can lead into a monthly arrangement, and a consulting review can define a separate build. We discuss the new scope and responsibilities before changing the arrangement. The handover and backlog provide context for that decision.

How do we handle new requirements?

We review their effect on the agreed priorities, dependencies and release boundary before implementation. A fixed-scope change needs an explicit scope decision. An ongoing backlog can be reprioritized together, with the change and its consequences recorded in the plan.

Include your other questions in the enquiry so we can review them during scoping.

A useful next step

Our process

See how decisions and working reviews fit the delivery.

Explore

Services

Explore a practical scope for your engineering problem.

Explore
Choose a relevant page, or bring the question to a conversation.

Tell us what needs to work better.

Share the problem and your current stage. We will talk through the fit and a practical starting point.

Book a Free Consultation

No pressure, no hard sell.