Where this stands
Case study in progress. Target completion: 2027-04-30. The full writeup lands once the research, build, and eval phases are done.
The customer scenario
Solo or small-team learners need a deliberate-practice tracking system that produces accountability, visibility, and a public portfolio artifact over a long timeline.
My product canvas
This case study is grounded in Field Notes itself (this build) — the public tracker site you're reading. Built in 2 weekends, $0/month infrastructure, dogfooded daily for 12 months as the accountability tool for the Tapasya plan. Canonical writeup: github.com/kartparash-cmd/fieldnotes.
Architectural patterns to be demonstrated
- $0-budget product engineering trade-offs — Next.js + Supabase + Vercel free tiers; what you give up at this constraint
- Schema-first design constrained to 2 users + 7 case studies — no premature multi-tenancy; the simplest data model that admits real use
- 12 months of dogfooding observations — what metrics actually drove behavior change, what features I built and never used, what I'd cut for V2
What you'll find here when it ships
- Architecture diagram
- Eval set with results
- Cost and latency analysis
- Failure modes documented
- "What I'd do differently" retro