What it does: See every tool you pay for on one page, and where 2 tools do the same job. It reads your tool list, your AI policy and your software receipts, then fills a department, job and tool table.
Use it when: Tools got bought one at a time, nobody has the full list, and every new AI chat has to be told again what you use.
You get: A filled table (department, job, tool, owner, overlap, gap, AI allowed, data it holds, monthly cost from receipts) plus a short list of overlaps, gaps and tools where AI is No or Ask. It makes a new Google Sheet only after your yes.
This one runs in Claude: paste it there.
You are my operations lead, a senior ops pro with 20 years of sorting out the software small teams pay for. Goal: map every tool my team uses by department, then the job it does, then the tool, so I can see where 2 tools do the same job, where a job has no tool and where AI isn't allowed. Done is a filled table I can paste into my "Map your tools" sheet. Context: I run [your business]. Our tools got bought one at a time by whoever needed them. Nobody has the full list, so we pay twice for some jobs, and every new AI chat has to be told again what we use. One map fixes both, because people and AI can read it. First, check what you can open: - My Google Drive: look for a tool list, a "Map your tools" sheet and any AI or data policy doc. Tell me what you found. - My Gmail: search the last 90 days for software receipts and invoices (words like receipt, invoice, subscription, renewal). Tell me how many tools you found that way. - If you can't open one, tell me: open https://www.simpleai.community/connect/, pick your AI, then that tool, and follow the steps. If you can't open either, ask me the 3 questions below and work from my answers only. Ask me these, then run. Skip any I already answered or that my files answer. 1. Which departments do we have? (Default: Sales, Marketing, Ops, Finance and Support.) 2. Which tools does each department use, and who owns each one? (Default: the tools you found, with the owner as [check: owner].) 3. Do we have rules on AI? (Default: no rules found, so AI allowed is Ask for every tool.) Do this: 1. List every tool from my files, my receipts and my answers. Count each tool once, even if it shows up in many places. 2. For each tool, write the jobs it does for us in plain words that start with a verb, like "Send invoices" or "Track deals". Write the job, not the feature. One row per department, job and tool. If no file or answer says which department uses a tool, add [check: department]. 3. Use the same words for the same job in every department, so overlaps line up. "Bill customers" and "Send invoices" are one job. 4. Overlap: write "Yes, also [other tool]" when 2 or more tools do the same job. Check every job, across departments too. 5. Gap: add a row for a job that has no tool, only if my files or answers name that job. Write "Yes" and leave the tool, AI allowed and cost blank. Don't guess at jobs. 6. AI allowed: Yes, No or Ask. Only write Yes or No if a policy doc or I said so, and name the source. Otherwise write Ask. If a tool holds card, bank, health or pay data, add [check: sensitive data]. 7. Data it holds: the kind of data only, like "customer emails". Never copy the data itself. 8. Monthly cost: only from a receipt, with its date. If there's no receipt, leave it blank. If a receipt is yearly, write the monthly amount and the real bill, like "$10 a month (billed $120 a year)". If a receipt is older than 90 days, keep the tool in its own row with [check: older receipt, still paying?] and leave it out of the tools found count. Example of one row, match this shape only: "Finance | Send invoices | QuickBooks | Bookkeeper | Yes, also Stripe | No | Ask | Customer billing info | from receipt, Oct 3" Give me: - Counts first: tools found, rows, overlaps, gaps, and AI Yes, No and Ask counted per tool. - The table with these columns in this order: Department, Function, Tool used now, Who owns it, Overlap, Gap, AI allowed, Data it holds, Monthly cost. - A short list under 150 words: each overlap with its tools, each gap, and each tool where AI is No or Ask. Then ask: "Want me to put this in a new Google Sheet?" Only after my yes, make a new sheet. Never write over an old one. Before you show me, check your work: - Every tool from my receipts, files and answers is in the table. Recount, don't guess. - Every "Yes, also" names a tool that is in the table for the same job. - No AI allowed says Yes or No without a source. - No cost is shown without a receipt and date. - No password, card number or login is in the table. Rules: - Drafts only. Don't cancel, buy, change or delete anything, and don't make a file until I say yes. Saving this skill is fine. - Don't make up a tool, owner, cost or rule. Use only my files, my email and what I tell you. - If something is missing, write [check: what is missing] and keep going. - Plain words. Short sentences. No em dashes, no semicolons. Last, save these steps as a skill called "Map My Tools" so you do it this way each time I ask. To run it again each quarter or when we add a tool, I just say: run Map My Tools.
You need
Gmail
Google Drive![]()
![]()
Any AITested on sample data
Connect first: your email. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on: The E-Myth Revisited. "Most companies organize around personalities rather than around functions", so the map goes by job, not by who bought the tool. By Corey Leon
Copilot version
Needs a Microsoft 365 Copilot work license. Grounded in your work email, files and meetings. Run it once, then save it in Copilot Prompt Gallery.
Goal: You are my operations lead, a senior ops pro with 20 years of sorting out the software small teams pay for. Map every tool my team uses by department, then the job it does, then the tool, so I can see where 2 tools do the same job, where a job has no tool and where AI isn't allowed. Context: I run [your business]. Our tools got bought one at a time by whoever needed them. Nobody has the full list, so we pay twice for some jobs, and every new chat has to be told again what we use. Source: Use only /[my tool list in OneDrive or SharePoint], /[our AI or data policy doc] if we have one, and my Outlook receipts and invoices for software from the last 90 days. First, check that you can open them. Tell me how many tools you found in each. If you can't find one, tell me which one is missing. Or I will tell you our tools instead. Expectations: 1. List every tool once, even if it shows up in many places. 2. For each tool, write the jobs it does for us in plain words that start with a verb, like "Send invoices". Use the same words for the same job in every department. One row per department, job and tool. 3. Overlap: write "Yes, also [other tool]" when 2 or more tools do the same job, across departments too. 4. Gap: add a row for a job with no tool only if my files name that job. 5. AI allowed: Yes, No or Ask. Only write Yes or No if the policy doc says so, and name it. Otherwise write Ask. If a tool holds card, bank, health or pay data, add [check: sensitive data]. 6. Monthly cost: only from a receipt, with its date. If the bill is yearly, show both. If there's no receipt, leave it blank. Example of one row, match this shape only: "Finance | Send invoices | QuickBooks | Bookkeeper | Yes, also Stripe | No | Ask | Customer billing info | from receipt, Oct 3" Give me the counts first, then an Excel-ready table with these columns in order: Department, Function, Tool used now, Who owns it, Overlap, Gap, AI allowed, Data it holds, Monthly cost. Then a list under 150 words of each overlap, each gap and each tool where AI is No or Ask. Before you show me, check that every tool from my receipts and files is in the table, and that no AI allowed or cost appears without a source. Rules: Drafts only. Leave it as a draft for me. Don't cancel, buy, change, share or delete anything. Don't make up a tool, owner, cost or rule. Never copy a password, card number or login into the table. If something is missing, write [check: what is missing]. Plain words, short sentences, no em dashes, no semicolons. When it works, save this in Copilot Prompt Gallery as "Map My Tools" and run it again each quarter.
See a real example
Tested on sample data Run by Claude on made up sample input (tool results simulated). Judged in a separate strict Claude pass. Passed first run with no major faults. Small fixes after it: a receipt older than 90 days gets its own flagged row and stays out of the count, yearly bills show the real bill, a gap row leaves AI and cost blank, and a guessed department gets [check: department]. Re-run passed.
Watch: no video for this one yet.
AuthorCorey Leon