the general case
Every function runs on the same mess: work happening in many places, knowledge in systems that don't speak, the real story in someone's head. Ask three people where a thing stands — where it lives, where it goes next, who acts on it — and you get three answers and a meeting.
The studio's flagship loop is the living map of what you sell, built in product marketing — because that's where Bob worked, and that's where the mess was loudest. But the engineering underneath never knew it was marketing. A core that holds the truth. Loops around it that do the work and register back. Point that shape at any function that runs on a mess and it behaves exactly the same.
bob@30loops.com the flagship: one living map of what you sell →
one shape
This is the construct from the front page, drawn once more — the labels are the only edit. The middle is still a map; which map depends on where the shape is pointed. Here it's the offering, whole. In sales operations it's the account, held in one view. In reporting it's the question and the answer that settled it. The middle changes; the shape doesn't: one core everyone goes to, loops around it that do the work and register back, one larger loop holding it all.
fig. 01 — the construct from the front page; the labels are the only edit. The filled loop is the front page.
already running
None of this is speculative. Every function below ran on its own mess; each got the same shape — a core, loops around it, and the keys handed to the team that owns it. The badges open the full specs.
product marketing — the flagship
The mess: the website says one thing, the deck another, the manual a third — nothing holds the whole. The loop: one living map of what you sell — every definition, every team, every phase — wired into every page, deck, demo, and room that speaks for you. This is the one on offer, and the deepest built.
sales operations
The mess: the account's truth split across the CRM, the project tracker, and the rep's memory. The loop: one presentation-ready view per account, merged from the systems that disagree — and every RFP question answered once, verified answers compounding into memory.
marketing operations
The mess: customer calls full of buyer language nobody mines; collateral rebuilt by hand for every meeting. The loop: every call distilled into campaigns, sequences, and social — in the buyer's own words — and decks, guides, and one-pagers assembled from one design system in minutes.
reporting
The mess: every question is a ticket for the one person who can pull the data. The loop: plain-English questions become saved, shareable reports — run daily by a non-technical operator, no query language anywhere.
knowledge
The mess: the facts are in there — contracts, manuals, old decks — but nobody reopens a sixty-page document to check one line. The loop: the facts locked in your documents, retrievable with citations and confidence.
people operations
The mess: who's here, what they cost, which journey they're on — spread over a spreadsheet, a signing tool, and someone's memory. The loop: an operating team with no engineer running its own platform — spend logged in plain English, journeys that can't drift, no API key anywhere. The furthest thing on this page from product marketing, and the shape didn't flinch. Not on offer — shown because it settles the question.
the door
The engagement is the same wherever the shape points: a discovery, a scored readout the same day, a first loop built embedded in weeks, and the keys handed over. The offering today is the flagship — the map of what you sell. If your loudest mess sits somewhere else in the operation, say where. The shape has been pointed at stranger things.
Not sure where it's loudest? Run the discovery — sixteen questions, asked out loud, scored in minutes.