Start free trial
Cookbook / Sales work with Claude or ChatGPT

Cookbook

Sales work with Claude or ChatGPT

A shared sales folder with proposals and call notes, a teammate with access, and the AI tools that can work on it today.

Goal: one folder with every account's proposals, call notes and pricing, shared with a teammate, that your AI tool can read and update. Every change has a version you can go back to.

Which AI tools can reach Wiele

The ChatGPT and claude.ai chat apps, in the browser or on desktop, can't connect to Wiele today. Their connectors sign in with OAuth, and Wiele's MCP server only accepts a bearer token.

These work now:

  • Claude Code and Codex, in the terminal or in their desktop and IDE apps. They run the wiele CLI, or connect to the MCP server with a token.
  • Cursor's agent, through the CLI or the MCP server.
  • Any other agent that runs terminal commands or sends a fixed Authorization header to an MCP server.

If your team drafts in ChatGPT or claude.ai, keep doing that and let a coding agent move the result into Wiele. The rest of this recipe uses Claude Code; Codex and Cursor work the same way.

Setup

An owner or admin creates the workspace. New workspaces are private.

wiele workspace create "Sales"
mkdir -p ~/Wiele/sales/accounts ~/Wiele/sales/templates
wiele track sales:/ ~/Wiele/sales
wiele push --directory ~/Wiele/sales -m "Start sales folder"

Give Anna, who works the same accounts, write access to everything. Give Ben, who only needs the templates, read access to that folder:

wiele access invite anna@example.com --path sales:/ --role write
wiele access invite ben@example.com --path sales:/templates --role read

Each of them signs in, accepts the invitation and fetches the folder:

wiele fetch sales:/ ~/Wiele/sales
wiele sync enable --directory ~/Wiele/sales

With sync on, each checkout pulls the others' pushes about every 30 seconds.

Install the Wiele skills for Claude Code on each machine so the agent knows the commands. See Working with agents.

Folder layout

sales:/
  accounts/
    lead-104/
      call-notes.md
      proposal.docx
      pricing.xlsx
    lead-117/
      call-notes.md
  templates/
    proposal-template.docx
    follow-up-email.md
  playbook.md

Working with the agent

Start Claude Code in ~/Wiele/sales.

"Share the lead-117 folder with Anna, with edit access."

wiele access invite anna@example.com --path sales:/accounts/lead-117 --role write

"Write up today's call with lead 104 from my notes and save it."

The agent appends to accounts/lead-104/call-notes.md, then:

wiele status
wiele push -m "Call notes for lead 104, Oct 7"

"What changed in the sales folder today?"

wiele pull
wiele branch history main
wiele revision show SHA

revision show lists the files each revision changed. History doesn't say who pushed it, so for that, ask Anna or keep a short changelog in each account folder.

"Draft a follow-up email from the template, but don't touch the shared copy yet."

wiele copy create lead-104-follow-up
wiele sync pause
wiele copy switch lead-104-follow-up
wiele sync resume

Switching needs a clean checkout with sync paused. The agent drafts on the copy, pushes, and later switches back with wiele copy switch main the same way. Anna reviews it with wiele copy compare lead-104-follow-up --to main, and whoever has write access merges it. See Conflicts and merging.

"The proposal looked better yesterday. Put it back."

wiele stat sales:/accounts/lead-104/proposal.docx
wiele history RESOURCE_ID
wiele restore accounts/lead-104/proposal.docx --revision SHA
wiele push -m "Restore proposal from yesterday"

When Anna and you edit the same file

If you both change pricing.xlsx before pulling, the second push fails with PUSH_CONFLICT. Wiele doesn't merge spreadsheets. The second person runs wiele pull --keep-local, gets the other version as a recovery file, copies their changes across and pushes again. To avoid it, give each account an owner, or draft changes on a copy.