Estimate

What will it cost? Find out in three minutes.

Pick a service, answer a few questions and see an indicative range with timeline and team. No call needed.

  • A range you can plan with
  • Your answers stay with us
  • A person replies within one working day

Build your estimate.

Five short steps. Your range opens at the end, with what drives it.

Step 1 of 5Service

Which service do you need?

Pick the closest fit. You can change it later without losing the rest.

Service

Your range opens at the end

What's included

Every estimate covers the whole job.

Six phases, priced together. If one doesn't apply to you, we take it out in the call.

01

Discovery and scope

A workshop with the people who own the process, then a written scope you sign off before we build.

Discovery and scope

A written scope, signed off before the build.

A workshop lead presenting the scope at a whiteboard
02

Design

Flows, screens and data models agreed up front, so nothing surprises you in week six.

Design

Flows, screens and data models agreed up front.

Design phase on a large display: the user flow for placing an order as four screen designs, with a sketch of the PostgreSQL data model beside it.
03

Engineering

The build itself, released weekly to a staging environment you can click through.

Integrations the estimate covers

Engineering

Weekly releases to a staging environment.

Engineering phase: this week's staging release of an order portal open in the browser, with its changelog of Jira tickets beside it.
04

Testing

Automated tests, a run against realistic data and an acceptance round with your team.

Testing

Automated tests and an acceptance round with your team.

Testing phase: an automated test run with every suite passing, next to the acceptance checklist the client team signs off.
05

Deployment

Release to your infrastructure or a hosting partner, with monitoring and a rollback plan in place.

Deployment

Monitoring and a rollback plan from day one.

Deployment phase: the release pipeline green from build to production on AWS, with monitoring of the last hour and the one-step rollback in view.
06

Handover or operations

Documentation and training for your team, or we run it for you under a support agreement.

Handover or operations

Documentation and training, or we run it for you.

A team walking a client through the handover in a meeting

Industries

The problem looks different in every industry.

Pick yours. This is what we hear in the first meeting, and what we build to fix it.

Healthcare and clinics

The problem

The front desk spends the morning on reminder calls and rebookings. Patient records sit in one system, invoices in another, and nobody sees which patients have quietly stopped coming back.

What we build

Booking, reminders and recall that run on their own, with one view of every patient across every site.

Usually connects to

Estimate a project for your industry

Every patient, every site, one view.

A surgical team at work while patient recalls and bookings run in the background

Professional services

The problem

Senior people spend their evenings on time sheets, engagement letters and status reports. Knowledge lives in inboxes, so every new case starts from a blank page.

What we build

Document drafting, time capture and a searchable memory of past work, inside the tools the firm already uses.

Usually connects to

Estimate a project for your industry

The firm's memory, finally searchable.

Two advisers in a meeting while a drafted document waits for partner review

Manufacturing

The problem

Orders arrive as PDFs and emails and get typed into SAP by hand. Planning runs on a spreadsheet that one person understands.

What we build

Order intake, planning data and supplier documents connected to SAP, with exceptions sent to the right person.

Usually connects to

Estimate a project for your industry

Orders that reach SAP without a keyboard.

An engineer at a laptop in a robotics lab while an order is matched in SAP

Retail and e-commerce

The problem

Customer service answers the same twenty questions all day. Returns are processed by hand, and by Friday the shop, the stock and the books disagree.

What we build

Service, returns and stock that run on the same data, from the shop front to the books.

Usually connects to

Estimate a project for your industry

Shop, stock and books that agree on Friday.

A shop assistant smiling at the till while a return is refunded automatically

Logistics and travel

The problem

Bookings, changes and documents arrive by email at all hours. The team types them into three systems, and customers call to ask where things stand.

What we build

Booking and status workflows that read the email, update the systems and tell the customer before they ask.

Usually connects to

Estimate a project for your industry

The customer knows before they ask.

A container port at sunset while booking changes flow into the system

Finance and insurance

The problem

Applications and claims arrive as documents and get checked by hand against rules everyone knows by heart. Every audit means a week of collecting evidence.

What we build

Document intake, rule checks and an audit trail that is written while the work happens.

Usually connects to

Estimate a project for your industry

An audit trail written while the work happens.

Two colleagues reviewing a claim at a desk while the rule checks run

Software and SaaS

The problem

The roadmap is full, support tickets keep pulling engineers off it, and the internal tools are scripts nobody owns.

What we build

Support, onboarding and internal tools that run without pulling your engineers off the product.

Usually connects to

Estimate a project for your industry

Engineers back on the roadmap.

An engineering team at work while the support queue links to the roadmap

Questions, answered.

How accurate is this?

It's a first read, built from typical effort for projects of this shape. It only knows what you told it, so use it for planning and wait for the quote before you set a budget. The 30-minute call is where we find the details that move it.

Why a range?

Because a single number at this stage would be a guess dressed up as precision. The range narrows as you answer more questions, and again once we've seen your systems.

What isn't included?

Third-party licences, hosting, model and API usage fees, hardware and VAT. We list them separately in the quote, so you can see exactly what you pay to whom.

Can you work to a fixed price?

Yes, once the scope is written down and agreed. Discovery and each delivery phase can be priced as fixed packages. Staff augmentation is billed monthly.

What happens after I submit?

Your range opens on screen as soon as you send your details, and a copy goes to your inbox. We read your answers and reply with a link to book 30 minutes, usually with two or three questions that would tighten the range. Your answers are used only to reply to you.

Rather talk it through?

The estimate is a first read. A conversation is where we find the details that move the range.

From the first call to a system in production.

The people you meet in the audit are the people who build and run it.

Two colleagues smiling at a laptop after booking a call