What changes when production moves?
A freelance roster produces pieces to briefs, at a rate per piece, with quality that varies by writer and facts that are checked as well as the editor has time for. A Content & SEO Engineer Digital FTE on ftes.ai produces clusters: a hub and its spokes, each drafted through the fact gate from approved sources, linked to each other, carrying the structured data the page type needs, and published on approval through the site's route. The migration moves the production of clusters and keeps the writers whose craft the site's flagship pieces need.
The comparison piece on a Content FTE against freelance writers sets out the division; this guide is about the move.
What should you keep with the writers?
The two or three writers whose voice and craft you can name: the ones who write the flagship pieces, the opinion pieces, the pieces that need an interview or a point of view. Keep them at a rate that reflects craft rather than volume. Brief them from the FTE's worth-it verdicts, so their pieces answer questions people ask, and pass their pieces through the fact gate before publication like everything else, which good writers welcome because it protects their name. Let the rest of the roster lapse as their current briefs complete.
The writers who remain usually find the briefs better, because a verdict is a better brief than a topic.
What moves to the FTE, and in what order?
First, record the baseline: cost per published piece across the roster, editing hours per piece, and time from brief to publication. Second, approve the sources and the Brand Brain, and connect the publishing route with a scoped account. Third, choose one cluster from the Search Visibility FTE's verdicts, or from a hand-run worth-it test, and let the Content FTE draft the hub and spokes while the writers finish their current briefs. Fourth, at the first review, read the fact gate results and the send-back reasons, and start the second cluster. Fifth, once two clusters are complete, brief the retained writers on the flagship pieces the hubs will link.
The cluster is the unit of the migration; do not move piece by piece.
- Baseline: cost, editing hours, and time per piece
- One cluster with the FTE; writers finish current briefs
- Retained writers briefed from verdicts after two clusters
What breaks in the first month?
The briefing habit. Briefs used to be topics; now they are verdicts with evidence, and the marketing lead has to stop commissioning pieces because they seem relevant. The writers' pieces also break at the fact gate: a good writer's draft may carry a statistic from memory or a comparison without a source, and the gate flags it, which is a conversation with the writer about sourcing rather than a rejection of the writer. And editing breaks in a good way: the lead's editing hours fall on the FTE's spokes and concentrate on the writers' flagship pieces, which is where editing was always worth it.
The content standard behind this library forbids invented statistics for the same reason the gate flags them.
What does the record show after a cluster?
A complete cluster in the Library tab: hub, spokes, links, schema, every claim with its source, every publish with its approver. Cost per published spoke from the role's usage against the roster's rate. Editing hours per piece against the baseline. Time from verdict to publication. The send-back reasons sorted, with tone reasons falling to a background level by the cluster's end. And the console's movement for the cluster's queries, read as an association with the pages published, not as a claim.
The metric explainer on cost per outcome shows the arithmetic for cost per published page.
What should you refuse during the migration?
Commissioning pieces by topic once verdicts exist. Publishing a writer's piece around the fact gate because the writer is good. Moving piece by piece instead of by cluster, which loses the linking and the schema. Promoting publishing to autonomy in the first quarter. And ending the retained writers' engagements, because the flagship pieces are where the site's authority comes from and the FTE does not write them.
The CMO persona piece describes what the agency and the freelancers become after the move.