We build ERP systems that survive their own implementation
- Based in
- Surat, Gujarat, India
- Built on
- ERPNext · Frappe
- Practice
- ERP engineering only
Essence ERP is an ERP engineering practice in Surat, Gujarat, India. We build on ERPNext and the Frappe framework, open source and self-hostable, and we work in the industries where generic ERP consistently falls short.
The work is deliberately narrow. We do not sell hardware, resell licences or run a general IT desk. We scope ERP systems, build them, migrate the data, train the people who will use them, and keep them healthy for as long as you run them.
- 200+
- Implementations delivered
- 98%
- Client satisfaction
- 40%
- Average efficiency gain
- 3-4
- Months to go live
Opinions we arrived at the hard way
Most of these came from watching something go wrong. Occasionally on one of our own projects.
- 01
The software is rarely the problem
ERP projects fail on undocumented scope, dirty data, badly timed training and vendors who leave at go-live. We spend our effort on those four rather than on feature comparisons.
- 02
Industry depth beats feature count
A system that already understands shade lots, near-expiry returns or bed-level tariffs is worth more than one with a longer specification sheet and no opinion about your business.
- 03
Customisation belongs in source control
Configuration typed straight into a production site disappears at the next upgrade. We write customisations as versioned applications, reviewed and deployed like any other code.
- 04
You should be able to leave
Open source core, your own database, deployable on your own hardware. A system you cannot exit is a system you will eventually resent, and lock-in is not a business model we want.
- 05
Say the uncomfortable thing early
If a requirement will cost more than it is worth, or a timeline is not achievable, that conversation happens during discovery. It is a far cheaper conversation then.
- 06
The team that builds it, supports it
Nothing is handed to a separate support pool after go-live. The engineers who learned your business stay attached to it, which is why year three works as well as year one.
Six phases, every engagement
Owners and dates are written down before anything is built, which is what turns a go-live date into a commitment rather than an aspiration.
The services in detail| Phase | Stage | What happens in it |
|---|---|---|
| 01 | Discovery | We document how work actually moves today and map the gaps against the ERP. Phases, owners and dates go into a written scope before anything is built. |
| 02 | Configuration | Chart of accounts, numbering, approval chains, roles and permissions follow your policies. Industry modules are tuned, not written from scratch. |
| 03 | Custom build | Whatever standard ERP will not do, we build: versioned code in a custom app, never one-off patches on a live site. |
| 04 | Data migration | Masters, opening balances and history from Tally, Excel or the legacy system, reconciled to the rupee against your trial balance before sign-off. |
| 05 | Training & go-live | Role-based training on your own data, written SOPs, on-site or remote cover through the first close. Hypercare ends when the daily questions do. |
| 06 | Run & improve | Managed support, monitoring and upgrades. Quarterly reviews name the next module worth adding, unprompted. |
Phases, owners, milestones and the open risks live in the system you are buying, not in a slide deck. You can read the whole plan on the day we start, and watch it move every week after that.
Come with a problem, not a specification
The most useful first conversation is about what is going wrong today: the report that takes two days, the stock figure nobody trusts, the month-end that eats a week. We work out from there whether an ERP is the answer.