Context
Urban Indian parents facing a recurring evening decision — what advice to trust tonight — were drowning in fragmented feeds and app theatre. Existing content failed because it optimised for volume, not a clear job.
Founder & Ventures
Growing With Kid

Context
Urban Indian parents facing a recurring evening decision — what advice to trust tonight — were drowning in fragmented feeds and app theatre. Existing content failed because it optimised for volume, not a clear job.
Build story
Audience
Primary: Indian parents (especially early-childhood years) who want depth over noise when making a daily parenting call.
Design objective
Help parents think clearly in one recurring moment — not collect more content. Ship newsletter and community before software surface area.
Three decisions
Define one job: clearer thinking for a recurring decision, not a feature catalogue of “parenting tools.”
Lead with newsletter and community hub — essays, guides, conversations — after software-first experiments felt like theatre without trust.
Keep the product small on purpose: one voice, one audience, one promise, so trust can compound; failed assumption was that more modules would equal more retention.
Frames

Outcome
business
Growing With Kid remains a working space for parents who want depth over noise.
operational
Fewer features forced sharper jobs — community and newsletter before software sprawl.
Have a similar challenge?