B2B Biz IQ Pack

Asset README for business intelligence handoff.

Download the Drive zip, unzip it locally, inspect the included Graphify graph, then use Claude Code to turn the source corpus into upmarket B2B judgment.

Download the pack

The recipient should use the Google Drive zip. Local links inside this file only work after the zip is downloaded and unzipped on their machine.

Full pack zip

Why it matters

This is the shareable package. It contains the generated graph, graph report, graph JSON, raw knowledge corpus, Claude Code context file, and this README.

How to use it

Download the zip, unzip it, open START_HERE.html, then work from the unzipped folder so every local graph and source link resolves correctly.

Graph assets

The graph is already included. Graphify is only needed if the recipient wants to rebuild, extend, or install query-first assistant behavior.

GRAPH_REPORT.md

Why it matters

Readable map of the corpus: 13 files, 1021 nodes, 1358 edges, and 73 communities. It is the best first pass before opening the visual graph.

How to use it

Ask Claude Code to identify buyer-pain clusters, commercial assumptions, weak proof, enterprise discovery gaps, and upmarket offer themes.

graph.html

Why it matters

Visual navigation layer for clusters and relationships. Useful when the report feels too linear.

How to use it

Search for terms like ICP, offer, discovery, upmarket, orchestration, proof, scope, and enterprise. Follow dense clusters back to source files.

graph.json

Why it matters

Structured graph data. This is the file to reference when Claude Code should inspect nodes, edges, labels, and relationships directly.

How to use it

Use it with GRAPH_REPORT.md when asking for ranked themes, cross-source links, missing assumptions, and source-backed business decisions.

Source assets

These are the core links and local files. Each one has a purpose inside the handoff.

Raw knowledge inventory

Why it matters

Shows the 13 files used to create the graph, including discovery, upmarket motion, offer construction, process selling, macro-signal outbound, and orchestration.

How to use it

Use it as the table of contents when a graph cluster needs source context or when rebuilding the graph from raw knowledge.

GTM Skills

Why it matters

Commercial operating material for ICP, targeting, qualification, discovery, outbound, follow-up, and deal control.

How to use it

Use it to convert graph insights into buyer profiles, acquisition paths, outreach angles, discovery flows, and written scopes.

Why it matters

Builds or refreshes the graph output from the raw source folder. Not required just to open the existing graph.html.

How to use it

Install Graphify only if you want to rebuild the graph, add new raw notes, or make Claude Code query the graph before reading files manually.

BenjaminPrinter

Why it matters

Market-language feed for operator phrasing, objections, positioning, and B2B sales judgment.

How to use it

Capture useful phrases and examples into the source folder, then regenerate the graph if the new material changes the map.

Why it matters

Quality control for public-facing pages, offer docs, pitch pages, and visible copy so the final assets do not look generic.

How to use it

Use only after the business logic is clear. It is a presentation and copy hygiene layer, not the source of the business strategy.

Core articles

These are the three renamed Termsheetinator assets. The local raw files are the reliable source. The X links are retained for origin context.

Going Upmarket Confidently Guide

About: How to go upmarket and charge high confidently. Use it to understand why bigger buyers pay for risk reduction, sharper positioning, and clearer business outcomes.

How to use: Apply it when pricing, framing a 30k-100k offer, deciding which clients are worth pursuing, or rewriting a weak offer around executive value.

Discovery as Due Diligence

About: Why normal sales does not work in enterprise. Enterprise buying requires diligence on pain, authority, budget, timing, politics, risk, and approval paths.

How to use: Use it to turn discovery from a pitch call into a verification process. The goal is to learn whether the problem, buyer, urgency, and decision path are real.

Orchestrator Advisory System

About: How to use AI, vendors, and operator networks to fulfill advisory outcomes for 30k-100k clients without pretending the founder must personally build every piece.

How to use: Use it when designing the delivery model: what the client buys, what AI accelerates, what vendors execute, what the advisor owns, and where margin comes from.

Graphify install

There are two modes. Use the existing graph with no install, or install Graphify if you want to rebuild and query the graph through the assistant workflow.

Use existing graph

No Graphify install required. Download the Drive zip, unzip it, open graphify-out/graph.html, and reference GRAPH_REPORT.md plus graph.json inside Claude Code.

Install for rebuild or query-first workflow

uv tool install graphifyy graphify install cd b2b-biz-iq-pack-clean claude # inside Claude Code, from the pack folder: /graphify .

Package name detail

The official PyPI package is graphifyy with a double y. The command remains graphify.

Use inside Claude Code

This is the recipient-side path. It assumes the Drive zip has been downloaded and unzipped locally.

Start from the pack folder

cd /path/to/b2b-biz-iq-pack-clean claude

Load the context

Read @CLAUDE.md, @graphify-out/GRAPH_REPORT.md, @graphify-out/graph.json, and @sources/RAW_KNOWLEDGE_INVENTORY.md. Use the graph and source files as business-intelligence context for a software engineer learning midmarket and enterprise B2B sales judgment.

Question 1

Using @graphify-out/GRAPH_REPORT.md and @graphify-out/graph.json, explain why every deliverable, mechanic, and feature needs to be anchored to an outcome that a [CFO/CTO/CEO/VP] cares about. Translate this into a practical offer-design rule for a software engineer selling midmarket or enterprise work.

Question 2

Using the graph and raw source files, explain how to run a sales cycle with a midmarket ICP when I am strong technically as a software engineer but weak in due diligence, procurement, and enterprise buying cycles. Break it into discovery, stakeholder mapping, proof, procurement, pricing, and next steps.