SMB guides
Operating guides for companies without a platform team.
Written for businesses where the person evaluating this is also the person who will run it, and where an implementation that needs a dedicated engineer is not an implementation.
No platform team
Assumes the operator is the implementer
Existing tools
Built around what you already pay for
Bounded
One workflow, provable in weeks
Introduction
What changes when there is no platform team.
Most operating guidance assumes someone whose job is to implement it. In a smaller business that person is also running the thing the workflow supports, which changes what counts as a good design: fewer moving parts, failures that are obvious rather than subtle, and no step that requires remembering.
It also changes the sequencing. A large company can afford to map everything first; a smaller one needs the first workflow returning value before the second is designed, because attention is the binding constraint rather than budget.
- Written for
- Owner-operators
- Assumes
- No dedicated platform team
- First result
- Weeks, not quarters
- Cost
- Free, no signup
Why this exists
Enterprise operating advice does not scale down.
The standard guidance assumes roles that do not exist here: a data owner, a platform team, a change manager. Applied literally it produces a plan nobody has time to execute, and the usual outcome is that nothing happens.
The second mismatch is tolerance for partial failure. A large company can absorb a workflow that works eighty percent of the time behind a support function. A five-person business cannot, because the exceptions land on the same person the automation was supposed to free.
That makes exception design more important here, not less — which is the opposite of how smaller implementations usually get scoped.
You're likely here because
- You are evaluating and would also be implementing
- Previous automation created more exception handling than it removed
- Advice you have read assumes roles you do not have
How to choose
Where to start.
If
You want a rough value estimate first
Start with
An interactive assessmentIf
You know the workflow and need the decisions recorded
Start with
An implementation templateIf
You are choosing what to automate first
Start with
The workflow discovery templateIf
You know both systems already
Start with
A workflow blueprintHow it works
The sequence that works without a platform team.
Step 01
Pick the weekly cost
Choose the task you personally do every week that you resent. Frequency and irritation are better signals than theoretical value here.
Step 02
Keep it to two systems
A first workflow spanning three or more systems has more failure surface than a small team can supervise.
Step 03
Design the exception first
Decide what happens when it fails before deciding what happens when it works, because failures land on you.
Step 04
Run it manually once
Walk the workflow by hand to confirm the completion condition is real before automating anything.
Step 05
Measure your own hours
The metric that matters is time you got back, and it should be visible within weeks.
Guides
SMB operating guides — 10 in total.
Real estate
Lead speed, appointment conversion, transaction visibility, client communication, and repeatable follow-up all depend on keeping contact, property, calendar, and pipeline context together.
Open the guides →Legal services
Business-development, intake, scheduling, document collection, and matter-administration workflows can be streamlined without automating legal judgment.
Open the guides →Accounting firms
Client intake, recurring document collection, status communication, deadline tracking, and business development create repetitive administrative work around the accounting system of record.
Open the guides →Marketing agencies
Agencies need to connect prospecting, proposals, client onboarding, campaign delivery, reporting, and renewal signals without adding another fragmented point tool.
Open the guides →Healthcare practices
Administrative intake, referral handling, scheduling, business reporting, and non-clinical workflows can be improved while diagnosis, treatment, and clinical decision-making remain outside the automation scope.
Open the guides →Insurance
Prospect intake, appointment scheduling, renewal reminders, client communication, and internal operations benefit from connected workflows while underwriting and coverage decisions remain in controlled systems and human processes.
Open the guides →Consulting firms
Discovery, proposal creation, onboarding, recurring delivery, client reporting, and business development often depend on experts manually coordinating documents, spreadsheets, email, and calendars.
Open the guides →Contractors and home services
Lead capture, estimates, scheduling, job status, customer communication, and invoicing require fast handoffs between office and field teams.
Open the guides →Financial services
Prospect intake, relationship management, scheduling, document workflows, and operational reporting can be streamlined without turning automation into investment, tax, or financial advice.
Open the guides →Small-business operations
Small businesses often run core work across email, spreadsheets, calendars, accounting software, and lightweight SaaS tools. The opportunity is to connect those systems around repeatable workflows without a large IT project.
Open the guides →Scope
What these guides assume.
- They assume you are the operator, not that you have a team to delegate to.
- They do not cover multi-entity, multi-region, or complex compliance structures.
- They assume existing tools stay; nothing here starts with a migration.
- Sector-specific regulatory obligations take precedence over anything written here.
FAQ
Questions about this collection.
Is this different from the main guidance?
The principles are the same; the sequencing and the tolerance for failure are different. Smaller teams need exception design earlier because exceptions land on the person the automation was meant to free.
How small is too small?
If you do a task repeatedly and it has a defined completion condition, it is worth automating regardless of headcount. Volume matters less than repetition.
Do I need technical skills?
To describe the workflow, no. To decide which system owns which record, you need to know your own business rather than to write code.
What if I already tried automation and it failed?
Look for a missing exception path rather than a wrong tool. That is the usual cause, and it is why the sequence here puts exception design before the happy path.
How long before this pays off?
Weeks for the first workflow if it is genuinely bounded. If the answer is quarters, the scope is too large for a first project.
Is any of this gated?
No. Free, no signup, no customer requirement.
Keep exploring
Related paths.
Start with ARIA
Ask ARIA about smb guides.
You do not have to pick your way through this collection to get started. Describe the outcome you want and ARIA determines which capabilities, systems, and workflows the job needs.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Start with the task you do every week.
Describe the thing you resent doing manually. ARIA resolves whether it is bounded enough to be a good first workflow, which is the question that decides whether this works.