One plan, $19 flat, everything included. bold or naive? (0 customers so far)

relnotely live with billing open and still zero paying customers is such a quiet post-build — write-once to page/widget/email is done, the audience isn’t. Soft free text-only week for that no-audience stall: one done sentence, then one next step a day. If you want, reply with the one small-SaaS founder place you’d show a real publish if the next step was five strangers, not another plan tweak.

One plan is the right call at this stage. Adding tiers before anyone’s paid just invents problems. Free to write, pay to publish also feels fair. That’s when the thing actually becomes public.

Hi ahnaf, I'm a QA engineer and I check products before launch. I read your pricing page and terms side by side, because "your changelog stays online if you stop paying" is the promise a careful buyer will lean on.

Section 3 of your terms says publishing, the widget and custom domains need a subscription. Section 4 says published pages stay readable at their existing addresses after a lapse. Someone on their own subdomain can't tell which rule wins for them, and the widget isn't covered by the lapse promise at all. One sentence naming both would settle it.

That's the public side only, the publish-to-paid step sits behind signup. Thanks for writing terms people can actually read.

free to write, pay to publish is the right shape. writing and importing is homework, publishing is the win. charging at the moment of value converts better than charging at the door, and your trial starting at first publish means the clock only runs once they have something real.

on the flat plan: the missing features are your future tiers telling you their names. nobody designs the team tier, customers do. when someone asks for SSO or seats, that request is the tier. until then one plan keeps the story simple, which matters more than the money at 0 customers.

On your second question, from someone who runs a small B2B services company on one flat price: the money you leave on the table with bigger teams is real, but it is not what breaks a flat plan. What breaks it is cost to serve.

The line I would look at twice is "more readers or subscribers never costs more." Your email sends scale with subscribers, and a single customer with a very large list can cost you more in sending than their $19 brings in. Put a fair use limit on email volume in your terms now, while you have zero customers, so it is a rule rather than a price hike later. Everything else on your list costs you roughly the same whether the customer is two people or two hundred, so flat holds up fine there.

On bigger teams: they will tell you what the second plan is, because they will ask for exactly the things you left out on purpose (SSO, seats, roles). When the first one asks and is willing to pay for it, that is your higher tier. Building it before that is guessing.

And if flat is the bet, make it visible. You chose it because others charge for the custom domain and the badge removal, so say that on the pricing page in one line. Flat pricing only works as positioning if the buyer notices what they are not being charged for.

One flat plan is neither bold nor naive - at 0 customers the pricing question is just unanswerable from the inside, because nobody has reached the value moment yet so you have no data on what it's worth. "Free to write, pay to publish" is well designed; leave it alone. What actually answers both your questions: onboard the first five customers personally, even write their first release notes with them. You'll learn whether the pain is writing the notes or getting them read, and those two pains carry very different price points. Where are you planning to look for those first five?

The "free to write, pay to publish" gate is the strongest part — you are charging exactly at the value moment, so I would skip the free tier. One flat plan holds until per-seat costs appear, and since you have deliberately left out team seats and SSO, that is not your problem yet. Honestly the bigger question is distribution: changelog buyers are usually founders already shipping something, so your own changelog running on relnotely is your best demo.

The thing that'll strain the flat plan isn't team size, it's subscriber email volume — that's the one cost in your stack that scales with your customer's growth rather than their usage, which is exactly the shape flat pricing handles worst.

Charging at the moment you publish makes sense to me. I went a different way for a different buyer

On the flat plan: it holds as long as the thing that grows with team size isn't in the product. You left out seats and SSO, so the first bigger team will hit that wall before they notice the price. I'd keep $19 and add a second plan only after three customers ask for the same missing feature, priced around that feature. Then the price list comes from requests instead of guesses about what teams want.

I'm a huge fan of the "Free to write, pay to publish" idea that you have going here. The main issue that I would be concerned with the free tier are bad actors within the situation. You have a seven day free trial listed, what's to stop people from creating a profile, starting the account, and letting it lapse after they've had it work through their changelog for that month? I have a feeling that seeing everything coming out finished, and THEN being asked the question, "Do you think this work is worth $19" would go much further than using it for seven days.

Food for thought.

“Free to write, pay to publish” is a clean value-moment gate — you’re charging when the changelog becomes a public asset, not when someone is still drafting.

I’d keep one plan until a real buyer asks for SSO or seats in writing. Flat pricing is easier to defend early than a ladder nobody has demanded yet. The piece that matters for trust is what stays live if they cancel: published pages staying up (write-only lock) is a strong “we won’t hold your history hostage” signal for teams comparing tools.

— Cameron M Deans

On the pricing question, one thing from someone also sitting at zero customers: with basically no audience, 0 at $19 isn't a price signal yet. Nobody has reached the card step, so the price hasn't been tested. I'd judge it after the first 20 people who actually hit "publish", not before.

One thing that costs you before price ever matters: your share image is only the "r" mark on dark green, 1200x630, no name, no line of text. The same image is on /changelog. So every link to relnotely in this thread, on X or in Slack shows a letter, and says nothing about writing a note once and publishing it to three places. That sentence from your post is the card.

On your two questions: 1) Keep "free to write, pay to publish." The value moment is the publish, so charging there aligns price with value — a full free tier mostly collects changelog tourists who never convert. If anything, make the first publish free so the upgrade triggers at the value moment, not before it. 2) One flat plan holds up longer than you'd think. The metric to watch is seats per account: when teams of 5+ start sharing one $19 login, that's your signal to add a team tier. Same with support — flat pricing dies when one account starts costing you 10x the support of another. Until either of those shows up, the simplicity is the feature.

The free to write pay to publish model is smart at zero customers because adding a full free tier mostly generates support load, not conversions. We run an SEO tool with a free scan that does over a hundred checks with no signup and no card required. Free users who will never pay outnumber real prospects by roughly fifty to one. The free tier taught us about the product but almost nothing about pricing.

At zero customers the real unknown is not whether nineteen dollars is right but whether anyone wants a standalone changelog tool enough to pay anything. AI helps here more than you would expect. The latest models are genuinely good at competitive positioning research: mapping how existing changelog tools frame their value, finding the gap you can own, and testing messaging angles before you spend months on distribution.

The feature restraint is your best pricing defense. The moment you add team seats and SSO, enterprise buyers expect enterprise pricing. Staying deliberately small keeps the flat nineteen dollars credible.

With zero paying customers so far, are you seeing any evidence that prospects reject the $19 price specifically, or is the bigger unknown whether they want a changelog tool at all?

I actually like the simplicity of the offer. At 0 paying customers, though, I’d be more concerned about proving the $19 value than optimizing pricing tiers. If someone can clearly see how the changelog saves them time or improves communication with users, $19 becomes an easier decision. I’d probably validate that before adding a free tier or more plans.

Not naive. One plan removes a decision, and custom domain + no badge are exactly what people resent paying extra for. I'd just watch whether "card at first publish" is where people drop; if the first 10 trial starts all stop there, test publishing to a preview URL without a card.

Flat and badge-free is a real differentiator in this category. I'd lead with it on the pricing page instead of listing it as one bullet among six.

On your two questions:

1. "Free to write, pay to publish" is fair, and for a changelog it's arguably better than a free tier. The value moment is the first publish, so that's exactly where the card should come in. One thing I'd add: a private preview of the page, widget and email before the card, so the 7-day trial doesn't start at the moment people are least sure.

2. One flat plan holds up longer than you'd think, because the teams that outgrow it will ask for exactly what you left out on purpose (SSO, seats, segmentation). When the third company asks for SSO, that's your second plan, priced for them, and the $19 plan stays honest. Don't invent it before then.

One thing to decide early: "your published changelog stays online if you stop paying" is a great trust signal, but put a number on how long, in writing, so you're not hosting abandoned pages forever.

Where are you looking for the first 10? Changelog buyers are usually the founder of a small SaaS, and they're easiest to find where they already post release notes.

with zero customers, i'd keep the one plan for now and treat the first 5–10 sales as interviews rather than optimizing tiers. the free-to-write/pay-to-publish split makes sense, but i'd spell out what happens to an unpublished draft during the trial so the boundary feels fair. have you tested whether people see the value more in the hosted changelog or the widget?

Love this angle. Building Xstream4K right now so this hits close to home — what made you look into it in the first place?