Board/home-cuts
LocalConsumerrotting
Directory of in-home hairdressers by city
Not another tool directory. A map of people who will cut hair in your kitchen. Filter by fade, curly, kids, color, price, and next available Saturday.
For Parents, people with mobility limits, anyone tired of salons
Riff on @T_Zahil niched idea list
The problem, sharper
Parents, people with mobility limits, anyone tired of salons already tried the generic version and bounced. Not another tool directory. A map of people who will cut hair in your kitchen. Filter by fade, curly, kids, color, price, and next available Saturday. The wedge is the constraint, not another feature list.
Features that make the pitch true
- 01Capture the job in one screen: Not another tool directory. A map of people who will cut hair in your kitchen. Filter by…
- 02Audience-aware defaults for parents, people with mobility limits, anyone tired of salons.
- 03Shareable artifact you can send to a teammate in one tap.
- 04Honest empty states. No fake social proof, no infinite onboarding.
- 05Export: the user can leave with their data on day one.
This weekend
- Friday: landing page, one happy path, seed data.
- Saturday: the core loop that makes the pitch true.
- Sunday: share link, ugly-but-working export, tell ten people.
Stack
- — Next.js + TypeScript
- — Local-first persistence, server later
- — city search
- — availability calendar
- — SMS confirmations
- — onboarding in under 60s
User stories
- As a person in this group: Parents, people with mobility limits, anyone tired of salons, I can describe the job in one sentence and get a usable first result.
- As a skeptic, I can try it without creating an account.
- As someone who might build this, I can copy a spec and start this weekend.
Paste into Cursor, Claude Code, or Codex
Build a working product called NudgeNote. Tagline: Directory of in-home hairdressers by city — without the usual product theater. One-liner: Not another tool directory. A map of people who will cut hair in your kitchen. Filter by fade, curly, kids, color, price, and next available Saturday. Who it is for: Parents, people with mobility limits, anyone tired of salons Non-goals: do not build a generic local app. Do not add auth until the core loop works. Do not invent extra personas. Must-have features: 1. Capture the job in one screen: Not another tool directory. A map of people who will cut hair in your kitchen. Filter by… 2. Audience-aware defaults for parents, people with mobility limits, anyone tired of salons. 3. Shareable artifact you can send to a teammate in one tap. 4. Honest empty states. No fake social proof, no infinite onboarding. 5. Export: the user can leave with their data on day one. Suggested stack: - Next.js + TypeScript - Local-first persistence, server later - city search - availability calendar - SMS confirmations - onboarding in under 60s UX: - Distinctive, editorial, not purple-gradient SaaS - Works on a phone - Empty states teach the product - One primary action per screen Ship this weekend: 1. A landing page that states the job in one breath 2. The core loop end to end with sample data 3. A shareable output 4. A README that explains what was intentionally left out Constraints: TypeScript. Keep the first version local-first if a database would slow you down. Name the product NudgeNote unless you have a clearly better one.