Score C · 6.21/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 16, 2026

Candor Digest

Candor Digest turns anonymous cohort questions into a moderated, shareable Q&A digest for cohort-based course creators.

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.

Speculative6.21/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct DM on LinkedIn and X to creators who publicly posted a cohort launch in the last 14 days, with a sample digest attached.
Who pays

Solo or 1–5 person cohort-based course creators running paid cohorts on Maven, Podia or Teachable, English-speaking in US/UK/CA/AU, at cohort launch or mid-cohort when student questions stall.

Biggest execution risk

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.6/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

9 concrete actions. Tick them off as you go — nothing is saved or sent.

0/9
Entry price
$99
Solo build
5 days
30d base revenue
$1,188
30d hackathon profit
$1,041
Section 1 of 8

Product opportunity and positioning

Target customer

Solo or 1–5 person cohort-based course creators running paid cohorts on Maven, Podia or Teachable, English-speaking in US/UK/CA/AU, at cohort launch or mid-cohort when student questions stall.

Why now

Cohort-based courses are sold as high-ticket live programs where a single unanswered confusion point costs a renewal, and creators already buy small one-time tools per cohort without procurement.

Problem

Students stay silent in public cohort Slack to avoid asking a 'dumb' question, so the creator teaches past real confusion and loses renewals; open anonymous forms then flood them with spam, abuse and duplicates nobody has time to moderate.

Solution

A branded anonymous question link per cohort feeds a pipeline that flags abuse, clusters duplicates, lets the creator approve/reject/merge, and outputs a redacted Candid Cohort Digest as PDF plus markdown with themes, verbatim questions and suggested answer outlines.

Differentiation · Typeform and Google Forms hand back a raw unmoderated dump; Candor Digest returns an abuse-filtered, de-duplicated, redacted digest the creator can paste into the next live session.

Product opportunity and positioning

Candor Digest sells to one buyer: a solo or 1–5 person course studio running paid cohorts on Maven, Podia or Teachable. The trigger is concrete — a cohort has just launched, or is midway through, and student questions have stalled in the cohort Slack. Public channels suppress the "dumb" question, so the creator teaches past real confusion and loses renewals they never see coming.

Open anonymous forms solve the silence and create a second problem: spam, abuse, duplicate questions, and a raw export nobody has an hour to moderate before a live call. The creator is not short of a form; they are short of a synthesised artifact at the moment they need it.

The product is a branded anonymous question link per cohort. Students submit. The pipeline runs moderation, clusters duplicates by embedding similarity, the creator approves, merges or rejects in a queue, and the tool emits a redacted "Candid Cohort Digest" as PDF plus markdown: top themes, verbatim questions and suggested answer outlines. The creator pastes it into the next live session and shares it back to students, which closes the loop and makes the anonymous channel credible.

The wedge is the artifact, not the platform. No creator has to adopt a new system of record — they get one document that saves an hour of synthesis before a call that is already on the calendar. That is why $99 one-time is an easy yes and why the sale can close inside a direct message instead of a procurement cycle.

Against Typeform, Google Forms and the anonymous-question features inside Slack, the difference is the output: abuse-filtered, de-duplicated, redacted, themed, and formatted for a live session. Against building it themselves, the difference is five days they do not have.

Internal JEV scoring for this concept is 6.21 weighted (62.1/100, band C, confidence 0.71). Speed to first revenue is the strongest dimension (normalized 8.56); market demand (4.84), monetization (4.58) and operational simplicity (4.92) are the weakest. The 30-day plan is explicitly built to correct those three: narrow the buyer to the mid-cohort trigger rather than "course creators" broadly, add a repeat-purchase path through per-cohort repurchase and the $249 Studio Pack, and keep operations stateless on managed services with the creator's own moderation queue as the only human step.

The honest constraint is that this is a small-ticket tool with a manual acquisition motion. It wins on speed and specificity, not on scale. The 30 days are therefore optimised for verified profit from a handful of direct-message sales, not for a funnel.

Section 2 of 8

Smallest sellable MVP

A hosted anonymous question page per cohort, a creator moderation queue, and one-click export of a redacted, themed digest as PDF and markdown, sold at $99 via Stripe Checkout.

Must-have features

  • Magic-link login and a cohort creation dashboard
  • Public anonymous question page at a unique slug with cohort name and QR code
  • Submission form with optional name/email, honeypot and IP rate limiting
  • OpenAI moderation endpoint check on every submission
  • Embedding-based duplicate clustering with a merge suggestion
  • Moderation queue: approve, reject, merge
  • Digest generator: redacts emails and names, groups themes, outputs PDF and markdown
  • Stripe Checkout at $99 per cohort gated by access code
  • Resend emails for new submission and digest ready

Explicitly out of scope

  • Public feed, profiles or follower graph
  • Student accounts or direct messaging
  • Real-time chat or live polling
  • Teachable, Podia or Maven API integrations
  • Mobile app
  • Enterprise SSO or analytics suite
  • Human moderation service by the founder

Demo flow (what the buyer sees)

  1. Creator logs in with a magic link and creates a cohort named after their program
  2. Tool returns a public question URL and QR code the creator drops into Slack or the course page
  3. A student opens the link, types a question anonymously, and submits
  4. Moderation flags abuse and embeddings group near-duplicates into clusters
  5. Creator opens the queue and approves, merges or rejects each item
  6. Creator clicks Generate Digest and receives a redacted PDF plus markdown with themes, verbatim questions and answer outlines
  7. Creator pastes the digest into the next live session and shares it back
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres + Auth (magic link)OpenAI moderation endpointOpenAI embeddings (text-embedding-3-small)Stripe CheckoutResendReact-PDFVercel Cron for digest jobs

Architecture

Next.js App Router on Vercel serves three surfaces: authenticated creator dashboard, public anonymous question page, and Stripe webhook handler. Supabase Postgres holds cohorts, submissions, embeddings and digests; Supabase Auth issues magic links. On submit, the API route writes the row, calls OpenAI moderation, embeds the text and stores the vector. A clustering step compares the new vector to existing approved submissions for that cohort via cosine similarity and tags a suggested merge. The digest job runs on demand from the dashboard, batches approved items, prompts the model for themes and answer outlines, redacts PII with a regex pass before the model call, and renders React-PDF plus markdown to Supabase Storage. Stripe Checkout with an access code unlocks cohort creation beyond the demo limit; Resend sends both transactional emails.

Build steps

  1. Create Vercel project, Supabase project and Stripe test account; wire environment variables
  2. Define Postgres tables: cohorts, submissions, digests, purchases with row-level security
  3. Implement Supabase magic-link auth and the cohort creation form
  4. Build the public /q/[slug] page with branding, honeypot and per-IP rate limiting
  5. Add OpenAI moderation call and rejection path on submission
  6. Add embedding generation and cosine-similarity clustering with a suggested-merge field
  7. Build the moderation queue UI with approve, reject and merge actions
  8. Build the digest generator: redaction regex pass, theme prompt, React-PDF and markdown render
  9. Wire Stripe Checkout and webhook to unlock cohorts; add Resend notifications
  10. Deploy to production with custom domain, run a full end-to-end test with 20 fake submissions

AI components

  • OpenAI moderation endpoint to flag abuse, spam and harassment before the creator ever sees it
  • OpenAI embeddings to cluster duplicate and near-duplicate questions per cohort
  • LLM theme synthesis and suggested answer outlines inside the digest generator
Hardest technical risk: Redaction failing on a submission that contains a student's name or email inside free text, which would leak identity into a digest the creator forwards to the whole cohort.
Section 3 of 8

Pricing and monetization

Single Cohort

Entry offer
$99 one-time

For Solo course creator running one paid cohort

  • 1 cohort
  • Up to 100 submissions
  • Moderation queue
  • Redacted digest PDF + markdown

Studio Pack

$249 one-time

For Small course studio running multiple cohorts

  • 3 cohorts
  • Custom branding
  • Priority email support
  • Digest archive

Model: One-time per-cohort purchase with a multi-cohort studio pack; no subscription, no free trial.

First revenue offer: $99 Single Cohort: I set up your anonymous question link today and you get a moderated, redacted digest before your next live session — live in 10 minutes.

Expected ACV: $99

Upsell path: Every new cohort is a new $99 purchase; creators running back-to-back cohorts convert to the $249 Studio Pack, and satisfied buyers refer other creators in the same cohort platform community.

Target customers
45
Revenue model
$4,455
Costs
$180
Profit model
$4,275
Section 4 of 8

First-customer acquisition

Primary channel

Direct DM on LinkedIn and X to creators who publicly posted a cohort launch in the last 14 days, with a sample digest attached.

Where to find them

  • LinkedIn posts containing 'cohort 2 starts', 'Maven cohort' or 'new cohort' from the last 14 days
  • X posts announcing a paid cohort launch with a checkout link
  • Maven cohort discovery pages with recent launch dates
  • Teachable and Podia creator communities and public course landing pages
  • Creators who publicly ask for feedback on their cohort curriculum

Exact outreach motions

  • Search LinkedIn and X for last-14-day cohort launch posts and log 100 creators with name, cohort name and platform
  • Build a one-page sample digest for each target using only their public testimonials and course page copy, no invented data
  • Send DM 1 with the sample PDF attached and the $99 offer
  • Follow up once at 48 hours with a single question: 'Is student question overload a problem this cohort?'
  • On a yes, send the Stripe link and onboard with a 5-minute form (cohort name, dates, branding colour)

Message template

Hey {name} — saw {cohort} just opened. I built a sample Candid Cohort Digest from your public testimonials so you can see the format (attached, 1 page). It's the anonymous student questions you never get in Slack, moderated and de-duplicated into a digest you can paste into your next live call. $99 one-time per cohort, your question link is live in 10 minutes. Want me to set it up before your next session?
Week-one goal: 100 personalised DMs sent with a sample digest attached, 10 replies, 3 demo requests, 1 paid cohort.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1230 days planned
Week 1 · Build & validate · 7 days
Day 1Scope lock

Freeze the digest spec and build the target list

  • Write a one-page digest spec: themes, verbatim questions, answer outlines, redaction rules.
  • Create Vercel, Supabase, Stripe test and OpenAI accounts; set environment variables.
  • Log the first 30 target creators from recent LinkedIn and X cohort launch posts.

Deliverable: Digest spec doc, live dev environment, 30-creator target sheet.

Day 2Data model and auth

Cohorts and creator login

  • Create cohorts, submissions, digests and purchases tables with row-level security.
  • Implement Supabase magic-link auth and session handling.
  • Build the cohort creation dashboard form.

Deliverable: Creator can log in and create a cohort row.

Day 3Anonymous intake

Public question page

  • Build /q/[slug] page with cohort branding, question field and optional name/email.
  • Add honeypot field and per-IP rate limiting.
  • Generate a QR code and copy-link button for the creator.

Deliverable: Live public question page accepting submissions.

Day 4Moderation and clustering

Abuse filtering and duplicate merge

  • Call OpenAI moderation endpoint on every submission and auto-flag categories.
  • Generate embeddings and compute cosine similarity against existing cohort submissions.
  • Build the queue UI with approve, reject and merge actions.

Deliverable: Working moderation queue with suggested merges.

Day 5Digest and checkoutMVP shipped

End-to-end paid path

  • Build the redaction pass for emails and names, then the theme and outline prompt.
  • Render the digest as React-PDF and markdown to Supabase Storage.
  • Wire Stripe Checkout at $99 and the webhook that unlocks cohort creation.

Deliverable: Paid cohort produces a downloadable redacted digest. MVP complete.

Day 6Production hardening

Ship to a real domain

  • Add Resend emails for new submission and digest ready.
  • Deploy to production on a custom domain and run a 20-submission load test.
  • Write the landing page with the $99 offer and a Stripe buy button.

Deliverable: Live production product and public landing page.

Day 7Sample assets

Make the outreach attachment

  • Build 5 sample digests from target creators' public testimonials and course pages.
  • Write the DM script and the 48-hour follow-up.
  • Prepare the 5-minute onboarding form.

Deliverable: 5 sample digest PDFs and a ready outreach kit.

Week 2 · Launch & first sale · 7 days
Day 8Outreach batch 1

First 25 personalised DMs

  • Send 25 DMs on LinkedIn with the sample digest attached.
  • Log every send and reply in a sheet with date and status.
  • Post one build-in-public note on X about the digest format.

Deliverable: 25 DMs sent, tracker live.

Day 9Outreach batch 2

Another 25 DMs and first replies

  • Send 25 DMs to creators launching cohorts this week.
  • Reply to every inbound response within 2 hours.
  • Tune the message based on which lines get responses.

Deliverable: 50 total DMs, first replies logged.

Day 10Outreach batch 3

Volume plus follow-ups

  • Send 30 DMs and 48-hour follow-ups to non-responders.
  • Offer a 3-minute async demo video instead of a call.
  • Record the demo video against a live cohort.

Deliverable: 80 total DMs, demo video ready.

Day 11Follow-ups and demos

Convert interest to checkout

  • Send Stripe links to every positive reply.
  • Run two live 10-minute setup demos.
  • Ask one 'no' exactly why, and log the objection.

Deliverable: At least 3 Stripe links out, objection log started.

Day 12First sale pushFirst sale target

Close the first $99

  • Follow up on every open Stripe link.
  • Send 20 more DMs to fresh cohort launches.
  • Publish a short post showing the digest format with real redacted sample output.

Deliverable: First paying cohort or explicit reason it did not close.

Day 13First onboarding

Deliver the first digest

  • Onboard the first paying creator via the 5-minute form.
  • Watch the first live submission flow and fix any blocker immediately.
  • Ship the first delivered digest and ask for one sentence of feedback.

Deliverable: First customer live with a delivered digest.

Day 14Fix from feedback

Remove the top friction point

  • Fix the single biggest complaint from the first customer.
  • Add the top objection answer to the landing page.
  • Refresh the target list to 150 creators.

Deliverable: Shipped fix and updated landing page.

Week 3 · Repeat & systematize · 7 days
Day 15Proof and referral

Turn the first buyer into evidence

  • Ask the first customer for a one-line quote and a referral name.
  • Send 30 DMs referencing the delivered digest workflow, not the quote.
  • Add a 'what the digest contains' section with a redacted sample.

Deliverable: One written quote and 30 new DMs.

Day 16Digest quality pass

Make the output obviously better than a raw export

  • Improve theme naming and answer-outline quality on two real cohorts.
  • Add a per-question 'answer this live' checkbox to the digest.
  • Reduce digest generation to one click with progress state.

Deliverable: Improved digest template shipped.

Day 17Studio Pack

Add the repeat-purchase tier

  • Build the $249 Studio Pack checkout with 3 cohorts and custom branding.
  • Add a digest archive list view.
  • Email all buyers and repliers the Studio Pack option.

Deliverable: Studio Pack live and offered.

Day 18Outreach batch 4

40 DMs

  • Send 40 DMs with cohort-specific sample digests.
  • Follow up at 48 hours with one question.
  • Log reply rate per message variant.

Deliverable: 40 DMs sent, variant reply rates known.

Day 19Demos

Convert live

  • Run three 10-minute setup demos.
  • Send Stripe links within 30 minutes of each demo.
  • Capture the two most common objections verbatim.

Deliverable: Three demos run, links sent same day.

Day 20Public build note

Create a second inbound surface

  • Post a build-in-public thread on X showing the moderation queue and a redacted digest.
  • Reply to creators discussing anonymous feedback in cohort communities.
  • Add the thread link to the DM follow-up.

Deliverable: One public thread live.

Day 21Funnel review

Decide where to spend week four

  • Compute DM sent, reply rate, demo rate and paid rate from the tracker.
  • Cut the two worst message variants and keep the best.
  • Decide whether to raise DM volume or improve the demo.

Deliverable: Funnel numbers and a week-four decision.

Week 4 · Scale what works · 7 days
Day 22Referral-driven outreach

Use buyers as entry points

  • Ask every buyer for one creator name in their community.
  • Send 30 DMs to referred and adjacent creators.
  • Add a 'set up a second cohort' email to past buyers.

Deliverable: Referral asks sent, 30 DMs out.

Day 23Outreach batch 5

Volume with the best variant

  • Send 40 DMs using only the winning message variant.
  • Follow up on all week-three non-responders once.
  • Update the sample digest set for new launch targets.

Deliverable: 40 DMs sent, follow-ups complete.

Day 24Objection handling

Remove the top three 'no' reasons

  • Add a moderation-controls answer to the landing page.
  • Add a GDPR-safe wording note about anonymous submissions and consent.
  • Add a 60-second 'what happens to a submission' explainer.

Deliverable: Landing page updated with three objection answers.

Day 25Second cohort reuse

Prove repeat purchase

  • Email buyers with a second-cohort setup link.
  • Ship cohort duplication so a new cohort takes 30 seconds.
  • Ask buyers to run the digest for a second cohort at $99.

Deliverable: Duplicate-cohort feature shipped, repeat offer sent.

Day 26Outreach batch 6

Final volume push

  • Send 40 DMs to creators with cohorts starting within 14 days.
  • Run two demos same day.
  • Send Stripe links immediately after each positive reply.

Deliverable: 40 DMs, 2 demos, links out.

Day 27Conversion close

Chase every open thread

  • Message every warm lead with a deadline-neutral close: 'want the link live before your next session?'
  • Offer the Studio Pack upgrade to any buyer running two or more cohorts.
  • Fix any checkout drop-off found in Stripe logs.

Deliverable: All warm leads contacted, checkout issues resolved.

Day 28Proof pack

Consolidate delivered work

  • Collect redacted delivered digests into a single sample pack.
  • Write a one-page 'how it works' for future outreach.
  • Reconcile revenue in Stripe against the TrustMRR-connected account.

Deliverable: Sample pack, how-it-works page, revenue reconciled.

Days 29-30 · Consolidate · 2 days
Day 29Final outreach

Last push on warm pipeline

  • Send 30 final DMs to creators launching in the next two weeks.
  • Follow up on every demo that did not convert.
  • Verify no pre-launch payments exist in the payment account.

Deliverable: 30 DMs sent, payment account audited.

Day 30Close and verify

Lock the numbers

  • Confirm all payments landed inside the contest window.
  • Export the Stripe transaction list and match it to cohorts delivered.
  • Publish a short launch recap with verified figures only.

Deliverable: Verified revenue statement and launch recap.

Section 6 of 8

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

  • Conservative: 100 personalised DMs produce a 4% reply rate and one closed sale per 25 DMs; Base assumes the message variant improves to one sale per 9 DMs.
  • Base: ARPU stays at $99 because the Studio Pack upgrade is not assumed in the base case.
  • Upside: assumes 30 paid cohorts, driven by repeat purchases from the same buyers and a small number of $249 Studio Pack upgrades folded into ARPU.
  • Payment processing assumed at Stripe standard rates (2.9% + $0.30), rounded to roughly 4% blended for international cards.
  • Refunds assumed at 0 in conservative, 1 unit in base, 2 units in upside, reflecting creators who buy before a cohort date changes.
  • Chargebacks assumed at 0 across all scenarios given low-ticket, DM-originated sales with a live setup conversation.
  • Ad spend assumed at $0 for conservative and base because the channel is organic DMs; upside includes $150 of sponsored community posts.
  • Operating costs cover Vercel, Supabase, domain, Resend and OpenAI moderation plus embeddings, estimated under $0.50 per cohort.
  • No founder salary, no contractor cost and no paid support is assumed.
  • Every figure is a projection from stated assumptions, not verified revenue or existing traction.

Conservative

4 customers
$396
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$16
Paid marketing
$0
Hackathon profit
$380
Operating costs
$30
Business profit
$350

Base case

12 customers
$1,188
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$48
Paid marketing
$0
Hackathon profit
$1,041
Operating costs
$60
Business profit
$981

Optimistic

30 customers
$2,970
collected revenue · avg payment $99
Refunds
$198
Chargebacks
$0
Payment fees
$119
Paid marketing
$150
Hackathon profit
$2,503
Operating costs
$140
Business profit
$2,363

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,188
Payment fees (3.9%)
$46
Paid marketing
$0
Hackathon profit
$1,142
Business profit
$1,082

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 built from the stated assumptions. They are not verified revenue, existing customers or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Creators treat it as a survey tool and compare it to Typeform or Google Forms at $99.

Mitigation

Lead every message with the digest artifact and moderation queue, never with 'anonymous form'; show a redacted sample in the first touch.

Validation experiment

Send two DM variants to 20 creators each: one leading with 'anonymous question link', one leading with 'moderated digest you can paste into your next call'. Compare reply rates over 5 days.

Kill criteria

If the artifact-led variant replies at under 2% across 40 DMs, the buyer does not value the digest and the positioning needs rework before more spend.

Risk 2Anonymous submissions still contain abuse or PII that survives redaction and lands in a digest the creator forwards.

Mitigation

Moderation endpoint blocks harassment categories before the queue, a regex redaction pass runs before any model call, and the creator approves every line that ships.

Validation experiment

Seed a test cohort with 30 adversarial submissions including emails, phone numbers and insults; measure how many reach the digest unredacted.

Kill criteria

Any unredacted email or name surviving into a generated digest on the adversarial test is a stop-ship bug until fixed.

Risk 3LinkedIn and X flag the DM volume as spam and the account is restricted.

Mitigation

Cap at 25–40 DMs per day, personalise every message with a real cohort name and sample, and spread volume across LinkedIn and X.

Validation experiment

Send 25 DMs per day for three days and track any warning banners, connection limits or message-delivery drops.

Kill criteria

Two platform warnings in one week means the channel is closed; shift to creator communities and warm intros only.

Risk 4At $99 the acquisition time is not covered and total profit stays in single digits.

Mitigation

Push the $249 Studio Pack and second-cohort repeat purchases to raise ARPU without new acquisition, and keep operating cost under $150 for the month.

Validation experiment

Offer the Studio Pack to every replier and measure upgrade rate over 7 days.

Kill criteria

If no buyer upgrades and repeat-cohort purchases are zero by day 25, the price architecture is wrong for the channel economics.

Risk 5Maven, Podia or Teachable ship native anonymous Q&A and remove the need.

Mitigation

Compete on the digest and redaction output, which a platform Q&A inbox does not produce, and keep setup under 10 minutes.

Validation experiment

Ask five creators directly whether their platform already collects anonymous questions and what they do with the raw list.

Kill criteria

If three of five say they already get anonymous questions and read them without pain, the wedge is too thin to sell.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Write the one-page digest spec covering themes, verbatim questions, answer outlines and redaction rules
  • List the three surfaces that must exist: creator dashboard, public question page, digest export

Output: Digest spec document and a one-page build scope.

Hours 3-5

  • Create the Vercel project, Supabase project, Stripe account and OpenAI API key
  • Store all secrets as environment variables and confirm a hello-world deploy

Output: Live deployment URL and a working local dev environment.

Hours 6-8

  • Define the cohorts, submissions, digests and purchases tables with row-level security
  • Wire Supabase magic-link auth and a protected dashboard route

Output: Database schema applied and creator login working.

Hours 9-12

  • Search LinkedIn and X for cohort launch posts from the last 14 days
  • Log 30 creators with name, cohort, platform and profile URL
  • Draft the DM and the 48-hour follow-up

Output: 30-creator target sheet and final DM copy ready to send on day 8.

Complete report

Full 30-day launch report

Read the full generated report

Candor Digest — 30-Day Public Report (concept v1)

1. Product opportunity and positioning

Candor Digest sells to one buyer: a solo or 1–5 person course studio running paid cohorts on Maven, Podia or Teachable. The trigger is concrete — a cohort just launched or is midway through, and student questions have stalled in the cohort Slack. Public channels suppress the dumb question, so the creator teaches past real confusion and loses renewals they never see.

Open anonymous forms solve the silence and create a second problem: spam, abuse, duplicates, and a raw export nobody has an hour to moderate before a live call. The creator is not short of a form; they are short of a synthesised artifact at the moment they need it.

The product is a branded anonymous question link per cohort. Students submit; the pipeline runs moderation, clusters duplicates by embedding similarity, the creator approves or merges in a queue, and the tool emits a redacted Candid Cohort Digest as PDF plus markdown with themes, verbatim questions and suggested answer outlines. The creator pastes it into the next live session and shares it back.

The wedge is the artifact, not the platform. No creator adopts a new system of record — they get one document that saves an hour before a call already on the calendar. That is why $99 one-time is an easy yes and why the sale closes in a DM rather than a procurement cycle. Against Typeform and Google Forms, the difference is abuse filtering, de-duplication, redaction and formatting. Against building it themselves, the difference is five days they do not have.

Internal JEV scoring is 6.21 weighted (62.1/100, band C). Speed to first revenue is the strongest dimension; market demand, monetization and operational simplicity are the weakest. The plan corrects those three by narrowing the buyer to the mid-cohort trigger, adding repeat purchase through per-cohort rebuys and the $249 Studio Pack, and keeping operations stateless on managed services with the creator's own queue as the only human step.

2. Smallest sellable MVP

A hosted anonymous question page per cohort, a moderation queue, and a one-click redacted digest export as PDF and markdown, sold at $99 through Stripe Checkout. Nine must-have features: magic-link auth, cohort dashboard, public question page with QR code, submission form with honeypot and rate limiting, OpenAI moderation, embedding clustering, approve/reject/merge queue, digest generator with redaction, and Stripe gated by access code. Explicitly not built: public feed, student accounts, chat, platform APIs, mobile app, SSO, or founder-run moderation. Build time is five days, and the demo runs in seven steps from magic link to a digest pasted into a live call.

3. Technical implementation plan

Next.js on Vercel with Supabase Postgres and magic-link auth, OpenAI moderation and embeddings, Stripe Checkout, Resend and React-PDF. On submit, the API route writes the row, calls moderation, embeds the text and stores the vector. Clustering compares that vector to existing approved submissions and tags a suggested merge. The digest job runs on demand, batches approved items, redacts PII with a regex pass before any model call, prompts for themes and answer outlines, and renders PDF plus markdown to storage. The hardest risk is redaction failing on free text and leaking a student's name into a forwarded digest.

4. Pricing and monetization

Two tiers, both one-time, no trial. Single Cohort at $99 covers one cohort, up to 100 submissions, the moderation queue and the digest. Studio Pack at $249 covers three cohorts, custom branding, priority email support and a digest archive. Every new cohort is a fresh $99 purchase, which is the repeat path. The upsell is the Studio Pack for anyone running back-to-back programs, plus referrals inside the same creator communities.

5. First-customer acquisition

One channel: direct DMs on LinkedIn and X to creators who posted a cohort launch in the last 14 days. The motion is to build a one-page sample digest from that creator's public testimonials and course page, attach it to the first message, and offer the $99 setup in ten minutes. Week-one goal: 100 personalised DMs, 10 replies, 3 demo requests, 1 paid cohort. Follow up once at 48 hours with a single question about question overload. No paid ads in the conservative or base case.

6. 30-day execution roadmap

Days 1–5 build: spec, schema and auth, public question page, moderation and clustering, then digest generation plus Stripe. Day 5 is the MVP deadline. Day 6 ships to production with Resend and a landing page. Day 7 builds five sample digests and the outreach kit. Days 8–11 send 80 DMs with follow-ups and a demo video. Day 12 is the first-sale target. Day 13 onboards the first paying creator and delivers a digest. Day 14 ships the top fix. Days 15–21 add proof, improve digest quality, launch the Studio Pack, send 40 DMs, run demos, post a public build thread and review the funnel. Days 22–28 push referrals, send three more DM batches, answer objections on the landing page, ship cohort duplication for repeat purchase and reconcile Stripe against the TrustMRR-connected account. Days 29–30 close the warm pipeline and verify every payment landed inside the contest window.

7. Revenue and profit scenarios (projections only)

Three projections, all hypothesis. Conservative: 4 cohorts at $99 = $396 gross, $0 refunds, $0 chargebacks, $16 fees, $0 ad spend, $30 operating cost. Base: 12 cohorts = $1,188 gross, $99 refunds, $48 fees, $0 ad spend, $60 operating cost. Upside: 30 cohorts = $2,970 gross, $198 refunds, $119 fees, $150 ad spend, $140 operating cost. Hackathon profit is gross revenue minus refunds, chargebacks, payment fees and ad spend; business profit also subtracts operating cost. The gap between conservative and upside is almost entirely DM reply rate and repeat purchases, not product scope.

8. Main risks and validation experiments

The five tracked risks are survey-tool comparison, PII leaking through redaction, DM channel restrictions, $99 not covering acquisition time, and platform-native Q&A. Each has a week-one test and a kill criterion. The redaction test is stop-ship: seed 30 adversarial submissions with emails, phone numbers and insults, and any surviving identity string blocks the launch until fixed. The positioning test compares an artifact-led DM against a form-led DM to 20 creators each and kills the form-led angle below 2% reply. The platform test asks five creators whether their LMS already collects anonymous questions and whether they read the raw list.

9. First 24-hour action plan

Hours 1–2: write the digest spec and freeze scope. Hours 3–5: create Vercel, Supabase, Stripe and OpenAI projects and confirm a deploy. Hours 6–8: apply the database schema and get magic-link auth working. Hours 9–12: log 30 recent cohort-launch creators and finalise the DM and follow-up copy. The day ends with a deployable skeleton, a schema, and a ready target list — the three inputs the five-day build depends on.

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 →