The Forcing Function

Research Engine

Forensic Research Plan methodology

Pulls earnings calls, regulatory filings, press releases, leadership changes, and market signals. Outputs a prioritized signal inventory for each target account.

Intelligence Funnel

Signal compression to forcing function

Distills raw research into a single Primary Forcing Function. The business pressure forcing a prospect to act. Locks the risk frame an executive will respond to.

Account Architecture

Tier-1 account blueprints

Maps the buying committee, assigns persona-level friction, sets the engagement sequence, and locks the outbound narrative.

Tier-1 Execution

Send-ready outbound artifacts

Produces final cold emails, LinkedIn messages, call scripts, and multi-thread follow-up sequences. Calibrated to each persona's role, incentives, and likely objections.

Tier-3 Sequence Engine

Automated nurture architecture

Multi-touch sequences for lower-priority accounts with angle rotation, thread continuity rules, and CTA variation to prevent messaging fatigue.

Measurement Engine

Pipeline health tracking

Tracks sequence activity, reply rates, meeting-to-sequence conversion, tier movement, and total pipeline velocity across the full portfolio.

How It Works

Locked prompts. Every component has a defined role, output standard, and known failure mode.

Each tool stands alone. Components run independently and feed structured outputs to the next.

Research and judgment stay separate. Data tasks are isolated from strategy tasks. Reliability holds.

Built On

Tech Stack

Anthropic Claude (API and Code), custom Claude skills, MCP-aware tool design, RAG patterns and eval frameworks.

Frameworks

Tenbit++ for account intelligence, Forcing Function for outbound design, Intelligence Funnel for committee mapping, Forensic Research Plan.

Distribution

Four installable Claude skills, open source on GitHub. Used daily across enterprise SaaS orgs. Built and sold by working sellers.

System Architecture