Pathway Sprint
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
Prices below are planning guides for common project shapes. A written scope confirms deliverables, responsibilities, assumptions and payment stages before work starts.
Two focused weeks to turn a care challenge into a testable product direction.
A working first release for one pathway, patient group or care team.
A broader implementation spanning multiple workflows, teams or system connections.
This estimate is for early budgeting only. Integration complexity, assurance needs and content volume can materially affect scope.
Support can cover monitoring, fixes, small improvements and a regular product review.
Essential product care for a focused service with agreed support hours.
Care plus a monthly improvement allocation and product review.
Ongoing product team capacity for active services and a managed roadmap.
Operational coverage, assurance or integration support shaped around the service.
| Item | Included | Usually separate |
|---|---|---|
| Design and engineering | Agreed product flows, interface design, implementation and testing | New requirements introduced after scope approval |
| Project management | Regular working sessions, demonstrations and delivery tracking | Client-side programme management |
| Launch | Deployment support, basic handover and agreed documentation | Large-scale training programmes or service desk operation |
| Third-party services | Configuration of agreed services where stated | External licences, message fees, hosting or specialist assurance |
| Tax | Prices shown exclude VAT where applicable | Any applicable tax is shown on the proposal and invoice |
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.