Most business owners, when they sit down to "onboard" an AI agent, open a Google Doc and start typing. They write their mission statement. Their service list. Their ideal client profile. Their values. They treat it like a new employee's first-day packet — and then they hand it to the agent and wonder why the outputs feel generic.
The document isn't the problem. The assumption is.
A static document captures what you think your business is. Your inbox, your calendar, your meeting transcripts, your Stripe data — those capture what your business actually is. The gap between those two things is where most AI agent setups fail before they begin.
This is the concept I call Data Intelligence vs. Document Intelligence, and understanding which one you're feeding your agent determines how accurate, useful, and genuinely autonomous Codex can become.
For the complete framework, read the full guide.
The Two Ways to Give an Agent Business Context
Document Intelligence is what you write. A brand kit. An "about my business" summary. A list of your services and your clients and your positioning. It reflects your self-perception. It reflects the version of your business you want to be running — which is not always the same as the one you are actually running. And it goes stale the moment anything changes, because documents don't update themselves.
Data Intelligence is what Codex reads directly from the tools you're already using. Your emails from the last 12 months. Your meeting transcripts. The proposals you sent and which ones closed. The recurring calendar blocks that reveal where your time actually goes. The Stripe records that show what customers actually pay for, not what you think they pay for.
The difference matters because agents don't fill gaps with intuition. A human employee can read a brand kit and intuit the nuance. They've worked in enough contexts to make reasonable assumptions. Codex operates on what it can access and verify. If you give it a document that says "we serve enterprise clients," but your email history shows that 80 percent of your revenue comes from solopreneurs, Codex will eventually encounter that contradiction. The question is whether it catches it early — or after it's made a dozen decisions based on the wrong premise.
What Codex Actually Discovers When You Give It Real Access
When you run the Business Intelligence Gathering Skill, Codex is instructed to read everything it has access to — all connected plugins, all available files, all meeting data — and conduct a thorough audit of your business. Then it comes back and proves what it knows about you.
That last part matters. You're not just getting a summary. You're getting a demonstration of the evidence it found. Which means you can see exactly how accurate the picture is, what it caught that you didn't think to mention, and what gaps still exist because certain tools aren't connected yet.
In my experience working across my own business and client businesses, this skill surfaces things people genuinely did not expect. Patterns in how they respond to certain types of clients. Services that appear on the website but never appear in actual sales conversations. Recurring calendar blocks that suggest priorities the business owner doesn't consciously claim. The data doesn't editorialize — it just shows what's there.
That accuracy is the point. An agent operating from real data makes better decisions, drafts more relevant outputs, and surfaces more accurate recommendations than one working from a polished self-description.
The Verification Step Most Business Owners Skip
Connecting a plugin and having real data access are not the same thing. This is the most common setup mistake I see.
A business owner connects Gmail, gets a checkmark, moves on. Later they ask Codex to review 12 months of emails and identify every proposal that was sent but didn't close. Codex stalls. Or it produces an answer that sounds plausible but doesn't match reality. The plugin handshake completed. The actual data retrieval didn't.
The fix is verification before you run any intelligence-gathering skill.
After connecting each plugin, ask Codex to prove access. Don't ask "do you have access to my Gmail?" — that produces a self-report. Ask it to pull something specific and real: "Show me the last five emails I received from anyone with the word 'proposal' in the subject line." If it retrieves actual emails with real subject lines and real senders, the plugin is functioning at the depth you need. If it stalls, hedges, or returns something generic, you have a cosmetic connection — and you need to investigate before building on it.
This applies to every plugin, not just Gmail.
| Plugin | What to Ask Codex to Retrieve | What a Functional Connection Returns |
|---|---|---|
| Gmail | Last 5 emails containing "proposal" in subject | Actual subject lines, senders, dates |
| Google Drive | Most recently modified document in your Drive | Real filename, last modified date, file type |
| Google Calendar | Next three events on your calendar | Actual event names, times, attendees |
| Stripe | Most recent successful payment | Real dollar amount, customer name, date |
| Fireflies / Google Meet | Most recent meeting transcript summary | Actual meeting title, key topics, date |
Run this verification table before you run the Business Intelligence Gathering Skill. The skill is only as good as the access behind it.
Watch me explain this live — I verified plugin access in real time during the session and showed what a functional connection looks like versus a cosmetic one.
The ChatGPT History Angle (If You Have It)
If you've been using ChatGPT for any length of time, your conversation history is a business intelligence file you've never read. Every question you've asked, every strategy you've explored, every operational problem you typed through at some point — it's all in there.
The ChatGPT Insight Skill runs inside ChatGPT directly and generates a business profile from your full conversation history. You copy that output and hand it to Codex as early context before running any other skill. Instead of starting from zero, Codex begins with a richer picture of who you are and how you think — drawn from months or years of actual questions you asked, not a document you wrote in an afternoon.
During the session, I ran this skill live. The output began generating a profile immediately — pulling from full conversation history to build a business and identity summary. The accuracy of what it surfaced, purely from chat history, is consistently higher than what most people write in a brand kit.
This is optional if your ChatGPT history is thin. It is not optional if you've been a heavy user. The signal in that history is too valuable to discard.
Common Mistakes at This Step
Skipping verification and trusting the checkmark. The checkmark means the authentication completed. It does not mean Codex can retrieve the depth of data you're assuming it can. Verify with a real retrieval test before proceeding.
Running the intelligence-gathering skill before all plugins are connected. Codex audits what it has access to at the moment the skill runs. If Gmail is connected but Google Calendar isn't, the profile it builds is missing a significant slice of how your time is actually structured. Connect and verify everything first. Then run the skill.
Treating the document and the data as equivalent. Some business owners run the intelligence-gathering skill and also hand Codex a brand kit, thinking this adds context. It does — but if the brand kit contradicts what the data shows, you've introduced a conflict Codex has to resolve. Be intentional about what you're handing over and in what order.
Not using Gmail analysis as a first real business task. One of the clearest demonstrations of what Data Intelligence can do: ask Codex to review the last 12 months of emails, identify everyone who received a proposal, identify who closed and who didn't, and build a strategy to re-engage the ones who went dark. That is a real business task with real revenue implications — and it's impossible without plugin access. Possible with it in a single prompt.
Learn about verifying plugin access before running any intelligence-gathering skill.
The Principle
Your business has a story it tells about itself — in your deck, your website, your brand kit. And it has a story that emerges from the actual record of what you do every day.
An agent built on the told story will produce outputs calibrated to the story you want to be true. An agent built on the actual record will produce outputs calibrated to the business you're actually running.
Give Codex permission to discover the second one.
Start with the plugins. Verify each one with a real retrieval test. Run the Business Intelligence Gathering Skill after verification. Use your ChatGPT history if you have it. And resist the urge to hand over a polished document as a substitute for access. The document is supplementary. The data is the foundation.
Data doesn't lie. Static documents only capture what you remember to write down on a good day.
Related reading:
- Verify Plugin Access Before You Build on It
- Run the Business Intelligence Gathering Skill
- Install and Connect Plugins
- Build the Agent Home Base
— Shanee
Use the prompts behind this system
The Growth Academy Skills Dashboard includes 100+ Codex skills and prompts for SMB owners.
See the Skills Dashboard →