Parsing for the Duo: How Boutique Consultants Format Case Studies for Apple and OpenAI

Ben Thompson of Stratechery recently introduced a term that should make anyone selling high-ticket expertise sit up a little straighter: the Duo. This portmanteau represents the deepening integration between Apple’s on-device intelligence and OpenAI’s cloud-hosted models—a tag-team that is rapidly positioning itself as the primary filter through which affluent, high-intent users interact with the digital world.

For boutique consulting firms, this integration represents a fundamental shift in how new business is won. Historically, a partner at a specialized firm could rely on a beautifully designed PDF or a narrative-heavy case study page to impress a prospective client. Today, however, that prospective client is increasingly likely to ask an on-device assistant to find a consultant who has successfully resolved a supply chain bottleneck in the mid-Atlantic food distribution sector.

If the Duo cannot parse your past performance, your firm simply does not exist in the output. Winning this game requires moving past human-centric design aesthetics and structuring your proprietary insights so that conversational agents can ingest, verify, and attribute them.

The Semantic Scaffold: Schema Markup Beyond SEO

For years, search engine optimization specialists treated schema markup as a way to win star ratings or recipe badges on Google search results pages. In the era of conversational agents, schema is the actual API of your website.

When an LLM-driven agent crawls a page, it does not read the way a human does. It looks for structured relationships between entities. For a consulting firm, the most critical schema type is not Article or WebPage, but rather TechArticle or a highly structured Product schema representing your specific service offerings, coupled with AboutPage schemas that link your partners to verifiable external entities—such as their LinkedIn profiles or published books.

To make your case studies machine-readable, you must explicitly declare the entities involved in your work. This means wrapping your case study metadata in JSON-LD that specifies: * The client’s industry (using standardized NAICS or ISIC codes). * The specific problem addressed (defined via standardized DBpedia or Wikidata URIs). * The precise methodologies employed.

By providing these explicit semantic guardrails, you prevent the Duo from hallucinating the context of your work. You are telling the model exactly what you did, who you did it for, and what the outcome was, using a structured syntax that the model can ingest without having to guess at the meaning of your marketing copy.

Eliminating Prose Friction: Plain-Text Accessibility

The reality of modern LLM retrieval-augmented generation (RAG) systems is that PDFs are a structural nightmare. They are hard to parse, their reading order is often interrupted by multi-column layouts, and their tables frequently render as unreadable gibberish to a parser.

To ensure your proprietary insights are accessible to the Duo, every case study must exist as a clean, semantically structured HTML page. This means: * Using hierarchical heading tags (h2, h3, h4) strictly for structure, never for styling. * Presenting data in simple, native HTML tables rather than embedding charts as images. * Avoiding JavaScript-heavy scroll effects or lazy-loading techniques that block search crawlers and LLM user-agents from reading the full text of the page on the first pass.

If you must include a visual chart for human readers, always pair it with an explicit, screen-readable description or a simple raw data table directly beneath it. The agent will parse the table, and human readers can look at the chart. Both pathways must be supported to ensure your performance data is properly ingested.

Direct Attribution and the Zero-Click Reality

One of the greatest anxieties surrounding the rise of conversational search is the zero-click phenomenon, where an AI agent synthesizes your content to answer a user’s question without ever sending the user to your website.

The strategy for boutique firms is not to withhold information in an attempt to force a click—a tactic that simply guarantees the agent will ignore your site in favor of a competitor’s. Instead, the goal is to write in highly specific, proprietary frameworks that are difficult to summarize without attribution.

When you describe a client engagement, avoid generic advice like “we optimized their operations.” Instead, name your proprietary diagnostic framework or your specific sequence of interventions. When the Duo synthesizes this information, it is forced to reference your specific methodology by name.

Furthermore, ensure your author profiles are tightly integrated into each case study page. By linking the successful outcome of a project directly to a specific partner’s bio—complete with their professional history and external publications—you make it easy for the agent to recommend the human behind the work. The Duo can then answer the user’s query not just with a summary of the solution, but with a direct recommendation: “This specific firm, led by this partner, has solved this exact problem using their proprietary methodology.”

This article was generated with the help of AI.