Why is this question even worth
The site is no longer a “one-time purchase”.[6] If a business counts on a stable flow of customers from search, the site simultaneously lives in three modes: it is developed (new pages, forms, integrations), it is promoted (SEO, content, links, analytics) and it is supported (updates, security, monitoring, rollback of incidents). These are three different disciplines, but they work with the same object - with one code, one database, one domain and one command on the client side.
In practice, a business almost always faces a fork in the road: hire three specialized contractors (each “the best in their own way”) or hire one agency that covers the entire cycle. On paper, the first model looks more reasonable - “professionals in their field.” At the level of daily work, it almost always comes up against the same thing: changes in the code break SEO settings, the SEO contractor requires improvements that the developer does not have time to implement, and technical support learns about the latter problem from the client’s ticket. In this article, we will look at why a single contractor most often turns out to be more economically profitable, in which cases this is not the case, and what to look for when choosing.
This is not the cost of contractor hours - it is easy to calculate. This is acoordination tax: the manager’s time on the client side, calls to find out “whose zone this is,” repeated task assignments, context reassembly and downtime between stages. According to various estimates, it eats up 20–40% of the project budget and is practically invisible in reports - because it is included in the salary of an internal employee.
Where is the budget lost with multivendor
To estimate the real cost of a divided model, it is useful to look at what it consists of - in addition to the actual payment to contractors.
Coordination and “football” of responsibility. Classic scenario: after updating the CMS, micro markup breaks. The SEO agency opens a ticket to the developer, the developer replies “everything was deployed as usual, this is an SEO module,” SEO says “the module has not changed, you rolled out the release.” While the sides are throwing the ball, positions in the search are sagging. The client's internal manager spends several hours just to find out which of the two contractors will take on the task.
Loss of context. The SEO contractor does not see the development backlog and learns about changes after the fact, when they are already in production. The developer does not understand which URLs and meta tags are critical for search, and can rename a template that has thousands of indexed pages behind it. Technical support does not know which forms close the sales funnel, and postpones the “non-priority bug” for a week.
KPI conflict. The SEO contractor’s KPIs are positions and traffic. The developer has stable releases and no bugs. Technical support has time to resolve the ticket. These metrics often work against each other: SEO wants edits at least every week, development wants rarer and more predictable releases, support wants a minimum of new errors. A single executive is forced to balance all three goals; three separate ones - each optimizes its own.
Parallel accounts, accesses, trackers. Each contractor has its own task tracker, its own Slack or Telegram chat, its own access to GA, Search Console, hosting, repository, CMS. The client has to agree on rights at each level and recreate them when rotating employees. Any incident requires gathering people from three different companies in one place - and this is not about a technical school, this is about a calendar.
Three typical contracting models
In practice, a company chooses between three approaches. Each has its own logic and its own weak points - let's analyze them in one format.
Inhouse team
expensive
Multi-vendor: 3 agencies
seams
Freelance stack
risk
Single agency
one contract
An important nuance: a “single agency” is not one person with three hats. These are separate teams (development, SEO, support), but under one legal entity, one project manager and one contract. This structure preserves the specialization of people, but removes the seams between companies.
The difference in qualifications between a good and a top specialist in one discipline is usually 10–20% on the result. Seam losses between three separate teams are 20-40%. This means that the gains from choosing the “best on the market” in each niche are most often eaten up by the coordination tax before it reaches business metrics.
Model comparison table
If you collect all the criteria by which a business makes a decision, the picture becomes more substantive. In the table below, we compare three working models - inhouse, multivendor and single agency - according to parameters that directly affect speed, cost and risks.
| Parameter | Inhouse | 3 agencies | Single agency |
|---|---|---|---|
| Coordination costs | low | high | low |
| Fixed expenses | high (payroll) | average | only agreement |
| Responsibility for metrics | director | blurred | one party |
| Single context project | yes | no | yes |
| Time-to-fix of a critical incident | 1–4 hours | 6–24 hours | 2–6 hours |
| SLA and legal liability | internal | 3 different SLAs | single SLA |
| Flexibility during load peaks | low | medium | high |
| Reporting for business | depends on PM | 3 reports | one summary |
| Vendor lock risk | no | low | managed by contract |
| Cost on the horizon 12 months | high | average | lower by 15–25% |
What exactly does a “single contract” include
When they say “one agency covers the entire cycle,” it is important to understand exactly which zones we are talking about. In the standard contract, ONTOP and similar full-cycle agencies cover four areas - below we will look at what is included in each.
Development and development of the platform
New pages and sections, forms and integrations, improvements for marketing, CMS core updates, transfer between servers, data migrations. Everything that requires working with code and templates.
SEO and content strategy
Semantics, landing page structure, meta tags, micro markup, site map, hreflang, internal linking, working with speed and Core Web Vitals[3], indexing control, links and content.
Technical support and monitoring
Security, updates, backups, monitoring availability and speed, responding to incidents according to SLA[5], working with logs and alerts, rolling back problematic releases, knowledge base on incidents.
Analytics and product hypotheses
Setting up GA, Search Console, goals and events, business dashboards, A/B tests, funnel reporting, a combination of marketing and technical contours, quarterly reviews of metrics.
The key difference from the multivendor scheme is that all four blocks live in one task tracker, one repository and one release calendar. This means that the SEO task “add Product markup to cards” ends up in the same backlog as developing a new shopping cart feature - and both tasks compete for priority transparently, rather than by mail between companies.
Where exactly does business save
“A single agency is more profitable” is not an abstract thesis. Below are four zones where savings are calculated in terms of money and internal manager hours.
With three contractors, the client’s manager spends 6-12 hours a week just on coordination: calls, forwarding tasks, clarification of statuses, coordination of accesses. With a single contract, this is one weekly status - 1-2 hours. At the horizon of the year, the difference is 200+ hours that the manager can spend on clients, and not on contractor logistics.
A new landing page in a split model is a chain: SEO prepares technical specifications, transfers to development, development puts it in the backlog, rolls it out for staging, checks SEO, returns the edits, and deploys the development again. Two weeks is a typical period.[2] In a single team, the same steps are done within one sprint: 3-5 working days.
SEO regressions after releases are the most expensive item of loss in a multi-vendor environment. If SEO sees the development backlog in advance and coordinates releases, critical regressions are caught in staging and not in production. One prevented two-week drawdown on commercial requests often pays for a single agency for the entire quarter.
Shared access, shared repository, shared monitoring - and you pay for the tools once, not three times. Parallel licenses for analytics systems, task trackers and subscriptions to SEO tools with three contractors are summed up; a single agency most often already includes its stack in the contract price.
When a single agency is not your option
Honest answer: a single contractor is not suitable for everyone. There are situations in which a divided or in-house model wins economically and organizationally. Below are two polar scenarios in which the solution is obvious.
When there is redundancy
You already have a strong in-house team
If there are 2-3 developers on staff, a dedicated An SEO specialist and system administrator, they already provide the context and speed of response that a single agency provides. In this situation, it makes more sense to involve external contractors on a targeted basis - for non-standard tasks: architecture audit, migration, complex integration, support for peak launches. A permanent contract with a full-service agency here will duplicate already paid functions.
When it is irreplaceable
Small and medium-sized businesses without a technical director
If there is no internal company a person who is able to provide technical specifications to the developer, check the results of the SEO contractor and evaluate the SLA of technical support, the multi-vendor model turns into a source of hidden losses - simply because there is no one to catch the seams. A single agency in such a situation covers both the role of the performer and the role of the technical partner: it sets tasks for itself, sets priorities and reports to the business in the language of metrics, not lines of code.
Also, a single agency is most often not suitable for a large enterprise with a complex project structure, where development is carried out by its own Agile teams, and only certain competencies are delegated to external contractors - say, SEO or external security audit. For such a mature structure, "all in one" means a loss of internal flexibility.
How to remove the risk of vendor lockin
The main rational argument against a single contractor is the risk of dependence. If development, SEO and support are from one company, then its departure or a price conflict could theoretically paralyze the project. This is a serious argument, but it is resolved not by splitting teams, but by the structure of the contract.
1. Export rightCode, database, media files, documentation - all this belongs to the client and is uploaded upon first request in standard formats. Must be stated in the contract.
2. Documentation of processesThe agency must have an up-to-date technical knowledge base: how the infrastructure is structured, where there are accesses, how releases are made, what external services are connected. Without this, any transition becomes reverse engineering.
3. SLA with clear metricsIncident response time, resolution time, uptime percentage, penalties. This is not a formality - it is the basis for quality assessment and leverage for the contract.
4. The right of independent auditThe client can at any time hire an external expert to check the code, security and SEO status. The agency is obliged to provide full access.
With this contract structure, changing the contractor is a matter of 1-2 months of planned handover, not a disaster. This removes the main fear and makes choosing a single agency rational - and not risky.
Checklist: how to choose a single contractor
If the “all in one” model looks suitable for you, you should choose a specific agency not by its website and portfolio, but by seven points that show the maturity of its processes.
- Portfolio in all three areas. Look at the cases separately for development, separately for SEO, separately for technical support. If one of the blocks is empty or the descriptions are general, the agency will most likely subcontract this direction outward.
- Team composition, not one person with three roles.Make sure there are dedicated developers, SEO specialist, DevOps/support and project manager. A narrow “team lead who can do everything” is a freelance stack under the guise of an agency.
- SLA for incidents, and not just for project tasks.Check the response time if the site crashes at 2 a.m. on Saturday. If the answer is “we work on weekdays from 10 to 19” - this is not support, this is the development department.
- Single tracker and access to sources.All tasks should go to one task tracker, to which the client has access. The code is in the client's repository or transferable. Documentation is in a common space.
- The right to export and exit.Right in the contract: the client can terminate the contract, take away the code, database and documentation. The agency is obliged to carry out the transfer to the new contractor.
- Quarterly business reviews, not just technical reports. A mature agency reports not on the number of closed tickets, but on changes in business metrics: conversion, applications, search traffic, loading speed, cost attraction.
- Transparent price structure. It should be clear what is included in the fixed part (support, monitoring, reporting), what is charged by the hour (development), what is charged in separate packages (SEO). “Total amount per month” without breakdown - flag.
“Unique SEO technique”, “TOP 10 guarantee in 3 months”, “our DevOps is the best in the country”, “we are not We disclose the technology stack before signing the NDA.” These are marker phrases that in 90% of cases mean either resale of other people's services or unwillingness to be responsible for real metrics.
Frequently asked questions (FAQ)
Will I overpay for “all in one” if I only need SEO?
No - an adequate agency does not force you to take the whole package. Typically, three scenarios are possible: outsource only SEO, start with SEO and gradually add development/support, or immediately connect a single contract. Overpayment only appears if you take services that you do not use. The benefit from a “single contract” arises when you simultaneously have a need in two or three directions - then the coordination gain covers the discount from narrow contractors.
What if the agency is weaker than a specialized contractor in one of the areas?
This is a fair risk, and it is checked before signing - with cases and a test task. A useful technique: ask the agency to do a mini-audit of your website in all three areas. Based on the structure of the audit (depth of SEO analysis, quality of technical recommendations, vision of support), you can immediately see where the agency is stronger and where it is “at the level of the market average.” If a weak point is critical for your business (for example, you work in a competitive SEO market), it makes sense to leave this area to an external specialist, and outsource development and support to a single contractor.
How to avoid vendor lock-in with a single contract?
By a contract, not by fragmentation. The agreement should include: the right to export code and data in standard formats, the obligation to maintain up-to-date documentation, an SLA with metrics and penalties, and the right to an independent audit. Under such conditions, a transition to another contractor is a 1-2 month planned transfer, not a disaster. Any scenario “we will not give away the code without an additional agreement” is a reason not to work with such an agency in principle.
How long does it take to transfer cases when changing the contractor?
With good documentation and a written right of exit - 4-8 weeks. Of these, 2 weeks are spent on uploading and reviewing code, documentation and infrastructure by the new contractor, 2–4 weeks on parallel work (the new one carries out tasks under the supervision of the old one) and 1–2 weeks on the final verification and release of the old contractor from access. If the documentation is poor, the deadlines are unlimited, so the clause about documentation in the contract is critical.
Is it possible to start with one direction and gradually add others?
Yes, this is the safest scenario when choosing a new partner. The usual sequence: first technical support (minimal risk, the quality of the SLA is quickly visible), then SEO (results within 3–6 months), then development (the most budget-intensive part). After six months of such gradual connection, you accumulate enough observations to decide whether to switch to a full contract - or stop at one or two services.
How to measure the effectiveness of a single contractor if there is no internal expert?
By business metrics, not by technical reporting. Record in the quarterly review: traffic from search (Google Search Console, Yandex.Metrica), the number of applications from the site, cost of attraction, uptime and average page loading time. These numbers are understandable without technical education. Once a year, it is useful to order an independent audit from an external expert - this is both an audit of the agency and insurance in case of controversial situations. The cost of such an audit is 1–2% of the annual budget for website support; it pays off several times due to prevented problems.
What is the difference between a “single agency” and “IT department outsourcing”?
IT department outsourcing is, as a rule, technical support for infrastructure: servers, workstations, corporate mail, VPN. A single full-cycle agency specializes specifically in the website and digital channel of attracting clients: development, SEO, web analytics, product work. These are different markets and different competencies. For a business whose website is the main lead generation tool, the second is more critical; the first can be closed separately or in-house.
ONTOP Practice
We at ONTOP were initially built as a full-cycle agency: the Drupal development team, SEO direction and technical support work under one project manager and in a single client repository. This means that the micro markup task ends up in the same backlog as the release of the new section; a drop in positions after a core update is caught by the same SEO specialist who coordinated this release a week earlier; and the incident with the feedback form at 23:00 is sorted out by the DevOps on duty, and the chain “SEO → development → support → back” is not created.
For business, this is expressed in specific numbers: one monthly report instead of three, one manager on call instead of three accounts, one legal entity for accounting instead of three contracts. And most importantly, there is one person responsible for business metrics: applications, traffic, conversion. In practice, this format is most often chosen by companies whose website is the main channel for attracting customers, and who at the same time do not want to maintain an in-house team.
We will discuss one contract for development, SEO and support specifically for your project - with a transparent SLA and the right to exit
Conclusion
A split contracting model—development separately, SEO separately, support separately—looks more reasonable at the “let’s hire the best in each niche” level. At the level of daily work, it almost always comes down to coordination tax: seams between companies, KPI conflicts, blurred responsibility for business metrics, and a two- to three-fold increase in time-to-fix for incidents.
A single agency solves these problems not with magic, but with structure: one contract, one manager, one SLA, one tracker, one party responsible for the metrics, and not for their area. In this case, the risk of vendor lock-in is removed not by splitting up teams, but by a competent contract - the right to export data, documentation, SLA and independent audit. As a result, the “all-in-one” model over a 12-month horizon provides, in our experience, savings of 15–25% of the total costs of maintaining a website - and almost always the best result in business metrics.
The only fair exception is companies with a mature in-house team or large enterprise structures where contractors are connected point-by-point. For small and medium-sized businesses whose website operates as the main sales tool, a single contractor is almost always more profitable than trying to build an orchestration of three separate agencies.
Sources
- Deloitte - Global Outsourcing Survey - annual management survey external contractors, coordination costs and multi-vendor procurement models for IT services.
- PMI - Pulse of the Profession - industry review of the Project Management Institute: statistics on deadlines, budgets and project failures with distributed responsibility.
- Google Search Central - Core Web Vitals - official Google documentation on the ranking factor, which directly depends on the quality of development and technical support of the site.
- Atlassian - SLA vs. SLO vs. SLI - practical analysis of response time metrics and incident resolution, by which the quality of technical support is assessed.
- Axelos - ITIL 4 Service Management is an international standard for IT service management, including Service Level Management and Incident Management, applicable to the support of web projects.
- Deloitte Insights - Tech Trends - annual review of digital transformation trends: a shift from the “project” development model to the continuous maintenance of digital channels.
