How Flectic Runs ERP Rollouts
Flectic runs ERP rollouts in five stages you sign off one by one, with a fixed price for each phase, so risk surfaces early and each phase expands only after your team uses the last one.
Flectic runs every ERP rollout in five stages under the Flectic Accelerated Delivery Framework: discover and scope, configure and adapt, migrate and connect, test and train, then launch and stabilize. You sign off each stage before the next one starts, and each phase has a fixed price in a written proposal before work begins. Most implementations that go wrong do so because of people, planning and process decisions made or skipped before anyone touches a screen, so the stages bring those decisions forward while they are cheap to change.
This page covers what happens in each stage, how the price and timeline are set, who runs the work and the habits we push back on.
Why we reframe "implementation" as a rollout
There's a statistic that everyone in this industry quotes and almost nobody acts on: Gartner's research finds that between 55% and 75% of all ERP projects fail to meet their objectives, where "failure" can mean anything from cost overruns of 100% or more all the way to systems that never meaningfully work (Lumenia Consulting, citing Gartner). That figure is cited widely, but the part that matters to us is the why. As the consultants at Lumenia put it after analyzing the post-mortems, the root causes cluster around people, planning, and processes — leadership gaps, weak project ownership, scope creep, and treating the whole thing as an IT problem rather than a business-change program. The technology is rarely the culprit. Modern ERP platforms are, by and large, fit for purpose; the purposes just differ wildly between businesses.
That single insight drives how Flectic operates. If the failure mode is human and procedural, then a methodology that optimizes for perfect Gantt charts and a single heroic go-live date is solving the wrong problem. So we reframe the work. We don't "implement software at you." We roll out a new way of running your business, one that happens to be underpinned by software — and we sequence it so the risky human stuff is confronted when it's cheap to fix, not the week you flip the switch.
The practical consequence is that we treat your ERP project as a business-change program with a technology backbone, which is the framing Lumenia and others argue is missing from most failed efforts. That means a named, accountable project owner on your side, an active executive sponsor, and a delivery team that works with the people who do the work, as well as the people who signed the purchase order. The five stages below are how we make that real.
Stage 1: Discover and scope
Every Flectic rollout starts with discovery, and we keep it even when there is pressure to start building. Discovery is the foundation the rest of the project stands on, and rushing it is the fastest route to the rework, scope creep and misfit that derail projects later. ERP Software Blog puts a thorough discovery for a mid-size business at roughly 80 to 100 hours of focused effort, a figure that looks large until you compare it with the months of rework it prevents. Those hours go into workshops and interviews, process mapping, gap analysis, requirement priorities and a written blueprint for what comes next.
We sit with the people who run the processes in scope, across finance, operations, sales, warehouse and service. We map how the business runs today, including the spreadsheets and workarounds nobody documented, then how it should run, and we compare that with what Odoo or Dynamics 365 does out of the box. That gap analysis shows where configuration, an extension or an integration is needed, and where a requested customization would only cover a broken process. A consultant checks every AI-drafted discovery note with you before it goes into the blueprint.
Discovery ends with a recommendation for Odoo or Dynamics 365 and a written proposal that fixes the scope and price of the first phase: the processes in and out of scope, the configuration decisions, the integrations, the data migration approach, the success criteria and a timeline that states its dependencies. Anything outside that scope goes through documented change control, which answers the scope creep Lumenia lists among the most common causes of overruns. For the wider industry lifecycle, see the standard ERP implementation phases. Our five stages cover the same ground, with a sign-off between each one.
Stage 2: Configure and adapt
With the blueprint agreed, we configure finance and operations around your processes. We configure first, extend second and customize only where configuration cannot close the gap and the business case pays for it. Many requests that arrive in discovery as a must-have customization turn out to describe an outcome, and standard settings often reach it once people see the configured system.
The first phase stays small on purpose. Instead of building everything and emerging months later for a big-bang go-live, we put a contained scope live first, such as one sales-to-cash flow, one warehouse or one production cell, so surprises show up while they affect a single process. The first phase delivers a working part of the system, and you fund the next phase on what you have seen work.
Stage 3: Migrate and connect
We clean and migrate your data and build the integrations your team depends on, such as banking, commerce, CRM and reporting. Data quality issues and integration quirks are the surprises that most often break a schedule, so we test them on your own records instead of a demo dataset. You check migrated balances before anyone relies on them.
Stage 4: Test and train
Your team runs acceptance tests on real scenarios, and we train each role on the processes it runs instead of giving a generic feature tour. Super-users in each team become the first line of support. A consultant reviews every test scenario and training document before your team sees it, including the first drafts AI writes. Testing turns leadership's assumptions into what people observed, which clears up the mismatched expectations Lumenia names as a leading cause of failure.
Stage 5: Launch and stabilize
We go live on the agreed scope and stay through launch stabilization to fix issues and track adoption. A module that went live on Friday and that nobody uses on Monday is a cost, so before the next phase starts we check whether people are in the system, whether processes run as designed and whether the data is trusted. On our Odoo industry packages, launch stabilization runs 30 business days with up to 10 advisory hours on Core, and 45 business days with up to 22 hours on Growth. On Business Central we work alongside your team through the first month-end close on the new system.
Each later phase repeats the stages on a new scope, with its own fixed price, testing, training and stabilization. A big-bang go-live puts every integration, migration and change-management challenge into one weekend, and when something breaks, it breaks for the whole company. A phased rollout spreads that risk across waves, so when one wave stumbles you fix it while the rest of the business keeps running. Work after launch stabilization is scoped as a new phase.
How a Flectic rollout differs from the alternatives
The word "implementation" covers very different engagements, and the differences explain a lot of the failure statistics. The list below compares Flectic's five-stage rollout with the three patterns we most often see brought to us as cleanup work.
- **Flectic: five stages, each signed off**. What it optimizes for: a working first phase, scope fixed in writing and expansion after adoption · Where it tends to break: slower to a first full go-live, which impatient stakeholders can misread as delay
- **Big-bang waterfall**. What it optimizes for: A single clean go-live date; everything live at once · Where it tends to break: Concentrates all risk in one weekend; one failure breaks the whole company
- **Template-only / "best practice" rapid deploy**. What it optimizes for: Speed and low consulting hours · Where it tends to break: Forces your business to conform to the template; unique processes get crushed or quietly worked around
- **Customization-first build**. What it optimizes for: Matching the system exactly to today's processes · Where it tends to break: Replicates today's inefficiencies; expensive, brittle, and slow to upgrade
The pattern to notice is that each alternative optimizes for something that looks good in a sales cycle — a date, a low price, a promise of "no change to how you work" — and pays for it later in the ways the failure research predicts. Flectic's rollout optimizes for the thing that actually determines whether you get value: a system your people use, configured around processes that were improved rather than copied, expanded at a pace your organization can absorb.
The team that runs your rollout
Methodology is only as good as the people who run it, and one of the clearest signals in the failure research is that ownership and sponsorship are decisive. Lumenia is blunt about it: an ERP project needs a named owner of appropriate rank who is involved day to day, plus an active sponsor at C-suite or executive-board level, because without that authority the project loses every fight against "local urgencies" — the day-to-day fires that crowd out the transformation work. We design our teams and our governance around that reality.
A Flectic rollout is led by a named senior consultant you meet in discovery and keep through launch stabilization, supported by a dedicated project manager who tracks the plan. At Flectic that consultant is Reza Ahmadi, co-founder and lead consultant. The consultant who writes your first-phase scope reports against it at every stage sign-off, so budget questions go to someone who was in discovery. On your side, we ask for a counterpart: a business owner with authority over the processes in scope, paired with an executive sponsor who can break ties and clear roadblocks. We hold firm on that pairing, because projects without it lose every fight against day-to-day urgencies.
This is also why we keep the engagement personal. ERP rollouts succeed or fail on trust as much as on configuration skill, between your people and ours and between your front line and your leadership. We build that trust by showing working software in the first phase, by saying what we don't know yet, and by leaving your team able to run the system without us. Flectic's ERP implementation service lays out how that works in an engagement.
What we refuse to do (and why that protects you)
Half of a good methodology is knowing what to say no to. These are the things Flectic will push back on, because each one is a well-traveled path to the failure statistics we're trying to help you avoid.
We refuse to skip or skim discovery. Pressure to start configuring is the most common request we get, and the one we redirect most firmly, because configuring against assumptions is what causes months of rework. If a stakeholder wants visible progress, we point to the first phase, which puts a working part of the system in front of the team.
We refuse big-bang by default. If your context calls for a single go-live, usually a small scope with one process, we will make the case in writing. The default is phased expansion, with each phase tested and signed off, because putting every risk into one weekend should need a justification.
We refuse to lift-and-shift broken processes. If discovery reveals that a current process is inefficient, our job is to say so and help redesign it, not to faithfully encode the dysfunction into a shiny new system. Copying inefficient processes into new ERP software is one of the most common — and most wasteful — failure patterns, because you spend a fortune to move the same problems somewhere more expensive.
We refuse customization-first thinking. We configure before we extend, extend before we customize, and customize only with a written business case and a clear view of the upgrade and maintenance cost. Most "we need it customized" requests ask for a different outcome, and the configured first phase usually shows that the outcome needs no bespoke code.
We refuse to vanish at go-live. The weeks after each go-live are when adoption is won or lost, so launch stabilization is staffed by the consultant who built the configuration. Handing over to a generic support queue on the first day is how you get a system people quietly abandon.
What a Flectic rollout costs and how long it takes
Cost and duration depend on scope, the number of processes and sites, the state of your data and how much customization your business needs. We quote after scoping, because a price set before anyone understands your processes is a guess with a contract attached, and the gap between the two is where overruns live.
The discovery call is free: 30 minutes with a senior consultant, ending with a recommended first phase or a clear reason to wait. Flectic then sends a written proposal with a fixed price for each phase before work starts. Each later phase gets its own scope and fixed price, so you expand in steps you have approved instead of signing one large figure up front for months of work.
On timing, our Odoo industry packages run 8 to 28 weeks, and a first phase outside the packages gets its own timeline in the written scope. As a market reference, Odoo and Business Central projects commonly take 3 to 9 months for a standard mid-market scope. Your own timeline comes from the written proposal, based on your processes instead of industry averages.
When a rollout is — and isn't — the right fit
A phased, five-stage rollout suits most of the companies we work with: firms of 20 to 100 people replacing spreadsheets and legacy systems with one platform, multi-site operators who need to standardize, and growing businesses whose processes have outgrown their tools. If you have processes to map, people to bring along and a wish to improve how the business runs, this approach fits.
It is a weaker fit in a few cases. If your scope is tiny, such as one well-understood process with no integrations and a handful of users, the full set of stage sign-offs may be more governance than the work needs, and a lighter engagement will serve you better. If your organization cannot provide a named owner and an executive sponsor, no method will rescue the project, and we would rather say so before taking the work. And if you want the software to keep your people working exactly as they do today, you are shopping for a template deployment, which will disappoint you for the reasons above, quickly and cheaply.
Signs your rollout is on track
Because each phase expands only after adoption, it helps to know what on track looks like. At the end of discover and scope, the signal is a blueprint your own team recognizes as their business. In test and train, it is working software that users have run their own transactions through, plus a short list of specific gaps. After launch, it is adoption: users are in the system daily, processes run as designed, the data is trusted enough to decide from, and your internal owners start answering their own team's questions.
The warning signs matter as much, because a good rollout surfaces bad news early. If the configuration keeps needing one more customization to handle a core process, revisit the platform fit before building further. If usage drops within weeks of a go-live, solve that change-management problem before the next phase starts. A rollout that hears no bad news until the post-mortem has been managed for appearances.
The bottom line
We run ERP rollouts in five stages, with a fixed price per phase, because that shape avoids the failure modes the industry has documented for decades. Discover and scope maps your business and fixes the scope in writing. Configure, migrate, test and train build a contained first phase on your own data with the people who will run it. Launch and stabilize stays until adoption holds, and the next phase starts on a foundation your people trust. It is slower to a single everything-live moment than a big-bang plan, and it is the approach most likely to turn a software purchase into a business result. If that is the rollout you want, Flectic's ERP implementation service is where it starts.
How Flectic can help
Flectic runs ERP rollouts for companies of 20 to 100 people in the US and Canada, where finance, stock and projects run on spreadsheets and disconnected tools. We replace those tools with one ERP on Odoo or Dynamics 365, led by a named senior consultant through five stages you approve. Each phase has a defined scope and price before it starts, and the first one delivers a working part of the system. Read the ERP implementation service to see the rollout stages, then Book a free discovery call with Flectic.