Buying software vs managed implementation: who owns the work?
Published by Vantage. Pebble is a Vantage product.
This is Vantage owned editorial content, sources checked on 9 October 2026. The decision framework is editorial guidance; it is not proof of Vantage delivery results.
Buy software when your team can configure, test and operate the process it needs. Consider managed implementation when that work needs a clearly accountable delivery owner. In either case, agree who owns the records, decisions and support before signing.
A subscription gives you access to a product under its terms. It does not, by itself, define who will clean your customer records, connect your systems or train your staff. Look for those responsibilities in the actual agreement.
Compare responsibilities, not promises
The table below is a buying framework. Packages vary, so confirm each row in writing rather than assuming that a label includes it.
| Responsibility | Buying software and implementing internally | Choosing managed implementation |
|---|---|---|
| Define the working process | Your business owner and team | Your business owner agrees the process with the delivery partner |
| Configure roles and workflows | Your administrator or internal delivery team | Named delivery owner, within agreed scope |
| Clean and move records | Your team plans and validates the migration | Partner executes agreed migration; your business validates the records |
| Connect other systems | Your team manages dependencies and testing | Partner coordinates agreed connections and documents exceptions |
| Accept the result | Your staff test real work | Your staff still test real work and approve acceptance |
| Operate after launch | Your team and the product's support route | Named support owner, response arrangements and change process |
Microsoft's Dynamics 365 implementation guidance uses business processes to define scope and connect design, testing and operation. Our editorial adaptation is a practical distinction: access to a product and delivery of a working process are separate decisions. The guidance concerns Dynamics 365. It does not establish what Vantage or any particular partner includes. Microsoft: process-based implementation
When internal implementation makes sense
An internal route can fit when the process is familiar, the required capabilities are demonstrated and someone has time and authority to own the work. Before deciding, name that person and list their responsibilities.
For example, an enquiry workflow needs a clear owner, a next action and a way to recover missed work. If your team can define and test that journey, you may need a product configuration rather than a wider implementation engagement. This is an illustrative scenario, not a customer case study.
Ask your team to demonstrate the process using sanitized records. Include a duplicate enquiry and an absent staff member. Inspect the resulting records, not just the screens.
When a delivery partner can help
Consider a partner when the process crosses departments or systems, migration needs coordination, or ongoing operational ownership is missing. The useful question is what the partner will be accountable for delivering.
Request concrete deliverables: an agreed workflow, record ownership, configured access, migration validation, acceptance evidence, staff guidance and a support handoff. Specify exclusions as carefully as inclusions. A partner cannot decide your business policies or accept the system on behalf of the people who will use it.
Microsoft's go-live checklist covers migration validation, user acceptance and operational support readiness. Use those areas to examine an implementation proposal, rather than treating launch as the moment an account is created. Microsoft: go-live checklist
Keep ownership clear after launch
Agree who controls administrative access, how records can be exported, who investigates a failed connection and how changes are approved. Put the handover and exit arrangements in writing before your team depends on the system.
Microsoft's production guidance calls for transferring knowledge to support teams and defining responsibilities and escalation. Our buying recommendation is to ask for a named support contact and a documented recovery path for your critical workflow. Microsoft: production and support readiness
If a proposal includes automated work, ask which actions are permitted, which require human approval and how exceptions reach a person. These are acceptance questions, not evidence that a particular product has those features.
Choose the route whose responsibilities your business can verify and sustain. Bring the broken handoff, the systems it touches and your acceptance criteria to the conversation.