What does a Content Officer FTE own?
A Content Officer FTE on ftes.ai owns commerce content, the guides, comparisons and answers that help a shopper choose the store's products, in the Demand department of the e-commerce org chart. It is judged on citations and assisted revenue, and accountable for commerce content that earns both with every piece approved. It exists because the questions shoppers ask before buying are usually answered by someone else's page, and the store's own catalogue holds the facts to answer them better.
It does not own site-wide search and AI visibility for the business, which the Search Visibility FTE does for any company, or catalogue eligibility, which the Visibility Officer FTE owns. It owns the content that sits between a product question and a purchase.
How does it decide what to write?
The Content Officer FTE maps the questions shoppers ask before buying the store's products from three sources: pre-purchase support tickets in the help desk, on-site search terms, and the queries the Visibility Officer FTE tracks. Each question is scored by how often it is asked and by the revenue of the products it concerns, and checked against the site to see whether a page already answers it. The plan proposes pieces for the unanswered questions with the highest revenue behind them.
The plan is a proposal for the owner, who can reorder it, remove topics the store does not want to publish on, and add questions the data has not seen.
Where do a draft's facts come from?
A draft may use three sources: fields in the catalogue, copy the owner approved before, and public sources the owner has allowed with the citation shown. Every product claim, a weight, a material, a compatibility, a care instruction, maps to its source, and the map sits beside the draft in Approvals. A claim with no source is flagged, not written. Before a product is recommended, stock is checked, so a guide never sends shoppers to a size that is out of stock.
This is the same fact-gate the Product Catalog FTE works under, applied to long-form content.
What waits for approval, and where does it publish?
Every piece waits in Approvals in its final form, with the claim map, the stock check and the attribution plan for assisted revenue. The owner approves, edits or sends back with a note; notes become remit rules. On approval it publishes to the store's blog or pages, currently Shopify Blog or WordPress. Refreshes of existing pieces that lost citations are proposed the same way.
Once a class of piece has a long clean record, the owner can promote refreshes to publish without a gate; new pieces usually stay gated because voice is a judgment.
What does the Content Officer FTE never do?
It never invents a product fact, never publishes without approval, never recommends a product it cannot confirm is in stock, and never reports page views as if they were revenue. It never writes on a topic the owner excluded, and it never copies a competitor's page. It does not buy ads, run social, or write the site's non-commerce content.
It also never claims a citation it did not observe; citation counts come from the same weekly checks the Visibility Officer FTE runs.
What does it report, and how honestly?
The Content Officer FTE reports pieces published and refreshed, citations by assistant per piece, and assisted revenue per piece from the store's analytics, meaning orders whose session included the piece within the attribution window the owner set, printed on the report. It reports pieces that earned no citation and no assisted revenue as such, with the refresh or retirement it proposes.
Where analytics attribution is ambiguous, the report labels the figure and explains the limit rather than rounding it up.
How does it work with the other roles, and in which tools?
The Content Officer FTE reads pre-purchase questions from the help desk the Order Support FTE works in, queries from the Visibility Officer FTE, stock from the Inventory FTE, and product data from the Product Catalog FTE. It publishes to Shopify Blog or WordPress, measures with Google Search Console and Google Analytics 4, and its assisted revenue appears in the value ledger.
A store that runs the Search Visibility FTE may route commerce content through it instead; the Content Officer FTE is for stores that want product-question content judged on commerce numbers by a role that reads the catalogue and the stock.