A Product That Keeps Changing, Not a Project That Ends

No, and we would advise against it. One module goes live with one team while everything else stays as it is. The next module starts when the first has proven itself, so there is no cutover date to defend.

Both, deliberately. We model the first pricing configuration with your estimator so the logic is right and your team can see how it was built. After that it is a no-code editor, and most changes stop needing us. Bespoke logic and integrations remain our work.

Usually the opposite, and that is deliberate. Where what you need makes sense for packaging companies generally, it goes into the product, which means it is maintained, tested, and upgraded like everything else rather than surviving as a special case. Genuinely proprietary logic, such as your own cost model or a connector to a system only you run, stays yours and stays isolated, so it does not block your upgrades either.

Only if it is genuinely easier than what they do now, which is our problem rather than theirs. We start with the people who price today, build the model with them rather than for them, and change the screens where they hesitate. Where a team does not come across, the honest read is usually that the interface is still asking too much.

Then we say so early, which is the part most projects skip. Where something you do is genuinely unusual rather than standard for the trade, we put the choice in front of you: change the process, or keep it and accept that it becomes bespoke work with a maintenance cost attached. Large ERP failures usually start with a mismatch nobody was willing to name, and end with a system that has been customised past the point where it can be upgraded.

Then we say so, and we help you get there. Usually it means writing down pricing logic that only exists in someone's head, or finding out what your customer and product data really looks like before it moves anywhere. That work is worth doing whether or not you buy anything from us.

One person who owns pricing and can decide, access to a handful of real jobs, and whoever knows where the data actually lives. That is materially less than a traditional rollout asks for, because we are not trying to document your whole business up front.