Give,
don’t ask.

What it is

This playbook turns the method in Carlos Justino's book Give, don't ask: Give away your best knowledge and become the obvious choice into something a B2B team can use on Monday morning. It explains why the method exists, sets out its four kinds of work, gives you plans for the first 30 and 90 days, and includes templates you can copy.

The method is called Non-Gated Demand Orchestration. The book defines it as "a continuous way to give buyers useful knowledge and tools before asking for personal information, learn from consented behaviour and market intent, and coordinate marketing and sales around the buyer's progress."

Who it is for

B2B marketers who have to make this change work inside a real business. Founders, sales leaders and agency teams face the same decisions from different positions, so they will find it useful too.

How to use it

• Read section 1 if you need to explain the change to a colleague.
• Read section 2 to understand the four kinds of work: understand, give, connect and learn.
• Pick one campaign and follow the 30-day plan in section 3.
• Copy the templates in section 4 into a shared document.
• Keep section 6 (what not to do) and section 7 (the formula on a page) close by.

Notes on sources and examples

• Quotations in this playbook come from the book and are marked with quotation marks.
• Research findings are the ones the book cites. They describe the buyers surveyed, not a rule every purchase follows. The full list is in section 8.
• Examples are illustrative. Maya, Nina, Sam and Ravi are fictional teaching characters from the book. They are not clients, and their companies are not real. Where an example comes from Carlos's own projects, it says so, and it is told as the book tells it, without added numbers.
• This playbook contains no client results, testimonials or invented statistics.

1.1 What changed in buying

The book opens with a fictional marketing director called Maya. Her pipeline has slowed and she has a meeting with her chief executive. She finds a report that looks useful, clicks download and meets a form asking for her name, work email, company, job title, company size, country and telephone number. She knows what follows: the report, an automated email, then a sales call.

So she opens an AI assistant instead, describes her problem in her own words and gets a starting point in minutes. The company with the report sees an abandoned landing page and no lead. As the book puts it: "The buyer did not disappear; she found an easier path to the answer."

That is the gap the method addresses: "Companies still behave as if knowledge is scarce, while buyers know that it is available almost everywhere."

Several things have changed at once:

• Buyers learn on their own first. Gartner found that a majority of the B2B buyers it surveyed preferred an overall experience without a sales representative, although they still wanted human input for decisions that needed context and judgement.
• Preference forms early. Research from 6sense found that buyers often formed a preference before contacting sellers. By the time someone asks for a proposal, much of the decision has already been shaped.
• AI moved the questions off your website. Buyers can investigate a problem without visiting your site, compare options before your analytics record a session and arrive at a sales conversation with a shortlist, objections and a view of what you should cost.
• The buying group is mostly invisible. Research by Edelman and LinkedIn found that influential internal stakeholders use expert content during vendor evaluation, even when they remain invisible to the seller.
• Most of your market is not buying this month. John Dawes's 95-5 rule, shared through the LinkedIn B2B Institute and the Ehrenberg-Bass Institute, is a planning principle rather than a measurement of your market. Its practical lesson is to stop judging every encounter as though the person should buy now.
• Buying never followed the funnel. People jump ahead, go backwards, ask a colleague, disappear for a month and come back with a different question. "The funnel was tidy, but buying remained human."

1.2 Why gated tactics fail

The gate solved a real problem once. It made the exchange visible: the company offered an asset, the visitor gave their details and marketing could count the response. Over time, teams began to judge content by the number of names it captured.

That created four problems.

• A form fill is not intent. People complete forms for many reasons: active buying, general learning, academic research, competitor research, curiosity about one statistic, interest in the author, or simple willingness to tolerate the form. Treat them all as leads and you create work for sales and irritation for buyers. "The company has mistaken access for intent, and the buyer has learnt that the apparent gift came with a string attached."
• The visible lead hides the real buyer. One person downloads your report with a false phone number. Another reads three open articles, uses a calculator and shares the result with a colleague without filling anything in. Your system calls the first a lead and the second ordinary traffic.
• Volume hides fit. In a project for a large software house described in the book, a famous report attracted plenty of form fills, yet fewer than two per cent of those leads matched the company's ideal customer profile. The book is careful about what this proves: it exposed a targeting problem, not that the form alone caused it.
• The gate slows knowledge down. Open knowledge can travel to the hidden buying group through colleagues, search results, AI answers and shared documents. A gated asset makes that movement harder.

Forms still have a job. The book is clear that forms belong after a clear decision to engage, when a buyer asks for a meeting, a proposal, a tailored assessment, access to a private account, a place at a live event, a personal response or saved results that must be delivered securely. Think of a bookshop: you can browse and ask for advice without giving your phone number, but reserving an out-of-stock book reasonably needs one. Same fields, different place, different meaning.

1.3 Why push tactics fail

Push tactics ask for a meeting before the buyer has a reason to want one. They fail for similar reasons.

• Irrelevant outreach makes the next message harder to trust. Gartner's research, cited in the book, found that many B2B buyers actively avoided suppliers whose outreach was irrelevant.
• Personalisation often decorates the same request. Adding a first name, a mention of a new office and a warmer tone does not give the recipient anything they can use.
• Repetition is not value. "Rephrasing the same meeting request does not become more useful because the interval between messages was selected by software."
• Inconsistency costs trust. Gartner found that 69 per cent of the buyers it surveyed encountered inconsistencies between a supplier's website and what its salespeople told them. More exposure to a confused company creates more uncertainty, not more demand.

1.4 Stop adding noise: marketing as a symphony

Most companies are not short of marketing activity. They publish content, run adverts, send emails, post on social media, build landing pages, track analytics and ask sales to follow up. Yet the activity produces little movement.

The book describes it like this: "It can sound like an orchestra warming up, with every instrument working but nobody sharing the same score." The social team discusses one problem, the advert promises something else, the landing page repeats a generic company description, outreach arrives with a third message and sales starts the conversation without knowing what the buyer has already learnt.

"Adding more activity only makes the noise louder."

The answer is to play from the same score, like a symphony. Orchestration gives every part of the system the same mission, context and feedback. Buyer questions shape content, intent affects timing, tool usage improves landing-page copy, and sales conversations reveal gaps in the website. Each instrument plays a different part from the same score. The book calls this shared plan the campaign score: it records the buyer's questions, the help available, the people responsible and the learning that should change their work.

Orchestration is also what makes marketing efficient. When every channel has one clear job and one person owns the whole buyer experience, the team stops paying for duplicate work, mismatched promises and leads nobody can use.

1.5 Being found is not enough

Carlos often puts it this way in his talks: being found is no longer enough. A company has to be understood, recommended and chosen.

The book is cautious about how to get there. A favourable AI answer, a citation or a perfect technical score is not proof of demand or revenue. Carlos's own audit work brought client websites close to 100 in Google PageSpeed Insights, and the book is clear that this gave a stronger technical base without deciding whether those companies appeared in the answers buyers were asking for elsewhere.

What earns the recommendation is useful, accurate knowledge that can be found, understood when it is quoted out of context and traced back to its source. That is the work of the give and connect stages below.

1.6 What we learnt from our own outreach

In September 2026, WitFlow ran its own outbound test. Cold emails that led with a product feature and asked people to click a generic link to a free audit produced almost no replies and no sales conversations. One of the few people who did reply said their company does not open external links. The sample was small, so it does not prove the message was wrong, but the pattern matched what the book argues: a feature-led ask that needs a click before the reader gets anything is easy to ignore.

The live rooms behaved differently. The workshops we ran in London and Manchester, where people came to learn something and stayed to talk, are where the warmest conversations started.

The lesson we took into this playbook: give the value inside the message or the room, keep the next step optional, and put human time where people have chosen to be.

2.1 The method in one paragraph

Non-Gated Demand Orchestration connects four kinds of work. Understand the business and the people it can help. Give them knowledge or tools they can use before identifying themselves. Connect that help to the places they spend time and the questions they ask next, including human guidance when they want it. Learn from appropriate evidence and carry the findings back into the campaign.

2.2 Four principles that hold it together

• These are the team's responsibilities, not stages the buyer must pass through. In the book's words, they are the team's responsibilities, "rather than four compulsory stages for the buyer". Someone can arrive ready for a proposal, use a tool privately or return months later with a colleague.
• Give first, ask only for what the requested help needs. "If you promise an answer, give the answer; if you offer a calculator, show the result; if you publish a guide, let people read it."
• Observe more, intrude less. "Marketing does not become blind when the gate disappears; it must become more observant." Consent and privacy still apply, and anonymous people stay anonymous until they decide otherwise.
• People keep the judgement. "The machine provides capacity, while people provide judgement." AI can research, draft and adapt from shared context. People decide what is true, what is promised and what gets sent.

2.3 The method on one page (from the book)

2.4 The running example used in this section

Illustrative example (fictional, from the book). Nina leads marketing for a supplier that helps B2B teams organise incoming enquiries. Sam handles its sales conversations. Maya, the marketing director from the introduction, is someone their work could help. None of these people or companies is real; the book uses them to show decisions closely without presenting an invented success as a client result.

Stage 1: Understand

Goal: know one buyer, one problem and why your business is qualified to help, well enough that a colleague could explain it back to you.

Core questions

• Who is the person inside the right kind of company, and what are they trying to get done?
• What problem do they describe in their own words, and what does it cost them?
• What have they already tried, and where did the available answers fail them?
• Why does our business work the way it does? What has the owner learnt that is not written down anywhere?
• Where can we give something useful before any commercial conversation?
• What would make us reconsider this campaign?

Concrete actions

• Interview a few people from the audience about a recent situation. Ask what they were trying to do, what prompted the search, where they looked first and what they could do after reading something useful. Avoid asking whether they liked your content.
• Interview the owner and the delivery team. Ask why the business refuses certain projects, why the service is built this way and what happened when an earlier approach failed. The book calls this missing understanding "the soul of the business".
• Separate what a "lead" can mean. Keep identity (who is this?), fit (does the problem fit our market?), interest (are they paying attention to a relevant problem?) and intent and readiness (is something changing, and are they preparing to act?) apart in your reporting.
• Choose one problem. One campaign per problem, unless your offer directly solves several connected difficulties and explaining them together helps the buyer.
• Write the mission and its boundary. State what the campaign will not promise.
• Walk through your current marketing as a buyer, on a phone as well as a computer, and build a gate inventory (see the worksheet below).

Worksheet: the mission sentence (from the book)

"Help [a defined audience in a specific situation] work through [a particular problem] by providing [useful knowledge or a practical tool], so they can [make a concrete decision or take a useful action]."

Beside it, record:

Worksheet: gate inventory (from the book)

Then test each form with the book's five questions:

• Does the buyer receive something genuinely personal or scarce?
• Is personal information required to provide that value?
• Can we give a useful version before asking?
• Have we explained what will happen after submission?
• Would I complete this form if I were the buyer?

Illustrative example. Nina starts with a request to "sell more" and an idea for a guide to managing enquiries. When she and Sam trace one real enquiry, they find it did not vanish. It reached the right department, where everyone assumed somebody else would reply. Her mission becomes: "Help small B2B teams find where responsibility for an enquiry becomes unclear, using an open diagnostic and a worksheet they can discuss internally, so they can agree who takes the next action." Her boundary: the campaign does not promise more enquiries, measure every lost sale or claim that software is necessary.

Metric to watch: fit of the people you reach. What share of the people who use your help match the company profile and roles in the mission? Pair it with a simple test: can a colleague who did not write the brief explain who the campaign helps, which problem it addresses and why the proposed value belongs there?

Stage 2: Give

Goal: give the right people an answer or tool they can use straight away, without a form, so that someone who never buys can still point to what they received.

Core questions

• What should the person be able to understand or do after using this?
• What is the smallest useful experience that answers the question: an explanation, a comparison, a planning resource, a diagnostic or a calculator?
• What information does the tool genuinely need to produce the result, and what would we only want for marketing?
• Where does the result stop being reliable, and have we said so?
• Does it still help if the person decides never to buy?

Concrete actions

• Choose the format that helps the buyer do the task, not the format that is easiest to call a lead magnet.
• Put the help inside the page. Show the result on screen. Offer an emailed copy only as a separate convenience.
• Ask only for the inputs that change the result. Allow answers such as "not agreed" or "I do not know". Avoid inviting confidential or personal information into open text boxes.
• Keep arithmetic in checked logic. If a tool calculates, the formula is fixed and tested. AI can help explain a result; it should not invent the numbers.
• Run two reviews: an expert checks accuracy, and someone less familiar checks comprehension.
• Test the real experience: on a phone, with missing answers, with odd inputs, and with the AI service unavailable. If generation fails, offer the checked worksheet, not an email field.
• Keep authorship clear. A resource that travels between colleagues should keep its title, source and an easy route back to further help.
• Name an owner for maintenance. The resource is a promise that continues after launch.

Worksheet: open value specification

Illustrative examples (fictional, from the book).

• Nina's open diagnostic asks three questions: where does the enquiry arrive, what happens when it is passed on, and how can the team tell that somebody has accepted the next action? Maya's result explains that her team records where an enquiry is sent but not who accepts it, and suggests checking one recent enquiry. She downloads the worksheet without a sales call being a condition of access.
• Ravi's calculator estimates the staff time one recurring report consumes. Four people spending forty-five minutes each, once a week over four weeks, gives twelve person-hours. The page shows the working, lets him change the assumptions and explains that this is current effort, not a promised saving.

From Carlos's own work, as told in the book. WitFlow built an open website audit at webaudit.witflow.co. A company could examine its website's technical preparation, search visibility and presence in AI answers, and download a report without giving a name or contact details. Two or three companies used it, took the report to their internal teams and tried the fixes themselves. Later they came back to explain what had worked and what remained, and they eventually hired WitFlow's SEO and AEO services. The book is clear that this is not a conversion benchmark. What it shows is a sequence worth designing for: receive a result, try to use it, and return with a specific question when help is needed. A historical parallel in the book: the early Michelin Guide, first published free in 1900, helped motorists with fuel, accommodation and tyres before their next tyre purchase.

Metric to watch: the promise kept. What share of people who start the tool or resource reach the promised result, and can they use it? Pair it with voluntary feedback ("Did this help?"), shares and return use. "A useful tool should help a buyer make progress even if the buyer never becomes a customer."

Stage 3: Connect

Goal: get the help to the right people where they already spend time, keep the promise consistent from the first message to the destination, and make human help easy to ask for when they want it.

Core questions

• Where does this audience already spend time, and which channel can reach them before they are looking for a supplier?
• What single job does each channel have in this campaign?
• Does every message lead straight to the help it promised?
• What is the likely next question, and is the answer already waiting?
• How can a buyer ask for a person, and what will that person already know?
• Do we have a genuine reason and permission to contact someone directly?

Concrete actions

• Give every channel one responsibility. "Assign one clear responsibility to each channel and one owner to the connected buyer experience." An advert helps the right person recognise a problem and reach the right destination. An article explains it. A tool helps the person examine their own case. A conversation handles the judgement that remains.
• Teach inside the post. A social post should give a useful idea on its own, with the link as an option, not a condition.
• Check the promise at the point of arrival. Read the advert aloud, open the landing page, and try to find the promised answer without help.
• Rehearse the route with someone who did not build it, from more than one entry point, on a phone and a computer.
• Make outreach worth receiving. Research for relevance, refer only to what the evidence supports, put the useful help in the message, set sequence limits before launch and stop when someone declines or changes the context.
• Use rooms. Workshops, clinics, webinars and small events let people bring their own questions. A place at a live event is one of the moments where a form makes sense.
• Prepare the human conversation. Sales follows four steps: establish fit, discover the real problem (listen for about 80 per cent of the conversation), design the solution together, then return to the beginning in the proposal. "Credentials tell them where you have worked; an explanation shows them how you think."
• Keep legal permission separate from presumed interest. Check the direct marketing rules for your audience and channel. In the UK, the Information Commissioner's Office guidance applies.

Worksheet: route map (one buyer question, end to end)

Add one extra row for a colleague who receives the resource out of context: can they understand it without visiting your website?

Illustrative example (fictional, from the book). Nina's first advert led Maya to the supplier's general website, where she could not find the promised diagnostic, and a demonstration request appeared before the answer. Nina repairs the route so the advert leads straight to the diagnostic. Separately, Sam sees a public announcement that a company is adding a second sales team. Instead of offering a demo, he writes a short note that teaches the difference between forwarding an enquiry and accepting responsibility for it, with a direct link to the open worksheet. Reading it needs neither a reply nor an appointment. When the recipient replies with a different problem (duplicate replies when someone is away), Sam answers that question first.

Metric to watch: buyer-requested conversations and the context they bring. Count conversations the buyer asked for, and note what they arrive with: a result, a specific question, colleagues already involved. Track broken promises found in route checks as a second number.

Stage 4: Learn

Goal: turn what people do and say into decisions, owners and changes, so the next buyer gets better help than the last one.

Core questions

• What did we observe, and what else could explain it?
• Which decision would this signal change? If none, why are we collecting it?
• What is the smallest change the evidence supports, and who owns it?
• Which other assets carry the same mistake?
• When will we check whether the change helped, given how long buyers take to decide?

Concrete actions

• Give each signal a job before collecting it. Record what it shows, what it cannot establish, which action it could change and who decides.
• Separate observation, interpretation and permission. An aggregate pattern can justify clearer wording. Contacting a named person needs a different level of evidence and permission. The book's rule: "a visit does not create permission to contact someone."
• Run a short review that ends in decisions. Weekly is a good starting rhythm. Each item ends as change, investigate or leave alone, with an owner and a review point.
• Change every affected asset, not just the newest one: page, advert, posts, outreach, tool instructions and sales material.
• Use five levels of evidence: usefulness, buyer progress, intent, conversation and commercial result.
• Agree the commercial test in advance: a baseline, a spending limit and a review date that suits the buying cycle.
• Keep what you learnt when the campaign ends: questions that mattered, assumptions that failed, resources worth keeping public.

Worksheet: learning record (from the book)

Illustrative example (fictional, from the book). Sam receives a reply about duplicate responses when someone is away. At a webinar, an attendee asks the same thing. Nina holds the next article, adds a cover arrangement and a visible response status to the worksheet, asks someone in delivery to check it, and updates the article, the diagnostic's result guidance, the social post and Sam's material. Her review question: can willing users now agree what happens during an absence? She also notes that two questions are enough to inspect an omission, not a survey of the market.

Metric to watch: time from finding to fix. How long does it take for something the team learns to reach every asset buyers actually use? Pair it with the share of review decisions completed. "Stop treating reporting as completed work when no decision or improvement follows it."

Both plans assume one campaign, one audience and one problem. They are starting sequences, not promises. In the book's words about the first month: "It is not a promise of revenue within a month."

3.1 Before day 1: the first working session

• Bring one live campaign and someone who knows what buyers ask after responding to it.
• Read its public promise together. Open the destination and try to get the promised answer without identifying yourselves.
• Record the first point where the answer disappears, the subject changes or the next step needs a colleague to explain it.
• Choose one repair within the team's authority, for example showing the result before offering an emailed copy.
• Write down the old promise, the repair, the owner and what you will check afterwards.

3.2 The 30-day plan

Small team roles. One person may hold several roles, but name them: owner of the whole buyer experience, accuracy checker, resource maintainer, and the person who reviews what happens after publication. Sales and delivery need a route into the review.

Tools. "You do not need my software to make the first campaign work," Carlos writes. A shared document, a page on your existing website and a short record of questions and changes are enough to start.

3.3 The 90-day plan

The book suggests that a ninety-day period can define the team's programme, but it "should not become a deadline imposed on the buyer's readiness." This plan extends the first month into a full cycle.

Days 1 to 30: build and launch one campaign. Follow the 30-day plan above.

Days 31 to 60: deepen the help and open the rooms

Days 61 to 90: review honestly and decide

Conditions for changing the plan (from the book). If the audience is irrelevant, review distribution and the promise. If relevant people cannot use the result, repair the resource before increasing spend. If useful conversations keep failing because the paid offer does not fit, revisit the offer. If the agreed budget runs out without enough evidence, pause or narrow the campaign rather than using the philosophy as a reason to keep spending.

Copy these into a shared document. Each one has a blank version and, where useful, an illustrative row using the book's fictional enquiry-handover campaign.

Template A: Buyer-understanding canvas

Fill one canvas per campaign. Mark every entry as evidence (with its source) or assumption.

Template B: The "give" asset menu

What to give at each point in the buyer's thinking. The book uses awareness, consideration, decision and action to organise the help, not to ration access. A buyer may want a person at any point.

Ask before giving anything: Does it answer a question this audience actually has? Can the person use it without us? Would we be comfortable if they used it with a competitor? If the answer to the last question is no, the help may be too thin, or tied too closely to a sale.

Template C: Non-gated content calendar

One campaign, four weeks. Every row must state what the reader gets without clicking or filling in a form.

Illustrative example (fictional, based on the book's enquiry-handover campaign):

Template D: Connect playbook (consent-based follow-up and rooms)

D1. Match the response to the evidence

D2. Follow-up rules

• Send what you promised first. The recording, the worksheet, the answer to their question.
• Answer the question they asked, not the one in your sequence.
• One reason per message. Each follow-up adds new help (a clearer example, a comparison, a relevant guide). If it only repeats the ask, do not send it.
• Set limits before launch: how many messages, over how long, and which replies stop the sequence.
• Respect a no, and treat silence as ambiguous. Do not escalate, and do not ask the person to explain themselves.
• Make the ask a reply, not a click. For example: "Would it help if I sent you the worksheet we used in the session?" Put any link where the reader can use it without replying first.
• A person reviews every outbound message for the reason for contact, the facts, the value offered and whether the recipient is suitable.
• Make objections stick across every connected system, including manually kept lists.

D3. Rooms and events

D4. The human conversation

Template E: Learn dashboard with leading indicators

The book organises evidence into five levels. Name an owner and a definition for each measure, and write down what it cannot tell you.

Dashboard rules

• Keep the evidence beneath any score visible: events, dates and uncertainty, not just a coloured label.
• When you show a rate, show both numbers that produce it.
• Keep definitions the same before and after you remove a gate.
• Ask buyers what helped them reach the conversation, and record it next to the tracked data.
• Separate mentions, citations, visits, useful interactions and commercial outcomes when reporting on AI and search visibility.
• Do not keep changing the success measure until the result looks good.

A note on comparing gated and open versions. The book offers a deliberately simplified hypothetical: a gated resource produces 100 contacts, ten relevant conversations and two customers; an open version produces 20 contact records, eight relevant conversations and three customers. Looking only at contacts makes the open version look weaker. The book adds that this does not prove opening the resource caused the difference; it shows why a form count alone cannot decide.

WitFlow is a demand orchestration OS (operating system). Carlos built it to connect the four kinds of work in one place, and the team uses it in its own work. You can run this method with a shared document and the tools you already have. The book is explicit about that, and section 3 is written so you can.

What a connected system changes is the amount of context people have to carry by hand between research, content, pages, social, outreach and review. It does not change who is responsible. The company remains responsible for what it tells people and what it does with their information.

How to judge any system, including ours. Follow one task through it. Can you see how the research informs the page, where a person checks the work, and how a buyer's question reaches a later improvement? Include the cost of maintaining the experience as well as buying the software. An extra feature is useful only when it solves a difficulty your team actually has.

If you would like to see how we run one campaign this way inside WitFlow, you are welcome to ask us at witflow.co.

THE GIVE, DON'T ASK FORMULA

The idea: Help buyers before you ask them to buy.

Why it matters

• Buyers learn on their own first, with search, AI assistants and colleagues.
• A form fill is not intent. Gating turns access into fake demand and hides the real buying group.
• More activity only makes more noise. Marketing works like a symphony when every channel plays from the same score.
• Being found is not enough. You need to be understood, recommended and chosen.

The method: four kinds of work, in a loop

• UNDERSTAND. One buyer, one problem, one mission. Leave with: the problem, its evidence and a clear mission. Watch: how many of the people you reach fit the mission.
• GIVE. An open answer or tool people can use without a form. Leave with: help that works even for people who never buy. Watch: how many people reach the promised result and can use it.
• CONNECT. Each channel has one job. Every promise leads straight to the help. Rooms, consented follow-up and human help when the buyer wants it. Leave with: a route that keeps its promise. Watch: conversations the buyer asked for, and the context they bring.
• LEARN. Observation, then decision, owner and review date. Change every affected asset. Leave with: a supported decision. Watch: time from finding to fix.

Then return to understand. The learning changes the next campaign.

The rule for forms: ask only when the buyer has chosen something that needs it, such as a meeting, a proposal, a tailored assessment or a place at an event.

Measure five levels: usefulness, buyer progress, intent, conversation, commercial result.

Never: gate, blast, bait, or count vanity.

Start small: one campaign, 30 days, one owner of the whole route.

Keep in mind: "The machine provides capacity, while people provide judgement."

The book

Carlos Justino, Give, don't ask: Give away your best knowledge and become the obvious choice (2026). The method, the four kinds of work, the campaign score, the templates marked "from the book" and all quotations come from it. The fictional characters Maya, Nina, Sam and Ravi come from the book. The software house, insurance company, landing page and website audit stories are anonymised accounts from Carlos's own work, as the book tells them.

Research cited in the book

• Gartner, sales survey finding that 61 per cent of B2B buyers prefer a rep-free buying experience, June 2025 (survey of 632 buyers, August and September 2024). Also the source for the findings on website and sales inconsistency and on irrelevant outreach.
• 6sense, B2B buyer experience report, 2025 (nearly 4,000 buyers). Preference and research before seller contact; LLM use alongside vendor material.
• Edelman and LinkedIn, B2B thought leadership impact report, 2025. Expert content used by stakeholders outside the seller's visible contacts.
• John Dawes, the 95-5 rule, LinkedIn B2B Institute and Ehrenberg-Bass Institute. A planning principle; the proportion varies by market.
• Cognism and Refine Labs, practitioner accounts of open content and demand creation, capture and conversion. The book credits them as prior practice: "The name does not mean I invented giving value, demand generation or coordination between marketing and sales."
• Michelin, history of the Michelin Guide.
• Google Search Central, AI features and your website; spam policies for Google web search.
• Bing Webmaster Tools, AI Performance documentation.
• Information Commissioner's Office (UK), guidance on storage and access technologies and on business-to-business marketing.

Survey findings describe the buyers surveyed. They do not show that one marketing method causes a sale. Check current platform documentation and the rules that apply to your market before you implement anything.

WitFlow's own experience

Section 1.6 summarises WitFlow's own outbound test in September 2026 and the workshops in London and Manchester. It is a qualitative lesson from a small sample, not a benchmark.

Licence

Share this playbook freely and use the templates in your own work. Please keep the attribution to Carlos Justino and the book.