GROW Framework: Put Strategy First. Always.

Your Site May Be Selling, But Is It Winning Deals?

B2B buyers have already formed an opinion about your product before they spoke to anyone on your team. They've skimmed your site, compared you to competitors, and decided whether you're worth a conversation.

That's the context every Webflow project we take on starts with.

We spend 1-2 weeks understanding your buyer, who they are, how they decide, and what they need to see before they'll book a demo. The GROW Framework is how we structure that phase, built from patterns identified across 20+ funded B2B startup projects we worked on.

What We Look for Before We Brief the Designer

There are three things we look for.

Has the positioning been stress-tested externally. A team that knows the product deeply will find the messaging clear. A buyer landing on the page without that context needs to answer "is this for me?" in seconds. If the answer isn't quick, they move on.

Does the messaging reflect the buyer's decision criteria? Founders naturally lead with how the product works. Buyers decide based on what changes for them after they buy. Those are different frames; a site built on the wrong frame can’t sell to the right audience. 

What data informs the build. Existing traffic behaviour, drop-off points, and the market analysis all tell us what the new site needs to do differently. Without them, the build starts blind.

The GROW Framework is how we close the gap between your business and your buyer.

The GROW Framework

The framework consists of four defined outputs, leading to a single brief that drives the build.

G – Groundwork: Know Your Buyer 

We start by defining the ICP, the specific person making the decision, how they evaluate solutions, what their buying process looks like, and what they need to believe before committing to a demo.

Every page, every headline, every CTA is either moving a specific person toward buying, or not. Your ICP is who we design the site for. To make sure your ICP is in fact the person who is most likely to buy, we need to understand exactly what that person needs to see.

What We're Trying to Answer in This Phase

• Who is the primary decision-maker, and who else is involved in the purchase?
• What does their evaluation process look like from first point of contact to closed deal?
• What objections appear at each stage? Where does the site need to resolve these objections?
• What does the buyer need to believe to book a demo?
• What language do they use to describe the problem the product solves?
• What does conversion look like for this buyer? a form filled? A call booked? A free trial?

These questions determine how the site is structured from the get go.

R – Refinement: Know Yourself

Positioning that's clear internally is often opaque to a buyer. 

Founders live inside the product. That depth is an asset in a sales call. Questions get live answers, but the same can’t be said for a website. Every page has to do the work without the founder in the room.

Refinement is where we close that gap. We immerse ourselves in the product until we can explain it the way your buyer would describe their problem you’re solving. That means reviewing your site, sales deck, and any recorded demos, then pressure-testing the positioning against the ICP defined in Groundwork.

The Test We Use to Know When Positioning Is Sharp Enough

Above-the-fold copy has one job: answer three questions before the visitor decides to scroll or leave.

Who is this for? What does it do? Why is it different?

If any of those require more than a second to answer, the positioning isn't ready. We keep working through Refinement until all three meet the bar. 

O – Observation: Evidence Over Assumptions

We look at three sources before drawing conclusions about what the site may need to do.

Google analytics (GA4) gives us the traffic picture, where visitors come from, which pages they land on, how far they get, and where they drop off.

Google Search Console (GSC) shows the gap between what the site appears for in search and what it's trying to rank for. The biggest opportunities often sit in queries driving impressions without clicks, or terms the ICP searches for that the site doesn't address.

Microsoft Clarity gives us the behavioural layer, including heatmaps, session recordings, and rage clicks. This is where we see what users are doing on site: what they're reading, where they scroll past, what they're trying to click on that isn't clickable. It surfaces friction that analytics alone doesn't show.

Alongside this, we run a competitive analysis.

Why We Look at Competitors 

When every company in a category leads with the same value propositions, those propositions have stopped being differentiators. The competitive analysis is how we find the whitespace: what isn't being said, what positioning angle is unclaimed. That gap becomes a direct input into the site's messaging hierarchy.

W – Workflow: The Strategy Compiled to a Brief

By the time we reach Workflow, the ICP is defined, the positioning is sharp, and the data has been reviewed. This phase turns all of that into a working brief, the document that connects strategy to execution.

This covers: a messaging hierarchy that defines what gets said first, second, and third on each key page; a tone of voice guide aligned with how the ICP expects to be spoken to; a page structure that maps each section to a specific job; and an agreed definition of what conversion looks like for this project.

What Gets Handed Off

• The primary ICP and what they need to see above the fold
• The messaging hierarchy for each page, in order
• Tone of voice guidelines
• Page structure and the job each section needs to do
• What a successful conversion looks like and where it should be prompted

What You Have at the End of a Strategy Phase

Before design has started, you have a precise ICP definition, a positioning document stress-tested against the competitive landscape, a messaging hierarchy, and a tone of voice guide.

These are standalone assets. They inform the pitch deck, the sales deck, and outbound — not just the homepage. For a Series A company preparing for a Series B raise, a positioning document built from buyer research holds up in investor conversations, not just above the fold.

Why This Matters for Funded B2B Startups

At seed to series A, speed is an asset — except when it comes to website strategy. Strong opinions about positioning, held by people who know the product deeply, produce sites that make sense internally and confuse buyers externally. The GROW Framework is the external check that catches that before it gets built in.

The opportunity cost is real. At seed to Series B, the website is the most-visited sales asset a company has. Prospects check it before every call. Investors review it before every meeting. A site that doesn't speak to the right buyer in the right language isn't a missed conversion, it's pipeline leaving at scale.

Getting the strategy right before the build is the reason the build works.

Frequently Asked Questions

How long does the GROW strategy phase take? 

One to two weeks. It runs as a dedicated phase before design or Webflow development begins. The output is a strategy document handed to the design team as a brief.

Is the strategy phase included in the project cost? 

Yes. Every Khod project begins with a paid strategy phase, scoped into the engagement from the start.

What's the difference between the GROW Framework and a standard discovery call? 

A discovery call is a conversation. The GROW Framework is 1-2 weeks worth of structured work, ICP research, positioning analysis, GA4 and GSC review, Clarity behavioural analysis, competitive mapping, and a written brief. The output is a document, not notes from a call.

Do you work with companies that don't have an existing website? 

Yes. For companies without an existing site, the Observation phase focuses on competitive analysis and ICP research rather than existing traffic data. Groundwork and Refinement remain unchanged.

Can we use the GROW outputs beyond the website project? 

Regularly. The ICP definition, positioning document, and tone of voice guide are assets clients use in pitch decks, sales decks, and onboarding materials.

What happens after the strategy phase? 

We move into design and development. The brief produced in Workflow drives the build directly, so the first design concepts are grounded in strategy, not interpretation.

You've built the product. You've got the team. Make your move.

Book a strategy call