6. Fundability
6.1 Would I invest at pre-seed or seed?
Pre-seed: No. There's no team, no traction, and the market is a regulated niche in one country. Well-funded players (Invopop, Storecove, Pagero/Thomson Reuters, Sovos, Avalara) already sell the multi-country, network-connected version. A developer API for one country's file formats is a good small business, not a venture thesis. I'd look again only if all of these were true:
- a founding team with e-invoicing or tax-technology background;
- a plan to become the multi-country transmission layer (access point, clearance connectors) for the ViDA 2030 wave;
- 50+ paying API customers with net revenue retention above 100%.
Seed: No. It would need repeatable acquisition, a multi-country product and enterprise sales, and none of that exists.
6.2 What a skeptical investor says in the first five minutes
- "Mustangproject is free and good. Why would a developer pay you?"
- "Billit is Stripe's preferred e-invoicing partner and free until 2027. How do you compete?"
- "What happens after the 2027 and 2028 deadlines pass? Is this a one-time migration market?"
- "How big is the set of companies that invoice from their own code, rather than using DATEV or lexoffice?"
- "You're not an access point. When Peppol becomes normal, aren't you just a file converter?"
- "Who on your team reads German tax guidance?"
- "What's your churn? Document APIs lose 5–9% a month."
- "What if Stripe builds it?"
- "Who's liable when an invoice is rejected?"
- "Why this team?"
Your answers must be crisp on 1, 3 and 7:
- (1) "Developers pay for the certainty, readable errors and maintenance, not the XML. Proof: X paying customers who tried the library first."
- (3) "The deadline brings them in, but the obligation is on every invoice forever. Once integrated, they stay until they stop trading. Our churn is Y%."
- (7) "Our buyers have no 'project end'. Measured revenue churn is Z%."
6.3 Three proof points that would flip my answer (for a small raise or an acquirer)
| # | Proof point | Threshold | Why it matters |
|---|---|---|---|
| 1 | Low churn, measured | ≤2.5% monthly revenue churn over 6+ months, with ≥100 paying customers | Proves the core thesis: an API inside a never-ending job doesn't stall like ScreenshotOne. |
| 2 | Expansion | Net revenue retention ≥105%. Customers grow volume or add inbound parsing, and an agency adds brands. | Shows the account grows with the customer's invoice count, not just holds. |
| 3 | Organic acquisition | ≥60% of new paying customers from the validator, search, docs or the Stripe App, with CAC payback under 2 months | Proves it grows without paid ads or a sales team. |
A strong fourth: a second country (France Factur-X or Belgium via a partner) adding ≥20% of new MRR. That shows the product travels.
6.4 Bootstrap or raise?
Bootstrap. Specifically:
- It's cheap to build. The format engines are free. The work is mapping, validation, error messages, docs and hosting. A solo developer can ship v1 in 6–8 weeks, and infrastructure costs well under 5% of revenue.
- Revenue arrives early. Design partners with a deadline pay before the product is complete.
- Raising would push the wrong strategy. Investors would want the multi-country access-point platform, which puts you against funded incumbents on their ground.
- The exit path is real without raising. DocRaptor, a bootstrapped document API with 1,800+ customers, was acquired by Artifex Software in October 2025. Likely strategic buyers for DocPress are accounting suites, billing platforms, PDF API companies adding e-invoicing, and Peppol access points that want a generation layer. Terms and multiples weren't disclosed or verified, so treat any valuation as unknown.
Honest bottom line: this is a profitable small-business idea, not a venture idea. That fits the goal of a steady, low-operations API. It is not a fit for anyone who needs a $1M ARR outcome in 3 years.