# Honorable offboarding
Source: https://docs.snapmarket.co/epilogue
Ending as the final chapter of a story we told together, not as an awkward silence.
Every partnership ends. Most agency relationships end as a gradual cooling followed by an email.
We treat the ending as a chapter with its own work and its own artifact. It is the last thing we do and it is the part of the manuscript most likely to determine what you say about us afterward.
## What happens
A proper look back across everything we built. Every artifact, what each chapter produced, what worked and what did not, and where the honest gaps are. Written the way the audits were written, which is to say without flattering anybody.
The claim we opened with is rendered confirmed, disconfirmed, or amended, with the full stack of revisions behind it.
Everything transferred into your control. Source files, documents, the site, the show, the accounts. Written documentation of what exists and where it lives, so nothing is stranded behind a login only we had.
A conversation about who else this might suit, and a genuine invitation to stay in touch.
## The verdict
This is the part that makes the ending mean something.
Because the [thesis](/method/thesis) was written as a claim that could be wrong, and because every audit measured against it, there is an actual answer at the end rather than a set of impressions. The bet either held, or it did not, or it turned out to be partly right in a way worth naming precisely.
A disconfirmed thesis is not a failed partnership. It is frequently the most valuable thing you leave with, because you now know something specific about your own market that you did not know before, and you know it with evidence rather than as a feeling.
The stack of revisions behind the verdict is the intellectual history of the work—what we believed at the start, where we were wrong, what we learned that changed the argument. That stack is what makes a handover feel like a finished book rather than a folder of files.
## What is already yours, and what has to move
The handoff splits cleanly in two, because of a line we draw at the beginning.
Anything that represents you in the world was always registered to you. Your domain, your analytics, your Search Console, your YouTube channel, your social handles, and any platform you already held when we met. For all of that there is nothing to transfer. You remove our access and the history, the settings, and the audience stay exactly where they were.
The production tooling is different. The platforms we record, edit, publish, and schedule in run on our subscriptions, which is what lets a partnership start on day one instead of after a procurement conversation. Those end when the partnership does. If you want to keep working in them, you set up your own accounts and we port everything across—content, settings, and configuration, as completely as each platform allows. We tell you which ones you actually need, with current pricing, before your last month rather than after it. Some transfers are clean and some are partial, and we say which is which rather than letting you discover it alone.
We draw the line there on purpose. An agency that holds your audience, your domain, or your data has leverage it should not have, and a client who stays because leaving would be painful is not a client who is choosing you. Holding the tooling is a convenience we carry. Holding your identity would be something else.
Every platform, which side of that line it sits on, and what porting involves.
## A pause is not an ending
Sometimes a partner steps back for a season rather than leaving. Budget cycles, a leadership change, a year where the company needs to focus elsewhere.
That is a pause, and we treat it differently. Context stays intact, the files stay organized, the thesis stays on record, and coming back does not mean starting over. We would rather hold a relationship open than force a clean break for the sake of tidiness.
## What ends the Epilogue
A completed final review and a documented handoff. At that point the manuscript is finished, and now it’s your story to tell.
How a partnership starts, and the argument it starts with.
# Welcome to Snapmarket.
Source: https://docs.snapmarket.co/index
What we make together, how it is sequenced, and what you can expect at every stage.
Most companies buy marketing in pieces—a website this year, a rebrand the next, a burst of content in between—and end up with a pile of work that never adds up to anything.
We build one body of work with you instead, where each piece inherits from the last, so that in year three your marketing is an asset rather than a run of expenses.
We call that body of work a manuscript. It has chapters, it is written in order, and you can always tell where you are in it.
The manuscript has three chapters and one layer running underneath.
1. Story is the message and visual identity.
2. System is the technical infrastructure.
3. Send is the disciplined act of putting work into the world on a schedule, usually in the form of a [podcast](https://docs.snapmarket.co/send/podcast/v2m).
4. Scale is the measurement, and it starts on the first day your website is live.
This site exists so you never have to wonder what happens next. It covers what each chapter contains, what we will ask of you, what you will hold at the end of it, and how to reach the accounts and platforms your work lives in. It is part philosophy and part instruction manual, which is roughly the ratio of the work itself.
You are not meant to read it front to back. Most people arrive on a single page because someone sent them there, and that is exactly the intended use.
Story, System, Send, and the Scale layer underneath. The shape of the whole partnership on one page.
The founder’s conviction, surfaced and shaped into effective marketing.
One page arguing why the partnership should exist, written as a claim that can be wrong. Everything else serves it.
Longer essays on marketing, patience, and craft. The thinking behind the Snapmarket method.
## How to read this site
Each chapter has an overview page that explains what the chapter is for and when it typically happens, then a page for each section inside it, then a page for each piece of work that section can produce. Read the overview if you want the shape. Read the sub-pages about individual units of work called “pieces” when a specific piece is on your calendar and you want to know what your week looks like.
Every piece page answers the same four questions in the same order.
1. What this is.
2. What we need from you.
3. What you will have when it is done.
4. How long it usually takes.
If you are looking for something specific, the search at the top of the page will find it faster than the navigation will.
## Who to ask
If you ever have any questions, please email [support@snapmarket.co](mailto:support@snapmarket.co), which puts it in front of the whole team so they can get to work efficiently.
## Working together
If you are reading this as a prospective partner and want to talk about what this would look like for your company, we would be glad to hear from you.
This site describes how we work in general. Your partnership has its own scope, cadence, and priorities, all of which are set in your proposal and revisited in the monthly audit. Where the two differ, your agreement governs.
# How to read a coordinate
Source: https://docs.snapmarket.co/method/coordinates
Every piece of work carries an address. Here is how to read it.
Every piece of work we produce carries a small address, which you will see on project tickets, deliverable footers, and in your monthly audit. It looks like this.
```text theme={null}
AAA · § 1.1.1 · A1
```
Read left to right, it says who the work is for, where it sits in the manuscript, and which stage of your buyer’s journey it serves.
The first part is a short code for your company. The middle part is the location—chapter, then section, then the specific piece. So § 1.1.1 is Chapter 1, section 1, first piece: the messaging document. The last part is the funnel stage.
This helps us keep track of what we’re producing and how it serves the overall story, business, and performance data, particularly when it comes to the monthly audit. Creating a systematic way to track and report on our work also allows AI agents to better analyze the data and provide strategic insights.
## The four stages
| Code | Stage | What the work is doing |
| ---- | --------- | ------------------------------------------------------------------------------- |
| A1 | Awareness | The buyer does not know you exist, and the work serves discovery |
| A2 | Affinity | The buyer knows you but is not ready, and the work builds trust over time |
| A3 | Action | The buyer is in market, and the work converts intent into commitment |
| A4 | Advocacy | The buyer has bought and is happy, and the work generates referrals and stories |
The stage is a separate axis from the location. A piece always has both, which is what lets us answer a question most marketing reporting cannot: not just what did we make, but which part of the buying journey did we actually serve.
It is also how imbalance becomes visible. A quarter that produced eleven A1 pieces and nothing at A3 is a quarter that filled the top of the funnel and left the bottom alone. That is sometimes the right call. It should never be an accident.
## Why you will keep seeing it
The coordinate is the reason we can find any piece of work in about ninety seconds, and the reason your audit can compare this quarter to last quarter honestly. You do not need to memorize it. But when you see § 3.2.1 on a ticket and want to know what it is, this site is organized on exactly the same numbering, so the address will always find the page.
## The status words
The audit uses four words and only these four, so that “steady” always means the same thing in March as it did in January.
| Word | What it means |
| --------------- | ---------------------------------------------------------------------------------- |
| Strong | Performing at or above benchmark. Protect it and do more of it. |
| Steady | Working, but not optimized. Refine when there is capacity. |
| Weak | Underperforming or causing concern. Intervention required. |
| Not yet running | Has not started. Either still in the baseline period or awaiting a scope decision. |
# How to work with us
Source: https://docs.snapmarket.co/method/how-to-work-with-us
Two ways to work with us: a bounded project, or a partnership we build over years.
There are two ways to work with us, and they’re genuinely different things rather than two sizes of the same thing.
A **project** is one bounded piece of work with a defined end. A website. An updated visual identity. A messaging workshop. You pay, we do the work, we ship it, and we move on. This is what most agencies do, and when it’s what you need, it’s the honest answer.
A **partnership** is a manuscript. We become your marketing department, or a substantial supplement to one, and we write a body of work with you over years. Everything else on this site—the chapters, the artifacts, the thesis, the Scale layer—describes a partnership. None of it applies to a project.
## Projects
**A project is right for you if you find yourself saying:** “Our site is five years old and I’m embarrassed to send the link.” “I know what we do, I just can’t get it onto a page.” “The brand doesn’t match the company we’ve become.”
A project is scoped, priced, and finished. It has a start, a defined deliverable, and an end you can see from the beginning.
You get the work, the source files, and a shared folder they live in. You get an address to reach us at while the project runs. What you don’t get is the apparatus built for the long term: no thesis, no monthly review, no measurement layer, no standing weekly call. Those exist to make years of work legible, and a six-week website build doesn’t need them.
That isn’t a lesser service. It’s a different one, and pretending otherwise would mean charging you for machinery you have no use for.
## Several projects in a row
There’s a middle path, and it’s often the best value we offer.
Projects strung together—a message, then a visual identity, then a website—amount to a short partnership. There’s no contract either way. You’re never signing up for a term, and if you stop, the payments stop.
Run that way, the work is usually faster and cheaper than the same three projects commissioned separately, because nothing has to be re-briefed between engagements. It also lets us pivot: three months in, if the message turns out to be different from what everyone assumed, we change course rather than delivering a website built on an answer we no longer believe. A sequence of separate projects locks scope at each invoice, so anything new becomes a change order. Run as a short partnership, each month simply buys the next thirty days.
## Partnerships
**A partnership is right for you if you find yourself saying:** “I need someone to own marketing and I can’t justify a CMO.” “We’re good at the work and invisible in the market.” “Every piece of marketing we make sounds like it came from a different company.”
A partnership is a team, not a person. A strategist, a content writer, a designer, a developer, a podcast producer, and an analyst, all pointed at the same argument. Assembling that internally is a different order of expense, and most companies at this stage should not try.
We hold a standing weekly call with most partners, and in practice we’re in contact daily. We sit inside your business rather than beside it—we know what’s launching, who just joined, which deal went cold and why. That’s what lets the work be specific rather than generic, and it’s the reason a partnership produces something a project can’t.
It starts with a [thesis](/method/thesis), an argument for why the work should exist that can be proven wrong. It moves through three chapters, each closing with an [artifact](/method/vocabulary). It carries a [measurement layer](/scale/overview) from the first day. And it’s measured monthly against the claim we opened with.
A partnership is the right answer when marketing is an ongoing function of your business rather than a task on a list. If you need a thing, buy the thing. If you need the function, that’s this.
Most of our work is partnerships, and that shapes how we behave. We take projects, we do them properly, and plenty of partnerships started as one. But if a project keeps generating the next question—what do we do with this site now, who’s writing the content, how do we know it’s working—we’ll tell you the question is really about a function rather than another project.
## Moving from one to the other
Project clients ask what’s next more often than not, and there’s no ceremony to it. A partnership starts the way every partnership starts: a discovery conversation and a thesis. Work already done doesn’t get redone, and it usually shortens Chapter 1 considerably, since the message or the identity is already settled.
The small set of words we use, and what each one means.
Whether a project or a partnership makes more sense depends on where your company is. That’s a conversation.
# Story, System, Send, Scale
Source: https://docs.snapmarket.co/method/overview
Three chapters, two bookends, and a measurement layer that runs underneath all of it.
Story, System, and Send are three chapters written in sequence, and Scale is the layer running underneath all three from the day the partnership begins.
Run properly, this gets you three things most companies never assemble at once: a message your whole team repeats the same way, a system that can tell you whether the work is landing, and a publishing rhythm that keeps producing after you stop thinking about it. Six months is a realistic run from the first conversation to a podcast publishing on a schedule, though a complex website or slow approvals will stretch it.
The sequence is not arbitrary. A publishing engine pointed at an unclear message produces a great deal of visible work that says nothing in particular. A message with no engine behind it stays in a document. And both of them, unmeasured, become merely a matter of opinion. So we settle what is true first, then build the thing that operationalizes it, and then put it into the world, while measuring throughout.
## The chapters
The message. Your conviction surfaced and shaped into effective marketing. Artifact: the Storybook.
The technical infrastructure. Website, integrations, and analytics. Artifact: a live website.
The publishing. Podcast, content, email, and social, on schedule, over years. Artifact: a podcast.
The measurement layer. Performance data and a monthly audit that says plainly what worked and what didn’t.
## The bookends
The two pieces of a partnership that usually go unnamed have names here. The [Prologue](/method/prologue) is discovery, the [thesis](/method/thesis), the proposal, and kickoff—the work of starting well. The [Epilogue](/epilogue) is offboarding done as an honored departure rather than an awkward silence, with a final review, a verdict on the thesis, a clean handoff of every asset, and an open door.
Naming them matters because unnamed work tends to be unowned work. A kickoff nobody scheduled and a handoff nobody documented are the two most common ways a good partnership ends badly.
## Timing, roughly
Most of Chapter 1 lands in the first thirty to sixty days, with the message revisited quarterly or annually thereafter. Chapter 2 typically lands in months two through five, depending on the size of the build. Chapter 3 begins once Chapter 1 has produced enough raw material to publish from, usually around month three or four, and then compounds for as long as the partnership lasts.
These are typical shapes, not promises. Your sequence is set in your proposal and adjusted as reality intervenes, which it does.
## What ends a chapter
Each chapter has exactly one artifact, the single deliverable that says the chapter is finished. Story ends with a Storybook. System ends with a website that is live, indexed, and wired for performance. Send ends with a podcast that has published on a stable cadence.
We are strict about this because “done” is a finicky word in agency work. An artifact gives it a definition you can hold in your hand.
## Why Scale is not a chapter
Measurement is not a phase you graduate into. The infrastructure gets built once, inside System, but the measuring itself starts as soon as the website is live, so the baseline for judging the work is your actual starting position rather than a number reconstructed later from memory.
Every month you receive an audit. It is written as an editor’s letter rather than a dashboard export—what the last period produced, what it did not, and what the next period is betting on. It is deliberately honest about the things that are not working, because a report that is always green is a report nobody can use.
# Prologue: onboarding and discovery
Source: https://docs.snapmarket.co/method/prologue
What happens between starting and the first real chapter.
The Prologue is the work of starting well. It runs from the first serious conversation through to the kickoff session, and it ends when three things are true: the partnership has officially started, your tools and folders are provisioned, and we have had a recorded kickoff conversation that becomes the raw material for Chapter 1.
Most of what goes wrong in a long engagement is set in place during these few weeks, which is why we treat them as a real section with a real ending rather than as paperwork.
## It starts with an argument.
The first substantive thing you receive from us is not a proposal. It is a [thesis](/method/thesis)—one page arguing why this partnership should exist, written as a claim that can be wrong, delivered in person and offered up to be debated rather than approved.
We do it in that order deliberately. A proposal that arrives before an argument is a price list, and a price list invites you to compare line items with someone else’s line items rather than to decide whether the underlying bet is right. If the thesis is wrong, no amount of well-priced work fixes it. If it is right, the proposal is just the math of executing it.
It also does something for us. A business about which we cannot write a falsifiable claim is a business we cannot be measured inside, and that is worth discovering before either of us starts anything.
## What happens
A recorded working conversation with whoever carries revenue accountability. Where your customers actually come from, what your close rate is, what has gone cold and why. Alongside it we look hard at what you already have—your site, your messaging, your public presence, and whatever measurement exists.
Drafted from that conversation within a few days and delivered live as the second conversation. You get this whether or not you go on to work with us.
Written only once the thesis is agreed, and it prices the bet the thesis names. If the proposal contains work the thesis does not argue for, one of the two documents is wrong and we would rather find that now. Where we think a chapter should wait, the proposal says so and says why.
Once approved, we set up the shared places the work will live: your document folder, your project management setup, your analytics dashboard, and access to whichever publishing platforms your plan calls for.
A recorded working session with you and whoever else needs to be in the room. Part introduction, part the first real conversation of Chapter 1. This is where the messaging work actually starts, so it is worth protecting 90 minutes for it.
## What we ask of you
The revenue owner’s genuine attention, twice—once for discovery and once for the thesis conversation. Not delegated. Nobody but that person can answer a question about close rate or pipeline, and a thesis written without those answers is fiction.
Access to what already exists—the old messaging deck, the sales emails that work, the analytics account. We would rather see the unflattering version than a curated one, because the gap between the two is usually where we find the useful insight.
One named person who can make a decision. Not a committee. Approval by committee is the single most reliable way to turn a four-week piece into a four-month one.
## What ends the Prologue
An approved partnership and a completed kickoff. At that moment you have an agreed thesis, tools provisioned, folders shared, projects open, and a recording from which Chapter 1 will be built.
The founder’s conviction, surfaced and shaped into language a market can carry.
# The thesis
Source: https://docs.snapmarket.co/method/thesis
A one-page argument for why the partnership should exist, written as a claim that can be wrong.
A thesis is a one-page argument for why this partnership should exist, and it is written as a claim that can be wrong. That last property is the entire point. A claim that can be wrong has to name what would prove it wrong, and naming that is what turns a document into an anchor.
What it gets you is a marketing budget you can defend in a board meeting, and a conversation in month nine that is specific rather than vague.
Everything downstream inherits its argument from this page. The proposal prices work. The messaging document defines language. The go-to-market plan sequences activity. The monthly audit reports movement. None of them say why any of it should be happening at all. The thesis does, and it becomes the standard against which the rest gets measured.
## Why one page
The limit is a quality mechanism rather than a formatting preference. At that length there is no room to waffle on the buyer or hedge the math, so it either lands on a finding or it says nothing. No room for a long list of unknowns, so only the ones that actually block the claim survive. The constraint does the editorial work, and a thesis that needs two pages is a thesis that has not been decided yet.
## What is on the page
Six sections, in this order, because each depends on the one before it.
Where your revenue comes from today, with numbers. The machine as it currently runs, not the company history.
One kind of person, described by what they believe, and what they are shopping for regardless of who sells it to them.
Why that buyer does not currently arrive. This is the problem being purchased, stated as one mechanism rather than a list of weaknesses.
Where we reach them, in what form, at what cadence, expressed in § coordinates. This is what makes the scope conversation legible a year later.
Derived, not asserted. We start at the number you care about and work backwards to the number marketing has to produce.
Your revenue goal divided by what a customer is worth gives the customers you need. That number divided by your close rate gives the conversations. That number divided by the share of people who raise a hand gives the prospects you have to reach.
Every step divides, so every number grows as we move back up the funnel. The last one is where the marketing starts.
What must be true, who owns which part, and one sentence beginning “This thesis is wrong if.” We do not control your price, your product, your close rate, or who answers the phone when a lead comes in, and naming that before anyone is disappointed is what makes month nine a specific conversation—the reach happened, the conversations happened, the close rate did not—rather than a vague argument about whether marketing is working.
## The math, worked
Abstractly it is four nouns in a row. With your numbers in it, it is a plan.
Say you want \$1 million of new revenue this year. A customer is worth \$50,000. You close one first conversation in four, and two people in every hundred who encounter your work raise a hand.
| What we know | The division | What it gives |
| ---------------------------------- | ------------------ | ---------------- |
| $1M goal, customers worth $50,000 | 1,000,000 ÷ 50,000 | 20 customers |
| You close one conversation in four | 20 ÷ 25% | 80 conversations |
| Two in a hundred raise a hand | 80 ÷ 2% | 4,000 prospects |
Four thousand is the number that sizes everything else—how much gets published, on what cadence, for how long. It is not a target we invented. It fell out of your own revenue goal, your own customer value, and your own close rate.
This is also where partnerships get decided, and not because of anything we say. Watching your own goal divide down into a reach number you have never hit is a different experience than being handed a proposal. Sometimes it means the plan is right. Sometimes it means the goal is wrong, or the price is, or the close rate is.
## What it is not
It has no deliverable table, no calendar, no price, and no tactics list. The moment it has a deliverable table it is a proposal, and the moment it has a calendar it is a go-to-market plan. Both exist downstream and both are better at their jobs.
It is also not a diagnosis with a prescription attached. The thesis names what is broken. It does not explain how to fix it. That is a deliberate line, and it is what keeps the second conversation an argument about your business rather than a free consulting session.
## The three states
The thesis is a manuscript in miniature. It has a draft, a revision, and a final form.
| State | When | What changes |
| -------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Draft | Written from the discovery conversation, delivered in person | Underwritten by judgment, and it says so on the page |
| Revised | At the Storybook artifact | The buyer and gap sections get rewritten from the messaging interviews, because that is where we learn the first draft was wrong. |
| Standing | When Scale’s baseline period closes | The math finally carries your real numbers, and every audit measures against it. |
At the Epilogue the thesis is rendered as confirmed, disconfirmed, or amended, with the full stack of revisions behind it. That stack is the intellectual history of the partnership, and it is what makes a handoff feel like a finished book rather than a folder of files.
We expect the first draft to be wrong about the buyer. The revision at the Storybook artifact is the plan, not a concession. Being corrected out loud is the mechanism.
## The monthly thesis review
Once a month we put the thesis on the table and ask whether it’s still true.
The data is reviewed every month and we act on it every month. The strategy itself is not on a schedule. It can hold for years, and often should, because a plan revised every thirty days never runs long enough to tell you whether it worked. What changes a strategy is evidence, not the calendar.
This is the recurring session of a partnership and it is not a status meeting. The numbers arrive beforehand in your [performance report](/system/analytics/performance-reporting). The review is what we make of them, measured against the claim we opened with.
Every chapter of your manuscript gets one of four words, used consistently so that “steady” means the same thing in September as it did in March.
| Status | What it means |
| --------------- | ---------------------------------------------------------------------- |
| Strong | Performing at or above benchmark. Protect it and do more of it |
| Steady | Working, but not optimized. Refine when there is capacity |
| Weak | Underperforming or causing concern. Intervention required |
| Not yet running | Has not started. Either still in baseline or awaiting a scope decision |
Alongside the statuses: what last month produced and what it didn’t, what we propose for next month with each recommendation tagged to the piece of work that would deliver it, and the standing question—is the thesis holding.
A review that never names something that isn’t working has stopped being useful. We would rather write an uncomfortable sentence in month four than have an uncomfortable meeting in month eleven.
During the first sixty to ninety days the review covers instrumentation and observation only, and makes no claims about improvement. [The baseline period](/scale/baseline) explains why.
### What we need from you
Read it and push back. A review received without response has become a formality, and formalities are how partnerships drift.
Context we don’t have. A pricing change, a new salesperson, a large customer who signed through a personal relationship. Missing context is the most common cause of a misread month.
And a decision on the recommendations. Each is tagged to a piece of work, so agreeing means it gets scheduled, and declining means we won’t raise it again without new evidence.
## What we will ask you
Six facts, asked in the same order every time. They are worth knowing before the conversation, because most companies discover they cannot answer all of them, and that discovery is frequently the finding the thesis is built on.
* The source of each of your last ideal customers
* Your close rate from first conversation to signed
* Average customer value and average tenure
* Sales cycle length
* What historical marketing has been completed and what it produced
* Whether your website can identify who arrived and where they came from
Many companies struggle to confidently answer all six. That is not a problem with you, it is the finding. If there is no CRM, no lead scoring, and no way to tell which conversations came from where, then no amount of content will produce an answer you can trust, and the first bet has to be instrumentation. We would rather have that conversation in month one than in month twelve, when there is a year of work to account for and no way to account for it.
So if most of that comes back empty, we do not write you a thesis with invented numbers. We write one whose bet is the plumbing itself.
## How it gets written
We have a discovery conversation and record it. We draft from that conversation over the following few days. Then we deliver the draft live and open with some version of “Here is what I think is true about your business, and here is what I would bet on. Tell me where I am wrong.”
How the thesis fits into everything else that happens before Chapter 1.
Writing one is where every partnership begins. If the argument above sounds like the thing your marketing is missing, let’s talk.
# The tools we use
Source: https://docs.snapmarket.co/method/tools
The platforms your work lives in, which ones you will ever log into, and what stays yours.
A partnership runs on a small number of platforms, and we would rather use a few of them rigorously than add a new one every time a need appears. Most partners only ever log into three or four. The rest run quietly underneath.
One line answers most of the questions people have about this. Anything that represents you in the world stays yours. Anything that is production machinery is usually ours.
Your domain, analytics, Search Console, YouTube channel and social handles are your identity. They usually exist before we arrive and we are simply added as users. The tools we record, edit, publish and schedule in are different: most partners do not hold licenses for those, so we carry them and you use them at no additional cost for as long as we are working together.
## At a glance
| Tool | What it does for you | Will you log in? |
| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | ----------------- |
| [Google Drive](https://drive.google.com) | Every file we make for you, in one place you can search | Yes, often |
| [Ordinal](https://www.tryordinal.com) | Approve or reject every social post before it goes anywhere | Yes, weekly |
| [MarkUp](https://www.markup.io) | Click on the thing you’re talking about instead of writing “third paragraph, about page” | Yes, to review |
| [Descript](https://www.descript.com) | Record from your desk in forty minutes; everything after that is ours | Yes, to record |
| [AgencyAnalytics](https://agencyanalytics.com) | Where your numbers live, though reading them is our job rather than yours | Whenever you like |
| [Figma](https://www.figma.com) | See the design itself and comment on it directly | Occasionally |
| [Framer](https://www.framer.com) or [Webflow](https://webflow.com) | Your website, editable by your team without a developer | Rarely |
| [Transistor](https://transistor.fm) | Puts your show on Apple, Spotify, and everywhere else people listen | Rarely |
| [Loops](https://loops.so) or [Mailchimp](https://mailchimp.com) | Newsletters and sequences, sent on your behalf | Rarely |
| Google Analytics, Search Console, YouTube | Measurement and your channel | Yours already |
Everything else we run—project tracking, our CRM, the automation plumbing—sits behind the curtain and never asks anything of you.
Lost a login, need to add a colleague, or cannot find something? Email [support@snapmarket.co](mailto:support@snapmarket.co). Access requests are usually sorted the same day.
## Who pays for what
We do, for the production tooling, for as long as you are a partner. Those subscriptions sit on Snapmarket’s accounts and are covered by your fee rather than billed on top of it.
That is worth explaining, because it is not how every agency does it. Carrying the stack ourselves means we keep it consistent across partners, replace something without asking you to approve a purchase order, and start work on day one rather than after a procurement conversation.
Your own properties are yours throughout and always were. We are added as administrators so we can instrument, measure and publish, and that is the whole of our claim on them.
## If the partnership ends
The handover splits along the same line.
For anything already yours, there is nothing to move. You remove our access and that part is finished. The history stays, the audience stays, the settings stay.
For the tooling we carried, our subscriptions end when the partnership does. If you want to keep working in those platforms you set up your own accounts, and we tell you which ones you actually need—with links, current pricing, and an honest note about which you can probably drop—well before your last month rather than after it. Then we port everything across as completely as each platform allows. Some transfers are clean and some are partial, and we say which is which up front.
How offboarding runs, and what the final handover includes.
# Our vocabulary
Source: https://docs.snapmarket.co/method/vocabulary
An editorial vocabulary instead of the usual agency one, and what it changes about the work.
We do not run accounts. We write manuscripts. That’s because a manuscript has an arc. At any point in a book you know roughly where you are—early, middle, or near the end—and what kind of thing should be happening. Marketing work usually has no such property. It arrives as a stream of tasks with no understood shape, which is why so many companies cannot say whether their marketing is going well, only whether it is going. The chapters give the work a shape in which you can locate yourself: E.g., “We are in Chapter 2. This is what comes next.”
A manuscript also has a notion of being finished. Each chapter closes with a single **artifact**, and until that artifact exists the chapter is open. Without something like this, engagements drift for years without anyone able to name what has been completed. We would rather be held to a small number of unambiguous finishes than a long list of ambiguous activities.
The word also sets the relationship. A manuscript has an author and an editor, and in this arrangement you are the author. The conviction is yours, the business is yours, and the story is yours to stand behind for years after we are gone. Our role is editorial—to surface what is already true, shape it into language a market can carry, build the machinery that carries it, and tell you honestly when a chapter is not working. That is a different posture than a vendor executing a brief, and the difference shows up in how much we push back.
## The words we use
We keep the vocabulary small and hold it steady, because language matters.
| Word | What it means |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Thesis | The one-page argument for why the partnership should exist, written as a claim that can be wrong |
| Project | One bounded piece of work with a defined end—a website, a visual identity, a messaging workshop. Not part of a manuscript. |
| Partner | A client we write a manuscript with over years, with a standing weekly rhythm and daily contact. |
| Manuscript | The partnership itself—the whole body of work, built over years |
| Chapter | One of the three phases: Story, System, Send |
| Section | An area of work inside a chapter, numbered 1.1, 1.2, and so on |
| Piece | A single unit of delivered work |
| Artifact | The deliverable that signals a chapter is complete |
| Scale | The measurement layer running beneath all three chapters |
| Audit | The monthly thesis review, written as an editor’s letter |
| Prologue and Epilogue | The bookends: starting well, and ending well |
You will see this vocabulary on every surface—in our internal project management system, on your deliverables, in your monthly audit. Nobody is going to quiz you on it. It simply means that when someone says “the Storybook is close” or “we are still in 1.1,” everyone in the room is talking about the same thing.
## A note on slowness
The method is patient on purpose. Content published in month one does not produce pipeline in month two, and we would rather say that out loud at the start than manage around it later. What we can promise in the early months is that the work is compounding and that you can see it compounding, which is what the audit is for.
If you want the longer version of this argument, it lives in [Field notes](https://notes.snapmarket.co/introducing-scale/).
# The baseline period
Source: https://docs.snapmarket.co/scale/baseline
Sixty to ninety days in which we deliberately make no quantitative claims.
For the first sixty to ninety days of the Send chapter, we will not tell you that anything improved.
This is a commitment rather than a limitation, and it is worth understanding early because it shapes what the first few months of reporting look like.
## Why
Without a baseline, “we lifted click rate by thirty percent” means nothing. It could be regression to the mean. It could be seasonality. It could be an artifact of cleaning a list, or of a tracking change, or of one unusually good week that would have happened anyway.
An agency can always find a number that went up. The reason to distrust that is not cynicism about agencies—it’s just math. With enough metrics and no baseline, something is always up, and the story writes itself.
So the first two to three months of the Send chapter are spent establishing what normal looks like for your business. It is the least exciting period of the partnership and it pays for the next decade of measurement.
## What clean data means
The baseline clock does not start when instruments are installed. It starts when they are demonstrably working.
That means every tracked event tested end to end rather than assumed. Tags named consistently. Tracking parameters applied to every outbound link the team produces. Internal traffic filtered so your own people or bots stop counting as audience. Your CRM’s custom fields populated for the large majority of deals. And the dashboards pulling without errors for thirty consecutive days.
Until that is all true, we are not measuring. We are merely collecting noise carefully.
## What you get during it
Audits and reports still arrive on schedule. They cover instrumentation health and qualitative observation—what we are building, what is now being tracked, what we are noticing, what looks like it might be true and cannot yet be claimed.
What they do not contain is quantitative claims. Where a number appears it is labeled as a reading rather than a result.
## Shortening it
The baseline cannot be compressed, but the wait before it starts often can.
The default sequence has a partner waiting for the analytics work inside Chapter 2, then sixty to ninety days on top, which can put the first genuinely quantitative audit in month five or later.
So where a partner arrives with no CRM and no real analytics, we frequently pull the [integration](/system/integrations) and [analytics](/system/analytics/analytics-setup) work ahead of the website build. Instrumenting is cheaper than designing, it does not wait on review cycles, and it starts the clock in week two instead of month five. It is one of the more valuable decisions available in the Prologue and it is easy to miss.
## What we ask of you
Mostly patience of a specific kind—a willingness to accept “we don’t know yet” as an answer for a defined period, in exchange for everything after it being grounded in something real.
And help with the CRM discipline. The baseline needs deal records that are actually filled in, which is your team’s habit rather than ours. It is the single thing most likely to extend a baseline period beyond ninety days.
Once the baseline closes, your [thesis](/method/thesis) moves from revised to standing. The math on it stops being an estimate and starts carrying your real numbers, and from then on every audit measures against a fixed claim.
# Experiments
Source: https://docs.snapmarket.co/scale/experiments
Every test declared before it runs, including the number that would make it a failure.
**Forthcoming.** This describes where the Scale practice is going rather than what runs today. We are building toward it deliberately, and we would rather show you the destination than imply we are already there.
Every period we run a small number of deliberate experiments, and every one of them is declared in writing before it starts.
The declaration names what we believe will happen, which piece of work is the test, what we will measure, the number that counts as success, how long we will wait, and—the part that matters most—what we will do if it fails. All of that is on record in the audit before any result exists.
## Why bet
Without a threshold written down in advance, any outcome can be narrated as a partial success. Engagement was flat but reach was up. Conversions did not move but the audience got more qualified. These sentences are not lies, exactly. They are what happens when a result arrives and a story gets constructed to fit it, and every agency in the world does this.
Writing the number down first makes retrofitting harder than reporting honestly. That is the entire mechanism, and it is a discipline imposed on us rather than on you.
## Failures get reported as plainly as successes.
A month where two of three experiments missed their threshold is reported as a month where two of three experiments missed their threshold. We revert or move on according to what we said we would do, and the audit says what we learned.
This is uncomfortable to write and it is the point. A report that is always green is a report nobody can use, and a partner who never hears about a failure has no reason to believe the successes.
## What counts as an experiment
Something bounded and answerable within a defined window. A change to the newsletter’s structure. A different opening format for episodes. A landing page tested against its predecessor. A shift in publishing time. A new topic area, run long enough to be judged.
What does not count is anything too diffuse to threshold. “Improve the brand” is not an experiment. Neither is a change measured over a window too short to distinguish signal from an ordinary bad week.
We run a small number at a time, because a month with six simultaneous changes teaches you nothing about which one mattered.
## Where these sit relative to the thesis
The [thesis](/method/thesis) is the engagement-level claim, and it carries its own falsification line—one sentence naming what would prove the whole bet wrong.
Monthly experiments are subordinate bets underneath that claim. A failed experiment is a local correction. A pattern of failures in the same direction is evidence about the thesis itself, and the audit will say so rather than letting a hundred small corrections accumulate into an unexamined position.
Falsifiability at the experiment level is fairly common. Falsifiability at the engagement level is not, and it is the more consequential of the two.
## The rigor is not in the metrics.
Anyone can produce a dashboard. The thing that separates real measurement from a well-designed report is the willingness to call something a failure when it was your own idea.
That is what this section exists to enforce, and it is a standard we hold ourselves to whether or not you are checking.
# The funnel and cohorts
Source: https://docs.snapmarket.co/scale/funnel-and-cohorts
Four stages, four populations, and the transitions between them.
Every piece of work we produce carries a funnel stage, every audit organizes its findings by stage, and every dashboard slices the data the same way. Four stages, defined once, used everywhere.
| Stage | Where the buyer is | What the work is trying to do |
| ------------ | --------------------------------------- | -------------------------------------------------------- |
| A1 Awareness | Does not know you exist | Create an encounter |
| A2 Affinity | Knows you but is not ready | Leave a mark sharp enough to survive the watching period |
| A3 Action | Something triggered, and they converted | Lead them to the promised land |
| A4 Advocacy | Had a good experience, telling others | Give them a story they would want to tell a peer |
## Cohorts, not metrics
Each stage is a population rather than a number. We do not measure metrics floating in isolation. We measure groups of people and how they move between stages.
The Awareness cohort is everyone who encountered you for the first time in a given month, across every surface—search, the podcast, social reach beyond your own followers, press, events.
The Affinity cohort is everyone showing return engagement without yet being in market. Subscribers, repeat readers, people who listen to most of an episode rather than the first two minutes.
The Action cohort is everyone who took a step within the period. A form, a download, a call booked, a record created in your pipeline.
The Advocacy cohort is converted customers producing second-order pipeline. Referrals, customers cited by inbound leads, case studies shipped, and growth in people searching for you by name.
## Transitions are the point (forthcoming)
Cohort counts alone produce a taxonomy. The transitions between them produce a funnel, and that is where the meaning lives.
We aim to track three transitions per month. What share of a month’s Awareness cohort becomes Affinity within thirty days. What share of an Affinity cohort takes an in-market step within ninety. What share of a quarter’s Action cohort closes within six months.
Here is why this matters more than anything else on your dashboard. “A thousand new visitors” is not insight. “Eight percent of last month’s new audience came back and subscribed within thirty days, up from six percent last quarter” is a finding, because it says something about whether the work is doing its job rather than how much of it there was.
It also reframes what a good month looks like. A small audience with a fifteen percent transition rate is a healthier business than a large one at one percent, even where the absolute numbers look similar. One has a machine. The other has traffic.
## Reconciliation
Discrepancies are useful. A gap between what the site recorded and what the pipeline shows almost always points at a tracking problem worth fixing, and finding it in month three is far better than discovering in month eleven that a quarter of your form submissions were never counted.
# Leading and lagging indicators
Source: https://docs.snapmarket.co/scale/leading-and-lagging
Separating what predicts from what confirms, and why that solves the patience problem.
**Forthcoming.** This describes where the Scale practice is going rather than what runs today. We are building toward it deliberately, and we would rather show you the destination than imply we are already there.
Most marketing reporting mixes two kinds of numbers together, and the mixture produces the worst of both.
Put a closed-won figure next to a social engagement rate on the same page and one of two things happens. Either the slow number dominates and everyone loses patience with work that was always going to take three quarters to show up, or the fast number dominates and everyone over-reacts to noise, chasing a bad week and abandoning something that was working.
## Leading indicators
These predict downstream movement. They are shown forward-looking, and the framing is explicit: here is what suggests something about next quarter.
Search impressions trending. Reach to people who do not already follow you. Engagement relative to audience size rather than in absolute terms. Time spent on your editorial pages. The share of visitors who return. Newsletter open trend. How far into an episode people actually get.
None of these are revenue. All of them move first, and a partnership where the leading indicators are climbing in month three is a partnership that is working even though nothing has closed yet.
## Mid-funnel indicators
The transition events themselves. Newsletter clicks, downloads, calls booked, pipeline created. These sit alongside both views because they are the hinge between the two.
## Lagging indicators
These confirm work already done. They are shown retrospectively with the lag stated on the page—work published in the first quarter has now produced this.
Closed deals. Signed contracts and commitments. Retention. Customer lifetime value. The number of people searching for your company by name.
## Why the layout matters
This is the patience problem solved as a design decision rather than a conversation you have to keep having.
When leading indicators sit prominently and lagging ones sit in a clearly labeled retrospective panel, a client in month four can see genuine movement without anyone having to argue that the slow numbers will eventually arrive. And when the slow numbers do arrive, they are attributed to the period that actually produced them rather than to whatever happened to be running that month.
## The lag is real.
Work published in month one does not produce pipeline in month two. Depending on your sales cycle, the lag between the two is commonly three to nine months.
We say this at kickoff, we put it on the dashboard, and we repeat it in the audit. Not to lower expectations, but because a partnership where both sides understand the lag makes better decisions than one where somebody is waiting for month three to justify itself.
# Scale: the measurements
Source: https://docs.snapmarket.co/scale/overview
Measurement as a posture rather than a phase, running from the first day.
Scale is not a chapter. It is the layer running underneath all three, from the day the partnership starts until the day it ends. The instruments get built once, inside [Chapter 2](/system/analytics/overview). The measuring itself never stops.
What this layer gets you is the ability to walk into a board meeting and account for the spend without an interpreter, and to know which part of the work to stop doing.
## What this layer holds
Building the number that actually means something.
Why we separate what predicts from what confirms, and why patience matters.
Sixty to ninety days where we make no quantitative claims at all, and why.
What a customer costs and what they are worth, computed simply and honestly.
Every test declared before it runs, including the number that would make it a failure.
A letter on what the last period produced and what the next one is betting on.
## Translators, not a data team
We do not pretend to be data scientists. We are translators. We read messy data from six platforms and turn it into a clear account of what is happening, in language you can take to a board without an interpreter. What you need is someone who explains the funnel plainly and shows what is working without burying you in numbers that flatter everyone and inform nobody.
You are not expected to log into a dashboard and work out what it means. That is our job. You get a written account of what happened and what we think it implies, and the dashboard sits underneath it if you ever want to check our work.
So our job is to make your data legible, not to invent more of it.
## How often this happens
The data is reviewed every month and we act on it every month. The strategy itself is not on a schedule. It can hold for years, and often should, because a plan revised every thirty days never runs long enough to tell you whether it worked. What changes a strategy is evidence, not the calendar.
## What this layer asks of you
Context we do not have. A pricing change, a new salesperson, a large customer who signed through a personal relationship. Missing context is the most common cause of a misread month.
And a decision on each recommendation. Every one is tagged to a piece of work, so agreeing means it gets scheduled and declining means we will not raise it again without new evidence. A review received without a response has become a formality, and formalities are how partnerships drift.
## The point of all of it
The standing [thesis](/method/thesis) is the claim. Scale is the apparatus for finding out whether it is true.
Without the thesis, measurement produces a stream of numbers with no argument behind them, and any month can be narrated as a good one. With it, there is a fixed claim on record, and every audit is a report on whether reality is cooperating.
How a partnership ends well, and what is already yours when it does.
# Unit economics
Source: https://docs.snapmarket.co/scale/unit-economics
What a customer costs and what they are worth, computed simply and honestly.
**Forthcoming.** This describes where the Scale practice is going rather than what runs today. We are building toward it deliberately, and we would rather show you the destination than imply we are already there.
At some point the question stops being whether the marketing is working and becomes whether it is worth what it costs. This is the section that answers that, and it is deliberately simple.
## The five-minute retro
Every time you close a deal, someone answers three questions. It takes five minutes and it is the foundation of everything else here.
Where did this customer first encounter anything we produced. Which specific piece most clearly prompted them to reach out. What was the final step before they signed.
That’s it. Recorded in your CRM at intake or close, cross-checked by us monthly.
## Why this instead of attribution modeling
Multi-touch attribution exists to find signal in populations too large to ask individually. When the population is small enough to ask, asking is more accurate, far cheaper to maintain, and produces something a model never does—the actual sentence the customer used about why they got in touch, which frequently turns out to be more useful than the attribution itself.
## What we compute
Once the baseline has closed, quarterly, per partner.
What it costs to add a genuinely engaged contact. What it costs to produce a discovery conversation. What it costs to produce a closed customer. What a customer is worth over their life, using your revenue and tenure figures. And the ratio between those last two.
Each is a straightforward division rather than a model. Our fee and any spend over the outcome. Nothing more sophisticated than that, deliberately.
## The trend, not the number
None of these numbers are exactly right, and we will say so rather than implying a precision we do not have.
What they are is consistently computed, which makes the direction trustworthy even when the absolute figure is not. A cost-to-value ratio moving from three to five across four quarters is a strong signal about whether the machine is improving. The same ratio quoted to two decimal places in a single quarter is a number pretending to be a finding.
## What we need from you
The two inputs only you have: what a customer is worth and how long they stay. We cannot derive these and a guess makes everything downstream fiction.
And the retro discipline. Three fields, at close, most of the time. Where those fields are empty more often than not, this section degrades to guesswork.
## Where this shows up
In your [thesis](/method/thesis), which built its math using these inputs, and in the quarterly audit that checks the math against what actually happened.
# A podcast with 10 episodes
Source: https://docs.snapmarket.co/send/artifact
Not launched. Sustained. The distinction is the whole point.
Chapter 3 closes when your podcast has published on its stated cadence for up to 10 episodes without a miss.
Not when it launches. Launching is a project with a deadline and everyone shows up for it. Sixty days later, when the novelty is gone and the recording is competing with a full calendar and nobody outside the company has said anything encouraging yet, is the point at which we learn whether the thing is real.
## Why this is the line
Because cadence is the multiplier, and cadence is the thing that fails.
The overwhelming majority of company podcasts stop between episode four and episode nine. They do not stop because the content was bad. They stop because nobody built a routine that survives a busy month, and because the audience had not yet grown large enough to create any obligation to continue.
Ten episodes on schedule means the routine exists. The recording is on the calendar and gets protected. Approvals move. The process runs without heroics. Once that is true, the show tends to keep going for years, and everything downstream of it—the writing, the newsletter, the social—has a reliable source.
We made it an artifact because it is the honest test of whether Chapter 3 has actually started.
## What counts
Published on the cadence you set, without a gap. We would rather you chose a cadence you will clear comfortably than an ambitious one you have to rescue. The number of episodes is not the point. The unbroken line is.
## What happens after
Nothing changes and that is the intention. The chapter is marked complete and the machine keeps running, and from here Send compounds for as long as the partnership lasts.
What changes is what we watch. Before the artifact the question is whether the routine will hold. After it, the question moves to what the work is producing—which episodes performed, which topics generated replies, which pieces show up in the path of people who eventually became customers. That is the [Scale layer’s](/scale/overview) work, and by this point it usually has enough clean data to say something.
## If the schedule doesn’t hold...
Sometimes it doesn’t, so it’s worth saying what happens then.
A cadence that keeps slipping is information, not a failure to be managed. Usually it means one of three things: the format asks too much of the host, the cadence was set optimistically, or the person on the show does not actually want to be doing it.
All three are fixable, and all three are cheaper to name in month two than to discover in month eight. The audit will raise it rather than describe a stalling show as steady.
How we measure any of this, and what we refuse to claim.
# § 3.3 Sales and other assets
Source: https://docs.snapmarket.co/send/assets/overview
Collateral your sales team uses, and the specialists we coordinate rather than replace.
The last section of Send covers two quite different things: the physical and printable material your sales team puts in front of people, and the specialist partners we bring in where the work is genuinely outside what we do.
The second half is where we are most explicit about our limits, and that is deliberate. An agency that claims every capability is an agency that is mediocre at several of them.
## What this section covers
One-pagers, leave-behinds, brochures, signage, and event material.
Specialist partners, coordinated by us, with the money and the mandate staying yours.
## The part most companies neglect
A1 and A2 work—the podcast, the writing, the social—gets the attention because it is visible and it feels like marketing. A3 material, the thing a salesperson hands to a serious buyer two weeks before a decision, is frequently five years old and/or made in a hurry.
The [coordinate system](/method/coordinates) exists partly to make that imbalance visible. When a quarter’s work is entirely A1 and A2, the audit says so, and the question of whether that is deliberate gets asked out loud rather than discovered in a lost deal.
## Why we coordinate rather than execute
Paid media and PR are both real crafts with practitioners who do nothing else. Running ads well requires daily attention to an account and a tolerance for a kind of work we are not organized around. Media relationships take years to build and cannot be faked.
So where you need those, we bring in someone who is genuinely good at it, brief them properly, keep the message and creative consistent with everything else you publish, and stay accountable for the outcome. What we do not do is touch your ad budget or claim media relationships we do not have.
The partner’s fee and any spend are yours, quoted separately, and paid directly. We can invoice on a pass-through basis if you prefer. We just want to be clear about what is our time and what is theirs.
# Paid media and PR
Source: https://docs.snapmarket.co/send/assets/paid-and-pr
Specialists we coordinate. The money and the mandate stay yours.
§ 3.3.2 and § 3.3.3 · A1 / A2 / A3 · two weeks to stand up · monthly oversight thereafter
## What this is
Coordination of specialist partners on your behalf. For paid media, that means briefing the partner, keeping creative and message consistent with everything else you publish, and reviewing performance monthly. For PR, it means bringing the story and the relationship while the partner brings media access.
We stay accountable for whether the work serves your thesis. We do not do the specialist execution.
## What we do not do, precisely
We do not build, run, or manage advertising campaigns, and we do not touch your ad account or your budget. Ad spend goes directly from you to the platform. The paid partner’s fee goes directly from you to them, though at times we can invoice on a pass-through basis.
We do not write press releases, pitch journalists, or maintain media lists. Those relationships take years to build and cannot be improvised.
## What we do instead
The thing specialists most often lack is context. A paid partner given a budget and a vague objective will optimize for the metric in front of them, which is frequently not the metric that matters to your business. A PR partner without your positioning will pitch a generic story.
So we write the brief, and the brief comes out of your [thesis](/method/thesis) and your [messaging document](/story/message/messaging-document). We review the creative before it runs so your ads look and sound like the rest of your work. We read the performance and tell you what we think, including when we think the spend is not earning its place.
That last part is why coordination is worth paying for. A specialist is rarely the right person to tell you their own channel is not working.
## Paid is an accelerant, not a foundation
Paid attention stops the moment you stop paying. It works well on top of something that already converts—a proven landing page, a message that has been tested organically, an offer with evidence behind it. It works badly as a substitute for building those.
It also requires lots of ongoing content to populate channels, test messages, and build the infrastructure required to convert leads from paid media.
We will usually argue for organic first and paid later, and we will say so if we think you are reaching for spend to avoid a harder problem.
## What we need from you
A decision on budget and a tolerance for the learning period, which is real and costs money before it produces anything.
Someone on your side who owns the relationship with the specialist commercially. We coordinate. We do not sign their contract.
For PR, something genuinely newsworthy. The most common failure is a campaign built around an announcement that is interesting internally and to nobody else, and it is better to hear that from us before billing our specialist.
## What sits outside the fee
All ad spend, the paid specialist’s fee, the PR specialist’s fee, media database subscriptions, and wire distribution. All of it is yours, quoted separately, and paid directly or on a pass-through basis.
Sixty consecutive days of publishing, and why that is the line.
# Print and collateral
Source: https://docs.snapmarket.co/send/assets/print-and-collateral
One-pagers, leave-behinds, brochures, signage, and event material.
§ 3.3.1 · A3 / A4 · typically two weeks per piece
## What this is
Anything physical or printable. One-pagers, leave-behinds, brochures, business cards, signage, trade show material, and PDFs your sales team sends after a meeting.
Designed to your brand system, which means this piece is far cheaper and better when § 1.3 has been done. Collateral produced without a visual identity to inherit from ends up as a set of documents that each invented their own rules.
Of everything in this section, the one-pager is the piece that most often changes an outcome, and it is the piece most companies have not touched in years.
It is what a champion inside a prospect’s organization forwards to the person who actually decides. That person was not in your meeting, will not read your website, and will form their impression from one page. If that page is a feature list in an old template, your champion is arguing your case with a bad instrument.
A good one is short, says the one thing, and is written for the reader who did not meet you.
## Batches are not linear.
The first piece in a set carries the cost of the thinking—the layout system, the grid, the treatment of your brand in a printed context. Every subsequent piece inherits that and runs considerably lighter.
So commissioning six pieces at once is meaningfully cheaper than commissioning six pieces across a year, and if you know a batch is coming it is worth telling us now.
## What we need from you
The content, and clarity about the reader. A one-pager for a technical evaluator and one for a chief executive are different documents even when they describe the same thing.
For anything printed, the quantity, the deadline, and where it needs to physically be. Print has real lead times and shipping is not instant, and the deadline is almost always the constraint that shapes the decisions.
## What sits outside the fee
Print production, shipping, any specialty finishing, and stock imagery, billed at cost.
# Blog and long-form content
Source: https://docs.snapmarket.co/send/content/blog-and-long-form
Articles, thought leadership, guides, and case studies written from scratch.
§ 3.2.1 · A1 / A2 · typically one week per piece · recurring
## What this is
Written pieces originated rather than derived. Articles, thought leadership under an executive’s name, resource guides, and case studies. Research, outline, draft, edit, and search optimization.
A standard piece runs around a thousand words. Substantial pieces with original research or interviews run considerably longer and get scoped as their own thing rather than absorbed into a standard slot.
## When to originate rather than derive
Most of your written output should come out of the [Voice-to-Market™ package](/send/podcast/v2m), because that is cheaper and it sounds more like you. This piece is for the things the show does not naturally cover.
The common cases are a topic that needs research the founder does not carry in their head, a case study that needs a customer interview, a piece with a deadline that will not wait for the recording schedule, and a search-driven piece targeting a specific question your buyers ask.
If a topic could plausibly be an episode, we would usually rather it were one.
## What we need from you
For most pieces, very little—the messaging document and the audience profile carry it.
A short conversation with an expert in the topic if possible. Writing from a brief produces something publishable and slightly hollow, and the difference is legible to readers even when they cannot name it. Twenty minutes on the phone changes the piece more than any amount of research.
For a case study, an introduction to the customer and their permission. This is almost always the slow part.
Subject-matter review where the content is technical or regulated, ideally from someone who can actually approve rather than only comment.
## What you will have
A finished piece, optimized for search.
The standard we hold every piece to is whether it sounds like you rather than like a marketing agency, whether it serves the strategy rather than filling a slot, and whether your ideal customer would find it useful rather than only your marketing team.
## How long it takes
About a week for a standard piece. Longer where an interview or subject-matter review is in the path, which is usually the constraint rather than the writing.
## What this is not
Not a piece derived from a recording—that belongs to the [V2M package](/send/podcast/v2m) regardless of how it reads at the end.
# Email
Source: https://docs.snapmarket.co/send/content/email
Newsletters, campaign sends, and the sequences that run without anyone touching them.
§ 3.2.4, § 3.2.5 and § 3.2.5r · A2 / A3 / A4 · sends in days, sequences in weeks
## Why email still matters most
Of everything in Chapter 3, email is the only channel where you own the relationship outright. A platform can change what your followers see. A search engine can change what ranks. Nobody can come between you and a list you own.
For the kind of business we work with—long consideration periods, high trust requirements, a buyer who is not in market today but will be in eighteen months—a list of people who agreed to hear from you is the single most valuable asset the Send chapter builds.
## The two kinds of work
**Sends.** A newsletter or a campaign email: copy, build, segmentation, testing, and dispatch. Most of your newsletters come out of the [Voice-to-Market™ package](/send/podcast/v2m) rather than being written here. What lives in this piece is the send that is not derived from a recording—an announcement, an investor update, a campaign email.
The first send for a new partner runs materially longer than the ones after it, because it includes building the template and the components everything afterward inherits.
**Sequences.** Automated flows that run without anyone touching them: welcome series, onboarding, nurture. Brief, flow map, copy, build, triggers, and end-to-end testing. Five emails is our standard recommendation for a welcome sequence.
The hidden half of any sequence project is connecting your email platform to your CRM, which is [integration work](/system/integrations) and is quoted separately. A sequence with no trigger data behind it is a set of well-written emails nobody receives.
## Sequences get reviewed, not set and forgotten.
We review a live sequence against its actual numbers monthly. Diagnose, revise, rebuild, retest.
This matters because a sequence written before anyone has behaved is a hypothesis. The second email that everyone stops reading, the subject line that underperforms, the step where the timing is wrong—none of these are visible until real people move through it. An automation nobody has revisited in two years is usually costing you something.
## What we need from you
A list you have permission to email, and honesty about its history. A list that has not been sent to in two years needs careful re-warming rather than a full send, and getting that wrong damages your domain’s ability to reach anyone.
Working authentication on your domain, which we check as part of [domain and hosting](/system/website/domain-and-hosting). Without it a share of everything you send does not arrive.
A reviewer who can turn around a send quickly, since email is the piece most often tied to a date.
# LinkedIn lead generation
Source: https://docs.snapmarket.co/send/content/linkedin-lead-gen
A warm-list pipeline that surfaces the people already paying attention to you.
§ 3.2.6 and § 3.2.6r · A1 / A3 · two to three weeks to build · ongoing tuning monthly
## What this is
A pipeline that watches who engages with your posts and the posts of people in your orbit, scores those people against your ideal client profile, and releases the best few each day into your CRM with a drafted opening message ready for a human to review and send.
It is not cold outreach. Every person in it did something first—they liked, commented, or followed. The premise is that a warm list of people already paying attention to you is a better use of a sales hour than a purchased list of people who are not.
## Where the human stays
A person reads and sends every message. Always.
The drafting is automated because writing forty opening lines a week is drudgery that produces worse results than it should. The judgment is not automated, because the entire value of a warm list is that the outreach feels like a person noticed you, and a fully automated sequence destroys that in the first message.
We would rather send fifteen good messages a week than a hundred that make your company look like everyone else’s automation. That is a real constraint on volume and it is deliberate.
## The prerequisite
A defined [ideal client profile](/story/message/ideal-client-profile). The scoring is only as good as the profile it scores against, and without one the pipeline surfaces everyone who ever clicked something, which is worse than nothing because it wastes the sales attention it was supposed to save.
If you do not have one, that piece comes first.
## What we need from you
A decision on which CRM this lands in and who owns it.
A person on your side who will actually work the list daily. Ten minutes, most days. A pipeline nobody opens is an expensive way to accumulate contacts, and this is by far the most common way this piece fails.
Agreement on tone for the opening message. It goes out under a real person’s name, so it has to sound like that person.
## Expect ongoing work
We are direct about this. A pipeline like this is not built once and left alone. Scoring thresholds drift, duplicates accumulate, credentials expire, and draft quality needs tuning against what is actually getting replies.
## What this is not
Not paid lead generation. Not a purchased contact list. Not an automated sequence that sends without a human reading it.
# § 3.2 Content marketing
Source: https://docs.snapmarket.co/send/content/overview
Writing, social, email, and the warm-list pipeline. The recurring surface area.
This is the widest section in the manuscript and where most of a partnership’s monthly volume lives. Long-form writing, social, email, and the pipeline that turns engagement into a conversation.
Most of it is derived rather than originated. The [Voice-to-Market™ package](/send/podcast/v2m) already produces a written piece, a newsletter, and clips from each recording, so what lives here is the work that sits alongside that—the pieces the show does not cover, the standing management of channels, and the sequences that run automatically once built.
The difference matters when you are looking at a list of work. A newsletter derived from an episode belongs to § 3.1. A newsletter written from scratch belongs here.
## What this section produces
Articles, thought leadership, resource guides, and case studies written from scratch.
The monthly batch, the management layer, and one-off posts.
Newsletters, campaign sends, and the automated sequences behind them.
A warm-list pipeline that surfaces the people already paying attention to you.
## The through-line
Everything in this section is downstream of the [messaging document](/story/message/messaging-document), and that is not a formality.
The failure state for content marketing is output that could belong to any company in the category. It is competent, it is on schedule, and it is completely forgettable, because it was written to fill a slot rather than to say a specific thing that a specific person needed to hear. Generic output on a reliable cadence is still generic.
So every piece here is written against your settled positioning and your audience’s actual vocabulary. Where we cannot tell what makes a piece yours rather than anyone’s, the piece is not finished.
## Organic first
We are an organic-first agency and it is a considered position rather than a limitation we are dressing up.
Paid attention stops the moment you stop paying for it. Owned attention—a list, a following, a search position, an audience that expects your next thing—compounds and stays yours. For the kind of businesses we work with, where twenty to fifty customers a year is a good year and trust is the actual bottleneck, the compounding asset is worth more than the rented one.
That does not mean paid never makes sense. It means we treat it as an accelerant on something that already works rather than a substitute for building it, and where you want it we [coordinate a specialist](/send/assets/paid-and-pr) rather than running it ourselves.
# Social media
Source: https://docs.snapmarket.co/send/content/social
The monthly batch, the management layer, and the occasional one-off.
§ 3.2.2, § 3.2.3 and § 3.2.3b · A1 / A2 · batch produced weekly, published monthly · recurring
## Three different things
Social gets talked about as one item and is actually three, with quite different economics. Knowing which you are buying prevents the most common source of confusion in this section.
**The monthly batch** is a full month of content produced in one pass—roughly forty posts with graphics, written to your voice, loaded and scheduled with advocacy and reposting configured. This is the default for any partner running a consistent cadence, and it is materially more efficient per post than producing them individually.
**The management layer** is the ongoing tending: calendar planning, publishing oversight, platform maintenance, and watching what is being said. It is sold alongside the batch, not instead of it.
**A single post** is exactly that—one graphic, one caption, for an announcement that will not wait for the next batch. Useful occasionally. Expensive as a habit, and if you find yourself asking for several a month, the batch is the answer.
## Why batching
Because the expensive part of a social post is not making it. It is deciding what it should be.
Produced in a batch, that thinking happens once across forty posts, with a coherent shape to the month. Produced one at a time, it happens forty times, each from a standing start, and the output is both costlier and less coherent—a month of posts that were each individually reasonable and together say nothing in particular.
Much of the batch is drawn from your recordings and long-form pieces, which is why this section costs less when Chapter 3’s engine is running.
## Employee advocacy
People buy from people, not from companies.
A post from a named person with a face and a history outperforms the same words from a company account, and it does so consistently enough that we treat it as the default rather than an experiment. So where there is a choice, we publish from a person’s account. We still post from company accounts—there is a real role for them, particularly for announcements—but the personal account is more authentic and it travels further.
The second half is amplification. We add three to five senior leaders to the Ordinal workspace, and their accounts like and repost the work as it goes out. That early engagement is what decides whether a post reaches beyond the people who already follow you.
This is mostly a LinkedIn practice because that’s where this works best. It asks very little of the people involved—no writing, no thinking, just permission and a few seconds—and it is the highest-return, unglamorous thing available in this section.
## What we need from you
One consolidated approval per batch. This is the step that determines whether you publish on cadence.
A note of anything coming that we should build around—an event, a hire, an announcement, a quiet period. A batch built without knowing about next month’s launch is a batch that gets rebuilt.
For employee advocacy, a short conversation with the people whose accounts are involved. It works well and it works considerably better when the participants understand what it is before posts start appearing.
## What you will have
A scheduled month of content across your platforms, on brand and on message, with tracking on every link so the [Scale layer](/scale/overview) can tell which posts did something rather than which posts felt good.
## What this is not
Not clips derived from an episode, which belong to the [V2M package](/send/podcast/v2m). Not paid social, which we [coordinate through a specialist](/send/assets/paid-and-pr) rather than run.
# Send: the work in the world
Source: https://docs.snapmarket.co/send/overview
The disciplined act of putting work into public, on schedule, over years.
Chapter 3 is the one that never ends.
One recorded hour becomes a dozen things. A written piece, a newsletter, a set of clips, show notes, and weeks of social posts, all worked outward from a single conversation. That ratio is the entire reason this chapter is built the way it is.
Story settles what is true and System builds what carries it. Send is the ongoing, unglamorous discipline of putting work into public on a schedule and continuing to do so long after the novelty has worn off. It is where most of the monthly volume of a partnership lives.
Cadence is the multiplier. Not brilliance, not volume, not any single piece. A modest thing published reliably for two years outperforms an excellent thing published four times and abandoned. Audiences do not form around quality alone. They form around the reasonable expectation that something will be there again.
## The engine underneath
Most of what this chapter produces comes from one source: your voice, recorded. Trying to generate a written piece, a newsletter, clips, show notes and weeks of posts independently, from a blank page, every week is what makes content programs collapse. We would rather capture one hour of genuine thinking and work outward from it. **We call that [Voice-to-Market™ (V2M)](/send/podcast/v2m)**, and it is the reason the podcast is this chapter’s artifact rather than one channel among several.
## The three sections
The show, and the V2M package every episode produces.
Long-form writing, social, email, and the warm-list pipeline.
Collateral, and coordination of the paid and PR specialists we work alongside.
## The artifact
Chapter 3 closes with a [podcast](/send/artifact) that has published on a stable cadence for 5 to 10 episodes. Not launched. Sustained. The distinction is the whole point, because launching is easy and sustaining is the thing that actually produces an audience.
## When this happens
Send begins once Story has produced enough raw material to publish from, usually around month four. Once it starts it does not stop, and it compounds for as long as the partnership lasts.
That compounding is real and it is slow. Work published in month one does not produce pipeline in month two. The [Scale layer](/scale/overview) exists partly to make the lag visible rather than a matter of faith, so you can see the leading indicators moving while the lagging ones are still catching up.
## What this chapter asks of you
About an hour per episode in front of a microphone. That’s most of it.
You choose the cadence. Weekly means roughly four hours a month, monthly means one, and the results follow from whatever you pick. We would rather build the schedule around what you will still be doing next winter than around what sounds ambitious in month one.
From each recorded hour we produce the written piece, the newsletter, the clips, the show notes, and the social posts, then run them through an approval process that does not have to involve you. The person being interviewed is often a founder or a senior expert. Approvals can sit with whoever runs marketing.
If you already have recordings, footage, or a back catalog, we work from those instead, and even that hour largely disappears.
The measurement running underneath all three chapters, from the first day.
# § 3.1 Podcast
Source: https://docs.snapmarket.co/send/podcast/overview
One recording, worked outward into everything else you publish.
The podcast is not a channel we happen to like. It is the input to the rest of Chapter 3.
Here is the problem it solves. A content program that generates each piece independently—a blog from a blank page on Monday, a newsletter from a blank page on Wednesday, five social posts from a blank page on Friday—asks a founder for the same scarce thing over and over, which is original thinking on demand, and it often collapses within a quarter. It also happens to be expensive to produce.
A recorded conversation asks for that thinking once, in the format humans are best at, and everything else is derived from it. Forty minutes of you talking about something you actually know produces a written piece, a newsletter, a set of clips, show notes, and up to a month of social material. The founder’s job becomes showing up and being interesting for forty minutes, which is a job most leaders can actually do. A recorded conversation asks for that thinking once, in the format humans are best at, and everything else is derived from it. Forty minutes of you talking about something you actually know produces a written piece, a newsletter, a set of clips, show notes, and a month of social material. The founder’s job becomes showing up and being interesting for forty minutes, which is a job most leaders can actually do.
## What this section produces
Standing up a new show: format, artwork, templates, hosting, distribution, and a pilot.
Every episode becomes its full set of derived pieces and gets published everywhere it belongs.
Post-production on footage you already have.
## Podcast is a loose word here.
It does not have to be a podcast in the conventional sense, and for several partners it is not.
The format is a recorded conversation on a schedule. That can be an interview show, a solo commentary, a recorded internal briefing, a webinar series, or a monthly conversation with a customer. What matters is that it is recorded, that it happens regularly, and that it captures a real person thinking out loud rather than reading a script.
We help you pick a format you will sustain rather than the one that sounds most impressive at kickoff.
## The honest prerequisite
This section asks something of you that no other section does, and it is worth being direct about it.
Someone has to be willing to be on record, regularly, for a long time. Usually the founder, executive, or SME. If nobody in your company wants that, this is the wrong bet, and we would rather establish that in the Prologue than four months into a show that slowly dies.
The question we ask in the thesis conversation is deliberately blunt: are you willing to be on camera every week for a year? A no is a perfectly good answer. It changes the bet rather than ending the conversation.
# Show setup
Source: https://docs.snapmarket.co/send/podcast/show-setup
Standing up a new show, once, so every episode afterward is routine.
§ 3.1.0 · A1 / A2 · typically four weeks · one-time per show
## What this is
Everything required to bring a show into existence: format and positioning, cover artwork, video and social templates, a branded layout pack for editing, hosting and distribution to the podcast directories, integration with your website, and a calibrated pilot run.
It happens once. After it, every episode is a routine that runs on rails, which is the entire objective. A show that requires a series of decisions every week is a show that stops.
## The format conversation
The most consequential hour of this piece, and it is not about equipment.
We work out who is on the show, what it is about narrowly enough to be recognizable, how long an episode runs, and—the one that matters most—how often. That last answer should be the cadence you will still be keeping in eighteen months, not the one that sounds ambitious at kickoff. Every other week sustained beats weekly abandoned, and we will argue for the slower answer more often than you might expect.
We also settle the positioning. A show about your industry in general competes with everything. A show about the specific thing your ideal client is subtly worried about competes with almost nothing.
## What we need from you
A decision on who hosts, and their genuine commitment to the cadence. We can host the show and interview you if needed—many of our clients prefer this approach.
An existing brand system for the artwork and templates to extend. If you do not have one, the [visual identity](/story/visual-identity/overview) work comes first, because artwork invented in a vacuum will not match anything else you publish.
A few hours across the setup period for format conversations, artwork review, and the pilot recording.
A short conversation about your recording setup. We are not precious about equipment, but audio quality is the one production variable listeners actually notice, and it is cheap to get right at the start.
## What you will have
A show that exists—artwork, a feed live in the major directories, a website page, templates for video and social, and a per-show configuration recording every decision so that no episode requires re-deciding anything.
And a pilot episode that has been through the full process end to end, so the first real episode is not also the first time the machine has run.
## How long it takes
About four weeks, with syndication directory approval accounting for some of it and being outside anyone’s control.
## The kit we recommend
You don’t need a studio. You do need to not sound like a conference call.
Go all-in Apple where you can, cables included, and keep everything USB-C. Fewer adapters means fewer things to go wrong five minutes before a guest joins.
Supplement with an [Elgato](https://www.elgato.com) kit—the [Wave 3](https://www.elgato.com/us/en/p/wave-3) microphone, a [Key Light Air](https://www.elgato.com/us/en/p/key-light-air), and a [Facecam MK.2](https://www.elgato.com/us/en/p/facecam-mk2). The whole set runs roughly \$300 to \$500. A [Rode Wireless Micro](https://rode.com/en-us/products/wireless-micro) is a good alternative if you would rather be free of a desk. Editing happens in [Descript](https://www.descript.com), which we handle.
The part that costs nothing and matters most is light. Put a natural window in front of you, a lamp behind you for depth, and kill the overhead. Overhead lighting is the single most common reason a well-equipped setup still looks wrong.
What happens to every recording after you make it.
# Voice-to-Market™ (V2M)
Source: https://docs.snapmarket.co/send/podcast/v2m
One recording becomes the whole set, published everywhere it belongs.
§ 3.1.1 · A1 / A2 · typically seven days from recording to published · recurring per episode
## What this is
Voice-to-Market™ (V2M). A recording arrives and becomes the show’s full content package, published everywhere it belongs.
The exact set is defined per show, because a fund’s package and a contractor’s package should not look the same. A typical one includes the edited episode, a long-form written piece, a newsletter, a set of Q\&A drawn from the conversation, short clips for social, an announcement post, show notes, and the transcript.
Everything in that list comes from the same forty-minute recording. That is the whole idea, and it is why this piece exists as a single unit rather than seven separate requests.
## Why it is one piece and not seven
If a deliverable originates from a transcript, it belongs to this piece regardless of what it looks like at the end. A newsletter derived from an episode is part of the V2M package, not a separate email marketing piece. A blog post derived from an episode is part of the package, not a separate writing piece.
The reason is not bookkeeping. It is that deriving seven things from one conversation is a fundamentally cheaper operation than producing seven things from nothing, and pricing them as if they were the same would misrepresent both.
## What we need from you
The recording, and a review pass.
On the recording: record a bit more than you think you need, do not stop for small mistakes, and resist scripting. The pieces that travel furthest are almost always the moments where someone said something slightly more candid than they had planned to.
On review: a single consolidated approval, ideally within a couple of days. This is the step that determines whether the show publishes on cadence, and a package sitting in an approval queue for a week is how a fortnightly show becomes a monthly one without anybody deciding that.
Where your industry is compliance-sensitive, tell us at the start rather than at review. Certain claims need particular handling, and knowing that up front is far cheaper than a rewrite.
## What you will have
The full package for the episode, provided via [Ordinal](/method/tools), and published to your feed, your website, your social accounts, and your list, with tracking on every link so the [Scale layer](/scale/overview) can see which pieces actually did something.
## How long it takes
About seven days from recording to approval, sometimes fully published, assuming review comes back promptly. Technically complex or compliance-sensitive episodes run longer, and we will say so when we take one on.
## A note on sources
This process does not require a podcast. Any recording works—a webinar, a conference talk, an internal briefing, a customer conversation you had permission to record, or a voice memo you made in the car because you had a thought. If it is a recording of someone saying something true, it can become a package.
# Video editing
Source: https://docs.snapmarket.co/send/podcast/video-editing
Post-production on footage you already have, within a deliberately drawn boundary.
§ 3.1.2 · A1 / A2 · typically one week · per project
## What this is
Post-production on footage that already exists. Trimming, removing filler, captions, lower thirds and simple graphics, and formatting for whichever platform it is destined for.
A testimonial someone filmed on a phone at a conference. A recorded talk. A case study interview. Footage sitting in a folder that nobody has had time to cut.
## The boundary, stated plainly
We do light editing. Trims, logo, filler removal, captions, straightforward graphics.
We do not do heavy multi-camera work or motion graphics. Where a project needs that, we say so and quote it with a specialist partner rather than attempting it and delivering something merely acceptable. Video is a craft with a steep quality curve, and the gap between competent and good is visible to everyone.
## What we need from you
The footage, in the highest quality version you have—not the compressed copy someone sent over a messaging app.
A sense of length and destination. A ninety-second cut for social and a six-minute cut for a website page are different edits, not the same edit trimmed.
Anything you know you want kept or cut. One pass of notes at the start saves two rounds later.
## How long it takes
About a week per video, depending on the length of the source footage and how much of it there is to work through.
## What this is not
Not original video production—concept, script, crew, and shoot are [brand video](/story/visual-identity/photography-and-video) in Chapter 1. Not social clips cut from a podcast episode, which are part of the [Voice-to-Market™ package](/send/podcast/v2m) and already included there.
# The Storybook
Source: https://docs.snapmarket.co/story/artifact
The single artifact that closes Chapter 1 and governs everything after it.
Every chapter closes with one artifact. Chapter 1 closes with the Storybook.
It is the canonical brand document—worldview, audience, differentiation, language, and visual identity gathered into a single place you can stand behind for years.
## Why it exists
The practical answer is that the work of Chapter 1 is otherwise scattered across a messaging document, an audience profile, a strategy, and a folder of design files, which means that in eighteen months nobody can find the whole picture and a new marketing hire reconstructs it from the website. The Storybook is the consolidation that prevents that.
The real answer is that a company needs one document it can hand to someone and say: this is who we are. Not the pitch, not the deck, not the about page. The account that the pitch and the deck and the about page are all derived from.
## What is in it
Your worldview—what you believe about your category and why the company exists at all. The audience, described the way § 1.1 described them. The differentiation, in the single sentence that survived the pressure test. The language: the words you use, the words you avoid, the narratives you return to. And the visual system, so that the way the brand looks and the way it sounds are visibly the same claim.
## What it looks like
The form varies. Some partners want a printed artifact, physically well made, that sits on a desk and gets handed to new executives. Others want a living page their team can reference and search. Both are the Storybook. The name and the definition of complete stay constant, and the medium follows how your company actually works.
We will ask you which you want, and if you are unsure, we default to whichever one your team is more likely to actually open.
## When it is done
When it exists and you have approved it, Chapter 1 is closed. That is the whole definition, and we keep it strict on purpose. “Done” is the hardest word in this business, and an artifact is what gives it a meaning you can hold.
Closing the chapter does not mean the message is frozen. It gets revisited quarterly or annually through a [messaging refresh](/story/message/messaging-refresh), and the Storybook is updated with it. But the foundation is settled, and Chapter 2 can be built on top of something that is not still moving.
# Ideal client profile
Source: https://docs.snapmarket.co/story/message/ideal-client-profile
Who you are trying to reach, described well enough to change how we write.
§ 1.1.3 · A1 / A2 · typically two weeks
## What this is
Question one of the five, formalized into a document of its own. Who you are trying to reach, where they are, what they care about, what language they use, and what specifically moves them from content to actively looking.
Most of the time this is absorbed into the messaging document rather than sold separately. It becomes a standalone piece when something downstream needs a sharp target to score against—outbound lead generation, a paid campaign, or a sales team that needs to agree on what a good lead looks like before they can agree on anything else.
## What makes it useful
The test we hold it to is simple. If the profile does not change how a headline gets written, it is not finished.
That rules out most of what passes for audience work. “High-net-worth investors in North America” is a filter, not a profile. “Accredited investors who built their wealth running a landscaping business out of the back of a pickup, who value grit and distrust anything that looks expensive” tells you the tone, the photography, the sentence length, and which three words to never use. Both describe real people. Only one of them can be written from.
So the document leans on what your audience believes rather than what they are. Demographics and firmographics are in there, bounded and specific, but the weight sits on the asymmetric beliefs—the things this audience holds more strongly than the audience next door.
## What we need from you
Conversations with whoever knows your buyers best, which is usually the founder or leading executive plus a leading salesperson. Three to five calls with actual current customers if you can facilitate them, which is the single highest-value input available and also the one clients most often skip.
Your last few months of closed-won and closed-lost, in whatever form it exists. Patterns in who bought and who did not are more honest than anyone’s recollection of them.
## What you will have
A document of a few thousand words covering the structural profile, the psychographics, the events that trigger a buying decision, the exact words your audience uses and the words they distrust, where they actually spend attention, the objections that stall your deals, and an explicit statement of who is not your customer.
## How long it takes
About two weeks, most of which is scheduling the conversations. The writing is quick once the interviews are done.
Keeping a settled message current as the business changes.
# Messaging document
Source: https://docs.snapmarket.co/story/message/messaging-document
The master document that governs every piece of copy we write for you.
§ 1.1.1 · A1 / A2 · typically two to four weeks
## What this is
The master messaging document, built from the five core questions. It defines your voice, your value proposition, the language your audience actually uses, your differentiators, and the handful of narratives you will return to over and over.
Everything downstream inherits from it. Website copy, podcast framing, email, social, sales collateral, and the visual identity brief all cite this document, which means that when it changes, we know exactly what else needs to change. It is the single reference that keeps a year of work sounding like one company rather than eleven freelancers.
This is not a tagline exercise. A tagline may fall out of it, but a tagline arrived at without the underlying answers is a nice sentence that could belong to anyone in your category.
## What we need from you
A workshop of about two hours with the founder or executive team, ideally with one or two others in the room—whoever runs sales, whoever holds the closest relationships with your best customers. If you can get an actual customer on a call at some point in the process, that’s ideal.
Depending on complexity we may run three to five conversations rather than one, each around sixty minutes. We will tell you up front which shape yours is.
Beforehand, send us what already exists. The current site, the sales deck, the emails that get replies, any prior positioning work, and examples from the last twelve months of closed-won and closed-lost if you track it. We read all of it before the workshop so the session pressure-tests a hypothesis instead of starting from a blank page.
## What you will have
A written document, usually substantial, structured so you can hand a section of it to a new hire and have them sound like you by their second week. It covers who you are for, the category you compete in, why anyone buys in that category, what actually stands between you and a closed deal, and the one sentence that says why it is you.
Alongside that, the layered context that determines how the brand sounds rather than what it claims—tone, voice, the one or two themes you return to obsessively, and the driving force behind why the company exists at all.
## How long it takes
Two to four weeks from the workshop to an approved document. The drafting happens within a couple of days of the conversation while the language is still warm. The rest of the time is your review and one or two rounds of revision.
## What this is not
It is not a campaign brief—that is [campaign strategy](/story/strategy/campaign-strategy). It is not a twelve-month plan—that is the [go-to-market plan](/story/strategy/go-to-market-plan). And if you already have a messaging document that is directionally right and needs updating rather than rebuilding, that is a [messaging refresh](/story/message/messaging-refresh) and costs considerably less.
Question one, formalized into its own document.
# Messaging refresh
Source: https://docs.snapmarket.co/story/message/messaging-refresh
Keeping a settled message current as the business changes underneath it.
§ 1.1.2 · A1 / A2 · typically two weeks · quarterly or annual
## What this is
An update to an existing messaging document. New product line, a shift in who is actually buying, a competitor doing something that changes the conversation, or a year of performance data telling you which narratives landed and which never did.
One conversation and a rewrite, rather than the full five-question process again.
## When to reach for it
The test is whether your positioning is still directionally right. If the document still describes a company you recognize and the changes are additive—a new offering to fold in, an audience to sharpen, a claim that has stopped being true—this is the right piece.
If the document describes a company you have stopped being, this is the wrong piece. We will tell you so and propose the [full messaging document](/story/message/messaging-document) instead rather than performing a refresh on a foundation that has moved.
## What we need from you
An hour, usually with the founder or leading executive. What changed, what stopped being true, and what you have found yourself saying in sales conversations that is not in the document. That last question is often the whole meeting—the message tends to evolve in live conversation months before anyone writes it down.
If we have been running your measurement for a while, we bring performance evidence to the conversation. Which narratives got read, which posts got replies, which page people leave. It is a useful counterweight to everyone’s instinct about what’s working.
## What you will have
The updated document, with the changes visible rather than absorbed, so anyone who learned the old version can see what moved. We also flag which downstream assets now contradict the update—the website section, the sales one-pager, the podcast description—so they can be scheduled rather than discovered later by a customer.
## How long it takes
About two weeks, including your review.
## Cadence
Quarterly if the business is moving fast, annually if it is not. We will usually raise it in the monthly audit when the evidence suggests the message and the market have drifted apart.
Turning a settled message into a sequence.
# § 1.1 Message
Source: https://docs.snapmarket.co/story/message/overview
Five questions, asked in order, that settle what you say and who you say it to.
This is the foundation of the entire manuscript. Section 1.1 produces the answers that every later piece of work inherits, and it produces them through conversation rather than research. Most of the value is in the room.
The framework is adapted from Geoffrey Moore’s *Crossing the Chasm*, and it is five questions asked strictly in order.
Not your addressable market. The narrow slice of it you most want more of, described by what they believe rather than by their job title.
The category your buyer uses when they go looking, which is not always the category you use to describe yourself.
What someone in this category is trying to accomplish when they buy anything at all. Not yet about you.
The real obstacle to a closed deal, which is usually not a named competitor. Usually it is inertia, budget timing, or a bad experience with your category three years ago.
One sentence. The reason this buyer chooses you. It comes last because it can only be answered honestly after the other four.
The order is the method. Nearly every company can produce a confident answer to question five on demand, and nearly every one of those answers is a sentence a competitor could say with a straight face. Answered after the first four, it becomes something specific and defensible. A great resource on this topic is the positioning expert [April Dunford](https://fs.blog/knowledge-project-podcast/april-dunford-2/). She recommends starting from competition, so sometimes we think from that perspective to test the logic of the message.
We will spend the majority of the workshop on question one, and it will feel disproportionate while it is happening. It is not. Once the ideal client is genuinely specific, the remaining four questions largely answer themselves. Our longer argument for this lives in [Field notes](https://notes.snapmarket.co/how-to-find-your-business-story-who/).
## What this section produces
The master document. Voice, value proposition, audience language, differentiators, and core narratives.
Question one, formalized into a standalone document when the work downstream needs a sharp target.
The quarterly or annual update, once a messaging document already exists.
A hard rule we hold: no copy gets written before this section is settled. If the website copy is not landing, the problem is almost never the copy.
## A word about the uncomfortable answer
The most useful thing that comes out of a messaging workshop is usually the sentence you would never say in a sales meeting but that happens to be true. The strongest differentiators tend to be slightly costly to claim—they rule out business, they take a position, they admit a limit. If nothing in the conversation makes you a little uneasy, we have probably not gotten to the bottom of it yet, and we will keep asking.
# Story: the message
Source: https://docs.snapmarket.co/story/overview
The founder’s or executive team’s conviction, surfaced and shaped into effective marketing.
Chapter 1 answers one question in as much depth as it takes: What is the true thing this company is saying, to whom, and why should they care?
Until the message is settled, every piece of marketing you buy is a guess, and you pay for the guessing twice: once to produce it, once to redo it.
Everything downstream inherits that answer. Website copy, podcast episodes, email, the visual identity, the way your sales team opens a call—all of it is either an expression of a settled message or a series of improvisations that happen to share a logo. This is why Story comes first and why we resist starting the engine before it is done. A publishing machine pointed at an unresolved message produces a great deal of visible work that says nothing in particular, and it does so expensively.
The work here is more editorial than creative. We are not inventing a story for you. In almost every case the real story already exists, usually in the founder’s or executive team’s heads, usually in language that has never been written down because it sounds too plain to be marketing. Our job is to surface it, test it, and put it in a form that survives being repeated a thousand times by people who were not in the room.
## The three sections
Who you are for, what category you are in, and the one reason they choose you.
Turning a settled message into a sequence: what to say, where, and in what order.
How the brand looks, so that what it says and how it appears are the same claim.
## The artifact
Chapter 1 closes with the [Storybook](/story/artifact)—the canonical brand artifact holding your worldview, your audience, your differentiation, your language, and your visual system in a single place you can stand behind for years. When the Storybook exists and is approved, the chapter is finished.
## When this happens
Most of Chapter 1 is front-loaded into the first thirty to sixty days. The message work in § 1.1 comes first because § 1.2 and § 1.3 both depend on it. Strategy usually follows within the same quarter. Visual identity work runs in parallel with strategy where an identity needs building, or is skipped entirely where the existing one is directionally right and only needs sharpening.
After the first ninety days, Chapter 1 does not close permanently so much as go quiet. The message gets revisited quarterly or annually, and a new campaign or a new product line reopens § 1.2 for a few weeks at a time.
## What this chapter asks of you
More than any other chapter, and almost all of it early. Chapter 1 runs on interviews, and the quality of the output is bounded by the honesty of those conversations. After this chapter our claim on your calendar drops considerably: Chapter 2 is mostly us building, Chapter 3 is a rhythm you settle into. This is the demanding part.
### Time
About two hours for the messaging workshop, with the founder or executive team present and not multitasking. If your engagement calls for a series of interviews instead, expect three to five conversations of roughly sixty minutes. If a [go-to-market plan](/story/strategy/go-to-market-plan) is in scope, add six weekly sessions of about an hour.
Then review time: two rounds of consolidated feedback on each document, turned around inside a week. This is the single biggest lever you hold on how long Chapter 1 takes, and it is almost always the reason a four-week piece becomes a ten-week one.
### People
The founder or leading executive, or whoever actually holds the conviction the company is built on. This cannot be delegated to marketing. One named decision-maker who can approve without convening a committee—everyone can have input, one person approves. And whoever runs sales, for at least part of the conversation, because they hear the objections in real time and know which sentences make a prospect lean in.
If you can facilitate a conversation or two with actual customers, that is the highest-value input available to this chapter, and the one most often skipped.
### Material
Send whatever exists, including the version you are not proud of. We would rather see the real state of things than a tidied one, because the gap between the two is usually where the useful insight lives.
Any prior messaging work, positioning decks, brand guides, or strategy documents, even outdated ones. Knowing what you have already tried and abandoned saves us proposing it again.
Your current deck, the emails that actually get replies, and any objection-handling notes your team keeps. The sentences that work in a live conversation are frequently better than anything on the website.
Examples from closed-won and closed-lost from the last twelve months in whatever form it exists, plus a few call recordings or notes if you keep them. Patterns are more honest than recollection.
Website access, social accounts, and any analytics you have, even if nobody has logged in for a year. In fact, especially then.
Original source files if they exist, the logo in whatever formats are circulating, current templates, and a list of every place the brand appears. That list is always longer than expected.
### Posture
One thing that is harder to put on a checklist. The most useful moment in a messaging workshop is when you stop sounding like a CEO and start sounding like a person—when the polished answer gives way to the actual reason you built this.
We will keep asking the same question in different words until we get there. It can feel like we are not listening or simply asking dumb questions. We are (listening and asking dumb questions). The first answer is almost always the corporate version, the second is closer, and the third is usually the one worth building a decade of work on.
The website, the integrations, and the measurement layer that carries the message.
# Campaign strategy
Source: https://docs.snapmarket.co/story/strategy/campaign-strategy
A brief for one bounded initiative, complete enough that either team could run it.
§ 1.2.1 · A1–A4 · typically two weeks · per campaign
## What this is
The concept, channel plan, asset list, and timeline for one bounded initiative. A product launch, an event, a webinar, a fundraising push, a service line rollout—anything with a start, an end, and a thing you are trying to make happen.
## What we need from you
A conversation of about an hour, and one decision before it: what would make this campaign a success, stated as a number? Not “more awareness.” Fifty qualified demo requests by the end of Q3, or 300 registrations, or \$400,000 raised.
We will help you set the number if you do not have one, and we will push back if it is not measurable with the tools you already have. A campaign whose success is defined afterward is a campaign nobody can learn from.
We also need to know your real constraints early. The date that cannot move, the budget ceiling, the approval that takes two weeks, the executive who will want to change the headline the day before launch. Constraints named at the start shape a plan. Discovered at the end, they break one.
## What you will have
A brief of 1,000 to 2,000 words, opening with a summary an executive can read in 30 seconds.
It names the objective and how it will be measured, the audience including who you are deliberately not talking to, the one idea the campaign must plant, the channels in order and at what emphasis, every asset the campaign requires with an owner and a due date, the timeline with its dependencies, any spend or production cost, the assumptions the plan rests on, and what gets reviewed after it ends.
## How long it takes
About two weeks from the conversation to an approved brief. Execution of the assets the brief names is scoped and tracked separately, so you can approve the plan before committing to the build.
## What this is not
Not a twelve-month plan—that is the [go-to-market plan](/story/strategy/go-to-market-plan). Not ongoing channel management, which lives in Chapter 3. We do not build or run paid media campaigns ourselves. Where a campaign calls for paid, we develop the creative and the message and hand off to a paid specialist, with that cost shown separately.
Making what the brand says and how it looks the same claim.
# Go-to-market plan
Source: https://docs.snapmarket.co/story/strategy/go-to-market-plan
A twelve-month plan built with you.
§ 1.2.2 · A1–A4 · typically six weeks
## What this is
A twelve-month marketing plan: what to say, to whom, through which channels, in what order, and how you will know it is working. It sits above the campaign brief and below the messaging document—it assumes positioning is settled and turns it into a sequence.
The collaborative build is the product. We construct it with you across weekly sessions rather than disappearing for a month and returning with a document. A plan you watched get built is a plan you will actually run.
## The typical sessions
Each is about an hour, weekly, with writing happening between and after them.
Current state, honestly. What is running, what it produces, what you believe about it, and what the evidence says. This establishes the baseline everything later gets measured against.
Who you are reaching now against who you want to reach, and what has to happen between a stranger encountering you and a customer signing.
Which surfaces suit this business, this founder, and this buying journey. We will tell you when a channel is wrong for you. This session is as much about what you stop as what you start.
Twelve months in order, with dependencies made explicit. Foundational work first, because a content engine pointed at a broken website wastes the content.
What we do, what you do, what a partner does, and what nobody has time for and therefore should not be in the plan. This is where ambitious plans get honest.
What success looks like at three, six, and twelve months.
## What we need from you
A few hours of the right person’s time, spread across a few weeks, plus whatever homework each session generates—usually a number you need to look up or a question you need to ask your sales team.
The right person is whoever can actually commit the company to a sequence. If that person can only attend a few of the sessions, tell us at the start and we will restructure. A plan built with someone who cannot approve it is an expensive draft.
## What you will have
A single substantial document, structured so you can find one section a quarter later rather than rereading the whole thing.
It covers your current state and baseline, your audience and buying journey, the channel strategy including what got ruled out and why, the twelve-month sequence with phases and dependencies, who owns what, and the measurement plan with its review cadence.
## How long it takes
Several weeks, paced by the sessions.
## What this is not
Not a single campaign brief—that is [campaign strategy](/story/strategy/campaign-strategy), and if you only need the next three months, two or three campaign briefs will serve you better and cost less. Not the messaging document. If positioning is unsettled, we build that first, because a plan on top of an unresolved message is a schedule for saying something you have not yet decided.
# § 1.2 Strategy
Source: https://docs.snapmarket.co/story/strategy/overview
Turning a settled message into a sequence: what to say, where, and in what order.
Section 1.1 settles what is true. Section 1.2 decides what to do about it.
Strategy here means sequence more than it means ambition. Almost every company we work with already has a list of things they could be doing, and the list is not the problem. The problem is that the list has no priorities, no order, no dependencies, and no honest account of who has time to do any of it. A plan that says do all of this is indistinguishable from no plan at all.
So the work in this section is mostly the work of putting things in order and ruling things out. What has to be true before the next phase can start. Which channel suits this business and this founder, and which one everyone likes the idea of but nobody will sustain. What you should stop doing, which is usually the most valuable sentence in the document.
## Two pieces, two scales
Twelve months, built with you across weekly working sessions. The year that contains the campaigns.
One bounded initiative—a launch, an event, a webinar, a fundraising push. Two weeks to a brief.
The distinction is scope, and it matters for what you should ask for. If the question is “what should we be doing this year,” that is the go-to-market plan. If the question is “how do we launch this in March,” that is a campaign strategy, and if you have three such questions you probably want three campaign briefs rather than a year-long plan.
## Both are built with you, not for you
This is the part of our method that differs most from what you may be used to. Strategy documents delivered cold get read once and filed, no matter how good they are, because nobody in the building watched the reasoning happen and therefore nobody can defend the plan when the first budget conversation arrives.
So we build these in working sessions with you in the room. It takes longer and it is a real claim on your calendar. It is also the difference between a plan you run and a plan you own a copy of.
Both pieces assume the message is settled. If § 1.1 is not done, a strategy built on top of it is a sequence for delivering an unresolved claim, efficiently. We will say so rather than proceed.
## What every plan we write includes
Every recommendation carries its reasoning, so you can defend it internally without us in the room. Every phase has a named owner and a rough date. And the measurement is defined before the work starts rather than retrofitted to whatever happened, because a metric chosen after the fact is a story, not evidence.
# Brand identity development
Source: https://docs.snapmarket.co/story/visual-identity/brand-identity
A full visual identity system, built from the message outward.
§ 1.3.1 · A1 / A2 · typically four weeks
## What this is
The complete visual system: a logo suite, a color palette, a typography selection, written visual guidelines, collateral templates, and a brand guide document that holds all of it together.
It is the foundational design asset. Every piece of creative work that follows—the website, the podcast artwork, the sales one-pager, the social templates—inherits from it, which is why building it before the website rather than during is worth the wait.
## What we need from you
A settled message. This is the real prerequisite, and it is not a formality. The brief that drives the design is written directly out of the messaging document, so if § 1.1 is unfinished, the design work becomes a series of educated guesses about a personality nobody has decided on.
One named decision-maker with actual authority. Identity work is the single most opinion-attracting thing we do, and it is where approval-by-committee does the most damage. Everyone can have input. One person approves.
An honest inventory of where the brand has to live. Every place a logo currently appears, every template someone maintains in a spreadsheet, every piece of letterhead. The list is always longer than anyone expects, and finding out in week four is expensive.
A few hours of review time at defined points, with feedback consolidated rather than trickling in.
## What you will have
A logo suite covering the primary mark, secondary lockups, and an icon, in the file formats each context needs. A defined palette with each color’s intended role. A typography system with hierarchy rules. Written guidelines showing how the system behaves and how it breaks. And templates for the things you make most often—presentation, letterhead, social, whatever the inventory turned up.
## How long it takes
About four weeks of design work once the brief is approved, though the calendar time depends more on your review turnaround than on ours. Two rounds of consolidated feedback keeps this to four weeks.
## Costs that sit outside our fee
Typeface licensing, trademark searching, stock or mockup assets, and print proofing are billed at cost and quoted separately. Typeface licensing in particular is worth knowing about early, because it scales with how many people and platforms will use the fonts.
## What this is not
Not a refresh of an existing identity—that is a [brand refresh](/story/visual-identity/brand-refresh), which costs considerably less. Not a website build, though the identity governs it. The site comes later, in Chapter 2, and goes much faster for having this in place.
# Brand refresh
Source: https://docs.snapmarket.co/story/visual-identity/brand-refresh
Tightening an identity that is directionally right so the work downstream has a foundation.
§ 1.3.4 · A1 / A2 · typically one to two weeks
## What this is
A scoped pass over an existing identity to bring it up to standard. Specifications written down, the palette settled and documented, typography made consistent, and templates rebuilt so the next twelve months of work has something solid to stand on.
This is the piece most companies actually need. The identity is usually fine. What is missing is the discipline around it—the file nobody can find, the four logo variants in circulation, the deck template that drifted, the hex code that is slightly different on the website than in the pitch deck.
## When it is the right piece
The test is whether the existing brand is directionally right and needs sharpening, or wrong and needs replacing.
Directionally right means you look at it and recognize the company, even if the execution is loose. Wrong means it represents a business you have stopped being, in which case sharpening it just makes the wrong thing sharper, and we will say so and propose the [full identity](/story/visual-identity/brand-identity) instead.
This is not a logo redesign. If the mark itself is the problem, this is not the piece.
## What we need from you
Everything you have, including the messy parts. The original design files if they exist, the current logo in whatever formats are floating around, the deck someone rebuilt from scratch last year, the website’s actual colors rather than the ones in the old brand guide.
And a short list of what you actually make. We rebuild the templates you use, not a comprehensive set you will never open.
## What you will have
Updated specifications, a documented palette and typography system, and clean templates for the formats you use most. Enough that a new hire, a contractor, or a printer can produce something on-brand without asking anyone.
## How long it takes
One to two weeks. It is deliberately a bounded pass rather than an open-ended improvement project, which is what keeps it a fraction of the cost of a full identity.
Art direction and coordination for brand shoots.
# § 1.3 Visual identity
Source: https://docs.snapmarket.co/story/visual-identity/overview
Making what the brand says and how it looks the same claim.
A brand that sounds careful and looks careless is making two claims, and people believe the second one. Visual identity sits inside Story rather than alongside it because how a company looks is part of what it says, not a decoration applied afterward.
Which is also why this section comes after § 1.1. A visual identity built before the message is settled is a designer guessing at a personality that has not yet been decided. Once the message exists, the design brief nearly writes itself—the adjectives are already in the messaging document, and the audience research already described what this particular buyer trusts.
## What this section can produce
A full identity system built from scratch: logo suite, palette, type, guidelines, and templates.
Tightening an identity that is directionally right so downstream work has a solid foundation.
Art direction and coordination for brand shoots. We direct, specialists shoot.
## Which one you need
The question is not whether your current identity is good. It is whether it is pointing in the right direction.
If it is directionally right and simply inconsistent—four versions of the logo in circulation, a palette nobody wrote down, decks that each invented their own typography—that is a [refresh](/story/visual-identity/brand-refresh), and it is a fraction of the work.
If it is pointing somewhere the company no longer is, sharpening it makes the wrong direction sharper. That requires a [full identity](/story/visual-identity/brand-identity). We will tell you which one we think you have, and we are more often arguing for the refresh than against it.
## How the work is split
We write the brief, our design lead executes it in Figma, and you review at defined points rather than continuously. The brief covers brand personality with a visual definition for each adjective, where the brand sits between minimal and expressive and between classic and modern, color and typography direction, imagery direction, and a set of explicit do-and-don’t pairs so that “make it feel warmer” has a shared meaning before anyone opens a file.
The pattern that wastes the most time in design work is feedback arriving as adjectives with no shared referent. The brief exists to prevent that, and the review points exist so you are never surprised by a direction three weeks after it was set.
Photography and video are coordination pieces. We art direct, source the specialist, and oversee the shoot if needed. The photographer or crew is contracted directly and billed at cost, always quoted separately so you can see what is our time and what is theirs.
# Brand photography and video
Source: https://docs.snapmarket.co/story/visual-identity/photography-and-video
We art direct and coordinate. Specialists shoot, and their cost is always quoted separately.
§ 1.3.2 and § 1.3.3 · A1 / A2 · photography typically four weeks · video typically four to six weeks
## What this is
Art direction and coordination for brand imagery. For photography, that means developing the shot list, setting the creative direction, sourcing and selecting the photographer, and coordinating the location if needed. For video, it means concept development, scripting, team selection, and oversight through post-production.
We are direct about the boundary: Snapmarket does not shoot. What we do is make sure the person who does arrives with a brief that is actually derived from your message, rather than a vague request for “some good photos of the team.”
That matters because the most common failure in brand imagery is not technical. It is a shoot that produced beautiful pictures of the wrong thing, discovered six months later when nothing in the library fits the website.
## How the money works
Our fee covers coordination and art direction only. The photographer, videographer, and crew are contracted and billed to you at cost, and we always quote their fee separately so the two numbers never blur together.
The specialist’s fee is typically the larger of the two numbers, and it varies considerably with complexity, so we scope it per shoot rather than quoting a range that would be wrong for most projects. Styling, hair and makeup, location fees, permits, and music licensing are additional and quoted as they arise.
## What we need from you
Availability, which is usually the hard part. A shoot needs the right people in the right place on one specific day, and coordinating five executives’ calendars takes longer than everything else combined. Start early.
A decision on what the imagery is for. A library that has to serve the website, the podcast, social, and a sales deck is a different shot list than one for a single campaign. We would rather over-shoot deliberately than discover the gap later.
Someone on your side who can make calls on the day. Shoots generate small decisions constantly, and waiting on approval burns paid hours.
## What you will have
A shot list and creative direction before the shoot, the coordination through it, and a reviewed, selected, and delivered set of final assets afterward—organized and named so your team can find the right image without opening forty files.
## What this is not
Not editing existing footage, which is a Chapter 3 piece. Not ongoing content photography. This is the foundational library that the rest of the manuscript draws from.
The capstone that closes Chapter 1.
# Analytics setup
Source: https://docs.snapmarket.co/system/analytics/analytics-setup
The tracking layer a website needs to answer who arrived, from where, and what they did.
§ 2.3.1 · typically one to two weeks · one-time
## What this is
Configuration of the analytics layer your website needs: property setup, tag management, and conversion tracking on the actions that matter—form submissions, calls booked, downloads taken.
It is a small piece of work with an outsized dependency behind it. Nothing in the Scale layer can say anything until this exists and is verified, and “verified” is doing real work in that sentence. Analytics that are installed but firing incorrectly are worse than none, because they produce numbers people trust.
## What verified means
Every event tested end to end, tags named consistently, internal traffic filtered out so your own team does not inflate your numbers, and thirty consecutive days of the dashboards pulling without errors.
We do not consider this piece finished at installation. We consider it finished when the data has been clean for a month, because that is the point at which it can be built on.
## What we need from you
Admin access to your existing analytics properties, including the ones nobody has opened in years. We would rather inherit and clean up a messy history than start fresh and lose the comparison.
A list of the office IP addresses to filter, so internal traffic stops counting as audience.
Agreement on what counts as a conversion. This is a shorter conversation than it sounds and it prevents a long one later, when somebody asks why the number on the dashboard does not match the number in the CRM.
## What you will have
Working analytics in accounts you own, with conversion tracking on the actions you care about, internal traffic excluded, and a written note of every exclusion and definition applied—so a year from now anyone can see exactly what a number does and does not include.
## What this is not
Not the full measurement build. Cohorts, transition rates, and the reporting spine the monthly audit reads from are [Scale setup](/scale/overview), which is a separate and larger piece. Not the recurring monthly report, which is [performance reporting](/system/analytics/performance-reporting).
# § 2.3 Analytics
Source: https://docs.snapmarket.co/system/analytics/overview
Where the Scale layer gets its instruments, built once and running continuously.
This is the section where measurement becomes possible. The [Scale layer](/scale/overview) is a practice that runs for the life of the partnership, but its instruments get installed here, once, inside Chapter 2.
The distinction is notable. § 2.3 is the tracking a website needs in order to answer basic questions—who arrived, from where, and what did they do. Scale’s own setup is the layer above it: cohorts, transition rates, and the reporting spine the monthly audit reads from. They are separate builds.
## What this section produces
Property configuration, tag management, and conversion tracking.
The standing monthly report. What the instruments read, gathered in one place.
Technical review, keyword research, and hands-on optimization of the pages that matter.
## What we are and are not
We are translators, not a data science team. Our job is to make your data legible, not to invent more of it.
In other words, we do not build multi-touch attribution models or anything requiring data-science tooling, and if you ask for attribution modeling we will redirect you to a five-minute conversation at every closed deal instead—where did this customer first encounter you, what specifically prompted them to reach out, what was the last step before signing. For a business closing fifty to a hundred customers a year, that retro is more honest than a model and far cheaper to maintain.
What we are good at is taking messy data from six platforms and turning it into a clear account of what is working, in language you can take to a board meeting without a translator.
## Track everything, once
One piece of discipline that pays for itself repeatedly: every link the team produces carries consistent tracking parameters, from the first day of the partnership.
It costs nothing at the time. Without it, six months later you have traffic you cannot attribute and a question you cannot answer, and there is no retroactive fix. This is the kind of thing that is invisible when done and irreversible when skipped.
# Performance reporting
Source: https://docs.snapmarket.co/system/analytics/performance-reporting
The standing monthly report. Every partner, every month.
§ 2.3.2 · continuous · recurring monthly
## What this is
The standing monthly report. We pull the data, check it, and send it. Every partner, every month, without being asked.
It covers traffic, engagement, conversions, channel performance, and movement against the prior period—the state of the instruments, gathered in one place so nobody is logging into six platforms to assemble a picture.
## Where the interpretation happens
Not here. This report is the evidence; the [monthly thesis review](/method/thesis) is where we say what we think it means and what we propose to do about it.
We keep them separate deliberately. A number arriving with a narrative already attached is hard to argue with, and you should be able to look at the evidence before you hear our reading of it.
## What you will get
A report you can forward to your board without translating it first. Prose alongside the numbers, the trend rather than the isolated figure, and an explicit note wherever a number isn’t trustworthy yet—a tracking gap, a partial month, a change that broke comparability.
During the [baseline period](/scale/baseline), it covers instrumentation health only and makes no quantitative claims. We say so on the page rather than filling the space with numbers that can’t yet mean anything.
## What we need from you
Almost nothing, which is the point. It arrives whether or not you ask.
The one thing worth doing is telling us when something outside marketing moves—a pricing change, a new salesperson, a large customer signed through a personal relationship. Bring your questions to the monthly review, where there is time to answer them properly.
# SEO audit and optimization
Source: https://docs.snapmarket.co/system/analytics/seo
Technical review, keyword research, and hands-on work on the pages that matter.
§ 2.3.3 · A1 · four weeks for a scoped audit, a quarter for a full technical audit plus optimization
## What this is
A technical review of how search engines see your site, keyword research grounded in the language your buyers actually use, content gap analysis, and hands-on optimization of your highest-value pages.
A scoped audit answers one question—why is this section not indexing, or which terms should this page be competing for—and runs about four weeks. A full technical audit plus optimization is a quarter of work, and it goes deeper into site structure, internal linking, and a page-by-page pass over what matters most.
## The keyword work is downstream of the message
This is the part most SEO work gets backwards. Keyword research that starts from search volume produces a list of terms with traffic behind them and no relationship to who you want to reach.
Ours starts from your [ideal client profile](/story/message/ideal-client-profile)—the words that audience actually uses, which is often not the words your industry uses about itself. A term with modest volume that your exact buyer types is worth more than a high-volume term that brings you people who will never buy.
## Search is slower than everything else
Worth saying plainly. Changes made in month one commonly show up in month four or later, and there is no version of this work where that is not true.
This is why search sits inside the Scale layer’s lagging indicators rather than its leading ones, and why we would rather set the expectation at the start than manage a disappointment in month two.
## What we need from you
Search Console and analytics access, and patience of a specific kind—a willingness to let a change sit long enough to be judged.
Where optimization touches copy, a reviewer who can approve changes to page text reasonably quickly. Recommendations that sit unimplemented are the most common way this work fails to produce anything.
## What sits outside the fee
Research tooling subscriptions, billed at cost, and only where the scope requires them.
## What this is not
Not general [performance reporting](/system/analytics/performance-reporting). Not paid search, which we do not run.
# The live website
Source: https://docs.snapmarket.co/system/artifact
Live, indexed, and wired to measure. All three, or the chapter is not finished.
Chapter 2 closes when your website is live, indexed, and integrated with publishing and measurement.
Three conditions, and we hold all three. A site that launched but does not appear in search has not finished the chapter. A site that launched and ranks but cannot tell you who arrived or where they came from has not finished it either, because everything the Scale layer does for the next several years depends on that instrument being in place before the traffic starts.
## What each condition means
**Live** is the obvious one. The site is public at your domain, responsive, tested, and editable by your team.
**Indexed** means search engines can find and read it. Search Console verified, sitemap submitted, no accidental blocks left over from the staging environment. This last one is the classic failure—a site that spent six weeks correctly hidden from search and then launched with the hiding still switched on.
**Integrated** means the forms go where they should, the email platform is connected, and analytics and conversion tracking are firing correctly and have been verified rather than merely installed.
## Why this is the artifact
Because it is the one asset you own outright, and because it is the moment the engine becomes real.
Everything in Chapter 3 assumes it. A podcast needs somewhere for a listener to land. A newsletter needs somewhere to send people. A campaign needs a page that converts and reports. Publishing into a world with no destination is the most expensive mistake available in marketing, and it is common, because publishing feels like progress in a way that infrastructure does not.
## What it does not mean
It does not mean the site is finished forever. Sites are living things and § 2.1 keeps producing updates and landing pages for as long as the partnership lasts.
It also does not mean measurement can yet tell you anything. The instruments exist from launch, but they need sixty to ninety days of clean data before any claim about improvement means something. The [baseline period](/scale/baseline) explains why, and it is worth reading before the first month where you want a number.
The disciplined act of putting work into the world, on schedule, over years.
# § 2.2 Integrations
Source: https://docs.snapmarket.co/system/integrations
The plumbing between the tools you already run.
§ 2.2.1 · A3 / A4 · typically one week per integration
## What this is
CRM setup, email platform configuration, form handling, third-party tool connections, and the automations that route information between them. The plumbing.
It is the least visible work in the manuscript and the most consequential when it is missing. A form that submits into nothing, a lead that arrives in an inbox nobody watches, a newsletter list that never syncs with the CRM—none of these look like problems on a dashboard. They look like a marketing operation that’s not working.
## The principle we hold
Fewer tools, used properly, rather than more tools.
The stack we standardize on covers what nearly every partner needs, and the work is almost always rigor rather than addition. When a partner asks for a new platform, the first question is whether the thing they want is already possible in something they are paying for. Frequently it is, and the honest answer saves them a subscription and a migration.
Where you already run something that works, we integrate with it rather than replacing it. Migrations are expensive, disruptive, and not always the actual solution to the problem that prompted them.
## What actually delays this
Not the build. Credentials.
The reliable pattern is that a one-week integration takes three weeks because admin access to two systems has to be tracked down—one owned by a person who left, one requiring a plan upgrade nobody knew about, one where the only admin is on holiday. We ask for access at the start of the project rather than at the point we need it, and it is worth treating that request as urgent even though it does not feel it.
## What we need from you
Admin credentials, or an admin who can act, for every system in scope. Not a shared login where possible—proper access with your own audit trail.
A decision about who owns each account, where it is not already settled. The rule we work to is that anything representing you in the world stays registered to you with us added as users, and anything that is production tooling sits on our subscriptions unless you already hold a license. [The tools we use](/method/tools) sets that out in full.
A clear statement of what should happen when a lead arrives. This sounds obvious and is the question that most often surfaces an unresolved internal disagreement. Who is notified, how quickly, and what are they supposed to do.
## What you will have
Working connections, documented—what talks to what, what triggers what, and where to look when something stops. Written down rather than held in someone’s head, because an undocumented automation is a liability the moment its author is unavailable.
## Where each tool lives
Which platform does what, who owns the account, and which ones you will ever log into are all set out in [the tools we use](/method/tools). If you are trying to work out where something lives or how to get access to it, start there rather than here.
## What this is not
Not analytics setup, which is [§ 2.3](/system/analytics/overview). Not email marketing execution, which lives in Chapter 3. Connecting your email platform to your CRM is this piece, and it is very often the hidden second half of an email automation project.
# System: the engine
Source: https://docs.snapmarket.co/system/overview
The technical infrastructure that turns one true thing into a thousand visible ones.
Chapter 1 settles what is true. Chapter 2 builds the thing that carries it.
Most of what looks like a marketing problem two years into a partnership turns out to have been an infrastructure problem the whole time. That’s because in order to publish and measure marketing effectively, you need a website, the connections between the tools you already run, and the measurement layer underneath everything.
Aside from the website, this chapter is the least romantic part of the build but it’s the one that determines whether the next year of publishing produce anything you can point to. A story with no engine behind it stays in a document.
The framing that matters here is faithfulness. Everything built in this chapter exists to take one settled message and reproduce it accurately across a thousand small surfaces—a page, a form, a confirmation email, a tracking parameter on a link somebody clicked at ten at night.
## The three sections
The site itself, the pages that follow it, and the domain and hosting underneath.
The plumbing between your CRM, your email platform, your forms, and everything else.
The tracking layer, the recurring reporting, and search visibility.
## The artifact
Chapter 2 closes with a [website](/system/artifact) that is live, indexed, and wired to measure. All three conditions, not just the first. A site that launched but does not appear in search, or launched but cannot tell you who arrived and from where, has not finished the chapter.
## When this happens
Chapter 2 typically lands in months two through five, depending on the size of the build. The website is the long run and the one with the most review cycles in it.
There is an important exception. If you arrive with no CRM and no real analytics, we will often pull § 2.2 and § 2.3 ahead of the website. Instrumenting is cheaper and faster than designing, it does not wait on approval cycles, and it starts the measurement baseline in week two instead of month five.
After the artifact, § 2.1 becomes a steady trickle of updates and landing pages, § 2.2 gets touched whenever your stack changes, and § 2.3 runs continuously for the life of the partnership.
## What this chapter asks of you
Less of your time than Chapter 1, and more of your patience.
The two things that reliably delay this chapter are both administrative. Credentials for third-party systems—the reliable delay in an integration project is almost never the build but rather the waiting on admin access to two platforms nobody remembers the password for. Add to that review turnaround on the website, where scattered feedback across many rounds is what turns a six-week build into a five-month one.
A note on calendars. Domain and DNS work carries mandatory waiting periods that no amount of urgency shortens—sometimes servers need a few days to publish a site.
Putting the work into the world on a schedule, and the artifact that closes it.
# Website design and build
Source: https://docs.snapmarket.co/system/website/design-and-build
The full project, from information architecture through launch.
§ 2.1.1 · A1 / A2 / A3 · typically six to eight weeks
## What this is
A complete website project: information architecture, wireframing, design, build, content population, quality assurance, responsive testing, and go-live coordination.
It is scoped by template page rather than by total page count because that is what actually drives the work. A homepage is its own design problem. A services page and a second services page are one design problem and two sets of content. A resources index and a resources detail page are two templates even though they feel like one section.
We will walk you through the template count before we scope.
## What we need from you
A settled message. This is the real prerequisite. Website copy is downstream of the messaging document, and building a site while positioning is still moving means writing the same three pages four times.
A named reviewer and a consolidation plan. Everyone can have input. One set of comments comes back to us per round.
Content that only you have—team bios, headshots, client logos and the permission to use them, case study details, legal and compliance language. This is the single most common cause of a site sitting finished but unlaunched, and it is worth starting on in week one rather than week six. We can provide a base draft of a Privacy Policy and Terms of Service, which we will implement for a cookie consent banner, but your team—particularly your legal team—needs to review and sign off.
Access to your domain registrar, which frequently takes longer to locate than anyone expects.
## What you will have
A live site you own and can edit, built responsively and tested across devices, with analytics and conversion tracking wired in before launch rather than after. Search Console verified and the sitemap submitted, so indexing starts immediately.
And a short handoff session with whoever on your team will be making small changes, because a site nobody but us can edit is a site that can go stale.
## How long it takes
Six to eight weeks for a build of typical size, paced by review turnaround more than by production.
## What this is not
Not a single page added to an existing site, and not a campaign page—both are [updates and landing pages](/system/website/updates-and-landing-pages). If an update grows into restructured navigation or a new template system, it has become this piece and we will say so rather than absorb it.
# Domain and hosting
Source: https://docs.snapmarket.co/system/website/domain-and-hosting
Small effort, long calendars. The infrastructure nobody thinks about until it breaks.
§ 2.1.4 · typically one week of work, but see the calendar note below
## What this is
DNS configuration, SSL, hosting coordination, domain registration and renewal, email routing and deliverability records, and a written inventory of what exists and where.
That last item is the one clients end up most grateful for. A surprising number of companies do not know which registrar holds their domain, who has admin access, or when it renews, and the moment that becomes urgent is always the worst possible moment.
## The calendar warning
The effort here is small. The calendar is not, and it is not negotiable.
A registrar transfer carries a mandatory five-day window that nobody can shorten. DNS propagation adds time on top of that. Email deliverability records need to settle before you can trust that sends are landing.
So we never schedule a launch tightly against domain work, and we would ask you not to promise a date to anyone else that depends on it. When a launch slips for this reason it is almost always because the domain work started too late, not because it went wrong.
## Email deliverability
If your domain’s authentication records are absent or misconfigured, a meaningful share of everything you send—newsletters, sequences, and sometimes ordinary sales email from your own team—lands in spam or never arrives. It is invisible from your side. You see sends going out and no bounce, and you conclude the audience is not interested.
## What we need from you
Access to the registrar or domain hosting service (e.g., GoDaddy, Namecheap, etc.), which usually means finding out who set it up. If that person left the company three years ago, tell us early and we will work through the recovery process, which is itself slow.
## What sits outside the fee
Domain registration and renewal, and any email workspace seats, stay in your name and on your card. The website platform itself runs on our subscription for the life of the partnership—see [the tools we use](/method/tools) for where that line falls and what happens to it at the end.
# § 2.1 Website
Source: https://docs.snapmarket.co/system/website/overview
The one asset you own outright, and everything that keeps it current.
Your website is the only significant marketing asset you fully own. Every other surface is rented—a platform can change its algorithm, its terms, or its mind, and your audience there goes with it. This is why the website is Chapter 2’s artifact rather than one item among several.
It is also the place where a settled message either survives contact with reality or does not. A messaging document that reads beautifully and then produces a homepage nobody can navigate has not actually been settled. The site is the first honest test.
## What this section produces
The full project, from information architecture through launch.
The ongoing work after launch, and single-purpose pages built for one campaign.
DNS, SSL, email deliverability, and the infrastructure inventory.
## What we build in
[Framer](https://framer.com), by default.
The reasoning is not fashion. Framer sites are fast to build, fast to load, and—critically—editable by your team without a developer. A site that requires us for every copy change becomes a bottleneck.
## The thing that decides the timeline
Website projects run long for one reason more than any other, and it is not design. It is review structured as a stream of individual reactions rather than a small number of consolidated responses.
Two rounds of feedback, each gathered from everyone who has an opinion and delivered as one document or set of comments, keeps a build to six or eight weeks. The same total volume of feedback arriving as forty messages across nine weeks does not produce a better site.
We will ask you at the start who the reviewers are and how feedback will be consolidated. It is worth answering carefully.
# Updates and landing pages
Source: https://docs.snapmarket.co/system/website/updates-and-landing-pages
The ongoing work after launch, and single-purpose pages built for one campaign.
§ 2.1.2 and § 2.1.3 · A2 / A3 · updates typically one to two weeks · landing pages typically one week
## Website updates
Discrete changes to a site that already exists. New pages, copy updates, image swaps, layout adjustments, bug fixes, publishing a post, or a small feature addition.
This is the steady, unglamorous work that keeps a site from going stale, and it is where most of Chapter 2’s ongoing hours go after launch. A single new page is a small piece. A multi-page rollout is a real project and we scope it as one rather than absorbing it, because absorbing it is how a month’s capacity disappears into work nobody planned.
If an update turns out to require restructured navigation or a new template system, it is a [build](/system/website/design-and-build) wearing an update’s clothes. We will flag that before starting, not halfway through.
## Landing pages
A standalone page built for one campaign, event, offer, or lead generation push. One objective, one call to action, tracking wired in from the start.
The distinction from a normal new page is intent rather than effort. A services page is part of the site’s permanent structure and has to work for every visitor. A landing page exists to convert one audience on one thing, and everything that would help a general visitor—navigation, alternative paths, related content—doesn’t always help it.
Because of that, a landing page is only as good as the campaign brief behind it. If there is no [campaign strategy](/story/strategy/campaign-strategy) naming the audience, the message, and the success number, we would rather write that first than build a page nobody can evaluate afterward.
## What we need from you
For updates, the actual content and a clear statement of what should change. “Make the team page better” generates questions back to you. “Replace these three bios with the attached and remove the fourth” does not.
For a landing page, the offer, the audience, the deadline, and where the traffic is coming from. That last one shapes the page more than anything else on the list.
## How long it takes
A single update runs one to two weeks. A landing page runs about a week from an approved brief. Both move faster when the content arrives with the request rather than after it.