Build, buy or choose a managed marketing stack?
The right answer depends on capability, ownership and the real cost of making technology useful.
Build when the capability creates genuine strategic differentiation and you can own it long term. Buy when the requirement is standard and the team can configure and operate the product. Use a managed model when the technology is necessary but internal capacity, integration or ongoing ownership is the real constraint.
The sourcing decision
Build, buy and managed technology are different ownership models. The decision should consider strategic differentiation, internal capability, speed, integration, governance, support and the cost of operating the system after launch.
The choice is becoming harder because the market is vast. Chiefmartec counted 15,505 commercial marketing-technology products in its 2026 landscape, up from 150 in 2011. More choice creates optionality, but it also increases evaluation and integration work.
When building is rational
Build when the capability is central to how the organisation differentiates, standard products cannot support an essential requirement, and the business can fund product management, security, maintenance, support and continuous improvement.
Do not confuse configuring an existing system with building a product. Genuine ownership continues after launch. The organisation inherits the backlog, technical debt, documentation, incident response and succession risk.
When buying is rational
Buy when the requirement is common, the market offers a credible product and your team can operate it. Buying can accelerate deployment, but it still requires selection, configuration, data migration, adoption, integration and governance.
Zylo’s 2025 SaaS Management Index analysed more than 40 million licences and $40 billion in managed SaaS spend. It reported an average of 152 applications among organisations with 1 to 500 employees and average SaaS spend of $4,830 per employee across its dataset. The sample reflects Zylo customers and should not be treated as a benchmark for every small business. It does show how quickly unmanaged purchasing can expand.
When a managed model is rational
Use a managed model when the capability matters but the business does not want to become its own systems integrator, administrator and first-line support team. The provider should contribute implementation, operating design, maintenance and a clear accountability model, not simply resell access.
Managed does not mean surrendering control. The customer still needs clarity on data ownership, portability, security responsibilities, service scope, configuration rights and exit arrangements.
The RAAJE build, buy or managed decision framework
| Question | Build | Buy | Managed |
|---|---|---|---|
| Is this strategically differentiating? | Usually high | Usually low to medium | Low to medium |
| Do we have product and technical ownership? | Required | Helpful | Shared with provider |
| How quickly is value needed? | Slower | Potentially faster | Faster when implementation is included |
| Who integrates and supports it? | Internal team | Internal team or partners | Defined managed responsibility |
| What must remain under our control? | Architecture and roadmap | Configuration and data | Outcomes, data and service governance |
Look beyond licence cost
Compare the complete operating model: discovery, selection, implementation, data preparation, integration, security review, training, administration, support, upgrades, reporting and exit. A low subscription can still create a high internal workload.
McKinsey’s survey of 250 CIOs and technology decision-makers found that more than half believed close provider relationships were necessary to achieve their digital-transformation goals, while about 60% considered a provider’s ability to engage with the business an important selection criterion. The respondents were large organisations with substantial IT budgets, so the percentages are not direct SMB benchmarks. The principle is still useful: technology value depends on business engagement, not only technical supply.
Sequence the decision
- Define the business problem and the outcome that matters.
- Separate differentiating requirements from standard requirements.
- Assess the capacity to own implementation and ongoing operation.
- Compare build, buy and managed models using the same full-life criteria.
- Test one bounded workflow before expanding the stack.
- Record exit, portability and governance requirements before commitment.
RAAJE technology uses a managed model for current tools because implementation and ongoing operating support are part of the proposition. RAAJE Consulting remains available where the problem requires broader Strategy, Communication, Technology or Execution work.
Clear answers
When should a business build its own technology?
Build when the capability creates genuine strategic differentiation, standard products cannot meet an essential requirement and the organisation can own product management, security, maintenance and support over time.
When is buying software the better choice?
Buy when the requirement is common, a credible product already exists and the team has the capacity to configure, govern and operate it.
What does a managed technology model add?
A managed model combines software with implementation, operating support and defined accountability, reducing the amount of integration and administration the customer must own internally.
FAQ
Is building software cheaper than buying it?
Not necessarily. Building includes product management, engineering, security, maintenance, support and opportunity cost, not only initial development.
What is a managed marketing stack?
It is a set of commercial systems delivered with defined implementation, configuration, operational support and accountability rather than software access alone.
Does a managed service create vendor lock-in?
It can if data portability, configuration ownership, documentation and exit arrangements are unclear. These should be agreed before implementation.
Can a business combine build, buy and managed models?
Yes. Many organisations build differentiating capabilities, buy standard tools and use managed support where integration or operating capacity is constrained.
AJ’s perspective
Technology decisions become much clearer when ownership is treated as part of the product decision rather than something to solve later.
My starting question is not simply what a platform can do. It is who will configure it, connect it, support it and improve it after launch.
If that responsibility is unclear, a licence comparison is incomplete. A managed model can be the right answer when it closes that operating gap without taking control of the business outcome away from the customer.
New RAAJE series
Continue with the launch collection
From insight to implementation
Choose the ownership model before choosing the product.
RAAJE helps organisations define the requirement, assess operating capacity and implement a proportionate technology model without unnecessary complexity.
Start a conversationSources
- Scott Brinker and Frans Riemersma, State of Martech 2026, 6 May 2026.
- Zylo, 2025 SaaS Management Index, 16 January 2025.
- McKinsey & Company, CIOs are redefining what a successful relationship with their IT providers looks like, 1 October 2019. Survey of 250 global CIOs and similar decision-makers.