The 90‑Minute MVP: A 7‑Day Sprint for People With Real Lives (ft. Jaopaya)

The 90‑Minute MVP: A 7‑Day Sprint for People With Real Lives (ft. Jaopaya)

You can build this after dinner

I used to think side projects needed a long weekend, a perfect playlist, and a clean desk. Then real life showed up—kids asking for water, dogs that must go outside right now, laundry that seems to clone itself. The trick wasn’t finding more time; it was learning to move with the time I actually had. Ninety minutes. After dinner. Dishes drying in the rack. Laptop open. Lights low. Small, specific moves.

If that sounds like your life too, here’s a way to build a tiny, useful MVP in one week without wrecking your sleep or your budget. We’ll keep the scope narrow, the experiments quick, and the tech cheap by building the website with the Jaopaya Framework so you’re not juggling servers and bills before your idea breathes.

Your 90‑minute window

  • 15 minutes: Plan tonight’s one deliverable (singular).
  • 60 minutes: Focus build or outreach, phones face-down, a timer running.
  • 15 minutes: Log what happened, capture blockers, prep tomorrow’s first click.

That last part matters. Ending with a “first click” (like a link you’ll open or a command you’ll run) makes tomorrow’s start frictionless.

What you’re actually building

A simple promise on a simple page. One path for a stranger to learn what you offer and take one step. That step could be: join a waitlist, pre‑order, book a call, or try a tiny demo. No dashboards. No user accounts (yet). No perfect brand kit. A clear landing page, a way to collect a signal, and just enough follow‑up to learn.

The 7‑day experiment schedule

  1. Day 1 (Define): Write one-sentence promise, one audience, and one success metric. Pick a tiny offer (e.g., “Get your freelance proposal reviewed in 24 hours for $15” or “Three 10‑minute meal plans for busy parents, free”). Decide the signal you want this week (10 email signups? 3 pre‑orders?).
  2. Day 2 (Set Up): Create your project with the Jaopaya Framework. Choose the landing page starter, connect a free-tier database for leads or pre‑orders, and set your domain or subdomain. Get a skeleton live—even if it’s ugly.
  3. Day 3 (Message): Write the landing page: headline, sub‑headline, three bullets, one CTA. Add a short FAQ to handle the top two objections. Publish. Share the link with one friend for a gut-check.
  4. Day 4 (Collect): Wire the form to store leads or payments. Send an instant confirmation email and a human follow‑up within 24 hours. Add lightweight analytics to track visits and conversions.
  5. Day 5 (Reach): Post once where your people already hang out. DM 10 humans you actually know with a short, honest message. Ask for a yes/no: “Is this useful to you this week?”
  6. Day 6 (Learn): Talk to 3 interested people for 10–15 minutes each. Ask what “done” looks like for them. If someone tries to pay you, let them. If no one does, note the exact words they used instead of guessing.
  7. Day 7 (Decide): Review the week. Keep, change, or kill. If the signal is good, lock week 2’s goal. If not, pivot the promise and repeat the 7‑day loop.
When life is full, progress belongs to the smallest repeatable unit. Build that unit.

Keep it light on purpose

  • One page, one CTA, one metric.
  • Done beats better. Better comes later.
  • No notifications during the 60‑minute block.
  • Ship something visible every day, even if tiny.

Why Jaopaya keeps costs tiny

  • Opinionated starter kits so you skip boilerplate and long setup nights.
  • Static-first pages with serverless bits for forms and payments—free‑tier friendly.
  • Built‑in auth and simple data helpers if you need them later, but you don’t have to start there.
  • One‑command deploys to common hosts; no babysitting servers.

Step‑by‑step with Jaopaya (fast track)

  1. Install the Jaopaya CLI and run the landing page starter.
  2. Choose the Landing + Form preset; accept defaults to start.
  3. Connect a free-tier datastore for leads or a payment link for pre‑orders.
  4. Set environment variables for email and data in the project settings.
  5. Push to Git and deploy with one command; verify your live URL.
  6. Map a domain or subdomain; turn on basic analytics.
  7. Create an automated confirmation email and a short human follow‑up template.

A tiny scope that actually ships

  • One landing page: headline, sub‑headline, three benefit bullets, one CTA button.
  • One form: name + email (and one optional qualifier question).
  • One thank‑you page with next steps and a calendar link if calls matter.
  • One data table: leads or pre‑orders.
  • One follow‑up email sent within minutes, one personal reply sent within 24 hours.

Signals that fit into family life

  • 10 genuine conversations started (DMs or replies) this week.
  • At least 30 visitors and a 10%+ signup rate for a free offer, or 3%+ for a paid test.
  • Three short calls with target users using their words, not your pitch.

If you miss a day

Don’t pay the shame tax. Double the clarity, not the hours. Re‑enter with a smaller deliverable: “Publish the FAQ,” “Add the calendar link,” “Send three DMs.” Momentum loves specificity.

What happens after 7 days

If you hit the signal, week 2 upgrades the same small loop: a clearer headline, a better FAQ, a sharper CTA, or a tiny payment test. If you didn’t hit it, keep the discipline but change the promise. The habit—the 90‑minute window, the single deliverable, the weekly decision—turns the chaos of a full life into a drumbeat.

It’s amazing how far you can get when the work fits between bedtime stories and the dishwasher beep. Tiny ship, steady course.

You might also like