Digital health products shaped around real care workflows — not the other way around.
Guide pricing

Clear starting points. Scope before commitment.

Prices below are planning guides for common project shapes. A written scope confirms deliverables, responsibilities, assumptions and payment stages before work starts.

0%surprise work. Changes outside the agreed scope are described and priced before they are started.
Validate the direction

Pathway Sprint

£4,800

Two focused weeks to turn a care challenge into a testable product direction.

  • Stakeholder working sessions
  • Current-state workflow map
  • Clickable patient and team flows
  • Risk and assumption register
  • Prioritised first-release scope
Choose sprint
Extend and connect

Service Platform

£38,000 from

A broader implementation spanning multiple workflows, teams or system connections.

  • Multi-role product design
  • Configurable pathway logic
  • Integration engineering
  • Operational reporting
  • Deployment and adoption support
Scope a platform
Rough planning tool

Estimate a first release.

This estimate is for early budgeting only. Integration complexity, assurance needs and content volume can materially affect scope.

Indicative build range£6,000–£8,000Indicative delivery window4–7 weeksGet a scoped proposal
Ongoing support

Keep the product healthy after launch.

Support can cover monitoring, fixes, small improvements and a regular product review.

£950/mo

Essential product care for a focused service with agreed support hours.

£1,800/mo

Care plus a monthly improvement allocation and product review.

£3,500/mo

Ongoing product team capacity for active services and a managed roadmap.

Custom

Operational coverage, assurance or integration support shaped around the service.

Commercial clarity

What is normally included.

ItemIncludedUsually separate
Design and engineeringAgreed product flows, interface design, implementation and testingNew requirements introduced after scope approval
Project managementRegular working sessions, demonstrations and delivery trackingClient-side programme management
LaunchDeployment support, basic handover and agreed documentationLarge-scale training programmes or service desk operation
Third-party servicesConfiguration of agreed services where statedExternal licences, message fees, hosting or specialist assurance
TaxPrices shown exclude VAT where applicableAny applicable tax is shown on the proposal and invoice
Pricing questions

Before a proposal.

Smaller fixed engagements are usually split across commencement and completion. Product builds are normally divided into agreed milestones, such as discovery, prototype approval, working release and launch.

Yes. A focused pathway or team is often the safest starting point. The design can still consider future roles and integrations without paying to build them immediately.

The largest factors are the number of distinct user roles, integration depth, workflow complexity, assurance requirements, content volume and the amount of migration or operational change involved.

Build care technology people can actually live with.

Start a conversation