I Priced a Forex SaaS Product Using a Spreadsheet and Three Customer Calls. Here's What I Learned.
When I walked into Finvestfx, pricing was the first fire I had to put out. We were building treasury and forex management software for mid-sized businesses. The problem? Nobody else was doing exactly what we were doing. There were accounting tools, sure. FX platforms, yes. But our specific combination of real-time forex tracking, treasury reconciliation, and compliance reporting? That space was empty.
Enterprise clients were asking for quotes. I had no competitors to look at, no pricing pages to reverse-engineer, and a product that was still being stabilized. I needed a number that wouldn't kill deals but also wouldn't leave money on the table.
Here's what actually worked.
I Started With the Customer's Current Pain, Not Our Feature List
Most pricing advice tells you to look at competitors or do value-based pricing. Great. But when you have no benchmarks, value-based pricing is just a fancy way of saying "guess what they'll pay."
I called three finance heads at companies in our ICP. I didn't pitch. I asked one question: what does the current manual process cost you?
One CFO told me his team spent 15 hours a week reconciling forex transactions across five banks. That's nearly half an FTE at 60-70k per year. Another company was paying $2000/month for an FX analytics tool plus another $1500 for a separate treasury system, and they still had to export and merge data manually.
That gave me a ceiling. If we saved them half an FTE plus consolidation of two tools, I had a rough value band of $4000-5000 per month. Not scientific, but real.
I Built a Reverse P&L to Stress-Test the Price
This is where I learned that pricing isn't a marketing problem. It's a business model problem.
I opened a spreadsheet and worked backwards. If we priced at $3000/month per enterprise client, how many clients did we need to hit our revenue target? What did that imply for sales cycles, customer success load, churn assumptions?
At $3000/month with a 12-month contract, we needed 15 clients to hit our year-one goal. That felt doable. At $1500/month, we needed 30 clients. Our sales team was two people. That math didn't work.
This exercise killed a pricing idea before it became a problem. I almost priced us at $1800/month because it felt "safer." The reverse P&L showed me it would've starved the business.
I Offered Two Tiers, Not Because I Wanted To, But Because Clients Demanded Anchor Points
I launched with one price: $3200/month, annual contract. Within two weeks, three prospects asked the same question: "What's the basic version?"
They weren't trying to negotiate down. They wanted context. Is this the premium version or the starting point? Without a reference, $3200 felt arbitrary.
I added a second tier at $1800/month with fewer integrations and delayed support. Almost nobody bought it. But it did two things: it made the $3200 tier feel justified, and it gave prospects a decision framework. Paradoxically, adding the cheaper option increased conversions to the higher tier.
This wasn't aStrategyâ„¢. It was a reaction to customer confusion. But it worked.
I Didn't Nail Pricing on Day One. I Nailed the Mechanism to Adjust It.
Six months in, I realized we'd underpriced. Our best clients were getting $8k-10k/month in value but paying $3200. The problem wasn't the initial price. It was that I had no system to revisit it.
I built a lightweight framework: every quarter, review three metrics. Customer payback period (how long until they recover the cost in time saved), feature utilization (are they using the high-value modules?), and expansion revenue (are they asking for more seats or modules?).
When two clients asked for multi-entity support, I didn't bundle it into the base price. I created an add-on at $800/month. That became 25% of our revenue within a year.
Pricing isn't a launch-day decision. It's a monitoring system.
The Real Lesson: Pricing is a Forcing Function for Clarity
When you can't benchmark competitors, you're forced to answer harder questions. What problem are we actually solving? How much is that problem costing them right now? What's our operational reality?
At Finvestfx, I didn't get pricing perfect. But I got it defensible. I could explain to a prospect why we cost $3200. I could explain to our CEO why we couldn't go lower without breaking the business.
If you're in a similar spot, forget the frameworks for a minute. Call three customers. Build a reverse P&L. Ship a price, watch what happens, and adjust in 90 days.
Pricing without competitors isn't a disadvantage. It's just uncomfortable. And discomfort is usually a sign you're working on something that matters.