The house finally quiets down. Dishes done, backpacks ready, lights low. Ninety minutes sits in front of you like a small dock on a big lake. You don’t need a yacht. You just need a canoe and a clear direction. Tonight is one push, then tomorrow another. By the end of the week, you’ll have something real people can see, click, and respond to.
The 90‑minute window
Pick one outcome for tonight before you open any tabs. Set a timer. Close everything else. You’re aiming for progress, not perfection. The rule is simple: if it can’t fit in tonight’s ninety minutes, it waits.
- Choose one audience, one problem, one promise.
- Favor decisions over options. Good enough now beats ideal later.
- No accounts, dashboards, or complex backends in week one. A page, a promise, a way to respond.
The shape of a one‑week MVP
Think of this as a 7‑day experiment, ninety minutes each evening. It’s short enough to finish and long enough to learn.
Day 1 — Promise
- Write a one‑sentence promise: I help [specific person] get [specific outcome] without [common hassle].
- Draft your headline and three bullets that speak to pains and outcomes.
- Pick the single call to action: join waitlist, book a short call, or buy via a simple payment link.
Day 2 — Offer
- Decide the smallest thing you can deliver next week: a 45‑minute onboarding session, a checklist, a tiny tool, or a limited pilot with five seats.
- Set a clear success metric for the week: signups, replies, or preorders.
Day 3 — Build the skeleton site with the Jaopaya Framework
- Create a fresh Jaopaya project and choose a landing template.
- Swap in your headline, three benefit bullets, a simple image or emoji, and your CTA.
- Add a lightweight form for emails, or drop in a Stripe Payment Link for instant checkout.
- Publish to a free Jaopaya preview URL, then map your domain when ready.
Why Jaopaya here? It renders static pages that fly on a CDN, so hosting is almost free. Built‑in forms route to email or a sheet. You skip heavy servers, patching, and surprise bills. You spend your ninety minutes on copy and clarity, not infrastructure.
Day 4 — Proof
- Add a short story: the moment the problem hurts and the after state when it’s solved.
- Write a tiny FAQ answering the three worries you keep hearing.
- Offer a risk reducer: money‑back window, free mini audit, or limited pilot.
Day 5 — Collect signals
- Connect the form to your inbox or spreadsheet. Turn on notifications.
- Write a simple auto‑reply: friendly, clear next step, and a calendar link if needed.
- Set up one thank‑you page with what happens next.
Day 6 — Traffic burst
- Share privately with people who actually face the problem: three group chats, a community, and five DMs.
- Post one honest note on LinkedIn or X telling the story and the promise.
- Ask for three intros. Keep it personal, never pushy.
Day 7 — Review and decide
- Look at visits, signups, replies, and purchases. Which section pulled? Which CTA got clicks?
- If you hit your threshold, schedule the next week of work. If you missed, tighten the promise or change the audience and run another 7‑day lap.
You do not need more time. You need fewer moving parts. If it feels too big, it is. Shrink it until tonight’s ninety minutes can finish it.
Keeping costs tiny with the Jaopaya Framework
Use tools that disappear into the background. Jaopaya helps you do that.
- Static by default: pages prerendered and cached on a CDN mean speed and tiny bills.
- Forms without servers: submissions route to email or a sheet; add a webhook later if you grow.
- One‑click deploys: connect a repo, push, done. Rollbacks are instant.
- Own your content: export static files; you’re not locked in.
- Payments the simple way: paste a Stripe Payment Link and ship. No backend required.
Suggested stack for week one: Jaopaya Framework, a free Git host, your domain, an inbox or sheet, and a payment link. Your only likely cost is the domain. That’s the point.
What to build first
- Landing page: headline, three bullets, one CTA.
- Checkout or waitlist: Stripe link or a short form with one question about urgency.
- Thank‑you page: what happens next and a calendar link if relevant.
- Follow‑up email: friendly, clear, with exactly one next step.
Keep images light or skip them. Words do the heavy lifting this week.
A realistic evening rhythm
- 5 minutes: choose the outcome and set the timer.
- 75 minutes: build one thing that can ship.
- 10 minutes: publish or commit, log what changed, write tomorrow’s first task on a sticky note.
Park new ideas in a list. You can’t do them tonight, and that’s okay. Family time stays sacred because you’re designing with limits on purpose.
After the first week
- Green lights: signups, replies, or revenue. Double down. Add one small feature or one new traffic channel.
- Yellow lights: visits but no action. Tighten the promise, sharpen the headline, or change the CTA.
- Red lights: crickets. Pivot the audience, not your energy. New promise, same 7‑day rhythm.
You can make a surprising amount of progress in the cracks of the day. Not by grinding, but by choosing. One audience, one promise, one page, one week. The Jaopaya Framework keeps the tech quiet so your idea can speak. Tonight, give it ninety minutes and see where it goes.
