Standby Desk
A private shift-fill desk for restaurants, hotels and clinics that turns their existing list of past extras into one form, one blast, one accept page, and one mission sheet PDF.
One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.
Decide in 20 seconds
The facts that decide whether this is worth thirty days of yours.
Owner-manager, head chef or ops coordinator of an independent restaurant, boutique hotel or small clinic with 1-3 sites and 10-60 staff in France, the UK, Belgium or Switzerland, plus micro-agencies and freelance coordinators placing 10-100 extras per month.
Market demand 5.0/10
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 8; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.7/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
10 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner-manager, head chef or ops coordinator of an independent restaurant, boutique hotel or small clinic with 1-3 sites and 10-60 staff in France, the UK, Belgium or Switzerland, plus micro-agencies and freelance coordinators placing 10-100 extras per month.
Why now
The venue already owns the supply, so no marketplace density, verification or brand is needed to deliver value; the proof is one live shift during a screen share and the price is below the cost of a single unfilled cover.
Problem
Filling a last-minute shift means scrolling 200 WhatsApp contacts, retyping the same message into a dozen threads, losing track of who said yes, then hand-typing a mission sheet before service and reconstructing hours and pay at month end.
Solution
A 30-second shift form emits three escalating FR/EN message drafts plus a no-login accept link, a live fill board tracks replies, and acceptance generates a one-page mission sheet PDF with a confirmation code, followed by a pay recap and monthly accountant export.
1. Product opportunity and positioning
Brigad proved the demand: hospitality and healthcare venues need bodies for short missions at short notice. It also proved what serving that demand costs — a two-sided marketplace needs supply density, verification, ratings and a commission engine before a single venue gets any value. A solo founder has none of that inside 30 days.
Standby Desk keeps the customer and the pain and throws away the marketplace. The venue already owns a list of past extras in WhatsApp and phone contacts. The painful task is not finding people; it is the 40 minutes of scrolling, retyping the same message into a dozen threads, losing track of who said yes, and hand-typing a mission sheet before service — then reconstructing hours and pay at month end.
The product is a private shift-fill desk. Paste the roster once. Fill a 30-second shift form. Get three escalating message drafts in FR and EN with a unique no-login accept link. Watch a live fill board of invited, accepted, declined and silent workers. On acceptance, print a one-page mission sheet PDF with a confirmation code. After the shift, a pay recap and a monthly accountant export.
Why this is sellable inside the window: the buyer is one named person (owner-manager, head chef, ops coordinator); the trigger is a shift they must cover this week; the proof is one live shift during a screen share; and $49/month sits below the cost of a single unfilled cover. JEV scores the concept 66.3/100 in band B, strongest on speed to first revenue (8.67/10 normalized), weakest on market demand (5.0/10). That is the right shape for a 30-day profit contest — fast first cash, honest low-four-figure ceiling.
Positioning statement: for independent restaurants, boutique hotels and small clinics covering shifts with freelancers, Standby Desk is the private fill desk that runs on the staff list you already own — not a marketplace you have to populate, and not a WhatsApp group someone has to babysit.
Deliberate non-goals define the wedge: no worker marketplace, no discovery feed, no matching engine, no in-app payouts, no payroll filing, no credential verification, no native app, no POS integration. Each of those would burn weeks and add nothing to the first $49. The competitive moat is not technology; it is that the founder can onboard a venue's real roster in ten minutes and prove the saving on their own next shift.
Smallest sellable MVP
A venue pastes its extras list, fills one shift form, sends the generated drafts with an accept link, watches replies land on a fill board and downloads a mission sheet PDF — all payable at $49/month by card.
Must-have features
- Roster paste-import with role tags and last-worked date
- Shift intake form (role, date, start/end, rate, address, what to bring)
- Three escalating FR/EN message drafts with copy buttons and a unique accept token
- No-login accept page with Yes/No/Maybe and name field
- Live fill board showing invited, accepted, declined and silent workers
- Mission sheet PDF with venue branding, confirmation code and signature line
- Close-out with hour adjustment, pay recap PDF and monthly CSV export
- Stripe Checkout for $49 and $129 with 14-day trial and billing portal
Explicitly out of scope
- No worker marketplace, discovery feed or matching algorithm
- No in-app payments, escrow or worker payouts
- No payroll filing, tax calculation or right-to-work verification
- No native iOS/Android app and no worker accounts
- No background checks, ratings or credential verification
- No permanent rota planning
- No POS or booking integrations
- No automated WhatsApp or SMS sending in v1
Demo flow (what the buyer sees)
- Founder pastes 20 sample contacts into the roster and tags roles
- Founder fills the shift form for Saturday dinner service
- App emits three FR/EN drafts and an accept link
- Founder opens the accept link on a phone and taps Yes
- Fill board updates to show the acceptance
- Founder downloads the mission sheet PDF with the venue name and confirmation code
- Founder closes the shift and exports the pay recap CSV
Technical implementation plan
Stack
Architecture
One Next.js app on Vercel handles the authenticated desk (roster, shift form, fill board, close-out) and the single public route, the accept page. Supabase stores venues, contacts, shifts, tokens and responses with row-level security scoping every row to the authenticated venue. The shift form calls the LLM once to produce three FR/EN drafts, falling back to stored templates if the call fails or is slow. Resend delivers accept-link and mission-sheet emails. PDFs are rendered server-side from the same shift record, so the mission sheet, pay recap and CSV never disagree. Stripe Checkout creates the subscription; a webhook flips the venue to active; the Billing Portal handles cancellation.
Build steps
- Deploy Next.js skeleton to Vercel and claim the domain
- Create Supabase schema (venues, contacts, shifts, tokens, responses) with row-level security
- Add magic-link auth and a venue onboarding screen
- Build roster paste-import with a parser and role tagging
- Build the shift intake form and accept-token generator
- Add the LLM draft call with FR/EN escalation levels and template fallback
- Ship the public accept page with opaque tokens and one response POST
- Build the live fill board with polling and one-tap re-blast to top past acceptors
- Render the mission sheet PDF with confirmation code and branding
- Add close-out, hour adjustment and pay recap PDF
- Add monthly CSV/PDF accountant export
- Wire Stripe Checkout for both tiers, webhook and Billing Portal
- Publish the landing page with a 40-second Loom of the full flow
- Load-test the accept page and pre-warm PDF rendering before each demo
AI components
- One LLM call per shift to produce three escalating message drafts in French and English, with deterministic templates as the fallback path
- No matching, ranking, screening, verification or decision-making is delegated to a model
Pricing and monetization
Venue
Entry offerFor One independent restaurant, boutique hotel or small clinic covering shifts with extras
- Unlimited shift fill packs and FR/EN drafts
- No-login accept page per shift
- Live fill board and re-blast to past acceptors
- Mission sheet PDF with confirmation code
- Pay recap and monthly accountant export
- Roster up to 100 contacts
Desk
For Micro-agency or freelance coordinator placing extras across several venues
- Everything in Venue for up to 10 venues
- Shared roster across venues
- Branded mission sheet and pay recap PDFs
- CSV export of all shifts and payouts
- Priority email support
Model: Two flat monthly subscriptions with card required at trial start, no commission and no per-shift fee.
First revenue offer: I will set up your roster and run your next shift through Standby Desk live and free today — if it fills faster than your WhatsApp routine, it is $49/month and the first month starts today.
Expected ACV: $49
Upsell path: Coordinators with three or more venues move from Venue to Desk at $129, referred venues arrive through existing paying managers, and venues that keep the desk past month two are offered a prepaid annual plan.
First-customer acquisition
Direct Instagram and WhatsApp DMs to named owner-managers and head chefs in one city.
Where to find them
- Google Maps: independent restaurants and boutique hotels in one city, owner or chef named on the listing
- Instagram stories and posts containing a last-minute cover request
- Local hospitality job boards with open extra or freelance cover ads
- Hospitality manager Facebook groups and city WhatsApp groups
- Small clinics and medico-social sites advertising nurse-aide cover
- Instagram accounts of micro-agencies and freelance coordinators posting placements
Exact outreach motions
- Send a three-line DM referencing the venue's own cover post and asking how long that shift took to fill
- Offer to run their next shift live and free on a 10-minute screen share with their own roster
- Run the shift on the call: blast, accept page, fill board, mission sheet PDF with their venue name
- Send a 40-second Loom of the fill time plus the $49 Stripe link within ten minutes of the call
- Follow up once at 48 hours with the Loom, then drop after two touches
- Post the before/after fill pack in three hospitality manager groups per week with a first-shift-free link
Message template
Hi [Name] — saw your cover story on Saturday. How long did that shift take you to fill? I built Standby Desk: paste your extras' numbers once, one form sends them a message, they tap Yes on a link, and you get a mission sheet PDF. I'll set up your roster and run your next shift through it free today. Want me to?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Deployable skeleton
- Claim the domain and deploy a Next.js app to Vercel
- Create Supabase project with magic-link auth and a venues table
- Connect Stripe test mode with a $49 product
Deliverable: Live URL with working login and an empty desk
Paste-import
- Build paste-import that parses name and phone lines into contacts
- Add role tags and last-worked date per contact
- Seed a founder test venue with 20 placeholder contacts
Deliverable: A 20-contact roster imported in under two minutes
Shift form and drafts
- Build the shift intake form (role, date, start/end, rate, address, bring)
- Generate FR and EN drafts at three escalation levels with copy buttons
- Create a unique accept token per shift
Deliverable: One form outputs three copyable drafts and a live accept link
Public page and fill board
- Build the no-login accept page with Yes/No/Maybe and a name field
- Build the fill board with invited, accepted, declined and silent columns
- Add polling so the board updates without a manual refresh
Deliverable: Worker taps Yes and the board reflects it within seconds
PDFs and close-out
- Render the mission sheet PDF with confirmation code and signature line
- Add close-out with hour adjustment and a pay recap PDF
- Add the monthly CSV and PDF accountant export
Deliverable: End-to-end MVP on the founder test venue; build stops here
Billing and landing
- Wire Stripe Checkout for $49 and $129 with a 14-day trial
- Add Billing Portal and trial-to-paid handling
- Publish a landing page with a 40-second Loom of the full flow
Deliverable: A stranger can pay $49 without speaking to the founder
First outreach
- Build a 60-venue list from Google Maps and recent cover posts
- Send 20 three-line Instagram DMs offering a free live shift
- Log every touch in one sheet
Deliverable: 60-venue list and 20 DMs sent
Week 2 · Launch & first sale · 7 days
Prove it on a call
- Run one shift end to end on a 10-minute screen share
- Send the $49 Stripe link at the end of the call
- Fix every blocker hit during the call the same day
Deliverable: First paying venue or a dated follow-up commitment
Outreach and follow-up
- Send 20 more DMs in the same city
- Follow up day-7 silent DMs once with the Loom
- Cut any step in the flow that takes over 30 seconds
Deliverable: 40 cumulative touches, 3 demos booked
Roster imports
- Import rosters for two venues on a call
- Write a one-page setup guide
- Add role filters to the re-blast shortlist
Deliverable: Two venues with 15 or more contacts live in their account
Community posts
- Post the before/after fill pack in three hospitality manager groups
- Reply in two open extra threads with the free-shift offer
- Track which post produces DMs
Deliverable: Three group posts live with tracked links
Widen the segment
- Send 25 DMs to clinics and boutique hotels
- Run two live demos
- Send two $49 links
Deliverable: Five demos run cumulatively
Demo assets
- Record a fill-time Loom on the founder test venue
- Publish an anonymised numbers-only shift recap
- Update the landing page headline with the measured fill time
Deliverable: Loom v2 published with no client names used
Funnel audit
- Count DMs, demos, links sent and payments collected
- Kill the weakest message variant
- Pick the single segment for week three
Deliverable: Funnel numbers written down with one decision attached
Week 3 · Repeat & systematize · 7 days
Ship from call notes
- Add one-tap re-blast to the top five past acceptors per role
- Fix the top three support complaints
- Add shift duplication for recurring covers
Deliverable: Two shipped fixes traced to real call notes
Multi-venue buyers
- Add a multi-venue switcher and shared roster for the $129 tier
- Write the Desk-page copy and branded PDF toggles
- DM 15 micro-agencies and freelance coordinators
Deliverable: Desk tier purchasable and 15 agency DMs sent
Outreach sink
- Send 30 DMs
- Follow up every 48-hour-silent thread once
- Book demos into two 45-minute blocks
Deliverable: 70 cumulative DMs and 8 demos booked
Second segment skin
- Send 20 DMs to small clinics with cover posts
- Adjust mission sheet wording for clinical roles
- Add a not-legal-advice footer to every PDF
Deliverable: Clinic variant of the mission sheet live
Accept links everywhere
- Test accept links in Gmail, Outlook and WhatsApp on two phones
- Add an SMS-length draft under 300 characters
- Add a plain-text fallback email
Deliverable: Accept links open cleanly on four client and device combinations
Close rate
- Run four live demos
- Send each $49 link within ten minutes of the call
- Log objections verbatim
Deliverable: 12 demos run cumulatively and a written objection list
Hard decision
- Compare collected revenue against the 22-customer base plan
- If under half, drop the Desk tier and double DMs
- Do not change prices mid-window
Deliverable: Written midpoint decision with the next 9 days fixed
Week 4 · Scale what works · 7 days
Remove founder onboarding
- Add an in-app setup checklist with a sample roster download
- Write six canned support replies
- Add a copy-paste onboarding email
Deliverable: A venue can go live without founder assistance
Outreach sink
- Send 30 DMs
- Re-DM the ten warmest no-replies with a specific shift example
- Post in three more groups
Deliverable: 100 cumulative DMs sent
Borrowed trust
- Ask every paying venue for one intro to another manager
- Offer one free month per intro that pays
- Record referral source on every new signup
Deliverable: Referral link live and ten asks sent
Reusable asset
- Publish a before/after fill-pack carousel on Instagram
- Post the same asset in the two best-performing groups
- Add the first-shift-free link to the bio
Deliverable: One reusable content asset published in three places
Outreach sink
- Send 30 DMs
- Run three live demos
- Send three $49 links
Deliverable: 16 demos cumulative and all links sent
Agency sale
- Demo the Desk tier to two coordinators
- Offer founder-assisted migration of their venue list
- Send the $129 links
Deliverable: First Desk-tier payment attempt or a dated no
Money in the window
- Confirm every trial has a card on file
- Email every trialing venue a one-line next-shift nudge
- Check no first charge is scheduled after day 30
Deliverable: All trials have a payment path before day 30
Days 29-30 · Consolidate · 2 days
Collect
- Send 30 DMs with last-week-of-the-free-first-shift framing
- Call the five warmest leads
- Send payment links to every verbal yes
Deliverable: Every pending yes has a link in hand
Verified profit
- Reconcile Stripe payouts against the customer list
- Export revenue, refund and fee reports
- Write the day-31 plan for the two best-performing segments
Deliverable: Verified profit number and a written day-31 plan
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- All scenarios assume Stripe processing at 2.9% plus $0.30 per charge, with the fee applied to collected revenue.
- Conservative: 8 Venue customers at $49, reached from roughly 120 outreach touches.
- Base: 22 Venue customers at $49, reached from roughly 300-450 outreach touches at a 5-10% demo rate and 20-30% demo-to-paid.
- Upside: 40 customers, 34 on Venue at $49 and 6 on Desk at $129, giving a $61 blended ARPU.
- Ad spend is $0 in every scenario because the acquisition channel is organic DM outreach.
- Operating costs cover Vercel, Supabase, domain, Resend and LLM draft calls; they are excluded from hackathon profit but included in business profit.
- Refunds are modelled at one to two monthly charges in the upside case only; a single refund reduces profit by about $47 at Venue.
- The $100K target is not reachable with this wedge; low four figures is the honest 30-day projection.
- Every figure is a projection built from these stated assumptions, not verified revenue.
Conservative
8 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $14
- Paid marketing
- $0
- Hackathon profit
- $378
- Operating costs
- $28
- Business profit
- $350
Base case
22 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $38
- Paid marketing
- $0
- Hackathon profit
- $1,040
- Operating costs
- $42
- Business profit
- $998
Optimistic
40 customers- Refunds
- $98
- Chargebacks
- $0
- Payment fees
- $83
- Paid marketing
- $0
- Hackathon profit
- $2,259
- Operating costs
- $85
- Business profit
- $2,174
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $1,078
- Payment fees (3.9%)
- $42
- Paid marketing
- $0
- Hackathon profit
- $1,036
- Business profit
- $994
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
All scenarios are projections derived from the stated assumptions. They are not verified revenue, existing customers or traction of any kind.
Main risks and validation experiments
Risk 1Managers decide WhatsApp plus memory is good enough and never pay.
Qualify on the measured time and message count of their last cover before demoing, and sell only to venues above the threshold.
On the first five demo calls, ask how many minutes last Saturday's cover took and how many people they messaged.
If fewer than three of the first ten venues report more than 20 minutes or more than eight messages, re-scope the wedge.
Risk 2Thin or stale rosters make the product useless for a given venue.
Qualify for at least 15 usable contacts on the first call and decline venues below that.
Ask each of the first ten venues to paste their list during the first call and count usable phone numbers.
If fewer than half of the first ten venues have 15 or more usable contacts, the concept collapses.
Risk 3The decision-maker is on the floor during service hours and cannot be reached inside the window.
Restrict DM sends to 14:00-16:30 and 22:00-23:30 local time and book demos into two fixed daily blocks.
Track reply rate by send hour across the first 60 DMs.
If reply rate stays below 3% after 100 DMs, switch from DM to in-person drop-in at 15:00.
Risk 4Upfront monthly charges are refunded or charged back after the contest window, eroding verified profit.
Keep the trial short, show the fill time and mission sheet before the first charge, and require a card at signup.
Measure how many trials touch the product twice before their first charge.
If refunds or chargebacks exceed 10% of collected revenue, move to a per-shift pack model.
Risk 5Solo founder splits time between build, support and outreach and ships too late to sell.
Freeze the build on day 5 regardless of polish and route all remaining time to demos and collection.
Check on day 5 whether an accept link and a mission sheet PDF work end to end on a phone.
If the MVP is not payable by day 7, cut PDFs to a plain HTML print view and keep selling.
Hour-by-hour: the first 24 hours
Hours 1-2
- Claim the domain and deploy the Next.js skeleton to Vercel
- Create the Supabase project and connect environment variables
Output: Public URL serving a placeholder page
Hours 3-4
- Create venues, contacts, shifts, tokens and responses tables with row-level security
- Add magic-link auth and a protected desk route
Output: Working login that lands on an empty desk
Hours 5-6
- Build the roster paste-import parser for name and phone lines
- Add role tags and last-worked date inputs
Output: A 20-contact roster importable in one paste
Hours 7-9
- Build the shift intake form
- Generate the unique accept token and the public accept route shell
Output: A form that emits a live accept URL per shift
Hours 10-12
- Create the Stripe $49 and $129 test products with a 14-day trial
- Seed the founder test venue with 20 placeholder contacts and one demo shift
Output: Test-mode checkout and a demo venue ready for tomorrow's screen share
Full 30-day launch report
Read the full generated report
Standby Desk — 30-Day Launch Report
Contest window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. Only money collected inside that window counts, through the payment account connected to TrustMRR. No customer, payment or usage exists before launch.
1. Product opportunity and positioning
Venues do not lack staff lists; they lack a fast way to work them. Standby Desk converts the private contact list a venue already owns into a shift-fill pipeline: one intake form, three escalating FR/EN message drafts, one no-login accept link, a live fill board, and a mission sheet PDF with a confirmation code. There is no supply side to seed, no verification, no commission — the venue keeps paying workers the way it does today. The buyer is one named decision-maker with a shift to cover this week, so the sale can close on a single screen share. JEV places the concept at 66.3/100 in band B, strongest on speed to first revenue and weakest on market demand. That shape rewards narrow execution and an honest expectation of low four figures, not a $100K run.
2. Smallest sellable MVP
Ship only what a manager can be shown live: roster paste-import with role tags, the shift form that emits three drafts plus an accept token, the public accept page, the fill board, the mission sheet PDF, and a close-out that produces a pay recap and a monthly CSV. Auth is a magic link; billing is Stripe Checkout with a 14-day trial. Anything that does not appear on that ten-minute screen share is out: no marketplace, no worker accounts, no payouts, no rota planning, no POS or booking integration, no mobile app, no ratings, no credential checks.
3. Technical implementation plan
Next.js on Vercel, Supabase Postgres with row-level security and magic-link auth, Stripe Checkout plus Billing Portal, Resend for accept-link and mission-sheet email, @react-pdf/renderer for PDFs, Tailwind. Five build days: day 1 skeleton and auth, day 2 roster import, day 3 shift form and draft generation, day 4 accept page and fill board, day 5 PDFs and close-out. Drafts come from one LLM call per shift with hard-coded templates as fallback, so a model outage costs polish and never a sale. The accept page is the only public surface: opaque per-shift tokens, a read-only shift summary, one POST to record a response. The realistic breakage points are PDF font embedding and serverless cold starts during a live screen share — cache a sample PDF on page load and pre-warm before every demo call.
4. Pricing and monetization
Two monthly plans: Venue at $49 for one site and up to 100 roster contacts; Desk at $129 for micro-agencies coordinating up to ten venues with a shared roster and branded PDFs. Monthly, card at trial start, so the first charge lands inside the window. No per-shift fee and no commission: commission invites comparison with marketplaces and adds accounting work the founder cannot support. The base case assumes the $49 plan only; Desk is upside, never the plan. Revenue grows through referred venues and by moving coordinators with three or more sites onto Desk.
5. First-customer acquisition
One channel: direct Instagram and WhatsApp DMs to named owner-managers in one city. Build a 60-venue list from Google Maps plus venues that posted a last-minute cover request or an open extra ad in the last fortnight. Three-line message: name their post, ask how long Saturday's cover took to fill, offer to run their next shift live and free with their own roster. The demo is the sale — blast, accept page, fill board, mission sheet PDF with their venue name on it, then the Stripe link inside ten minutes. Follow up once at 48 hours with a 40-second Loom; drop after two touches. Week-one goal: 40 DMs, 5 demos, 1 payment.
6. Detailed 30-day execution roadmap
Days 1-5 are build only; the MVP must be payable by day 5, and day 6 is landing page, trial billing and a Loom. Days 7-14 are list building and the first live shifts: roughly 20 DMs a day, one screen-share shift per booked demo, same-day fixes for anything that broke on the call. Targets: first $49 by day 8, five demos by day 12. Days 15-21 add the re-blast shortlist, the Desk tier, a clinic variant of the mission sheet, and four demos every two days; day 21 is a hard midpoint decision — if collected revenue is under half of plan, drop Desk and double DMs rather than change the product. Days 22-28 push past 100 cumulative DMs, add referral asks, and confirm every trial has a card on file with a charge inside the window. Days 29-30 are collection and reconciliation: chase every verbal yes, reconcile Stripe payouts against the customer list, and write down the verified profit number.
7. Revenue and profit scenarios
Every figure below is a projection from stated assumptions, not verified revenue. Conservative: 8 Venue customers at $49 = $392 collected, $14 processing at 2.9% plus $0.30, no refunds, no chargebacks, no ad spend, $28 operating. Base: 22 customers = $1,078, $38 fees, $42 operating. Upside: 40 customers with a $61 blended ARPU = $2,440, $83 fees, two refunds at $98, $85 operating. Hackathon profit subtracts refunds, chargebacks, fees and paid marketing only; business profit additionally subtracts hosting, tooling and AI delivery. In every case absolute dollars are small and percentage margin is high, which is the point: the contest ranks verified profit, and this wedge is built to be profitable on the first day it earns anything.
8. Main risks and validation experiments
The killer risk is that WhatsApp plus memory is good enough. Test it before building more: on the first five demo calls ask how many minutes last Saturday's cover took and how many people they messaged; if fewer than three of ten venues report more than 20 minutes or more than eight messages, the wedge is too small and the concept must be re-scoped. Second, thin rosters: qualify on the first call and politely decline venues with fewer than 15 usable contacts. Third, reachability: send DMs only 14:00-16:30 and 22:00-23:30 local, and track reply rate by hour. Fourth, refund exposure on upfront monthly charges: keep the trial short and the value visible before the first charge; if refunds exceed 10% of collected revenue, move to per-shift packs. Fifth, solo-founder overload: the build freezes on day 5 regardless of polish, because days 6-30 are worth more than any remaining feature.
9. First 24-hour action plan
Hours 1-2: claim the domain, deploy the Next.js skeleton, create the Supabase project. Hours 3-4: schema with row-level security, magic-link auth, a protected desk route. Hours 5-6: roster paste-import parsing name and phone lines with role tags. Hours 7-9: shift intake form and the accept-token generator with the public route shell. Hours 10-12: Stripe test products at $49 and $129, plus a founder test venue seeded with 20 placeholder contacts and one demo shift. Day one ends with a deployed URL, a working login and a form that emits a link — not a plan.
This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.
Related ideas
All ideas →Bulletin Nounou
Bulletin Nounou turns a French childminder's month of attended days into a ready-to-send bulletin de salaire PDF plus a copy-paste Pajemploi figure card, in under three minutes per child.
ShiftClean Payroll
ShiftClean Payroll turns messy frontline timeclock exports into payroll-ready CSVs and a one-page risk report for independent bookkeepers.
ShortPay Sifter
ShortPay Sifter ingests a small practice's ERA/835 files or claims export and returns a per-payer list of claims that paid below that practice's own historical allowed rate, packaged as a ready-to-send underpayment dispute packet.