Nine services across three practices

There's no per-user licence, so your twentieth user costs nothing extra. It's open source, so whoever you hire next can read how your data is structured. And ERP, CRM, HR and analytics all run on one framework, so you aren't paying to connect four separate products. It isn't right for every business, though. If you need a specialised proprietary product for your industry, we'll tell you.

Your setup is stored in a repository as an app. Installing that app recreates your configuration, so if a site is ever lost, it comes back set up and only the data needs restoring. Every change is reviewed and tracked, instead of someone changing a setting by hand late at night.

You own everything built specifically for your business once the final payment is made. Reusable pieces, like a connector we use across an industry, stay ours and you get a licence to use them. All of this is written into the proposal before you sign.

When discovery is free, its cost is hidden in the implementation price and it gets rushed to win the deal. That's a bad setup when the right answer might be a smaller project, or no project at all. Paid discovery gives you a blueprint you own and can take to any implementer, and the fee is credited if you build with us. The first call is still free.

Yes, and there's a separate page for it. We help partners with growth, run a remote PMO, and help with enablement and resourcing. We don't buy or sell leads, take a revenue share, or go after your clients.

A focused CRM or HR build takes four to eight weeks. A full ERP with data migration takes three to six months. What usually decides the timeline is how quickly you can answer the blocking questions and send us your opening balances, rather than the build itself.

Yes, on Frappe Cloud with dedicated resources, in the Mumbai region so data stays in India under the Digital Personal Data Protection Act. If you prefer your own cloud account, we set it up there and hand over the keys.

We never fork the framework. Your customisations live in your own app, and our code looks up your settings by type rather than by name, so renaming a stage won't break anything. Every upgrade goes onto a test site first.

Everything is in your repository, on standard open source software, with a runbook covering deploys, rollbacks and recovery. We don't use a custom framework or leave anything undocumented. Any competent Frappe partner can take over, and we write the code expecting that someone may have to one day.

Often, yes. We start by auditing what was customised and what breaks when it's upgraded. Sometimes rebuilding is cheaper than fixing, and if so we'll tell you before you spend money finding out.