Partner portfolio

Compare the suite fit.

Use this overview to start the right partner conversation. Manufacturing is the primary summit focus; Base, Starter, Supply Chain and Mobile complete the modular path.

How to use this page

Choose the conversation, not a generic bundle.

The original Inceptum comparison covers Base, Manufacturing, Supply Chain and the Mobile add-on. This partner version adds an opportunity view for the confirmed Starter option.

Portfolio comparison

Focus a suite

Showing the full portfolio comparison.

Partner portfolio comparison of Starter, Base, Manufacturing, Supply Chain and Mobile suites
Partner question Starter Base Manufacturing Supply Chain Mobile
Where does the conversation start? Extended printing functions Core processes for non-manufacturing business Production planning, costing and control Automotive and supply-chain requirements Mobile production and logistics workflows
Printing and document output Primary focus Core process scope Builds on Base Builds on Manufacturing Not core
Reporting, layouts, EDI and intercompany Not core Foundation Builds on Base Builds on Manufacturing Works alongside
Production planning, costing and insights Not core Not core Primary focus Builds on Manufacturing Production reporting
Variants, resource planning and traceability Not core Not core Primary focus Builds on Manufacturing Shopfloor data capture
Supply-chain formats, schedules and sequencing Not core Not core Not core Primary focus Logistics execution
Mobile reporting, inventory and quality workflows Not core Can be extended Can be extended Can be extended Primary focus

“Builds on” reflects the hierarchy presented in the Inceptum suite overview: Manufacturing includes the Base scope and Supply Chain includes the Manufacturing scope. Mobile is positioned as an add-on to the suites; Starter is the confirmed printing-focused entry option.

Source basis: Inceptum price and feature comparison page, the supplied 2025 partner flyer, and the confirmed project brief. This is a solution-fit overview, not a price list or a contractual feature specification.

Make it specific

Bring the customer context.

Industry, process bottleneck, integration need and people on the shop floor are more useful than a generic feature request. We will help map them to the right suite conversation.

Next step

Reserve time in Amsterdam.

Use the summit meeting to test the suite fit alongside the customer opportunity.

Book a meeting