We capped Free at 1 invoice on purpose — here’s the tradeoff
A lot of invoicing tools win attention with unlimited free. We didn’t.
On InvoiceSnap (invoicesnap.ca), Free is a 1-invoice preview (watermark, no logo). That feels strict next to Wave-style free volume — and it’s intentional:
- You can judge PDF quality without a card
- Unlimited branded invoices sit on Pro at $4.99/mo (our wedge vs suites that often start around $19–$36/mo — list prices)
- Email send + Projects & Time live on Business $9.99/mo, not stuffed into Free with a bait switch
Not competing on contracts / CRM / pay-now — focused invoicing only.
If you’re building a Free tier: curious how you decide preview vs forever-unlimited?
(If useful: try one invoice at https://app.invoicesnap.ca — still no card.)
Site: https://invoicesnap.ca
—
Cameron M Deans
InvoiceSnap
https://www.linkedin.com/in/cameron-d-816308b2
Good framing — splitting PDF-quality vs validator/workflow cohorts is exactly how we’ll keep the second-invoice and 7-day return signals clean. Still early; we’ll let those cohort returns decide whether the one-preview boundary is teaching the right next step.
— Cameron M Deans
That framing is exactly right: tie the cap to the proof question. I’d keep the PDF-quality test and the validator/workflow test as separate cohorts, then compare second-invoice intent and 7-day return within each. That should show whether the limit is teaching the right next step without conflating the two jobs.
Yes, separating those jobs should keep the read honest. We’re watching first-export quality separately from second-invoice and 7-day return intent; if someone needs repeat branded invoices, Pro is $4.99/mo. Still early, so we’ll let the data decide.
— Cameron M Deans
The "1 invoice free" cap isn't just a pricing decision - it's a measurement boundary. Unlimited free measures nothing. You don't know if customers leave because the product doesn't work, or because they're waiting for a reason to upgrade.
With 1 invoice, you measure whether someone gets value fast enough to do it twice. That's a real signal. It's also the point where you learn the customer cares enough to check that "wait, I need this paid" moment. The people who do it are telling you they measure themselves differently - they count invoices, not features.
And the free-to-paid conversion rate becomes your clearest measurement of product-market fit. Not signups. Not DAU. Conversion. Because you've made it impossible to lurk.
Exactly. The useful signal is not conversion in isolation; it’s whether someone gets enough value from the preview to come back for the next invoice. We’re tracking that return and second-invoice intent alongside upgrades, while staying honest that the sample is still early.
Respect for stating the cap out loud — most founders disguise the free tier as generosity when it's really a conversion experiment with feelings attached. The question I'd pressure-test: where do your 1-invoice users hit the wall? If it's a team-size wall, they outgrow you and upgrade naturally. If it's a value wall — they never scan enough to see the product work — the cap quietly kills your best salesperson. Same dilemma I had with a free scan tier, and the answer changed twice.
Thanks! Keeping the boundary simple is helping us learn without over-building the pricing model. The important test for us is whether the preview gets someone to a real next job; if it doesn’t, we’ll revisit the shape rather than assume the cap is automatically right.
Completely agree with this perspective. Keeping things simple early on really helps avoid over-engineering. Thanks for sharing!
Yes—one sample can prove the output, but not necessarily the recurring workflow. We’re separating “the PDF looked good” from “I came back for the next job,” and using that second signal to judge whether the boundary helps or just interrupts an active use case.
The one-invoice preview makes sense as a quality gate because it lets someone judge PDF output without a card, but the watermark/no-logo choice also makes the value boundary visible. I’d watch second-invoice conversion separately from generic signup conversion; the product is asking users to experience the exact moment their workflow becomes recurring. If that cliff is too sharp, a delayed or sample-data path might preserve the constraint without making active users stop mid-job.
That’s the distinction we’re trying to preserve: a useful “aha” first, then an honest signal of recurring need. We’ll watch activation and upgrade triggers separately, because loving the workflow and needing it every month are different things.
The strongest free-tier test is whether the free action creates a useful “aha” without requiring a long-term commitment. I’d watch activation and the first upgrade trigger separately: a free user can love the workflow but still not have a recurring need. The cap feels much easier to defend when it is tied to the moment the customer gets ongoing value, rather than an arbitrary usage limit.
I like that distinction. We’re instrumenting first export and return-to-create separately; drafts are a reasonable hypothesis, but we want to avoid adding a workaround before we see where real users actually stop. The second job is the cleanest test for recurring value.
That’s the honest question, and it’s too early for us to claim a signup or paid lift. We’re comparing the full path—signup to first preview, return intent, and upgrade—rather than optimizing one number. If the cap reduces learning or blocks legitimate use, we’ll adjust it.
The preview-vs-habit distinction is the bit I’d watch. I’d instrument the first export and then the return to create a second invoice separately—those two events tell you whether the cap proves output quality or just cuts off a real workflow. Have you considered keeping drafts unlimited while charging for the second sent invoice?
That’s a good test. We’re treating drafts as a possible way to preserve learning, but for now the one live invoice is our simplest proof point. We’ll watch whether users return for a second invoice—and whether a recurring allowance helps occasional users—before changing the boundary.
— Cameron M Deans
Smart move doing this on purpose. To answer your question, I think a preview works when people can see the value right away, like one PDF invoice. It doesn't work when the value takes weeks to show. I have a digital product for $39 and I'm not sure if I should give a free Lite version to build trust. My question: after you capped Free at 1 invoice, did signups drop or did more people pay?
That’s the clean signal we’re hoping for: separating evaluators from people with a recurring invoicing need. I agree the hard part is not relaxing the constraint just because top-of-funnel looks smaller. We’ll let repeat use and paid retention—not signup volume alone—guide the decision.
This is a sharp insight dressed up as a constraint. The 1-invoice limit actually makes your conversion metrics intelligible - you're separating "people evaluating the UX" from "people who need to invoice." That distinction is everything.
With unlimited free you're measuring noise (did they convert because of value, or because they already had access?). Here you know: if someone upgrades, it's because the paid tier solved an actual need they discovered in that preview. That's clean signal.
The hard part isn't the constraint - it's resisting the urge to relax it when signup numbers look lower. But you're right to keep it tight. Your retention curve on paid users probably tells a much truer story about product-market fit than a Wave competitor's, even if their free cohorts look bigger on day 30.
The recurring-vs-one-off distinction is exactly why we chose a one-invoice preview for this product. A time-zone conversion can be complete in one use; invoicing usually repeats. We did consider a larger usage allowance, but the simpler boundary gives us a clearer test: does the next job matter enough to return?
This resonates a lot. I run a completely free tool (GMT-EST time zone converter, no signup, no card, no paywall at all) and the tradeoff you're describing is real either way — going fully unlimited-free gets faster word-of-mouth and adoption, but you're leaving zero room to eventually monetize without backlash from existing users. Your "1 invoice preview" approach is smart because it lets people judge quality without feeling nickel-and-dimed. For a tool like mine that's inherently simple and one-off (people just need one conversion at a time), the free-forever model probably makes more sense — but for something like invoicing where usage is recurring, your tiered approach seems like the right call. Did you consider a usage-based free cap (e.g. 3 invoices/month) instead of a hard 1-invoice ceiling, or did you rule that out early on?
Your property-level cap is a good example of pricing on the unit that maps to value. We’re applying the same principle to invoices, though our first test is a one-time preview rather than a standing allowance. The useful comparison will be repeat creation and upgrade intent, not just who signs up.
That’s a real risk for occasional freelancers. One preview may prove quality but not build a habit, so we’re segmenting repeat intent by use case rather than assuming everyone has monthly volume. A small recurring allowance remains a hypothesis if the one-time boundary creates too much friction.
I landed on a forever-free tier, but capped on the unit that actually maps to value. My product is for landlords, so Free is 1 rental unit, permanently, and paid plans are priced per unit (5, 25, 100). Capping by property instead would have let someone run a 4-plex on the free plan.
The other choice I made: no standing 14-day trial. The trial starts at the moment someone hits a gate that matters (adding a second unit, importing a CSV, exporting tax reports), so the clock only runs once they're actually trying the paid part.
Honest caveat: I haven't had enough signups to prove it converts better, so this is design reasoning, not data. Your preview-vs-habit question is the right one to measure.
That’s a thoughtful unit/value mapping. The “trial starts at the gate that matters” approach is especially useful—we’re similarly trying not to confuse a successful preview with recurring need. We’ll compare repeat use and upgrade intent before treating the cap as proven.
— Cameron M Deans
I get the logic, but I’d be careful with the 1-invoice cap because occasional freelancers might be exactly the users who don’t need unlimited volume yet.
For them, one invoice may prove the PDF works, but not whether the product is worth coming back to.
Personally I’d test whether a small recurring free allowance converts better than a one-time preview. The real question is whether Free helps users build a habit, or just lets them test once and leave.
Yes—the second-invoice event is the important follow-up to the first PDF. We’re tracking it separately from repeat logins and treating the payment workflow as a different problem from invoice creation. Still early, but that split should tell us whether the preview boundary is doing its job.
Interesting framing—using the first invoice as a quality/activation test seems cleaner than an arbitrary usage cap. For freelancers, the hard part after the PDF is getting paid; I’m testing that workflow in Close & Collect OS, and put a short MicroLaunch teaser here if useful: https://microlaunch.net/p/closecollectos. Curious whether you’ll track second-invoice creation separately from repeat logins.
The “getting paid” problem is important, and I agree it’s adjacent to invoicing but not the same job. We’re keeping the first experiment focused on whether the invoice output and repeat workflow earn a return; your export-vs-core split is a useful reminder that the right gate depends on what the customer must verify.
In my experience building compliance calculation tools, deciding where the free line falls is always tricky. When I tested strict one-off previews, users often bounced because they couldn't verify edge cases. In my case, keeping the core math and utility free while gating the actual export and recurring filing reports usually converted much better. A tight preview might protect against free-riders, but letting users fully test the workflow first tends to build genuine trust before asking for a card.
Agreed on unlimited drafts as a possible way to preserve learning, especially for someone testing edge cases. We’re starting with the simpler boundary because one live PDF answers our core quality question; if users need repeat workflow to trust it, that’s a strong case to expand the test path.
The no-card preview is a strong trust signal. I’d watch whether one live invoice is enough for a new freelancer to test the full workflow; one live invoice plus unlimited drafts could preserve the boundary while letting them experience repeat usage. The watermark/no-logo tradeoff also feels like a clear upgrade path.
That validator use case is a great example of when one sample is the wrong instrument. For our PDF-focused workflow, one preview can answer the quality question, but we’re still watching whether the watermark or the count is the bigger friction point. Different product, different proof threshold.
Mostly the count so far — one free sample is enough for people to judge PDF quality. Watermark hasn’t been the main complaint; hitting the free-cap is. Sounds like your e-invoicing case needs a higher free threshold before the proof sticks.
That’s useful signal—thanks for separating the two. If hitting the cap is the main complaint, we’ll test whether one preview is too tight rather than assume the boundary is right. For now it’s still Free = one watermarked preview; we’ll let repeat use and return intent decide.
— Cameron M Deans
Makes sense to let return intent decide. One metric that helped me elsewhere: among people who hit the free cap, what % come back within 7 days vs convert. If return is high but convert is low, the boundary is teaching the workflow but not the upgrade — usually means the free sample ends one step before the aha.
Good luck with the test.
That’s a great example of the cap needing to match the proof the user needs. If the real question is validator acceptance, one PDF would be too weak a test; 20 documents gives enough room to validate the workflow. Our narrower cap fits the first question we’re asking—whether the PDF output is usable—so we’re treating it as a preview, not a claim that one sample proves the whole invoicing workflow.
— Cameron M Deans
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?
That framing resonates. We want the upgrade prompt to explain the value of the next job, not just announce a wall, and we’re tracking second-invoice intent separately from signup conversion. That should show whether the limit creates a useful handoff or unnecessary friction.
I like the distinction between proving the output and providing a permanent substitute. For us, the key test is whether the first invoice gives enough confidence to justify returning for the second; if not, changing the cap won’t solve the underlying value gap.
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.
That’s a useful framing. We’re separating “proof the PDF works” from “need to run this workflow repeatedly,” and the second-invoice event should help us tell those apart. We’ll keep an eye on time-to-return and upgrade intent rather than assume the cap is automatically right.
— Cameron M Deans
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?
That’s the right segmentation question. We’re separating occasional users from repeat operators and watching whether the first invoice proves enough value to return, not assuming a single conversion rate explains both. If occasional use proves to be the friction point, a small recurring allowance is a hypothesis we can test alongside the current Free=1 preview.
— Cameron M Deans
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.
Agree — time-to-second-invoice is a cleaner guardrail than conversion alone.
We’ll segment real-client vs test first invoices, then compare repeat use / abandonment / Pro upgrades. That should show whether the Free=1 preview creates urgency or just interrupts a real workflow. Still early; no pattern claimed yet.
Pro stays $4.99/mo (unlimited branded); Business $9.99/mo (email + Projects & Time).
— Cameron M Deans · InvoiceSnap (invoicesnap.ca)
LinkedIn: https://www.linkedin.com/in/cameron-d-816308b2
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?
That’s exactly the question we’re watching. The cap is intentionally a preview, so we’ll compare second-invoice intent and Pro upgrades against abandonment rather than assume the cap wins. Pro is $4.99/mo for unlimited branded invoices; the free preview keeps the watermark and no logo. We’ll make the upgrade path explicit after the preview—thanks for calling out that value threshold.
— Cameron / InvoiceSnap
That second-invoice vs. abandonment test is the key signal. If you’re open to it, what’s the best email to reach you on?
No need to share an email — happy to keep the discussion here. We’re watching second-invoice intent alongside return rate and Pro upgrades, rather than treating one conversion as proof the cap works. Appreciate the thoughtful question.
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.
Totally fair — one invoice proves the output quality, but not the recurring workflow. That’s why we’re watching return and second-invoice intent rather than treating a successful preview as conversion.
The ongoing value is in using it repeatedly: Pro is $4.99/mo for unlimited branded invoices, and Business is $9.99/mo with email send plus Projects & Time. We’ll keep that handoff explicit once the preview is done.
— Cameron / InvoiceSnap
That distinction makes sense. I’d treat second-invoice creation as the activation event and track it alongside time-to-return and upgrade rate; the watermark/removal handoff should make the value boundary clear without overloading the free preview. Curious whether you’ll segment that by freelancer versus small-team usage.
Yes, that split should be useful. We’ll segment return, second-invoice intent, and upgrades by solo freelancer versus small-team usage, but it’s still too early to claim a pattern. The boundary stays simple for now: one free preview, Pro at $4.99/mo, and Business at $9.99/mo with email send plus Projects & Time.
This comment was deleted 8 days ago
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?
Yes — that’s the right funnel to watch. We’re tracking what happens after the preview (returning to create a second invoice and interest in paid features), but it’s too early to claim a result or pretend we’ve proven the cap works.
The free invoice answers “does the PDF work for me?”; repeat use answers whether the workflow is worth paying for. If the handoff feels too abrupt, that’s the part we’ll revisit. Pro is $4.99/mo for unlimited branded invoices; Business is $9.99/mo with email send plus Projects & Time.
Appreciate the thoughtful push on this. — Cameron / InvoiceSnap