Short answer
Build a ServiceNow center of excellence (CoE) yourself if you already have a Platform Owner, senior architects and time to hire. Use a partner if the mandate is urgent or skills are thin, and write the handover into the contract. Either way, your company should own roadmap decisions. The difference is who carries the hiring and start-up risk.
Last reviewed Nov 2, 2026
As of Nov 2, 2026. This reflects our operating experience, and we have a stake in the answer, so test it against your own situation.
| Factor | In-house | Partner-built |
|---|---|---|
| Control | Full from day one | Yours by contract and governance |
| Speed to start | Depends on hiring | Faster if the partner has a bench |
| Skills risk | You carry attrition and gaps | Shared; the partner backfills |
| Knowledge | Stays with you if retained | Transfers only if the contract says so |
| Cost shape | Salaries, training, tools | Fees, plus your own core team |
| Standards | You write them | Partner's starter set, adapted by you |
| Exit risk | None from a partner | Real, unless transfer is dated |
| Best fit | Mature teams, stable demand | New mandates, thin teams, urgent releases |
What has to be true either way
You need a named Platform Owner and process owners, a single prioritized backlog and a clear rule for who decides what. A partner can't supply these, and without them a partner-built CoE becomes managed services under another name.
A staged route
A common path starts with managed capacity while the core team forms, moves critical roles to permanent hires through contract-to-hire, and ends with the partner on specialist work only. The comparison of BOT and managed capacity sets out the two main models.
Questions to put to any partner
- Which of the people named in the proposal will actually work on your account?
- Who owns the runbooks, the architecture repository and the dashboards at the end?
- What exactly is the transfer date, and what happens if it slips?
- How will you report attrition on the account?
- What's built on our instance that we couldn't keep?
What GCC Now™ builds on your instance is yours, and iForge™ stays an inMorphis asset, with a license route if you want to keep using it. Get that in writing from anyone you consider, including us.
The boards and scorecard are in our CoE guide.
GCC Now™ is the ServiceNow Accelerator by ANSR × inMorphis, a joint venture for global capability centers (GCCs) and GBS organizations.