Step 15: Run the Business Intelligence Gathering Skill

How to let Codex audit your own business — and what it discovers when you give it actual access

Most business owners, when they set up an AI agent, start by writing a document. A brand kit. A "here's who I am and what I do" summary. A list of services, clients, ideal customers. It feels thorough. It feels like a proper handoff.

Running the Business Intelligence Gathering Skill produces something categorically different.

Instead of asking you to describe your business, this skill instructs Codex to read everything it already has access to — your connected plugins, your files, your email history, your calendar data — and build a picture of your business from the evidence it finds. Then it comes back and proves what it knows about you.

That distinction matters more than most business owners realize. For the complete framework, read the full guide.

Why Documents Lie and Data Doesn't

When you write a document about your business, you are writing about the business you think you run. The services you intend to sell. The clients you believe you serve best. The work you imagine fills your time.

Actual email threads, meeting transcripts, Stripe records, and calendar data reveal the business you actually run. Where your time really goes. What clients ask about most. What proposals went out and never came back. Which services generate the most back-and-forth before a yes. The patterns you never articulated because you were too close to see them.

Codex, given direct access to your data through verified plugins, builds a model of your business from that evidence. From the real operational record you have been generating for years — not from your curated self-description.

I call this the difference between Data Intelligence and Document Intelligence. Document intelligence is faster to produce. Data intelligence is more accurate and more useful, because it reflects what is actually happening rather than what you remember or intend.

The Business Intelligence Gathering Skill is the mechanism for switching from one to the other.

What the Skill Actually Does

When you run this skill, Codex does not ask you a questionnaire. It reads.

It goes through every connected plugin — Gmail, Google Drive, Google Calendar, Stripe, meeting transcripts if you have Fireflies or Google Meet connected — and conducts a structured audit. It looks at what kinds of emails you send and receive, what files exist and how they are organized, what your calendar shows about how you spend your time, and what financial data suggests about how your business actually operates.

Then it comes back and proves what it found. A profile built from your own records — not a summary you handed it.

This serves two purposes simultaneously. First, it starts Codex's learning process about who you are and how your business works, which makes every subsequent task more accurate because Codex operates from real context rather than generic assumptions. Second, it surfaces a picture of your business that is often more complete and more honest than anything a static document could capture.

Business owners are frequently surprised by what the audit surfaces. The operational record of a business contains patterns that are obvious in aggregate and invisible day to day.

Watch me explain this live

Before You Run It: The Prerequisite That Matters

The Business Intelligence Gathering Skill is only as good as the access Codex has when it runs. If your plugins are connected but not verified, the audit is incomplete — and incomplete audits produce profiles with gaps that look fine on the surface and fail on specific tasks later.

Two things must be in place before you run this skill.

Connect the core plugins first. Gmail, Google Drive, Google Calendar, and Stripe are the foundational data sources. Without them, Codex is auditing a partial record. Meeting transcripts add depth if you have them — Google Meet is the more reliable option based on my experience; Fireflies has been inconsistent.

Then verify that each plugin actually works. Connecting a plugin gets you a checkmark. Verification confirms Codex can retrieve real data from it. Those are two different levels of access, and most business owners treat the checkmark as sufficient.

The way to verify: ask Codex to pull something specific. "Do you have access to my Gmail?" produces a confident yes whether the access is real or cosmetic. Ask it to retrieve the last five emails you received from a specific domain, or the three most recent proposals you sent. If it can do that, the plugin is functional. If it stalls, hedges, or produces something that looks plausible but cannot be verified against your actual inbox, the connection is cosmetic and the audit will have a blind spot.

Learn how to verify plugin access properly before running this skill.

The Two Things This Skill Accomplishes

Business owners sometimes ask why this skill is necessary when Codex could just ask them questions to learn about the business. A questionnaire cannot do either of the things this skill does.

It starts Codex's contextual memory correctly. When Codex builds its initial understanding of your business from real data rather than a document you wrote, every subsequent task benefits. Codex operates from a record of how your business actually behaves. The difference shows up in every prompt you write after this.

It reveals what you do not know to mention. A questionnaire surfaces what you think is relevant. A data audit surfaces what is actually significant. Those are not always the same list. Codex may identify that a particular type of client generates significantly more communication volume than others, or that a service you consider secondary appears constantly in your email threads, or that a gap in your Stripe records lines up with a pattern in your calendar. These are not things most business owners would include in a document — but they are the kind of context that makes an agent meaningfully more useful.

Common Mistake: Running It Too Early

The most frequent mistake business owners make with this skill is running it before the foundation is ready.

Running the Business Intelligence Gathering Skill before your plugins are connected and verified means Codex is auditing an empty room. Agents are good at producing output regardless — but output built on partial access is shallow, incomplete, and potentially misleading if Codex fills gaps with inference rather than data.

The correct sequence:

Do not interrupt the skill halfway through and start issuing tasks. Business owners who do end up with an agent operating from incomplete context — which looks fine until it fails on something specific, and by then the cause is hard to trace.

What Comes After the Audit

Once Codex has built its intelligence profile, every subsequent task runs faster and more accurately. The first real business task I recommend after the audit is a Gmail analysis: ask Codex to review your last twelve months of email, identify every prospect who received a proposal, determine who closed and who did not, and build a revival strategy for the ones who went dark.

Without the audit, a task like this produces generic output. With it, Codex is working from a model of your actual business — the real clients, the real patterns, the real gaps — and the output reflects that specificity.

Learn about connecting and verifying plugins if you have not completed that step yet. And if your file structure is still organized for human recall rather than agent retrieval, handle that first — the file organization step matters more than most business owners expect before running any intelligence-gathering skill.

The Principle

Give an agent your description of your business and it operates on your self-perception. Give it access to your actual records and it operates on your reality. The second approach produces more accurate, more complete, and more actionable context in practice.

The Business Intelligence Gathering Skill is built on the second approach. Run the permissions audit first. Connect and verify your plugins. Then run this skill and let Codex do what it was built for.

Every task that follows will be working from a richer foundation because of it.

*

This article is companion content to LinkedIn post: linkedin-posts/post-16.md

— Shanee

Additional Context: Codex Knows Your Business Better Than You Think It Does — If You Let It Look

You've spent years building your business. You know your clients, your offers, your patterns. When someone asks you to describe what you do, you can give a polished answer in 90 seconds.

But that polished answer is not the same as your business. It's a curated story about your business — shaped by what you choose to highlight, what you remember clearly, and what you think matters most. Codex, given real access to your emails, your meeting transcripts, your sales data, and your files, will build a more accurate picture of what your business actually is than any document you could write.

This is the insight most business owners miss when they start setting up an AI agent: the onboarding process is not primarily about you teaching Codex. It's about giving Codex permission to discover.

For the complete framework, read the full guide.

The Difference Between Document Intelligence and Data Intelligence

When I watch business owners set up Codex for the first time, almost all of them do the same thing: they write a document. A brand kit. A summary of their services. A "here's who I am and what I do" file they paste into the system as context.

That document is a static snapshot of what you think your business is, written at a single point in time, filtered through your self-perception.

Your inbox tells a different story. Your calendar tells a different story. Your sales history tells a different story.

I call these two approaches Document Intelligence and Data Intelligence — and they are not equivalent.

Data intelligence is not just more convenient. It is fundamentally more accurate. How you actually respond to clients in email, which proposals actually closed, where your time actually goes — that information lives in your data. It does not live in any document you've written about yourself.

What the Business Intelligence Gathering Skill Actually Does

The Business Intelligence Gathering Skill instructs Codex to read everything it has access to — every connected plugin, every authorized tool, every file it can reach — and conduct a thorough audit of your business. Then it comes back and proves what it knows about you.

This serves two purposes simultaneously.

First, it starts Codex's learning process. Before you issue any real operational tasks, Codex has already built a working model of your business from evidence rather than summary.

Second, it surfaces an accurate picture of your business that you can review, correct, and build on. Most business owners are surprised by what Codex surfaces. Not because it gets things wrong — because it gets things right in ways that feel uncomfortably specific.

Watch me explain this live to see the Business Intelligence Gathering Skill run in real time.

Why Your ChatGPT History Is a Business Intelligence File You've Never Read

If you've been using ChatGPT with any regularity, your conversation history is a compressed record of your thinking, your challenges, your strategy sessions, and your frustrations over the entire period you've been using it.

Every question you've asked. Every late-night prompt about a difficult client situation. Every strategy you've explored. It's all in there — and most people treat it as ephemeral and ignore it entirely.

The ChatGPT Insight Skill, run directly inside ChatGPT, converts that raw conversation history into a business and identity summary you can hand to Codex as early onboarding context. It generates a profile — not of who you say you are, but of who shows up in the questions you've been asking for months or years.

That profile, given to Codex at the start of the onboarding process, means Codex begins with context no document could have produced.

The data export itself takes a few days for OpenAI to process, but the Insight Skill runs immediately on what's already in your history.

The Order of Operations Matters

Data intelligence only works if the data access is real — not cosmetic.

This is the step most business owners skip, and it costs them. Connecting a plugin is not the same as giving Codex access. The checkmark on the plugin screen means the handshake completed. It does not mean the agent can actually retrieve the data you need at the depth you need it.

Before running the Business Intelligence Gathering Skill, verify every plugin actually works. Don't ask Codex "do you have access to my Gmail?" and accept a yes as proof. Ask it to pull something specific and real — a recent email, a calendar event from last week, a transaction from Stripe. If it can retrieve real data, the connection is functioning. If it stalls or generates a vague, hedged response, the connection is cosmetic and you need to investigate before proceeding.

The sequence I recommend before running any intelligence-gathering skill:

1. Connect Gmail, Google Drive, Google Calendar, and Stripe
2. Ask Codex to prove access to each one by retrieving one piece of specific, real data
3. Investigate and resolve any connection that fails the verification test
4. Run the ChatGPT Insight Skill inside ChatGPT directly, if you have substantial history
5. Run the Business Intelligence Gathering Skill only after all plugins are verified
6. Let it run to completion before issuing any operational tasks

Learn about verifying plugin access before you build on it.

The Gmail Analysis Use Case That Illustrates the Whole Point

The clearest way to demonstrate why data intelligence beats document intelligence is a prompt that would be impossible without it.

Ask Codex: review the last 12 months of my emails, identify who was sent a proposal, who closed, who didn't close, and create a strategy to revive the ones who went dark.

No document you've written about your business contains this information. You might have notes, a loose CRM, a mental sense of who went quiet and why. But the actual email record — every proposal thread, every follow-up, every silence — is sitting in your Gmail.

Codex, with real plugin access, can run that analysis. Without plugin access, it cannot. That gap — between what an agent can do with real data access versus what it can do without it — is the gap this entire step is trying to close.

Learn more about installing and verifying plugins so this kind of task is possible.

The Common Mistake That Breaks This Step

Business owners connect their plugins, see the confirmation screen, and move on. They feel like the integration is done. Then they run the Business Intelligence Gathering Skill, and Codex produces something thin — a generic summary that could describe almost any business in their category.

The problem is not the skill. The problem is that the plugins were never verified. The connections were cosmetic. Codex was working with less data than the owner assumed, and the output reflected that.

The other version of this mistake is running the Business Intelligence Gathering Skill too early — before files are organized, before the home base is built, before Codex has access to the full range of business data. The skill reads what it can access at the moment it runs. Access more, get more.

The sequence matters. The Foundation Phase exists precisely to ensure that by the time Codex starts building its model of your business, it has the cleanest, most complete access possible.

What Codex Is Actually Building When It Discovers Your Business

When Codex runs the Business Intelligence Gathering Skill with full access, it is not building a summary. It is building a working model — a compressed, evidence-based understanding of how your business actually operates.

That model informs every subsequent task Codex runs. The email it drafts for a client will reflect how you actually write to clients. The proposal strategy it builds will reflect how your closed deals actually compared to your lost deals. The priorities it surfaces will reflect where your time actually goes, not where you think it goes.

This is what I mean when I say Codex knows your business better than you think it does. It is not complimenting you. It is doing the work of looking at the actual record, without the filters and narratives you've built around it.

Give it access. Let it look.

Key Takeaways

• Document intelligence — writing a summary of your business for Codex — is a static, filtered snapshot. Data intelligence, pulled from your actual emails, meetings, and files, is more accurate, more complete, and requires no effort from you to create.
• The Business Intelligence Gathering Skill reads everything Codex has access to and builds a model of your business from evidence. Run it after plugins are verified, not before.
• Verifying plugin access means asking Codex to retrieve specific, real data — not accepting a checkmark as confirmation.
• Your ChatGPT conversation history is a business intelligence file most owners throw away. The ChatGPT Insight Skill converts it into context you can hand directly to Codex.
• The sequence matters: verify access first, build the home base, then let Codex discover.

Learn about building the Agent Home Base that makes all of this context persistent and accessible to every agent in your system.

-- — Shanee