The short version
- Handoff is the bottleneck in most marketing teams. The skill on either side of it was never the problem.
- The failure mode is building what you should have bought.
- Hire a builder who can read a page critically. Two specialists with a document between them is the arrangement you are removing.
Three AI engineers work inside our marketing team rather than in a queue behind it. What changed was ownership. The person who decides what a page says now decides what it does, and the brief that used to carry one decision across to the other is gone, along with everything that fell out of it in transit.
What actually breaks in a handoff between writer and developer?
The spec. A page is a long run of small decisions about emphasis and order, and about what each heading has to do to the reader. A brief carries the loudest of them and drops the rest, so whoever implements the page makes those decisions again with less information than the person who made them first.
Then the loop runs. Draft, ticket, build, review, comment, rebuild. Every pass crosses a scheduling boundary, and a question that could be answered in the time it takes to read it waits for the next standup instead. The work is small, and the queue wrapped around it is not.
The same work, seen from both arrangements:
| The work | Its size | What a handoff adds to it |
|---|---|---|
| Programmatic content engine | 255 pages | A template spec nobody writes, or 255 tickets |
| Enterprise site rebuild | 42 routes | Copy handed across in a document, then retyped |
| Automated publish gate | 44 pages guarded | A style guide nobody runs |
| Rewording a page that is already live | A sentence | A ticket, and a wait behind everything already queued |
What changes when the writer can ship?
The unit of work shrinks. A schema field missing from a template gets fixed in the session somebody noticed it was missing, because noticing and fixing are now the same person’s job. It never becomes a ticket with a queue position in front of it.
On one account, 44 content pages sit behind a script that refuses to publish a page below the standard those pages are held to.
Where does this go wrong?
Engineers inside a marketing team build. The test we hold to: build when the workflow is the product, and buy when a company already exists whose only job is maintaining that thing. A publish gate that encodes one client’s editorial rules has to be built, because nothing off the shelf knows those rules. A course platform does not.
Who do you actually hire for this?
Someone who can read a page critically and ship it. The expensive mistake is hiring a strong engineer who treats copy as content to be placed, which rebuilds the handoff you were deleting.
The people who write the page can now build it.
What does this not fix?
The workload. Pages still get written one at a time by a person who has to understand the client’s business and everything the account has done since it started. What went away was the waiting.
It also hands the writer a production risk that used to sit with somebody else. On one engagement the publish path ran through a git push, and the deploy command that looks obvious for that stack would have overwritten the live site. Learning how a client publishes is now part of learning the account, and it has to happen before anyone has write access rather than after.
Related reading: why style rules need a script and what a CMS migration actually costs.
Frequently asked questions
Should a marketing team hire engineers?
If the team ships web pages or tooling, yes. What you gain is speed of correction rather than extra build capacity. The person who decides what a page says can change what it does, so the brief and the queue behind it stop existing.
What does an engineer do on a marketing team?
Builds the machinery the content runs on: page templates, generators that turn a data file into a set of pages, validators that block a post below standard, and the tracking that makes any of it measurable. Almost none of that arrives as a brief.
Is it cheaper to hire a marketing engineer or use a development agency?
We have not measured the two against each other, so the case for hiring is not a cost case. It is that a small change to a page has to be written down for somebody who did not write the page, and then it waits its turn behind everything already in the queue.
What goes wrong when a marketing team builds its own tools?
It builds things it should have bought. The test is whether the workflow is the product. A publish gate encoding one client's editorial rules has to be built, because nothing off the shelf knows those rules. A course platform or a CRM should be bought.
What should you look for when hiring an engineer into a marketing team?
Judgement about copy alongside the ability to ship. An engineer who treats copy as content to be placed rebuilds the handoff you were trying to delete.
Does hiring engineers into marketing reduce the workload?
No. It removes waiting. Pages still get written one at a time by someone who understands the client's business. What disappears is the queue between the draft and the live page, plus the second round of decisions made by whoever implemented it.
Sources
- Chua Network delivery data across 8 client accounts (internal fact bank)
- Chua Network engagement records, anonymized (internal experience bank)
