Four sections: GitHub setup, how the agentic system works, what's on the agenda right now, and reference docs.
The entire B2B consulting practice lives in one repo. All client files, proposals, rules, and notes are versioned here. No Notion, no Google Drive for working files — everything is in the repo.
If you don't have it yet:
Things change fast. Before any session, pull to get the latest state.
Always create a branch first. Claude Code enforces this too.
call-notes.md — source of truthproposal.html — internal + externalmodule-*.html — one-pagerspricing-philosophy.md — pricing modelmodule-registry.md — what we buildicp.md — ideal client profiletodo.md — active pipeline taskslessons.md — what we've learnedOpen Claude Code from inside b2b/ and it already knows everything — client names, confirmed pains, pricing model, pipeline state. You don't explain context; you just give it a situation. Everything you do goes through a workflow, not a single command. You trigger it, Claude chains through the steps, asks you questions at key gates, and updates the right files automatically.
Reads all client files, todo.md, and pipeline.json and gives you a brief you can read in 10 seconds. Stale clients are flagged automatically. Here's what it actually looks like:
Give it a name, company, and LinkedIn URL. Claude reads our internal docs first — ICP criteria, modules, pricing — then researches the person and company externally. It flags ICP mismatches before you're in the call, maps their likely pains to our modules (Most Likely / Secondary / Longest Shot), writes 5 tailored discovery questions, and builds a decision tree for how to handle the call.
We ran this for Antu before the Lamosa call. The output was a 10-section brief — ICP assessment, Antu's background and what drives her, company snapshot, confirmed pains, agenda, decision tree, tech stack, red flags, what to bring, what to do right after. → See the Lamosa meeting prep
This is the most important chain. Paste in your notes — transcript, bullets, anything — and the system runs from there. You don't decide the next step; Claude asks you at each gate.
The single document that answers "what are we building, for whom, at what price, and where does the pipeline stand?" Not a deck — an intelligence report built from all client data. The pipeline tables load live from pipeline.json, so they're always current without a manual rebuild.
/venture-signal after a significant new signal (new client, confirmed pain, product decision). Pipeline tables never need a rebuild — they're always live./adapttoai-review runs automatically and drops a prioritized action list into the AdapttoAI Telegram group. No trigger needed.
Updated Apr 4. Two strategic topics to align on first, then the commercial pipeline below.
New model built April 2026: module-based annual fee, 12-month minimum, no separate implementation fee. You haven't reviewed it yet. This isn't just a pricing doc — it's a strategic shift toward recurring revenue. The retainer model in your MAGG proposal ($140K MXN/mo, time-based) is the old model. We need to align before Lamosa and before Omar replies.
File: b2b/docs/pricing-philosophy.md — read the prepay table and the floor/ceiling section. The goal is to make every engagement a subscription, not a project.
Two open questions: (1) Which features in the MVP prototype map to the modules we're proposing? Does it reflect what we're actually building? (2) Neither of us has a shared view of which modules are proposed to which client — we need this before any new client call.
Tuesday call with Antu (+ possibly Doménico). Goal: verbal agreement to move to formal proposal. Three things to lock before the call: (1) which pricing tier to lead with — Quick Win $12–17K vs Core $20–28K, (2) Mexico/Peru sign-off — can San Lorenzo Peru decide independently?, (3) who asks what (Giuseppe, you, Diego).
Proposal sent. Follow up no earlier than Apr 8. The key question isn't the math — Claude can run /pricing-workflow magg and generate module-based numbers in minutes. The real question is strategic: do we shift MAGG to the new subscription model, or hold the retainer approach for ops-heavy engagements? Decide with Giuseppe before Omar comes back, so we're aligned on how to respond.
Pre-proposal exists but isn't finished. Stalled for 7+ days. Blocker: WhatsApp API access path needs to be confirmed before sending. Who owns this client and closes the brief?
Pre-proposal sent March 2026. No reply. 33+ days of silence — going cold. Send this now. Main message to Ferdi, plus two short forwarding snippets for his After-Sales Manager and Technical Lead (one-pagers already built).
→ Full pre-proposal · → One-pager: After-Sales · → One-pager: Technician App
Message sent Apr 3 had old Netlify links. Resend now with updated links. Same message, same forwarding snippets — links now point to Cloudflare Pages.
→ Full pre-proposal · → One-pager: Sales · → One-pager: Technical Matching
You won't need these every session, but they're the source of truth the workflows read from. If something doesn't add up in a proposal or pricing conversation, these are the first files to check.
New pricing model built April 2026. Module-based annual fee, 12-month minimum, no separate implementation fee. Team rates, complexity tiers, build cost estimates, competitor benchmarks, and a hidden labor cost calculator. The Learning Log at the bottom gets updated after every deal — won or lost.
File: b2b/docs/pricing-philosophy.md
Canonical definitions of every module: A1 (Discount Approval), A2 (Quote Gen), A3 (Spec Matching), B1–B4 (Ops Intelligence). Each entry has scope, complexity tier, ERP dependencies, and open questions to confirm before pricing. Read before any pre-proposal.
File: b2b/docs/module-registry.md
Every client folder has one. Confirmed pains, discovery answers, open questions, pipeline stage, internal language. Claude reads this before doing anything for a client. Updated automatically via /client-intake — never edit manually unless you're correcting something specific.
Location: b2b/clients/[client]/call-notes.md
Holds current stage, next action, and partner sync items for every client. Drives the Venture Signal tables and the Monday review. Updated automatically after every /client-intake. Edit manually only if you have context from outside the system (e.g. Omar texted you back). Update next_action, status, and the updated date.
File: b2b/venture-signal/pipeline.json