name: b2b-playbook description: Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance. Use when the user needs a concrete plan, checklist, template, software shortlist, or next action; do not use for generic inspiration or legal advice.

B2B Playbook

Produce a usable artifact or decision, not broad advice.

Route the task

If the master index marks a requested topic as planned, read the relevant domain README for its scope, decisions, build order, and interfaces. State that no complete tactic playbook is published yet; do not fabricate one or silently substitute an adjacent tactic.

All maintained playbook, tool, working-file, reading-source, and Skill content is in English. The root README is English. A Chinese entrance lives in README.zh.md and must stay a full mirror of coverage counts.

Working rules

• Begin with the buyer, account, business problem, current alternative, and observable trigger.
• Label important judgments as fact, observation, assumption, or to validate.
• Write unknown and a discovery action when evidence is missing.
• Use the playbook's template and label every external case with a source and date. If the playbook links a file in templates/, point the user there for Google Sheets/Docs/Slides; do not paste a third-party member template.
• For software selection, prefer a qualified AI-native product or modern infrastructure over a legacy default, but never treat novelty or AI marketing copy as evidence of fit.
• Give each tool one primary category, state a real limitation, label established benchmarks, and disclose when a product is maintained by the repository owner.
• For reading sources, use RESOURCES.md. Treat grades as editorial evidence, not a ranking. A newsletter is not a case study and does not override a published playbook.
• When adding a third-party web link, preserve existing query parameters and append ref=b2b-playbook to the query string before any fragment. Do not add it to repository-internal or canonical-source links.
• End with a concrete next action and the metric that will evaluate it.
• Never invent customer facts, contacts, proof points, legal requirements, or performance claims.
• Do not expose or request credentials, customer lists, private contacts, or unapproved sources.

Default output

Unless the user requests another format, produce:

1. the decision or recommended operating path;
2. the evidence supporting it;
3. assumptions and unknowns;
4. a copyable working artifact;
5. a pre-flight checklist;
6. the next action and review metric.

B2B Playbook

A practical field guide for founders and small B2B teams finding customers, explaining their product, and helping people succeed with it.

Read the library on Mintlify · 中文简介 · Browse the playbooks

Last reviewed: 2026-09-06 · Reading edit: 2026-09-12

You might be writing a first outreach email, preparing for a customer call, or trying to understand why a campaign did not work. Pick the guide for that job. Work through an example, copy a useful worksheet, and adapt it to your situation. You can come back for the rest.

Free to read. Working files can be copied for your team’s private use under the reuse terms.

Start with the work in front of you

If you would like a guided start, these three paths pair the reading with something you can use:

Already know what you need? Jump straight to a guide:

What you will find

Read it like a book

Pick a short path or jump straight to the guide you need.

• First customers: Idea discovery → validation → ICP → first ten customers.
• A clearer offer: Positioning → messaging → homepage → demo.
• A repeatable plan: Channel strategy → content strategy → GTM planning → measurement.

The nine chapters

Agent Skill

npx skills add weilun88313/B2B-Playbook

Try this task:

Use $b2b-playbook to review these five target accounts.
Explain who fits, what is still unknown,
and one sensible next step for each.

The Skill provides guidance. It does not send messages or change your CRM. Read the instructions.

About this library

I’m Ivan Xu, the founder of Lensmor. I maintain B2B Playbook to make the everyday work of building and marketing a B2B product easier to think through. The aim is useful explanations you can bring to a real task, whether you are doing the work yourself or alongside a team.

• English is the main language. README.zh.md is a separate Chinese introduction, updated alongside this page.
• Read comfortably on Mintlify. GitHub holds the source and revision history.
• Illustrative examples are labelled. Company cases link to dated primary sources; reported results have not been independently audited.
• Tools are not paid placements. Lensmor is my product, and its entry says so.
• Third-party links use ref=b2b-playbook to identify the referral source. It is not an affiliate code.
• This is a living reference. A guide can be a useful starting point while still leaving room for your judgment and a better example.
• The repository is public to read; its content is not released under an open-source license. The reuse terms explain what you can copy or republish.

Current coverage: 131 published playbooks · 56 working files · 43 curated tools · 20 reading sources · 9 domain guides

You can make a private working copy of the templates. Republishing the content requires permission; see the copyright and reuse terms.

If a page helps, share it with someone working on the same problem, or star the repository to keep it handy. If something is confusing, tell me which step lost you. A question from real use is a useful starting point for the next edit.