The Minimum Viable Operations Stack for a 20-Person Company

A team that has its operations infrastructure configured properly spends less time on coordination overhead and more time on the work that grows the business. The six categories below cover the tools that make the biggest difference: identity, finance, communications, documentation, IT ticketing, and security. The right time to configure them is before you need them. If your team has already grown past out-of-the-box settings, it is not too late to build the foundation the right way.

Cross-referenced against vendor documentation for Google Workspace, Microsoft 365, QuickBooks Online, Xero, Ramp, Brex, Slack, Microsoft Teams, Google Meet, Zoom, Notion, Confluence, Jira Service Management, Freshdesk, 1Password, Bitwarden, Jamf, Kandji, and Microsoft Intune on 2026-07-03.

1. Identity: Google Workspace or Microsoft 365

The identity layer is what everything else connects to. When a new hire joins, you add them here; when they leave, removing them from the directory deactivates access across every integrated app in one action. That single point of control is what makes a growing team auditable and offboarding fast.

Google Workspace is the right choice for teams living in Docs, Sheets, and Gmail. Microsoft 365 is the right choice for teams with Windows devices and Office dependencies. Whichever you choose, configure SSO for each SaaS application as you add it rather than after the fact. A tool that authenticates through the directory can be deprovisioned instantly; one with a standalone login becomes a manual step in every offboarding.

2. Finance: Accounting Software and Expense Management

Two finance tools earn their place at this size: an accounting platform for the books and payroll coordination, and an expense management tool for corporate cards and reimbursements. Running both from a single spreadsheet works until it does not, and it stops working right when the business is too busy to clean it up.

QuickBooks Online and Xero are the two most widely supported accounting platforms for SMBs. Both integrate with payroll processors, banks, and document storage. For expense management, Ramp and Brex offer corporate cards with per-user spending controls, receipt capture, and direct sync to the major accounting platforms. The specific tool matters less than having both layers in place: one for the books, one for the cards.

3. Communications: Internal Messaging and Video

The communications stack at this size needs two layers: a persistent messaging channel for daily coordination and a video platform for structured meetings. Adding more before these two are well-configured creates noise without adding capacity.

Slack is the standard for channel-based team messaging. Microsoft Teams is the natural fit for Microsoft 365 teams. For video, Google Meet is included in Google Workspace; Zoom is the standard for mixed-platform teams and external calls. Pick one video platform, standardize your meeting links, and set a recording and storage policy before the team starts hosting client calls.

4. Documentation: A Shared Knowledge Base

The documentation layer is where institutional knowledge lives: how processes work, what decisions were made and why, who owns what, and the standard procedures that keep operations consistent as team members change roles. Without it, every new hire ramps up by asking the same questions the previous person asked.

Notion handles everything from wikis to lightweight project tracking and works well for teams that want flexibility. Confluence is the right choice for teams already running Jira. Google Sites is a workable option for teams that want to stay entirely within Google Workspace. Set up the top-level structure before content accumulates; reorganizing a flat wiki after the fact takes significantly longer than building the skeleton first.

5. Ticketing: An IT Help Desk

When someone on the team loses access to a tool, has a hardware issue, or needs a software account created, that request needs a clear place to land. Without a help desk, it goes to whoever is most accessible that day. A ticketing system converts ad-hoc requests into a visible queue with ownership and resolution tracking.

Jira Service Management has the most configurable request-type system and integrates directly with Jira for teams doing product development alongside IT operations. Freshdesk is more accessible for teams without a dedicated technical IT function and handles both internal requests and customer-facing support from the same interface. JSM's free tier covers the request types most SMBs use (access requests, hardware issues, software procurement) without significant configuration overhead.

6. Security: Password Management and Endpoint Protection

Security at this size reduces to two tools that cover the highest-return surface area: a password manager and an endpoint management platform. Together they close the two most common vulnerability categories in growing teams: weak credential practices and unmanaged devices.

1Password and Bitwarden both offer team plans with directory sync and shared vault controls. 1Password has deeper integration with the most common identity providers; Bitwarden is the cost-competitive choice for teams keeping the SaaS bill lean. For device management, Jamf and Kandji both handle Mac fleets with out-of-the-box policies for encryption, screen lock enforcement, and remote wipe. Microsoft Intune, included in Microsoft 365 Business Premium, covers Windows devices well. Enroll every company-owned device at setup, not after a security incident makes it urgent.

Ready to Configure Your Stack?

ScaleIt helps startups and SMBs build the operations infrastructure so the team can focus on growth. Book a free call to walk through your current setup and identify the gaps worth closing first.