AGENT SKILL

b2b-timing-engine

Design recurring B2B buyer-presence systems that keep a company remembered until pain becomes urgent, using time-based visibility cadence instead of unreliable intent signals or linear funnel assumptions. Use when buyers know the company but deals stall, follow-up is inconsistent, the team waits for triggers, expands markets too early, or wants a 4-6 week account visibility rhythm.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1.6k
Forks
491

01 前言 Front Matter

name
b2b-timing-engine
license
MIT
metadata
{ "tags": "b2b-sales,sales,timing,follow-up,pipeline", "version": "0.1.0", "category": "Marketing", "displayName": "B2B Timing Engine" }
description
Design recurring B2B buyer-presence systems that keep a company remembered until pain becomes urgent, using time-based visibility cadence instead of unreliable intent signals or linear funnel assumptions. Use when buyers know the company but deals stall, follow-up is inconsistent, the team waits for triggers, expands markets too early, or wants a 4-6 week account visibility rhythm.
compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.

03 SKILL.md 正文

B2B Timing Engine

Use this skill when the company is known and understood but is not present when buyers become ready. The goal is to engineer repeated visibility across the real target market so buyers remember the company when pain spikes.

Source Traceability

Primary source: Unf*ck Your Sales by Jakob Greenfeld, especially the "Timing", "Diagnostics", "The Trigger Fallacy", "The Annoyance Fallacy", "The Shiny New Market Fallacy", "The Funnel Fallacy", "The 95-5 Law", and "Engineering Timing" sections.

Diagnostic Signals

Timing is likely the constraint when:

  • Buyers know what the company does but engage only sporadically.
  • Outreach is based on replies, opens, or supposed intent triggers instead of a reliable presence cadence.
  • The team worries about annoying the market before the market reliably remembers the company.
  • The team wants to chase a new segment before fully covering the proven one.
  • CRM attribution overstates one touch while ignoring months of buyer memory building.

Timing Check

Audit the target account list:

  • Has every viable buyer seen or heard from the company in the last 4-6 weeks?
  • Is last touch tracked by buyer or account?
  • Are touches distributed across useful channels?
  • Is the current segment saturated before considering a new market?

If coverage is missing or inconsistent, timing is the likely constraint.

Workflow

1. Set The Visibility Window

Use a 30-45 day window as the default. Every viable buyer should receive or see at least one relevant touch inside that window.

2. Build The Timing Ledger

Track:

  • Account.
  • Buyer.
  • Last touch date.
  • Channel.
  • Message or asset.
  • Next planned touch.

Track last exposure, not only last reply.

3. Rotate Touch Types

Use a mix of channels that create low-friction familiarity:

  • Short outbound notes.
  • Useful follow-up with proof or perspective.
  • Manual DMs.
  • Calls where appropriate.
  • Retargeting or account-based ads.
  • Founder or company content the buyer is likely to see.

4. Stay With The Proven Market

Do not expand into a new segment because the current one feels boring. Expand only after the current viable market has sustained coverage and a clear reason to believe the constraint is no longer timing.

Output Format

# B2B Timing Engine

## Market Coverage
- Segment:
- Accounts:
- Buyers:
- Current 30-45 day coverage:

## Timing Ledger Fields
| Field | Definition |
|-------|------------|
| Account | |
| Buyer | |
| Last touch | |
| Channel | |
| Next touch | |

## Cadence Plan
| Buyer Segment | Touch Type | Frequency | Purpose | Owner |
|---------------|------------|-----------|---------|-------|

## Risks
- Intent-signal traps:
- Over-contact risks:
- Market expansion risks:

Quality Bar

  • Do not build the plan around third-party intent data unless there is strong evidence it predicts buying readiness.
  • Do not treat one ignored email as proof that the market is annoyed.
  • Do not optimize linear funnel attribution for long, nonlinear B2B decisions.
  • Do not expand markets before the proven market has repeated coverage.
  • Make presence systematic, measurable, and boring enough to compound.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-review-with-annotations

Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-find-and-synthesize-context

Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-update-docs

Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-records

Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-interactive-html

Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-collaborate-threads

Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.

★ 1.6k