A buyer's guide to Kinaxis services partners: SI, boutique or offshore?

Most Kinaxis buying decisions are made on two inputs: the logo on the proposal and the day rate. Neither predicts whether the programme will land. What does predict it is fit — between the shape of your problem and the shape of the firm.

The three shapes

The global system integrator. Deep bench, global coverage, a methodology with a name. Right when you’re running a multi-region rollout with SAP in the middle, a PMO that needs a counterpart, and a board that wants a brand on the risk register. The cost is indirection: the people who sold the work are rarely the people who do it, and the senior architect you met in the pitch will be on three other accounts by month two.

The boutique. Small, senior, usually founded by people who came out of the integrators. Right when you need the architect in the room — a rescue, a first implementation where design decisions will haunt you for a decade, an S&OP rebuild that has to win over planners one by one. The cost is scale: a boutique cannot field forty people by Tuesday, and it shouldn’t pretend it can.

The offshore delivery team. Cost-efficient, tireless, excellent at configuration at volume once the design is fixed. Right for build and test phases with a clear specification, analytics and workbook production, and sustained post-go-live support. The cost is design risk: an offshore team will build exactly what it’s told, and if what it’s told is wrong, it will build that perfectly.

The questions that reveal fit

1. “Who will be on site in week one, and how many programmes are they on?” If the answer is a grade rather than a name, you’re buying a bench.
2. “Show me the last implementation where you changed the design after go-live.” Every honest firm has one. The story tells you how they handle being wrong.
3. “What happens in the first two weeks?” If the answer is configuration, walk away. If it’s an assessment with a deliverable you could execute without them, keep talking.
4. “Where does the offshore team sit in your model, and who reviews their work?” Every firm uses one. The good ones can draw the review loop on a whiteboard.

The hybrid most programmes actually need

The pattern we see succeed most often is not a choice between the three — it’s a sequence. A senior boutique team runs the assessment and owns the design. An offshore practice builds at volume against that design, with the same architects reviewing every sprint. The integrator, where there is one, holds the programme frame and the SAP work. Each does the thing it is shaped for.

That sequence is what our Three Gates Framework formalises: Assess, Architect, Accelerate. The first gate is two weeks and ends with a plan you own outright. If the plan says you need a global integrator, we’ll say so.

What each shape actually costs you

Rate cards make the three look comparable. They aren’t, because the thing you are buying differs.

With an integrator you are buying coverage and indemnity. The day rate carries a bench, a methodology, a delivery assurance function and a legal entity large enough to be worth suing. If your programme spans four regions and three ERPs, that overhead is doing real work. If it spans one plant and one instance, you are paying for insurance against a risk you don’t have.

With a boutique you are buying attention. The senior person is on your programme because there are only a handful of programmes. That is the whole proposition, and it is also the whole risk: if that person leaves, you have lost a meaningful fraction of the firm. Ask what happens if your architect is hit by a bus, and take the quality of the answer seriously.

With an offshore practice you are buying throughput against a specification. The economics are excellent and the work is often better than its reputation, provided somebody upstream is producing a specification worth building. The failure mode is not poor work; it is fast, competent work in the wrong direction, discovered late.

The two questions buyers forget to ask

“Who owns the data model?” Kinaxis programmes live or die on the planning hierarchy and the data model behind it. These get decided early, often informally, by whoever is most confident in the room in month two. Ask, in writing, which named individual owns those decisions and who signs them off. If nobody can answer, the decision will be made by accident.

“What does month seven look like?” Every firm can describe mobilisation. Far fewer can describe the middle of a programme — the point where the novelty has worn off, the planners are tired, the first design compromise is being paid for, and the steering committee has started asking about scope. The firm that answers that question concretely has been there. The firm that returns to its methodology slide has not.

A note on the boutique’s honest limits

We are a boutique, so read the next paragraph with that in mind.

There are programmes we should not bid for, and we say so. A simultaneous multi-region rollout with a hard regulatory date and a parallel SAP S/4 migration needs a delivery organisation with a bench, a PMO and the ability to absorb two people leaving without the plan moving. That is not us, and a boutique that tells you otherwise is selling you its cash-flow problem.

What we do claim is narrower and, we think, more useful: when the design decisions are the risk — a first implementation, a rescue, an S&OP rebuild that has to win planners over one at a time — the person who makes those decisions should be the person who has made them before, and they should be in the room rather than on the account.

How to run the decision

1. Write down the three riskiest things about your programme. Not the deliverables — the risks.
2. For each, ask which of the three shapes reduces that specific risk.
3. Where the answers disagree, you have a hybrid, not a compromise.
4. Test the hybrid by asking each firm how they would work alongside the others. Firms that have genuinely done it answer immediately and unsentimentally; firms that haven’t tell you they prefer to own end-to-end delivery.