We capped Free at 1 invoice on purpose — here’s the tradeoff

I build an e-invoicing API and went a third way, decided by what the prospect actually has to check. The question a new user is answering is not "does this look nice", it is "does the file my customer's system receives pass their country's validator". One sample cannot answer that, so a preview would have been the wrong instrument however good it looked.

So free is 20 documents a month, every feature on, no watermark, no card. Small enough that a real business outgrows it in a week, big enough to run their own invoices through and read the validation output.

Yours is a genuinely different case, since PDF quality you can judge from one sample. Has anyone told you the watermark put them off, or is it only the count?

The one-invoice limit is a clean positioning choice because the free version proves the core output without becoming a substitute. I’d watch the moment users hit the cap: if they have already experienced a good PDF, the upgrade prompt can frame Pro around the next job’s time saved rather than extra features. Tracking preview-to-second-invoice conversion should tell you whether the limit feels like a useful boundary or just friction.

The one-invoice preview is a useful way to test value without requiring a card. I’d watch not only free-to-paid conversion, but whether that first invoice teaches the recurring workflow: branding, client follow-up, and reminders. If the watermark creates the upgrade moment, a short “what changes on Pro” comparison at export could make the boundary feel like a product lesson rather than a hard wall. How are you separating price sensitivity from users who only need occasional invoices?

A useful guardrail may be time-to-second-invoice, not just the conversion rate. Segment by whether the first invoice was a real client invoice or a test, then compare repeat use and abandonment; that should show whether the cap creates urgency or just blocks a real workflow.

The tradeoff seems measurable. Have you seen the 1-invoice cap push more users into Pro, or does it mostly increase abandonment because they haven't experienced enough value before hitting the limit?

The deliberate constraint makes sense if the first invoice is doing the job of a product demo. I’d watch second-invoice conversion closely and make the upgrade path explicit right after the preview—especially around watermark removal and saved client details. That keeps the free tier useful without training users to expect unlimited volume.

The one-invoice limit makes sense as a product preview, but I would watch whether users can experience enough of the recurring workflow to understand why they need Pro. Someone creating one invoice may confirm that the PDF looks good without encountering the ongoing problem the paid product solves.

Are you tracking what happens after that first invoice, such as how many users return intending to create another one or try a paid feature?