The tools I use
The tools I use make more sense when you can see the job each one has. A writing assistant, a business record, and a connection between systems do different things. I would map those jobs before adding another subscription.
What you will leave with
A tool map that makes duplication and missing ownership visible.
Practice time: about 20 minutesKnow where the authoritative information lives
The source of a number, decision, or commitment should remain easy to find. A summary in a chat is useful working material; it should not silently replace the underlying business record.
I use this distinction when explaining a setup: the record holds the facts, the assistant helps produce a draft, and a person approves the action. A connection moves information between those places. Each needs a clear purpose.
The tools, grouped by the work
This is a map of tools described in the practice, rather than an exhaustive inventory of every experiment or account. It is not a claim that the same setup fits your organization.
- Claude and ChatGPT: Writing, thinking, and another view on a draft. Give the assistant approved material and a clear task. Another model's agreement still needs a source check.
- Google Workspace: Mail, calendars, and working documents. An assistant's access depends on the account, enabled features, and permissions; a connection should be chosen for a task.
- Notion: Plans, projects, and decisions that need to be found again. Agree on where the current decision lives so a draft is not mistaken for an approved instruction.
- Shopify and QuickBooks: Retail and accounting records. Keep calculated results traceable to the relevant records and period. Separate reading or drafting from permission to change records.
- Zapier: A way to connect steps between tools. Start with a narrow task, a test input, a visible result, and a way to stop or handle duplicates.
- Granola: A meeting-notes aid. Follow the meeting's recording and consent rules, check names and actions, and choose where approved notes belong.
- Beehiiv, Calendly, and Doodle: Publishing the notes, booking a conversation, and gathering date preferences. Keep the final send, availability, and event decision visible to the person responsible.
For account selection and current vendor controls, use the tool-choice guide. Exact features and availability change; this page explains roles rather than promising a particular plan includes them.
Follow a customer reply through the setup
Worked example / Fictional practice material
A question arrives in the inbox. A staff member takes the approved facts from the relevant record, asks an approved assistant for a draft, checks the facts and commitments, and sends the reply through the normal mail system.
The inbox holds the exchange. The business record supports the facts. The assistant drafts. The staff member owns the reply. There is no need to connect every system to try this once.
If that manual experiment proves useful, consider whether a connection would remove repetitive handling. Add the review and stop steps before giving a recurring system broader access.
Make your own map before buying more
For each tool, write its job, owner, data access, output, and destination. Look for two tools doing the same job, facts copied into several places, and steps no one owns.
Ask what would happen if the tool were unavailable tomorrow. Keep an export or manual fallback where the work needs one. A useful setup is one your team can explain, operate, and change when the work changes.
Keep this
Map the tools behind one job
Copy this into your own document and fill in the brackets. Use approved or fictional material when trying it with AI.
JOB: [One piece of work, from request to completion.]
SOURCE OF FACTS: [System, record, owner, current version.]
ASSISTANT: [Approved tool, account, and allowed input.]
DRAFT: [What it produces and where the reviewer finds it.]
REVIEW / ACTION: [Who checks, who approves, who acts.]
CONNECTIONS: [Data moved, permissions, error handling, duplicate handling.]
RECORD: [Where the approved result belongs.]
FALLBACK: [How the job works without this tool.]
SIMPLIFY: [Duplication to remove or a missing owner to name.]
NEXT CHANGE: [Smallest improvement worth testing.]Want help applying this to your organization? Bring the job you have in mind, and we can work out a useful next step.