About Torotech
A small practice that ships AI you can audit.
Torotech is led by Ravi Soni, an SAP BTP and Fiori solutions architect with more than twelve years across food distribution, healthcare, consulting and event management — including time at KPMG and Philips. The AI and automation work grew out of the same discipline: propose before you post, and measure what changed.
How we got here.
Torotech is the generalisation of a career spent shipping software people actually use.
- 2010
Started in mobile
Shipped Blackberry and Android apps as a sole developer, then led mobile delivery — the first taste of owning a product end to end.
- 2014
Enterprise delivery at KPMG
Founded KPMG India's mobile technology team; ran SAP and non-SAP enterprise projects across the Middle East.
- 2017
Fiori at global scale, Philips
Founded Philips Healthcare's global Fiori team — architecture, DevOps and mobile Personas flavours used by teams worldwide.
- 2020
Leading a 30-person delivery team
Ran the S/4HANA Fiori migration and 40+ custom apps for a large Australian conglomerate — an estimated $5–10M in customer value.
- 2023
SAP BTP / Fiori architect, Mindfore Inc.
Building agent-driven S/4HANA apps and BTP extensions, onsite in the US — based in Houston, TX, working with a client in New Jersey.
- 2025
Relocated to Canada
Moved the practice to Kitchener, Ontario, continuing the same SAP engagement remotely and taking on Canadian clients directly.
- Now
Torotech
Everything above, generalized: the same discipline applied to websites, mobile apps, BI, SAP BTP, test automation and workflow automation.
Vision
Software your team trusts enough to stop double-checking.
AI and automation only earn their place when the person who owns the process can see exactly why the system did what it did.
Mission
Ship the first real result in days, not a discovery deck.
Every engagement is scoped to one process and one number you can check within the first month — or we don't start.
How we work.
The core stays clean
Extensions live on BTP. Agents talk to SAP through released APIs and CDS views. Upgrades stay boring — that's the point.
A person holds the pen
Every write-back is proposed first and approved by someone with the authorisation to do it by hand. Auto-approval is earned with numbers.
One process, one number
We scope to a process you can name and a metric you can check. If we can't measure it in the first month, we don't start.
Your repo, your infrastructure
Everything we build is handed over as code in your repository, deployed to infrastructure you own. No platform fee, no hostage.
Questions we get asked.
Yes. The read side (CDS views, OData) works on both. Write-backs on ECC go through BAPIs behind the same approval step we use on S/4HANA.
Tell us about the process that hurts.
A 30-minute call is enough to tell whether an agent, an extension or a plain good Fiori app is the answer. No deck, no discovery fee.