AI copilots in SaaS apps: what they are, how they work and what they cannot do
What an AI copilot inside a SaaS app does, how it reads your data, how it differs from an agent, where it fails, and the seat-cost arithmetic before you buy.
The apps you already pay for now have a sidebar that drafts emails, summarizes meetings and answers questions about your files. You need to know what it can see, how far you can trust it and whether the extra seat price is worth paying. An AI copilot is an assistant built into a software product that uses a language model to help a person do a task in that product. The person reviews the result and decides what happens next.
That last sentence is the line between a copilot and an agent, and it decides most of the risk. This guide covers how copilots work, what they typically do, what they cannot do, and how to check the seat cost before you buy. For the basics of the software they sit in, see What is SaaS?.
Copilots in plain terms
Think of a co-driver in a rally car. The co-driver reads the notes, calls the next bend and warns about the ditch. The driver keeps both hands on the wheel. If the co-driver misreads a note, the driver can still brake.
A copilot is the co-driver. It suggests, drafts and summarizes; you accept, edit or ignore. An agent, by contrast, takes the wheel for a stretch. Microsoft’s AI agent shared responsibility model describes an agent as one that “invokes tools, calls APIs, writes data, and triggers workflows without a human approving each step”.
GitHub’s description of GitHub Copilot shows both modes in one product. For assistive features, “You review and apply each suggestion.” For its agentic features, where Copilot works through several steps toward a goal, “You remain responsible for reviewing and approving.”
How a copilot works
Microsoft’s data, privacy and security page for its Microsoft 365 assistant (updated October 8, 2026) names three parts, a pattern most copilots share:
- A large language model that reads and writes text.
- Your organization’s content, “such as emails, chats, and documents that you have permission to access”.
- The app you are working in, such as Word or PowerPoint.
The page also records a rename: Microsoft 365 Copilot is now called Microsoft Copilot, and some licenses may keep the old name during the transition.
The second part is the one to understand. Before the model answers, the copilot retrieves content that matches your request and adds it to the prompt. This is called grounding. Microsoft states that its copilot “only surfaces organizational data to which individual users have at least view permissions”. It also states that prompts, responses and data accessed through Microsoft Graph “aren’t used to train foundation LLMs”. Other vendors make their own commitments, so read each vendor’s terms rather than assuming the same.
What copilots typically do
Microsoft’s Copilot overview (updated October 14, 2026) lists in-app features. Together with GitHub’s, they show the usual pattern: draft, summarize, analyze, explain.
| App | What the copilot does (vendor’s description, checked October 2026) | Who acts on the result |
|---|---|---|
| Word | Draft, rewrite and summarize documents | You |
| Excel | Analyze data, create formulas and visuals | You |
| Outlook | Draft emails and summarize threads | You send |
| Teams | Summarize and transcribe meetings, capture action items | You follow up |
| GitHub | Inline code suggestions; answers about files and repositories | You review and apply |
| GitHub, agentic features | Works through several steps, edits files, prepares pull requests | You review and approve |
The last row is where a copilot product starts to behave like an agent. The approval step is still yours, but more happens before it.
What copilots cannot do
Guarantee accuracy. Microsoft’s own page says the responses that generative AI produces “aren’t guaranteed to be 100% factual”, and that users should use their judgment before sending output to others. A summary can drop the one sentence that mattered. A formula can look right and reference the wrong column.
Fix your permissions. A copilot that respects permissions also respects bad ones. If a salary spreadsheet is shared with the whole company, the copilot can surface it to anyone who asks the right question. Microsoft points admins to SharePoint Advanced Management, which “helps you reduce oversharing”, for this reason. The copilot did not create the exposure; it made it easy to find.
Know what it was not given. A copilot sees what it retrieves for that request. Content in a system it is not connected to does not exist for it.
Act on its own, by design. That is a feature. When you need actions taken without review, you are buying an agent, with a different risk profile.
The seat cost, worked through
Copilots are usually sold as a per-user add-on. Prices change often, so check the vendor’s page on the day you buy.
Example: GitHub lists Copilot Business at $19 per granted seat per month and Copilot Enterprise at $39 (checked October 17, 2026). A team of 40 developers, with a hypothetical loaded cost of $75 an hour per developer:
- Business, yearly: 40 x $19 x 12 = $9,120.
- Enterprise, yearly: 40 x $39 x 12 = $18,720.
- Break-even on Business: $19 / $75 = 0.25 hours, about 15 minutes saved per developer per month.
- Break-even on Enterprise: $39 / $75 = 0.52 hours, about 31 minutes per developer per month.
The seat price is a floor, not a cap. GitHub’s plans documentation says each Business seat adds 1,900 AI Credits to a shared pool. Use beyond the pool is billed at $0.01 a credit if your admins allow it. The break-even is low, which is why the real question is usage, not price. If only 25 of the 40 developers use it, the Business cost per active user is $19 x 40 / 25 = $30.40 a month. Measure active use for a month or two before you buy seats for everyone. For how seat-based licenses work in general, see SaaS licensing.
Common mistakes
- Rolling out before cleaning up sharing. The copilot surfaces whatever each person can already open. Why it happens: oversharing was invisible until search got this good. Instead: review sharing on sensitive sites and files before switching the copilot on.
- Treating output as fact. Drafts and summaries can be wrong in ways that read well. Why it happens: the text is fluent and confident. Instead: check anything that leaves your team, and keep the human review step in every process.
- Buying seats for everyone on day one. Unused seats raise the real cost per active user. Why it happens: the vendor’s bundle price looks simpler. Instead: start with a pilot group and use the vendor’s usage reports to decide on the rest.
- Calling a copilot an agent, or the reverse. The approvals and permissions you need differ. Why it happens: vendors use both words for the same product. Instead: ask who acts on the output and whether a person approves each action.
For how Microsoft’s and Google’s suites package their tools, see Microsoft 365 as SaaS and Google Workspace as SaaS.
Sources
- Microsoft Learn, Data, privacy and security for Microsoft Copilot and What is Microsoft Copilot?, checked October 17, 2026.
- Microsoft Learn, AI agent shared responsibility model, checked October 17, 2026.
- GitHub Docs, What is GitHub Copilot? and GitHub Copilot plans, checked October 17, 2026.
In three sentences
An AI copilot is an assistant inside a SaaS app that drafts, summarizes and analyzes using your data, while a person reviews and acts on the result. It sees what you already have permission to open, so oversharing becomes visible, and its output is not guaranteed to be accurate. Seat prices such as GitHub’s $19 a month break even at minutes of saved work, so measure who actually uses it before you buy seats for everyone.
