Fifteen years of building software that works.

The founding story

Janagaran and Ramalakshmi started Maaya in 2011 because the ERPs available to Indian SMBs were a false choice: either the global giants (SAP, Oracle) at prices and timelines that didn’t fit, or the commodity options that needed to be rebuilt before they could run the business. They decided to ship a third option — enterprise depth with SMB reality, customised at the code level with named accountability.

Fifteen years later, the portfolio has grown to six products and the company has served 453+ customers across 13 countries. The second-generation team continues with the same principles: ship what works, explain what doesn’t, never make claims without proof.

The Pi Family, explained

Every product after MaayaERP carries a Pi suffix — PoultryCare, RestoPi, FeedPi, StratoPi, LivMatrix. It’s a deliberate family signal: same engineering backbone, same implementation standard, same consultant model, purpose-built surface per sector.

Three governing rules

Every decision inside Maaya is tested against three rules. They’re written down, repeated weekly, and occasionally broken — but only after we argue about it.

1. Reveal or Obscure. Pick a side. Half-honesty is worse than either.
2. Earn or Claim. If you can’t back it up, don’t say it. If you can, say it plainly.
3. Reward the Curious. A customer who asks harder questions should get deeper answers, not a thicker sales deck.

By the numbers

• 453+ customers across 13 countries.
• 15 years continuously shipping.
• 32 modules across the product line.
• AWS Marketplace listed and billable.

What we won’t change

• Named accountability. Every customer has a single consultant. No ticket queues, no escalation mazes.
• Code-level customisation. Your operation is not forced into our mental model.
• Quarterly review rhythm. Post-launch isn’t a support contract — it’s a relationship.