
Key takeaways
- Context-Led Growth is a growth model in which every interaction with a customer, across every stage, team, channel and system, continues from the last one, so no signal of intent is lost between conversations.
- The problem it solves is funnel amnesia: businesses capture a customer's intent, then lose it at the handoffs between teams, channels, systems and time.
- The cost is real: firms that respond to an enquiry within an hour are nearly seven times as likely to qualify the lead, yet more than half of customers say companies feel like separate departments rather than one business.
- Four shifts make it urgent now: customers expect continuity, tech stacks are more fragmented than ever, every customer costs more to win, and AI agents are taking over customer conversations.
- It rests on five principles: respond while intent is warm, meet customers on their channel, never make them repeat themselves, follow through to resolution, and measure what leaks.
- It is measured with two numbers: leakage rate, the share of customer signals that end without resolution, and Context Score, which grades speed, relevance, recognition, continuity and follow-through.
- It runs on a context layer: a conversation graph that sits across every channel, team and system of record, so every person and AI agent knows the customer's story.
- Any business can start today with a Leakage Audit: a ten-minute self-assessment and a two-week test from the customer's side.
Context-Led Growth in one sentence
Context-Led Growth is a way of growing a business in which every interaction with a customer, across every stage, team, channel and system, continues from the last one, so no signal of intent is lost between conversations.
Most businesses don't have a lead problem. They have a memory problem.
They spend heavily to earn a customer's attention: the ad, the enquiry form, the store visit, the free trial. Then the thread breaks. The enquiry waits a day for a call. The call doesn't know what the form said. The salesperson who closed the deal never tells the service team what was promised. Months later, a renewal reminder arrives from someone who has never heard of the customer's complaint. Every team did its job. The customer still left.
The evidence has been pointing at this for more than a decade. In a classic Harvard Business Review study, firms that responded to an online enquiry within an hour were nearly seven times as likely to qualify the lead as those that waited even an hour longer, and 23% of the companies audited never responded at all. Today, 79% of customers expect consistent interactions across departments, yet 55% say it feels like they are dealing with separate departments rather than one company.
We call this funnel amnesia. Context-Led Growth is the cure.
In short
- Customers leak in the gaps between conversations: between teams, between channels, between systems, and across time.
- The businesses that grow are the ones that never lose the thread of what each customer said, wanted and objected to, from first enquiry to renewal.
- In the age of AI agents, that customer context is the scarcest asset a business owns, and the one no competitor can copy.
The enemy: funnel amnesia
Funnel amnesia is what happens when a business forgets what its customer already told it. It rarely looks like a failure. It looks like four ordinary weeks.
The online store. A shopper fills a cart with two pairs of running shoes, checks the size chart, and leaves. She was comparing, not abandoning. Two days later she gets a generic "you forgot something" email with a discount on a jacket. When she messages support to ask whether the shoes run small, she is asked for an order number she doesn't have. She buys elsewhere. Baymard Institute puts the average documented cart abandonment rate at about 70%, and much of it is intent left unanswered: shoppers still browsing, comparing, not yet ready.
The gym. A new member comes four times a week in January, twice a week in February, then stops. Nobody calls. In April the membership quietly ends. Industry figures suggest about half of new joiners leave within six months, and 52% of cancellations are silent, with no notice and no reason given. Retention researcher Paul Bedford found that members who are ignored are more than twice as likely to cancel as members who are regularly spoken to.
The bank. A customer applies for a personal loan in a mobile app, uploads her documents, and gets stuck at income verification. A call-centre agent rings the next day and asks her to upload the same documents again. A week later, a message from the branch asks for them a third time. In Signicat's survey of 7,600 European consumers, 68% had abandoned a financial application in the previous year.
The car dealership. A buyer test-drives an SUV, mentions that rear-seat space matters most to his family, and asks for a callback after payday. The callback never comes, and he buys from a competitor. At the same dealer, another customer complained at delivery about a rattling dashboard. When her first service came due, the reminder said nothing about it, and the service advisor heard the story for the first time from an angry customer at the counter.
Four industries, one pattern. The customer did their part: they showed intent, shared a preference, raised a concern. The business captured each signal somewhere, in a form, a CRM note, a call log or one employee's memory, and then lost it at a handoff.
Where the thread breaks
Funnel amnesia lives in four gaps:
- Between teams. Marketing captures, sales converts, service supports, and each holds a different slice of the customer.
- Between channels. The enquiry arrived on WhatsApp or SMS, the follow-up was a phone call, the confirmation was an email. Each channel starts from zero.
- Between systems. The CRM, the loan system, the store platform, the booking tool and the help desk rarely share what the customer actually said.
- Across time. Intent decays. A signal that isn't acted on within minutes or days is, in practice, gone.
The cost doesn't appear on any single team's dashboard. Marketing reports leads generated, sales reports deals closed, service reports tickets resolved. The customers who slipped between those numbers are nobody's metric, which is exactly why they keep slipping.
At every handoff, part of what the customer said is lost, and no team's dashboard shows it.
Why now
Funnel amnesia is not new. What is new is that it has become the deciding factor in who grows. Four shifts explain why.
1. Customers now expect continuity
The best consumer brands have reset expectations. People move between channels and devices without thinking about it, and they expect the business to keep up. Salesforce research found that 71% of customers prefer different channels depending on context, and 77% expect to interact with someone immediately when they contact a company. A customer who starts on a messaging app and finishes on a phone call does not think of that as two interactions. To them, it is one conversation, and they notice when the business treats it as two.
2. Stacks are more fragmented than ever
The average growing business now runs its customers through a dozen tools: an ad platform, a website builder, a CRM, a messaging provider, a payments system, a help desk, a loyalty app, an industry system of record such as a loan platform or a dealer management system. Each holds a fragment of the customer. None holds the whole conversation. Every tool added to solve one problem creates one more gap for context to fall into, so funnel amnesia gets worse by default.
3. Every customer costs more to win
Acquisition keeps getting more expensive. Privacy rules and tighter tracking on mobile devices have made ad targeting less precise, and businesses pay more for every lead as a result. In ecommerce, SimplicityDX found that merchants lost an average of $29 on every new customer acquired, up from $9 in 2013. When each customer costs more to win, each one lost in a gap costs more too.
Keeping them pays. Frederick Reichheld's research at Bain & Company, among the most widely cited findings in business, showed that a 5% increase in customer retention can raise profits by 25% to 95%. Funnel amnesia leaks customers at exactly the points where that retention is won or lost: the slow first reply, the forgotten callback, the onboarding nobody followed up, the complaint that never reached the next team.
4. AI agents are taking over customer conversations
Businesses are handing enquiries, qualification, bookings and service requests to AI agents, and this shift cuts both ways. An agent without context is a polite stranger who greets a five-year customer like a first-time visitor, and it can repeat that mistake across thousands of conversations an hour. Funnel amnesia, automated, spreads faster than any human team could manage.
But AI also changes what is possible. For the first time, it is affordable to capture every conversation, understand it, and carry it into the next one, for every customer. Part of this is what the AI industry calls context engineering; Shopify CEO Tobi Lütke described the goal as giving AI enough context to make a task "plausibly solvable." For a customer-facing agent, that context is not a better prompt. It is the customer's own story. The problem is getting worse at exactly the moment it becomes solvable.
What it adds up to: software is cheap, context is not
A few years ago, building a CRM screen, a booking flow or a customer portal took a team and a quarter. Today a capable person can build a working version in a weekend with AI tools. What cannot be rebuilt in a weekend is a customer's history: the questions they asked, the objections they raised, the promises made to them, the moment they went quiet. That history only exists if the business captured it, connected it and kept it.
As software gets cheaper, that record becomes the most valuable thing a business owns, and the hardest for a competitor to copy. The advantage is moving away from whoever has the most software, and toward whoever remembers their customers best.
The conversation lives where the customer lives
Context-Led Growth is channel-agnostic, but customers are not. Where the conversation happens depends heavily on where the customer lives.
In the United States, the default is the text message, backed by voice and email. In a 2026 survey, 86% of US consumers said they had opted in to texts from businesses, up from 62% five years earlier. WhatsApp is growing, but SMS remains the everyday channel.
In India, Brazil, Indonesia, Mexico and much of the Middle East and Southeast Asia, the default is WhatsApp, backed by voice. India alone has more than 500 million WhatsApp users, and across these markets people use it for everything from support questions to purchases. A customer asked to fill in a web form or wait for an email is already halfway out the door.
In Europe and elsewhere, the picture is mixed: messaging apps, SMS, email and voice each lead in different countries and age groups.
The channel matters less than what happens across channels. Customers rarely stay on one. A loan enquiry starts on WhatsApp and continues on a phone call. A gym trial is booked by SMS and confirmed by email. An online order is placed on the website and questioned in a chat. Each switch is a chance for the thread to break.
And customers notice when it does. Being reachable on a channel is not the same as listening on it.
The principle is simple: meet customers on their channel, and carry the conversation with them when they switch.
The channels change from market to market; the conversation should not.
What Context-Led Growth is
Context-Led Growth treats the entire customer relationship as one continuous conversation, and makes that conversation the engine of growth.
It rests on a simple idea: every interaction should start where the last one ended. Not where the last interaction in this department ended, or on this channel, or in this software. Where the customer left off.
What "context" means here
The word is used loosely across the industry, so it is worth being precise. In Context-Led Growth, context is what the customer has told you and shown you, carried forward:
- What they said: questions asked, preferences shared, the words they used.
- What they wanted: the need behind the enquiry, the outcome they were after.
- What held them back: objections, hesitations, complaints, unanswered questions.
- What was promised: a callback, a discount, a delivery date, a fix.
- What they did: visits, purchases, logins, missed appointments, the moment they went quiet.
- How they like to talk: the channel, language and time that work for them.
This is different from two other things often called context. It is not account intelligence, the firmographic and intent data that tells a sales team which companies might be in market. And it is not prompt context, the documents and instructions fed to an AI tool to improve its output. Both are useful. Neither tells you what this customer said to your business last Tuesday.
Across the whole lifecycle
Context-Led Growth spans every stage of the relationship, because funnel amnesia strikes at every handoff between them:
- Capture: an ad click, an enquiry, a walk-in, a cart. The first signal of intent, and the first thing to remember.
- Convert: the conversations that turn interest into a purchase, a sign-up, an application or a booking.
- Onboard: the first weeks after the decision, when customers are most likely to drift away quietly.
- Serve: questions, issues and requests, each one a chance to strengthen or break trust.
- Retain and grow: renewals, repeat purchases, upgrades and referrals, funded by everything learned before.
Most growth models focus on one or two of these stages. Context-Led Growth is about the joins between all five.
How it compares
| Model | Core belief | Growth engine | Key metric | What it fixes |
|---|---|---|---|---|
| Inbound marketing | Attract buyers with useful content instead of interrupting them | Content, search and social | Leads and marketing-qualified leads | Cold, interruptive outreach |
| Sales-led growth | Skilled people close and expand the best accounts | Sales teams and relationships | Pipeline and win rate | Complex, high-value deals that need a human |
| Product-led growth | Let the product sell itself through use | Free trials, freemium and self-serve | Activation and product usage | Friction between trying and buying |
| Context-Led Growth | Never lose the thread with a customer | Continuous, context-carrying conversations across every stage | Leakage rate | Customers lost in the gaps between teams, channels, systems and time |

Context-Led Growth does not replace the others. A business can attract with content, close with salespeople and onboard through its product. Context-Led Growth is what connects those motions, so the customer experiences one company instead of three.
Who owns the customer conversation today
Nobody owns the whole conversation. That is the problem in one sentence.
In most businesses, the customer relationship is split across teams, and each team runs its own tools. Every one of those tools is good at its slice. None of them was built to carry the customer's story from one slice to the next.
The tools: every category holds a fragment
- CRM (Salesforce, HubSpot, Zoho) records accounts, deals and activities, but mostly what the sales team typed in, not what the customer said.
- Marketing automation and engagement platforms (HubSpot, Adobe Marketo, Braze, MoEngage, CleverTap) send campaigns and journeys, but rarely know what happened on the sales call.
- Customer data platforms unify profiles and behavioral events, but conversations, objections and promises are hard to fit into an event stream.
- Messaging platforms (Twilio, Infobip, Gupshup) deliver SMS and WhatsApp at scale, but are pipes: the message passes through, the meaning doesn't stay.
- Contact center and help desk software (Genesys, NICE, Zendesk, Freshdesk, Intercom) resolve issues efficiently, but each ticket often starts from zero.
- Industry systems of record (loan origination systems, dealer management systems, practice management software, ecommerce platforms) hold the transactions that matter most, and very little of the conversation around them.
- AI agents and workflow tools answer, route and automate faster than any team, but are only as good as the context they are given.
Each category is filled by strong companies. The gaps between the categories are filled by nobody.
Each category does its own job well; the customer's story falls between them.
The people: every role owns a stage
The same split runs through the organization chart. Find yourself in the table below, then look at the last column.
| Role | Owns | Usually measured on | Where the thread breaks for them |
|---|---|---|---|
| Marketing and growth | Capture | Leads, cost per lead, campaign ROI | Leads are handed to sales and disappear from view |
| RevOps and marketing operations | The systems and data between teams | Data quality, funnel conversion, tool adoption | Owns the pipes, but not the conversations flowing through them |
| Sales and inside sales | Convert | Pipeline, conversion rate, revenue | Calls leads without knowing what they asked marketing |
| Onboarding and customer success | Onboard and retain | Activation, renewal, net revenue retention | Inherits customers without the promises made during the sale |
| Customer service and contact center | Serve | Resolution time, satisfaction, cost per contact | Each ticket starts from zero, and insights rarely flow back |
| IT and data teams | Integration and security | Uptime, compliance, cost | Asked to connect everything, rarely asked what the customer needs |
| CEO, CRO or COO | The whole lifecycle | Growth and profit | Sees the totals, not the customers lost between departments |
Every role in this table is doing its job. The customer is still lost, because the handoffs between roles belong to no one.
Who champions Context-Led Growth
In practice, Context-Led Growth tends to be driven by whoever is closest to the joins: a RevOps or growth leader who sees the leakage in the data, or an executive who owns revenue across marketing, sales and service. It works only when it is treated as a company-wide way of operating, not as one department's project. The question to ask is not "which tool owns the customer?" but "who owns the thread?"
The five principles
Context-Led Growth comes down to five principles. None requires a particular industry, team size or technology. Each can be checked against how your business works today.
1. Respond while intent is warm
Every customer signal has a half-life. An enquiry, an abandoned cart, a missed class, an approaching renewal date: each is a moment when the customer is paying attention. Wait too long and the moment passes, no matter how good the eventual reply.
Example: an online store. A shopper messages at 11pm asking whether a jacket runs large. One store replies the next morning with a link to the size chart. Another replies within minutes, remembers she bought a medium in a different style last winter, and suggests the same size. Only one of them makes the sale that night.
You're doing this if every kind of signal, not just enquiry forms, triggers a timely and relevant response, including at night and on weekends, and you know your response time for each.
2. Meet customers on their channel
Customers choose where to talk, and they change their minds. The business's job is to be there, and to keep the conversation intact when the customer moves.
Example: a bank. A customer asks about a home loan on WhatsApp in the evening. The next day, a loan officer calls her, already knowing the property type, her rough budget and her one worry: the processing fee. A week later, the branch confirms the documents by message. Three channels, one conversation.
You're doing this if customers reach you on the channel they prefer, and switching channels never sends them back to the beginning.
3. Never make the customer repeat themselves
Asking a customer something they have already told you is a small failure that signals a big one: the business doesn't remember them. Context has to travel with the customer, across every team and every handoff.
Example: a car dealership. At delivery, a customer mentions a rattle in the dashboard. Six months later, the service reminder mentions it, the advisor has a note ready, and the part is in stock. The customer never has to explain it twice, and tells three friends about it.
You're doing this if anyone, human or AI, who speaks to a customer can see the last conversation, the open questions and the promises made.
4. Follow through to resolution
Most businesses stop following up when they get tired, not when the customer's need is resolved. Context-Led Growth stays with every open signal until it reaches an end state: a purchase, a booking, a solved problem, or a clear "no, thank you." Following through is not the same as nagging. Each follow-up should carry the context of the last one and respect how often the customer wants to hear from you.
Example: a gym. A member who came three times a week drops to once a fortnight. Instead of waiting for the cancellation, the gym checks in: she'd mentioned training for a 10K in spring, so the coach suggests a running-focused plan that fits her new work schedule. She stays.
You're doing this if every open signal has an owner and an end state, and no customer goes quiet without someone noticing.
5. Measure what leaks
Businesses measure what comes in: leads, traffic, tickets. Far fewer measure what quietly goes out: the enquiries never answered, the onboardings never completed, the renewals never discussed. You cannot fix a leak you don't measure.
Example: a clinic. It tracks appointment bookings closely. When it starts tracking leakage too, it finds that a third of enquiries about a new treatment never got a callback, and that most patients told to "book a follow-up in three months" never did. Neither shows up in the bookings report, and both are fixable.
You're doing this if you know what share of customer signals, at every stage, ended without resolution, and someone is accountable for bringing that number down.
Each principle guards a different point where the thread can break; together they hold one conversation together.
The metrics: leakage rate and Context Score
Context-Led Growth is measured with two numbers. Leakage rate shows the outcome: how much customer intent ended without resolution. Context Score shows the behavior behind it: how quickly, how consistently and how knowledgeably the business responds. Leakage rate comes first: the share of customer signals that ended without a resolution.
A signal is any moment a customer shows intent or needs something: an enquiry, a cart, an application, a new membership, a complaint, an approaching renewal. A resolution is any clear end state: a purchase, a booking, a solved problem, a renewal, or an explicit "no, thank you."
That last part matters. Leakage rate is not the inverse of conversion rate. A customer who says no after a good conversation has not leaked; the business listened, answered, and closed the loop. A customer who was never called back has leaked, whatever they would have decided.
Leakage at every stage
| Stage | Signals to count | Resolved when | Leaked when |
|---|---|---|---|
| Capture | Enquiries, carts, sign-ups, walk-ins | The customer gets a real answer while still interested | No response, or a response after the interest faded |
| Convert | Quotes, trials, applications, test drives | A purchase, a booking, or a clear decision | The customer goes quiet and nobody follows through |
| Onboard | New customers, members, accounts | The customer reaches first real value | The customer drifts away before getting there |
| Serve | Questions, complaints, requests | The issue is solved and the customer confirms it | The ticket closes without a fix, or the customer has to come back |
| Retain and grow | Renewals, reorders, lapsing customers | Renewed, reordered, or a reason captured | The customer leaves silently |
A worked example
A car dealership receives 1,000 enquiries in a month. Thirty days later, 620 have reached an end state: a test drive, a purchase, or a clear decision not to buy. The other 380 have nothing: no reply, a single unanswered call, or a quote that was never followed up. The dealership's capture-and-convert leakage rate is 38%.
The lead report for that month would have looked healthy: 1,000 enquiries, up 12% on last year. Leakage rate tells the real story. More than a third of the demand the dealership paid for was never worked to a conclusion.
Why it beats lead counts
- It measures what you did with attention, not how much you bought. Lead counts reward spending more on ads. Leakage rewards using the demand you already have.
- It crosses team boundaries. No single team can lower leakage alone. It forces marketing, sales and service to look at the same customers.
- It is honest about follow-through. A business can hit its lead target and its sales target while leaking heavily in between. Leakage makes the gap visible.
- It improves with context. Every principle in this model lowers leakage directly, which makes it the natural scorecard for Context-Led Growth.
Context Score: how well the business holds the thread
Leakage rate tells you how much was lost. It does not tell you why. Two businesses can both resolve 70% of enquiries, one within minutes and with full knowledge of the customer, the other after three days and a round of repeated questions. The second is leaking trust even when it closes the loop.
Context Score captures that difference. It looks at every customer signal through five questions:
- Speed: how quickly did a real answer arrive?
- Relevance: did it answer what the customer actually asked?
- Recognition: when the customer came back on another channel, did the business know who they were?
- Continuity: did the business remember what it had already been told, or ask again?
- Follow-through: did it stay with the customer until there was an answer?

Every one of these can be observed from the customer's side of the conversation: a timestamp, a question answered or ignored, a detail asked for twice, a follow-up that never came. That means Context Score can be measured from the outside in, exactly as customers experience a business, without access to its systems. It is the basis of the Leakage Audit described later in this piece.
The two metrics work as a pair. Context Score is the leading indicator: it moves as soon as a business changes how it responds. Leakage rate is the lagging indicator: it follows a few weeks later, in revenue that stops slipping away.
Start simple: pick one stage, one signal type and one window, such as enquiries resolved within seven days, and measure leakage for a month. Then look at the same customers through the five Context Score questions. The two numbers together are usually the most persuasive argument a business will ever see for changing how it works.
One customer, two journeys
To see the difference Context-Led Growth makes, follow one customer through the same eighteen months, twice.
Maya is 34 and buying her first home. On a Saturday night she messages a bank: she wants a home loan for an apartment under construction, her income includes a variable bonus, and she is nervous about hidden fees.
Journey one: funnel amnesia
- Capture. An auto-reply thanks her for her interest. A loan officer calls on Tuesday, asks what kind of property she is buying, and whether she is salaried. She explains everything again.
- Convert. The quote arrives by email with a processing fee nobody mentioned. She asks about it by message; the reply comes two days later from someone else, asking for her application number.
- Onboard. Documents are collected twice, once by the call centre and once by the branch. The loan is approved, but the construction-linked disbursement schedule is never explained. Her first instalment surprises her.
- Serve. She calls to ask about prepaying with her bonus. The agent has no record of her bonus, her earlier questions or her complaint about the fee.
- Retain. Eighteen months later, rates fall. A competitor offers to refinance her loan. Her own bank sends a generic newsletter. She switches.
Every team followed its process. The bank still lost a customer it had already paid to win.
Journey two: Context-Led Growth
- Capture. Within minutes, she gets a real reply on the same messaging channel: it answers the question about under-construction property, notes the bonus, and lists every fee up front.
- Convert. The loan officer who calls on Monday already knows all three of her concerns and starts with the one she cared about most: fees. No question is asked twice.
- Onboard. Documents are collected once. Because the bank knows the property is under construction, it explains the disbursement schedule before the first payment is due.
- Serve. When she asks about prepaying, the agent already knows about the bonus and shows her the saving.
- Retain and grow. When rates fall, the bank reaches her first, with a rate review that references her loan, her prepayment and her original worry about fees. Two years later, she takes her car loan with the same bank.
Same customer, same bank, same products, same teams. The only difference is that in the second journey, every conversation started where the last one ended.
The products and teams are identical in both rows; only the memory differs.
The maturity model
No business moves from funnel amnesia to Context-Led Growth in one step. It happens in five stages, and most businesses can place themselves within a minute.
| Stage | What it looks like | The telltale sign | The next step |
|---|---|---|---|
| 1. Fragmented | Customer information lives in inboxes, spreadsheets, call logs and employees' phones. Response depends on who is on shift. | Customers repeat themselves at every step. | Put every signal in one place, with an owner. |
| 2. Connected | Systems are integrated and each customer has a single record, but the conversations still live inside each channel and team. | The data is shared; the story isn't. | Respond to every signal quickly, on the customer's channel. |
| 3. Responsive | First responses are fast everywhere, often with AI help, around the clock. But each conversation stands alone, and follow-ups are generic. | Quick answers that forget yesterday. | Carry context across channels, teams and time. |
| 4. Continuous | Each customer has one thread across every stage, channel and team. Handoffs carry promises. Leakage is measured. | Customers stop repeating themselves. | Let context drive action, not just answers. |
| 5. Compounding | Context drives what happens next: outreach before the customer asks, insights flowing back to marketing and product, AI agents that improve with every conversation. | Leakage falls quarter after quarter, without adding headcount. | Keep raising the bar. |

In our experience, most businesses sit at stage 1 or 2. Many of those investing in AI jump straight to stage 3 and stall there: they have made their amnesia faster, not cured it. The step from responsive to continuous is the hardest one, and the one that changes the economics, because it is where customers stop leaking between conversations.
Stage 5 is where Context-Led Growth earns its name. Every conversation makes the next one better, every customer's history becomes an asset, and growth compounds from the demand a business has already won.
What it takes: the context layer
Getting from stage 3 to stage 4 is not a matter of buying one more channel or hiring one more team. It requires something most businesses don't have: a context layer.
A context layer sits across every channel, team and system a business uses, rather than being another box among them. Customers talk to the business on WhatsApp, SMS, calls, email and in person. Records live in the CRM, the loan system, the store platform and the help desk. The context layer is what connects the two: it holds the customer's story and makes it available to every person and every AI agent, at the moment they need it.
At its heart is a conversation graph: each customer connected to every conversation they have had with the business, the signals inside those conversations (needs, objections, promises, outcomes), and the people and agents involved. Where a CRM records what the business did, the conversation graph records what the customer said, and keeps it connected over time.
Every person and agent reads the customer's story before responding and adds to it afterwards, whatever channel or system the conversation touches.
Six capabilities a context layer needs
- Identity. Recognize one customer across every channel, phone number, email address and visit. Without this, nothing else works.
- Capture. Record every conversation, in both directions and on every channel, including voice. Not just what an employee remembered to type into a system afterwards.
- Understanding. Turn raw conversations into usable context: what the customer needs, what worries them, what was promised, how they feel. This is where the conversation graph is built.
- State. Know which signals are open, who owns each one, and what end state it is waiting for.
- Action. Make every human and AI agent read the context before responding and add to it afterwards. Trigger the next step when a customer goes quiet, a promise comes due, or a renewal approaches.
- Measurement. Compute leakage rate and Context Score continuously, from the layer itself.
Underneath all six sits governance. A context layer holds some of the most sensitive information a business has, so consent, privacy, access control and data residency are not optional extras. In regulated industries such as banking, insurance and healthcare, they are the first question, and rightly so.
Three ways to build it
Businesses typically take one of three routes:
- Stitch it together from a CRM, a customer data platform, messaging tools and integrations. This works when the stack is small, but the conversation itself usually falls through the gaps between tools.
- Build it on the company's own data warehouse. This offers full control, but needs a dedicated team to capture, interpret and act on conversations, not just store them.
- Adopt a purpose-built context layer designed around conversations from the start, connected to the systems the business already runs.
Whichever route a business takes, the test is the same. Pick any customer, at any stage, on any channel. Can the next person or agent who speaks to them continue the conversation exactly where it left off? If the answer is yes, the business has a context layer. If not, it has a collection of tools.
How to start: the Leakage Audit
The fastest way to understand funnel amnesia is to experience your own business the way a customer does. The Leakage Audit has two parts: a ten-minute self-assessment, and a two-week test from the outside.
Part one: the self-assessment
Tick each statement that is true for your business today.
- ☐ We know our response time for every kind of customer signal, including at night and on weekends.
- ☐ If a customer messages us and then calls, the person on the phone can see the message.
- ☐ Anyone who speaks to a customer can see the last conversation and any promises made.
- ☐ Every open enquiry has an owner and an end state.
- ☐ Our follow-ups go beyond two attempts, and each one says something relevant.
- ☐ We notice when an existing customer goes quiet, before they cancel.
- ☐ We know our leakage rate for at least one stage of the lifecycle.
- ☐ When AI responds to our customers, it knows their history with us.
Seven or eight ticks puts you at stage 4 or beyond. Four to six usually means stage 2 or 3. Three or fewer means funnel amnesia is costing you more than you think.
Part two: the outside-in test
Self-assessments are optimistic. The outside-in test is not. It measures your business purely from the customer's side of the conversation:
- Become a customer. Create a realistic enquiry with a few specific details: what you need, a constraint, and a concern.
- Reach out. Contact the business on its main channel. Note when a real answer arrives, and whether it addresses what you actually asked.
- Switch channels. A couple of days later, get in touch through a different channel. Does the business know it is you, or does it start from zero?
- Go quiet. For the next two weeks, note every follow-up: when it comes, on which channel, and whether it remembers anything you said.
- Repeat. Run the test at different times of day and week, because funnel amnesia is often worst at night and on weekends.
Keep it to enquiries; never submit real applications or documents. Run it on your own business first, then on two competitors. The comparison is usually the moment the conversation inside a company changes.
A scored version of the audit, benchmarked against other businesses in your industry, is available at contextledgrowth.com.
What Context-Led Growth is not
New ideas get absorbed into old categories quickly. So it is worth being clear about what Context-Led Growth is not.
- It is not a CRM. A CRM is a record of what a business did. Context-Led Growth is about what the customer said, and acting on it everywhere.
- It is not a chatbot. A fast answer that forgets yesterday is still funnel amnesia, just quicker.
- It is not omnichannel. Being present on every channel is the starting point. The point is that the conversation survives the move between them.
- It is not prompt engineering. Feeding an AI tool better instructions improves its output. Context-Led Growth is about the customer's own story, carried from one conversation to the next.
- It is not intent data. Knowing which companies might be in market is useful. Knowing what this customer told you last week is decisive.
- It is not a single tool or a single team's job. It is a way of operating that spans marketing, sales, service and every system in between.
Tools will help, and AI will help most of all. But the shift is in what a business chooses to treat as its most important asset: not its software, not its lead lists, but the thread of every conversation it has ever had with its customers.
The Context-Led Growth manifesto
Your customers remember every conversation they have had with you. It is time your business did too.
Every signal deserves an answer while it still matters.
No customer should have to repeat themselves.
The channel is the customer's choice. The thread is the business's job.
Follow-through is a system, not a mood.
What leaks should be measured, and owned.
The next decade of growth will not be won by the businesses with the most leads, the most tools or even the most AI. It will be won by the ones that never lose the thread: the ones that remember what every customer said, wanted and was promised, and let that memory shape every conversation that follows.
That is Context-Led Growth.
Context-Led Growth was developed by the team at Zigment, from building AI agents that work across the customer lifecycle for lenders, auto dealers, healthcare providers and consumer brands. Take the Leakage Audit at contextledgrowth.com.
Sources
- Oldroyd, McElheran and Elkington, "The Short Life of Online Sales Leads," Harvard Business Review, 2011
- Salesforce, "How Are Customer Touch Points Changing?," drawing on the State of the Connected Customer report
- Baymard Institute, "Cart Abandonment Rate Statistics"
- Les Mills, "The secret to boosting new member attendance"
- Health Club Management, "Retention: Reaching capacity," on Paul Bedford's retention research
- Signicat, "The Battle to Onboard 2022"
- GTM Strategist, "The GTM Guide to AI Context Engineering"
- Forrester, "Profiting From Post-Sale Marketing," on Frederick Reichheld's retention research at Bain & Company
- MarketingProfs, "The SMS Marketing Preferences of Americans," SimpleTexting survey, 2026
- CXM World, "Texting Beats Email, Phone, and Social for Almost Every Message Type," EZ Texting report, 2026
- Textmagic, "2025 Consumer SMS Survey"
- Skillademia, "WhatsApp Statistics"
- Mobile Ecosystem Forum, "WhatsApp and A2P messaging growth"
