CEO & Executive Edition

THE RAPID
DEPLOYMENT BAG

Your AI field kit — one tap from your pocket, anywhere you are.

A go-bag is the stripped-down kit you grab when you have to move now — no time for the full loadout. This is that, for AI. No bloat, no hype: the few tools that actually matter, each with the exact prompt to run it through your ACE Compass so the answer comes back aimed at your business. Build the kit once. Grab what you need from here on out.

Build Your Kit Once · ~5 Minutes

SET UP THE BAG

Do this once. After that, every prompt below drops straight into a Claude that already thinks like an executive advisor.

01

Install the ACE Compass

Open Claude, create a Project named nittygritty-CEO, and paste in the ACE Compass — your executive foundation.

Free. The ACE Compass prompt is provided with the course.
02

Add the Knowledge File

Drop the NITTYGRITTY-CEO operating framework into that Project's knowledge files. It governs every answer — including flagging data risk automatically.

Free download — provided with the course.
03

Paste the Primer

Start a chat in that Project and paste the Primer below as your first message. Then grab any prompt on this page and run it.

Copy it with one tap — right here.
Paste This First

THE PRIMER

One paste turns generic Claude into a tailored advisor for the whole session. Everything else feeds it.

You have my ACE Compass loaded as your foundation. I'm a CEO / business owner
working through the Nitty Gritty AI "CEO Rapid Deployment Bag." For this entire
session, act as my AI implementation guide — executive-grade, plain English, no hype.

Here's my context:
- My business: [what you do, roughly how many people]
- My biggest time-drains right now: [name 2-3]
- My data sensitivity: [e.g. client contracts, financials, health/legal info - or "low"]
- My comfort with tech: [hands-on / I delegate everything / somewhere between]

Before we start, ask me up to 3 questions to sharpen the above. Then:
1. Tell me which 2-3 tools in this kit to use first, and why - in order.
2. For each thing we work on, aim the answer at MY role and business, not generic advice.
3. Always flag any data-governance risk before recommending I connect or upload anything.
4. End each topic with one concrete action I can delegate or do this week.

Keep it tight. I'm busy. Let's begin.
The Loadout

THE KIT

Every resource is free and official. Open the link, then run its prompt inside your nittygritty-CEO Project.

A · Foundations — Read First

Claude 101

The plain-English starting point. Why you care: 20 minutes that makes you fluent enough to lead the conversation instead of nodding through it.
Open Resource ↗
Run it through your ACE Compass
I just went through Claude 101. Based on my business and role, show me the 5 ways
I'd personally get the most value from Claude this month - ranked by payoff, with
one example prompt for each that fits what I actually do.

AI Fluency: Framework & Foundations

How to collaborate with AI well — the skill under all the tools. Why you care: this is the literacy you want your whole team to have. The floor.
Open Resource ↗
Run it through your ACE Compass
Apply the AI Fluency framework to my role as a leader. Where am I likely to
over-trust AI, and where am I likely to under-use it? Give me a personal
operating rule for each.

AI Capabilities & Limitations

An honest course on what AI can and can't reliably do. Why you care: the best inoculation against being oversold by a vendor or consultant.
Open Resource ↗
Run it through your ACE Compass
Here's a use case someone pitched me: [paste the pitch]. Using what's actually
known about AI's capabilities and limits, pressure-test it. Is this real or hype?
What would have to be true for it to work in my business?

Claude for Work

Anthropic's own guidance on rolling Claude out across an organization. Why you care: your deployment playbook — free, from the source.
Open Resource ↗
Run it through your ACE Compass
Build me a 30-day rollout plan for Claude across my business (size and type are
in your context). Include: who owns it, the data policy I need first, the 3
highest-value use cases to start with, and how I'll measure whether it worked.
B · The Tools That Matter

Projects

Workspaces that remember instructions and files across every chat (where your Compass lives). Why you care: how you make Claude consistent — load standards once, stop re-explaining.
Open Resource ↗
Run it through your ACE Compass
Help me design a set of Claude Projects for my business - one per function that
would benefit (sales, ops, comms). For each, tell me what instructions and
reference files to load so it produces on-brand, consistent output.

Claude Cowork

A desktop assistant that works across files on your computer and runs multi-step tasks. Why you care: for document-heavy work, it's a force multiplier.
Open Resource ↗
Run it through your ACE Compass
Look at my recurring work (in your context). Which document- and file-heavy tasks
are the best candidates to hand to Cowork, ranked by hours saved? For the top one,
write the exact instruction I'd give it.

Skills

Reusable instruction files that encode a playbook so Claude runs it the same way every time. Why you care: turn your SOPs into consistent, repeatable output.
Open Resource ↗
Run it through your ACE Compass
Here's one of my standard operating procedures: [paste or describe it]. Help me
turn it into a Claude Skill - structured so anyone on my team gets the same
quality output every time they run it.

Connectors

Secure links between Claude and your other tools (email, calendar, drives). Why you care: powerful — and exactly where governance matters most.
Open Resource ↗
Run it through your ACE Compass
Given my data sensitivity (in your context), which of my tools would be safe and
worthwhile to connect to Claude, and which should I NOT connect? Give me the
governance line in plain terms before any convenience.
C · Hand To Your Tech Team

Claude Code & the API

For engineers building software (Claude Code) and embedding AI in your products (the API). Why you care: these go to your team, not your reading list.
Open Resource ↗
Run it through your ACE Compass
I'm not technical, but I have a tech team. In plain English, help me write the
brief I'd hand them about whether and how to use Claude Code and the API in our
products - including the questions I should make them answer before we invest.
D · Governance, Plans & Support

Plans, Small Business & Support

Plan tiers handle your data differently — this is the unglamorous, load-bearing part. Why you care: the right tier is a governance decision, not a budget one.
Open Resource ↗
Run it through your ACE Compass
Based on my business size and data sensitivity, which Claude plan should I be on,
and why - specifically regarding how each tier handles company data? Give me the
one-paragraph version I could forward to whoever manages our software.
More: Small Business solutions · Support · Docs
The Whole Model, In Ten Seconds

THREE ALTITUDES OF THE SAME ENGINE

01

UNIVERSAL

Claude, straight

Brilliant guidance, free for anyone. The door everyone can walk through — and we tell you to.

02

CATEGORICAL

A PRIME Compass · free

The same engine, aimed at your role. Installed into your own Claude — every answer lands in your lane.

03

INDIVIDUAL

Archetype Compass · with you

The same engine, tuned to you — designed for you exactly, and nobody else.

Content produced under AEIN-2026-UT-0000  ·  Verified Entity: Edwin Earle Jacobi III | BlackListCode  ·  Founding Operator — AEIN Registry | EDit 2.0 | Ω-PRIME Systems  ·  aeinregistry.com/registry/AEIN-2026-UT-0000