ERP boundaries & custom software

ERP matters, but we do not offer ERP implementation as a standalone service. The useful question is which work belongs cleanly in your ERP - and which workflows need their own software layer because spreadsheets, email, or manual exports still carry the work.

Typical ERP boundaries

• Variants, configuration and quotation logic live in spreadsheets.
• Project status, purchasing, inventory and service need manual coordination.
• Accounting handovers, exports and reviews depend on repeated manual work.
• People copy data between ERP, files, email and specialist teams.
• An AI agent could prepare or execute part of the work, but needs clear data and permission boundaries.

MAFU-SHERPA shows the point: Business Central remained the place for stable master data, orders and accounting. Differentiating product logic sat in a focused CPQ configurator: CPQ at MAFU-SHERPA. For month-end accounting, the DATEV export complements that setup as a lean finance workflow.

The practical starting point is a scoped review of the workflow, data ownership and system boundaries.

If a workflow is stuck between ERP, spreadsheets and people, let us review the software layer.