FlowQuote Cost Compiler
Turns an n8n or Make workflow export into a client-ready cost quote — per-node token estimates, cost per 1,000 runs, monthly projection and agency margin — so automation freelancers can price AI builds without guessing.
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.
The solo automation freelancer or 2-15 person agency selling n8n/Make builds to SMB clients, specifically the person who writes the proposal.
Market demand 4.5/10
Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 9; 35 sales at $29 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.9/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
18 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
The solo automation freelancer or 2-15 person agency selling n8n/Make builds to SMB clients, specifically the person who writes the proposal.
Why now
LLM and agent nodes are now standard in freelance automation builds, so every proposal carries an unbudgeted monthly API cost the client will challenge in month two.
Problem
There is no per-run cost visibility in n8n or Make, so freelancers guess the client's monthly AI spend, rebuild the math in a spreadsheet and throw it away after one proposal.
Solution
Upload the workflow JSON, get a Costed Workflow Sheet: per-node token bands, cost per run and per 1,000 runs, monthly projection at the client's volume, agency margin, branded PDF plus read-only share link, and a patched JSON with the estimate in sticky notes.
FlowQuote Cost Compiler - Product opportunity and positioning
FlowQuote Cost Compiler turns an n8n workflow export into a client-ready cost quote. Right now a freelance automation builder pricing an AI build has two options: ship it and watch the bill, or rebuild the math node by node in a spreadsheet that gets thrown away after one proposal. Neither n8n nor Make shows tokens or dollars in the execution log - you see runs, not cost.
The buyer is deliberately narrow: the solo freelancer or 2-15 person agency selling n8n/Make builds to SMB clients, specifically the person who writes the proposal. The trigger event is a new build containing an LLM or agent node, or a client pushing back on a monthly API bill. Geography skews US/EU/India; the buyer is reachable in the n8n community forum, r/n8n, Upwork and LinkedIn posts showing workflow screenshots.
The product sells a document, not infrastructure. There is no proxy, no SDK, no traffic in the request path. That has two consequences: the buyer can evaluate it in one upload without an integration trial, and the founder can produce the first free output this week from any publicly shared workflow JSON with no audience and no ad budget.
JEV scored this concept 61.0/100, band C. The weak criteria are market demand (4.54) and monetization potential (4.79); the strong ones are speed to first revenue (7.92) and reachable customers (7.40). The 30 days below are shaped by that: reach a paid document fast, then answer the monetization weakness with repeat quotes and a monthly agency tier instead of pretending one $29 sale is a business.
Versus a free spreadsheet template: the compiler rebuilds the node graph, isolates AI nodes, extracts prompt text and model parameters, and writes the estimate back into the workflow JSON as sticky notes - the build ships with its own cost documentation.
What is not being built
No runtime proxy, no traffic interception, no shadow testing, no quality scoring, no automatic model-swap advice. Those belong to a different buyer (a lead engineer running production inference) with a different buying process. This buyer is buying proposal accuracy, which is a document problem.
The commercial wedge
A $29-$99 one-time purchase is a rounding error against a single lost client for a freelancer whose income depends on proposal accuracy. The deliverable is auditable in 60 seconds, needs no procurement, and the founder can create the first ten units of marketing output from public template JSON before writing a single line of sales copy.
Smallest sellable MVP
A one-page app: upload an n8n workflow JSON, receive a branded PDF and read-only share link with per-node token bands, cost per run, cost per 1,000 runs, monthly projection and an agency margin line, paid by Stripe Checkout before download.
Must-have features
- n8n workflow JSON importer that reconstructs the node graph and isolates LLM/agent/model nodes
- Explicit unsupported-node list shown to the user instead of silently skipping nodes
- Prompt and model resolver: extracts system/user prompt text and the model parameter per AI node
- Token band estimator producing low/base/high input and output token counts per AI node
- Hand-maintained model price table keyed by model ID, dated in the repo
- Run-count model control (linear, per-item loop, per-branch) with a branch multiplier
- Costed Workflow Sheet: branded PDF plus read-only share link with per-node table and monthly projection
- Agency price and margin line on the sheet
- Patched workflow JSON export that writes the estimate into node notes or sticky notes
- Stripe Checkout connected to TrustMRR, gating the sheet behind one quote credit
Explicitly out of scope
- Runtime proxy, SDK wrapper or any traffic interception
- Shadow testing, LLM-as-a-judge quality scoring, automatic model-swap recommendations
- Zapier support (no reliable full workflow export)
- Live provider billing API connections or OAuth into customer cloud accounts
- Team collaboration, roles or approval workflows
- Any claim of exactness - every sheet is labelled as an estimate range
- Make-specific parser beyond a clear unsupported warning
Demo flow (what the buyer sees)
- User uploads an exported n8n workflow JSON
- Importer rebuilds the graph and flags unreadable nodes
- Classifier isolates AI nodes and extracts prompt text plus model ID
- Estimator produces low/base/high token bands per node
- User sets run volume and picks a run-count model
- Price table converts tokens to cost per run, per 1,000 runs and monthly at volume
- User enters an agency price; margin line is computed
- Stripe Checkout is completed and the credit is released
- User downloads the branded PDF, shares the read-only link, exports the patched JSON
Technical implementation plan
Stack
Architecture
The browser uploads the workflow JSON to a Next.js route handler, which stores it in Supabase and hands the AI-node candidates to a single structured-output LLM call. The response is validated against a schema; unsupported nodes are surfaced rather than dropped. The cost engine is pure TypeScript: token bands times the price table times the run-count model. The sheet is rendered server-side as a react-pdf document and as an HTML share page behind an unguessable token. Stripe Checkout writes a credit row into Supabase via webhook, and only then does the download and share link unlock. The patched JSON is generated by mutating the original export and adding sticky notes next to each AI node.
Build steps
- Scaffold the Next.js app, deploy to Vercel, create Supabase tables for quotes, credits and share links
- Write the n8n parser that reconstructs nodes and connections from the export
- Build the AI-node classifier with a structured-output schema and an unsupported-node list
- Extract prompt text and model parameters per AI node and store them on the quote row
- Implement the token band estimator and validate it against one hand-checked workflow
- Author the model price table JSON and the per-run / per-1,000-run / monthly math with unit tests
- Add the run-count model control (linear, per-item loop, per-branch) with branch multipliers
- Render the quote page with the per-node table and cost bands
- Generate the branded PDF with react-pdf and the read-only share page with an unguessable token
- Wire Stripe Checkout to TrustMRR and gate the download behind a credit row
- Generate the patched JSON with sticky notes and expose it as an export
- Run 10 real workflows end to end, calibrate token bands, and ship v1
AI components
- One structured-output LLM call per workflow to classify nodes and extract prompt text and model IDs
- No LLM in the cost math - the arithmetic is deterministic TypeScript so numbers are reproducible
Pricing and monetization
Single Quote
Entry offerFor Freelancer pricing one workflow for one proposal
- One Costed Workflow Sheet PDF
- Read-only client share link
- Per-node token band and per-1,000-run cost
- Patched workflow JSON with cost annotations
Proposal Pack
For Agency or freelancer sending several proposals a month
- Five workflow quotes
- Agency logo and branding on the PDF
- Agency price and margin calculator line
- Saved client workspace and quote history
Agency Monthly
For Small agency quoting constantly across clients
- Unlimited quotes
- Model price table updates
- Multiple saved client workspaces
- Priority re-run when a workflow is revised
Model: One-time quote credits with a $99 multi-quote pack as the planning price, plus a $199 monthly agency plan for constant quoters.
First revenue offer: A free Costed Workflow Sheet for one of their own publicly shared workflows, delivered in a DM, with the paid Proposal Pack offered only after they reply.
Expected ACV: $99
Upsell path: Single Quote buyers are emailed the Proposal Pack upgrade within 48 hours of delivery; pack buyers are offered Agency Monthly when they request a sixth quote; monthly buyers get a price-table update notification each time the table changes.
First-customer acquisition
Public workflow teardowns: compile publicly shared n8n template JSON and publish 'what this template actually costs per 1,000 runs' with the free sheet attached, then DM the people who reply.
Where to find them
- n8n community forum threads asking about running costs
- r/n8n posts containing workflow screenshots
- n8n Discord cost and billing channels
- r/automation and r/nocode threads about client pricing
- Upwork automation freelancers with n8n or Make in their profile
- LinkedIn posts and profiles matching n8n plus agency
Exact outreach motions
- Publish a free teardown of a popular community template with the per-1,000-run number in the title
- Reply in cost threads with the actual number for the workflow being discussed, sheet linked
- DM every builder who posted a workflow screenshot: offer one free compile of their own export, no signup
- DM 20 Upwork freelancers with a costed example of the workflow type they advertise
- Ask each paying customer to name one other freelancer who quotes AI builds
- Post one teardown per week to the same channels to keep the free-sheet supply alive
Message template
Saw your workflow post - the LLM nodes in it run about $X per 1,000 executions and roughly $Y/month at 40 runs a day, assuming gpt-4o-mini on the summarise step. I built a compiler that reads the n8n JSON and writes that sheet with a per-node breakdown. Want me to run yours free? One export, no signup, sheet back today.
30-day execution roadmap
Week 1 · Build & validate · 7 days
App skeleton and a real workflow corpus
- Scaffold Next.js on Vercel and create Supabase tables for quotes and credits.
- Download 10 publicly shared n8n template JSONs into a fixtures folder.
- Write the parser that reconstructs nodes and connections.
Deliverable: Deployed skeleton plus a 10-workflow fixtures folder.
Find and describe AI nodes
- Build the AI-node classifier with a structured-output schema.
- Extract prompt text and model parameters per node.
- Surface an unsupported-node list instead of skipping silently.
Deliverable: Classification output for all 10 fixtures.
Tokens to dollars
- Implement the low/base/high token band estimator.
- Author the model price table JSON keyed by model ID.
- Unit-test per-run, per-1,000-run and monthly math.
Deliverable: Cost engine with passing unit tests.
The thing the buyer pays for
- Render the quote page with the per-node table.
- Generate the branded PDF and read-only share link.
- Export patched JSON with the estimate in sticky notes.
Deliverable: Full Costed Workflow Sheet generated end to end.
Payments and v1 launch
- Wire Stripe Checkout to TrustMRR and gate the sheet behind a credit.
- Run all 10 fixtures and calibrate token bands.
- Deploy v1 and record a 3-minute demo.
Deliverable: Live v1 that can take a payment.
First public output
- Publish 3 free Costed Workflow Sheets on the n8n forum.
- Cross-post one to r/n8n.
- Reply to every comment the same day.
Deliverable: 3 public teardowns live.
First 25 DMs
- DM 25 freelancers who posted workflow screenshots or cost questions.
- Offer one free compile, no signup, in each message.
- Log every reply in a spreadsheet with source thread.
Deliverable: 25 DMs sent and a reply log started.
Week 2 · Launch & first sale · 7 days
More free sheets, more surfaces
- Publish 3 more teardowns.
- Post a LinkedIn breakdown with the per-1,000-run number in the first line.
- Answer cost questions in the n8n Discord.
Deliverable: 6 teardowns total and 2 channel posts.
Convert the warmest repliers
- Send the checkout link to the 10 warmest repliers with their own quote attached.
- Offer to cost their live workflow in a 60-second screen recording.
- Follow up once after 24 hours.
Deliverable: First paid quote or a written objection list.
Fix the top confusion
- Run 3 fifteen-minute interviews with free-sheet users.
- Ship a fix for the most confusing step in the run-count control.
- Polish the patched-JSON export so it opens cleanly.
Deliverable: 3 interviews and one shipped fix.
The $99 tier
- Ship logo upload, margin line and 5 credits.
- Add a saved client workspace per buyer.
- Add an upgrade path from the single-quote page.
Deliverable: Proposal Pack purchasable.
Beyond the n8n forum
- Publish teardowns 7 to 9.
- Post the sheet format to r/automation and one Discord.
- DM 20 Upwork automation freelancers.
Deliverable: 9 teardowns and 20 Upwork DMs.
Second touch on every lead
- Re-contact every non-buyer with the $29 Single Quote.
- Send a free sheet of their own workflow to anyone who replied.
- Update the reply log with objections.
Deliverable: Second touch sent to all warm leads.
Kill the weakest channel
- Compute revenue, refunds and close rate by channel.
- Cut the channel with no replies or no purchases.
- Publish one teardown as a permanent post.
Deliverable: Channel scorecard and one public post.
Week 3 · Repeat & systematize · 7 days
Recurring revenue
- Ship Agency Monthly at $199 with unlimited quotes.
- Add a dated model price table update note.
- Refresh the price table from public provider pricing pages.
Deliverable: Monthly tier live and price table dated.
2-15 person shops
- DM 15 LinkedIn founders matching n8n plus agency.
- Offer to cost two of their live client workflows free.
- Pitch the Proposal Pack to anyone who replies.
Deliverable: 15 agency DMs sent.
Comparison post
- Publish a side-by-side cost of two popular community templates.
- Post it to the n8n forum and X.
- Link the free sheet in the first reply.
Deliverable: Comparison post live.
Get names
- Email every buyer asking for one other freelancer name.
- Add a two-line referral ask to the delivery email.
- Offer one free extra quote per referral.
Deliverable: Referral ask sent and names captured.
Answer the top five
- List the five most common objections from the reply log.
- Answer each in an FAQ block on the pricing page.
- Put the estimate-range disclaimer in the PDF footer.
Deliverable: FAQ page and updated PDF footer.
Post-purchase sequence
- Write a 3-email sequence: upload, share link, margin line.
- Trigger it after purchase.
- Test the whole flow with one live transaction.
Deliverable: Sequence live and one real transaction tested.
Numbers, not vibes
- Compare actuals against the base scenario.
- Resolve any refund request the same day.
- Raise or cut the Single Quote price based on close rate.
Deliverable: Mid-point numbers memo.
Week 4 · Scale what works · 7 days
Fix what users actually hit
- Fix every unsupported node reported by users.
- Add clear warnings for Make-style exports.
- Add regression tests over 20 stored workflows.
Deliverable: Importer v1.1 with warnings.
Teardown cadence
- Publish 5 new teardowns, one per day.
- DM 30 new freelancers from fresh threads.
- Reply to every open cost thread.
Deliverable: 14 teardowns total and 30 DMs.
The line agencies want
- Add agency price and margin inputs with a suggested band.
- Show margin percentage on the PDF.
- Gate margin overrides to paid tiers.
Deliverable: Margin line shipped.
Raise order value
- Email single-quote buyers a Proposal Pack plus one month Agency bundle.
- Cap the offer at 24 hours.
- Track take-up in the reply log.
Deliverable: Upgrade offer sent to all single-quote buyers.
Real buyers only
- Ask two paying customers for a one-line quote with permission.
- Add approved quotes to the pricing page.
- Never publish a sheet that was not generated for a real buyer.
Deliverable: Two approved quotes on the site.
Largest outreach day
- DM 50 freelancers with a costed example of their own public workflow.
- Reply in every thread mentioning n8n cost.
- Publish teardown 15.
Deliverable: 50 DMs and one post.
Payment integrity
- Verify every payment landed in TrustMRR.
- Reconcile refunds, chargebacks and Stripe fees.
- Confirm no payment predates launch.
Deliverable: Reconciliation sheet.
Days 29-30 · Consolidate · 2 days
Convert the backlog
- Email all warm leads a final reminder with the $29 entry offer.
- Publish the last teardown.
- Ask buyers to forward the sheet to one peer.
Deliverable: Final reminder sent to every lead.
Report real numbers
- Freeze the product and export the profit figures.
- File the hackathon submission.
- Publish a launch recap using only verified numbers.
Deliverable: Submission filed and recap published.
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
- Blended ARPU is a mix of $29 Single Quotes, $99 Proposal Packs and $199 Agency Monthly plans; the mix differs per scenario and is a hypothesis, not observed (applies to all).
- Payment processing is modelled at about 4% of collected revenue, assuming Stripe card fees of 2.9% plus $0.30 and a share of cross-border cards (applies to all).
- LLM extraction cost is below $0.30 per workflow, so every tier covers its own delivery cost (applies to all).
- Operating cost covers Vercel, Supabase, the domain, tooling and inference for both paid and free teardown sheets (applies to all).
- Conservative: 6 closed customers, mostly $29 single quotes, no paid promotion, no refunds.
- Base: 22 closed customers on a $86 blended ARPU, one refund, no paid promotion.
- Upside: 55 closed customers on a $97 blended ARPU, two refunds and $250 of paid promotion late in the window.
- No chargebacks are modelled in any scenario; a single chargeback would remove roughly one to two sales from hackathon profit.
- Paid marketing is zero in Conservative and Base because the acquisition channel is organic outreach and public teardowns.
- These are projections built from the stated assumptions, not verified revenue or existing customers.
Conservative
6 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $18
- Paid marketing
- $0
- Hackathon profit
- $426
- Operating costs
- $35
- Business profit
- $391
Base case
22 customers- Refunds
- $86
- Chargebacks
- $0
- Payment fees
- $76
- Paid marketing
- $0
- Hackathon profit
- $1,730
- Operating costs
- $60
- Business profit
- $1,670
Optimistic
55 customers- Refunds
- $194
- Chargebacks
- $0
- Payment fees
- $213
- Paid marketing
- $250
- Hackathon profit
- $4,678
- Operating costs
- $140
- Business profit
- $4,538
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $638
- Payment fees (3.9%)
- $25
- Paid marketing
- $0
- Hackathon profit
- $613
- Business profit
- $553
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 three scenarios are projections derived from the stated assumptions. They are not verified revenue, existing customers or real traction.
Main risks and validation experiments
Risk 1Static token estimates land far enough off that quotes mislead clients, producing refunds and word-of-mouth damage.
Every sheet carries low/base/high bands and an explicit estimate label; sell the range, never a single number, and never call the output a bill.
Cost 10 real workflows whose owners will share their actual billed spend for the same period, and measure the error distribution.
If median error across 10 workflows exceeds 2x, stop selling and move to a human-assisted review flow before taking another payment.
Risk 2n8n and Make JSON schemas change and break the importer, which is the load-bearing component.
Pinned parser, 20 stored fixtures with a regression test, and a visible unsupported-node list so a bad parse is obvious to the user.
Run the parser against 20 publicly shared exports and count how many complete without manual intervention.
If fewer than 60% of public exports parse cleanly, pause outreach and fix the parser before pushing teardown volume.
Risk 3One-time purchase with weak repeat intent: buyers copy the sheet format once and never return.
Credits that expire, the margin calculator and branding locked to paid tiers, and a monthly agency plan with price-table updates as the retention hook.
Ask every buyer at delivery how many client quotes they expect to send in the next quarter, and record the answer.
If fewer than 20% of buyers say two or more, stop investing in the low tier and restructure toward the monthly plan.
Risk 4Teardown posts and cold DMs read as spam and breach community or forum rules.
Publish value-first sheets with the number in the title, follow each community's self-promotion rules, and DM only people who asked a cost question or posted a workflow.
Send 25 DMs and track reply rate plus any moderator warnings across the first week.
If 25 DMs return zero replies or one moderator warning, stop cold DM and move entirely to reply-driven conversations.
Risk 5The buyer refuses to pay for a document at all and expects a free spreadsheet template instead.
Lead with the free sheet, sell only the branded deliverable and patched JSON, and anchor the price against one lost client rather than against a template.
A/B the Single Quote page at $29 and $49 across the first 200 qualified teardown viewers and record purchase or objection.
If 200 qualified viewers produce zero purchases and objections are all price-based, drop to a $19 entry or change the paid artifact.
Hour-by-hour: the first 24 hours
Hours 1-2
- Scaffold the Next.js app and deploy to Vercel.
- Create Supabase tables for quotes, credits and share links.
- Confirm Stripe is connected to TrustMRR and no live payment can be taken yet.
Output: Deployed skeleton with an empty database and a verified payment setup.
Hours 3-5
- Collect 10 publicly shared n8n workflow JSONs into a fixtures folder.
- Write the parser that reconstructs nodes and connections.
- Print the parsed graph for one fixture as a sanity check.
Output: Fixtures folder plus a working node graph parser.
Hours 6-9
- Build the AI-node classifier with a structured-output schema.
- Add the unsupported-node list to the output.
- Run the classifier over all 10 fixtures and record failures.
Output: Classification results for 10 real workflows with a failure list.
Hours 10-14
- Implement the low/base/high token band estimator.
- Author the model price table JSON from public provider pricing pages.
- Unit-test per-run, per-1,000-run and monthly math against one hand-computed workflow.
Output: Cost engine with unit tests and a dated price table file.
Hours 15-18
- Render a first quote page with the per-node table.
- Generate a PDF from one fixture.
- Hand-check every number on the sheet.
Output: One generated Costed Workflow Sheet, numbers verified by hand.
Hours 19-24
- Draft the first public teardown post.
- Build a list of 25 freelancers with a source thread and a reason to message each.
- Stage the DMs to send the moment checkout is live.
Output: Teardown draft plus a 25-row outreach list ready to send.
Full 30-day launch report
Read the full generated report
FlowQuote Cost Compiler - 30-Day Public Report
1. Product opportunity and positioning
FlowQuote Cost Compiler turns an n8n workflow export into a client-ready cost quote. Right now a freelance automation builder pricing an AI build has two options: ship it and watch the bill, or rebuild the math node by node in a spreadsheet that gets thrown away after one proposal. Neither n8n nor Make shows tokens or dollars in the execution log - you see runs, not cost.
The buyer is deliberately narrow: the solo freelancer or 2-15 person agency selling n8n/Make builds to SMB clients, specifically the person who writes the proposal. The trigger event is a new build containing an LLM or agent node, or a client pushing back on a monthly API bill. Geography skews US/EU/India; the buyer is reachable in the n8n community forum, r/n8n, Upwork and LinkedIn posts showing workflow screenshots.
The product sells a document, not infrastructure. There is no proxy, no SDK, no traffic in the request path. That has two consequences: the buyer can evaluate it in one upload without an integration trial, and the founder can produce the first free output this week from any publicly shared workflow JSON with no audience and no ad budget.
JEV scored this concept 61.0/100, band C. The weak criteria are market demand (4.54) and monetization potential (4.79); the strong ones are speed to first revenue (7.92) and reachable customers (7.40). The 30 days below are shaped by that: reach a paid document fast, then answer the monetization weakness with repeat quotes and a monthly agency tier instead of pretending one $29 sale is a business.
Versus a free spreadsheet template: the compiler rebuilds the node graph, isolates AI nodes, extracts prompt text and model parameters, and writes the estimate back into the workflow JSON as sticky notes - the build ships with its own cost documentation.
2. Smallest sellable MVP
One page. Upload an n8n JSON export, get a quote. The must-haves are the importer (nodes and connections), an AI-node classifier that also lists what it could not read, a token band estimator (low/base/high) per AI node, a hand-maintained price table keyed by model ID, a run-count control (linear, per-item loop, per-branch), and the output artifact: branded PDF plus a read-only share link with per-node table, cost per run, cost per 1,000 runs, monthly projection and an agency price/margin line. The patched workflow JSON with the estimate in sticky notes is what makes it feel like handover material rather than a calculator.
Explicitly out: runtime proxy, shadow testing, quality scoring, automatic model swaps, Zapier, live provider billing APIs, team roles, and any promise of exactness. Every sheet carries an estimate-range label.
3. Technical implementation plan
Next.js on Vercel, Supabase for Postgres and object storage, one structured-output LLM call for prompt extraction and node classification, react-pdf for the PDF, Stripe Checkout connected to TrustMRR, and a price table JSON file kept in the repo.
Build order: scaffold and deploy; parse the export; classify AI nodes; extract prompts and models; estimate tokens; multiply by the run model and the price table; render the sheet; gate it behind a paid credit; write sticky notes back into the JSON. The hardest technical risk is the importer, not the model: n8n schema drift breaks the load-bearing component. Mitigate with stored fixtures, a regression test over 20 saved workflows and an explicit unsupported-node list shown to the user instead of silent wrong numbers.
4. Pricing and monetization
Three tiers, all one-time except the top: Single Quote $29, Proposal Pack $99 (five quotes, agency logo, margin line, saved client workspace), Agency Monthly $199. The $99 pack is the planning price. The repeat path is credits - a freelancer who sends three proposals a month buys the pack again; an agency converts to monthly. Model price table updates are the natural reason to stay subscribed, and the margin calculator line is the feature agencies ask for first.
5. First-customer acquisition
One channel: public workflow teardowns. Take publicly shared n8n template JSON, run it through the compiler, publish what the template actually costs per 1,000 runs with the free sheet attached and a single line of context. Then DM the people who reply or post workflow screenshots asking about cost, and offer to compile their own workflow once, free, no signup. Paid offers go into the follow-up, not the first message. Week-one goal: 6 public teardowns and 25 DMs.
6. Detailed 30-day execution roadmap
Days 1-5 build the MVP: importer, classifier, token and price engine, sheet, Stripe. Day 5 is the MVP deadline and the first paid-capable deploy. Days 6-9 are the first teardown wave and the first sale push; day 9 is the first-sale target, measured as a paid quote or a written objection list, because the objection list is also information. Days 10-14 harden the run-count control, ship the $99 Proposal Pack, open a second channel (Upwork freelancers, r/automation), and kill the weakest channel on day 14. Days 15-21 add Agency Monthly, run agency-focused LinkedIn outreach, ship the margin calculator, set a three-email onboarding sequence and do a mid-point price check against close rate. Days 22-28 harden the importer against real unsupported nodes, push teardown volume to 15, send an upgrade bundle to single-quote buyers, collect two approved customer quotes, DM 50 freelancers, and reconcile every payment against TrustMRR. Days 29-30 are closing: one final reminder to all warm leads, freeze the product, export the numbers, file the submission.
7. Revenue and profit scenarios
Three projections, all hypotheses. Payment processing is modelled at roughly 4% of collected revenue (Stripe card fees plus cross-border), delivery cost at $0.30 or less per workflow for the LLM call plus hosting.
Conservative: 6 customers at a $74 blended ARPU, mostly $29 single quotes, for $444 collected, $18 in fees and $35 operating. Base: 22 customers at $86 blended for $1,892 collected, one refund, $76 in fees, $60 operating. Upside: 55 customers at $97 blended for $5,335 collected, two refunds, $213 in fees, $250 of paid promotion and $140 operating. Hackathon profit excludes operating cost; business profit subtracts it.
The concept's own planning number was 120 customers and roughly $11.9k, which is more than six times the base case here and should be treated as the stretch ceiling, not the plan. The honest read: a one-time $29-$99 document does not reach $100k in 30 days at this price. The plan optimises for a credible, profitable, verifiable result plus a repeat-purchase path that outlives the contest.
8. Main risks and validation experiments
Estimate error is the first risk: bad ranges produce refunds and reputational damage. Validate by costing 10 real workflows whose actual billed spend the owner will share, and require a majority within plus or minus 40%; if median error is 2x or worse, stop selling and move to a human-assisted review flow. Importer fragility is second: measure parse success across 20 public exports and require 60% or better before pushing volume. Weak repeat intent is third: ask every buyer how many quotes they will send next quarter and require 20% or more saying two or more, otherwise make the pack bigger. Community spam perception is fourth: DM only people who asked, follow each forum's self-promotion rules, and stop the channel if 25 DMs return zero replies. Fifth, the buyer may refuse to pay for a document at all: A/B the Single Quote page at $29 and $49 and kill after 200 qualified viewers with no purchase.
9. First 24-hour action plan
Hours 1-2: scaffold and deploy the Next.js app, create Supabase tables, confirm Stripe and TrustMRR are connected and no live payment can be taken. Hours 3-5: collect 10 publicly shared n8n workflow JSONs into a fixtures folder and write the parser that reconstructs nodes and connections. Hours 6-9: build the AI-node classifier with the unsupported-node list and run it over all 10 fixtures. Hours 10-14: build the token band estimator, the price table and the per-run math, unit-tested against one hand-checked workflow. Hours 15-18: render a first quote page and PDF from a fixture and hand-check every number. Hours 19-24: draft the first public teardown and build a 25-row DM list, staged to send the moment checkout takes payments.
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 →FlakeReceipt
Turns a flaky test's failure logs into a signed, shareable flake report that proves the test is unstable, not the code.
BriefToBoard Compiler
Turns a signed client brief into an importable project board, a one-page scope memo, and a missing-inputs checklist for small web-design and branding agencies.
ListingGrade
Turns one raw product photo into a marketplace-ready image pack — exact dimensions, pure-white background, correct product fill, and a pass/fail compliance report for Amazon, Etsy, Walmart, and TikTok Shop.