The person who sells the engagement should be the person who delivers it.
There is a pattern in ERP consulting that most buyers have experienced but few talk about openly. A senior architect presents during the sales process. They understand the problem, they ask the right questions and they inspire confidence. The contract is signed. The project kicks off. And a different team appears: more junior, less experienced and unfamiliar with the commitments made during the sales conversation.
This is the bait-and-switch model. It is standard practice in large consulting firms. It is not inevitable.
In a principal-led engagement, the person who designs the solution is the same person who oversees its build, reviews the code, runs the testing and manages the deployment. They are present in every working session, not just the steering committee.
This does not mean the principal writes every line of code or configures every workflow. It means they direct the work, review every deliverable and take personal accountability for the outcome. If a developer builds a Suitelet, the principal reviews the code against the development standards before it reaches UAT. If a functional consultant configures a workflow, the principal validates it against the functional design before it is presented to the client.
The result is consistency. The quality of the output does not vary based on which team member happened to be available that week.
The most common cause of ERP project failure is not technical. It is the gap between what was agreed in the design phase and what was built in the development phase. This gap opens when different people own different phases. The architect who understood the business problem hands off to a developer who understands only the technical specification. The nuances, the context, the reasons behind design decisions are lost in the handoff.
In a principal-led model, there is no handoff. The same person who sat in the discovery workshop with the finance director is the person who reviews the adjustment journal logic in the code. They know why the control exists, not just how it should work.
Principal-led delivery is not without constraints. Capacity is the most obvious one. A principal can direct a limited number of workstreams simultaneously. This means principal-led firms typically run fewer concurrent engagements and may have longer lead times for new projects.
It also means the daily rate is likely higher than a team staffed with junior consultants. But the total cost of the engagement is often lower because there is less rework, fewer miscommunications and no wasted time re-explaining context to new team members.
The honest comparison is not "senior rate versus junior rate." It is "total cost of a project delivered right the first time versus total cost of a project that requires remediation."
Before signing a contract, ask three questions. First: who will be my day-to-day contact during the project? If the answer is different from the person in the room, you know what is coming. Second: who reviews code and configuration before it reaches me? If there is no defined review process, quality is being left to chance. Third: what happens if the assigned resource is unavailable? If the firm has no continuity plan, a single departure can derail your timeline.
The answers to these questions tell you more about the likely outcome of your project than any capability deck or case study ever will.
We operate exclusively on a principal-led model. Every engagement is directed by a certified Solution Architect from discovery through to production handover. We do not sell senior and deliver junior. The constraint this places on our capacity is a deliberate choice. We would rather deliver fewer engagements well than many engagements poorly.
Want to experience principal-led consulting first-hand?
Book a Free Consultation