AI Business Workspaces
Turn the knowledge scattered across your business into an AI workspace your team can actually use.
I don't teach companies how to prompt. I build an AI operating environment around how the business actually works.
Twenty minutes. We map your people, knowledge, processes, tools, and repetitive work to where AI can actually help, and you leave with a picture of how your business could be structured.
The problem
Most companies use ChatGPT or Claude one conversation at a time. Someone opens a blank prompt, explains the company again, and gets an answer that doesn't know how the business operates. The problem isn't access to AI. It's that the context the AI needs is spread across Google Drive, Microsoft 365, spreadsheets, email, PDFs, and the owner's head.
What it usually looks like
- Critical information is spread across Google Drive, Microsoft 365, spreadsheets, email, PDFs, shared folders, and individual people.
- Important operating rules are undocumented and live in people's heads.
- Several versions of the same file leave nobody sure which one is current.
- People answer the same questions again and again, or rebuild context from scratch.
- AI gets used for one-off writing tasks rather than real operating work.
- The owner and managers stay the bottleneck because too much of the company's knowledge lives with them.
An AI Business Workspace organizes what the company already knows, its documents, spreadsheets, SOPs, pricing rules, customer information, project context, and decision rules, into a structured, client-owned environment in ChatGPT, Claude, or another platform, so the team isn't starting from zero every time.
Before and after
| Before | After |
|---|---|
| Scattered files and tribal knowledge | Structured company knowledge with a clear source hierarchy |
| Blank-prompt AI use | Workspaces that already know the business |
| Explaining the company again every session | Persistent instructions and reusable context |
| Disconnected tasks | Repeatable AI-assisted workflows |
| The owner as the knowledge bottleneck | Institutional knowledge the team can reach, with controls |
| AI as a writing toy | AI as a practical operating layer |
What gets built
A business knowledge layer
Company context, terminology, products and services, customers, policies, roles, goals, constraints, and the past decisions that still matter.
Knowledge architecture
A deliberate structure for what belongs in canonical documents, project files, databases, instructions, workspaces, dashboards, and source systems.
Purpose-built workspaces
Working environments for leadership, sales, operations, customer accounts, finance, projects, people, or whichever areas matter most.
AI instructions
Persistent instructions for how the AI should weigh sources, handle conflicts and uncertainty, follow policy, set tone, and run recurring tasks.
Repeatable workflows
AI-assisted workflows for research, meetings, proposals, customer briefings, issue triage, analysis, planning, and reporting.
A command center
A skimmable view of priorities, risks, opportunities, deadlines, next actions, decisions, and the operating context behind them.
Governance
Rules for source authority, access, sensitive information, human review, uncertainty, and ownership.
A maintenance model
A process for keeping knowledge, instructions, and workflows current as the business changes.
A walkthrough of a fictional company, before and after, is in production and will appear here.
How it works
Discovery
Interviews with leadership and key people, and an inventory of tools, information, recurring work, business rules, decisions, and bottlenecks.
Knowledge extraction
Collecting and reviewing the documents, spreadsheets, SOPs, notes, email knowledge, and project records that matter, and what people know but haven't written down.
Architecture
Deciding the source hierarchy, the workspaces, the canonical knowledge, the instructions, and where workflows will help.
Build
Configuring your AI environment and loading the approved knowledge structure.
Workflow implementation
A focused set of recurring workflows, built on your team's actual work.
Activation
Training people by running the new system on real business tasks, not through general AI lectures.
Handoff and governance
Documenting ownership, source authority, maintenance, permissions, and where a person reviews the output.
After handoff, optimization is ongoing: keeping knowledge current, improving instructions, adding workflows, and adapting the workspace as the business changes.
You own the result
The production workspace is yours: your company data, your documents, and your configured environment in ChatGPT, Claude, or whatever platform you choose. I'm invited in to build it, and when the engagement ends you keep everything that was built. What I keep is the method I bring to the next client. You're not locked in to me, and you're not locked in to one vendor's interface, because the system sits above the platform layer and moves with you.
You own
- Your files, data, and proprietary information
- Company-specific documentation and generated knowledge
- The configured operating environment
- Your internal processes and decision rules
I keep
- The discovery method
- Architecture frameworks and knowledge schemas
- Instruction frameworks and templates
- Workflow-design methods and reusable components
Who it's for
- Owner-led or operationally complex companies, roughly 10 to 150 people
- Heavy users of Excel, Sheets, Docs, PDFs, email, and disconnected SaaS tools
- Teams that have tried ChatGPT or Claude but use it for isolated tasks
Professional and business services, healthcare operations, construction and field services, property management, small and midsize manufacturers, agencies, and other spreadsheet-heavy businesses.
You'll recognize this if
- “Everything is in my head.”
- “We have several versions of the same spreadsheet.”
- “We tried ChatGPT, but everybody uses it differently.”
- “Our SOPs exist, but no one really uses them.”
How it connects to the rest of the work
Spreadsheet modernization takes a legacy spreadsheet to business rules, a data model, and an application. AI Workspace modernization takes scattered knowledge to structured context, repeatable workflows, and an AI operating environment. Working across both, I can tell you what should stay a document, become structured data, become software, become an AI workflow, or remain a human decision.
Engagement options
AI Workspace Audit
Discovery, current-state assessment of workflows and knowledge, risks, opportunities, recommended architecture
AI Business Workspace Buildout
Knowledge architecture, workspace setup, instructions, workflows, templates, handoff
AI Business Command Center
Deeper implementation with dashboards, integration, automation, cross-functional operating views
AI Operations Support
Knowledge goes stale: people, policies, services, tools, and AI capabilities all change. Ongoing maintenance, workflow expansion, governance, and new use cases.