Skip to main content

    B2B & Professional Services · project showcase · content architecture

    Project ShowcaseReal client work that shipped. No performance figures are published, because none have been verified and approved for release.

    An expert answer library: articles built so a machine can attribute the answer to a named person

    Most professional-services content is written to show a firm is knowledgeable. This library is written so a search engine *and* an answer engine can retrieve a specific answer and attribute it to a specific named practitioner.

    At a glance

    The engagement in brief

    Services

    • Content
    • AEO GEO
    • Personal Brand
    • Content Systems

    Stack

    • Question inventory
    • Article brief template
    • Schema markup
    • Google Search Console
    • LinkedIn

    The situation

    What we walked into

    A professional-services expert's knowledge is almost entirely spoken. It exists in calls, panels, internal memos and the two minutes after a meeting ends, and none of that is retrievable by anyone who was not in the room. The library exists to convert what the practitioner already says into a form that both a search engine and an answer engine can find, quote and credit — under a person's name rather than under a firm's.

    An answer engine cannot cite a conference panel. If the analysis is not written down under a name, the citation goes to whoever wrote it down instead.

    What we found

    The diagnosis

    1. 01

      The unit is the question, not the topic

      A topic produces an article nobody searched for. A question produces an article that matches a query, an answer that can be lifted into a summary, and a heading a reader can scan to. The inventory is built as questions first and grouped into themes afterwards.

    2. 02

      Attribution needs entities, not adjectives

      A model resolves names, statutes, jurisdictions, agencies, dates and roles. It cannot resolve 'leading practitioner' or 'decades of experience'. Every brief in the library carries a required entity list, and an article that names none of them is not finished.

    3. 03

      Publishing under a person is an approval problem before it is a writing problem

      Inside a firm, a byline is a risk decision made by someone who is not the writer. The schema carries an approval owner and a review-by date on every row, and the draft is written in two versions — the answer and the caveat — so the review conversation is about the caveat rather than about the whole piece.

    4. 04

      The library and the profile are one artefact

      The featured section on the practitioner's profile is the table of contents. An article that does not earn a place there has been written for the archive rather than for a reader.

    The number behind it

    What this is built around

    High-growth professional-services firms are **2.5× more likely to activate their subject-matter experts** (Hinge *High Growth Study 2026*, 770 firms). As answer engines take share of research, named-expert attribution is how that activation shows up in AI results.

    What we built

    The system

    Each row in the library carries the question in the words a buyer would use, the buying stage it belongs to, the required entity list, the primary sources to cite, the approval owner, the review-by date, the internal link targets, the derivative social post, and the digital PR angle. The article itself opens with the direct answer in the first forty to sixty words underneath a question-shaped heading, then expands, then qualifies. Specifications and definitions are marked up as structured data rather than left as prose. Internal links point from the general question to the specific one and never the reverse, so the library has an obvious entry point for a reader arriving from a summary with no context.

    An expert answer library: articles built so a machine can attribute the answer to a named person — stackA stack of 9 connected layers, from "Question inventory" through to "Digital PR angle", each feeding the one below it.Question inventoryRequired entity listPrimary sourcesAnswer-first draftFirm review (named owner)Published article + schemaProfile featured itemSocial derivativeDigital PR angle

    The sequence

    How it was delivered

    1. Week 1

      Question inventory

      Questions in buyer language, grouped into themes, ranked by buying stage

      Owner: OmniFlow + practitioner

    2. Week 1

      Brief schema

      Row schema with entity list, sources, approval owner and review-by date

      Owner: OmniFlow

    3. Week 2

      Approval route

      Named reviewer per theme, two-version drafting rule agreed before the first article

      Owner: OmniFlow + firm

    4. Week 3 onward

      Publishing

      Answer-first articles, schema markup, internal links, featured-section placement

      Owner: OmniFlow

    Outcome

    What shipped

    This entry makes no performance claim. It documents a content architecture and the constraints it was designed against: a busy practitioner, a firm review gate, and two different machines that need to find the same answer.

    Reporting

    What you would actually see

    These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

    These are demo dashboards. They show the reporting surfaces this engagement is run and measured from, with representative figures generated around the published benchmarks cited on this page — not a client account and not a client result. Live reporting for your own account replaces every number here.

    Google Analytics 4

    B2B & Professional Services · all web data

    Demo
    Acquisition overview
    Last 12 months vs. preceding period

    Sessions

    5,098

    +81.8%

    Key events

    123

    +102.3%

    Session key event rate

    2.4%

    +0.7%

    Engagement rate

    54.0%

    +6.4%

    Sessions by month

    AprJunAugOctDecFeb

    Dashed line marks the month the engagement started.

    Session default channel groupSessionsKey eventsRate
    Organic Search2,128472.2%
    Paid Search1,197252.1%
    Direct878263.0%
    Referral440112.5%
    Organic Social45692.0%

    LinkedIn Campaign Manager

    Sponsored Content · B2B & Professional Services audience

    Demo
    Campaign performance
    Last 12 months

    Impressions

    128,046

    +43.0%

    Clicks

    801

    +47.3%

    CTR

    0.6%

    +0.14%

    Cost per lead

    $148.52

    -15.5%

    Impressions by month

    AprJunAugOctDecFeb

    Dashed line marks the month the engagement started.

    CampaignImpr.ClicksLeadsCPL
    Thought leadership — practice leads43,53627226$148.52
    Problem-aware — retargeting33,29220820$148.52
    Case study download28,17017617$148.52
    Webinar registration23,04814414$148.52

    Honestly

    What we would do differently

    The approval route was designed after the first three articles rather than before them, which cost two full rewrites and a fortnight. A named reviewer and the two-version drafting rule should exist before article one, because the thing that stalls an expert content programme inside a firm is never the writing.

    Next

    Start the same conversation

    Start the same conversation

    Tell us what you are working on and we will say plainly whether this is the right shape of engagement for it.

    We use your details only to respond to this request. No lists, no resale.