ProofDay Site Log
Solo contractors reply to one daily email and get a timestamped, client-ready site-log PDF that proves what was done, when, and with what materials.
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-operator home-service contractors (electricians, plumbers, handymen, remodelers) with 1-5 workers in the US, Canada or UK, triggered by a client demanding daily updates or a payment or warranty dispute.
Monetization potential 4.6/10
Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/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
12 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner-operator home-service contractors (electricians, plumbers, handymen, remodelers) with 1-5 workers in the US, Canada or UK, triggered by a client demanding daily updates or a payment or warranty dispute.
Why now
Contractors already live in email and already lose disputes for lack of a dated record; a $99 one-time purchase is approved by the owner without procurement, integration or training.
Problem
Jobs finish with no consistent daily record, so when a client disputes scope or files a warranty claim the contractor rebuilds days from memory and text threads, losing time and sometimes money.
Solution
A daily email prompt takes a short reply plus optional photos; the system extracts job site, work completed, materials, delays and safety notes, stores the entry, and generates a branded daily or weekly PDF site log with timestamps and photo thumbnails that the contractor forwards to the client.
1. Product opportunity and positioning
ProofDay Site Log sells a record, not a habit. The buyer is an owner-operator home-service contractor — electrician, plumber, handyman, small remodeler — running one to five workers in the US, Canada or UK. The buying trigger is concrete and recurring: a client asks for daily updates, disputes scope, or files a warranty claim, and the contractor has to reconstruct three weeks of work from memory and text threads.
The product reuses the OhLife loop — one daily email, one reply, an archive — and points it at a commercial artifact. The reply becomes a timestamped, branded PDF site log with photo thumbnails that the contractor forwards to the client, the general contractor, or an insurer. Nothing to install, no field-service suite, no training session.
JEV scored this concept 61.9/100 (band C, confidence 0.70). Speed to first revenue is the strongest criterion at 8.32; monetization potential is the weakest at 4.64. That shapes the whole plan: zero paid acquisition, a $99 price a single invoice-protecting PDF justifies, and a deliberate second revenue unit (extra site packs, then renewal) offered to every buyer instead of chasing a bigger first cheque.
Positioning: for contractors who lose disputes they should win, ProofDay turns a one-line email reply into a dated PDF site log in under a minute.
2. Smallest sellable MVP
The MVP is one loop and one artifact: a contractor pays $99, gets a unique inbox address, replies to a daily prompt with text and photos, and downloads a branded PDF for any day or week from a magic-link portal. Everything else is out.
In: Postmark inbound webhook per customer address; photo ingestion with thumbnails; OpenAI structured extraction into job site, work completed, materials, delays and safety notes; React-PDF daily and weekly logs; Stripe Checkout and webhook; magic-link portal listing PDFs; daily prompt and weekly digest via Resend; an admin regenerate/resend button.
Out: mobile app, scheduling, dispatch, invoicing, accounting, team roles, SSO, handwriting OCR, hardware, client portal, two-way messaging.
Demo flow: founder replies to a sample address — "Replaced 40A breaker at 118 Maple, customer added garage outlet, ran out of 12/2, back Thursday" — with two phone photos. Webhook stores the raw email, the model returns structured fields, the PDF renders with date, address, bullets and thumbnails, the portal lists it, the contractor forwards it. Build time: four days.
3. Technical implementation plan
One Next.js app on Vercel, Supabase for auth, Postgres and file storage, Postmark for inbound and Resend for outbound, OpenAI for extraction, React-PDF for rendering, Stripe for money. Inbound email is the risky edge, not the PDF.
Pipeline in plain language: Postmark posts the parsed email to a webhook, the webhook resolves the recipient address to a customer and site, uploads attachments to Supabase storage, sends the body and photo captions to the model with a strict JSON schema, writes the entry row, and triggers a render job. The PDF is generated server-side on demand, cached in storage, and linked in the portal and the weekly digest.
Build order: schema and address provisioning, inbound webhook, storage upload, extraction call, PDF template, portal, Stripe, crons, admin. Hardest risk is messy inbound: quoted replies, forwarded chains, signatures and HTML-only clients polluting extraction — strip quoted text before the model and keep the raw email as the fallback the contractor can always edit. The model is used for exactly one job: turning free-text site notes into structured fields plus a clean two-sentence summary.
4. Pricing and monetization
Single tier: Founding Contractor, $99 one-time, 12 months of archive access, up to three active job sites, daily prompt and weekly digest. No free tier and no trial in 30 days — a free plan destroys the only signal the contest needs.
Gross margin is effectively the full price: per-customer serving cost is under $0.25 per month for extraction and rendering at this volume, with hosting, domain and email inside low single-digit dollars per month. Collection is the main deduction, assumed at roughly 4% processing.
Second revenue unit, same price point: after purchase, every buyer gets an offer for an additional site pack at $99 when they run more than three concurrent jobs. Month 12 brings a renewal email. Every buyer is also asked for one contractor peer intro, which is the only compounding channel available to a solo founder in 30 days.
5. First-customer acquisition
One channel: direct outreach in trade Facebook groups and subreddits. No ads, no SEO, no partnerships.
Where: r/electricians, r/Plumbing, r/Contractor, r/handyman, r/Construction; Facebook groups for electrical contractors, plumbing businesses, handyman businesses and remodeling contractors; state-level contractor groups.
Method: search for "client won't pay", "chargeback", "warranty", "daily report", "get paid". Reply with substance first, then the angle: "I can turn that job's texts into a dated PDF site log — want a free sample?" Build the sample from their public description, send it with the Founding Contractor offer at $99, follow up once after 48 hours with three lines and the sample attached. Week-one goal: 120 named prospects, 60 direct messages, 5 sample PDFs delivered, at least 1 paid.
6. 30-day roadmap
Days 1-5: build to a frozen MVP by day 5. Days 6-7: live checkout connected to the payment account, landing page, three sample PDFs, and a 120-name outreach list. Days 8-14: outreach volume, samples, and the first paid customer targeted for day 12, then hands-on onboarding of that buyer. Days 15-21: second and third sales, fix what the first buyers complain about, post samples in more groups. Days 22-28: sustained 20 messages per day, site-pack offer, testimonial capture. Days 29-30: proof page, final push, reconcile profit and export data.
7. Revenue and profit scenarios
All figures are projections from stated assumptions, not verified revenue. Conservative: 3 buyers × $99 = $297; fees $12; hackathon profit $285; operating costs $25; business profit $260. Base: 10 × $99 = $990; fees $39; hackathon profit $951; operating $45; business profit $906. Upside: 25 × $99 = $2,475, refunds $50, fees $97, ad spend $150; hackathon profit $2,178; operating $90; business profit $2,088. The base case needs roughly 300 direct touches at a 10% close rate — plausible for a founder doing 20 messages a day for two weeks, not guaranteed.
8. Risks and validation experiments
Activation is the real risk: a buyer who never sends a second log churns and refunds. Test it by watching whether the first three buyers submit three logs in week one; if under 40%, the prompt timing or reply friction is wrong.
Channel risk: groups block self-promotion. Test by posting a genuinely useful sample-only comment in three groups and measuring whether it survives an hour and draws any comment.
Accuracy risk: extraction mangles messy notes and the PDF embarrasses the contractor in front of a client. Test with ten deliberately ugly replies — forwarded chains, voice-to-text garbage, all caps — and keep raw text visible in the PDF so errors are correctable.
Price risk: $99 might be the wrong number. Test by offering the same package to half the prospects at $99 and half at $149; whichever closes faster sets the price for week three. Kill or narrow the concept if 100 direct touches produce zero sample requests.
9. First 24 hours
Hour 1-2: register the domain, create the repo, provision Postmark inbound and verify the forwarding subdomain. Hour 3-5: Supabase schema for customers, sites, entries and files; address provisioning. Hour 6-8: inbound webhook parsing plus attachment upload, verified against a real reply from a personal mailbox. Hour 9-11: extraction prompt with strict JSON schema tested on five hand-written messy notes. Hour 12-14: first PDF template rendered from a real entry. By hour 24 there must be one end-to-end PDF of a fake job sitting in storage and one sample address that works.
Smallest sellable MVP
A paid $99 account with a unique email address, a daily prompt, reply-to-log ingestion with photos, and a downloadable branded PDF site log for any day or week.
Must-have features
- Postmark inbound webhook with a unique per-customer email address
- Photo attachment ingestion with thumbnails embedded in the PDF
- OpenAI structured extraction: job site, work completed, materials, delays, safety notes
- Branded daily and weekly PDF site log with dates and photo thumbnails
- Stripe Checkout plus webhook provisioning the account
- Magic-link portal listing generated PDFs
- Scheduled daily prompt email and weekly digest via Resend
- Admin screen to regenerate or resend a PDF
Explicitly out of scope
- Native iOS or Android app
- Scheduling, dispatch, invoicing or accounting
- Team roles, permissions or enterprise SSO
- Handwriting OCR or hardware sensors
- Client portal or two-way messaging inbox
- Free tier or trial
Demo flow (what the buyer sees)
- Founder replies to the sample address with a short job note and two phone photos
- Postmark posts the parsed email to the webhook
- Attachments upload to storage; body and captions go to the extraction model
- Model returns structured fields plus a two-sentence summary
- PDF renders with date, site address, bullets, delays and photo thumbnails
- Portal shows the PDF; contractor forwards it to the client
Technical implementation plan
Stack
Architecture
Postmark delivers each inbound reply to a webhook that maps the recipient address to a customer and site, uploads photos to Supabase storage, strips quoted text, calls the model for structured fields, and writes an entry row. A server-side render job turns entries into a cached PDF in storage, linked from the magic-link portal and the weekly digest. Stripe checkout provisions the account and address.
Build steps
- Create Next.js app, Supabase project and storage bucket
- Model customers, sites, entries, files with per-customer inbound address
- Wire Postmark inbound webhook and address resolution
- Strip quoted reply chains and signatures before extraction
- Add OpenAI extraction with a strict JSON schema and a raw-text fallback
- Build the React-PDF template with logo, dates and photo thumbnails
- Build magic-link portal listing PDFs with download and forward links
- Add Stripe Checkout, webhook provisioning and receipt email
- Add daily prompt cron, weekly digest and admin regenerate button
- Run three fake jobs end-to-end and fix edge cases
AI components
- OpenAI structured extraction of free-text site notes into job site, work completed, materials, delays and safety notes
- Short generated summary line for the PDF header and weekly digest
Pricing and monetization
Founding Contractor
Entry offerFor Solo home-service contractors with 1-5 workers
- Daily email prompt and reply-to-log workflow
- Branded PDF site logs with photos
- 12 months of archive access
- Up to 3 active job sites
- Weekly digest email
Model: One-time $99 Founding Contractor purchase covering 12 months, with additional site packs at the same $99 unit price.
First revenue offer: Founding Contractor: $99 one-time, 12 months, up to 3 active job sites — I will build your current job's site log from your existing texts as a free sample before you pay.
Expected ACV: $99
Upsell path: Additional site pack at $99 when a contractor exceeds three active sites, then a renewal email at month 12; every buyer is asked for one contractor peer intro.
First-customer acquisition
Direct outreach in trade-focused Facebook groups and subreddits where solo contractors discuss payment disputes, warranty claims and clients demanding daily updates.
Where to find them
- r/electricians
- r/Plumbing
- r/Contractor and r/handyman
- r/Construction
- Facebook groups for electrical contractors and plumbing businesses
- Facebook groups for handyman and remodeling businesses
- State-level contractor Facebook groups
- Comment threads mentioning 'client won't pay', 'chargeback', 'warranty', 'daily report'
Exact outreach motions
- Search each group weekly for dispute and daily-report keywords, log every poster with a link
- Reply with one useful sentence about documentation, then offer a free sample PDF of their described job
- Build the sample from their public description and send it as a PDF attachment within 24 hours
- Include the Founding Contractor offer: $99 one-time, 12 months, free sample built first
- Follow up once after 48 hours with three lines and the same PDF attached
- Post a before/after sample in three groups with a 'comment SAMPLE' call to action
- Ask every buyer for one contractor peer intro the day after their first PDF
Message template
Saw your post about the client disputing the extra work. I turn a job's texts and photos into a dated PDF site log you can forward — dates, materials, delays, photos. Want me to build one from this job free so you can see it? If it's useful it's $99 for 12 months.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Repo, schema, inbound address
- Create Next.js app, Supabase project and storage bucket
- Model customers, sites, entries and files
- Verify Postmark inbound subdomain and webhook
Deliverable: An email to a test address creates a database row.
Model output to rendered PDF
- Write strict JSON extraction schema covering five fields
- Strip quoted replies and signatures before the model call
- Build React-PDF template with logo, dates and thumbnails
Deliverable: A branded PDF rendered from a real email reply with two photos.
Stripe and portal
- Add Stripe Checkout and webhook provisioning the account
- Generate unique inbound address on payment
- Build magic-link portal listing PDFs
Deliverable: Test-mode purchase produces a working address and portal.
Prompts, digest, admin
- Schedule daily prompt email at contractor local time
- Build weekly digest linking the week's PDFs
- Add admin regenerate and resend button
Deliverable: Cron sends a prompt and a digest to a test account.
End-to-end hardening
- Run three fake jobs across three sites
- Test HTML-only replies, forwarded chains and photo-only emails
- Fix the three worst failures only
Deliverable: MVP frozen with a known-limitations list.
Landing page and live payments
- Publish landing page with pricing and sample PDFs
- Connect the payment account to TrustMRR and switch Stripe live
- Write three sample site logs from invented jobs
Deliverable: Live checkout and a public sample PDF.
Prospect list
- Log 120 contractor prospects across groups and subreddits
- Draft the DM and comment templates
- Build a fast sample-PDF workflow for inbound requests
Deliverable: Spreadsheet of 120 prospects with source links.
Week 2 · Launch & first sale · 7 days
Send messages
- Send 20 direct messages to logged prospects
- Offer free samples to the two strongest dispute posts
Deliverable: 20 DMs sent, conversation log started.
Deliver proof
- Build and send 5 sample PDFs from public job descriptions
- Ask each recipient what is missing
Deliverable: 5 sample PDFs delivered.
Group presence
- Post before/after sample in 3 trade groups with 'comment SAMPLE'
- Reply to every comment within 2 hours
Deliverable: 3 posts live, inbound comments logged.
Second wave
- Send 20 more DMs
- Follow up the 48-hour non-responders with 3 lines plus PDF
Deliverable: 40 total DMs, follow-ups sent.
Close Founding Contractor
- Push the 3 warmest prospects to checkout with the sample attached
- Send the payment link directly in thread
Deliverable: First $99 payment collected.
Make buyer succeed
- Onboard the buyer on a call or voice note
- Watch their first real reply through to PDF
Deliverable: One customer-generated PDF forwarded to a client.
Feedback loop
- Run a 15-minute feedback call
- Ask for one contractor peer intro
- Fix the single biggest friction point
Deliverable: Testimonial line or referral intro.
Week 3 · Repeat & systematize · 6 days
Convert sample recipients
- Send 30 DMs including all prior sample recipients
- Repost the warmest comment thread
Deliverable: 30 new DMs, 2 active negotiations.
Ship feedback
- Fix timezone and date formatting issues
- Improve extraction on short replies
Deliverable: Deployed fix with a changelog line.
Helpful replies
- Answer 3 'client won't pay' threads with documentation advice
- Link the sample PDF only when asked
Deliverable: 3 substantive thread replies.
Free sample close
- Offer to rebuild a lost job's log from texts for 5 prospects
- Close anyone who receives a usable PDF
Deliverable: Second paid customer.
Outreach count
- Send 40 DMs
- Log every response with a next action
Deliverable: 70 cumulative DMs.
Public proof page
- Publish a shareable sample-log page
- Add it to the DM template
Deliverable: Public sample URL used in outreach.
Week 4 · Scale what works · 8 days
Numbers and message
- Count sends, replies, samples, sales
- Rewrite the weakest line of the DM template
Deliverable: Updated template and a conversion snapshot.
Site packs
- Email all buyers the additional site pack offer at $99
- Add tracking for the offer
Deliverable: Site-pack offer sent to every buyer.
Daily rhythm
- Send 20 DMs
- Follow up all 48-hour non-responders
Deliverable: 90 cumulative DMs.
Logging habit
- Nudge buyers with zero logs in 3 days
- Check weekly digest open behaviour
Deliverable: Activation list of who needs help.
Daily rhythm
- Send 20 DMs
- Post one sample in a new group
Deliverable: 110 cumulative DMs.
Cut support load
- Write a 5-line reply-to-log help note
- Add it to the portal and prompt footer
Deliverable: Self-serve help note shipped.
Warm pipeline
- Message every warm prospect with a deadline framing
- Offer the sample build as the closer
Deliverable: All warm leads answered.
Peer intros
- Ask all buyers for one intro
- Follow up on outstanding intros
Deliverable: Referral requests sent to every buyer.
Days 29-30 · Consolidate · 2 days
Testimonials and samples
- Publish buyer testimonials with permission
- Refresh sample PDFs with real log structure
Deliverable: Updated landing page with proof.
Reconcile and report
- Reconcile payments, refunds and fees
- Export logs and revenue snapshot
- Send final follow-up to all open threads
Deliverable: Final profit number and export archive.
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 are 30-day projections from stated assumptions, not verified revenue or existing customers.
- Base and Conservative assume organic outreach only, so ad_spend is 0.
- Upside assumes $150 of paid promotion in trade communities in the final week.
- Payment processing assumed at roughly 4% of collected revenue via Stripe.
- ARPU held at $99 for every scenario; site packs and renewals are not counted.
- Conservative assumes 3 buyers from roughly 150 direct touches.
- Base assumes 10 buyers from roughly 300 direct touches at about a 10% close rate.
- Upside assumes 25 buyers from roughly 500 touches plus group posts and $150 paid promotion.
- Operating costs cover Vercel, Supabase, Postmark, Resend, domain and OpenAI usage to serve those customers.
- Upside carries $50 of refunds on the assumption one or two buyers never activate.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $12
- Paid marketing
- $0
- Hackathon profit
- $285
- Operating costs
- $25
- Business profit
- $260
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $39
- Paid marketing
- $0
- Hackathon profit
- $951
- Operating costs
- $45
- Business profit
- $906
Optimistic
25 customers- Refunds
- $50
- Chargebacks
- $0
- Payment fees
- $97
- Paid marketing
- $150
- Hackathon profit
- $2,178
- Operating costs
- $90
- Business profit
- $2,088
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $990
- Payment fees (3.9%)
- $39
- Paid marketing
- $0
- Hackathon profit
- $951
- Business profit
- $906
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.
Scenario models from stated assumptions, not verified revenue.
Main risks and validation experiments
Risk 1Buyers pay but never send a second log, so the product becomes an unused subscription and drives refunds.
Hand-hold the first three buyers personally and time the daily prompt to their local evening.
Track whether each of the first three buyers submits 3 or more logs within seven days of purchase.
If fewer than 40% of buyers submit three logs in week one after two prompt-timing fixes, the email-only input is wrong.
Risk 2Trade Facebook groups and subreddits block self-promotion and DMs go unanswered.
Lead with documentation advice, post samples only where allowed, and spread across at least eight communities.
Post a sample-only comment in three groups and measure survival past one hour and comment count.
If three communities remove posts and 100 DMs produce zero sample requests, the channel is dead and the concept needs a different route.
Risk 3AI extraction misreads messy job notes and the PDF embarrasses the contractor in front of a client.
Always display the raw reply text in the PDF alongside extracted fields, and allow one-click regeneration.
Run ten deliberately ugly replies — forwarded chains, all caps, voice-to-text, photo only — through extraction and grade the output.
If more than two of ten test replies produce materially wrong fields after prompt fixes, extraction cannot be trusted for client-facing output.
Risk 4$99 one-time attracts low-intent buyers and produces refunds or chargebacks.
Build the sample PDF before payment so the buyer sees the artifact first, and keep the offer single and clear.
Offer the same package at $99 to half of prospects and $149 to the other half and compare close speed.
If refunds exceed 10% of collected revenue or chargebacks appear, stop one-time sales and require a paid sample step first.
Hour-by-hour: the first 24 hours
Hours 1-2
- Register domain and create the Next.js and Supabase projects
- Verify the Postmark inbound subdomain and webhook endpoint
Output: Working repo with inbound email routing to a test webhook.
Hours 3-5
- Create customers, sites, entries and files tables
- Implement per-customer inbound address provisioning
Output: Database schema plus address generation tested on two accounts.
Hours 6-8
- Parse inbound body, strip quoted chains and signatures
- Upload photo attachments to Supabase storage
Output: A real reply from a personal mailbox stored as an entry with photos.
Hours 9-11
- Write the strict JSON extraction prompt
- Test it on five hand-written messy job notes and fix failures
Output: Extraction prompt with five graded test results.
Hours 12-14
- Build the React-PDF template with dates, bullets and thumbnails
- Render one PDF from the stored test entry
Output: First end-to-end branded PDF saved in storage and download-ready.
Hours 15-24
- Log the first 30 contractor prospects from groups and subreddits
- Draft the DM template and sample-PDF workflow
Output: 30 named prospects and a sendable message template.
Full 30-day launch report
Read the full generated report
ProofDay Site Log — 30-day launch report
1. Product opportunity and positioning
ProofDay Site Log sells a record, not a habit. The buyer is an owner-operator home-service contractor — electrician, plumber, handyman, small remodeler — running one to five workers in the US, Canada or UK. The buying trigger is concrete and recurring: a client asks for daily updates, disputes scope, or files a warranty claim, and the contractor has to reconstruct three weeks of work from memory and text threads.
The product reuses the OhLife loop — one daily email, one reply, an archive — and points it at a commercial artifact. The reply becomes a timestamped, branded PDF site log with photo thumbnails that the contractor forwards to the client, the general contractor, or an insurer. Nothing to install, no field-service suite, no training session.
JEV scored this concept 61.9/100 (band C, confidence 0.70). Speed to first revenue is the strongest criterion at 8.32; monetization potential is the weakest at 4.64. That shapes the plan: zero paid acquisition through week three, a $99 price one invoice-protecting PDF justifies, and a deliberate second revenue unit — extra site packs at $99, then renewal at month 12 — offered to every buyer instead of chasing a larger first cheque.
Positioning: for contractors who lose disputes they should win, ProofDay turns a one-line email reply into a dated PDF site log in under a minute.
2. Smallest sellable MVP
The MVP is one loop and one artifact: a contractor pays $99, gets a unique inbox address, replies to a daily prompt with text and photos, and downloads a branded PDF for any day or week from a magic-link portal. Everything else is out.
In: Postmark inbound webhook per customer address; photo ingestion with thumbnails; OpenAI structured extraction into job site, work completed, materials, delays and safety notes; React-PDF daily and weekly logs; Stripe Checkout and webhook; magic-link portal listing PDFs; daily prompt and weekly digest via Resend; an admin regenerate and resend button.
Out: mobile app, scheduling, dispatch, invoicing, accounting, team roles, SSO, handwriting OCR, hardware, client portal, two-way messaging, free tier.
Demo flow: the founder replies to a sample address — "Replaced 40A breaker at 118 Maple, customer added garage outlet, ran out of 12/2, back Thursday" — with two phone photos. The webhook stores the raw email, the model returns structured fields, the PDF renders with date, address, bullets, delays and thumbnails, the portal lists it, the contractor forwards it. Build time: four days.
3. Technical implementation plan
One Next.js app on Vercel, Supabase for auth, Postgres and storage, Postmark inbound, Resend outbound, OpenAI for extraction, React-PDF for rendering, Stripe for money. Inbound email is the risky edge, not the PDF.
Pipeline in plain language: Postmark posts the parsed email to a webhook that resolves the recipient address to a customer and site, uploads attachments to storage, strips quoted text, calls the model with a strict JSON schema, writes the entry row, then triggers a render. The PDF is generated server-side on demand, cached in storage, and linked from the portal and the weekly digest.
Build order is fixed: schema and address provisioning, inbound webhook, storage upload, extraction, PDF template, portal, Stripe, crons, admin. The hardest risk is messy inbound — forwarded chains, HTML-only clients, long signatures — polluting extraction. Mitigation: strip quoted content before the model call and always print the raw reply text in the PDF so the contractor can correct a wrong field with one regenerate. The model does exactly one job: free-text site notes into structured fields plus a two-sentence summary.
4. Pricing and monetization
One tier: Founding Contractor, $99 one-time, 12 months of archive access, up to three active job sites, daily prompt and weekly digest. No free tier and no trial in these 30 days — a free plan would destroy the only signal the contest needs, which is whether a contractor pays for a dated record.
Margin is effectively the full price. Serving cost is under $0.25 per customer per month for extraction and rendering at this volume, and hosting, domain and email sit inside single-digit dollars per month. The meaningful deduction is collection, assumed near 4% processing.
Second revenue unit at the same price point: after purchase, every buyer is offered an additional site pack at $99 when they exceed three concurrent jobs. Month 12 brings a renewal email. Every buyer is asked for one contractor peer intro the day after their first real PDF, which is the only compounding channel available to one person in 30 days.
5. First-customer acquisition
One channel: direct outreach in trade Facebook groups and subreddits. No ads until week four, no SEO, no partnerships, no marketplace.
Where: r/electricians, r/Plumbing, r/Contractor, r/handyman, r/Construction, plus Facebook groups for electrical contractors, plumbing businesses, handyman businesses, remodeling contractors and state-level contractor groups.
Method: search each community for "client won't pay", "chargeback", "warranty", "daily report", "get paid". Reply with one genuinely useful sentence about documentation, then the angle: "I can turn that job's texts into a dated PDF site log — want a free sample?" Build the sample from their public description, attach it, and put the Founding Contractor offer behind it at $99. Follow up once after 48 hours with three lines and the same PDF. Week-one goal: 120 named prospects, 60 direct messages, 5 sample PDFs delivered, at least 1 paid.
6. 30-day roadmap
Days 1-5 build to a frozen MVP: schema and inbound on day one, extraction plus PDF on day two, Stripe and portal on day three, prompt cadence and admin on day four, then three fake jobs end-to-end on day five. Days 6-7 ship the landing page, the live payment connection and a 120-name prospect list. Days 8-11 are pure outreach volume with sample PDFs. Day 12 targets the first $99 payment; days 13-14 onboard that buyer personally and ask for a referral. Days 15-21 convert sample recipients, fix the top friction point, and publish a public sample log used inside every message. Days 22-28 hold a 20-message daily rhythm while offering the site pack to existing buyers and tightening support with a self-serve help note. Days 29-30 publish buyer proof and reconcile payments, refunds and fees into a final profit number.
7. Revenue and profit scenarios
Every figure below is a projection from stated assumptions, not verified revenue, existing customers or real traction.
Conservative: 3 buyers × $99 = $297 collected; fees $12; hackathon profit $285; operating costs $25; business profit $260.
Base: 10 buyers × $99 = $990 collected; fees $39; hackathon profit $951; operating costs $45; business profit $906. This needs roughly 300 direct touches at about a 10% close rate — 20 messages a day for two weeks — which is work, not a guarantee.
Upside: 25 buyers × $99 = $2,475 collected; refunds $50; fees $97; ad spend $150; hackathon profit $2,178; operating costs $90; business profit $2,088. Upside requires community posts to travel and $150 of paid promotion in the final week.
8. Risks and validation experiments
Activation. A buyer who never sends a second log is a refund waiting to happen. Experiment: watch whether the first three buyers submit three or more logs inside seven days. If under 40% do, fix prompt timing before buying another customer.
Channel. Groups may delete promotional posts. Experiment: post a sample-only comment in three groups and check survival after one hour plus comment count. If three communities remove posts and 100 DMs produce no sample requests, the channel and possibly the concept need replacing.
Accuracy. Extraction may mangle ugly notes and embarrass the contractor. Experiment: run ten deliberately difficult replies through the pipeline. More than two materially wrong outputs after prompt fixes means the artifact is not client-safe.
Price. $99 may be wrong in either direction. Experiment: offer $99 to half of prospects and $149 to the other half and compare close speed; whichever wins sets the week-three price. Refunds above 10% of collected revenue stop one-time sales until a paid sample step exists.
9. First 24 hours
Hours 1-2: domain, repo, Postmark inbound verified. Hours 3-5: schema and address provisioning. Hours 6-8: webhook parsing and photo upload, proven with a real reply from a personal mailbox. Hours 9-11: extraction prompt tested on five hand-written messy notes. Hours 12-14: first branded PDF rendered from a stored entry. Hours 15-24: 30 contractor prospects logged and the DM template drafted. The day is done when one end-to-end PDF exists and 30 named humans have somewhere to receive a message.
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 →ReviewReady Packet
Generates a reviewer-ready Meta App Review submission bundle — per-permission justifications, screencast script, test-account steps and deauth code — for solo devs and small agencies stuck at 'rejected'.
Chargeback Brief
Chargeback Brief turns a Stripe or Shopify Payments dispute into a bank-ready evidence packet — cover letter, delivery timeline and exhibit index — in under ten minutes for Shopify stores that currently lose disputes by missing the response deadline.
Flowproof Audit
Paste in an n8n or Make workflow export and get a scored reliability report plus drop-in patch nodes that stop silent failures, duplicate runs and untyped AI outputs before a client notices.