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

Manifest Doctor

A web tool that scans an Xcode project and hands back the ready-to-commit PrivacyInfo.xcprivacy manifest files, a third-party SDK manifest gap list, and a filled App Store Connect privacy answer sheet for the whole app.

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.22/10
MVP build (solo)
4 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Organic free-scan replies in r/iOSProgramming and r/SwiftUI, plus direct X messages to developers who posted recent App Review rejections.
Who pays

The iOS lead engineer or solo iOS developer at a 1-50 person app company, or a freelance iOS contractor carrying 2-5 client apps, with an App Store submission already scheduled in the next 30 days.

Biggest execution risk

Operational simplicity 4.0/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

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 8.2/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

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

0/8
Entry price
$99
Solo build
4 days
30d base revenue
$1,488
30d hackathon profit
$1,337
Section 1 of 8

Product opportunity and positioning

Target customer

The iOS lead engineer or solo iOS developer at a 1-50 person app company, or a freelance iOS contractor carrying 2-5 client apps, with an App Store submission already scheduled in the next 30 days.

Why now

Every submission in the next 30 days must satisfy the required-reason API declaration, and the failure surfaces only at archive time when a fix is most expensive.

Problem

Required-reason API calls are scattered across hundreds of files and inside third-party packages, so developers only discover their missing privacy manifest declarations at submission, then hand-audit and hand-write plists per target under deadline.

Solution

Upload a zipped source tree or run the CLI: the scanner maps every required-reason call site to file and line, writes one PrivacyInfo.xcprivacy per app target with reason codes, lists SDKs shipping no manifest, generates a Ruby xcodeproj attach script and an App Store Connect answer sheet, then emails a 7-day download link after Stripe checkout.

Differentiation · Xcode's privacy report runs after archive and produces no files; generic generators require you to already know your reason codes. Manifest Doctor finds the call sites in your own tree and writes the per-target files plus the patch script.

1. Product opportunity and positioning

Apple requires every iOS app target to ship a PrivacyInfo.xcprivacy file declaring required-reason API usage. Xcode's privacy report only appears after you archive, only lists what Apple detected, and never writes per-target manifest files. The triggering calls - UserDefaults reads, file timestamp access, system uptime checks, disk-space queries, active keyboard queries - are scattered across hundreds of Swift and Objective-C files and frequently buried inside third-party packages. The developer therefore discovers the gap at submission time, then hand-audits the tree, guesses reason codes and hand-writes a plist per target under deadline.

The buyer is the iOS lead engineer or solo developer at a 1-50 person app company, or a freelance iOS contractor carrying two to five client apps, with an App Store submission already scheduled in the next 30 days. That buyer is reachable today in r/iOSProgramming, r/SwiftUI, on X and in iOS Slack communities, and the trigger event (a rejection or a submission date) is public and dated.

The positioning is deliberately pre-commit: Manifest Doctor runs before you archive. Its output is a deterministic artifact - one PrivacyInfo.xcprivacy per app target with reason codes, a call-site table listing file and line for every match, an SDK gap list for integrated dependencies that ship no manifest, a generated Ruby xcodeproj script that attaches each manifest to the right target, and a markdown sheet of implied App Store Connect privacy answers.

JEV scored this concept 6.22/10 (band C, confidence 0.52). Its strengths are speed to first revenue (8.23 normalized) and reachable customers (7.14). Its two weak criteria are monetization potential (4.74) and operational simplicity (4.0). This plan attacks both without changing the wedge: price is anchored to a dated submission event and to a contractor pack that creates repeat purchase, and delivery stays stateless on managed services with no human review step and no custom infrastructure.

The narrowness is the point. There is no design-system buy-in, no integration, no migration, no Figma pipeline and no generated screen code. One zip in, one committable bundle out, on a date the buyer already has circled.

Section 2 of 8

Smallest sellable MVP

A deployed upload page where a developer drops a project zip, pays $99 via Stripe, and receives an emailed bundle containing one PrivacyInfo.xcprivacy per app target, the call-site table, the SDK gap list, the Ruby attach script and the App Store Connect answer sheet.

Must-have features

  • Swift and Objective-C scanner that reports every required-reason API call site with file, line and matched symbol
  • PrivacyInfo.xcprivacy generator writing one valid plist per detected app target with NSPrivacyAccessedAPITypes and reason codes
  • Dependency inspector reading Package.resolved, Podfile.lock and vendored frameworks to flag SDKs with no bundled manifest
  • Generated Ruby xcodeproj script that adds each manifest to the correct target's Copy Bundle Resources phase
  • App Store Connect answer sheet as a markdown table of implied privacy nutrition answers
  • Stripe Checkout on the TrustMRR-connected account plus Resend delivery of a 7-day signed download link
  • Free one-screen scan endpoint returning only the count of undeclared call sites, used as the lead magnet
  • Local CLI mode that prints manifests to stdout so source never has to be uploaded

Explicitly out of scope

  • No GitHub App, CI hook or automatic pull request
  • No Android, React Native or Flutter parsing
  • No App Store Connect API upload or automated submission
  • No privacy policy generator or legal advice
  • No team dashboard, seats, roles or audit log
  • No curated third-party SDK reason-code database - only what is physically present in resolved packages

Demo flow (what the buyer sees)

  1. Developer zips an Xcode project and uploads it (or runs the CLI locally)
  2. Scanner parses Swift and Objective-C sources, Info.plist files, Package.resolved and Podfile.lock
  3. Result page shows the free count of undeclared call sites and offers the $99 bundle
  4. Stripe Checkout completes on the TrustMRR-connected account
  5. Worker generates manifests, gap list, attach script and answer sheet
  6. Plist outputs are re-parsed and validated before packaging
  7. Resend emails a signed 7-day download link
  8. Buyer drops the manifests into the repo and runs the Ruby attach script
Build plan

Technical implementation plan

Stack

Next.js on Vercel for landing page, checkout redirect and upload formPython worker (serverless function) for scanning and generationtree-sitter-swift with regex fallbacks for Objective-CRuby xcodeproj gem script generated as text output, run client-sideStripe CheckoutResend for deliverable emailCloudflare R2 with pre-signed upload and download URLsSupabase Postgres for job records and scan resultsplutil for plist validation in the pipeline

Architecture

Vercel serves the landing page and the upload form. The browser requests a pre-signed R2 PUT URL, uploads the zip, then calls a Next.js route that inserts a job row in Supabase and triggers the Python worker with the object key. The worker unpacks into a 25 MB-capped temp directory, detects targets from the .xcodeproj and scheme definitions, runs the rule engine over the tree, and writes manifests, the call-site table, the gap list, the Ruby script and the answer sheet into a result zip that is uploaded to R2 with an expiry. Stripe webhook marks the job paid; only paid jobs get a download link, which is emailed through Resend with a 7-day signed URL. Source archives are deleted after the scan or after one hour, whichever comes first, and that policy is printed on the upload page.

Build steps

  1. Scaffold Next.js app on Vercel with /upload, /scan/[id] and /thanks routes
  2. Create Supabase tables jobs and scans plus an R2 bucket with pre-signed URL helpers
  3. Implement target detection from .xcodeproj, then the Swift/ObjC rule engine for the five required-reason API families
  4. Emit per-target PrivacyInfo.xcprivacy and validate each with plutil
  5. Parse Package.resolved and Podfile.lock and build the SDK manifest gap list
  6. Generate the Ruby xcodeproj attach script and the App Store Connect answer sheet
  7. Wire Stripe Checkout and webhook, gate downloads on paid status
  8. Wire Resend delivery with a 7-day signed link and delete source archives after the scan
  9. Ship the free one-screen scan endpoint that returns only the hit count
  10. Package and document the local CLI so privacy-sensitive buyers can run offline

AI components

  • No model in the manifest generation path by design: reason codes are deterministic rule matches
  • Optional LLM pass (small hosted model) that turns the call-site table into one plain-English paragraph per target; failure of this step must not block delivery
Hardest technical risk: Correctly mapping manifests to the right app target and producing an attach script that survives non-standard project structures (multiple targets, extensions, custom build phases, CocoaPods workspaces) - a wrong target mapping silently ships a non-compliant build.
Section 3 of 8

Pricing and monetization

Single App Fix

Entry offer
$99 one-time

For Solo iOS developer or lead engineer shipping one app in the next 30 days

  • Full source scan of one project
  • One PrivacyInfo.xcprivacy per app target
  • Call-site table with file and line per reason code
  • SDK manifest gap list
  • Ruby xcodeproj attach script
  • App Store Connect answer sheet

Studio Pack

$249 one-time

For Freelance iOS contractor with several client apps

  • Everything in Single App Fix for up to 5 projects
  • Unlimited rescans of those projects for 12 months

Model: One-time purchase per project, with a five-project contractor pack that includes 12 months of rescans.

First revenue offer: Free scan of one file or one public repo, posted publicly, followed by the $99 Single App Fix checkout link in the same reply once the scan shows undeclared call sites.

Expected ACV: $99

Upsell path: Free scan -> $99 Single App Fix -> $249 Studio Pack for contractors who mention more than one app, then repeat purchase on the next client submission because the rescan loop keeps the project on file.

Target customers
35
Revenue model
$3,465
Costs
$90
Profit model
$3,375
Section 4 of 8

First-customer acquisition

Primary channel

Organic free-scan replies in r/iOSProgramming and r/SwiftUI, plus direct X messages to developers who posted recent App Review rejections.

Where to find them

  • r/iOSProgramming threads mentioning privacy manifest, PrivacyInfo.xcprivacy or required-reason API errors
  • r/SwiftUI threads about App Store submission or App Review rejection
  • Stack Overflow questions tagged swift, swiftui or app-store-connect about privacy manifests
  • X posts from iOS developers describing an App Review rejection in the last 60 days
  • iOS developer Slack and Discord communities with a #app-review or #shipping channel

Exact outreach motions

  • Search the three communities for threads from the last 90 days and log each URL, handle and the exact error string quoted
  • Post one public free scan of the original poster's snippet showing matched call sites and the manifest entry that fixes it
  • DM 20 iOS developers on X with the same free-scan offer as the only ask, no pitch
  • Reply with the free scan within 10 minutes of any new matching thread
  • Follow up once after 72 hours with the remaining undeclared call sites and one $99 checkout link

Message template

Saw your App Review note about the privacy manifest. I built a scanner that finds required-reason API call sites in your tree and writes the PrivacyInfo.xcprivacy per target. Want a free scan of one file? I'll paste the matched lines and the reason codes - no signup, no pitch.
Week-one goal: 25 free scans delivered and 12 checkout links sent, with the first paid checkout collected by day 12.
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 1Problem validation

Confirm the exact failure language

  • Search r/iOSProgramming, r/SwiftUI and Stack Overflow for privacy-manifest threads from the last 90 days.
  • Record verbatim Apple error strings and the API each poster mentioned.
  • Build a 40-thread tracker with URL, handle and status.

Deliverable: 40-thread outreach tracker with quoted error strings.

Day 2Scaffold

Deploy the shell

  • Create the Next.js app on Vercel with /upload and /thanks.
  • Create Supabase tables jobs and scans.
  • Provision R2 plus pre-signed upload and download URLs.

Deliverable: Deployed skeleton that accepts a zip and writes a job row.

Day 3Scanner

Find the call sites

  • Add tree-sitter-swift parsing with an Objective-C regex fallback.
  • Encode the five required-reason API families.
  • Return file, line and matched symbol per hit.

Deliverable: CLI printing a JSON hit list for a sample project.

Day 4Generation

Produce the artifacts

  • Write one PrivacyInfo.xcprivacy per detected app target.
  • Parse Package.resolved and Podfile.lock to flag SDKs with no manifest.
  • Validate every plist with plutil.

Deliverable: Manifest bundle plus SDK gap table for the sample project.

Day 5MVP liveMVP shipped

Close the loop to money

  • Generate the Ruby attach script and the App Store Connect answer sheet.
  • Wire Stripe Checkout and Resend with a 7-day signed link.
  • Run one full end-to-end scan from upload to email.

Deliverable: Live MVP with the first self-served scan completed.

Day 6CLI

Remove the upload objection

  • Package the scanner as a downloadable CLI.
  • Add a dry-run flag that prints manifests to stdout.
  • Document install on the landing page.

Deliverable: Offline CLI documented and downloadable.

Day 7Payments on

Go live

  • Add the free one-screen scan returning only the hit count.
  • Switch Stripe to live mode on the TrustMRR-connected account.
  • Test a $99 and a $249 purchase, then refund the test charge.

Deliverable: Live checkout and live free-scan page.

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

First 10 public replies

  • Post 10 free-scan replies in active r/iOSProgramming manifest threads.
  • Paste the matched call sites and the manifest entry that fixes them.
  • Log every reply in the tracker.

Deliverable: 10 public replies with at least 3 responses.

Day 9Outreach batch 2

Second surface plus DMs

  • Post 10 replies in r/SwiftUI and on Stack Overflow.
  • DM 20 iOS developers on X who posted recent rejections.
  • Offer one free scan with no pitch.

Deliverable: 30 touches and the first inbound scan requests.

Day 10Scan volume

Turn requests around fast

  • Automate scan delivery so a zip returns results unattended.
  • Return each request in under 30 minutes.
  • Ask every recipient for their submission date.

Deliverable: 15 free scans delivered.

Day 11Follow-up

Convert warm leads

  • Follow up 72 hours later with the remaining undeclared call sites.
  • Attach the $99 checkout link in the same message.
  • Log which reason codes keep recurring.

Deliverable: Checkout links sent to 12 warm leads.

Day 12First saleFirst sale target

Collect the first payment

  • Hand-deliver the bundle to the hottest lead and watch them apply it.
  • Fix any output bug they hit immediately.
  • Record the exact objection raised before paying.

Deliverable: First payment collected and the pre-purchase objection written down.

Week 3 · Repeat & systematize · 7 days
Day 13Accuracy

Cut false positives

  • Cluster reason-code mismatches from delivered scans.
  • Add exclusions for test targets and SwiftUI previews.
  • Re-run 5 past scans to confirm no regression.

Deliverable: Updated rules file and an accuracy note.

Day 14Outreach batch 3

Repeat the winning phrasing

  • Post 15 new replies using the top-performing angle.
  • Publish a public before/after scan of an open-source iOS app.
  • Track reply-to-scan conversion per subreddit.

Deliverable: Public case scan and 15 new touches.

Day 15Studio Pack

Raise order value

  • DM every scan user who mentioned more than one app.
  • Offer the $249 five-project pack with 12-month rescans.
  • Add a rescan link to every delivered bundle.

Deliverable: First Studio Pack conversation open.

Day 16Trust

Lower upload friction

  • Add a delete-source-within-one-hour toggle stated on the page.
  • Publish a short note listing exactly what is stored and for how long.
  • Make the CLI the primary CTA for cautious buyers.

Deliverable: Updated upload page with retention controls.

Day 17Content

Build an indexable asset

  • Publish a required-reason API cheat sheet covering the five API families.
  • Include anonymised real match examples.
  • Link it from every reply and DM.

Deliverable: Cheat-sheet page live and linked.

Day 18Proof

Capture permissioned quotes

  • Ask each buyer for a one-line quote and app-name permission.
  • Add two quotes to the landing page if granted.
  • Record time-to-fix in minutes per buyer.

Deliverable: Landing page with permissioned testimonials.

Day 19Review

Pick the channel

  • Compute replies, scans, checkouts, sales and refunds.
  • Cut the worst-performing community.
  • Double volume in the best one.

Deliverable: Week 3 channel decision written down.

Week 4 · Scale what works · 9 days
Day 20Scale

Pour volume into the winner

  • Post 20 replies in the winning community only.
  • Reuse the exact phrasing that converted.
  • Reply within 10 minutes of any new matching thread.

Deliverable: 20 new touches in the winning channel.

Day 21Second surface

Add inbound

  • Post the cheat sheet to r/iOSProgramming and one Swift Slack community.
  • Answer 5 Stack Overflow questions with the free-scan offer.
  • Track inbound scans per surface.

Deliverable: Two additional inbound surfaces live.

Day 22Rescan loop

Create repeat use

  • Email every past buyer a rescan reminder 7 days after delivery.
  • Auto-generate a diff of newly introduced call sites.
  • Send Studio Pack buyers their 12-month rescan link; give Single App buyers one free rescan.

Deliverable: Automated rescan email running.

Day 23Unit cost

Keep delivery near zero

  • Move scanning to a serverless worker with a 10-minute cap.
  • Cache dependency resolution so rescans finish under 60 seconds.
  • Set a 25 MB zip limit with a clear error message.

Deliverable: Sub-minute rescans at near-zero marginal cost.

Day 24Refund-proofing

Make wrong output loud

  • Re-parse every generated plist and fail the job loudly on error.
  • Add a 'what we could not detect' section to every bundle.
  • Commit to answering any accuracy complaint within 4 hours.

Deliverable: Bundle self-check plus an explicit limitation note.

Day 25Second sales push

Reopen every warm lead

  • Follow up with every lead who has not paid.
  • Resend the remaining-call-site list with their submission date.
  • Offer a 15-minute screen share to Studio Pack leads.

Deliverable: All warm leads followed up twice.

Day 26Data post

Publish counted facts only

  • Publish the average undeclared call-site count from your own completed scans.
  • Label it as data from your own jobs, not a market study.
  • Link to the free scan.

Deliverable: One data post built from real job counts.

Day 27Edge cases

Fix the ugly projects

  • Collect the three projects where the attach script failed.
  • Add manual attach instructions for those project shapes.
  • Ship the fix and notify those buyers.

Deliverable: Documented attach-script fallback.

Day 28Buffer

Absorb support load

  • Recompute reply-to-paid conversion.
  • Cut any activity below 5 percent conversion.
  • Hold the day for outstanding support and a channel restart.

Deliverable: Updated funnel numbers and a written cut list.

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

Drain the pipeline

  • Re-post the free-scan offer to every thread that replied but never scanned.
  • Email past free-scan users once with deadline framing.
  • Ask every buyer for one referral handle.

Deliverable: Final outreach wave sent.

Day 30Close-out

Verify and write it down

  • Deliver every outstanding scan before the window closes.
  • Confirm all payments settled in the TrustMRR-connected account.
  • Write the post-mortem using verified numbers only.

Deliverable: Verified revenue tally and a post-mortem.

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

  • All figures are projections from stated assumptions, not verified revenue or existing customers.
  • Base and Upside assume a blended ARPU above $99 because a minority of buyers take the $249 Studio Pack.
  • Conservative assumes zero paid marketing and almost all traffic coming from public replies.
  • Payment fees assume Stripe at 2.9% plus $0.30 per transaction, with a small international card uplift, giving roughly 3.2-3.6% of gross.
  • Ad spend is paid marketing only: a promoted X post in Upside, zero everywhere else.
  • Operating costs cover Vercel, Supabase, R2 storage and egress, Resend volume and worker execution for the scans delivered.
  • No LLM inference is required to produce manifests, so inference cost is negligible and optional.
  • Every sale covers its own delivery cost; nothing is priced below cost.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$11
Paid marketing
$0
Hackathon profit
$286
Operating costs
$25
Business profit
$261

Base case

12 customers
$1,488
collected revenue · avg payment $124
Refunds
$99
Chargebacks
$0
Payment fees
$52
Paid marketing
$0
Hackathon profit
$1,337
Operating costs
$60
Business profit
$1,277

Optimistic

30 customers
$3,870
collected revenue · avg payment $129
Refunds
$99
Chargebacks
$0
Payment fees
$140
Paid marketing
$150
Hackathon profit
$3,481
Operating costs
$140
Business profit
$3,341

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.

Scenario models derive from stated assumptions and are projections only - not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Developers refuse to upload proprietary source to an unknown domain, collapsing the free-scan funnel.

Mitigation

Ship the local CLI in week one and make it the primary CTA for anyone who hesitates; state the one-hour source deletion policy on the upload page.

Validation experiment

Post two versions of the same reply on consecutive days, one linking the web scan and one linking the CLI, and compare reply and scan request rates.

Kill criteria

If fewer than 3 of 20 offered scans are accepted after both options exist, the upload model is the blocker and the offer needs rework.

Risk 2Static scanning produces false positives or misses, a buyer ships a wrong manifest and demands a refund or posts publicly.

Mitigation

Re-parse every generated plist before delivery, include an explicit 'what we could not detect' section, and answer accuracy complaints within 4 hours.

Validation experiment

Manually verify the output of the first five scans against the buyer's own archive-time Xcode privacy report and count mismatches.

Kill criteria

If more than 1 in 5 delivered bundles needs a manual correction, stop selling and spend two days on the rule engine before more outreach.

Risk 3Community moderators treat free-scan replies as spam and remove posts, killing the only channel.

Mitigation

Always lead with the actual scan output in the reply itself so the post has standalone value, and never post the same text twice in one subreddit.

Validation experiment

Track removal rate across the first 25 replies and compare a value-first reply against a link-first reply.

Kill criteria

If more than 30 percent of replies are removed, shift the channel to X DMs and stack overflow answers only.

Risk 4The 35-customer projection is unvalidated and may be off by a large multiple.

Mitigation

Measure reply-to-scan and scan-to-paid conversion daily from day 8 and adjust outreach volume rather than price.

Validation experiment

After 60 replies, compute the actual scan-to-paid rate and recompute the 30-day customer count from it.

Kill criteria

If scan-to-paid conversion is below 3 percent after 100 delivered scans, the $99 price or the artifact itself is wrong and the offer must change.

Risk 5The generated xcodeproj attach script breaks on unusual project structures and creates support load a solo founder cannot absorb.

Mitigation

Always ship manual attach instructions alongside the script and cap the worker at 10 minutes so a bad job fails fast instead of hanging.

Validation experiment

Run the script against five public open-source iOS projects with different target layouts and record failures.

Kill criteria

If the script fails on more than 2 of 5 public projects, demote it to a documented optional step.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Search r/iOSProgramming, r/SwiftUI and Stack Overflow for privacy-manifest threads from the last 90 days.
  • Copy the verbatim Apple error strings and the API each poster named into a tracker.

Output: A 40-row tracker with URLs, handles and quoted error strings.

Hours 3-5

  • Scaffold the Next.js app on Vercel with /upload and /thanks.
  • Create the Supabase jobs table and the R2 bucket with pre-signed URL helpers.

Output: Deployed skeleton that accepts a zip and stores a job row.

Hours 6-9

  • Implement the Swift rule engine for UserDefaults, file timestamps, systemUptime, disk space and active keyboard queries.
  • Emit file, line and matched symbol per hit and run it on one local project.

Output: CLI that prints a real hit list with file and line.

Hours 10-12

  • Generate one PrivacyInfo.xcprivacy for a single target and validate it with plutil.
  • Write the first version of the public free-scan reply, with the scan output pasted in.

Output: A validated sample manifest and a ready-to-post reply draft.

Complete report

Full 30-day launch report

Read the full generated report

Manifest Doctor - 30-Day Solo Launch Report

1. Product opportunity and positioning

Apple requires every iOS app target to ship a PrivacyInfo.xcprivacy file declaring required-reason API usage. Xcode's privacy report only appears after you archive, only lists what Apple detected, and never writes per-target manifest files. The triggering calls - UserDefaults reads, file timestamp access, system uptime checks, disk-space queries, active keyboard queries - are scattered across hundreds of Swift and Objective-C files and often buried inside third-party packages. The developer discovers the gap at submission time, then hand-audits the tree, guesses reason codes and hand-writes a plist per target under deadline.

The buyer is the iOS lead engineer or solo developer at a 1-50 person app company, or a freelance iOS contractor carrying two to five client apps, with a submission already scheduled in the next 30 days. That trigger is public and dated, which is what makes this sellable without a brand or a sales function.

Positioning is deliberately pre-commit. One zip in; one committable bundle out: manifests per target with reason codes, a call-site table with file and line, an SDK gap list, a Ruby xcodeproj attach script, and an App Store Connect answer sheet.

JEV scored this 6.22/10 (band C, confidence 0.52). Strengths: speed to first revenue (8.23) and reachable customers (7.14). Weaknesses: monetization (4.74) and operational simplicity (4.0). This plan attacks both without changing the wedge - price is anchored to a dated submission and to a contractor pack that creates repeat purchase, and delivery stays stateless on managed services with no human review and no custom infrastructure.

2. Smallest sellable MVP

Sellable means a developer drops a project zip and receives a bundle they can commit within ten minutes. Nothing else is needed for the first $99.

In scope: the Swift/ObjC scanner, the per-target manifest generator, the dependency gap inspector, the Ruby attach script, the App Store Connect answer sheet, Stripe checkout on the TrustMRR-connected account, emailed 7-day download link, the free count-only scan, and a local CLI so source never has to leave the machine.

Out of scope for all 30 days: GitHub App or CI hooks, Android/React Native/Flutter, App Store Connect API upload, privacy policy generation, team seats and audit logs, and any curated SDK reason-code database. The tool reports only what is physically present in resolved packages.

3. Technical implementation plan

Next.js on Vercel serves the landing page, the upload form and the free-scan endpoint. The browser gets a pre-signed R2 PUT URL, uploads the zip, then a route writes a Supabase job row and triggers a Python worker. The worker unpacks into a 25 MB-capped temp directory, detects targets from the .xcodeproj, runs tree-sitter-swift (with an Objective-C regex fallback) over the tree, and generates the five artifacts into a result zip on R2. Stripe webhook flips the job to paid; only paid jobs receive a signed link, delivered by Resend. Source archives are deleted after the scan or after one hour, whichever comes first.

Build order is fixed: scaffold, target detection, rule engine, manifest emission, dependency inspection, attach script, answer sheet, payments, email, CLI. The hardest risk is target mapping - multiple targets, extensions and CocoaPods workspaces - because a wrong mapping silently ships a non-compliant build. Mitigation: validate every plist with plutil, and always ship manual attach instructions beside the script.

There is no model in the generation path. Reason codes are deterministic rule matches. An optional small-model pass turns the call-site table into one plain-English paragraph per target, and its failure never blocks delivery.

4. Pricing and monetization

Two one-time prices: Single App Fix, $99 for one project, and Studio Pack, $249 for five projects with 12 months of rescans. No subscription, no seats.

The $99 is anchored to a dated event: one rejected submission or one resubmission costs more in delay than the tool costs. The Studio Pack exists specifically to answer the JEV monetization weakness - a contractor with three client apps is a repeat buyer, and the rescan link keeps the project on file for the next submission.

First revenue offer this week: a free scan of one file or public repo posted publicly, followed by the $99 checkout link in the same reply. Upsell path: free scan, then Single App Fix, then Studio Pack when the buyer mentions a second app.

5. First-customer acquisition

One channel: organic free-scan replies in r/iOSProgramming and r/SwiftUI, backed by direct X messages to developers who posted recent App Review rejections. Zero paid spend in the conservative and base cases.

Loop: search matching threads, post the actual scan output with matched call sites and the fixing manifest entry, log it, offer the paid bundle, follow up once after 72 hours with the still-undeclared call sites. Reply within minutes of a new thread - the buyer is on a deadline and posts when they are already stuck.

Week one goal: 25 free scans delivered and 12 checkout links sent, with the first paid checkout by day 12. Guardrail: if more than 30 percent of replies get removed as spam, shift to DMs and Stack Overflow only.

6. 30-day execution roadmap

Week 1 (days 1-7) - build and go live. Day 1 validates threads and quotes real error strings. Days 2-5 build the pipeline and reach the sellable MVP on day 5. Day 6 ships the CLI to kill the upload objection. Day 7 turns on live Stripe and the free-scan lead magnet.

Week 2 (days 8-12) - first money. Two 10-reply outreach batches, 20 X DMs, 15 free scans delivered, a 72-hour follow-up wave and a hand-delivered first sale on day 12.

Week 3 (days 13-19) - accuracy and trust. Cut false positives, publish an open-source case scan, open Studio Pack conversations, publish retention controls, ship the required-reason API cheat sheet, capture permissioned quotes, cut the worst channel.

Week 4 (days 20-28) - scale and harden. Double volume in the winning channel, add a second inbound surface, automate the rescan email, cut scan cost below a minute, add plist self-checks and a limitations section, follow up every warm lead twice, publish counted data from your own jobs, fix the three worst attach-script failures, and hold day 28 as a support buffer.

Week 5 (days 29-30) - close. Drain the pipeline, deliver every outstanding scan, confirm settlements, write the post-mortem with verified numbers only.

7. Revenue and profit scenarios

All three are projections, not verified revenue.

  • Conservative: 3 customers, $99 blended ARPU, $297 gross. Refunds $0, chargebacks $0, fees $11, ad spend $0, operating $25. Hackathon profit $286; business profit $261.
  • Base: 12 customers, $124 blended ARPU (a minority take the $249 pack), $1,488 gross. Refunds $99, chargebacks $0, fees $52, ad spend $0, operating $60. Hackathon profit $1,337; business profit $1,277.
  • Upside: 30 customers, $129 blended ARPU, $3,870 gross. Refunds $99, chargebacks $0, fees $140, ad spend $150 on a promoted X post, operating $140. Hackathon profit $3,481; business profit $3,341.

Fees assume Stripe at 2.9% plus $0.30, roughly 3.2-3.6 percent of gross. Every sale covers its own delivery cost.

8. Main risks and validation experiments

  1. Source upload refusal. Ship the CLI in week one; test web-scan versus CLI replies on consecutive days. If fewer than 3 of 20 offered scans are accepted, the model is wrong.
  2. Scan accuracy. Manually compare the first five bundles to the buyer's archive-time privacy report. If more than one in five needs correction, stop selling for two days.
  3. Community removal. Track removal rate over the first 25 replies. Above 30 percent, move to DMs and Stack Overflow.
  4. Demand projection. Recompute the 30-day customer count from actual scan-to-paid conversion after 60 replies. Below 3 percent after 100 scans, the price or artifact is wrong.
  5. Attach-script failure. Test against five public open-source projects. More than two failures means demoting it to an optional documented step.

9. First 24-hour action plan

  • Hours 1-2: build the 40-thread tracker with verbatim Apple error strings.
  • Hours 3-5: deploy the Next.js skeleton, Supabase jobs table and R2 pre-signed URLs.
  • Hours 6-9: implement the five required-reason API rules and run the CLI on one local project.
  • Hours 10-12: generate and plutil-validate one real manifest, and draft the free-scan reply with the output pasted in.

End of day one you should have a validated sample manifest and one reply ready to post the moment the pipeline is live.

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 →