Stan Consulting · Marketing Atlas · About
Why the graph exists. What it is. How it gets used. Who built it. The plain-language version, written in my voice rather than the firm's commercial register.
Marketing Atlas is the authority graph behind Stan Consulting. That sentence is the whole pitch.
Authority means the page can be cited. Graph means each page knows which other pages it sits next to and which commercial page it bridges to. The result is a piece of public infrastructure: schema-clean, internally linked, dense enough to read without filler and clean enough for a search engine or an AI assistant to lift the answer cleanly.
Inside the Atlas there are four layers. Reference pages give the definition. Case Files give the pattern with stakes attached. Positions give the firm's defended claims. Indexes are the routing surfaces that tie a cluster together. Eight months from this build, the Atlas will hold roughly 1,500 Reference pages, 300 Case Files, 50 Positions, and 150 Indexes. That number is a target, not a vanity count.
The output of the Atlas is four things. A citation when an AI assistant answers a marketing question. A search ranking when an operator types a long-tail query. A trust artifact when a buyer is doing due diligence on the firm. A reading destination when a referral arrives looking for substance, not slogans. Those four uses are the reason every page is built.
The honest answer is that the failure mode is specific. One agent builds the funnel pages. One agent builds the authority graph. One agent builds the SEO surface. One agent builds pricing. Each piece sounds thoughtful in isolation. None of the pieces connect. The site reads like a committee deliverable because that is what it is.
That cannot happen again.
Atlas is the answer to that failure mode. Every Reference page knows which Problem page it bridges to. Every Case File knows which Position it supports. Every Position knows which clusters it sits across. Every cluster has a designated funnel lane and a designated commercial bridge. The graph is named, not implied. The connection is structural, not promotional.
The other reason is more boring and more important. Distribution is changing. Ten years ago the prize was a top-three Google ranking. Today the prize is a citation inside an AI answer. A Reference page that an LLM trusts becomes the source for a category of question that gets asked thousands of times a month, and a buyer who arrives downstream of that citation already trusts the firm. Atlas is built to win that prize.
Each layer does one job. Mixing the jobs is what produces sludge. Holding them apart is what produces a graph that compounds.
If you ask the Atlas what something is, the answer comes from a Reference page. Definition first. How it works. What people get wrong about it. Diagnostic questions that turn the term into a check the reader can run. Reference is the layer the search engines and the AI assistants pull from. The voice is direct on purpose. A page that reads like a textbook gets cited.
If you ask the Atlas whether a problem is a real pattern or a one-off, the answer comes from a Case File. Each one labels itself: real anonymized, composite, scenario teardown, public teardown. Reading a Case File is how a founder shows up at the call already half-diagnosed because the structural pattern is already named in the head. Voice carries here.
If you ask the Atlas what the firm believes and why, the answer comes from a Position. Position pages name the claim, name what most operators believe, say why that belief fails, give the SC counter, and then admit where the position breaks. The break section is the test. A position that cannot name its limit is propaganda. A position that names the limit is methodology.
If you already know what you are looking for, the index pages route you there. By platform, by problem, by industry, by failure mode, by funnel, by service, by spend band. Light copy, heavy linking. An index does not try to teach. It surfaces the right Reference pages, the right Case Files, the right Position, and the relevant commercial bridge in a single screen.
The Atlas is written in my voice. The rest of the Stan Consulting site uses a McKinsey-Economist register because that is what the funded operator buying a $25,000 engagement expects to read. The Atlas does not use that register. It is more direct. It is more first-person where the page is mine. It allows short sentences as a rhythm device.
If a page in the Atlas reads too clean to be real, the page is wrong. If it sounds like a brochure, it is wrong. If it uses the words you would never say out loud at 9 pm to a real founder, it is wrong. Reference pages flatten further toward textbook prose because they are built to be cited, and a cited page should sound like a definition. Case Files and Positions allow more voice. The Atlas hub and these meta pages sit between, declarative and clear without theater.
There is a banned-word list. There is a banned-sentence-shape list. Both apply across the entire site. Atlas is no exception. The list is enforced before the page is shipped.
Atlas is the source. Decomposition is the method.
— Atlas Operating Principle
AI assistants do not cite a page because the page is decorative. They cite because the page is dense, schema-clean, definitionally precise, and structurally legible. The model needs to recognize the entity, find the answer, and trust the source. Atlas is engineered to clear all three checks.
Density means the body says what it says without filler. A 600-word Reference page that answers a question fully outperforms a 3,000-word page that buries the answer behind throat-clearing. Schema-clean means each page declares the right structured-data type: DefinedTerm for a concept, Article for a Case File, BreadcrumbList everywhere. Definitionally precise means the first paragraph contains the answer the model is looking for, not an introduction to the answer.
Structural legibility is the part most sites fail. The model wants to see that the page belongs to a graph. It wants the breadcrumb. It wants three sibling Reference pages linked. It wants a related Position. It wants a commercial bridge that does not pretend to be an answer. Atlas pages are built to satisfy that pattern by design, not by guess.
The result is that a search query like "what is performance max cannibalization" or "how does GA4 attribution differ from platform-reported conversions" can land inside an AI answer with the Atlas page named as the source. That is the prize. That is what the volume is for.
If you are reading this page, you arrived from one of four places. The Atlas is structured so each entry point lands on the right next surface without rerouting through home.
If you came from a search engine
The Reference page has the definition. Read that one. The graph below it links sideways to siblings and downward to a Position when one is published. The commercial bridge sits at the bottom of the page and does not interrupt the read.
If you came from a sales conversation
A Case File is what was probably referenced. Read the labeled case-type tag at the top, then the Setup, then the Structural Cause, then the Five Cents. The Lesson section is short on purpose. The Bridge tells you the next step in commercial terms.
If you want firm doctrine
Read a Position page. Each one names the claim, the counter-belief, the mechanism, and the place where the position breaks. The break section is the most useful part. If you disagree with the Position, you now know exactly where to push back.
If you want commercial action
Route to /how-we-work. The Atlas does not push and does not gate. The router asks two or three structural questions and lands you on the correct service page. The Atlas keeps doing its job either way.
I am the primary author and the doctrine review. I wrote the operating principle, I locked the layer templates, and I review every Position before it goes live. The voice rules are mine. The cluster sequence is mine. The commercial-bridge rules are mine. When a Case File names a structural cause, that cause has to be one I would name in a sales conversation. If it is not, the Case File gets rewritten or it does not ship.
Where AI tools assist on Reference page production, the assist is mechanical. Definitions get drafted faster, schema gets generated faster, source citations get checked faster. The voice review and the canon review are not delegated. A Reference page does not ship without my eyes on it. A Position does not ship without my hand on it. Five Cents inside a Case File is either a take I have already given on record or it is flagged for me to write directly. Generic AI opinion does not become Five Cents. Ever.
The team does the implementation. Stan Consulting is a small team, not one person at a keyboard. Build, schema, sitemap inclusion, machine-file updates, internal-link audits, and quality-grade tagging all run through the team. The doctrine sits with me; the production runs through the team. That is the only structure where the Atlas can hit volume without losing voice.
The full firm bio sits at /about. The team page lives there. The network of advisory and adjacent firms is also linked there. This page is about the graph; that page is about the people who run the graph.
Marketing Atlas · About
Authority graph. Four layers. Ten launch clusters. Built so an AI assistant can cite it cleanly and an operator can use it without being sold to. The hub is one click away. The changelog records what got built and when. Pick the door.
A graph that cannot be cited is a pile. A graph that cannot be read is a museum. The point of the about page is to keep the graph honest.