Separate core records from the unique workflow
Accounting, inventory and sales records often belong in an established system. The distinctive part may be an approval sequence, a client portal or a field workflow. Draw the boundary: which system owns customers, orders and balances, and which system owns the specialized process? Avoid duplicating master data unless you have a clear sync and reconciliation plan.
Test configuration before committing to code
Ask a team to demonstrate the required approvals and reporting in a test database. Give them an exception, such as a partial approval or an order change after invoicing. Record which steps use standard configuration, which need an extension, and which cannot be supported cleanly. Check how each extension will be tested during upgrades.
Define an MVP with an acceptance test
Take a business with a manual request and approval process. The first release could capture requests, show their status and send approved records to the ERP. Leave complex dashboards for later if they are not essential. Agree who will use it, what record the ERP receives, what happens when sync fails, and how to measure whether the process improved.
Compare maintenance over the life of the system
Estimate support, hosting, version upgrades, migration, ownership of source code and the effort of training. An inexpensive build can become costly if only one developer can change it. An ERP extension can be expensive if every upgrade breaks a private module. Decide who will own the system after launch and how to exit if requirements change.
Can I use both a custom app and an ERP?
Yes. Keep established records in the ERP and connect a focused custom app when the integration boundaries, permissions and failure handling are defined.
