Duedemo: A live demo and pitch pack before the deadline

The tender closes Friday, the hackathon ends Sunday, or the client launch date is already announced, and the scope is still loose. Teams lose the last day to a first deploy that fails, then pitch from slides. Duedemo runs a fixed-date sprint from brief to a deployed demo and a pitch pack.

What it does

• Scope lock turns the brief into one checklist: a coverage scoreboard for a tender, track plus rubric for a hackathon, a sitemap for a client site. Paying clients approve scope and payment phases on one page first.
• Pivot budget set up front, for example one pivot before the end of day 1.
• Kit scaffold from a sibling project's design kit or an existing team monorepo, with the data-layer choice written down.
• Demo data from public sources or personas, invented names and a reserved ID range.
• Deploy on day 1 with a checklist (Root Directory, framework, no secrets in vercel.json) and a phone smoke test.
• Demo pack and close: deck PDF, narration script with timing cues, 60-second walkthrough video, QR card, then a next-phase quote by module or a parked resume point and a 15-minute retro.

How it works

1. Lock scope and pick the track, with clarifying questions in one round.
2. Scaffold and seed from a kit and realistic demo data.
3. Build by epic or by day, with unit and E2E tests and a production build before each checkpoint.
4. Deploy early and harden just enough: security headers, sitemap, analytics, HSTS checked on subdomains.
5. Ship the demo pack, then close with a quote or a resume point.

Frameworks & tools

Common kits: Next.js + Supabase + Vercel, or Hono + Postgres on a VPS. Deploys to Vercel, Fly.io or a VPS with Docker Compose and GHCR images. Tests with Vitest + Playwright. Decks via pandoc or Marp.

Why this beats prompting it yourself

A prompt builds features in the order you ask for them. Duedemo puts must-haves before extras, deploys on day 1 instead of the last hour, and carries guards from real sprint failures such as hardcoded event dates and QR scanners failing in in-app browsers.

Use cases

• Weekend hackathons with a 4-minute pitch.
• Tender or RFQ demos with integrations mocked.
• Client sites in about a week.
• Event platforms hardened before registration opens.

Known limitations

Not for work with no date pressure or a fix on a live product. It does not enter secrets, push production migrations or create admin accounts; you do. It commits and pushes only when you say.