Field guide · for builders picking and setting up an AI tool · September 2026

Claude & ChatGPT Field Guide

Two products, the same job, different names for almost everything. This guide covers which plan to buy for a company, how to set it up so your data is protected and your team can share what they build, and a translation table so you can read either company's release notes without a headache.

The short version

They are closer than the marketing says

Both have a chat, a way to save instructions and files into a reusable assistant, a side panel that renders documents and code, a coding agent, an agent that works on your files, a browser agent, memory, connectors to Google/Microsoft, scheduled tasks, and a business tier that doesn't train on your data. Pick one. Don't run both.

Buy the business tier, not personal Plus/Pro

For a company the answer is Claude Team or ChatGPT Business: about $25 per seat monthly, ~$20 annual, 2-seat minimum. You get admin control, company billing, shared assistants, and a contract that says your conversations aren't training data. A personal $20 plan on someone's own card gives you none of that.

Pick by people, not benchmarks

Whichever one your most tech-comfortable person already uses is probably right. If your team lives in Microsoft 365 or Google Workspace, both connect. If someone on staff will write code or automate, check the coding-agent column below. If nobody will, ignore it.

Plans, side by side

US list prices as of early September 2026 from the vendors and current pricing roundups. Both companies change plans often — confirm on the pricing page before you buy.

TierClaudeChatGPTWho it's for
FreeFree — limited usage, latest modelsFree — limited messages; Go $8/mo ad-supported, no custom GPTs or agentsTrying it. Not for company work
IndividualPro $20/mo · Max $100 / $200 (5× / 20× usage, Claude Code included)Plus $20/mo · Pro $100 / $200 (higher limits, more Codex and Deep Research)One person. Consumer terms — check the training toggle (below)
CompanyTeam $25/seat mo · $20 annual; Premium seat $125 / $100 (~5× usage, for heavy Claude Code users). 2–150 seatsBusiness $25/seat mo · $20 annual, 2+ seats. Unlimited GPT-5 messages, no training on your dataEvery company in this room. Mix seat types on Claude; everyone's the same on ChatGPT Business
EnterpriseCustom — 150+ seats, SCIM, audit logs, data residency, Compliance APICustom — SCIM, enterprise key management, data residency (7 regions), retention controls, SLAsNot you yet. Revisit at 150 people or when IT/legal demands it
Rule of thumb for a 15-person builder: 3–5 seats to start (owner, next-gen leader, estimator, selections/office coordinator, PM lead), all standard. Add seats when someone asks for one because they watched a colleague save an afternoon. Track usage the first month before deciding anyone needs a premium seat.

Setup for a company — the checklist

Same shape on both products. Do these in order; the first four take an hour.

Day one · account & data

  • Buy the business tier on a company card with a company email as the owner/admin. Never let the company's AI live on a personal Plus/Pro account — you can't recover it when that person leaves
  • Owner is admin; one deputy. Owner + next-gen leader or office manager. Admins add/remove seats, see billing, control sharing; they do not read people's chats by default
  • Confirm the data setting. Business tiers don't train on your data by contract. If anyone still uses a personal account for work: Claude → Settings → Privacy → turn off "Help improve Claude"; ChatGPT → Settings → Data controls → turn off "Improve the model for everyone"
  • Invite by company email and set up domain capture / SSO if you have Microsoft 365 or Google Workspace, so a new hire's signup lands in your workspace automatically
  • Set a spending cap (Claude) or review the seat count monthly (ChatGPT)

Week one · structure

  • One shared assistant per process, not per person. "Selections follow-up," "Sub bid leveling," "Weekly client update." Instructions + your templates + 3 good examples. Claude: a shared Project. ChatGPT: a Project or a workspace custom GPT
  • Name things the way you talk. "Bid Leveler — Framing" beats "Estimating Assistant v2." Everyone should find it without asking
  • One owner per assistant — the person who fixes it when it's wrong. Their name goes in the description
  • Connect Drive or SharePoint/OneDrive first. Then Buildertrend exports land in a folder the assistant can read. Add more connectors only when a process needs one
  • Turn memory on for individuals, keep shared assistants stateless. Personal memory learns how you work; a shared assistant should behave the same for everyone

Ground rules · one page, plain language

  • Company work happens in the company workspace. Personal accounts for personal things
  • What never goes in: client SSNs, bank/card numbers, employee HR or medical details, anything under NDA you wouldn't email to a sub
  • What's fine in the business tier: plans, specs, bids, budgets, client names and addresses in the normal course of work, your pricing
  • AI drafts, a human sends. Nothing goes to a client, sub, lender or inspector without a person reading it
  • Numbers get checked against the source. The assistant is the estimator's helper, not the estimator
  • Say when you used it if the recipient would want to know

Month one · make it stick

  • Weekly 15-minute "what did you build / what broke" at the ops meeting
  • Each assistant has a metric written down: hours per week, turnaround days, errors caught
  • Recipes live in one shared folder as plain documents, so they survive a tool switch
  • Quarterly: delete assistants nobody used, promote the ones people copied
  • When someone leaves: admin transfers their Projects/GPTs before removing the seat

Rosetta stone — what the other one calls it

Read down the "what it is" column first. The names are the least important part, and both companies rename things.

What it actually isClaude calls itChatGPT calls itBuilder translation
Ask a question, get an answerChatChatLevel 1. Where everyone starts
Instructions + your files saved as a reusable assistant you can share with the teamProject (shareable in Team)Project (workspace of chats + files) or Custom GPT (packaged, shareable, can be published to the GPT Store)Level 2. The thing you build at the workshop — "Selections Chaser," "Bid Leveler"
A written procedure the AI follows when the task comes upSkill (a folder with a SKILL.md plus templates/scripts)No exact equivalent — closest is a Custom GPT's instructions, or a plugin inside ChatGPT WorkYour SOP, in a form the tool runs
Documents, tables, code or a small app rendered in a side panel you can editArtifactCanvasWhere the scope of work or client update appears
Agent that works on your files and apps on your computerCowork (desktop app, folders, connectors, scheduled tasks)ChatGPT Work (launched July 2026; cloud or local mode) — grew out of Agent modeLevel 3. "Go read this folder of bids and build me the comparison"
Coding agent in the terminal / IDE / cloudClaude Code (terminal, VS Code/JetBrains, web)CodexCodex CLI (terminal), Codex cloud (runs in OpenAI's environment), IDE extensionOnly matters if someone writes software or automations. Jock's takeoff tool is built with one of these
Agent that drives a web browserClaude in Chrome (extension in your Chrome)ChatGPT Atlas (its own browser) / Agent modeFilling web forms, pulling data out of a portal with no export
Hook the AI up to your tools (Drive, Gmail, Outlook, SharePoint, Slack…)Connectors — built on MCPConnectors / Apps — also MCPMCP is the open standard both use, like HDMI. A Buildertrend connector would be MCP
Remembers facts about you across chatsMemory (viewable/editable)Memory (viewable/editable)On for individuals, off for shared assistants
Multi-step web research with citationsResearchDeep Research"What do lenders in our market require for draw schedules right now"
Runs something on a scheduleScheduled tasks (Cowork / Chrome)TasksLevel 4. Monday 7am: draft the week's client updates
Team-shared automation with permissions, triggered by chat, schedule or APIShared Projects + Skills in Team; agents via Claude Code / APIWorkspace agents (Business/Enterprise; off by default, admin enables)Where a company's automations live once they're real
Thinks longer before answeringExtended thinking / adaptive reasoning, effort levelsThinking models / "Think longer"Turn it up for estimating and contracts, down for emails
Design mockups and graphicsClaude DesignImage generation; no design-tool equivalentMarketing one-pagers, selection boards
Chat that saves nothingIncognito chatTemporary chatFor the sensitive one-off
The models themselvesClaude Fable (top tier), Opus, Sonnet, Haiku (fast/cheap) — version numbers afterGPT-5.x family, GPT-6 "Astra" rolling out (Sept 2026), o-series older reasoning modelsYou'll rarely choose. Default is fine; pick the biggest for estimating and contract review
Programmatic access for developersClaude API / Claude PlatformOpenAI APIOnly if you hire someone to build on it

The four levels, in each product's words

The primer from the workshop, mapped to the buttons you'll actually click.

Level
What it means
In Claude
In ChatGPT
1 · Chat
You ask, it answers. No memory of your business unless you paste it in
New chat
New chat
2 · Assistant
It already knows your specs, templates, and rules. Same behavior for everyone on the team. This is Thursday's build
Project (shared)
Project or Custom GPT
3 · Agent
It goes and does steps — reads a folder, opens apps, fills a form, produces a file
Cowork · Claude in Chrome · Claude Code
ChatGPT Work · Atlas · Codex
4 · Automation
It runs without you, on a schedule or a trigger, and tells you when it's done
Scheduled tasks · Claude Code / API
Tasks · Workspace agents

Gotchas worth knowing before Thursday

Naming traps

  • "Codex" has been three things. A 2021 code model, then a 2025 coding agent, now the harness under ChatGPT Work too. When someone says Codex, ask which
  • "Project" means different things. In Claude it's a shareable assistant with files. In ChatGPT it's a folder of chats with shared files — the shareable packaged thing is a Custom GPT
  • "Agent" is everywhere. Both companies use it for anything that takes more than one step. Ask: does it run while I'm not there? If yes, it's Level 4
  • Claude Code ≠ Cowork. Same engine, different front door — Code is for the terminal, Cowork is for your Documents folder

Setup traps

  • Four tools is the trap. Copilot in Office, Claude, Gemini, and Perplexity each "for their strength" means four logins, four bills, and nothing shared. Pick one for company work
  • Custom GPTs can be public. Check visibility before you load your price book into one
  • Personal card, company data. The most common mistake in the room. Fix it by buying the business tier this month
  • Connectors use someone's login. When an assistant reads Drive through Carl's account, it sees what Carl sees. Set up shared connections as the admin, not a person
  • Usage limits are per person. A "we hit the cap" complaint means one person needs a premium seat, not that the plan is too small