QuickBooks Online works fine for one business. The trouble starts when bookkeepers try to run portfolios of clients on it. Past 15 clients, the math stops working. Software costs scale linearly. Hours per week climb. Rule maintenance becomes a part-time job. This article sits inside our bookkeeping automation guide and answers one question: what are your real options when QBO stops scaling at the portfolio level?
QBO is single-tenant by design. Each client gets a separate file, a separate login, and a separate set of bank rules. Nothing transfers across files. Cross-client AI training memory doesn't exist. Batch operations across the portfolio? Per file only. A single dashboard for all your clients? You bounce between tabs.
This is a scale-mismatch, not a product-quality problem. QBO is built for one company. Bookkeepers run 15, 25, 40 clients. Different job, different tool. You have three paths: layer a portfolio workflow tool like Growthy on top of QBO, switch the GL itself to Xero or Puzzle, or stay on QBO and accept the ceiling. Below we cover five specific breakpoints, an honest "when QBO is still right" section, the 15-client time and money math, a comparison of the four serious GL alternatives in 2026, and a quick migration overview.
When does QuickBooks stop scaling for bookkeepers?
QBO scales fine up to about 15 clients. Past that, the math breaks. Each new client adds a $115/mo Plus subscription, roughly an hour per week of categorization work, and a fresh set of bank rules that don't transfer from your other clients. At 15 clients you're paying ~$1,725/mo in QBO subscriptions, spending 15+ hours per week on categorization, and rebuilding the same rules over and over. The five breakpoints: no portfolio-level AI memory across clients, no portfolio dashboard, no batch operations, bank rules that stay per-client, and per-client billing that compresses margin. You have three options: layer a portfolio tool like Growthy on top of QBO, switch the GL to Xero or Puzzle, or stay on QBO and cap your client count.
QBO was designed for the small business owner managing their own books. One company file, one chart of accounts, one set of bank rules. The product is excellent at that job. Intuit supports thousands of US financial institutions, pours billions into the platform each year, and just announced a 15-25% price hike on May 1, 2026 because demand is strong.
The problem isn't the product. It's the architecture. Single-tenant means each new client opens a separate file. There's no shared layer that learns across your portfolio. Every bank rule you build for client A stays trapped in client A's file. Every login is separate. Every dashboard is per-client. For one business owner doing their own books, this is fine. For a bookkeeper running 15 engagements, it's a tax on every hour of your week.
A portfolio is not 15 separate single-business engagements stacked on top of each other. It's a single book of business with shared patterns. Your 15 clients use overlapping vendors. Stripe, Gusto, Adobe, AWS, and Google Workspace probably appear in 10 of them. The same rule for "Adobe = Software Subscription" should apply across all 15. In QBO, you build it 15 times.
A portfolio also needs a single dashboard. You want to answer: which 3 clients haven't closed April yet? Which 2 have unreviewed transactions over $50? In QBO, you log into 15 separate files to find out.
The portfolio model needs portfolio-aware tooling. QBO doesn't ship that, because that's not what QBO was built to do.
Bookkeepers consistently hit a wall around 12-15 clients on a QBO plus manual workflow. The numbers tell why. 15 clients times roughly an hour per week of categorization equals 15 hours of coding work before reconciliations or close. Add 15 QBO Plus subscriptions at $115/mo and you're paying $1,725/mo in software cost before bookkeeper time. Margin compresses. Most solo bookkeepers stop growing right here, at the exact point where they should be scaling into a real practice. One concrete pattern: Sarah managed 22 clients on QBO and was capped. After moving to a portfolio-aware queue, she handled 30 without adding evening hours.
QBO's bank rules learn nothing from your other 14 clients. If you spend an hour teaching client A's file that "Stripe Transfer" maps to "Sales Income," that rule does not transfer to client B. You start over.
Growthy categorization works on patterns across your full portfolio. It learns vendor patterns, amount ranges, memo strings, and counterparty behavior across every client at once. A new client added to the portfolio lands at 85% first-import accuracy (90%+ on returning clients) because the model has already seen Stripe and Gusto and Adobe in 14 other files.
That difference compounds. Every new client on QBO is a fresh setup project. Every new client on a portfolio model lands closer to "ready to review" on day one.
QBO has no concept of "your book of business." You have 15 separate files, 15 separate logins (or one login that switches contexts), and 15 separate dashboards. Want to see which clients haven't closed for April? Open each file. Want to see total unreconciled transactions across the portfolio? Open each file. Want to see who has uncategorized transactions over $500? Same.
A portfolio dashboard answers those questions in one view. Close status by client, exception count by client, transactions awaiting review across all clients. That's a different product category, and it's the gap a layer like Growthy fills on top of QBO.
When QBO releases a new feature or you change a process, you propagate the change file by file. Lock April for all 15 clients? 15 separate operations. Update a vendor name? 15 times. Add a custom GL account? 15 times.
Batch ops at the portfolio level are how solo bookkeepers handle 15 clients without burning out. Lock the period for the whole portfolio in one click. Push a new vendor mapping across every client. Roll forward year-end balances at the portfolio level. QBO has none of that, because QBO doesn't see your portfolio. It sees 15 unrelated companies.
QBO bank rules work fine inside one file and don't transfer across files. The rule "Vendor contains 'GUSTO' then category 'Payroll Expenses'" works for the client you built it for. It does nothing for the other 14 clients on Gusto.
You can copy rules client by client. Bookkeepers do this. It's manual, slow, and breaks every time Gusto changes the bank descriptor. Then you rebuild 15 times. The structural problem isn't the rules engine. It's that QBO has no portfolio layer where shared patterns live.
QBO Plus is $115/mo per company file as of May 2026. At 15 clients, that's $1,725/mo in subscriptions before you add Hubdoc, payroll, or your practice management tool. At 25 clients, $2,875/mo. The marginal cost per client doesn't drop. Linear scaling.
Growthy uses a flat portfolio price instead: $149/mo billed annually or $199/mo billed monthly, covering the bookkeeper running the portfolio (not per client). The alpha cohort gets $99/mo with a 2-year lock-in (invite-only, capped under 20 users). Whether you run 15 clients or 25, the Growthy line stays flat. Your GL bill (QBO if you layer, Xero or Puzzle if you switch) still scales per client.
If you're at 5-10 clients with no plans to grow past 15, QBO economics still work. $575-$1,150/mo in software is fine when you're billing each client $300-500/mo. Don't migrate just because there's a newer tool. Migrate when QBO becomes the bottleneck on your growth, not before.
If your clients are stable, your processes are dialed in, and you have no roadmap to add 5+ clients in the next year, leave QBO alone. The migration cost (20-40 hours of setup time) won't pay back inside a year.
QBO has the broadest 3rd-party ecosystem in small business accounting. Thousands of supported banks, native Gusto integration, Square POS sync, Shopify, BigCommerce, Stripe, and dozens more direct integrations.
If your clients depend on a specific QBO integration that doesn't exist elsewhere yet, switching the GL costs more than it saves. A retail client running QBO POS sync. An e-commerce client with a custom QBO Shopify integration. A construction client using a job-costing add-on that only writes to QBO. In those cases, keep QBO as the GL of record and layer Growthy on top for the portfolio workflow.
If your client's CPA pulls tax data directly from QBO via UltraTax, Drake, ProConnect, or Lacerte, switching to a new GL adds friction at tax season. The CPA has to learn a new export format. Your client pays in either money or risk.
Some CPAs accept CSV exports from any GL. Others insist on direct QBO pull. Ask before you migrate. If the CPA insists on QBO, keep QBO as the GL and layer Growthy on top with bank rules vs AI categorization running side by side. You get the portfolio workflow without breaking the CPA's pull.
At 5 clients on QBO + manual workflow, expect ~5 hours per week on bookkeeping. Categorization takes the bulk; reconciliation and close are spread across the month. Margin healthy at standard $75-150/hr bookkeeper rates.
At 15 clients on QBO, the same workflow scales to roughly 15 hours per week on categorization alone. Add reconciliations, close work, and admin and the bookkeeping work fills most of a normal week. That's where Sarah was at 22 clients before she moved to a portfolio queue — after the move she handled 30 without adding evening hours.
At 25 clients on QBO without portfolio tooling, the math doesn't work. 25 hours per week on categorization plus another 15 on close fills a full week before you take a single sales call. That's the wall most solo bookkeepers hit.
5 clients on QBO Plus = $575/mo software. 15 clients = $1,725/mo. 25 clients = $2,875/mo. QBO ships native receipt capture (QBO Receipts) bundled with the subscription; Hubdoc bundles with Xero, not QBO. Dext or AutoEntry adds $20-30/mo per OCR seat for portfolios needing more capable OCR. Practice management on top: Karbon at $59/mo or TaxDome at $60/mo per user.
Total stack at 15 clients on QBO: roughly $1,800-1,900/mo in software. At 25 clients: roughly $2,950-3,050/mo. That's before bookkeeper time.
At 15 clients billing $400/mo each, gross revenue is $6,000/mo. Software at $1,800/mo eats 30% off the top. Bookkeeper time fills most of a workweek on categorization and close. Bookkeepers stop here because the next client adds $400/mo in revenue and a disproportionate amount of operational drag.
Growthy is not a GL replacement. It's a portfolio workflow layer that sits on top of QBO or Xero and gives multi-client bookkeepers what their GL doesn't: cross-client categorization memory, a portfolio dashboard, and one queue instead of 15 logins. Flat pricing at $149/mo annual or $199/mo monthly (alpha cohort: $99/mo invite-only, 2-year lock-in, under 20 users). 85% first-import accuracy, 90%+ on returning clients. Strong on the categorize and match layers (layers 2 and 3 of the 4-layer automation framework). Honest gap: native receipt OCR is on the roadmap, not shipped today. Hubdoc, Dext, or AutoEntry handle OCR upstream.
Best for: bookkeepers at 15-25 clients who want portfolio-aware tooling layered on top of an existing QBO or Xero GL.
Xero is the dominant non-QBO GL globally, especially outside the US. Strong product, clean API, broad bank coverage. Architecturally similar to QBO: single-tenant per file. Same portfolio limits. Different country footprint and a stronger position with international bookkeepers.
Pricing in the US starts around $20/mo and runs to $80/mo per company depending on the tier. Marginal cost per client still scales linearly. If you switch from QBO to Xero, you get a different product but the same single-tenant constraint.
Best for: bookkeepers serving international clients or those moving away from QBO for product preference rather than portfolio scale.
Puzzle is engineering-led, designed for venture-backed startups and founders who want a clean modern GL. Strong dashboards, good UX, accrual-aware. Less mature multi-client tooling. The product targets the founder buying directly more than the bookkeeper running portfolios.
If you serve venture-backed startups and your founders push you toward Puzzle, it works. For solo bookkeepers running varied small business portfolios (restaurants, retail, professional services), the fit is weaker.
FreshBooks started as invoicing for freelancers and grew into a light GL. Strong on invoicing, time tracking, and project profitability for service businesses. Weaker on accrual accounting, inventory, and complex GL work. Per-client pricing.
Best for: bookkeepers serving freelancers, agencies, and service businesses where invoicing is the dominant workflow. Not a fit for portfolios with significant accrual or inventory work.
Tool | Type | Portfolio support | Categorization accuracy | Pricing model | Best for |
|---|---|---|---|---|---|
QBO | GL | Single-tenant per client | None native (QBO Live add-on) | Per-client $115/mo | 1-15 clients |
Growthy | Workflow layer (on QBO or Xero) | Portfolio-aware | 85% first / 90%+ returning | Flat $149/mo annual ($99/mo alpha) | 15-25 clients on a portfolio queue |
Xero | GL | Single-tenant per client | Limited | Per-client $20-80/mo | International or non-QBO GL preference |
Puzzle | GL | Founder-direct | AI-assisted | Per-client | Venture-backed startups |
FreshBooks | GL | Single-tenant | Minimal | Per-client | Service businesses, invoicing-first |
Every new client adds a full subscription. 15 clients on QBO Plus = 15 subscriptions = $1,725/mo. The marginal cost per client never drops. You pay full sticker for client 1 and full sticker for client 15.
This pricing model assumes the buyer is the business owner, not the bookkeeper. It works fine for the small business owner buying QBO for their one company. It punishes the bookkeeper running 15 engagements.
Growthy is $149/mo billed annually or $199/mo billed monthly. The alpha cohort gets $99/mo with a 2-year lock-in (invite-only, under 20 users). Whether you cover 15 clients or 25, the Growthy line stays flat — it prices the bookkeeper, not the client count.
This pricing model assumes the buyer is the bookkeeper running a portfolio. The GL bill underneath (QBO, Xero, or Puzzle) still scales per client; Growthy doesn't replace that.
The honest comparison is GL spend versus GL-plus-workflow-layer spend. Below 5 clients, a bare QBO stack is cheaper because you don't need a portfolio layer yet. Around 10-15 clients, adding the Growthy line ($149-199/mo flat) earns back the hours saved on cross-client categorization and the missing portfolio dashboard.
At 15 clients: QBO subscriptions ~$1,725/mo regardless. Add Growthy at $149/mo annual and the layer cost is a rounding error against the time it returns. At 25 clients: QBO ~$2,875/mo, Growthy still $149/mo. The leverage compounds as the portfolio grows.
The default move is to layer Growthy on top of your existing QBO files. Keep QBO as the GL of record, keep your client-by-client integrations intact, and add the portfolio dashboard and cross-client categorization as a layer above. This is the right call when QBO integrations are sticky — Shopify, POS sync, payroll add-ons, or CPA pull via UltraTax / Drake / ProConnect / Lacerte.
Switching the GL itself (to Xero or Puzzle) only makes sense when QBO integrations aren't blocking you and a client genuinely needs a different GL — international footprint, founder preference for Puzzle, or a clean-sheet rebuild. Growthy still sits as the workflow layer on top of whichever GL you land on.
Most bookkeepers layer Growthy on top of QBO for the whole portfolio first, then evaluate per-client GL switches separately as integrations get unblocked.
Run a 30-day onboarding plan from QBO with parallel run and decision gates. Week 1: COA mapping and historical data sync. Week 2: parallel run on one client. Week 3: parallel run on 3-5 clients. Week 4: switch the day-to-day workflow into Growthy for clients where the parallel run matched; defer the rest.
The parallel run is the safety check. If Growthy's categorizations match what you'd code in QBO, you're ready to move that client's daily work into the Growthy queue while QBO keeps the books.
Keep your QBO files active throughout — Growthy layers on top of them. If a client's tax preparer needs a year-end QBO export, you pull it as normal. If you discover a categorization issue, you compare against the QBO baseline. Because the GL of record stays in QBO, rollback is just turning off the layer for that client.
The full bookkeeper automation stack with practice management, OCR, and reporting tools sits in the bookkeeper automation stack.
Yes, in most cases. Growthy exports a clean trial balance, GL detail, and journal entries in CSV format, and when you layer on top of QBO the CPA's direct QBO pull keeps working. Most CPAs accept CSV anyway. If your CPA insists on direct QBO pull (UltraTax, Drake, ProConnect, or Lacerte), the layered setup is built for exactly that case — keep QBO as the GL of record and use Growthy as the portfolio workflow layer.
Ask the CPA before you change anything. The answer changes by firm.
Yes. The recommended pattern is to layer Growthy onto one client first, run parallel for 30 days, then expand across the portfolio. Pick a client where you have full chart of accounts control, low transaction volume (under 200/month), and a flexible tax preparer.
After the first onboarding, you'll know the exact time cost (typically 4-8 hours per client for COA mapping and initial training). Plan accordingly for the rest.
Yes. Growthy imports your QBO chart of accounts, vendor list, customer list, and historical transactions via QBO API. Historical data trains the categorization model. The more history Growthy ingests, the higher first-import accuracy on subsequent clients.
Plan for 2-4 hours of import + review per client. Not zero-touch but not painful.
Bank rules don't transfer directly because Growthy uses pattern-based categorization rather than rule-based matching. Cross-client patterns replace most rules. The 5-10 high-confidence repeat vendors (Stripe, Gusto, recurring SaaS) where rules genuinely win can stay in QBO when you layer Growthy on top, or be replicated as confidence-bypass overrides inside Growthy. See the breakdown of bank rules vs AI categorization for when each approach wins.
Plan for 6-10 weeks for a clean 15-client layered onboarding. Week 1-2: setup and initial training. Week 3-4: parallel run on first 3 clients. Week 5-6: parallel run on next 6 clients. Week 7-8: parallel run on final 6 clients. Week 9-10: switch daily workflow into Growthy and clean up.
You can do it faster if you're full-time on it. Most bookkeepers spread it over 8-10 weeks while serving existing clients.
Growthy is in alpha. SOC 2 Type II is on the roadmap. Today, security posture includes encryption at rest, encryption in transit, role-based access controls, and audit logging. If your clients require SOC 2 Type II for data handling (common in regulated industries), keep QBO as the GL of record and defer the Growthy layer for those clients until SOC 2 lands.
Ask about current security posture and roadmap timing during your alpha onboarding. If the alternative is outsourcing the client to a service vendor, compare the control tradeoff in Bench vs Pilot vs AI bookkeeping before moving the relationship out of your workflow.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Related: Bookkeeping Automation for Multi-Client Bookkeepers, Multi-Client AI Bookkeeping, Migrate Manual to AI: 30-Day Plan, Bookkeeper Automation Stack
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View author profileGrowthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
You're good at this work. You know QuickBooks cold. You've developed a rhythm: open the client file, scan the transactions, start clicking through categories. Bank feeds, credit cards, merchant accounts. One by one.
You've seen the demos. A tool ingests your bank feed, transactions appear pre-categorized, and the vendor calls it automated bookkeeping. It looks like magic until you're cleaning up 200 miscategorized transactions at month-end while your clients...
Trace Stripe charges from gateway through bank deposit to recognized revenue. Clearing-account JEs, Stripe Billing RevRec vs GL-side recognition, and when to graduate to a dedicated tool.