Case study 02 / 06
All workBRIMMHQ
Designing maternal-support operations around trust and continuity
A human-led maternal-support venture organising participant check-ins, expert access, escalation thinking and follow-up between appointments.
- Role
- Co-founder · Operations & Venture
- Period
- 2026–Present
- Public link
- Visit BRIMMHQ ↗
The operating problem
Pregnancy and postpartum needs do not disappear between appointments. The operating problem was to create support that could notice a need, respond at the right level, escalate when necessary and record whether the loop actually closed.
BRIMMHQ is an early-stage maternal-support platform for pregnancy and postpartum. It is being built deliberately through small pilots—not presented as a mature, scaled healthtech company.
Evidence, with attribution
What the proof
actually represents.
Company context establishes the environment. Pilot, project and commercial records establish the contribution. They are not interchangeable.
registrations recorded for Pilot 1
Internal pilot reportexpert-session attendees recorded during the pilot
Internal pilot reportaverage support score reported for Pilot 1
Internal pilot reporturgent red flags documented during the pilot
Internal pilot reportWhat I owned
From ambiguity
to an operating path.
The work is shown as decisions and systems—not a list of software tools or an inflated job description.
- 01
Defined the support loop
Turned a broad idea about maternal support into a working Need → Response → Escalation → Closure model.
- 02
Ran the operating layer
Built WhatsApp-led prompts, private check-ins, expert sessions, question capture and escalation routing for the first pilot.
- 03
Made learning visible
Created an evidence chain and learning report that separated participant signals, responses, escalations and known outcomes.
- 04
Used gaps as decisions
Converted weak closure documentation and untested willingness-to-pay into explicit design questions for the next iteration.
The evidence chain
Need → Response → Escalation → Outcome
Every step has to be observable. The absence of a recorded outcome is treated as a gap in the system—not quietly upgraded into success.
Evidence bank
Pilot operating record
Session records, participant feedback and a consent-safe learning report provide the strongest current evidence.
Public product footprint
The live BRIMMHQ site describes stage-based guidance, continuity of support and an expert-backed model.
What changed
The idea became an observable service flow spanning recruitment, verification, consent, segmentation, check-ins, education, escalation and follow-up.
What I learned
Pilot 1 suggested that structured support was valued. It did not prove clinical outcomes, willingness to pay, repeatable escalation closure, unit economics or scale. Those limits are part of the work, not footnotes to hide.