SAP covers more than one product and more than one size of business. Start with the system being proposed, then compare its fit with a custom build around the work your team actually does.
Start with the fit
Revenue alone does not decide the platform. The operational requirements, existing investment, internal capability, and implementation plan matter more than a simple size cutoff.
Consider SAP
Assess the relevant SAP product when a common operating model and an established platform are central to the plan.
Consider custom ERP
Assess custom when specific workflows create meaningful gaps, and a defined build can solve them without recreating an entire enterprise suite.
Side by side
Use the same workflow, volume, and operating requirements for both options. The right comparison includes setup, integrations, your team’s time, and what happens after launch.
| What to compare | Custom ERP | The proposed SAP product |
|---|---|---|
| Product scope12 | The workflows and modules agreed for your business; scope grows through delivery. | Specify the product and edition. SAP Business One serves smaller businesses; S/4HANA Cloud Public Edition offers a broader ready-to-run ERP model. |
| Operating model2 | Designed around your agreed handoffs, roles, and exceptions. | Assess how your process maps to the proposed product’s standard workflows and available extensions. |
| Finance & reporting | Connect operational records to the existing books or separately scope new finance capabilities with the people responsible. | Demonstrate the exact finance, reporting, and consolidation requirements in the proposed edition and configuration. |
| Cost to include | Build capacity, connected systems, migration, testing, team training, and ongoing operation. | The actual licence or subscription proposal, partner delivery, extensions, migration, internal capacity, and ongoing support. |
| Implementation | A phased first workflow with clear acceptance and reconciliation checks. | A product-specific rollout plan. Ask for the same dependencies, first-use milestone, and acceptance checks. |
| Controls & review | Plan access, audit trails, recovery, and any specialist validation around the workflow. | Verify the controls and assurance relevant to the proposed service and your configuration. Vendor assurance does not complete your own implementation review. |
| Continuity | You own the code we build. Document the system, dependencies, and support responsibilities. | Plan platform and partner responsibilities, access to the configuration, and handover of custom extensions. |
Product details checked against official documentation · 10 September 2026. Fit and scoping guidance is our assessment.
Reliable Training ran on forms, calendars, spreadsheets, and bookings handled by hand. We built a custom ERP connecting the work from registration through certification.
Compare the actual product, the actual scope, and the people who will use it. A platform name is the beginning of the assessment.
Trace one job from enquiry to payment. Include the exceptions, approvals, and work happening outside the current system.
Agree which processes should become standard and which differences are important enough to build around.
Ask every option to demonstrate the same records, handoffs, and difficult cases. Record what is configured, extended, or missing.
Compare delivery, subscriptions, integrations, migration, training, support, and likely changes over the same planning period.
Set acceptance checks, data ownership, a migration approach, and who can approve the move into daily use.
Document why the approach fits, what remains uncertain, and what would make you revisit it before expanding.
Clear answers on timelines, pricing, ownership, and what shipping actually looks like with a senior engineering team.
No. SAP offers different products for different needs, including Business One for smaller businesses. Identify the product and proposed scope before comparing it with custom software.
That is not a useful default scope. First identify what you use, what must stay, and which gaps matter. A focused operational build or integration may be more appropriate than a complete replacement.
The answer depends on the first release, data readiness, integrations, and change involved. Compare plans for the same usable milestone rather than a first custom module against an entire platform rollout.
Potentially. We need to understand your SAP edition, available interfaces, licensing constraints, permissions, and record ownership before recommending a portal or operational layer.
Bring operations, finance, the people using the system, and whoever owns technical delivery. Specialist requirements should be reviewed by the people accountable for them before the scope is agreed.
Bring the workflow, the proposals, or the questions holding things up. We’ll help identify the tradeoffs, the missing information, and a useful next step.
Or email hello@buildfutur.com
