TL;DR. Spend 30 minutes scoring ten honest questions about your stack — tool count, data accessibility, manual handoffs, reporting, onboarding, vendor reviews, integrations, people-vs-systems problems, customer onboarding, key-person risk. Each scores 1–5. Total 10–25 means healthy. 25–35 means friction. 35–50 means broken. Your score points you to the three highest-ROI fixes for this quarter. Start with the STOA tools directory when you've found your gaps.
When SMB owners ask us "is our stack working?" — they usually know the answer is no. What they don't know is which part hurts most, what to fix first, and how much it's costing. The usual result: add another tool to a stack that's already too big.
This is the diagnostic that runs before any of that. Ten questions. Thirty minutes. A notepad. At the end you'll have a one-page tech health score and the three highest-ROI fixes for your situation.
What this audit actually does
The output is a number from 10 to 50 and a three-item priority list. The number tells you whether your stack is healthy, frictional, or broken. The list tells you where to spend the next quarter of operational attention.
Every question can be answered in under three minutes — no reports, no IT, no meetings. A 47-page Gartner-style framework is great if you have a CIO. You don't.
A second purpose: surfacing the gap between "we're fine" and the data. According to the Productiv 2026 SaaS Management Index, the average company runs 130+ SaaS applications and wastes about 44% of license spend on tools nobody uses. Most owners score themselves about 30% better than the audit ends up scoring them. That gap is the value.
The 10-question framework
Each question scores 1–5. Read it, write down a number, move on. Don't deliberate — your first honest answer is almost always right. If you genuinely can't answer, score it 5; uncertainty is itself a failure mode.
Q1. How many software tools do you actively pay for?
Volume is the first signal. Over 25 SaaS subs almost certainly means duplicates, ghost subs, and tools nobody opens. The Salesforce 6th SMB Trends Report shows the average small business runs about seven core apps — but that count misses long-tail subscriptions on individual credit cards.
Score. 1: Under 10, tracked centrally. 2: 10–15. 3: 15–25. 4: 25–40. 5: 40+ or unknown.
Q2. Can you generate a current customer list in under 2 minutes from one place?
If your customer list lives in CRM, accounting, inbox, and project tracker — and only the union of all four is "complete" — you don't have a list, you have four partial ones. The Salesforce report shows 44% of SMBs hit data inconsistencies across systems; the customer record is usually where it bites first.
Score. 1: One source, under 2 minutes. 2: One source plus light reconciliation. 3: Pull from two and merge. 4: Pull from 3+. 5: No clean way to produce it.
Q3. When a deal closes, how many systems get manually updated?
Closed deals trigger kickoff, contracts, invoicing, project setup, onboarding. If a human re-keys the same info into more than two systems, you're paying labor as integration tax and seeding records that will drift apart.
Score. 1: One system; rest syncs. 2: Two manually. 3: Three. 4: Four to five. 5: More than five.
Q4. Can you see your current month's profit without exporting and reformatting?
The owner's job is to make decisions on numbers. If those numbers require a 20-minute spreadsheet rebuild every Monday, you'll skip the review or decide on stale data. The $600,000 problem usually traces back here.
Score. 1: Live dashboard, trusted, under a minute. 2: One report, under five minutes. 3: Export and reformat. 4: Multi-tool merge in Excel. 5: Month-end from your bookkeeper.
Q5. How long does it take a new hire to access all the tools they need?
Tool provisioning is a tax on every hire. Onboarding research shows technology roles average 12+ tools to provision per hire; SMBs that automate it cut HR admin time from 22+ hours to under 10.
Score. 1: Documented checklist, under a day. 2: Mostly documented, 2–3 days. 3: Ad-hoc, a week. 4: New hires complain by week two. 5: Never written down.
Q6. Have you done a vendor renewal review in the last 12 months?
Auto-renewal is how SaaS spend doubles silently. With 44% of license spend wasted per Productiv, the highest-ROI hour you can spend this quarter is probably reviewing your last 12 vendor invoices.
Score. 1: Reviewed last quarter; cancellations made. 2: Reviewed in last 12 months. 3: Reviewed once. 4: Never; renewals just happen. 5: No clear vendor owner.
Q7. Do your customer-facing tools talk to your back-office tools?
Customer-facing tools (website, scheduler, CRM, support inbox) generate data; back-office tools (accounting, payroll, project management) consume it. If they aren't connected, somebody on your team is the connector. That's not a person, that's an integration platform you haven't bought yet.
Score. 1: Native or iPaaS everywhere. 2: Zapier/Make/n8n with one or two manual handoffs. 3: Half connected. 4: Mostly manual. 5: No integrations.
Q8. How many "people problems" are actually systems problems in disguise?
When a project misses a deadline, the conversation starts with "who dropped the ball?" It rarely ends with "the handoff between Tool A and Tool B fails 30% of the time." Most repeat people problems are systems problems wearing a person's name.
Score. 1: Catch systems issues fast; rarely blame people. 2: Sometimes blur the two. 3: Default to "training problem" first. 4: Most issues framed as accountability. 5: Fired people for what was a broken handoff.
Q9. Can you onboard a customer from signup to kickoff without manual data re-entry?
Customer onboarding is the highest-stakes workflow in most SMBs — contracts, billing, kickoff all in week one. If the same details get re-typed into four systems, you're guaranteed a typo, a missed step, or data drift before the second invoice.
Score. 1: One form drives onboarding; rest automatic. 2: Two manual steps. 3: 3–4 manual steps. 4: Mostly manual with a checklist. 5: Every onboarding is a one-off.
Q10. What happens to your business if your most-tenured employee leaves tomorrow?
Key-person risk doesn't show up on a dashboard. If your most experienced person carries the only working knowledge of a critical workflow — pricing logic, customer history, vendor passwords, quarterly close — your stack isn't a system. It's a person with software around them.
Score. 1: Documented, redundant; we'd cover it. 2: Mostly documented; some gaps. 3: A few workflows in their head. 4: Several critical workflows are them. 5: The business stalls for a month.
How to score it
Add up your ten answers. The total falls between 10 and 50.
10–25 — Healthy. Your stack is working. 1–2 small optimizations available, no urgent fires. Spend attention on growth-side bets: which workflow AI could accelerate, which integration saves 2 hours a week, which tool review you keep postponing.
25–35 — Friction. Where most $1M–$5M SMBs land. The stack works but costs 5–15 hours a week in manual handoffs, duplicate entry, and reporting friction. Nothing is on fire — but you pay for the absence of automation every week. Cumulative cost over 12 months: $40,000–$120,000 in labor and lost decisions. The fix is targeted integration and documentation, not replatforming.
35–50 — Broken. The stack is actively a constraint. Hires take too long to ramp. Customers feel the cracks. The owner is in every decision because nobody else has the data. Per McKinsey/Oxford research on large IT projects, 66% of enterprise software projects run over budget — the SMB version is replatforming when you should have integrated. Do not buy new software yet.
The 3 highest-ROI fixes by score band
Pick from the band you scored. Ordered by what we see deliver the fastest payback.
If you scored 10–25 (Healthy):
- Automate one customer-facing workflow — lead intake, customer onboarding, support routing. Build once, save 1–2 hours a week.
- Run a vendor renewal sweep. Even healthy stacks hide a zombie subscription. Recover spend, redirect to a new capability.
- Pilot one AI workflow — meeting notes, document review, support triage. Healthy stacks earn the right to experiment.
If you scored 25–35 (Friction):
- Map your integration boundary (framework here). What flows in, out, and what's manual. Mapping usually reveals 2–3 quick wins worth 5+ hours a week.
- Connect the two highest-volume tools — almost always CRM and accounting. Native, or via Zapier/Make/n8n. Usually $20–$80/month, saves half a day a week.
- Document the top three workflows in plain text with the tools listed: onboarding, monthly close, highest-volume internal handoff. Cuts ramp time and surfaces who owns each step.
If you scored 35–50 (Broken):
- Stop buying. Don't add another tool. Don't replatform yet. Most "we need to replace it" instincts at this score are integration and configuration problems — see the signs of true outgrowth.
- Pick the workflow most visible to customers — onboarding, invoicing, support response. Fix it from start to finish before touching anything else. One working workflow shows the team what's possible.
- Get an outside read. Self-audits at this score under-rate the breakage because the owner is inside it. A 30-minute outside conversation is the cheapest way to confirm the diagnosis.
What to do with the result
Write your score down. Note the date. Pick exactly one item from the priority list and put it on next week's calendar with a real owner and a real deadline.
Owners who get value from this audit don't do all three fixes at once. They finish the first, watch the result, then continue down the list or re-run the audit to see how the score moved. A 5-point improvement quarter over quarter is a working operational rhythm.
If you want the deeper version — same framework with full visibility into your tools, data flows, and team usage — that's our free 30-minute Stack Audit. No deck, no pitch. About 40% of those calls end with us telling the owner to do nothing, save the money, and revisit in six months. The other 60% end with a clear scope.
If you'd rather browse options yourself, the STOA tools directory groups SMB-tested software by problem. The AI Advisor takes a problem statement and returns three candidates with reasoning.
Frequently asked questions
How long does a tech stack audit take?
The self-audit takes 30 minutes. A professional audit typically takes a 30-minute discovery call plus 2–4 hours of analysis. STOA's Stack Audit fits in a single 30-minute call because we work from answers an owner can give us in real time.
What's a good tech health score for an SMB?
10–25 is healthy — most owners aren't there, and that's normal. 25–35 is the most common range for $1M–$5M businesses; not a crisis, but a real cost. 35+ means the stack is actively limiting growth and should be triaged before adding any new software.
Should I do my own tech audit or hire a consultant?
Do the self-audit first, every time. At 10–25 you don't need a consultant — you need a focused project plan. At 25–35, an outside audit usually pays back in the first integration fix. At 35–50, an outside read is genuinely useful because internal teams under-rate the breakage they're inside.
What do I do after a tech audit?
Pick one fix and finish it before starting the next. Most stacks get worse from too many simultaneous improvement projects, not too few. The rhythm: audit, pick one fix, ship in 30–60 days, re-audit, repeat.
About the author. Alejandro Morales is a senior operations consultant and systems architect at STOA Digital Solutions. STOA helps SMB owners ($500K–$20M revenue) choose the right software, connect it, automate routine work, and build operations that don't depend on the owner being in every meeting. Based in the Triangle, NC; serving the US.
Sources.
- Productiv — 2026 SaaS Management Index (130+ apps average; ~44% wasted license spend). https://productiv.com/saas-management-index/?utmsource=stoa-agency&utmmedium=referral&utm_campaign=technology-self-audit
- Salesforce — Small & Medium Business Trends Report, 6th Edition (53% say too many tools complicate workflows; 44% report data inconsistencies; integrated stacks correlate with growth). https://www.salesforce.com/resources/research-reports/smb-trends/?utmsource=stoa-agency&utmmedium=referral&utm_campaign=technology-self-audit
- McKinsey & Company with the BT Centre for Major Programme Management at the University of Oxford — Delivering large-scale IT projects on time, on budget, and on value (66% of enterprise software projects have cost overruns; 5,400+ projects studied). https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/delivering-large-scale-it-projects-on-time-on-budget-and-on-value?utmsource=stoa-agency&utmmedium=referral&utm_campaign=technology-self-audit
- STOA Digital Solutions — observations from Stack Audit engagements with $1M–$5M SMBs, 2024–2026.