A done-for-you service is a good purchase when handing the work over costs less, in attention and risk as well as money, than keeping it inside the business. That is a decision to make for a particular job. A founder may sensibly outsource a website migration while continuing to write the company newsletter. The right answer depends on what the team needs to learn, what it can already do and what would happen if the work went wrong.
The frame below is an editorial decision aid, not a universal scoring system. Use it to compare one defined task across four questions: time, skill, risk and handoff cost. Avoid beginning with “Should the business outsource marketing?” That question is too broad. “Should an outside team produce the next campaign landing page?” is specific enough to examine.
First, describe the finished job
Write a sentence that another person could use to recognize completion. For a landing page, that might include an approved page published on the company’s site, tested on agreed devices and connected to the existing enquiry form. It should say who supplies the offer and who approves the copy. A result that cannot be described is difficult to price, delegate or review.
Separate the work from the hoped-for business outcome. A finished landing page is observable. A stronger sales pipeline depends on more than the page. This does not make commercial goals irrelevant; it means the buyer and provider need to discuss which parts of the goal the engagement can influence. A useful proposal explains both the deliverable and the limits of that influence.
Time: count the complete internal effort
DIY time includes learning, production, troubleshooting and the work displaced while those things happen. Estimate the whole sequence. A manager might spend an afternoon building a draft, then several more sessions fixing mobile layouts, gathering approvals and reconnecting a form. Counting only the first afternoon makes the comparison misleading.
External delivery also consumes time. The buyer still needs to brief the provider, answer questions and review the result. Put those tasks on the same calendar as the internal option. If the company cannot make the required decisions this week, an outside team cannot manufacture approval capacity. A service becomes more attractive when it removes substantial production work while leaving a manageable amount of customer participation.
Use rough ranges if precise estimates would be fiction. The purpose is to expose the shape of the work, not to create a spreadsheet that looks exact. Identify the largest uncertainty and ask what would reduce it. A sample task, a technical assessment or a clearer brief may change the decision more than another round of hourly comparisons.
Skill: decide what should stay inside
Some tasks teach the business something it needs to understand firsthand. Early customer interviews are an example. An outside researcher can help, but a founder who never hears customers describe their problems may miss information that matters to product decisions. Learning can be part of the return from doing the work internally.
Other tasks depend on specialist knowledge the team needs only occasionally. A one-time migration or a particular production technique may be a better candidate for outside delivery. The question is not whether an employee could eventually learn it. Ask whether developing that capability is a sensible use of attention given the company’s actual priorities and likely future workload.
A mixed arrangement can preserve the important learning. The team could define the offer and review customer language, while a specialist handles page design and implementation. Make that division explicit. “Collaboration” is not a useful scope description until both parties know who creates, who decides and who checks each part of the job.
Risk: examine errors and reversibility
Look at the consequence of a mistake. An awkward draft in a shared document is easy to fix. Incorrect changes to a live system may affect customers or interrupt operations. The more consequential the work, the more the buyer needs evidence of relevant competence, a review method and a plan for handling problems.
Outsourcing does not transfer every business responsibility. The customer may still own the accounts, approve the information and decide when a change goes live. Ask the provider to explain how work is checked and what happens if the check fails. A confident sales conversation should lead to a concrete answer, not a promise that nothing ever goes wrong.
Reversibility can guide the size of a first engagement. Start with a small, representative piece of work when that gives a fair test. A draft campaign asset may reveal communication and review quality. A migration rehearsal may reveal data problems. Choose a pilot that tests the difficult part of the relationship rather than an easy task unrelated to the eventual service.
Handoff cost: account for knowledge that is hard to write down
Some work is easy to transfer because the inputs and standards are already documented. Other work depends on a founder’s unwritten preferences or a team’s informal understanding of exceptions. The second kind requires discovery before it can become a repeatable package. Paying for production does not remove that need.
List what a competent outsider would need on day one. Include files, access, examples, decisions and a person who can answer questions. If the list is long but stable, the initial effort may be worthwhile across a continuing relationship. If the underlying direction changes every few days, a fixed delivery package may be a poor match until the business resolves those choices.
Documentation can improve either option. Asana’s scope management guide describes documenting project boundaries and deliverables. For this decision, even a one-page description can expose missing inputs before they become provider delays or internal rework. The brief remains useful if the team ultimately chooses DIY.
Work through a concrete comparison
Imagine a small consultancy with an approved workshop offer and a launch date. Its founder can explain the workshop well but has little experience publishing pages. A colleague can supply images and manage approvals. An external provider offers a defined page build using the existing site, with an agreed review round and a test of the enquiry path.
Time points toward outside help because the founder would otherwise need to learn the publishing system. Skill also points outward because page production is not a capability the consultancy expects to use often. Risk is manageable if the provider can work in a review environment and the company approves the live change. Handoff cost is moderate because the offer is already decided and the source material exists.
Now change one fact: the consultancy has not agreed what the workshop includes. The provider can still build a page, but the central decision remains unresolved. Buying a fixed page package may produce repeated copy changes. A short offer-development engagement or internal working session should probably come first. The delivery model depends on the readiness of the job, not just the attractiveness of the package.
Make a decision with a review date
For each of the four questions, write “internal,” “external” or “uncertain,” then one sentence explaining why. Do not total the labels mechanically. A major risk issue can outweigh several small time savings. Resolve the uncertainty that could change the answer before committing to a larger engagement.
If outside delivery wins, agree on a first review point and retain the files needed to continue the work later. If DIY wins, put the full effort on the calendar and identify when to reconsider. After completion, compare what happened with the estimate. Atlassian’s project review template offers a structured prompt for capturing lessons. A short, honest review makes the next outsourcing decision better grounded than the last.