Nobody Cares About Your Process

Here's what buyers are actually paying for.

In 2009, I was one of the founders and Chief Creative Officer of EPIX, the first direct-to-consumer premium streaming service built from the ground up with a digital-first vision. MGM, Lionsgate, and Paramount had come together to build something the industry didn’t yet have a naming convention for. (The term Streaming would be coined later.) We were not improving an existing model. We were trying to invent one.

The video player we were building had no real predecessor at this level. We wanted dynamic ad insertion that came across as native rather than intrusive, session shifting so a viewer could start watching on a laptop and finish on a television without losing their place, and a shared screening room, something like Mystery Science Theater 3000 brought into the streaming era, where watching a film became a social experience you could share with someone across the country, all wrapped in a slick UX/UI design. These weren’t features on a roadmap. They were a vision for what premium streaming could feel like to a human being at eleven at night on a couch.

Then the agencies came in.

Agency after agency sat across the table and told us about agile methodology, about scrum, about their tech stack, design process, and approach to budget and scope management. Thorough and professional, their decks showed exactly how they worked.

Nobody told us WHY them.

Nobody walked in and said: Here is what you are actually trying to build, here is what it could become if done right, here is the one decision that will determine whether this works or becomes another feature nobody uses, and here is why we are the people who should stand between you and that outcome.

They described their process and never made a claim about the result.

The air got sucked out of those conversations to the point of suffocation, and I have been watching the same thing happen in agency pitches ever since.

The Trap Founders Walk Into

Most creative agencies learn to sell by demonstrating competence through methodology. By showing the buyer they have a system, a framework, and a well-defined approach to the work. This feels safe, but it is also a kind of slow surrender.

Process language protects the founder from being held to a definitive commitment. You can describe a five-step discovery framework without promising an outcome. You can walk someone through your sprint cycles without staking a claim on what will be different about the business when the work is done. The methodology is defensible. The result is yours to worry about later.

Founders often don’t consider how process language affects buyers.

I have sat through hundreds, maybe thousands of pitches. I have seen the same discovery phase described seventeen different ways. It is, in all seventeen cases, the same discovery phase: stakeholder interviews, competitive audit, brand assessment, a workshop somewhere in the middle, findings delivered in a deck. The founder presents this as a differentiator with heartfelt pride. The buyer nods and thinks about lunch and checking their phone.

One founder I mentor described it perfectly. “When I talk about what I do in a real conversation, she said, I feel passionate. When I write it down, it sounds like everyone else.”

She had stated the problem without fully seeing it. Her conviction lived in the spoken word. Her process lived in the document. The document was what buyers saw first.

The Three Questions Already Running

When a founder describes their process in a pitch, a buyer is running three questions simultaneously. They are never in the RFP, yet they shape everything.

1. What is different about your process than everyone else’s?

   Every agency has a discovery phase, a creative brief, a revision cycle, and a delivery framework. If process is the differentiator, it needs to be unreplicable. Most are not. Are you a PMP or a creative director? Right now, you sound like the former.

2. Will your process make me money?

   The buyer is not purchasing a workflow. They are purchasing a consequence. If you cannot connect your methodology directly to an explicit business outcome, you have described the vehicle without mentioning its destination.

3. My internal team has better tools and processes than most agencies we see. Why do I need you?

   If the value lives in tools and process, an internal team wins on familiarity with the brand, velocity, and institutional knowledge every time. The CFO is not wondering if your Notion workspace or Monday board is better than theirs. It probably is not, since the internal team has corporate budgets funding it and a herd of employees powering it. The only answer that survives this question lives above that entirely.

What Was Actually For Sale

Execution is the cost of entry. Every agency executes. Competitors deliver the same categories of work in their own ways, some of them well. What was never in question at EPIX was whether the agencies pitching us could execute. What was in question was whether any of them understood what we were actually trying to build and why it mattered, whether any of them had thought past the sprint plan to the experience we were trying to create for a person sitting on that couch at eleven at night wanting to share something they loved with someone they missed.

They stayed in the methodology because it felt safer than making a claim.

Process is a record of what worked before. When there is no before, you are bringing judgment or you are bringing nothing.

The agency that earns the business in a moment like that is the one that makes the buyer feel, before anything is signed, that something concrete and important will be different because of this relationship. That the people across the table have been here before, have seen what goes wrong, and have a strong opinion about what this should become and why it matters.

That is a claim. A defined, uncomfortable, outcome-oriented claim that puts the agency on the hook for something tangible. Most agencies are not willing to make it because making a claim means risking being wrong. Being wrong means losing. Staying in the methodology feels safer. It is also why so many pitches close with the buyer choosing someone else, and nobody quite understands why.

The Distance Between Two Sentences

Execution language sounds like this: we start with a comprehensive discovery phase where we audit your existing technical architecture, conduct stakeholder interviews across your product and engineering teams, and map your competitive landscape prior to moving into sprint planning.

Read that again seven times. Then imagine the pain of hearing it from seven different agencies in the same week while trying to build something that has never been built before.

Strategy language sounds like this: most platforms building this kind of feature underestimate the session handoff problem. They solve the technical question and miss the human one. We have shipped something like this before, and here is what we learned about where viewers actually lose interest, and here is how we would build around that from the start.

One of those sentences could belong to any agency. The other could only belong to you if it is true, if you have actually done this, if you have actually seen what you are claiming to have seen. That is the standard. Not a better framework or an elevated methodology. The willingness to make a real claim about what you know and what will be different because of it.

Thirty years behind the desk as a buyer taught me one thing about what wins the work. It was never the process. It was the moment when someone looked across the desk and said something distinct enough to be wrong, measurable enough to demonstrate they had been there before and had an authentic opinion about what mattered, and nuanced enough to make the buyer feel, for the first time in a long day of presentations, that they were finally talking to someone who understood what they were trying to build.

When was the last time you said something in a pitch that could have been wrong?