--- title: "Workmap: AI Workflow Mapping for New Hampshire Businesses | T10" url: "https://t10.net/tools/workmap/" description: "Workmap is T10's guided workflow review. In one 75-minute working session we map how a process runs today, find where AI or automation can help, and give you a practical plan." lastmod: "2026-10-15" --- [Tools](https://t10.net/tools/) · Guided workflow review # Workmap: find the right places to use AI in your business Less retyping, fewer errors and faster service, with people still involved where judgment matters. Workmap is our guided workflow review. We work with you to map a real business process, find the repetitive work and bottlenecks, and decide where AI or automation can help. In a 75-minute working session, you leave with a clear workflow map, a prioritized plan and practical next steps. [Book a free review](https://t10.net/#book) ![Illustration of a meeting room at dusk: a wall screen shows a swimlane workflow map with steps coloured by work mode and an approval check, above a laptop of call notes, a phone on speaker and a sketched flow](https://t10.net/media/tools/workmap-hero-1200.webp) You see the map on screen as it takes shape. Nothing is marked for automation until you agree to it. Example ## A heating company's calls to invoices The problem Calls are written on a paper pad and typed into Jobber when the office manager has time. Estimates go out from the owner's personal Gmail. Invoices wait until Thursday. The improvement Every call and message is logged in Jobber automatically. Invoices are drafted the day the job closes. The owner still approves estimates over $500 and invoices over $2,000. The expected result About 5 hours a week of retyping and invoicing off the office manager's desk, no lost messages, and invoices out the same day instead of on Thursday. An illustrative example. The business is fictional; the process is typical of the trades companies we work with. On the call ## We map the process while you describe it. 1. ### Listen You describe the work the way you would to a new hire. We take notes in your words, and Workmap turns them into suggested steps for us to check with you. If you're happy for the call to be recorded, we also read the transcript afterwards to catch anything we missed. 2. ### Map Each person or role gets a lane. Steps sit in order, with the systems they touch: the phone, the paper pad, QuickBooks, the group text. We come with lanes and questions for your kind of business, from trades and professional offices to medical practices and boarding stables. 3. ### Mark For every step we agree who should do it: a person, a person with AI helping, AI with a person approving, or AI on its own. 4. ### Set the rules Wherever AI prepares work, you write one plain sentence for when a person must approve it. ### Start with the whole business. Before we map any one process, we sketch the whole business with you on a whiteboard: who comes to you, what happens next, and the systems each part touches. Anything you mention that we haven't drawn yet goes on a sticky note. Then we circle the part worth looking at first. The circle becomes a detailed map, and once it's mapped the board shows the hours a week AI or automation could take on there. Everything outside the circle stays on the board for the next session. ### The map uses your words. Steps are named the way you said them: "writes it on the pad", "prices the job from memory". When the notes mention an exception, such as "unless it's an emergency", Workmap flags it so we ask what happens then. Before we talk about AI, we walk through the map with you until it matches how the work really happens. ### Every system goes on the map, paper included. Each step records what it touches. The plan then shows which of those systems AI can work with directly, which it has to use through a website like a person would, and which stay with your team. - Phone - Text - Paper - Email - Spreadsheet - Accounting - Calendar - Website form - Files - Whiteboard Who does each step ## Five ways to handle the work. Most steps shouldn't be handed to AI outright. We agree the right option for each step together, and the map shows how many hours a week AI or automation could take on. - Person only Judgment calls, licensed work, and anything you'd rather keep human. - Assist Your person does the work; AI drafts, looks things up or fills in the form. - AI + approval AI does the work, and a person approves before anything leaves the building. - Automated AI or automation finishes the job on its own, inside the rules you set. - Exception The situations where the automation stops and hands the work back to a person. A person stays in charge ## Every approval point is clearly defined. Wherever AI prepares work for someone to approve, you set the rule in plain words. We won't produce a plan while any approval step is missing its rule. Priorities ## Prioritize the improvements worth making. We group steps into improvements, like "log every call in Jobber" or "invoice the same day", and rate each for what your customers notice, the risk if it goes wrong, and the effort to build. Hours a week come from the map, so the ones worth doing first are easy to see. What you keep ## A plan you can read, and the details your implementation team needs. ### For you The map Your workflow in your own words, with the whiteboard of the whole business, as a read-only link and a printable PDF. Policy sheet What AI may do on its own, what it prepares for approval, and when it stops. Checkpoint sign-off Every point where a person approves, written out for you to agree to. ### For your implementation team Build plan Which tool builds each piece and why: a Grok Bot for websites with no API, an automation workflow, or a custom agent. Grok Bot setup guide Step-by-step setup for any work a Grok Bot takes on, with the approval rules and test plan written in. Developer brief A first-sprint brief for a custom agent that an engineer can hand to Claude Code or Cursor, with acceptance tests. Agent spec Goal, scope, tools, approval gates, escalation and test cases. Systems checklist Each system the agent needs, and the access it should have. Open questions Anything the call didn't settle, so nothing is guessed later. Workflow skeleton A starting N8N workflow that follows the map. How it works ## From one conversation to a first improvement. 1. 01 ### Book a free review Tell us where the time goes. Together we pick one process worth improving, such as calls to invoices or quotes to orders. 2. 02 ### Map it together In a 75-minute working session we sketch the whole business, then draw the process as it really runs, with the people who do the work, then agree who should handle each step and when a person approves. 3. 03 ### Prioritize the improvements We rank the possible improvements by hours saved, what your customers notice, the risk if something goes wrong, and the effort to build. 4. 04 ### Leave with a practical plan You get the map, the approval rules and a plan for what to improve first. Build the first piece with us, or hand the plan to anyone you like. Questions ## Workmap: straight answers. Can we use Workmap ourselves? No. Workmap is a guided review: our consultants run it with you in a working session. You keep everything it produces: the map, a PDF of it, the policy sheet and the implementation plan. Who can see our map? Only the T10 consultants on your engagement. We send you a read-only link that expires, can be limited to named email addresses, and can be switched off at any time. Does AI decide what gets automated? No. Workmap can suggest steps from the notes, but a consultant confirms each one with you. A step is only marked for AI or automation once you've agreed. Which AI tools do you build with? Whatever fits each step. Work on websites that can't connect to other software usually suits a Grok Bot, which works in the browser like a person. Moving data between systems that can connect suits an automation workflow. Drafting and judgment calls suit a custom AI agent. The plan shows which step needs which. How long does it take? One process usually fits in a single 75-minute working session. A business with several distinct processes might need two or three. The other processes you mention stay on the whiteboard, so the next session starts from them. Do we have to build with T10 afterwards? No. The plan is written so any developer or implementation partner can start from it. Most clients build the first piece with us, because it is small and they can see it working quickly. New Boston · Statewide ## Start with one process worth improving. [Book a free review](https://t10.net/#book)