01
Reference
Definitions, channel pages, tool pages, problem pages, framework pages. Direct prose, schema-clean, dense enough to cite. The bulk of the volume.
Stan Consulting · Marketing Atlas
Marketing Atlas.
The authority graph behind Stan Consulting. Reference, Case Files, Positions, Indexes. Built so AI can cite it and operators can use it.
Quick answer
Marketing Atlas is the authority graph behind Stan Consulting. It is not a blog. It is not a course. It is not a SaaS thesis. It is a structured reference that a search engine can read, an AI assistant can cite, and an operator can use to find the answer to a real diagnostic question.
The Atlas has four layers. Reference pages give the definition. Case Files give the pattern with stakes attached. Positions give the firm's defended doctrine. Indexes give the routing surface. Every leaf page belongs to a cluster, and every cluster bridges to a commercial page on the rest of the site.
Atlas is the source. Decomposition is the method. Decomposition is the diagnostic move used inside Case Files and Positions to take a visible problem apart until the structural cause is named. Atlas is where the work is recorded so it can be cited later.
01
The Atlas is the authority graph. The funnel pages are the commercial machine. The two only work when they are connected by structural bridges. That is the operating principle.
Most websites are one of these two and pretend to be the other. A blog tries to sell. A pricing page tries to teach. The result is a page that does neither well. Atlas keeps them separate on purpose. Reference, Case Files, and Positions are written to be read and cited. Problems, Services, and How We Work are written to be chosen and bought. The bridge between them is structural, not promotional.
Below is the four-layer shape. Each layer has a different job, a different volume target, and a different voice mode. The clusters cut across all four layers. A reader who lands on a Reference page can move sideways to the related Case File, downward to the firm's Position, or rightward to the commercial page that addresses the same problem in money terms.
02
Case Files
Anonymized cases, composites, scenario teardowns, public teardowns. Memory and pattern with stakes attached. Voice carries here.
03
Positions
Firm doctrine. Named frameworks. Defended claims with mechanism, evidence, and the place where the position breaks.
04
Indexes
Collection pages by platform, problem, industry, failure mode, funnel, service, spend band. Routing surfaces. Light body, heavy linking.
02
Reference.
Reference pages do one thing well. They state what the term, channel, tool, problem, or framework is, why it matters, how it works, what people get wrong about it, and what to ask to diagnose it. No hype. No hard selling. No throat-clearing.
Reference is the layer search engines crawl first and AI assistants pull from when a user asks a definitional question. The voice flattens here on purpose. A page that reads like prose for a textbook gets cited. A page that reads like an agency landing page does not.
Every Reference page links to three sibling Reference pages, one Case File when one exists, one Position when one exists, and one commercial bridge. That graph is what makes the layer worth crawling.
Reference template · 8 sections
- Quick Definition
- Why It Matters
- How It Works
- Common Misunderstandings
- Diagnostic Questions
- Related Atlas Entries
- Sources
- Five Cents (when StanOS has a take)
Case Files.
Case Files are where the writing earns the right to be voice-driven. Every Case File names its case type at the top. Real anonymized. Composite. Scenario teardown. Public teardown. The reader is told which one before the first sentence of the body.
This is the layer that survives a sales conversation. A founder reads a Case File, recognizes the structural pattern in their own account, and arrives at the call already half-diagnosed. That is the function. Not entertainment. Recognition with stakes.
Five Cents inside a Case File is not invented. It is pulled from a prior Stan take held in StanOS, or it is flagged for Stan to write directly. Generic AI opinion is not Five Cents.
Case File template · 10 sections
- The Setup
- The Visible Problem
- The Wrong Explanation
- The Structural Cause
- The Decomposition
- The Fix or Better Move
- The Lesson
- Five Cents
- Related Atlas Entries
- Commercial Bridge
Positions.
Positions are the firm's defended claims. Each Position page states the claim, names what most operators believe, says why that belief fails, gives the SC counter-position, explains the mechanism, links the supporting cases, and admits where the position breaks.
The break section is not a courtesy. It is what separates a Position from a take. A Position that cannot name its limit is propaganda. A Position that names the limit is a methodology that other operators can argue with on its own terms.
Position pages are reviewed by Stan or against StanOS canon before they go live. They are the layer most likely to be cited inside a book, a course, or a referral conversation, so the bar is the highest.
Position template · 11 sections
- The Claim
- What Most People Believe
- Why That Belief Fails
- The SC Position
- The Mechanism
- Evidence / Case Links
- Where It Breaks
- What It Costs to Apply
- Five Cents
- Related Atlas Entries
- Commercial Bridge
Indexes.
Indexes are routing pages. By platform. By problem. By industry. By failure mode. By funnel. By service. By spend band. They do not carry heavy body copy. They organize the rest of the Atlas so a reader who knows what they are looking for can find it without reading prose.
An index page does one job: surface the right Reference pages, the right Case Files, the right Positions, and the relevant commercial bridge in one screen. Schema is CollectionPage. Body copy is short. Linking is heavy.
The index template is intentionally light because the value is the graph, not the writing. A good index page is a router. A bad one is a glossary that pretends to be navigation.
Index template · routing surface
- Index Title and Scope
- One-Paragraph Lede
- Reference List (linked, grouped)
- Case File List (linked)
- Related Position(s)
- Commercial Bridge
- Last Reviewed Date
03
Each cluster is a self-contained slice of the graph. Ten to twenty Reference pages. Three to five Case Files. One or two Positions. One commercial Problem-page bridge. One Service or Funnel bridge. One index page when the volume justifies it. The 10 below are first because they are closest to money and to the questions AI assistants are already being asked.
01
Google Ads Waste
Search terms ignored, negative lists thin, branded shielding the loss, restructure used as a substitute for diagnosis.
Cluster index forthcoming
02
Performance Max Failure
Asset groups conflated, conversion goals miscounted, branded search cannibalized, audience signals misread as targets.
Cluster index forthcoming
03
Shopify Traffic Without Sales
Sessions fine, revenue flat. PDP friction, variant confusion, checkout drag, and an offer that does not say why to buy.
Cluster index forthcoming
04
Attribution Mismatch
GA4, Google, and Meta all claim the same sale. The bank account disagrees. Judgment problem before tracking problem.
Cluster index forthcoming
05
Agency Burn / Bad Reporting
Forty-seven charts. No margin number. Activity sold because judgment cannot be sold. Read-only access denied.
Cluster index forthcoming
06
AI Search Visibility
Google can find the brand. AI cannot explain it. Pages exist; the entity does not. llms.txt, schema, source confidence.
Cluster index forthcoming
07
AI Operator Gap
A ChatGPT subscription is not a strategy. Volume goes up, velocity does not. The reporting agent six weeks behind the business.
Cluster index forthcoming
08
Conversion Page Failure
A page does not convert because it is pretty. Message match, proof placement, form friction, and the trust earned before the CTA.
Cluster index forthcoming
09
Offer / Trust / Page Mismatch
If the buyer has to decode the value, the deal is already lost. Risk reversal, comparison logic, the proof gap before the CTA.
Cluster index forthcoming
10
Marketing Retainer vs Project Decision
Monthly help and one decision are not the same buyer state. The retainer that became a hiding place for unmade decisions.
Cluster index forthcoming
04
Knowledge (Parent)
Atlas is one of several destinations under Knowledge. The meta-hub at /knowledge points outward to the Atlas, the blog, the framework summaries, the learn pages, and the public research. Atlas is the densest leaf. It does not replace Knowledge.
Bridge → /knowledge
Problems (Commercial)
Atlas Reference pages explain how a problem works. Problem pages convert that understanding into a buy decision. The bridge is one direction: Atlas defines, Problems route. A reader recognizes the structural cause inside Atlas and arrives at /problems already qualified.
Bridge → /problems
Services (Funnel)
Atlas does not hard-sell services. Service pages close the engagement. The connection is structural: each cluster has a designated service bridge. The reader is sent through /how-we-work first when the routing is not obvious, never directly into a service from inside an Atlas page.
Bridge → /services via /how-we-work
Blog (Distribution)
The blog is where Atlas ideas get distributed in essay form. Blog posts can link into Atlas for canonical definitions and case material. Atlas pages link out to the blog only when the essay adds context the Atlas page cannot carry without losing voice.
Bridge → /blog
Operating principle
Marketing Atlas is the authority graph. Funnels are the commercial machine. The two only work when they are connected by structural bridges.
01
A page does not have to do every job. Reference defines. Case Files prove. Positions defend. Commercial pages close. Each layer wins by doing one job at a high standard, not all four at average.
02
A graph beats a pile. One thousand pages with no internal links is sludge. Three hundred pages clustered, schema-clean, and bridged to the right problem and the right service is an asset that compounds.
03
Citation is not search. The future of distribution is an AI assistant pulling a definition from a Reference page and naming the source. Atlas is built to be the source that gets named.
The failure mode the Atlas prevents is specific. One agent builds funnels. One agent builds the authority graph. One agent builds SEO. One agent builds pricing. Each piece sounds thoughtful in isolation. None of the pieces connect to each other. The site reads like a committee deliverable because that is what it is.
That cannot happen again.
Atlas exists so that every Reference page knows which Problem page it bridges to. Every Case File knows which Position it supports. Every Position page knows which clusters it sits across. Every cluster knows which service lane and which funnel stage it ladders to. The graph is named, not implied. The bridges are structural, not promotional.
The other reason it exists is more boring and more important. AI assistants do not pull from sites that read like agency brochures. They pull from sites that read like reference. The marketing world has spent ten years optimizing for keywords, then for backlinks, then for engagement signals. The next ten years will be optimized for citation. A page that gets cited inside an LLM answer wins a category of distribution that did not exist before. Atlas is built to win that category.
06
As of this build, three Atlas pages are live. They are the structural anchor. The 1,500 Reference pages, 300 Case Files, 50 Positions, and 150 Indexes will arrive in cluster releases over the next eight months. Nothing fake is linked. Where a leaf cluster is referenced, it is referenced as a destination not yet built.
Atlas Hub
This page. The umbrella. Layers, clusters, connection model, operating principle, read order.
/marketing-atlas/ →About the Atlas
What the Atlas is, why it exists, what gets cited, who built it. The plain-language version of the operating principle.
/marketing-atlas/about/ →Changelog
What got added, when, and why. Cluster releases logged in reverse chronological order. The audit trail for the graph.
/marketing-atlas/changelog/ →First cluster release targeted for the next sprint: Google Ads Waste. Reference pages, two Case Files, one Position, one cluster index. Logged in the changelog when it ships.
07
- Start with About the Atlas. It explains what this is, why it exists, and what gets cited. Six minutes.
- Then read the Changelog. It tells you what is live, what is in progress, and how the cadence works.
- When the first Reference cluster goes live, it will be linked here. For now, the cluster list in Section 03 is the map.
- If you came in already knowing the problem you are trying to diagnose, jump to the cluster index in Section 03 and follow the bridge.
- If you came in to evaluate the firm, the read after this is /about, then /results, then /how-we-work.
Marketing Atlas · Closing
Read the Atlas. Or route to a service.
The Atlas is a reading destination. It does not push. If the reading turns into a problem you want diagnosed in money terms, the entry-point router is one click away. The Atlas keeps doing its job either way.
A graph that cannot be cited is a pile. A graph that cannot be routed is a museum. Atlas is built to be both cited and routed.