AI for small business: a practical guide

This guide is for owners and operators of companies with 5 to 50 people and no dedicated ops, finance, or data staff, where the owner's day disappears into checking the bank, answering quote requests, chasing invoices, and answering the same staff questions.

By the end you will have one type.com workspace running seven workflows. Each runs on a schedule or when an email arrives, posts into a channel your team can see, and leaves anything going to a customer, supplier, or candidate as a draft for a person to approve. You keep your tools and reuse the AI subscriptions you already pay for.

The examples follow Cedar Row Heating & Air, a fictional 24-person HVAC company in Columbus, Ohio: Dana Whitfield owns it, Luis Romero runs the office and billing, Tom Okafor writes estimates, Kendra Bishop manages technicians, and Grace Lin is the part-time bookkeeper. The time ranges below are typical for an owner-run company doing this by hand; time your own week first.

Small businesses often adopt AI one app per job, each with its own login, its own copy of your price list, and its own fee. In type.com, a Space is a shared computer for a team: one set of connections, instructions, skills, and memory, with channels for each kind of work. In a small company the whole company is the team, so start with one Space, plus a private one for work not everyone should see, which usually means money.

Why not a private channel? Channels share their Space's access, so if only three people should see the bank balance and payroll totals, they need their own private Space. Add a third Space only for a group with different access, such as a second location. Use Sidekick, which is private to you, for your personal inbox and anything about one employee.

Owner: Dana. Inputs: QuickBooks, the office@ inbox, the job board export in Drive, and Dana's calendar. Choose Create, then Automation, pick Back Office, set the destination to daily-brief and the schedule to weekdays at 7:00 AM, America/New_York.

Most owners check the bank, the invoicing tool, the inbox, and the calendar before 8:00. The briefing reads them and says which one needs you. On Wednesday, October 7, it showed $184,320 in checking with Friday's $61,400 payroll covered, $27,480 invoiced and $18,240 collected on Tuesday, and three emails out of 31 that needed Dana.

Keep your personal inbox out: Back Office reads the shared office@ mailbox, which Luis and Grace already see. For your own email, use Sidekick, your private place to work with AI for a morning summary only you can see.

Review rule: Dana reads it and replies in the thread with who handles what. The briefing changes nothing in any system.

Owner: Tom. In the company Space's Automations page, add an email source with inquiries as the destination. A Space gets one inbound address, created when you ask for it, and the destination is fixed once created. Then add a Gmail filter on office@ that forwards your website form notifications and quote requests to that address. Send a test inquiry and confirm a thread opens.

Speed wins small jobs: the first reply with a time and a price usually gets the visit. The draft does the price and calendar lookup, and Tom spends two minutes editing.

On Tuesday at 6:40 PM, after the office had closed, Janelle Price at Northgate Property Management asked about three rooftop units, one not cooling. The draft offered two visit times from Tom's calendar, the $149 diagnostic fee, and a maintenance agreement at $1,140 a year ($190 per unit per visit, two visits), asked for unit ages and tonnage, and did not guess at a repair price.

Review rule: Tom or Dana approves every reply. Anything off the Price Book, any discount, and any job over $15,000 goes to Dana first.

If you have a sales team with a pipeline and follow-up sequences, AI for sales goes deeper. For high-volume service questions, see AI for customer service.

Owner: Luis. Runs Tuesdays and Fridays at 9:00 AM ET in collections, from QuickBooks open invoices and the office@ inbox. Small businesses rarely lose money to customers who refuse to pay; they lose it to invoices nobody chased.

Careless automation reminds customers who already paid or promised a date, nudges a disputed invoice, or takes the wrong tone with a good customer. The instructions check all three.

Tuesday's test run found 14 overdue invoices worth $34,600 and drafted 9 reminders, including a firm one to Brookfield Apartments for $6,480 at 22 days. It held Kessler Bakery's $2,140 because the owner had emailed about a warranty part, and suggested Dana call Lakeview Church about $9,900 at 41 days.

Review rule: Luis edits and sends approved drafts from office@ and notes what went out. A person still creates invoices in QuickBooks.

Shortcut: the Invoice Generator & Chaser skill in the type.com Skills Library packages this workflow: four tiers of follow-up, no repeated tier, no late-fee or legal language unless you configure it, and nothing sent without approval.

Owner: Dana. Runs Mondays at 8:00 AM ET in numbers, from QuickBooks, the job board export, and the inquiries channel. Pick eight to ten numbers you would act on, define each one, and keep the order fixed so changes jump out.

For September 28 to October 4, Cedar Row invoiced $142,600 across 96 jobs, a $1,485 average ticket. Close rate was 38% against 40%, and callbacks (return visits for the same problem within 30 days) were 4 against 3. Two were on the same furnace model, which became Kendra's item.

Review rule: Dana assigns each flag in the thread. If a number is wrong, fix its definition in the instructions.

Shortcut: if cash is tight or seasonal, the Cash Runway Forecaster skill builds a 13-week cash forecast from receivables, bills, payroll, and recurring costs instead of an average burn rate. For the bookkeeper's monthly close, Month End Close Checklist tracks close tasks by owner and dependency. Both are covered in depth in AI for finance and operations.

Owner: Luis, with Dana approving anything about prices. Runs Thursdays at 10:00 AM ET in marketing, from the job board export, technicians' photos in a Drive folder, new reviews exported or pasted into a Reviews sheet, and the how-we-work documents.

This week's pack had three posts (a furnace install, a filter reminder before the first cold week, a technician spotlight), six review replies, and one theme: two reviews mentioned a long arrival window, which went to Luis as a scheduling problem.

Review rule: Luis or Dana approves and posts each item. No customer addresses or faces without permission, and no job details in a reply to a negative review.

Shortcut: the B2B Newsletter Writer skill drafts a newsletter for business customers, such as Cedar Row's property managers, from your notes and links, learns your voice from past issues, checks for unsourced numbers, and never sends. The Review Insight Miner skill groups reviews and complaints into themes and ranks them by how much they pull your rating down. More channels, budgets, and campaign reporting are in AI for marketing teams.

Owner: the hiring manager, here Kendra. Runs on demand in the hiring channel. Each hire needs a job post, interview questions, and a first week that is usually improvised.

Keep the channel for documents only. Candidate names, resumes, and evaluations do not belong in a company-wide Space; keep them in your applicant tracking system or a private thread limited to the interviewers.

Review rule: the hiring manager edits and owns every word. AI does not screen, rank, or suggest pay for candidates. Have whoever handles HR check posts and questions against local employment law.

For recruiting pipelines, policies, and people operations in more depth, see AI for HR.

Owner: Luis. Writing every procedure down at once never happens; writing down what people actually ask does.

Start with five documents in how-we-work: Pricing and Fees, Scheduling and Dispatch, Warranties and Returns, Safety, and Who Approves What. Dictate each in a thread, let AI draft it, and have the person who knows the process edit the document directly.

In ask-office, AI answers from the documents and names the one it used. If nothing covers it, it says so and tags Luis.

Every Friday at 3:00 PM ET, an automation lists the week's questions that no document answered or that a person corrected. On Friday, October 2, it found three, and each became a short addition to a document.

Space memory is helpful context, not a source of truth; rules and prices belong in documents you can edit. More in shared AI memory for teams.

A type.com plan includes a set number of members and a shared monthly AI usage allowance, metered at the model provider's published rates. New workspaces start with a 14-day trial that includes trial credits. Plans and prices are on the billing and pricing page; count the people who will actually work in type.com before choosing one.

The biggest saving is the subscription you already have. Requests that run through a connected Claude or ChatGPT subscription do not draw down the workspace allowance. A subscription is personal and covers the turns you start and the automations you create, so whoever holds it should create the automations. Not every request type is eligible, and subscriptions have their own limits.

Enforce access at the tool, not just in the instructions. The type.com docs note that read-only tells the agent not to make changes but does not block changes at the connected service. Use QuickBooks user roles, Drive folder selection, and no bank connection that can initiate payments. For approval patterns, see AI agent approval workflows.

Scheduled runs use the creator's identity, connections, and billing, while Test runs privately as whoever presses it. When someone leaves, recreate their automations under a new owner first. Three failed runs in a row pause a schedule.

Keep data narrow: money in the private Space, personal email and anything about one employee in Sidekick or a private thread, and passwords, bank details, and card numbers out of threads and instructions entirely.

Never automate payroll and pay decisions, tax filings, hiring and firing, refunds and payments, legal replies, or safety advice. AI can prepare the paperwork; the decision and the click stay with a person.

Put each on its reviewer's calendar, or runs pile up while they are on a job site.

New automations start paused. Save, then Test, which runs privately as you, compare with what you would have done, then Enable. The scheduled automations docs cover recovery if a schedule pauses itself. Turn every correction into a line in the instructions.

Record the baseline before week 1. If a workflow saves time but needs heavy correction every run, fix it before adding another.

To see how a recurring report gets built step by step, read how to automate a weekly team report. For more ready-made workflows, see the best AI skills for B2B teams.