Estimates built from the real shape of the project.

We work project by project. Each estimate is based on an hourly rate, the expected development hours, and the scope needed to get the work across the line cleanly.

Standard rate

£125

per hour

Use this as the planning baseline. Discovery may adjust the hours, but the logic stays the same.

Estimate formula: hourly rate × expected hours = project estimate

Estimates

Clear estimates, not package theater.

We scope against actual effort and keep the plan flexible as the work becomes clearer.

Current estimate

App development

Adjust the inputs below to match the likely build.

Estimate

£10,000

Typical range

60 - 120 hrs

Range value

£7,500 - £15,000

Final scope, third-party costs, and timeline risk are reviewed before work begins.

01

Discovery

Clarify the goal, audience, and constraints before any estimate is locked in.

02

Scoping

Break the work into screens, integrations, and acceptance criteria.

03

Build

Design, implement, review, and iterate with regular demos.

04

Launch

Deploy, monitor, and stay close through the stabilisation window.

Start a project

Typical project shapes

These ranges are useful for planning, even before discovery begins.

Landing site

25 - 40 hrs

Marketing sites, campaign pages, and redesigns.

Internal tool

60 - 120 hrs

Ops dashboards, workflow apps, and admin panels.

MVP app

120 - 250 hrs

Customer-facing products with auth, data, and integrations.

Ongoing support

20 hrs / month

Bug fixes, monitoring, and iterative improvements.

Pricing FAQs

The estimate process stays simple: define the work, apply the rate, and agree the scope before development starts.

What does the hourly rate include?

The rate covers strategy, design, build, QA, deployment, and the day-to-day delivery overhead needed to keep a project moving.

Why use hours instead of fixed packages?

Hours let the estimate reflect the real shape of the project. That gives you a clearer picture when scope changes or the work turns out to be more involved than expected.

Can we start with a smaller scope?

Yes. We often start with a narrower slice, then extend once the first release is live and the next priorities are clear.