본문으로 건너뛰기
cccskills
무료GitHub에 공개

account-based-marketing

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md4.8 KB
  • references/sources.md1.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Account-based marketing

Account-based marketing inverts the usual model: instead of generating leads and finding out which accounts they came from, you choose the accounts and work them. It is a good fit for a narrow set of businesses and an expensive mistake for the rest.

Qualify the model before adopting it

It works when deal sizes are large enough to justify per-account effort, the addressable market is small enough to enumerate, buying groups have several people, and sales cycles are long enough for sustained effort to compound.

It does not work when the deal size cannot carry the cost, when the market is too large to name, or when marketing and sales will not actually coordinate. That last one is the usual failure: the tooling gets bought, the account list gets built, and the program becomes a more expensive way to run the same campaigns.

Run the arithmetic first. Total program cost divided by the number of accounts, against expected deal value and a realistic win rate, tells you the tier structure you can afford — or that you cannot afford this at all.

Build the list from fit and evidence, then hold it still

Start from the accounts that already look like your best customers — not by revenue but by why they bought and whether they stayed. Add observable signals: hiring, technology in use, funding, regulatory pressure, a change in leadership.

Then commit. A list that churns quarterly cannot compound, and compounding is the only reason this model beats broad demand generation. Agree the list with sales and get their explicit acceptance, because a list sales does not believe in is a list sales will not work.

Map the buying group, not the contact

Purchases at this size are made by several people with different concerns: the person with the problem, the person with the budget, the person who will operate it, and whoever can veto on security, legal or procurement grounds.

Reaching one champion and mistaking that for account coverage is the most common structural error. Track how many roles you have reached within each account, and treat single-threading as a status that needs fixing rather than a warning to note.

Tier the effort, because one-to-one does not scale

  • One-to-one for a small number of the highest-value accounts: genuinely bespoke research and content, executive engagement.
  • One-to-few for clusters that share an industry or a problem: shared narrative, light customization per account.
  • One-to-many for the rest of the named list: programmatic personalization at segment level.

Being honest about which tier an account is in prevents the common outcome where everything is nominally one-to-one and nothing is actually customized.

Coordinate, or the account experiences three campaigns

The account should see one coherent effort. That requires marketing and sales working the same plan, with agreed timing, agreed messaging, and an agreed sequence of who reaches out when.

Set up a shared cadence between the two teams for the tiered accounts and hold it. Without that meeting the program degrades into marketing sending things and sales prospecting separately, which is the status quo with extra software.

Measure account progression, not lead volume

Lead counts are the wrong instrument. What matters is how accounts move: coverage of the buying group, engagement across it rather than by one person, movement into and through pipeline, and eventually win rate and deal size against non-target accounts.

Expect the timeline to be long. Judging an account-based program on a quarter is judging it before any of its mechanism has had time to work, and canceling it there is the most common way the investment is wasted entirely.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Adopt the model without checking whether the deal size carries the per-account cost.
  • Run a target list sales has not explicitly accepted.
  • Treat one engaged champion as account coverage.
  • Judge the program on lead volume, or on a single quarter.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

cbrock84의 스킬 모두 보기

이 스킬의 문제 신고