Three ways to buy, and one reason not to.
Every engagement starts with the mapping call. Exact figures are quoted per category after that call, because library depth is gated by prominence tier and nobody should pay for persona depth their market position cannot use.
Query Map
The Run 1 architecture for one category: entity and landscape resolution, personas, head queries with verdicts, the 500+ row library, scored priorities. Yours to execute with any team.
- /Entity and citation landscape
- /3 to 6 persona cells
- /500+ labeled subquery rows
- /Scored priority stack
Architecture + Production
Run 1 plus Run 2: the full content pack produced against approved priorities, through extraction QA in your voice.
- /Everything in Query Map
- /Pages, blocks, posts, placements
- /Voice Card built from your writing
- /14-point extraction QA gate
The Engine
Quarterly library refreshes as engines change, monthly production sprints down the priority stack, capture updates on observable engines, and the measurement loop.
- /Quarterly library refresh
- /Monthly production sprints
- /Live capture on observable engines
- /Pairs with VISIBLD monitoring
When Citabld is the wrong buy, we say so on the call.
If you are the runaway category leader, engines already recommend you to everyone; spend elsewhere. If your category is answered almost entirely by institutions, the play is entity accuracy on those surfaces, not content volume, and that is a short, cheaper engagement. If your category resolves to "you do not need this," you will hear it from us first.