Skip to content
Idea AtlasSign in

DocPress

As described:StopNarrowed:Continue

No as a generic PDF or document API. Go as a German e-invoice API for developers.

e-invoicing · ~$75 a month per customer · last reviewed (next review by 29 Dec 2026) · 69 cited sources

Save
Share

← All research

1. Verdict

Why a ladder instead of one target

This idea is assessed at six MRR levels instead of one fixed target, the same as the rest of the portfolio. For a small developer API the useful question isn't "will it hit $20k?". It's how likely each level is, and what each level costs in hours.

The anchor: what base rate?

There is no verified base rate for bootstrapped B2B micro-SaaS reaching MRR levels from launch.

  • MicroConf's State of Independent SaaS surveys founders who already run businesses. It measures survivors, not launches. Its secondary citations also conflict ("70% under $1k MRR" in one place, "28%" in another). The reports couldn't be opened to check.
  • RevenueCat 2026 is verified, but covers mobile subscription apps:
    • all categories: 17.3% reach $1k a month within 2 years, and 4.6% reach $10k;
    • Business category: 14.7% and 1.6%. A B2B API needs far fewer customers for each level, so those numbers understate the chance at $1k. It also sells into a much smaller, harder-to-reach market, so they probably overstate it at $50k.

The odds below are judgment estimates. They're anchored to three real bootstrapped comparables:

ComparableTypePathChurn
ScreenshotOneScreenshot and PDF API, solo$10K MRR at ~28 months, $20K at ~37, now $32K9%/mo, "project ended"
APITemplate.io + CraftMyPDFDocument/PDF APIs, solo + 1~$15K at ~2 years, $50K at ~4 years (end 2024)~5%/mo, "no longer needed"
BannerbearImage/video generation API, solo~$400 MRR in late 2019, $10.5K in Jan 2021, ~$20K by mid-2021, $50K in Jul 2023, $1M ARR reported Sept 2025% not disclosed. "Low tier customers churn fastest, mid and high tier customers stay longest."

All three are survivors, and many similar APIs never reach $1k. Only Bannerbear reached $20k MRR within 24 months, and it did so in 2020–21, before AI-built clones. In Sept 2026 its founder wrote that "competing on features is over, because anyone can build any feature in a weekend now."

Step 1: which API? Churn decides

CandidateRecurring job?Churn evidencePrice per customerSubstitutesVerdict
Generic invoice / document PDFsPartly. Invoices recur, but many buyers use it for one-off documents and no-code projects~5%/mo at CraftMyPDF, 9% at ScreenshotOne (project-based)$15–90DocRaptor, PDFMonkey, APITemplate, CraftMyPDF, PDFShift, ScreenshotOne's PDF API, Gotenberg (~140M Docker pulls), plus native invoice PDFs in Stripe, Paddle, Lemon Squeezy, Chargebee, QuickBooksCrowded, substituted, and churn is middling
Mandated e-invoices (EN 16931: ZUGFeRD / XRechnung)Yes, by law. Every B2B invoice, every month, for as long as the company tradesNo direct benchmark. Reasoned: the need can't end while the customer trades, and they switch only if something breaks€29–199Open-source libraries, Billit (free on Stripe until 2027), Invopop (€500/mo), accounting suitesPick. Strongest churn logic, a dated demand wave, and Stripe leaves the gap
EU VAT / company-ID validationYes, at checkout and onboardingLow ARPA → ~6% median churn (ChartMogul <$25 band)$10–30Stripe validates automatically, VIES and VATcomply are free, and many clones existLow churn in theory, but tiny revenue and heavy substitution
Regional address validationYes, in checkout formsNo data. Probably low, since it's embeddedUsage-basedGoogle $17/1,000 with 5,000 free a month, Loqate, Ideal PostcodesRejected: data licence costs and legal risk (the GetAddress.io ruling)
Niche data feed (FX rates, holidays, etc.)YesNo data$10–100Free ECB rates, ExchangeRate-API free tierRejected: commodity data, and no moat unless you own the data

Why e-invoices win on churn:

  1. The need can't end while the business trades. ScreenshotOne's churn reason ("the project ended") can't happen. The duty stops only when the customer stops invoicing.
  2. Switching costs rise with every invoice. After an integration, stored validation reports and an archive, leaving means re-testing compliance, and no finance team wants that.
  3. The price sits in the lower-churn band. At a ~€65 blended ARPA, benchmarks put monthly churn around 3–4% (Recurly: 3.15% at $50–100). The need can't end, so ≤2.5% is a realistic target. That's a judgment call, not a published figure.

Odds at each MRR level (reached by month 24)

MRR at month 24Base rateAs described: generic invoice/document PDF APIVAT validation APIUK address API (licensed)Niche data feedRecommended, ~15 hrs/weekRecommended, full-time
$1kNo verified base rate30%30%20%20%45%60%
$3kNo verified base rate16%12%12%9%30%45%
$5kNo verified base rate10%6%7%5%22%35%
$10kNo verified base rate5%2%3%2%12%22%
$20kNo verified base rate2%<1%1%<1%5%11%
$50kNo verified base rate<1%<0.5%<0.5%<0.5%1%3%

The "as described" column and the other candidates' columns assume full-time work.

Recommended means the German e-invoice API set out in WHAT-TO-DO-AND-AVOID.md, with the 3 conditions met:

  • German-language capability plus a paid tax or e-invoicing adviser;
  • direct access to 30 buyers in month 1;
  • 3 paying design partners by day 21, and steady hours for 24 months.

If any one condition is missing, multiply the recommended odds by about 0.6.

These are judgment estimates, not computed statistics.

How to read the ladder

  • $1k–3k is realistic. It takes 14–40 companies at ~$75 a month, and the 2027 and 2028 deadlines give them a date to act by.
  • $5k–10k needs a second channel beyond search, most likely the Stripe App or agency partners. It probably also needs France (Factur-X) by month 18.
  • $20k is a stretch. Only one of three comparables did it in 24 months, in an easier year, and the German developer-buyer pool is finite.
  • Hours matter less here than in consumer ideas. The product is self-serve and search-led. The gap between 15 hours and full-time is mainly in how fast you ship formats and write content.

Portfolio definitions (for comparison with other ideas)

TierDefinitionRecommended, ~15 hrs/weekRecommended, full-timeAs described
Tier A (venture)$1M ARR within 36 months, ≥70% margin, ≥50% month-12 logo retention<1%~1%<0.5%
Tier B (profitable business)$20k+ MRR within 24 months, profitable, ≥80% gross margin, ≥70% month-3 retention~5%~10%~2%

Tier B is almost the $20k rung. Gross margin (~88–90%) and B2B month-3 retention aren't the constraint. The customer count is.

Compared with the other ideas in this portfolio:

  • At the $1k–5k levels, DocPress has the highest odds per hour worked, because a few dozen business customers are enough.
  • At $20k it sits between BhashaCity (3% / 6%) and CreatorDesk.
  • Its ceiling is limited by one country's developer market, not by churn.

Fundable in current form?

No. There's no team, no traction, and the market is a regulated niche. Funded players (Invopop, Storecove, Pagero/Thomson Reuters, Avalara) already sell to enterprises. The business doesn't need funding: build cost is low, and the first revenue can arrive in weeks. See 06-fundability.md.

One-paragraph verdict

The design rule is right: a developer API only compounds when it's embedded in a job that never ends. Of the four candidates, only invoices pass that test and have a dated legal trigger behind them. A generic PDF API doesn't qualify: it's crowded, and its churn (~5% or more) comes from the same project-based buyers that stalled ScreenshotOne. Narrowed to "JSON in, valid German e-invoice out, validated every time, with inbound parsing", it serves developers whose billing code must change by 1 Jan 2027 or 1 Jan 2028, and it stays in their stack for as long as they invoice. The real threat isn't a competitor. It's the free library plus a weekend of developer time. So sell certainty: validation, versioned rules, readable errors, German support and a Stripe connector. $1k–5k MRR is a sound expectation, $10k needs a second channel and a second country, and $20k is a stretch.