Map the operating loop first
Start with how a person finds the business, contacts it, books or becomes a lead, receives follow-up, gets documents and becomes a customer. The stack should support this loop.
A practical guide for small businesses choosing core software: domain, email, calendar, website, CRM, scheduling, forms, documents, tasks, password manager and automation.
Disclosure routeCommercial disclosureHelp small businesses choose tools in the order that supports real customer work instead of buying a scattered stack.
Start with how a person finds the business, contacts it, books or becomes a lead, receives follow-up, gets documents and becomes a customer. The stack should support this loop.
Domain, business email, calendar, documents and account recovery are the foundation. Google Workspace or Microsoft 365 often matters before specialized tools.
A CRM is useful when leads, deals or customer conversations are being missed. Before that, a simple sheet or inbox process may be enough.
Scheduling tools help when meetings are frequent. Form tools help when intake needs structure. Do not buy them because a generic stack diagram includes them.
Choose one place for tasks and one place for documents. Add password manager and two-factor authentication before adding automation.
Automate repeated, stable workflows only after the manual process is understood. Automation should reduce friction, not hide confusion.
| User type | Best path | Why |
|---|---|---|
| Solo consultant | Domain, email, calendar, simple website, password manager | Credibility and communication matter first. |
| Lead-driven service business | CRM plus scheduling or forms | Follow-up and intake become operational bottlenecks. |
| Small team | Shared docs, task system and access policy | Coordination and ownership become important. |
| Growing workflow | Automation after manual process is stable | Automating unclear work creates hidden failures. |
| Security-conscious business | Password manager and two-factor authentication early | Account control protects the whole stack. |
Related decision page.
Related decision page.
Related decision page.
Related decision page.
Related decision page.
Related decision page.