Sam's Getting Started Guide

First-hour onboarding for Sam

Version 1 · June 29, 2026 onboardingsam

Content

---

slug: sams-getting-started

title: Sam's Getting Started Guide

parent_slug: how-we-work-together

sort_order: 1

---

# Sam's Getting Started Guide

_Parent: [How We Work Together](./how-we-work-together.md)_

The first hour. What to read, what to set up, and how to use this wiki with claude.ai.

---

## Your first hour

### Step 1 — Read these 5 pages (~15 min)

These are the foundation. Read them top-to-bottom before your first call:

1. [The Confluxion Point Story](./confluxion-story.md) — voice, positioning, what we say and don't say

2. [The 3 "Why Us" Anchors](./three-why-us-anchors.md) — memorize these three sentences

3. [Standard Engagement: $22K + $25K](./standard-engagement.md) — the pricing structure and rationale

4. [Cold Call Opener](./cold-call-opener.md) — the first 30 seconds

5. [Objection Responses](./objection-responses.md) — the most common pushback + how to answer

### Step 2 — Set up your claude.ai with the wiki (~20 min)

This connects Claude to the live wiki on GitHub so every chat Sam has knows the whole playbook.

1. **Sign in** to claude.ai with your Confluxion Team seat

2. **Settings → Connectors → GitHub** → connect your GitHub account

3. **Authorize** access to the `addisonhoward1/confluxion-crm` repo (read access is enough)

4. **Create a new Project** called "Confluxion Sales"

5. **Paste the project instructions** (Addison will share these — they live in the wiki under "How We Work Together")

6. **Test it:** start a new chat in the Project and ask *"What are the three Why-Us anchors?"* — Claude should pull them from this wiki and answer in our voice

7. Done. Use that Project for all sales work.

### Step 3 — Bookmark these in your browser (~2 min)

- This wiki: [confluxion-crm.vercel.app/wiki](https://confluxion-crm.vercel.app/wiki)

- Active deals: [confluxion-crm.vercel.app/wiki/active-deals](https://confluxion-crm.vercel.app/wiki/active-deals)

- Companies index: [confluxion-crm.vercel.app/wiki/companies](https://confluxion-crm.vercel.app/wiki/companies)

---

## Daily workflow

### Before every call

- Open the **company page** for the prospect (or create one — see below)

- Re-read the **3 Why-Us anchors** (don't paraphrase — memorize)

- Check **active-deals** for status + recent decisions

### After every call

- **Update the company page** — new contacts, decisions, what they said, next step

- **Move the deal status** on active-deals if it changed

- **Add a row to the call notes log** (Date · Who · What was decided · Next action)

### When you learn something new

- If it's about a **specific company** → add it to that company's overview page

- If it's about **how we sell or position** → add it to the relevant playbook page (or create a new one)

- If it's about **a deal in flight** → add it to the deal page under the company

---

## How to edit the wiki

> **The wiki is read-only in the UI.** All edits happen through GitHub.

This sounds annoying — it's actually clean. Here's why and how:

1. **Why** — every edit is a git commit. We get version history, the ability to review changes before they go live, and Claude can read the wiki in real-time via the GitHub connector. The wiki UI used to allow inline edits to Supabase; we turned that off so there's one source of truth.

2. **How — ask Claude to edit it for you.** In your Confluxion Sales project on claude.ai, type something like:

> *"Update the B. Jackson overview page — add Maria Kowalski as AP director, email maria@bjackson.com, met her on 2026-05-24."*

Claude reads the current page, drafts the change, and opens a pull request via the GitHub connector. Addison gets a notification and merges it. The live wiki updates in ~30 seconds.

3. **How — directly on GitHub if you prefer.** Navigate to the file in [the repo](https://github.com/addisonhoward1/confluxion-crm/tree/main/wiki-content), click the pencil icon, edit the markdown, commit. Same result.

---

## What you don't need to know

These belong to Addison, not Sam:

- The `build_decks.py` Python script that renders pitch decks to PDF

- Anything about the Supabase backend

- The Vercel deployment

- The Next.js app code

- The GitHub Action that syncs the wiki to Supabase

When you need a deck rendered or a new pitch built, you write the content in your claude.ai Project (it knows the voice and the playbooks). You send the content to Addison. She renders the PDF. You both ship it.

---

## When you're stuck

Three places to look, in order:

1. **The Confluxion Sales project on claude.ai** — ask it. Most questions have an answer in the wiki.

2. **This wiki — search the top-right search bar** — finds matches across all 28+ pages

3. **Addison** — text or call. Faster than guessing.

---

_Last updated: 2026-05-24_

Change notes (optional)

Cancel