The Forex SaaS That Cost What We Thought We Were Worth (And Why That Almost Killed Us)

When I joined Finvestfx, we had a problem I'd never dealt with before. We'd built a treasury and forex management SaaS for mid-sized companies, and there was literally nothing like it in the Indian market.

No direct competitors. No pricing benchmarks. No SaaS multiples to lean on.

So we did what felt logical: we estimated our costs, added a margin, looked at what enterprise software "usually" costs, and landed on ₹2.5 lakh per year per client.

It felt reasonable. It felt defensible. It was also completely wrong.

We were pricing our effort, not their problem

Here's what we missed: our first few clients weren't buying "treasury management software." They were buying peace of mind for their CFOs who were manually reconciling forex transactions across 6 banks in Excel.

One client told me they'd had a ₹40 lakh discrepancy that took 3 weeks to trace. Another had missed a hedging window because their analyst was on leave and no one else knew the process.

When you frame it like that, ₹2.5L isn't expensive. It's suspiciously cheap.

But we didn't know that yet because we were stuck thinking about what we'd built (Django backend, React frontend, cool reconciliation logic) instead of what they were avoiding (compliance risk, operational chaos, CFO panic attacks).

The turn: I started asking what *not* having us would cost

About 4 months in, I changed my discovery calls. Instead of demoing features, I asked:

• How many hours a week does your team spend on manual reconciliation?
• What happens if you miss a regulatory filing deadline?
• Have you ever had a forex exposure you didn't know about?

Turns out, most of these companies had 2-3 people spending 15+ hours a week on treasury ops. That's real salary cost. Then there's the risk cost, which is harder to quantify but way scarier for a CFO.

One prospect casually mentioned they'd been fined ₹8 lakh by RBI for a late FEMA filing. Another had eaten a ₹25 lakh loss on an unhedged exposure.

Suddenly, our ₹2.5L price tag looked different. Not because we changed it, but because I started anchoring it to their reality, not ours.

I tested pricing by customer segment, not by feature tier

We had about 20 enterprise clients by the time I really started experimenting. Here's what I did:

For companies with <₹100 Cr revenue: kept it at ₹2.5L, positioned as compliance automation.

For companies with ₹100-500 Cr revenue: tested ₹4.5L, framed around risk mitigation and finance team productivity.

For larger companies (₹500 Cr+): quoted ₹7-9L and talked about audit readiness and real-time exposure tracking.

Same product. Same features. Different framing.

The smaller companies pushed back on ₹4.5L. The larger ones didn't even blink at ₹7L. One CFO literally said, "If this prevents one compliance screw-up, it pays for itself."

That's when I realized: in the absence of competitor pricing, you're not pricing the product. You're pricing the absence of the problem.

What I'd do differently if I had to do this again

If I were pricing a first-of-its-kind product today, here's the playbook:

Start with discovery, not cost-plus. Talk to 10-15 potential customers before you even think about a number. Ask what they're doing now, how much time/money it costs, and what happens when it breaks.

Anchor to their current spend, not your build cost. If they're paying 2 people ₹8L/year to do something manually, your ₹3L software is a steal. If they're paying ₹50K for a janky solution, your ₹3L product better have a really compelling "this will break and cost you more" story.

Test 3 price points across your first 20 conversations. You don't need a statistical model. You need to see where people wince, where they don't react, and where they ask "is that annually or per user?"

Segment by problem severity, not company size. A ₹50 Cr company with messy compliance is a better customer at ₹5L than a ₹500 Cr company that's already nailed their process.

Don't lock in annual pricing too early. We did 6-month pilots with 3 clients at different price points. It let us learn faster and adjust without burning bridges.

The real lesson: pricing is a discovery tool

At Sonic Linker, we launched our AI SaaS at $49/month. Within 2 months, we had users asking for a $499 enterprise tier because the ROI was so clear for their use case. We hadn't even built half those features yet.

Pricing isn't something you set and forget. It's a way to learn what your product is actually worth to different people.

When you have no competitors, you have no crutch. That's uncomfortable, but it's also an advantage. You get to define the category and anchor the value in a way that makes sense for the problem you're solving.

Just don't make the mistake we did: don't price what you built. Price what breaks if they don't have you.