Editions
Community, B1 and Enterprise are the same product family on the same backbone. An upgrade unlocks modules, companies and commercial flexibility — it is not a migration to a new ERP.
Fit finder
Four questions, and the recommendation updates as you answer — with the reason it landed there. Most of what separates the editions is company count, whether approvals must be enforced, and a handful of modules.
Four questions
0 of 4 answeredSelect any that apply. Leave empty if procurement, stores and billing come first.
Answer the first two questions
Company count and whether approvals must be enforced are what actually separate the editions. The recommendation appears here and updates as you go.
The upgrade path
Nothing is taken away as you move up, and nothing is rebuilt. Your masters, approval rules, history and audit trail carry forward.
Small and growing construction teams moving off Excel and starting their ERP journey.
Starts with 5 modules
Mid-size project-driven organisations that need finance, workflow, payroll, mobile and multi-project control.
Adds 7, for 12 total
Large, multi-entity construction organisations that need budget control, production and rent-out coverage.
Adds 3, for 15 total
Named-user bands are sized to your team by sales. EAS attendance users, API users and vendor portals sit outside the ERP user band unless agreed. See every module in detail →
Straight answers
No. The editions are the same product. An upgrade opens modules and limits — your masters, approval rules and transaction history stay where they are.
Because the number depends on named-user bands, edition, hosting and implementation scope. A list price would be a guess, and you would have to unpick it later.
Yes, and most do. Getting procurement and stores genuinely under control is worth more than switching on fifteen modules nobody has time to adopt.
Then we will have said so on the first call. Recommending an edition you will outgrow in six months costs us more than it earns.
Next step
Tell us your company structure, the modules you need first and roughly how many people will use it. You get an edition recommendation you can defend internally and a commercial structure that matches it.
Two lines on your projects and where control leaks today. No form marathon — the optional fields exist only to make the first call sharper.
We narrate the Procurement to Pay cycle against how you actually work. It is your process on the screen, not a feature tour.
Scope, edition fit and what a sensible first phase would cover — in writing, so you can circulate it internally.
Request pricing
Quoted against your edition and user band — not a public list you have to negotiate down from.
Request a walkthroughNo obligation and no procurement process to start a conversation. If a smaller edition would do the job, we will say so.
