About Guides What I Use
Free Guide

How to connect your tools to your AI

The 3-level framework for working out what plugs in, what needs a bridge, and what to replace

by Lucia | @reallyusefulai

Section 01

Why this matters

The real value of Claude or any AI isn't asking it questions in a chat window. It's connecting it to the tools you already use every day. That's when it actually saves you time instead of just sounding clever.

I've been thinking about this a lot. When AI is just a chat tab, you're the one doing all the work. Copy from Gmail, paste into chat, get a draft, paste it back into Gmail. You're the bridge. You're also the bottleneck.

The shift happens when AI can read your inbox, your accounting tool, your meeting notes, your CRM, on its own. Then the work happens without you ferrying things back and forth.

But here's the catch. Not every tool is ready for that yet. Some plug in today, some need a bit of work, and some are actively making it hard. The trick is knowing which is which before you waste a weekend trying to connect the wrong one.

Who this is for

Anyone running a business who's using AI in a chat and thinking "this would be so much better if it could just see my stuff." You don't need to be technical. You just need to know what to look at.

Section 02

The 3 levels of AI-ready

Every tool in your business sits at one of three levels. Once you can spot the level, you know what to do next.

LevelWhat it meansWhat you do
Level 1
Native
Already AI-ready. Built-in connectors.Plug it in. Takes minutes.
Level 2
Bridgeable
Has an API but no AI connector yet.Build a small bridge or use a connector marketplace.
Level 3
Hostile
No API, or actively blocking it.Ask yourself if you should be using it at all.

Walk through your tool stack and label each one. Most businesses end up with a mix: maybe four tools at Level 1, three at Level 2, and one stubborn Level 3 you've been putting up with for years.

Section 03

Level 1: Plug it in

These are the easy ones. The tool's already built the connection. You just turn it on.

Level 1 · Native
Examples I use weekly

Gmail · Google Drive · Google Calendar. Native connectors in Claude. Switch on, sign in, done.

Xero · QuickBooks. Both have AI integrations. If you're on either for your books, plug them in.

Microsoft 365. Outlook, OneDrive, Teams, the lot. Built-in connectors.

Notion · HubSpot · Docusign · Canva · PayPal. All have official Claude connectors as of 2026.

To plug in a Level 1 tool, you usually:

  • 1Open the Claude Desktop app and go to Settings → Connectors (or in Cowork, Customise → Connectors).
  • 2Find the tool in the list. Hit Connect.
  • 3Sign in with the account you actually use for that tool. Approve the permissions.
  • 4Test it in a new chat. Ask Claude to read or list something to confirm it's working.
Start with one

Don't try to connect everything in one sitting. Pick the tool you use most. Get used to what Claude can do with it. Then add the next one. Stacking too many at once means none get used properly.

Section 04

Level 2: Build the bridge

The tool has an API but no AI connector yet. The tool wants to connect, no one's wrapped it for you. You can usually wrap it yourself.

Level 2 · Bridgeable
Common examples

Smaller industry-specific tools. Booking systems, CRMs, project trackers. Often have an API, often don't have a Claude or ChatGPT connector yet.

Newer SaaS tools. The 2024 and 2025 launches that haven't built AI plugins yet but have proper APIs.

Internal tools. Anything your business runs that has a way to read or update data programmatically.

Three ways to bridge a Level 2 tool, easiest first:

  • 1Check Composio or a connector marketplace. Lots of Level 2 tools already have someone else's bridge ready to install. No code, just plug it in.
  • 2Ask Claude to build the MCP for you. If the tool has API docs, you can paste them in and ask Claude Code to write the connector. This used to be a developer job. Now it's a one-conversation job.
  • 3Use Zapier or Make as a stop-gap. Not the prettiest answer, but if the data only needs to flow one way (tool to AI), an automation can shovel it across into Google Sheets or Notion, which Claude can then read.
MCP, in one line

MCP stands for Model Context Protocol. Think of it as the USB-C port for AI. Once a tool has one, any AI can plug straight in. Most Level 2 tools will get an MCP in the next year. You're just front-running it.

Section 05

Level 3: Replace or rethink

No API. No connector. Sometimes actively blocking automation in their terms of service. These are the tools where the honest question is whether you should still be using them at all.

Level 3 · Hostile
What you're looking at

Old enterprise software. No public API. The vendor wants you to use their own clunky AI add-on, on their pricing.

Tools that explicitly ban scraping or automation in their terms. Even if you could hack a bridge, you'd be one update away from getting locked out.

Anything custom-coded by your IT team 10 years ago. No documentation, no API, no path forward.

For Level 3, I ask myself three questions:

  • 1How much do I actually use this? If the answer is "we have a $500/month subscription and use 5% of the features," that's your signal.
  • 2Could I rebuild the part I actually use? Claude Code can build a simple alternative for the one or two things you really need. A custom-built tool you own is often less work than fighting with a hostile vendor.
  • 3Is there a Level 1 or Level 2 alternative? Most "essential" tools have at least one competitor that's already AI-ready. Switching is harder, but the payoff is real.
The hardest call to make

Sometimes the right answer is yes, keep paying for the Level 3 tool. If it's mission-critical and the alternatives don't exist yet, ride it out. But don't kid yourself it's the only option just because it's the one you're used to.

Section 06

Audit your stack

Knowing the framework is one thing. Walking through your tools and labelling each one is what actually moves you forward. Block out an hour this week.

Here's the simplest way to do it. Open a doc or a spreadsheet. List every tool you pay for. Next to each one, write the Level and one action.

Tool | Level | Action Gmail | 1 | Connect this week Xero | 1 | Connect this week Notion | 1 | Connect this week Cal.com | 2 | Check Composio for a connector [old CRM] | 3 | Test cheaper alternative [industry tool] | 2 | Ask Claude to build MCP [scheduling app] | 3 | Re-evaluate next quarter

You'll finish the audit with a Top 3 list to connect right away, a Top 3 list to bridge over the next month, and one or two Level 3 tools to put on the watchlist.

Don't audit alone if you don't have to

If you've got a business partner or a team, do this together. Different people use different tools. The audit usually surfaces tools nobody's actually opened in months. That's the easy win.

Section 07

Safety rules I always follow

Connecting AI to your business tools is powerful. Powerful things can break. These are the four rules I never skip.

  • 1Give it the smallest access that works. If Claude only needs to read your calendar, don't give it edit permission. Most connectors let you scope this. Take the time to do it.
  • 2Be on a paid plan. Free tiers often train on your data. Paid tiers don't. If you're connecting anything sensitive, this matters.
  • 3Turn off data sharing. Even on paid tiers, check the settings and switch off any "improve the model with my data" toggles. Defaults aren't always private.
  • 4Have a human-in-the-loop for anything that leaves the building. Set up AI to draft, but a human approves before it sends. Especially for emails, invoices, anything client-facing.
If this is for a company

Run all of this past your IT security rules first. Most companies have a policy for what AI can and can't see. Better to ask before you connect than after you've piped customer data somewhere you shouldn't have.

Section 08

Feed it into your AI brain

The tools-to-AI connection only really pays off if your AI already knows your business. That's where your AI brain comes in. Connect the tools, then point Claude at your brain folder, and now it's working with full context.

Quick recap on the AI brain idea: it's a folder on your computer that holds the stuff Claude should know about you before any conversation starts. Who you are, how you talk, what your business is, what your priorities are. Once you point Claude at it, every chat starts with full context.

When you add tool connections on top of that brain, the combination gets really powerful. Claude can now read your inbox and already know which clients are which. Pull your calendar and know which meetings matter most. Draft a proposal and know your voice without you re-explaining it.

Don't have an AI brain yet?

Build that first. Here's the free guide. 20 minutes of setup, then connecting tools makes ten times more sense.

Want the printable version?

Get the Tool-by-Tool Audit Checklist

I packaged the audit into a one-page PDF you can run through with your team. Lists the common tools, the Level for each, and the first action to take. I'll email it straight to you.

Free. One email with the download. Unsubscribe whenever.

Check your inbox. The Tool Audit Checklist is on its way. If it's not there in a minute, check spam.

That's the framework.

Plug in your Level 1s this week. Pick one Level 2 to bridge this month. Watch the Level 3s.

Got a tool you're not sure how to label? DM me @reallyusefulai

More free guides at reallyusefulai.co/guides

← Back to all guides