The house is finally quiet. Dishes done, bedtime stories wrapped, and there it is—the little 90-minute window that either disappears into scrolling or turns into something you can ship. I’ve lived both nights. The difference wasn’t motivation. It was boundaries. A tiny MVP that fits into the cracks of real life, one small promise at a time, shipped over seven evenings.
Why 90 minutes can be enough
Short windows force clarity. You won’t build everything, and that’s great. You’ll build the next step that proves the thing matters. The surprising part is how much momentum shows up when the rules are simple and kind to your schedule.
- Small scope means low stress, which means you actually show up tomorrow.
- One clear user promise keeps decisions easy: does this help the promise or is it extra?
- A fixed timebox keeps you out of rabbit holes and in shipping mode.
If it doesn’t ship in 90 minutes, it’s too big.
The 7-day experiment schedule
Here’s the arc you can run this week. Each night has one job, one deliverable, and an easy stop signal.
- Day 1: Pick the narrow promise and name the one metric.
- Day 2: Set up the website skeleton in Jaopaya and a landing page.
- Day 3: Add a basic value path (demo, free tool, or concierge flow).
- Day 4: Collect signals (email form, simple checkout, or booking link).
- Day 5: Talk to five people and invite them to try it.
- Day 6: Watch what breaks, fix only what blocks the promise.
- Day 7: Measure, decide next bet, and write tomorrow’s 90-minute plan.
Day 1: Make one promise
Think of one person you can help this week. Not a market—an actual person. Write a single-line promise like: I’ll help freelance designers get two qualified leads without buying ads. Choose one metric you’ll count by next Sunday, such as email signups, completed demos, or preorders.
- Audience: one sentence.
- Promise: one sentence.
- Metric: one number you can check in under 10 seconds.
Day 2: Stand up the site in Jaopaya
Open Jaopaya and start with the simplest starter. You’re not building an empire; you’re opening a door. One home page, one promise, one call to action.
- Home page with headline, short paragraph, and one button.
- Lightweight brand: pick a color and a readable font and move on.
- Analytics toggle on; no fancy dashboards tonight.
Day 3: Create the smallest path to value
Give them something real in one click. If your idea is a service, offer a concierge signup where you personally deliver the result for the first five users. If it’s a tool, ship a tiny version that solves one slice of the problem. Keep it scrappy and manual; automation comes later.
- One helpful action: upload, calculate, or schedule.
- One outcome: a short report, a result screen, or a booked slot.
- One follow-up email triggered when they finish.
Day 4: Capture signals that matter
Collect only the signal that proves your promise: an email, a payment intent, a booking, or a simple thumbs-up survey. Remove every field you don’t need—friction costs you learning.
- Email form with clear privacy note.
- Optional: simple checkout or reservation using a low-fee option.
- Tiny success page that explains the next step.
Day 5: Invite five people
Reach out directly. Friends, colleagues, communities—whoever fits the promise. Keep it honest and brief, and ask for permission to follow up. You’re not launching to the world; you’re learning from a handful of real attempts.
- Send five messages that reference their context.
- Offer to stay live on chat while they try it.
- Write down the exact words they use to describe the problem.
Day 6: Fix only what blocks the promise
Watch one person use it, then patch the biggest blocker and stop. Don’t polish the footer while the form still confuses people. Twenty minutes of the right fix beats two hours of perfecting the wrong thing.
- Prioritize: does this change increase completed promises?
- Cut scope before you add features.
- Ship a tiny improvement and retest with one person.
Day 7: Count and choose
Open your metric, say the number out loud, and decide: continue, pivot, or park. Write a one-paragraph log of what you learned and the next 90-minute task. You now have momentum and notes that future-you will actually understand.
- Keep going if the signal improved or conversations deepened.
- Pivot if people light up about a different slice.
- Park it if the week stayed quiet and your gut agrees.
Keeping costs down with the Jaopaya Framework
When time and budget are tight, the tools should disappear. Jaopaya helps by bundling the basics so you don’t juggle ten subscriptions. You get a simple way to ship pages, collect signals, and iterate without spinning up heavy infrastructure.
What Jaopaya gives you out of the box
- Starter templates for pages and components so you can write content, not boilerplate.
- Built-in routing and forms that post to lightweight endpoints.
- Static-first output with optional serverless actions for the one or two dynamic needs.
- Easy deploy adapters to common free-tier hosts.
- Zero-setup local dev so your 90 minutes aren’t spent configuring.
A bare-minimum stack to ship
- Jaopaya Framework for the site.
- Git hosting for versioning and one-click deploys.
- Free-tier static hosting to keep costs close to zero.
- Serverless function for form handling or a simple JSON store.
- Email notifications through a basic SMTP or provider’s free plan.
That’s enough to run your whole 7-day experiment without buying anything new. If traction shows up, you can layer on payments, auth, or a database later.
What to build: a thin slice
Think slice, not layer. Instead of building a full backend then a full frontend, build end-to-end for one tiny outcome. For example, a single-page lead magnet that turns a spreadsheet upload into a clean PDF report, delivered by email. It proves value, it’s demoable, and it’s cheap to run.
- One user path from entry to result.
- One metric that changes when the result lands.
- One message that invites a real conversation afterward.
Staying unstuck in 15 minutes or less
- Rename the feature to something smaller and ship that.
- Swap a custom build for a manual step you can automate later.
- Delete any UI element you can’t explain in one sentence.
- Ask one person to try it while you watch silently.
- Write tomorrow’s 90-minute task before you close the laptop.
After the seven days
It’s Sunday night and you’ve shipped something real. Maybe five people tried it, maybe one. Either way, you have data, stories, and a site you can iterate on. The next week is just another lap with a sharper promise and an easier build. Keep it light. Keep it friendly to your real life. Let Jaopaya handle the plumbing while you focus on the promise you’re making to one person who needs it tonight.
