NORTHSTAR NOTE
KivoSignal
The website problem often starts before the website
A B2B website rarely loses clarity because of one bad headline. More often, different teams are carrying different versions of the product story: the founder deck names one category, release notes emphasize features, and sales adapts the message deal by deal. The website inherits the contradictions.
A visual refresh can make that inconsistency look better without fixing it. Before redesigning pages, define a narrative system that can survive multiple audiences, channels, and owners.
Start with the repeatable sentence
Ask five people inside the company to explain the product in one sentence. If the answers use different categories, outcomes, or audiences, the website has no stable center. A useful positioning sentence does not have to become public copy word for word. Its job is to constrain the story: this is the category, this is the primary audience, this is the expensive problem, and this is the distinctive way the product helps.
The constraint is valuable. It tells the homepage what to introduce, tells solution pages what to deepen, and tells feature pages what not to pretend they are. It also gives sales and lifecycle teams a common starting point. Without it, every new page becomes a fresh strategy workshop disguised as a copy task.
One-sentence test
Category · Primary audience · Costly problem · Distinctive mechanism
If five people inside the company cannot answer those four prompts with the same core idea, the website has no stable center yet.
Build a hierarchy, not a pile of claims
Most B2B sites contain the right raw material: a useful product, credible technical detail, real customer questions, and a clear operational pain. The problem is that everything is presented at the same level. Category language, product mechanics, proof, and feature detail compete for the opening screen. Visitors cannot tell which idea should organize the rest.
A better hierarchy moves from orientation to consequence to mechanism. First, help the right visitor recognize the situation. Second, name what becomes easier or more controlled. Third, explain how the system works. Technical detail becomes more persuasive when the visitor already knows why it matters. The KivoSignal concept case study uses this sequence by leading with the decision, then revealing the research trail behind it.
Give every page one narrative job
A page should not try to complete the entire sales process. The homepage establishes the frame and routes intent. A solution page translates that frame for a specific operating problem. A feature page explains mechanism. A case study or concept story demonstrates how the pieces connect. An article creates understanding around a question the buyer already has.
When each page has one job, internal links become part of the argument rather than a navigation afterthought. The visitor can move from broad recognition to relevant detail without repeatedly restarting the story. Teams also gain a practical editorial test: if a section cannot support the page’s job, it belongs elsewhere or should be removed.
Use design to reveal the argument
Design should make the hierarchy visible. Scale can separate the main idea from evidence. Grids can show relationships. Repeated components can signal that several pages belong to the same system. Motion can explain a transition or connection. None of these tools should compensate for a missing argument.
A useful review method is to blur the page or read only the headings. Can you still understand the sequence? Then read the body copy without the interface. Does each section earn the next one? If either test fails, adding more visual novelty will increase noise. Positioning and narrative work should come before the component polish, which is why Northstar treats them as part of the website engagement rather than a separate pre-project document.
The practical reset
Before redesigning, collect the current homepage, sales deck, onboarding copy, and the five most common buyer questions. Mark repeated ideas, contradictory category language, and claims that have no explanation beneath them. Choose one primary narrative and define the role of each supporting page. Only then translate the hierarchy into sections and components.
The objective is not a perfectly uniform voice. Different pages can change depth and emphasis. The objective is coherence: every surface should feel like a more specific expression of the same underlying product position. When that center holds, the website becomes easier to scan, easier to edit, and easier for the company to repeat.