Covered Doula Care MVP
A real web home for the covered-benefit doula questions people keep asking in private.
This should feel like a field guide and professional reading room, not a feed clone. The point is to make Carrot, Maven, reimbursement, listing, and provider-friction questions easier to find, easier to trust, and easier to use than they are inside a buried thread.
The first version should organize the conversation, not reproduce the platform it came from.
This page is the public-facing shape for the idea: fewer mechanics, more structure, and enough clarity that someone immediately understands what this is for. Discussion can come later. The homepage should first show that the knowledge itself is worth returning to.
No giant member wall, no obvious discussion-board chrome, and no homepage that looks like a copied feed.
The value here is the shared operating knowledge around covered-benefit doula work, not just a sales wedge.
When someone needs cleanup instead of more reading, the quiet escalation path is still Carrot-Ready.
Three topic lanes are enough to launch the idea cleanly.
Questions about the Carrot doula directory, Carrot-approved doulas, provider eligibility, certifications, and what actually blocks listing progress.
Questions about invoices, packages, covered-benefit language, reimbursement friction, and what clients or platforms seem to need in practice.
Questions about independent vs agency work, naming on invoices, provider overlap, and the edge cases that keep showing up in real conversations.
Use stable case pages instead of letting the best questions disappear in comments.
This is the kind of question that should become a findable page with context, patterns, and a working answer set, not vanish three weeks later.
Questions like this are exactly why the product should feel like a field guide and not just a member lounge.
Content first. Discussion second. Heavy mechanics later.
Short pages built around one operating question at a time.
Plain-English references for terms, rules, and recurring platform-specific friction.
Questions and commentary should reinforce the library, not replace it.
That is enough for the MVP. Profiles, favorites, deeper member mechanics, and broader community plumbing can wait until the structure proves itself.
Need direct help?