DocPress (originally "a developer API tied to a job businesses repeat forever")
Idea status: Idea stage · Target: an MRR ladder ($1k → $50k) instead of one fixed number · Verdict: No as a generic PDF or document API. Go as a German e-invoice API (ZUGFeRD / XRechnung) for developers · Last updated: 30 Sept 2026
Origin: this idea came from the 30 Sept 2026 micro-SaaS research. That research looked for a developer API tied to a job businesses repeat forever, after ScreenshotOne showed how project-based use caps growth.
Name: "DocPress" is a working name. Check trademark and domain before using it publicly.
Start here → WHAT-TO-DO-AND-AVOID.md for:
- odds at each MRR level, with the conditions met ($1k ~45–60%, $5k ~22–35%, $10k ~12–22%, $20k ~5–11%);
- customer math, the churn check, 12 do's, 14 avoids and checkpoints.
Which API, and why: four candidates were compared, with low customer churn as the deciding factor:
- invoice and business-document PDFs;
- EU VAT validation;
- regional address validation;
- a niche data feed.
Invoice documents won, narrowed to legally mandated e-invoices. Germany requires structured e-invoices for B2B from 1 Jan 2027 (turnover >€800k) and from 1 Jan 2028 (everyone). That makes the job a legal duty on every invoice, forever. See analysis/01.
Research was run on 30 Sept 2026, with a confidence level on each claim. See research/10-verified-research.md.
Folder layout
docpress/
├── WHAT-TO-DO-AND-AVOID.md ← final analysis and decision (read first)
├── README.md ← this index
├── analysis/ ← the investor-style assessment
│ ├── 00-one-page-brief.md
│ ├── 01-verdict.md
│ ├── 02-market-reality-check.md
│ ├── 03-feature-scrutiny.md
│ ├── 04-expanded-feature-catalog.md
│ ├── 05-pre-mortem.md
│ ├── 06-fundability.md
│ ├── 07-gaps.md
│ └── 09-assumptions-and-open-inputs.md
├── plans/ ← execution plans
│ ├── 08-90-day-plan.md
│ └── 11-24-month-gated-roadmap.md
└── research/ ← cited evidence
└── 10-verified-research.md
File numbers match the other ideas in this portfolio, so cross-references like "doc 08" work the same way.
Documents
| # | Document | What it answers |
|---|---|---|
| — | WHAT-TO-DO-AND-AVOID.md | Final decision: MRR ladder, customer math, profit and churn checks, 12 do's, 14 avoids, checkpoints |
| 00 | analysis/00-one-page-brief.md | The whole assessment on one page |
| 01 | analysis/01-verdict.md | The four candidates scored on churn, the MRR ladder for each, Tier A/B, fundable yes/no |
| 02 | analysis/02-market-reality-check.md | Buyer segments, pain scores, competitors (PDF APIs, e-invoice APIs, Stripe, open source), market size |
| 03 | analysis/03-feature-scrutiny.md | The stated candidates and their typical features, classified |
| 04 | analysis/04-expanded-feature-catalog.md | About 35 features, classified and prioritised for the wedge |
| 05 | analysis/05-pre-mortem.md | Top 3 causes of death, warning signs, whether each is fixable |
| 06 | analysis/06-fundability.md | Invest?, the skeptic's questions, proof points, bootstrap vs raise |
| 07 | analysis/07-gaps.md | Gaps to paid, renewed and referred customers, pricing, compliance map |
| 08 | plans/08-90-day-plan.md | First 90 days, week by week |
| 09 | analysis/09-assumptions-and-open-inputs.md | Assumptions made, and the inputs that would change the verdict |
| 10 | research/10-verified-research.md | Cited research with confidence levels, and what's still unverified |
| 11 | plans/11-24-month-gated-roadmap.md | Phases, gates, revenue path for each time commitment, budget guardrails |
Caveat
Team, hours per week, geography, German-language ability and budget were not provided. The assumptions are in analysis/09.
No verified base rate exists for bootstrapped B2B micro-SaaS reaching MRR levels, and no churn benchmark specific to developer APIs was found. All odds are judgment estimates.