Confirmed Carers
Care marketplace: service journeys, privacy gates and a move from Replit to production
A care-matching service where families find verified carers, taken from a Replit prototype to production.
- Year
- 2024 – present
- Client
- Confirmed Carers, a UK care-matching service
The live site. Families describe the support they need, verified carers apply, and contact details stay private until the family chooses who to message.
- API endpoints
- ~300
- Vitest test files
- 157
- database migrations shipped by CI
- 58
- carer verification, including DBS and CQC
- 4-stage
Overview
Confirmed Carers matches families and councils with verified self-employed carers and care agencies. I designed the research and the service journey, then took the client's Replit-built app to production: verification, subscriptions, messaging, and an admin team that can step in when needed.
Research & service design
Designed the research instruments: an interview guide and separate surveys for people seeking care and people providing it.
Mapped the full service journey, from a family posting a request through carer applications, acceptance or decline, notifications and admin intervention.
Replaced a single long form with a staged request journey that asks sensitive questions one step at a time, with privacy gates so contact details are only shared when the family chooses.
Iterated the service using conversion analytics and an SMS consent and delivery rollout, and wrote the UI conventions documentation the team now builds against.
What I built
Moved the app off Replit to Vercel serverless and Neon Postgres, with an Express API and scheduled jobs.
Put the database under version control: 58 Drizzle migrations pushed to staging and production by GitHub Actions.
Built four-stage carer verification, including DBS and CQC checks, so families only see verified carers.
Added Stripe subscriptions with a customer portal and billing reconciliation, real-time chat and scheduling.
Used OpenAI to moderate job posts, and Brevo for email and SMS with consent handling.
Inside the work
Outcomes
Families describe the support they need, verified carers apply, and contact details stay private until the family chooses who to message.
Around 300 API endpoints and 157 Vitest test files now run on a stack the client can maintain, with CI to staging and live.
Privacy and role-based visibility were treated as product requirements, not afterthoughts.
Sensitive service design, journey mapping, privacy-aware product decisions, and rescuing a prototype into production with tests, CI and payments.