ERP Implementation
ERP implementation is selecting and rolling out the system a business will run on, and doing the process work that has to happen before any software is configured.
Service within Execution OS
How we help with ERP Implementation
An ERP laid over a broken process automates the breakage.
Do the process work first
What the business should do, agreed and documented, before any system is configured. A system built around a broken process entrenches it.
Select for fit, not for features
The system the team will actually use at this company's size and complexity, chosen against a defined requirement rather than a demo.
Plan the data migration honestly
Master data is where implementations lose months. Cleaning it is unglamorous, slow and the thing that decides the timeline.
Land it in stages
Module by module with each one stable before the next, rather than a single switchover that gives the business no way back.
More services within Execution OS
HR Business PartneringStrategic people operations that align org design and hiring with what the business is actually trying to do.
Performance ManagementThe numbers a leadership team actually runs on, and the cadence that makes them act.
Process Standardisation and OptimisationMaking the way work happens repeatable, so it survives the people who invented it.
An ERP laid over a broken process automates the breakage.
FAQ
Questions founders ask about ERP Implementation
Do you implement ERP systems?
We deliver ERP work inside a larger transformation or controllership mandate rather than as a standalone implementation. The process design, the requirement, the selection and the programme are ours; the technical configuration is done with an implementation partner.
Which ERP should we choose?
It depends on entity structure, transaction volume, statutory requirements and what the team can operate. The expensive mistake is almost never the product chosen, it is choosing before the process is decided.
How long does an implementation take?
For a mid-sized Indian company, typically six to twelve months, and the variable is data quality rather than software. Migration of master data is where most overruns happen.
What makes implementations fail?
Automating a process nobody agreed on, underestimating data cleanup, and treating it as an IT project rather than an operating change. All three are decided before any software is installed.
What our research says about ERP Implementation
Founders sometimes want to start with the tool selection. We tend to start with the workflow design, because the wrong tool inside a good architecture is recoverable, while the right tool inside a bad architecture is not.
A stack with architecture has defined sources of truth. Every team knows which system holds the canonical version of each piece of data. Integrations between systems are deliberate, with clear ownership of each handoff.
Further reading
Article · Srikar KedarisettyWhy Finance Tech Decisions Break Scaling CompaniesRead
Article · Srikar KedarisettyBuying Tools Is Not Building a Finance StackRead
Article · Srikar KedarisettyIntegrating Accounting, MIS, and Planning ToolsRead
Article · Sriram ChidambaramYou can't AI your way out of a broken baseRead
The people behind ERP Implementation
ERP Implementation is run by the studio team: one multidisciplinary team whose pods work in tandem, matched to the sector and the stage the company is in.
FinOps: CFO Office pod
Led by Srikar Kedarisetty
Lead, FinOps & Transformation. Manages cash flow and financial control.
See the pod structure
What usually runs alongside this
CFO Tech StackThe technology architecture behind a finance function: accounting, MIS and planning tools that work as one system.- Process Standardisation and OptimisationMaking the way work happens repeatable, so it survives the people who invented it.
Business TransformationChanging how a business runs, not just what it reports, with the sequencing that keeps it trading throughout.
