Skip to content
from our cohort 3

petminder

Care schedules and reminders for pet parents.

live

built using

builders behind petminder

core problem they tried solving

Pet care runs on several repeating schedules: feeding, grooming, medication, and vet visits. Pet parents need one place to organise those routines and keep recurring care visible.

the build story

Petminder started with the ordinary work that makes pet care hard to hold in your head: meals, grooming, medicine and vet visits all run on different clocks. Apurva and Nandita turned that loose problem into user flows, requirements and a feature backlog before the team tried to make it feel like one product.

The useful win was not a clever demo. They got to a working MVP, tested it, refined it and left both the product domain and its fallback deployment running. The result gives recurring care a single home instead of asking a pet parent to remember one more thing unaided.

The failure is in what the record cannot show us. There is no preserved builder retrospective that says which assumption users rejected, what was cut, or whether reminders changed anyone's routine. Shipping the MVP is real; claiming a user outcome from that missing evidence would not be.

artifacts

  1. Design file — figma (opens in a new tab)
visit petminder (opens in a new tab)