Growing Fast but Still Waiting on ERP?

Sales are up 40% this year, and the company has just opened its third branch. But accounting still closes the books in Excel, stock at the new branch is checked by phone, and management reports are always a week late. Everyone knows it is time for ERP. Yet the decision keeps getting pushed back.

The reason is rarely a lack of need. When choosing ERP for growing businesses, four concerns tend to delay the decision.

Will an ERP project take a whole year?

The concern is fair: projects that cover every department at once are often slow and over budget. SAP’s cloud ERP lets you start with what you need most, such as finance, supply chain or HR. Once that part runs well, you switch on more capabilities without implementing again from scratch.

Data and settings from earlier phases carry forward. You do not have to choose between “start small to go fast” and “build enough for the long term”.

Is AI in ERP usable now, or just for demos?

Many companies have tried AI tools: a chatbot here, a forecasting file there. Results are often scattered, because sales, inventory and finance data sit in different places. AI only gives sound suggestions when the data lives in one system.

SAP’s cloud ERP has AI built into its processes. In the sales-to-cash flow, for example, AI can help create invoices, flag unusual invoices, remind customers to pay and forecast cash flow. Some AI features are included in the package; others are charged by usage.

Will the system keep up with new markets and new requirements?

SAP’s cloud ERP comes with standard processes for many industries: manufacturing, distribution, retail, services and construction. Accounting, tax and invoicing are localized for many countries. When you open a company in a new country that SAP already supports, the system expands with you instead of being replaced.

Exporters, especially to the EU, may need to report emissions by product or shipment. When purchasing, production and logistics data already sit in ERP, you have the base to calculate these figures. No more estimating in Excel.

The trade-off is that you need to adjust some ways of working to fit standard processes. For many growing companies, this is a chance to drop manual steps that have become habits.

Will costs creep up after go-live?

With on-premise software, you look after servers, security and upgrades yourself. Each upgrade is a small project that costs money and time.

SAP’s cloud ERP moves this work to SAP. SAP handles infrastructure, security and system updates twice a year, so you always run the latest version. In return, you pay a recurring subscription instead of a one-time license.

The package scope is defined up front, so you know what you are paying for. Costs usually become hard to predict when the system is heavily customized beyond the standard. That is why getting the scope right at the start matters more than picking features.

How TDI APJ helps

TDI APJ is an SAP partner and part of the TDI Group (Japan), with 300+ SAP projects delivered in 15+ countries. We implement SAP Cloud ERP through SAP GROW in Vietnam, Malaysia, Singapore and Indonesia, in four steps:

1. Compare your current processes with SAP standard processes and agree on scope.
2. Configure the system and migrate data.
3. Go live.
4. Support after go-live and plan the next phase.

At Kajima (Malaysia), a construction company with around 350 staff, project cost and finance data used to sit apart between sites and head office. TDI APJ implemented SAP Cloud ERP through SAP GROW to bring them into one system. The project earned value (EVM) reporting cycle dropped from 30 days to 3 (SAP, 2026).

Companies with many specific processes can consider RISE with SAP. TDI APJ implements both, so we can advise on the right fit. For specific AI needs, TDI AI Studio builds AI applications on your own SAP data.

Weighing ERP but unsure where to start? Talk to TDI APJ about the right first-phase scope for your current size.

Sources: SAP – SAP GROW (2026); SAP – What is SAP GROW? (2026); SAP – Kajima (Malaysia) Customer Reference (07/2026).