Case Study · Enterprise Telecom Advisory

How an Enterprise Telecom Advisory Got Named in ChatGPT Before the Form Fill

Enterprise advisory doesn't convert on blog clicks. The buyer is a VP of Infrastructure or a CIO. The cycle runs 6 to 18 months. The first touch is almost never a form fill. This engagement was built around a different question: when a sophisticated buyer asks an AI assistant about their problem, whose name shows up?

The starting point

The client is an advisory firm working at the enterprise tier of telecom and communications infrastructure. Their buyers are decision-makers at Fortune 1000 companies evaluating carrier contracts, unified communications migrations, and network modernization programs. Average engagement size is six figures. Sales cycles run 6 to 18 months. The buyer has read everything before the first call.

Traditional SEO metrics don't move the needle here. Nobody is going to Google "enterprise UC advisory" and picking a firm off the results page. What matters is earlier: when a VP asks ChatGPT to compare approaches to SASE deployment, or when a procurement lead asks Claude for a framework to evaluate carrier RFPs, whose thinking gets cited? That's the battleground.

What we built

The strategist built a narrow, deep content plan around the specific advisory questions this firm actually wins on. Each topic was treated as a thesis. The anchor piece wasn't a generic 3,000-word overview. It was a publishable framework with a name and a point of view. Supporting pieces extended the framework into specific enterprise scenarios: carrier consolidation, hybrid workforce UC, zero-trust networking, procurement governance.

Every piece shipped structured so AI assistants could lift it cleanly into a response: named frameworks, cited data, primary-source references, direct-answer sections. Visibility was tracked daily on both Google rankings and mentions in ChatGPT, Claude, and Gemini. In this market, the second metric matters more.

A content agency chasing organic traffic would have published broader, shallower pieces on high-volume keywords. That's the wrong target here. We narrowed coverage to the exact questions the firm is known for and published with enough depth to be the source answer.

What happened

The engagement isn't measured in traffic multiples. It's measured in presence. The firm's named frameworks started appearing in AI responses on the specific enterprise questions they advise on. Inbound calls started opening with "your framework on carrier consolidation came up in my research," not "I found you on Google." That's the signal.

Organic SEO did improve, but it's a secondary outcome here. The primary win is a compounding library of cited, AI-readable thesis content that shows up when sophisticated buyers do their pre-RFP research, whether that happens in a browser or a chat window.

The mechanics

• • Each topic was a thesis: named frameworks with a point of view, not generic overviews.
• • Tracked daily on both fronts: Google rank position and mentions in ChatGPT, Claude, and Gemini.
• • Built to be cited: every piece shipped with named frameworks, direct answers, and primary-source citations that AI assistants can lift cleanly.
• • Narrow and deep: fewer topics, more depth per topic. No keyword expansion into areas the firm doesn't actually advise on.
• • Strategist review on every piece. Enterprise buyers spot generic content instantly. Nothing auto-published.

"Our buyers aren't finding us through blog posts. They're finding us when their AI research surfaces our name as the source. Aumata understood that from day one. The strategist built the content program around getting cited in AI search, before I even had a vocabulary for it. The pipeline reflects it."

Operator, Enterprise Telecom Advisory