In short
- What you can hand over
- The finding-out and the writing. That is the largest part in hours and the smallest in risk.
- What stays with you
- What is accurate, and what appears under your name. Those two cannot be delegated, not even by contract.
- The agreement in writing
- What may be published without your consent. Usually nothing — and that should be written down.
Which three ways are there, and what shifts at each step?
Note the last row: it does not change. Who answers for what is published about your company shifts under no form of outsourcing — and that is exactly why the third column contains an approval per action and not a blanket mandate.
| What happens | All yourself | Prepared, you execute | Executed after your approval |
|---|---|---|---|
| Who finds the source | you | the service | the service |
| Who writes the text | you | the service, you check | the service, you approve |
| Who puts it online | you | you | the service, after your approval per action |
| Who is liable for what is written | you | you | you — which is why that approval is not a formality |
Why must the approval never disappear?
Because the mistakes that cost most are not language mistakes but factual ones. A text naming a service you do not provide, an opening hour that is wrong, a claim about an expired certification: all three read smoothly and all three can only be spotted by you.
Here that step is not a procedure but a gate in the code: certain actions cannot be executed without an approval attached. That is the difference between a promise in a contract and a boundary the system cannot cross.
Where does the risk sit with full outsourcing?
In two things that rarely appear in a quote. The first is access: whoever publishes on your behalf holds keys to your site, your profiles or your accounts. What happens to those keys when the collaboration ends belongs in the agreement and usually is not there.
The second is voice: a service handling fifty clients ends up writing roughly the same thing fifty times. That is not only dull, it is measurably harmful — pages that resemble each other crowd each other out, and that is exactly how a family of twenty-three pages once collapsed.
How do I choose which of the three suits me?
By one question: how many hours per month are genuinely available internally, not planned. If that is less than half a day, the middle column is an illusion — the fixes arrive and sit there, and then you are paying for a list.
Frequently asked questions
Can I take a package once and carry on myself?
Yes, and for the first round that is often the best ratio: the one-off things — access, structure, the first register listings — are also the things that yield most. What comes after is maintenance, and that is work more easily scheduled than clearing up years of backlog.
What if I disagree with a proposed text?
Then it does not go live, and that should be the default state rather than the exception. Here an action without approval simply waits; there is no setting that skips it, not even for a client who asks.
Read on
Free, no account and no card.