Score B · 6.61/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 15, 2026

Negative Keyword Refinery

Turns a Google Ads search term report into a Google Ads Editor-ready negative keyword CSV and a one-page wasted-spend memo for solo Google Ads freelancers and small advertisers.

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.

Promising6.61/10
MVP build (solo)
4 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach in Google Ads freelancer communities with a free teardown offer.
Who pays

Solo Google Ads freelancer or in-house marketer at a 1-10 person ecommerce or service business spending $2k-$50k/month on Google Ads, triggered by a monthly budget review, client reporting deadline, or cost-per-lead spike; English-speaking US/UK/CA/AU.

Biggest execution risk

Competitive defensibility 4.9/10

Move from a generic AI feature to a specific workflow with a named output, a constrained input and an integration that generic assistants do not handle.

Why this could work in 30 days: one founder can ship the MVP in 4 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 9.1/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.

0/12
Entry price
$99
Solo build
4 days
30d base revenue
$990
30d hackathon profit
$958
Section 1 of 8

Product opportunity and positioning

Target customer

Solo Google Ads freelancer or in-house marketer at a 1-10 person ecommerce or service business spending $2k-$50k/month on Google Ads, triggered by a monthly budget review, client reporting deadline, or cost-per-lead spike; English-speaking US/UK/CA/AU.

Why now

Google Ads budgets are under review, freelancers need a fast billable cleanup, and CSV exports are available without API approval or OAuth.

Problem

Search term reports contain thousands of queries; the buyer manually scans them, misses high-spend zero-conversion queries, and rarely ships a negative keyword list, so wasted spend continues and client reports lack concrete actions.

Solution

Upload a CSV or paste rows; the product maps columns, flags high-spend/zero-conversion and irrelevant queries, clusters themes, and returns an Editor-ready negative keyword CSV, a prioritized cut list with estimated monthly waste removed, and a one-page client memo.

Differentiation · Generic AI chat gives advice; agency audits cost more and take days; this returns the exact bulk-upload file and client memo from one CSV in minutes.

1. Product opportunity and positioning

Negative Keyword Refinery is a narrow paid artifact for solo Google Ads freelancers and small advertisers spending $2k-$50k/month. The trigger is a monthly budget review, a client reporting deadline, or a cost-per-lead spike. The buyer already exports a search term report; the painful work is scanning thousands of rows, finding high-spend zero-conversion queries, and turning them into a negative keyword list that Google Ads Editor will accept. The product does that in one upload.

It is inspired by AdGrok's wasted-spend problem but deliberately avoids bid automation, OAuth, and campaign management. JEV scored the concept 66.1/100 (band B), with speed-to-first-revenue at 9.07/10 and monetization at 4.97/10. The weak monetization score is a design instruction: sell a named output tied to money saved, then create a repeat path. The defensible wedge is the constrained input (Google Ads search term CSV) and the named output (Editor-ready negative keyword CSV plus client memo), not a generic AI assistant.

The buyer does not need a platform, a dashboard, or a monthly subscription to start. They need a clean list they can upload today and a memo they can send to a client. That is why the first offer is a $99 one-time Campaign Cleanup Kit with a 24-hour turnaround. The market is reachable without paid ads: freelancers congregate in r/PPC, r/GoogleAds, LinkedIn groups, and Slack/Discord communities, and they openly discuss wasted spend. The product replaces hours of spreadsheet scanning and agency-priced audits with one upload and three files.

This is not a broad AdWords replacement. It is a refinery: input a messy report, output the negatives, the cut list, and the memo. The narrow scope is the advantage for a solo founder in a 30-day contest because it avoids API approvals, procurement, and ongoing campaign writes.

Section 2 of 8

Smallest sellable MVP

A paid upload-to-artifact flow: CSV in, three files out, no account required.

Must-have features

  • CSV upload and paste with auto-detection of campaign, ad group, search term, impressions, clicks, cost, and conversions.
  • Manual column mapping fallback when auto-detection fails.
  • Rule-based flagging for high-spend zero-conversion, high-cost low-conversion, and irrelevant intent terms with user-set thresholds.
  • Theme clustering of flagged terms by shared tokens, with optional LLM labels.
  • Google Ads Editor-compatible negative keyword CSV export with campaign/ad group and match type columns.
  • One-page memo generator with estimated monthly waste removed, top 10 negatives, and next-step checklist.
  • Stripe Checkout for $99 one-time payment and signed download links for artifacts.

Explicitly out of scope

  • No direct Google Ads API integration or OAuth.
  • No automated bid changes or campaign management.
  • No multi-user team accounts or dashboards.
  • No ongoing monitoring or scheduled reports.
  • No Microsoft Ads, Amazon Ads, or other platforms.
  • No human account management or done-for-you service.

Demo flow (what the buyer sees)

  1. Buyer exports a Google Ads search term report as CSV.
  2. Buyer uploads the CSV or pastes rows into the landing page.
  3. Product auto-detects columns and shows mapped fields.
  4. Buyer sets thresholds or accepts defaults.
  5. Product flags terms, clusters themes, and previews estimated waste.
  6. Buyer pays $99 via Stripe Checkout.
  7. Product generates and serves the negative keyword CSV, cut list, and memo via signed links.
Build plan

Technical implementation plan

Stack

Next.js on VercelStripe CheckoutSupabase Storage or Vercel KV for temporary filesPapa ParseOpenAI API optional for theme labelsTailwind CSSPostHog or simple server logs for funnel events

Architecture

The landing page accepts a CSV upload or pasted rows. A serverless route parses the file with Papa Parse, maps columns, applies deterministic scoring rules, clusters flagged terms by shared tokens, and renders three artifacts. The preview is shown before payment. Stripe Checkout confirms payment, then a webhook generates signed download links and stores files temporarily. Core scoring is rule-based; an LLM is optional for labeling themes and is capped per run to control cost.

Build steps

  1. Create Next.js repo and deploy the landing page to Vercel.
  2. Build CSV upload and paste input with Papa Parse.
  3. Implement column auto-detection and manual mapping fallback.
  4. Add threshold controls and deterministic scoring rules.
  5. Build theme clustering by shared tokens and optional LLM labels.
  6. Generate negative keyword CSV, cut list, and memo HTML/PDF.
  7. Wire Stripe Checkout and a webhook for payment confirmation.
  8. Add signed download links and temporary file storage.
  9. Test with synthetic and volunteer-exported search term reports.
  10. Deploy production, run end-to-end test, and fix Editor CSV formatting.

AI components

  • Optional LLM call to label clustered themes in plain English; core flagging and CSV generation remain deterministic.
Hardest technical risk: Google Ads Editor may reject the negative keyword CSV if campaign names, ad group names, or match types are not exactly formatted.
Section 3 of 8

Pricing and monetization

Campaign Cleanup Kit

Entry offer
$99 one-time

For Solo freelancer or small advertiser with one Google Ads account needing a monthly cleanup

  • Google Ads Editor-ready negative keyword CSV
  • Prioritized cut list with estimated monthly waste removed
  • One-page client-ready memo
  • Threshold settings saved for repeat runs

Model: One-time $99 Campaign Cleanup Kit per search term report, with repeat purchases for additional accounts or months.

First revenue offer: Send a free waste scan of one search term report; return three negative keyword CSVs and a memo; pay $99 for the full kit with a 24-hour turnaround.

Expected ACV: $99

Upsell path: Repeat cleanup for the next month or account at $99; three-account bundle at $249; paid CSV-format check at $29.

Target customers
20
Revenue model
$1,980
Costs
$80
Profit model
$1,900
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach in Google Ads freelancer communities with a free teardown offer.

Where to find them

  • r/PPC recent threads about wasted spend or search term reports
  • r/GoogleAds posts asking for negative keyword help
  • LinkedIn Google Ads freelancer groups
  • Google Ads Slack and Discord communities
  • X/Twitter Google Ads practitioners posting campaign screenshots

Exact outreach motions

  • Send 10 personalized DMs per day offering a free scan of one search term report.
  • Post a redacted before/after memo in r/PPC and ask for feedback.
  • Reply to 5 threads per week where someone describes wasted spend.
  • Follow up after 3 days with a Stripe link and a 24-hour turnaround.
  • Ask every free-scan recipient for one referral after delivery.

Message template

I'm testing a free Google Ads search term cleanup. Send me one CSV export and I'll return 3 negative keyword CSVs plus a one-page waste memo. No call, no access needed. If it's useful, the full kit is $99. Want me to run yours?
Week-one goal: Send 30 personalized DMs, deliver 5 free scans, and book 2 feedback calls.
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 1Foundation

Repo and landing page

  • Create Next.js repo and deploy to Vercel.
  • Write landing page with sample memo and CSV preview.
  • Add Stripe test link and sample artifacts.
  • Define CSV column schema.

Deliverable: Live landing page with sample artifacts.

Day 2CSV ingestion

Upload and mapping

  • Build upload and paste parser with Papa Parse.
  • Auto-detect campaign, ad group, search term, cost, conversions.
  • Add manual column mapping fallback.
  • Test with 3 synthetic exports.

Deliverable: Parser handles common Google Ads exports.

Day 3Scoring

Flag wasted spend

  • Implement high-spend zero-conversion rule.
  • Implement low-conversion cost rule.
  • Add irrelevant intent token list.
  • Expose threshold sliders.

Deliverable: Flagged term table with waste estimate.

Day 4Artifacts

CSV and memo output

  • Generate Editor-ready negative keyword CSV.
  • Build one-page memo template.
  • Add signed download links.
  • Validate CSV against Google Ads Editor help.

Deliverable: Three downloadable artifacts.

Day 5Payment and launchMVP shipped

Sellable MVP

  • Wire Stripe Checkout for $99 one-time.
  • Gate artifact generation behind payment.
  • Deploy production and run end-to-end test.
  • Publish launch post in one community.

Deliverable: Sellable MVP live.

Day 6Hardening

Real CSV tests

  • Test 5 real search term exports from volunteers.
  • Fix column mapping failures.
  • Add error messages for missing columns.
  • Log anonymized failures.

Deliverable: Mapping fixes for 5 real files.

Day 7Outreach prep

30-prospect list

  • Build list of 30 freelancers from r/PPC and r/GoogleAds.
  • Create free-scan offer message.
  • Record 60-second walkthrough.
  • Prepare redacted sample memo.

Deliverable: 30-prospect list and outreach kit.

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

First DMs

  • Send 10 personalized DMs offering free scan.
  • Post redacted before/after in r/PPC.
  • Reply to 5 threads about wasted spend.
  • Track responses in sheet.

Deliverable: 10 DMs sent, 1 community post.

Day 9Concierge delivery

Free scans

  • Run free scans for first 3 respondents manually.
  • Note threshold issues.
  • Ask two questions on memo clarity.
  • Update rules from feedback.

Deliverable: 3 free scans delivered.

Day 10Outreach wave 2

LinkedIn and follow-up

  • Send 15 DMs to LinkedIn Google Ads freelancers.
  • Follow up with day-8 non-responders.
  • Share sample memo in one Slack group.
  • Book 2 feedback calls.

Deliverable: 25 total prospects contacted.

Day 11Conversion prep

Paid offer ready

  • Fix top 3 CSV mapping bugs.
  • Add refund policy for no negatives found.
  • Create Stripe payment link with 24-hour turnaround.
  • Write follow-up email.

Deliverable: Paid offer ready.

Day 12First sale pushFirst sale target

First paid sale

  • Offer $99 Campaign Cleanup Kit to free-scan recipients.
  • Send Stripe link with deadline.
  • Post limited 5-slot offer in community.
  • Deliver any paid kit within 24 hours.

Deliverable: First paid sale target.

Day 13Delivery and polish

Paid delivery

  • Deliver paid kit and collect written feedback.
  • Add threshold presets for ecommerce and lead gen.
  • Improve memo wording.
  • Fix any CSV rejection.

Deliverable: One paid delivery completed.

Day 14Referral ask

New prospects

  • Ask buyer for referral to one freelancer.
  • Send 10 new DMs.
  • Post redacted paid memo with permission.
  • Update FAQ from questions.

Deliverable: 10 new prospects and referral request.

Week 3 · Repeat & systematize · 7 days
Day 15Proof asset

Public case study

  • Publish redacted case study with waste estimate.
  • Create LinkedIn post about negative keyword workflow.
  • Add sample CSV download to landing page.
  • Send to 5 LinkedIn groups.

Deliverable: Public proof asset live.

Day 16Outreach wave 3

In-house marketers

  • Send 15 DMs to in-house marketers.
  • Comment on 10 recent posts about wasted spend.
  • Follow up with day-12 leads.
  • Track conversion rate.

Deliverable: 15 new DMs, follow-ups sent.

Day 17Product hardening

Format validation

  • Add campaign/ad group match-type validation.
  • Handle currency symbols and commas.
  • Add CSV preview before payment.
  • Reduce LLM calls to optional labels.

Deliverable: Fewer format rejections.

Day 18Support and refunds

Reduce support load

  • Write CSV formatting troubleshooting guide.
  • Set refund rule for fewer than 5 negatives.
  • Respond to all support within 24h.
  • Update checkout terms.

Deliverable: Support guide and refund policy.

Day 19Pipeline review

Channel decision

  • Review response and paid conversion rates.
  • Double down on best-performing community.
  • Send 10 follow-ups.
  • Ask two non-buyers why not.

Deliverable: Channel decision memo.

Day 20Bundle offer

Increase ACV

  • Launch 3-account cleanup bundle at $249.
  • Email past free-scan recipients.
  • Post bundle in one community.
  • Track take-up.

Deliverable: Bundle checkout live.

Day 21Weekly close

Books and backlog

  • Reconcile Stripe payments and fees.
  • Deliver all outstanding kits.
  • Update waste estimate examples.
  • Plan week 4 outreach.

Deliverable: Books and backlog clean.

Week 4 · Scale what works · 7 days
Day 22Content push

Teardown post

  • Publish teardown of a redacted search term report.
  • Share 3 negative keyword mistakes in r/PPC.
  • Pitch 3 freelancer newsletters.
  • Send 10 DMs.

Deliverable: Teardown post and 10 DMs.

Day 23Community trust

Public mini-scans

  • Answer 10 questions in Google Ads forums.
  • Offer 3 free mini-scans publicly.
  • Collect before/after screenshots.
  • Update landing page proof section.

Deliverable: 3 public mini-scans.

Day 24Outreach wave 4

UK/CA/AU freelancers

  • Send 20 DMs to UK/CA/AU freelancers.
  • Follow up with all day-16 leads.
  • Post limited 24-hour offer.
  • Track replies by segment.

Deliverable: 20 new DMs sent.

Day 25Checkout optimization

Conversion

  • Add FAQ on CSV export steps.
  • Add sample memo above checkout.
  • Test mobile checkout.
  • Reduce form fields.

Deliverable: Higher checkout completion.

Day 26Follow-up sprint

Non-buyers

  • Email every non-buyer with sample memo.
  • Offer 15-minute CSV check.
  • Send final call for month-end cleanup.
  • Log objections.

Deliverable: All leads followed up.

Day 27Delivery quality

Second-pass validation

  • Review all delivered kits for errors.
  • Add second-pass CSV validation.
  • Ask buyers for permission to quote feedback.
  • Fix top memo complaint.

Deliverable: Quality review complete.

Day 28Final sales push

Month-end cleanup

  • Post month-end cleanup offer.
  • Send 10 DMs to warm leads.
  • Offer bundle to existing buyers.
  • Close any pending payments.

Deliverable: Final pipeline pushed.

Days 29-30 · Consolidate · 2 days
Day 29Reconciliation

Financial log

  • Reconcile all revenue, refunds, fees.
  • Confirm TrustMRR payment flow.
  • Export customer list and artifacts.
  • Write delivery log.

Deliverable: Accurate financial log.

Day 30Retrospective

Next-step decision

  • Calculate response and conversion by channel.
  • Decide repeat vs new wedge.
  • Document top 3 CSV failures.
  • Plan next 30 days.

Deliverable: Retro and next-step decision.

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: 3 paid $99 kits, no paid ads, no refunds.
  • Base: 10 paid $99 kits from direct outreach, no paid ads, no refunds.
  • Upside: 25 paid $99 kits, 2 refunds, $150 paid sponsored post.
  • Payment processing assumed Stripe at 2.9% + $0.30 per transaction (Conservative, Base, Upside).
  • Operating costs cover Vercel, Supabase, domain, and optional OpenAI labels; founder time is excluded.
  • No chargebacks assumed; refund policy is limited to fewer than 5 negatives found.
  • Buyers pay one-time $99; no subscription is required.
  • Outreach response of 10% and paid conversion of 3-5% are hypotheses, not verified results.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$10
Paid marketing
$0
Hackathon profit
$287
Operating costs
$25
Business profit
$262

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$32
Paid marketing
$0
Hackathon profit
$958
Operating costs
$45
Business profit
$913

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$50
Chargebacks
$0
Payment fees
$79
Paid marketing
$150
Hackathon profit
$2,196
Operating costs
$90
Business profit
$2,106

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.

Section 7 of 8

Main risks and validation experiments

Risk 1Google Ads CSV export formats vary and column mapping may fail.

Mitigation

Add manual mapping fallback and store anonymized failure patterns.

Validation experiment

Run 5 volunteer exports through the parser and count mapping failures.

Kill criteria

If more than 40% of real exports need manual repair after 20 tests, narrow to one export type or add a pre-built mapping library.

Risk 2Google Ads Editor rejects the negative keyword CSV.

Mitigation

Validate campaign/ad group names and match types; test against Editor help docs and real uploads.

Validation experiment

Ask 3 freelancers to upload the generated CSV to Editor and report errors.

Kill criteria

If fewer than 3 of 5 CSVs import cleanly, pause sales and fix format before further outreach.

Risk 3Buyers expect direct Google Ads integration and reject manual upload.

Mitigation

Position the output as an Editor-ready file, not an API integration; show the upload step clearly.

Validation experiment

Ask 10 prospects whether a CSV upload is acceptable versus OAuth.

Kill criteria

If more than 60% require OAuth before paying, pivot to a different artifact or add an approved API path.

Risk 4Freelancer communities treat direct outreach as spam.

Mitigation

Lead with a free scan, personalize each message, and follow community rules.

Validation experiment

Send 30 DMs across two communities and track reply and removal rates.

Kill criteria

If 30 DMs produce fewer than 3 replies and 2 warnings, switch to content-led inbound or paid sponsored posts.

Risk 5Refunds if the report finds few negative keywords.

Mitigation

Set a clear refund rule for fewer than 5 negatives and show the waste estimate before payment.

Validation experiment

Track refund requests across the first 10 paid kits.

Kill criteria

If refunds exceed 20% of paid kits, tighten qualification or change the offer to a paid audit with a minimum spend threshold.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Next.js repo and landing page copy.
  • Build sample memo and sample negative keyword CSV.
  • Deploy to Vercel.

Output: Live landing page with sample artifacts.

Hours 3-4

  • Build CSV upload and paste parser.
  • Add column auto-detection for core fields.
  • Add manual mapping fallback.

Output: Working CSV parser.

Hours 5-6

  • Implement high-spend zero-conversion and low-conversion rules.
  • Generate flagged term table and waste estimate.
  • Draft one-page memo template.

Output: Scoring engine and memo draft.

Hours 7-8

  • Wire Stripe test checkout.
  • Run end-to-end test with a synthetic CSV.
  • Send 5 personalized DMs offering free scans.

Output: Test payment flow and 5 DMs sent.

Complete report

Full 30-day launch report

Read the full generated report

Negative Keyword Refinery — 30-Day Launch Report

1. Product opportunity and positioning

Negative Keyword Refinery is a narrow paid artifact for solo Google Ads freelancers and small advertisers spending $2k-$50k/month. The trigger is a monthly budget review, a client reporting deadline, or a cost-per-lead spike. The buyer already exports a search term report; the painful work is scanning thousands of rows, finding high-spend zero-conversion queries, and turning them into a negative keyword list that Google Ads Editor will accept. The product does that in one upload.

It is inspired by AdGrok's wasted-spend problem but deliberately avoids bid automation, OAuth, and campaign management. JEV scored the concept 66.1/100 (band B), with speed-to-first-revenue at 9.07/10 and monetization at 4.97/10. The weak monetization score is a design instruction: sell a named output tied to money saved, then create a repeat path. The defensible wedge is the constrained input (Google Ads search term CSV) and the named output (Editor-ready negative keyword CSV plus client memo), not a generic AI assistant.

The buyer does not need a platform, a dashboard, or a monthly subscription to start. They need a clean list they can upload today and a memo they can send to a client. That is why the first offer is a $99 one-time Campaign Cleanup Kit with a 24-hour turnaround. The market is reachable without paid ads: freelancers congregate in r/PPC, r/GoogleAds, LinkedIn groups, and Slack/Discord communities, and they openly discuss wasted spend. The product replaces hours of spreadsheet scanning and agency-priced audits with one upload and three files.

This is not a broad AdWords replacement. It is a refinery: input a messy report, output the negatives, the cut list, and the memo. The narrow scope is the advantage for a solo founder in a 30-day contest because it avoids API approvals, procurement, and ongoing campaign writes.

2. Smallest sellable MVP

The smallest sellable MVP is a paid upload-to-artifact flow. The buyer uploads a Google Ads search term CSV or pastes rows, sees mapped columns and a preview of flagged terms, pays $99 through Stripe, and receives three files: an Editor-ready negative keyword CSV, a prioritized cut list with estimated monthly waste removed, and a one-page client memo. No account is required. The build target is four days, with a live MVP on day 5. The MVP includes auto-detection for campaign, ad group, search term, impressions, clicks, cost, and conversions, plus a manual mapping fallback. Scoring is deterministic: high-spend zero-conversion, high-cost low-conversion, and irrelevant intent terms. Theme clustering groups flagged terms by shared tokens. An LLM is optional for labels only. Out of scope: Google Ads API, OAuth, bid changes, team accounts, monitoring, other ad platforms, and done-for-you service.

3. Technical implementation plan

The stack is Next.js on Vercel, Stripe Checkout, Supabase Storage or Vercel KV for temporary files, Papa Parse, Tailwind, and an optional OpenAI call for theme labels. The landing page accepts a CSV or pasted rows. A serverless route parses and maps columns, applies rules, clusters themes, and renders a preview. Payment confirms through a Stripe webhook, then signed download links are generated. Core scoring stays deterministic to control cost and make outputs repeatable. The hardest risk is Google Ads Editor rejecting the negative keyword CSV because campaign names, ad group names, or match types are formatted differently. Build steps run from repo and landing page through parser, scoring, artifact generation, Stripe, signed links, real-export testing, and production validation. Keep LLM use optional and capped per run.

4. Pricing and monetization

The model is one-time $99 per Campaign Cleanup Kit. The kit includes the negative keyword CSV, the prioritized cut list with waste estimate, the one-page client memo, and saved threshold settings for repeat runs. The first revenue offer is a free scan of one search term report; the buyer pays $99 only if they want the full kit with a 24-hour turnaround. The expected initial ACV is $99. The upsell path is repeat cleanup for the next month or account at $99, a three-account bundle at $249, and a paid CSV-format check at $29. This keeps the entry price low enough for a freelancer to approve without procurement while creating a repeat-purchase path that addresses the weak monetization score.

5. First-customer acquisition

The primary channel is direct outreach in Google Ads freelancer communities with a free teardown offer. Find prospects in r/PPC threads about wasted spend, r/GoogleAds posts asking for negative keyword help, LinkedIn Google Ads freelancer groups, Google Ads Slack/Discord communities, and X/Twitter practitioners posting campaign screenshots. Send 10 personalized DMs per day. Post a redacted before/after memo in r/PPC. Reply to five threads per week where someone describes wasted spend. Follow up after three days with a Stripe link and a 24-hour turnaround. Ask every free-scan recipient for one referral. The message is direct: send one CSV, get three negative keyword CSVs and a one-page waste memo free; pay $99 for the full kit. Week-one goal: 30 DMs sent, 5 free scans delivered, 2 feedback calls booked.

6. Detailed 30-day execution roadmap

Days 1-5 build the MVP: repo, landing page, CSV parser, scoring rules, artifacts, Stripe, and production deploy. Day 5 is the MVP deadline. Days 6-7 harden mapping with real exports and prepare a 30-prospect list. Days 8-11 run outreach wave one and two, deliver free concierge scans, fix mapping bugs, and prepare the paid offer. Day 12 is the first-sale target. Days 13-14 deliver the first paid kit, collect feedback, and ask for referrals. Days 15-21 publish a redacted case study, run outreach wave three, harden format validation, add support and refund rules, review the pipeline, launch a $249 three-account bundle, and reconcile the week. Days 22-28 push content, community trust, outreach wave four, checkout optimization, follow-up sprints, delivery quality, and a final sales push. Days 29-30 reconcile revenue and fees, confirm TrustMRR flow, and decide the next 30 days.

7. Revenue and profit scenarios

These are projections from stated assumptions, not verified revenue. Conservative: 3 kits at $99 = $297 gross; $0 refunds, $0 chargebacks, $10 payment fees, $0 ad spend, $25 operating costs. Base: 10 kits = $990 gross; $0 refunds, $0 chargebacks, $32 payment fees, $0 ad spend, $45 operating costs. Upside: 25 kits = $2,475 gross; $50 refunds, $0 chargebacks, $79 payment fees, $150 ad spend, $90 operating costs. Payment fees assume Stripe at 2.9% + $0.30 per transaction. Operating costs cover hosting, storage, domain, and optional LLM labels. The contest ranks hackathon profit after refunds, chargebacks, fees, and paid ad spend; business profit also subtracts operating costs. The upside case depends on paid sponsored posts working alongside organic outreach. The base case assumes no paid ads and a 3-5% paid conversion from direct outreach, which is a hypothesis.

8. Main risks and validation experiments

First, CSV export formats vary. Mitigation: manual mapping and anonymized failure logs. Test 5 volunteer exports and count failures; if more than 40% need manual repair after 20 tests, narrow the supported export type. Second, Google Ads Editor may reject the CSV. Test 5 real uploads; if fewer than 3 import cleanly, pause sales and fix format. Third, buyers may demand direct Google Ads integration. Ask 10 prospects whether CSV upload is acceptable; if more than 60% require OAuth before paying, pivot or add an approved API path. Fourth, communities may treat outreach as spam. Send 30 DMs across two communities; if fewer than 3 replies and 2 warnings, switch to content-led inbound or sponsored posts. Fifth, refunds may rise if reports find few negatives. Track refunds across the first 10 paid kits; if refunds exceed 20%, tighten qualification or change the offer.

9. First 24-hour action plan

Hours 1-2: create the repo, write landing copy, build a sample memo and sample negative keyword CSV, and deploy to Vercel. Output: live landing page. Hours 3-4: build CSV upload and paste parsing, add auto-detection for core fields, and add manual mapping fallback. Output: working parser. Hours 5-6: implement high-spend zero-conversion and low-conversion rules, generate a flagged term table with waste estimate, and draft the one-page memo. Output: scoring engine and memo draft. Hours 7-8: wire Stripe test checkout, run an end-to-end test with a synthetic CSV, and send 5 personalized DMs offering free scans. Output: test payment flow and 5 DMs sent.

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 →