When someone reliable gives you this kind of feedback, you now have some true sense of your work’s effect on people, and you may now know how to approach your final draft. If you are getting ready to send your work to a potential agent for the first time, you don’t want to risk burning that bridge by sending something that’s just not ready.

Your product’s story is its design, its features, images and videos, quotes from customers, tips from reviewers, conversations with support agents. It’s the sum of what people see and feel about this thing that you’ve created.

And the story doesn’t just exist to sell your product. It’s there to help you define it, understand it, and understand your customers. It’s what you say to investors to convince them to give you money, and to new employees to convince them to join your team, and to partners to convince them to work with you, and to the press to convince them to care. And then, eventually, it’s what you tell customers to convince them to want what you’re selling.

And it all starts with “why.”

Why does this thing need to exist? Why does it matter? Why will people need it? Why will they love it?

The best way to do that is with a compelling story. And knowing your audience. Even in Silicon Valley, most VCs won’t be technical. So don’t focus on the technology, focus on the “why.” [See also: Chapter 3.2: Why Storytelling.]

If you want to build a great company, you should expect excellence from every part of it. The output of every team can make or break the customer experience, so they should all be a priority. [See also: Chapter 3.1: Making the Intangible Tangible.]

There can’t be any functions that you dismiss as secondary—where you casually accept mediocrity because it doesn’t really matter.

Everything matters.

And it’s not just about you.

After your product launch, and hopefully with revenue coming in, your board meetings will focus more on data and what’s happening externally—what’s the competition doing, what are customers asking for, how well are we attracting and retaining customers, what kinds of partnerships have you set up. And as always when you’re presenting numbers, it becomes much more important to craft a narrative. You have to tell a story. [See also: Chapter 3.2: Why Storytelling.] Your board isn’t in the business every day like you are—they can’t immediately understand the nuances or what the numbers actually mean unless you give them context.

Being able to help the board grasp exactly what’s going on is good for the CEO, too. The better you can explain something, the more you understand it. Teaching is the best test of your own knowledge. If you’re struggling to explain what you’re building and why, if you’re presenting a report without really understanding it, if the board is asking you questions that you can’t answer—then you have not internalized what’s actually going on at your company.