u/Cultural_Mall_6729

Had a realization this month that kind of changed how I think about our whole close process and wanted to share it.

We track time across all our clients and reconciliation consistently shows up as about 2 hours per client per month. That's pretty standard from what I hear. Everyone says recs take about 2 hours. It's one of those numbers that just gets accepted as normal.

But this month I asked my team to break their rec time down by subtask. Not just log 2 hours to reconciliation but actually track what they were doing during those 2 hours. The results were kind of surprising.

Actually matching transactions between the bank feed and QBO took about 25 minutes on average. That's the thing most people think of when they say reconciliation. It's the core task. And it wasn't even close to being the biggest time block.

Investigating and resolving exceptions took about 20 minutes. These are the transactions where something doesn't line up and you have to dig into it.

But here's the big one. Fixing miscategorized transactions so the reconciliation would even work correctly took 48 minutes on average. That's almost half the total reconciliation time. These are transactions that got auto categorized wrong by QBO's bank rules or that a client went in and changed to the wrong account or that landed in Uncategorized because nothing matched. Before you can reconcile anything you have to clean all of this up first.

The rest was downloading and organizing statements at about 12 minutes, creating adjusting entries at 15 minutes, and documenting the completed rec at about 10 minutes.

So what we call a reconciliation problem is actually almost 40% a categorization problem. The reconciliation itself isn't slow. The data going into it is messy. And messy data means you spend almost half your rec time on cleanup before you can even start the actual matching.

Once we saw this we started thinking about it completely differently. The fix for slow reconciliation isn't getting better at reconciling. It's getting the categorization right in the first place so that when you sit down to reconcile everything is already clean and you're just confirming matches instead of hunting down errors.

I don't know if this is obvious to everyone else or if it's just something we missed at our firm. But it was a genuine shift in how we approach the close and I'm curious if other firms see a similar breakdown when they actually track where their rec time goes

There's this weird pattern I keep seeing with QuickBooks Online firms.

They start out strong. First few clients come in, the work is manageable, revenue is growing. They hire one or two people. Things are humming. They push to 10 clients, then 12, then 15.
And then everything just... stalls.

Not because they stopped getting referrals. Not because their work got worse. But because somewhere around that 15 client mark, the wheels start coming off internally and most owners don't even realize it's happening until they're already in it.

Here's what that actually looks like in practice:

Your team is good. But every month end, they're operating on memory. Who handles which client, which accounts need reconciling first, which client always sends their statements late, it all lives in people's heads. That works fine at 8 clients. At 15 it starts cracking.

You take on client 16 and suddenly close week is a disaster. Deadlines get missed. A reconciliation gets done wrong because someone rushed it. A journal entry gets skipped because it fell through the cracks between two people who both thought the other one had it.

So you think about hiring. But your margins are already tighter than you'd like. And the last person you hired took 6 weeks to onboard and still needs hand holding on anything complex.
So you stay at 15. Maybe 16 on a good month. And you tell yourself you'll figure out the growth piece later.

The ceiling isn't about capacity though. It's about infrastructure.
Firms that break past 15 and get to 30, 40, 50 clients with the same core team, aren't doing it by working harder. They've just built the scaffolding that lets work move without everything depending on one person's memory or one team member always being available.

Clear handoffs. Documented close processes per client. Checklists that actually reflect how your firm works, not a generic template from 2019. Reconciliation that doesn't require a senior to babysit it every step of the way.

That's what 30 client firms have that 15 client firms don't. Not more people. Just better scaffolding.

If you're running a QBO firm, where did things start feeling unmanageable for you? Was there a specific client number where it shifted?

this was about 18 months ago, we were building a SaaS product for logistics companies, small team, 4 engineers, tight runway and a co-founder who was convinced that moving fast was more important than moving carefully. we had a launch date, investors were watching and slowing down for proper testing felt like the wrong call at the time.

we shipped. the product worked in demos. it fell apart in production almost immediately.

the first bug was a data sync issue that was corrupting records for about 12% of users, we did not catch it for 11 days. by then 3 enterprise clients had already flagged it and one of them had made decisions based on the corrupted data. the second issue was a billing error that was charging some accounts twice on renewal, that one ran for 19 days before someone on the team noticed.

total refunds issued in the first 6 weeks were $34,000. two enterprise clients left and did not come back. one of them had been worth $1,400 a month. the cost of the QA process we skipped would have been around $8,000 in engineering time.

the part that still bothers me is that both bugs were completely detectable with basic testing, they were not edge cases or rare scenarios, they were things that would have shown up on day one of any structured QA process. we just chose not to have one because we were in a hurry.

has anyone else been through something like this and actually changed how they approach testing after, genuinely curious what actually stuck and what was just good intentions that faded after the next deadline pressure hit

I have been in this field long enough to know that most people outside of QA think we're all the same

There's the QA who actually thinks, who sits with a feature before touching a test case and asks "okay but what could actually go wrong here." who finds the bug nobody filed because nobody thought to look there, who understands the product deeply enough to know when something feels off even if it technically passes, who advocates for the user even when the user isn't in the room.

Then there's the QA who opens the test case, follows the steps, runs on the pipeline, files tickets on failures, no judgment, that's just what the job is for them.

The first type didn't disappear because they were bad at their job, they disappeared because the industry made it impossible to do that job.

You can't think critically when you're testing three projects simultaneously, you can't find the interesting bugs when you have 20 tickets already open and a release in two hours, you can't be curious when your manager's only metric is how many test cases got executed this sprint. you go through the motions and you become the second type not because you wanted to but because the first type wasn't sustainable.

and then there's automation. which should have been the thing that freed us up to think more instead it became its own full time job that nobody properly owns.
Devs push code and don't touch the tests, pipelines. QA spends the entire day debugging test scripts instead of actually testing anything.
The automation that was supposed to create space just created more noise.

and the outsourcing. I'll keep it short because just NO, you get what you pay for  and what you pay for when you offshore your QA to the cheapest vendor you can find is a team that doesn't know your product, doesn't know your users, and is working off a test plan written by someone who left the company a year ago. Good luck with that.

The part that genuinely depresses me is that good QA is rare and valuable and most companies won't know what they had until it's gone, the person who was quietly thinking through edge cases and catching things before they became incidents,  that person just accepted an offer somewhere else or got laid off in a restructure or just quietly stopped trying because nobody noticed when they did.

and now you have a pipeline and a ticket count and a dashboard that says coverage is at 94% and somehow everything still breaks.

quality isn't a metric, it's a mindset, and you can't automate your way into it.

when I started this agency I genuinely thought working hard and being consistent was enough, first client was a web development company, guy was super money driven and wanted a constant flow of qualified leads every single week, we gave everything we had, manually going through LinkedIn posts, scraping profiles, building lists and after weeks of work we could barely pull five or six decent prospects for him, they were good prospects but nowhere near what he needed to run a proper sales motion so he let us go and honestly it crushed us because we had put everything into that client

instead of taking a break we went straight into finding another one, landed a UI UX design company and told ourselves we were just going to work harder, more hours, more manual scraping, going through LinkedIn post by post looking for anyone who showed even a slight signal of interest, we pushed ourselves to the limit and still could not get past eight or nine halfway decent leads a week, the rest of what we were handing over was just noise, random people with no real intent and the client could tell because conversions were terrible, after a month and a half he was done with us too and we were sitting there exhausted with two failed clients and seriously questioning whether we even knew what we were doing

around that time I was just sitting with everything that had gone wrong and trying to figure out what the actual problem was because clearly working harder was not the answer, I started going back through all the leads we had delivered to both clients and looking at which ones had actually converted into real conversations and which ones had just been ignored and a pattern started showing up that I had completely missed before

almost every lead that had converted into a real conversation had some prior touchpoint with the client's content, they had liked a post, left a comment, engaged in some way before we ever reached out to them, and the ones that went nowhere were people we had just cold scraped based on job title and company size with zero signal behind them, it sounds obvious in hindsight but when you are in the middle of grinding through manual work every day you do not stop to actually look at what is working and why

so I started building our entire process around that one insight, instead of scraping cold profiles we shifted to tracking who was actually engaging with our clients LinkedIn content and then filtering those people by whether they matched the ICP, it was still manual at first and honestly painful to do consistently across multiple clients but even in that early messy version the difference in lead quality was immediately obvious

the first month after we made that shift our lead to conversation rate jumped from around 4 to 5 percent to somewhere closer to 19 percent, we retained both clients we were working with which had genuinely never happened before and one of them referred us to another company the following month, eventually we found a tool that automated the tracking and filtering side of it which is when we could finally scale it properly without burning out but the real change was just figuring out that signal quality matters infinitely more than volume

within three months we had rebuilt our reputation, got new clients through referrals from people who saw the quality of what we were delivering and started scaling properly for the first time, we went from losing clients and barely covering our own costs to consistently doing $15k a month in agency revenue and still growing, the work did not get easier but it finally started making sense because we were not wasting hours on leads that were never going to convert

the problem was never how hard we were working, it was that we were chasing people who never showed any interest in the first place, fix the signal and everything else falls into place

i'd written about QA finding a bug before release and the team's reaction being "why didn't we catch this sooner" instead of thank you. the point i was making was about culture and how finding bugs gets treated as failure.

the reply pushed back on something more fundamental. i was using "QA" and "testing" interchangeably and treating QA as a role that a specific team performs. the commenter's point was that this framing is itself the problem. QA is a process that belongs to the whole organization, not a function that gets handed off to a specific group of people at the end of a sprint.

and the "QA holds a release" thing i said  they called it an oxymoron and they're right. if quality is genuinely built into the process from the start, no single team is in a position to hold or release anything. the gate shouldn't exist because the work shouldn't need a gate.

as long as testers see themselves as responsible for quality and as long as the org treats them that way, you get the exact dysfunction i was describing. the tester becomes the last line of defense, everything flows to them under pressure, they find something, and now they're the problem instead of the solution.

the uncomfortable version of "why didn't we catch this sooner" isn't about the testing team at all,  it's about why the process allowed something to get that far in the first place. that's a process question and the answer lives upstream of whoever is doing the testing.

i've been trying to shift how i think about this in practice. we've moved to running automated checks continuously throughout the build cycle rather than treating testing as a phase at the end. using a tool for the flow coverage so it's not dependent on one person's attention at crunch time. it's helped but honestly the harder change is cultural and it moves slowly.

has anyone has actually managed to shift an org from "QA team = quality owners" to something more distributed. 

Can't afford ads. So I get creative.

Every week I read my competitors' changelogs and release notes. All of them. Takes maybe 30 minutes.

Why? When they announce breaking changes or deprecate features their users complain. Twitter, Reddit, support forums. People get mad publicly.

That's when I show up.

Not salesy. Just helpful. "Hey we still support that feature if you're looking for alternatives." One comment, that's it.

Last month a competitor deprecated an API that a lot of their users relied on. People were pissed. I posted in one thread saying we still support it and migration takes 10 minutes.

11 signups that week. From one comment.

But I screwed this up once. Someone asked "does your tool work on Samsung tablets?" I said yes confidently. It didn't. They tried it, found the bug, and posted about how I lied.

That was worse than saying nothing. Damaged trust publicly.

Now I verify every claim on actual devices before commenting anywhere. Run things through this to make sure I'm not about to promise something that's broken.

Your marketing is only as good as your product's reliability. One lie and you're the villain in someone else's thread.