When an agency asked for a deck, we sent them the codebase instead

A partner agency emailed last month asking for a slide deck. Something to walk their team through how our automation work translates to client outcomes. Standard ask. Most agencies have a polished 15-slide answer ready for this exact moment.

We did not have a deck. We sent a Loom of the Atlas dashboard, a link to this blog, and a paragraph: here is the work, here is how it ships, here is the activity feed for the last 30 days. The codebase is the deck.

The follow-up question

They wrote back the next day with the question that mattered. Were we an agency, a product company, or something in between?

The honest answer is that we are an AI-native operating system that sells outcomes. The agency framing is a legacy of how the industry used to be priced. The product framing is what the work has actually become. "Something in between" is what most of the market is still saying because they have not finished the transition.

What changed when we stopped writing decks

Every prospect now gets a working demo: a personalised instance, pre-loaded with their briefs, running live for a week. They see the dashboard. They see the activity feed. They see drafts arriving in their queue with their voice. The conversation skips "how do you work" entirely and lands on "what should the agents focus on for our team."

Close rates went up. Sales cycles got shorter. The decks we used to send took two weeks of rework per prospect. The trial takes 90 seconds to provision and runs itself.

The deeper shift

Pricing moved from billable hours to outcomes per month. Cost structure compressed because labour was no longer the constraint. Sales conversations got shorter because the artifact does the talking. The agency framing started to feel like an expensive habit instead of a category.

The lesson is not "send Looms instead of decks." It is that when the work is reproducible, the artifact replaces the explanation. If your work still needs a deck to be understood, you have a process problem. If it does not, the deck is the part you should stop writing.