Session Nine

Joe's Magic CRM Installation

Open up a terminal first so you can copy and paste the Claude command, then use this session to install the All Sorted CRM module into your existing Mission Control setup, validate the live CRM routes, and get the sample data and email wiring ready for use.

Why this matters

A CRM is a place to track who your leads are, where each conversation stands, what needs to happen next, and which follow-ups should happen automatically instead of living only in your head or inbox.

We are learning it because once your pipeline gets even a little busy, money leaks out through missed follow-ups, slow replies, forgotten notes, and leads that never get moved forward.

A useful CRM gives you one working board for your leads, your stages, your automations, your messages, and your settings, so you can see what is happening and act on it quickly.

The income upside is simple: better lead tracking means more conversations stay warm, more prospects get the right follow-up at the right time, and more of the people already interested in working with you actually convert.

Need the computer-use setup and ghost-browser practice steps first? Use Automated Ghost Computer Use in the Resource Vault.

Duration ~90 minutesIntermediate

Table of Contents

1Claude Dangerously Skip Permissions
2Install The CRM Module
3Use The CRM
4Lead Capture Tests And Prompts

Start Here

Claude Dangerously Skip Permissions

Open up a terminal

In your open terminal, start Claude in the workshop project folder before you install the CRM.

Terminal

claude --dangerously-skip-permissions

Heads Up

Dangerously Skip Permissions is powerful. Use it only in the project folder you mean to edit.

Install

Install The CRM Module Into Mission Control

Download, install, and open the CRM with one prompt

Use this exact installer prompt in Claude Code. The prompt handles both Mac and Windows, finds your Mission Control repo, downloads and extracts the package if needed, installs anything missing, tries to wire Resend if it already exists, imports the sample CRM data, starts the app if it is not running, and opens Mission Control inside the CRM in the browser when validation is done.

Claude Code prompt

Edit before copying

Install the All Sorted CRM module into my existing Mission Control on this computer.

If the operating system is macOS, use macOS commands and paths.
If the operating system is Windows, use Windows commands and paths.

Keep going until the install is complete, tested, and working unless you hit a real blocker.

Download the CRM module from:
/downloads/allsorted-crm-module-v1.5.zip

Your rules:
1. First locate my existing Mission Control repo automatically.
2. Confirm it is the right repo before editing anything.
3. If the package zip is not already on this computer, download it first. Then extract it.
4. Back up every CRM-related file before you change it.
5. Run the packaged installer.
6. If dependencies are missing, install what is needed.
7. Look for existing Resend configuration in .env.local, .env, and nearby workspace env files.
8. If RESEND_API_KEY already exists, wire email automatically.
9. If Resend is missing, do not block the install. Finish the CRM install anyway and tell me exactly what to add later.
10. Preserve any existing CRM data. Do not overwrite it.
11. Import the included sample CRM data.
12. If Mission Control is not already running on port 3000, start it. If it needs a restart after install, restart it.
13. Run the packaged validation checks and also verify these routes in the browser:
   - /app/crm
   - /app/crm/pipeline
   - /app/crm/templates
   - /app/crm/automations
   - /app/crm/settings
14. If a test fails, fix it and rerun the validation until it passes.
15. When everything passes, open Mission Control in the browser directly to /app/crm/pipeline so I land inside the CRM immediately.
16. Only when everything passes, tell me:
   - CRM installed correctly
   - the exact Mission Control path
   - whether Resend was auto-wired
   - that the sample leads are available
   - which tests passed

Hard blockers only:
- you cannot find a real Mission Control repo
- the repo is not writable
- the app structure is too broken to patch safely

If you're getting a null error, try this prompt.

CRM null-error fix prompt

Edit before copying

Fix the Mission Control CRM install in this repo so lead creation no longer crashes with NOT NULL constraint failures in lib/crm.js.

Tasks:
1. Open lib/crm.js.
2. Find the INSERT INTO crm_lead_events statement inside the lead ingest flow.
3. Add the missing created_at column to the insert column list.
4. Expand the values tuple from 9 placeholders to 10 placeholders.
5. Pass capturedAt again as the final .run() argument so created_at is populated.
6. Find function upsertSyncState and its INSERT INTO crm_sync_destinations statement inside the if (!existing) branch.
7. Add the missing created_at and updated_at columns to that insert column list.
8. Expand the values tuple from 9 placeholders to 11 placeholders.
9. Append nowIso() and nowIso() as the final two .run() arguments.
10. Save the file, restart Mission Control if needed, then verify a new lead can be created without a null / NOT NULL SQL error.

Rules:
- change only what is required for this fix
- do not remove or overwrite existing CRM data
- after patching, tell me exactly what you changed and what you verified

Heads Up

If you use Codex instead of Claude Code, use the Copy Codex Onlybutton below the prompt block. That button adapts the installer prompt for the Codex environment.

What success looks like

Do not stop after files are copied. The install is only done when the live Mission Control runtime has the CRM in the nav, the pages load on port 3000, the sample data is visible, and the validation checks pass.

Navigation

The CRM shows up in Mission Control

`CRM` appears in the main Mission Control nav so you know the module is live.

Routes

The core CRM pages load

`/app/crm`, `pipeline`, `templates`, `automations`, and `settings` all open cleanly.

Data

Sample leads appear in the pipeline

You should see believable sample data instead of an empty board.

Assets

Templates and automations are present

The starter templates and starter automations are available for testing.

Existing Resend config is wired automatically

If Resend already existed in the repo, the CRM should pick it up without extra setup.

Use It

Use The CRM Right Away

Start with the sample leads

The package installs Golden Claw sample CRM data so you are not staring at an empty board. That gives you real cards to move, sample templates to inspect, and sample automations to turn on when you are ready.

What is included

50+ believable sample leads across different stages
Starter email templates
Starter automations installed but disabled by default
`Joe Tester <newyork1@gmail.com>` as one live test lead for automation practice

Open Settings and change the three defaults

Go into CRM Settings and update the three values you will use right away:

1. Change Default delay
2. Change Email send from
3. Change Send test email to

Then press Save Settings. This gives your automation layer the correct timing and sender details before you start turning anything on.

Move cards like a real pipeline

Open the Pipeline view and drag cards from one column to another as if you are working real leads through a sales process. Drop each card exactly where you want it to sit in that column.

What to practice

Move a lead from `Possible Candidate` to `Interested`
Reorder cards inside the same column by dragging them higher or lower
Notice which columns have automations attached and which do not

Pro Tip

This is where the CRM becomes useful. You are not just storing names, you are moving people through a process that shows who needs attention next.

Create a new manual lead and fill it in

Use the add button in the pipeline or contacts view to create a new manual lead. Add enough information so the lead is real and actionable instead of just being a blank card.

Good fields to fill out

Name
Email
Phone
Primary project
Next step
Notes
Business description

Once the lead exists, move it to the right stage so you can see how a real pipeline starts to take shape.

Run a quick Resend test first

Before you start building automations, run a quick Claude Code check so you know whether Resend is already working in this Mission Control install. That lets you catch email problems before you waste time testing the pipeline.

Claude Code resend test prompt

Edit before copying

If Claude reports that Resend is not working yet, fix that first. It is much easier to solve email setup before you start debugging templates and automation rules.

Lead-capture test: read the last 20 Instagram DMs and add real leads

Once the Instagram agent is installed, this is the first real sales workflow to practice. The point is not to automate outreach. The point is to review inbound conversations, identify actual opportunities, and get the right people into the CRM with useful notes.

Claude Code prompt

Edit before copying

Use my installed Instagram agent and my CRM together.

Goal:
Read the last 20 Instagram DM conversations, identify which ones are actual leads, and add only the real leads into my CRM with useful information filled in.

Rules:
1. First verify the Instagram agent works on this machine.
2. If the global command works, use it. If not, find the saved install path and use the fallback launcher command.
3. Read the last 20 DM conversations.
4. For each conversation, decide whether it is:
   - a real lead
   - not a lead
   - unclear / needs manual review
5. Treat someone as a lead only if there is real business intent, such as:
   - asking about working together
   - asking about services, pricing, availability, or booking
   - showing serious interest that could reasonably become a sales conversation
6. Ignore obvious spam, friends chatting casually, low-signal reactions, and anything that is not a real business opportunity.
7. For each real lead, add a CRM contact or lead record with as much of this as you can find:
   - Instagram username
   - display name
   - lead source = Instagram DM
   - short summary of what they want
   - current stage = New Lead or Interested, whichever fits better
   - next step
   - notes from the conversation
8. If a lead already exists in the CRM, do not create a duplicate. Update the existing record instead.
9. At the end, give me:
   - how many DMs were reviewed
   - which conversations were treated as real leads
   - which ones were unclear
   - exactly what was added or updated in the CRM

Important:
- Do not send any DMs.
- Do not post anything.
- This is read, qualify, and capture only.
- If anything blocks the CRM write, stop and tell me exactly what failed.

Lead-capture test: create example inbound leads from different sources

Not all leads start on Instagram. Use this prompt to practice the same CRM logic for referrals, email inquiries, and other inbound channels so your operating system is bigger than one platform.

Claude Code prompt

Edit before copying

Lead-capture test: enrich one lead before follow-up

This ties Session 8 and Session 9 together. Use research and web fetch to make one CRM lead more actionable before you follow up.

Claude Code prompt

Edit before copying

Pro Tip

The CRM stores the lead, and your research tools make the next message or call sharper.

Tests

Lead Capture Tests And Prompts

Configure Resend ONLY

If it was not found automatically, email stays disabled until you add your own values. Open your Mission Control project's `.env.local` and add:

Environment values

RESEND_API_KEY=re_xxxxxxxxxxxxxxxxx
RESEND_FROM_EMAIL=hello@yourdomain.com

Then restart Mission Control, open CRM Settings, and confirm email sending is now available.

Update your CRM Settings before testing

Go back into CRM Settings and make sure the defaults are set for a fast demo run using your own email.

Change these settings now

1. Set Default delay to 0 or 1 minute for now.
2. Set Email send from to the address you want the demo emails to come from.
3. Set Send test email to to your own inbox.

Save those settings before you continue. That makes the demo fast, and it ensures the test email goes to the inbox you are actually watching.

Review a starter automation and queue flow

Go to Templates to review the starter copy, then go to Automations and enable one example email automation. Move a sample lead into the matching stage, approve it if needed, and confirm the message reaches the queue.

Pro Tip

The safest first test is to use the sample lead with a real inbox, then confirm the automation through the CRM Approval and Delivery Queue before trusting it on your own real leads.

Create a template

Open Templates and create a message you would actually want a new lead to receive. The template is the content the automation sends when a lead reaches the matching stage.

How to create it

1. Click the button to add a new template.
2. Give the template a clear name so you can recognize it later.
3. Choose the channel you want to use, which for this demo should be email.
4. Write a subject line and body that fit someone who just became interested.
5. Save the template, then reopen it once to confirm the content saved correctly.

Keep the copy simple. For the demo, one short follow-up email is enough as long as it is clearly saved and available in the template list.

Create an automation

Go to Automations and create a rule that uses the template you just made. The automation connects a pipeline stage change to a specific outgoing message.

Setup process

1. Click to add a new automation.
2. Name it something obvious, like `Interested follow-up`.
3. Leave the project set to the pipeline you are testing.
4. Set the destination stage to Interested.
5. Choose Email as the channel.
6. Select the template you created in the previous step.
7. Save the automation and make sure it is enabled.

Pro Tip

The automation is not useful until the stage, channel, and template all line up. Check those three settings before you move on.

Test the automation

Create or use a test card that contains your own email address, then move that card into a column that has the automation attached to it.

Exact test flow

1. Make sure the test lead record contains your real email address.
2. Open the Pipeline view.
3. Drag that test card into the Interested column.
4. Use the Interested column specifically, because the demo includes an automation for that stage.
5. Check the Approval or Delivery Queue and confirm the message was generated.
6. Make sure you actually receive the email in your inbox before treating the automation as working.

If nothing happens, go back and verify the template exists, the automation is enabled, and the card was dropped into Interested rather than a different stage. The test is only complete once the email reaches your inbox.

Using Codex instead of Claude Code? Codex version of this page

Session 9 Overview All Sessions