Comparing the ways to buy corporate communications on responsibility, charging and exit

The useful comparison is not "agency versus software" in the abstract. It is which route can complete one authorised job while the buyer retains factual authority. The case here is fictional: an England-operating manufacturer must explain a confirmed change to service access to employees, contracted customers and suppliers, then publish a correction if an approved fact changes.

No route below has a default price, capacity or quality advantage. Those fields stay blank until a buyer has dated evidence.

Like-for-like comparison

Route	Buyer keeps	Supplier or system delivers	Charging unit to request	Exit evidence
Buyer-owned manual baseline	All approvals, writing, channel operation and records	None	Internal hours by role and period	Approved source, send logs and archive remain with buyer
Defined external project	Authority, claims and final acceptance	Agreed outputs for one scope	Fixed deliverable, time unit or milestone, with VAT status	Editable files, decision log, rights schedule and final invoice
Retained specialist advice	Decision rights and publication approval	Recurring advice or drafting within a stated allowance	Period, included units, overage and notice	Current work list, unused-unit rule and handover
Embedded or interim capacity	Employment and contractor-status decisions, access approval and supervision	Named temporary capacity	Time unit, minimum commitment and expenses	Access removal, record transfer and account closure
Managed communications operation	Policy, reserved decisions and oversight	Contracted workflow across defined channels	Service period plus transaction or change units	Queue export, correction history, continuity plan and deletion record
Software-supported self-service	Every communication decision and human review	Configured storage, workflow or distribution functions	Edition, user or usage unit, term and add-ons	Open-format export, access revocation and verified deletion

Responsibility cannot be bought away

A supplier can prepare text or operate a workflow, but the organisation still needs a named factual owner and publication authority. If material becomes marketing, CAP Code section 3 says objective claims within its remit should be supported by documentary evidence before publication. That gate belongs to the actual content and channel, not to the chosen commercial model.

Contact handling needs a separate decision. The ICO's business-to-business marketing page does not turn public details into unrestricted permission. Ask each route to identify controller and processor roles, data source, purpose, recipient type, transparency, objections and suppression.

Rights also remain explicit. IPO copyright ownership guidance says the creator of commissioned work is normally the first owner unless the parties agree otherwise in writing. A buyer should record ownership and licences for copy, photographs, research, templates and later edits.

Treat hard gates separately

Security, accessibility and exit are not scoring bonuses. The NCSC's supply-chain control guidance supports clear security responsibilities, subcontracting controls, incident routes and return or deletion terms. The buyer should also define accessible formats and test them with the intended audience rather than accepting a generic capability claim.

Compare acceptance, not presentation

Ask each route to process the same authorised, non-live fixture. Evidence should show who changed the source, which version was approved, how each eligible audience was selected and whether a correction can be traced. Do not send the fixture to real recipients. A successful desk exercise demonstrates the configured workflow only; it says nothing about persuasion, employee understanding, customer behaviour or commercial return. Record untested functions as unknown.

Choose a route only after filling the same blanks: eligible recipients, approval owner, deliverable, acceptance evidence, unit, period, VAT position, internal labour, correction path, renewal and exit. A hybrid may be sensible, but splitting work does not remove the need for one accountable communication record.