Pricing a product where nobody pays in dollars

Almost everything written about SaaS pricing assumes a customer who will pay $49 a month without thinking about it. Build for value, they say. Charge more. Your price is too low.

Some of that survives the trip to a market like Romania. A surprising amount doesn’t, and the parts that don’t fail in ways that look like your product is wrong when actually your reference material was.

I’ve priced products in this market at BONO and Firmoscop. Here’s what held.

The advice that doesn’t survive

“Charge what it’s worth to them.” Value-based pricing assumes value converts to willingness cleanly. In a market where the alternative to your product is often an accountant’s nephew, a spreadsheet, or simply not doing the thing, the value can be genuinely high and the willingness still low. You’re not competing with another tool. You’re competing with “we manage”.

“Your price is too low, raise it.” Sometimes true. But this advice was formed in markets where a price rise loses you the bottom decile of customers. In a small market it can lose you the category — because there’s a psychological ceiling for “software like this” that has nothing to do with your value and everything to do with what the market has seen before.

“Annual plans with a discount.” Works. But the reason it works elsewhere is cash-flow smoothing for the vendor. Here you’ll find a chunk of your customers genuinely cannot commit a year ahead, not because they’re cheap but because their own revenue is that lumpy. Push too hard and you don’t get commitment, you get churn with extra steps.

“Land and expand.” Assumes the account grows. Many small businesses in a small market are stable by design — the owner doesn’t want twelve employees, they want the same six and better evenings. Your expansion revenue isn’t delayed; it isn’t coming.

What does survive

Anchor to what they already pay. Not to competitors’ software — to the line item your product displaces or reduces. Accounting fees, a part-time role, the cost of one bad debt. That number exists in their head already and it’s the only number your price gets compared to. Find it in the first conversation and you have priced correctly before you’ve built anything.

Price the outcome, bill the unit. People will pay for “don’t get burned by a client who doesn’t pay”. They will not pay per API call for the same thing, because per-call pricing asks them to do arithmetic about a risk they’d rather not think about. Same money, different question, very different conversion.

Make the cheapest tier genuinely useful. In a market where trust in software vendors is thin and hard-won, a crippled free tier reads as a trick. A small tier that solves one whole problem builds the credibility you need for the second sale. This is the trust argument applied to the price list.

Be transparent about price on the website. “Contact us for pricing” is a filter that works in enterprise and a wall everywhere else. A small business owner who can’t see a price assumes it’s expensive and leaves. You never learn they visited.

The thing that actually moves the number

Not the price. The payment friction.

I have watched more revenue lost to a bad payment flow than to a price that was ten percent too high. Card entry that fails on the second attempt. An invoice that doesn’t include the fiscal fields the customer’s accountant needs. A renewal that fires without warning and triggers a chargeback out of irritation rather than intent.

In a market where bank transfer is still normal and the customer’s accountant is a real stakeholder in the purchase, “can they pay you easily and account for it correctly” is a bigger lever than any pricing page experiment. It’s unglamorous, it’s mostly plumbing, and it’s where I’d spend the first week.

The mistake I’d warn against hardest

Pricing for the customer you want instead of the one you have.

It’s tempting to set a price that only larger companies will pay, on the theory that they’re less trouble and the market will grow into it. What happens instead: you get very few customers, you learn very slowly, and the feedback you do get comes from a segment that isn’t representative of anyone.

Small markets punish slow learning more than they punish low prices. You can raise a price later — it’s awkward but survivable, and existing customers can be grandfathered. You cannot recover the year you spent building for a segment you couldn’t reach.

Start where the volume is, learn fast, and let the price follow what you’ve proven.

The one number to know

Before you set a price, know what a customer costs you to acquire — not in ad spend, in hours of your attention. In a small market, most early sales are personal: a call, a demo, a follow-up, hand-holding through onboarding.

If a customer takes four hours of you and pays you the equivalent of one, the price isn’t the problem. The model is. Either the price goes up substantially, or the onboarding has to stop involving you — and figuring out which of those two you’re doing is the actual pricing decision.

Everything else is a rounding error on that.