The Story Arc

Brochures vs. Narratives

Open any B2B SaaS homepage and you will probably find the same skeleton: hero section with headline, feature grid, logo bar, testimonial block, call to action. That is a brochure. It is organized by content type, not by argument. And it is what the vast majority of SaaS companies build when they redesign their homepage.

A narrative page does something different. It moves visitors through a progression. It starts with a problem the buyer recognizes, agitates it so the reader feels the weight of it, introduces the solution as a direct response, proves the solution works, and then asks for action. Each section earns the right to exist by answering a question the previous section raised.

The difference between these two approaches is not cosmetic. Green and Brock's 2000 research on narrative transportation found that people who are absorbed in a story are significantly less likely to counterargue. They do not pick apart claims the way they would with a list of bullet points. Their beliefs shift in the direction of the narrative, and those shifts stick. Information presented as a story is both more persuasive and more memorable than information presented as a catalog.

Most homepage teams never think in these terms. They think in sections: "We need a hero, a feature block, some social proof, and a CTA." That checklist produces a brochure every time. The page might look polished, but it has no throughline. Nothing connects the hero to the features, the features to the proof, or the proof to the ask. The visitor is left to assemble the argument themselves. Most of them will not bother.

This is the dimension we call the Story Arc. It measures whether a homepage has a coherent narrative progression, whether the page moves the visitor from recognizing a problem to believing in a solution to taking action. And across the 50 companies in the SignalScore benchmark study, the results tell a specific story about how companies approach this dimension.

What 50 Homepages Reveal

The average Story Arc score across all 50 companies was 58.3 out of 100. That puts it in the middle of the pack, fourth out of eight dimensions. Not the weakest, not the strongest. Comfortably mediocre.

Thirty-six percent of companies scored below 50. Only 5 companies scored above 70. And here is the detail that matters most: no company in our entire study had Story Arc as their single weakest dimension.

That last point deserves explanation. Story Arc is one of the "easier" dimensions to score passably on because any page with basic sections, a hero, some features, social proof, a CTA, gets partial credit for having a message hierarchy. You do not need to be a great storyteller to get a 50. You just need sections that follow a vaguely logical order. The bar for partial credit is low.

But clearing 70 is a different challenge entirely. That requires each section to build on the previous one, to have connective tissue between ideas, to move the reader through an argument rather than a slideshow. Only Demandbase (74), Fireflies.ai (71), Vitally (71), Gong (71), and Outreach (70) managed it.

Here is every company in the study, ranked by Story Arc score:

The spread is wide. Fifty-six points separate the top from the bottom. But the real story is in the cluster: most companies land between 42 and 68, bunched up in a range where their pages have sections in a logical order but lack the connective tissue that makes a page feel like an argument instead of a catalog.

What 74 Looks Like

Demandbase earned the highest Story Arc score in our study at 74. Their homepage does something that most SaaS pages do not: it has a throughline.

The page opens with the buyer's challenge. Not a product capability, not a feature announcement, but a problem that B2B marketing and sales teams recognize immediately. The messaging establishes that traditional approaches to account-based marketing are fragmented, that teams are running campaigns without the intelligence they need to target the right accounts at the right time.

From there, the page builds. The problem gives way to an agitation: what happens when you keep running the old playbook? Wasted spend. Missed accounts. Pipeline that never materializes. This is not stated as a feature gap. It is framed as a business consequence that compounds over time.

Then the solution enters. Demandbase positions its platform as the direct answer to the problem it just spent two sections establishing. The features it describes are tied back to the pain points it already made the reader feel. There is a cause-and-effect logic at work: you have this problem, it costs you this much, here is how we solve it, here is proof it works.

The proof section reinforces the narrative with customer logos, results, and specifics. And the final CTA feels earned rather than presumptuous, because the page has built a case for why the visitor should act rather than simply asking them to.

This is what narrative structure looks like on a homepage. Each section answers a question raised by the one before it. "What is the problem?" leads to "Why does it matter?" leads to "How do you solve it?" leads to "Does it actually work?" leads to "What should I do next?" That chain is the story arc.

Compare that with a brochure-style page that opens with "The leading platform for X" and then drops into a feature grid. That page might have all the same information as Demandbase's, but it has no progression. The visitor can read the sections in any order and get roughly the same experience. Nothing compels them forward.

What 18 Looks Like

DemandScience/Terminus scored an 18, the lowest in the study. Their homepage, at the time of scoring, read like a series of disconnected capability statements. The page described what the platform does, section by section, without ever establishing why the reader should care about any of it.

There was no problem framing. No "before and after." No progression from the buyer's world to the product's world. The sections existed independently of each other, like slides pulled from different presentations and stacked into a single page. A visitor could rearrange them in any order and the experience would be identical. That is the hallmark of a page with no narrative structure.

Feature dumps are the most common form this takes. The page lists what the product can do: target accounts, run campaigns, measure engagement, integrate with your CRM. Each capability is presented with equal weight, in no particular sequence, with no argument connecting them. The implicit assumption is that visitors will read the list and self-select the capabilities that matter to them. In practice, most visitors scan the first two sections and leave.

Salesforce B2B Marketing Automation also scored an 18, and for similar reasons. This is an enterprise brand with enormous marketing resources, but the homepage at the time of scoring was organized by product capability rather than by argument. It answered the question "What does this product do?" without ever answering "Why should I change what I am doing today?" or "What happens if I do not act?"

The pattern across the bottom of the table is consistent. These pages treat the homepage as a product spec sheet. They assume the visitor already understands the problem, already feels the urgency, and just needs to evaluate features. For most visitors, that assumption is wrong. The homepage is often the first place a buyer encounters a company's point of view. If that first encounter is a feature list, there is no reason to keep reading.

Building a Narrative Page

Turning a brochure into a narrative is a structural change, not a copywriting exercise. You can not fix this with better headlines alone. The page needs to be reorganized around an argument, not a list of capabilities. Here is the framework.

Start with the problem

The first thing a visitor reads should be about their world, not yours. Name the specific challenge your buyers face. Not a category-level observation like "B2B marketing is changing." A felt pain: teams are wasting budget on accounts that will never close, sales reps are flying blind without engagement data, your customer success team cannot see churn signals until it is too late.

The problem statement earns the right to talk about your product. Without it, everything that follows is unsolicited advice.

Agitate with a "before" picture

After naming the problem, make the reader feel it. What does daily life look like for someone living with this problem? What decisions are they making badly? What is the compounding cost of inaction over six months, over a year?

This is the "before" half of a before-and-after structure. It grounds the problem in the buyer's experience. The goal is recognition: the reader should think, "Yes, that is exactly my situation." Green and Brock's transportation theory explains why this works. When readers feel absorbed in a narrative that mirrors their own experience, their resistance to persuasion drops. They stop evaluating claims analytically and start feeling the argument emotionally.

Introduce the solution as the "after"

Only now do you talk about your product. And you frame it as the bridge between the "before" state and the "after" state. The features you describe should map directly to the problems you established earlier. If you named three pain points, your product section should address those same three pain points, in the same order.

This mapping is what gives the page its connective tissue. The reader does not need to figure out why a feature matters, because the page already built the context for it.

Prove it with specifics

Social proof comes after the solution section, not before it. Logos and testimonials mean nothing if the reader has not yet bought into the premise. But after the problem-agitate-solution sequence, proof becomes the answer to the reader's natural next question: "Does this actually work?"

The strongest proof ties back to the problem. If you framed the problem as wasted ad spend, your case study should show reduced ad waste. If you framed it as missed pipeline, the testimonial should reference pipeline gains. Proof that echoes the original problem is far more persuasive than generic "we love this product" quotes.

Apply the "so what?" test

After writing each section, read the one before it and ask: "So what?" The answer to that question should be the section you just wrote. If the connection is not obvious, the narrative has a gap.

Here is the chain for a well-structured page:

• Problem section: "Your team is wasting 30% of ad budget on unqualified accounts."
• So what? "That waste compounds every quarter, and your competitors who have solved this are pulling ahead."
• So what? "Our platform identifies and prioritizes the accounts most likely to buy, so every dollar goes further."
• So what? "Companies using this approach have reduced waste by 40% and increased pipeline 2x."
• So what? "You can see if this would work for you in 60 seconds."

Each step creates a logical pull toward the next. That pull is what makes a page a narrative instead of a brochure.

Use section transitions as connective tissue

The space between sections is where most homepage narratives fall apart. Two sections might each be well-written, but if there is no bridge between them, the reader experiences a jump cut. Their attention resets. The narrative momentum breaks.

The fix is simple. The last sentence or two of each section should raise a question that the next section answers. "This is the problem teams face. But what does it actually cost?" Transition to the agitation section. "Here is how the platform works. But does it deliver results?" Transition to proof. These bridges keep the reader moving forward because they feel a gap in their understanding that the next section promises to fill.

The companies above 70 in our study, Demandbase, Fireflies.ai, Vitally, Gong, Outreach, all follow some version of this framework. They do not all use the same words or the same visual structure. But they all move the reader through a progression rather than presenting a catalog. The pages have a beginning, a middle, and an end. That sounds basic. But only 10% of the companies in our study managed it at a score of 70 or higher.

The opportunity here is large precisely because the bar is so low. You do not need to write like a novelist. You need to organize your page around an argument, give each section a reason to exist, and connect them with transitions that pull the reader forward. Most of your competitors are not doing this. The Status Quo Tax dimension showed how few companies frame the cost of inaction. The Five-Second Verdict dimension showed how many fail to communicate their value proposition quickly. Story Arc sits at the intersection of both: it is the structural backbone that makes every other dimension work harder.

Score Your Homepage

Pull up your homepage. Read it top to bottom. Ask yourself: does each section earn the right to follow the one before it? Is there a progression from the buyer's problem to the product's solution to proof that it works? Or could you rearrange the sections without anyone noticing?

If the sections are interchangeable, you have a brochure. If they build on each other, you have a narrative. The full benchmark report scores all eight dimensions across 50 companies, but this one dimension shapes how effectively every other dimension lands. A strong value proposition buried in a brochure has less impact than a decent value proposition delivered through a story. Structure is not a substitute for substance, but substance without structure gets ignored.