One person · Setup 1 of 3

Their own tools

What has to work together for useful work to improve? Five jobs around one decision-maker. AI supports the workflow. It is not the workflow.

Example setup · open a role to see its limits and where you decide

Approved sourceHolds what the work may use

In this example: Google Workspace holds approved docs, email and working files.

May
Give the routine current, approved material to read.
May not
Stand in for customer status. That stays in the record system.
You decide
Which files count as approved. Each one has an owner, a version and a review date.
Draft and assistPrepares a first version

In this example: Grok Bot runs as a recurring agent, with weekday follow-up drafts and a morning brief.

May
Organize information and prepare a draft to check.
May not
Auto-send, change pricing or edit deal stages.
You decide
Whether the draft is right and whether it goes out.
ReviewChecks against good examples

In this example: Claude writes, analyzes and reviews against approved examples. One sample task is a client brief from dated, authorized files.

May
Point out gaps and compare a draft with the quality bar.
May not
Replace your approval. A review pass is still input to you.
You decide
Which points to accept and what changes.
You approveEvery role hands work to one person, who checks it and sends it

Why you sit in the middle: in this example each tool runs on its own account. You pass work between them by file, link or repo commit.

A decision that stays yours: a proposal draft can be prepared automatically, but you still check scope and prices before sending.

This keeps one person’s setup simple. Connections between tools need permissions and upkeep, which is the department’s harder job.
Record systemKeeps status, tasks and next-action dates

In this example: HubSpot holds deals, tasks and next-action dates, and every send gets a HubSpot note.

May
Show what happened on a deal and what comes next.
May not
Be changed by the agent at the deal-stage level in this setup.
You decide
When a deal moves and what the next action is.
BuildMakes the small tools the routine needs

In this example: Codex builds and tests a small script, report or internal tool in VS Code or a repo. One week, it tests a script that fixes dates and removes duplicate contacts, then Git commits it with history.

May
Build and test a small, named piece of work.
May not
Decide what goes to a client.
You decide
You check the tested result before relying on it.

What to take from this: choose tools by the job they do in your routine. The routine matters more than the logo.

Named tools, one example week and monthly licensesWho does what, how work passes, license tiers and pricing sources

Their own tools

Who does what

Grok BotPrepares
ClaudeReviews
OwnerApproves
HubSpotLogs

Grok Bot: Recurring agent. Weekday follow-up drafts and a morning brief.
Codex: Builds and tests a small script, report or internal tool in VS Code or a repo.
Claude: Writes, analyzes and reviews against approved examples.
HubSpot: Deals, tasks and next-action dates.
Google Workspace: Approved docs, email and working files.

How work passes

In this example each tool runs on its own account. The owner passes work by file, link or repo commit.

One example week

Codex in VS CodeTests a script that fixes dates and removes duplicate contacts
GitCommits the tested script with history
ClaudeDrafts and reviews a client brief from dated, authorized files
OwnerChecks both, then sends

Monthly licenses

Illustrative planning prices in USD a month before tax, checked Nov 4, 2026. Plans, terms, usage and regional pricing change, so check current plans before relying on them.

Entry tiers: Grok Premium $30 + ChatGPT Plus $20 + Claude Pro $20 = $70
Heavier tiers: Grok Super $100 + ChatGPT Pro $100 tier + Claude Max $100 = $300
Optional: New Google Workspace Business Standard adds $16.80, so entry becomes $86.80. VS Code editor $0. CRM and extra usage are separate.

Back to Capacity