Login

I’m trying to figure out how to price my first SaaS product for small marketing agencies. I’m worried that if I set the monthly subscription too low, I’ll leave money on the table and struggle to cover my support costs, but if it’s too high, I’ll scare off the early adopters I desperately need for feedback.

I started with a low beta price, around 25 a month, then nudged it to 49 after a couple of months as we added features and cut support headaches. The real learning was that the cost hub wasn’t just money, it was what they could accomplish with our tool. I kept onboarding tight and used a simple self‑serve model to avoid extra handholding.

We asked a dozen potential customers what they'd pay for outcomes, not features, and the range kept landing around 40–60 a month. We ran a two‑week trial with both prices, tracked activation and install rate, and watched support tickets spike when price and value didn’t align. Ended up with a tiered plan that seemed fair to both sides, but it wasn’t perfect.

First launch I priced too low and saw a burst of signups but high churn as soon as they hit the first barrier. We cut price further to 19 hoping more would try, but the volume didn’t compensate for the reduced margins and I ended up burning more time on discount maintenance than sales.

I find myself spending more time tweaking onboarding emails and activation triggers than arguing about price. The price always feels like a lever, but maybe it’s the product‑market fit or setup costs that are the real bottleneck. Do you think the problem is the price or something else entirely?

Login
Username:
Password:	Lost Password?
	Remember me