What apps does a small team need?

One for each of seven jobs: chat, video calls, documents, a task board, a shared calendar, file storage and an AI assistant. Most teams get chat, video, documents, calendar and storage from Google Workspace or Microsoft 365, then add a board and an assistant.

Should a small team use Google Workspace or Microsoft 365?

Usually whichever the team already uses for email, since calendar, files and sign-in come with it. If you are starting fresh, consider what your clients use, because sharing documents and meetings with them is easier on the same suite.

How many apps is too many for a team?

More than one per job. Seven jobs can be covered by five to seven apps. The warning sign is two apps doing the same job, such as two chat tools or two boards, because work then has two homes and people check neither.

Is it safe to use a free AI assistant account for work?

Check the provider’s data policy first. Business and consumer plans often handle data differently, including whether chats may be used for training. Many teams use one business plan with an admin, and a rule that no customer data goes into personal accounts.

Apps for Teams: The Small-Team Stack

A small team needs one app for each of seven jobs: chat, video calls, documents, a task board, a calendar, file storage and an AI assistant. What to decide for each, what to avoid, the rules that cut across all of them, and a worked example for a six-person team.

September 30, 20267 min read

A small team needs one app for each of seven jobs: chat, video calls, documents, a task board, a shared calendar, file storage and an AI assistant. Most teams already get four or five of those from one suite, Google Workspace or Microsoft 365, and add a board and an assistant on top. Which brand you pick for each job matters less than a few decisions that apply to all of them: one tool per job, accounts the company owns rather than personal ones, a named person who can let outsiders in and take them out again, multifactor sign-in everywhere, and a clear line on what an AI assistant may read and change. This is not a ranked list. It is the set of choices to make, job by job, and the mistakes that cost small teams the most.

Start from the suite you already have

If your team already has company email, it almost certainly has a suite, and the suite covers most of the stack. Map each job before you buy anything:

Seven jobs, and where each one usually comes from

Job              Google Workspace     Microsoft 365          Common standalone apps
Chat             Google Chat          Teams                  Slack, Discord
Video calls      Google Meet          Teams                  Zoom
Documents        Docs, Sheets         Word, Excel, Loop      Notion, Confluence
Task board       (none built in)      Planner                Trello, Asana, Jira, fenbs
Calendar         Google Calendar      Outlook                (use the suite's)
File storage     Drive, shared drives OneDrive, SharePoint   Dropbox, Box
AI assistant     Gemini               Copilot                Claude, ChatGPT

The standalone column is alphabetical within each row and not a recommendation. A standalone app earns its place when it does a job the suite does not do well enough for your team, or when your clients already use it. It does not earn its place because one person liked it at a previous job.

Job by job: what to decide and what to avoid

Chat

Decide how channels are organized (by client, by project or by function), who may create them, and who may invite people from outside the company. Outside access is the setting teams forget. Microsoft’s documentation on guest access in Teams (opens in a new tab) notes that a guest leaving a team does not remove the guest account from your directory; an admin has to remove it. Every chat tool has an equivalent, so put “remove outside guests” on your offboarding list for clients and contractors.

Avoid making decisions in direct messages, where nobody else can find them later. Reply times and what belongs in chat versus a task are covered in async communication.

Video calls

Use the one that comes with your calendar, so every invite has a link without anyone thinking about it. The real decisions are about recordings and AI notes: whether calls are recorded, where recordings and transcripts are saved, who can see them, and that everyone on the call is told. Check the consent rules that apply to you before recording calls with customers. What AI note-takers capture, and where it goes, is in AI meeting note-takers.

Documents

Pick one home for written material: procedures, decisions, client briefs, how-tos. Decide the top-level folders or pages on day one and keep them few. Avoid the most common failure, documents created in someone’s personal space and shared with a link, which vanish when that person leaves. Written procedures are where a small team saves the most time; SOP examples has eight to adapt.

A task board

This is the one job most suites leave thin, and the one that holds everything else together: the single place where the team’s work is listed, with a status everyone can see. Decide what counts as a task, what the columns are, and who may move something to done. Personal to-do apps, such as Google Tasks, are fine for each person’s own reminders; they are not where shared work should live. If you are unsure whether you need a board yet, kanban board vs to-do list lists the signs.

Calendar

Use the suite’s calendar and do not add a second one. Create one shared team calendar for time off, releases, client deadlines and holidays, and ask everyone to publish their working hours. Avoid putting team events only on one person’s calendar, where they disappear on the day that person is out.

File storage

Store team files in space the company owns, not in anyone’s personal drive. Google’s help page on shared drives (opens in a new tab) puts the reason plainly: “Shared drive files belong to the team instead of an individual,” and they stay when a member leaves. In Microsoft 365 the equivalent is SharePoint. Decide which folders clients may see, and share those folders, never the whole drive.

AI assistants

Decide which assistant the team uses, on which kind of account, and what may go into it. The account type matters because business and consumer plans handle data differently. Anthropic’s privacy center, for example, says that by default it does not use inputs or outputs from its commercial products (opens in a new tab), such as Claude for Work and the API, to train its models, and covers consumer plans on a separate page with their own settings. Read the equivalent page for whichever assistant you choose before anyone pastes in customer data.

Then decide what the assistant can reach. Connectors to your email, drive and board are where assistants become useful, and where a mistake travels furthest. AI agent governance for small teams covers the rules, and shadow AI agents covers what happens when you do not set any.

Rules that apply to every app

Company accounts only. Every app is signed into with a company email address, so access ends when employment does.
Multifactor sign-in on everything. CISA’s guidance on multifactor authentication (opens in a new tab) calls it “More than a Password” for a reason: a stolen password alone should not open your chat, files or email.
Two admins per app, never one. The second is the person who can act when the first is on vacation or has left.
One written list of every app, who administers it, and what it connects to. Five minutes a quarter keeps it current.
An offboarding checklist that names every app, including guest accounts for clients and contractors.
Integrations are decisions. Each one gives an app access to another; write down who approved it.

A worked example: a six-person agency

An invented design agency in Austin with six staff and a dozen client projects a year. It already had Google Workspace for email. This is the whole stack, with the one rule that makes each app work:

The stack, one line per job

Job           App                   Admins            The rule
Chat          Google Chat           Owner, ops lead   One space per client; no decisions in DMs
Video         Google Meet           (with Calendar)   Client calls recorded only with consent
Documents     Google Docs           Ops lead          SOPs in one folder; each has an owner
Task board    a shared board        Owner, ops lead   If it is not on the board, it is not planned
Calendar      Google Calendar       Ops lead          Team calendar for time off and deadlines
Files         Shared drives         Owner, ops lead   One shared drive per client; no My Drive
AI assistant  One business plan     Owner             No client data in personal AI accounts

Seven jobs, seven apps, two admins on each, and no job covered twice. When a designer asks for another tool, the question is which line it replaces.

What to avoid

Two apps for one job. Two chat tools or two boards means every message and task has two possible homes, and people check neither.
Choosing by feature list. Choose by the job, then by what your clients and your email already use.
Letting the tool set the process. Decide how work flows first, and configure the app to match.
Free personal tiers for company work. Files, history and admin controls leave with the person who signed up.
Notifications on by default everywhere. Agree which app may interrupt people, and mute the rest.

How a manager runs a small team across these tools, from overlap hours to one-on-ones, is in managing a remote team.

Where fenbs fits in the stack

fenbs fills the task board line and nothing else. A board has four lanes, To Do, Next Up, In Progress and Completed; every task is a feature, an enhancement or a bug with a priority from 1 to 10, and has a note for the problem and a plan for how it will be done. Roles are set per company, and Client and Reporter are suggested roles for people outside the core team, so a client can see and comment without rewriting the plan.

It is also where the AI assistant line connects. Claude, ChatGPT, Cursor, Copilot and other assistants join the board over MCP as members with a role, read the team’s rules on the Decisions and rules page first, and have their changes recorded in History under their own names. What fenbs does not do: it has no chat, no file storage, no calendar, no due dates, no assignee field you can set, and nobody sees a board without a role on it. Those stay with the rest of your stack.

Small business teams: fenbs for small business. Why a board with fewer features: a simple project management tool for small teams. Connecting apps with rules: workflow automation tools. What each person may do on a board: roles and permissions for humans and AI agents.