u/dhana231_231

I ran the numbers on our last 3 month end closes. Tracked every single task by category across all our clients. I wasn't trying to prove anything I was just curious where the time was actually going.

Here's what came back.

Actual accounting work like reconciliation, journal entries, accruals, and trial balance review took up about 38% of our total close time. That's the stuff we trained for. That's the stuff we're actually good at.

Everything else took up 62%. And by everything else I mean writing close memos from scratch because nobody saved a template from last month. Emailing clients three times to get a single receipt. Explaining to a SaaS founder what SG&A means and why it went up 18% when he's the one who hired two people last quarter. Reformatting reports into whatever format the client's board wants this month. Updating the Google Sheet that tracks the close itself which is somehow its own 30 minute task every month.

This is what bugs me. Every time someone on here posts about speeding up their close the answers are always the same. Hire another senior. Get better at reconciliation. Work faster. But nobody ever talks about the fact that more than half the time isn't spent on the ledger at all. It's spent on communication and writing and admin work that just happens to live next to the accounting.

We have good people. They're not slow at accounting. They're slow at all the stuff surrounding the accounting that nobody talks about because it doesn't feel like real work even though it takes up most of the day.

I genuinely think most firms could cut their close time significantly without touching their actual accounting process at all. Just by fixing the writing and communication layer around it. But I rarely see that conversation happening

I track this informally. I've been on this team for 2 years. In that time, 9 engineers have been in the on-call rotation. All 9 of them either transferred to a different team or left the company within 6 months of starting on-call. I'm number 10.

The rotation is one week on, three weeks off. That sounds reasonable until you learn that "on" means you carry a pager that goes off on average 14 times per week. Not 14 alerts. 14 pages that require human intervention. At any hour.

Most of them are the same 5 issues. A memory leak in a service that was "fixed" three times but keeps coming back because the root cause is an architectural decision nobody wants to revisit. A third-party API that rate-limits us at 2 AM because our batch job isn't using exponential backoff. A queue that fills up when traffic spikes, because the consumer was configured for a traffic level we outgrew 18 months ago.

Management knows about all five. They've been in the backlog for over a year. They keep getting deprioritized because they're "operational" and not "customer-facing." Every sprint planning, the PM asks "what's the customer impact?" and the answer is "none, unless the on-call engineer doesn't fix it in 15 minutes." So the fix never gets prioritized. The 15-minute human response window is the permanent solution.

I raised this in a retro. My manager said "I hear you" and opened a Jira ticket. The ticket is tagged "P3 - investigate." It's been open for 7 months.

I'm updating my resume. That will make it 10 for 10.

running content for multiple B2B clients at the same time means you get very focused on output, posts going out on schedule, engagement numbers going up, follower counts growing, monthly reports looking good, it is easy to get into a rhythm where the metrics feel like the job

about eight months into last year one of my clients asked me a question I did not have a good answer for, he wanted to know which of the people engaging with his content were actually potential buyers versus just people who found the posts interesting, I had never thought to separate those two groups because I had been treating all engagement the same way

so I actually went through the engagement data properly for the first time, looked at who was liking and commenting on his posts, checked their profiles, their job titles, their companies, and what I found made me feel like I had been doing the job wrong for months, there were genuine ICP fits buried in every high performing post, founders and directors and heads of sales at exactly the right kind of companies, people who had been showing up consistently for weeks that we had never followed up with because we had no system to identify or act on them

I did this audit across all six clients and found roughly the same pattern everywhere, warm interested people hiding inside engagement data that everyone was treating as a vanity metric

we shifted the entire approach for every client, less focus on follower growth and reach numbers, more focus on who specifically was engaging and whether they matched the ICP, outreach went out fast to the people who did and the quality of conversations those clients were having changed noticeably within about six weeks

the number that still sticks with me is that across all six clients we identified over 200 ICP matched engagements in a single month that had previously just been ignored, that is 200 warm conversations that never happened because nobody was looking at the right data

if you are running content for B2B clients and not doing this breakdown for them you are leaving a significant part of the value of what you do completely on the table

I want to be careful here because i am not saying quality goes away. quality matters more than ever. i am saying the organizational model of a separate team responsible for finding bugs after developers write code is fundamentally broken and the industry is slowly figuring that out.

the best engineering teams I have worked with or studied do not have a traditional QA handoff. quality is embedded. developers write tests as part of the work. the pipeline catches regressions automatically. the definition of done includes quality criteria from the start.

the reason dedicated QA teams exist in most companies is because historically it was hard to shift that responsibility earlier and automate it reliably. those barriers are eroding. when you can write a test in plain english and run it on real devices in a CI pipeline without a specialist maintaining it, the case for a separate quality gate staffed by humans gets weaker.

I think the QA role is going to bifurcate. some people will move into quality engineering embedded in product teams. others will specialize in security testing, accessibility, performance, the things that genuinely need deep expertise. the middle, the people doing manual regression and maintaining automation scripts, that middle is going to shrink considerably.

nobody in the industry wants to say this out loud because it is uncomfortable. but the trajectory seems pretty clear.

I run an online store selling handmade leather goods. Started on Etsy, moved to Shopify in 2022, grown it to a point where it is my primary income. I have a bookkeeper who handles the monthly work and an accountant who does the year end filing. I thought I had the financial side covered properly

Last month I was doing a deeper review of my expenses than usual because I was trying to understand why my margins had been slightly lower than expected for most of last year. Not dramatically lower, just enough to feel off

I started going through my Shopify tax settings and comparing them against what I was actually required to collect and remit in each state

This took me several hours and a lot of googling about economic nexus thresholds and I am not going to pretend I understood everything perfectly. But what I found was that Shopify had been collecting and remitting sales tax in four states where I had not yet crossed the economic nexus threshold that would actually require me to collect it

Shopify's tax settings had been configured at some point to collect in those states and nobody had reviewed whether the thresholds were actually met. My bookkeeper was recording the remittances as tax payments which they were. My accountant was filing based on what had been remitted. Nobody was asking whether the remittances should have been happening in the first place

I had been overpaying sales tax in four states for about fourteen months

The process of reviewing whether I can reclaim any of that is still ongoing and may not be fully recoverable depending on the state. The amount involved is somewhere between four and six thousand dollars depending on what can be claimed back

The thing that gets me is that this did not require sophisticated accounting knowledge to catch. It required someone to periodically look at whether the tax collection settings in Shopify matched the actual nexus obligations of the business. That is a review that should happen at least annually for any ecommerce business and it had never happened once in three years

If you are running an ecommerce business on Shopify or any other platform and you have never reviewed your tax collection settings against your actual nexus obligations in each state, that is worth doing this week. The settings Shopify suggests during setup are not always correct for your specific situation and they do not automatically update as your business grows or your nexus situation changes

The mistake in either direction is expensive. Collecting when you do not need to costs you margin. Not collecting when you should creates liability. Neither one takes care of itself without someone actually looking at it periodically

I have been a bookkeeper for eleven years and I want to say something that might be unpopular in some circles but I think is genuinely true

The business model of most major accounting software is not actually to give you clean books. It is to give you just enough automation to feel like you have clean books while quietly creating enough complexity that you need paid support, paid accountants, paid integrations, and paid upgrades to fix the problems the software itself generated.

Think about how this plays out in practice.

QuickBooks sells you on automatic bank feeds and transaction matching. What they do not tell you upfront is that the matching is wrong often enough that someone still has to review every single transaction. And if you have any integrations running alongside it, Stripe, PayPal, a POS system, an inventory tool, those integrations each have their own way of pushing data into QBO that creates reconciliation problems you then need to spend hours or money fixing.

Xero does the same thing with slightly better UX. The bank rules are smarter but still break regularly. The integrations still create data quality issues. The month end close still requires significant human time.

Every one of these platforms has a thriving ecosystem of accountants, bookkeepers, consultants, and add-on tools that exist specifically to fix problems the core software creates or cannot solve. That ecosystem is not an accident. It is the business model.

I am not saying these tools are bad. I use them every day and they are genuinely useful. But there is a significant gap between what is marketed and what the reality of using them looks like after the first month.

The businesses that have the cleanest books are almost never the ones who just trusted the software. They are the ones who either have a genuinely skilled bookkeeper who understands the specific quirks of their setup or who have taken the time to understand their own accounts well enough to know when something looks wrong.

Software is infrastructure not a solution. The sooner small business owners understand that the less money they will waste chasing the dream of books that just take care of themselves

I've been at this company 6 years. SDET, mostly Python + Playwright, some mobile stuff. Good reviews every cycle. Last December leadership announced we were "investing in AI-augmented quality engineering" and rolled out one of those tools that writes tests from natural language prompts. Cool, fine, I was actually excited.

Three months in and here's what's happening:

My manager keeps asking me to "validate the AI's output" instead of writing tests myself. The PM started CCing me less on requirements docs because "the tool can read the Jira ticket directly." Two of the three SDETs on my team got moved to "platform engineering" which as far as I can tell means they maintain the AI tool. Headcount for QA next year is flat. Headcount for "AI quality" doubled.

Meanwhile the tool is fine. It's not great. It writes tests that look right and pass on the happy path and miss every edge case a human would catch in 10 seconds. I flagged this in a retro and got told I was being "resistant to change."

Am I being paranoid or is this what it looks like right before they tell you your role is being "restructured"? I genuinely can't tell anymore. My partner thinks I'm reading too much into it. My gut says start interviewing.

For anyone who's been through this, what were the early signs? And does QA-specific experience even matter on the market right now or am I going to be competing with 800 other people with the same resume?

I took on a new client in January last year, small retail business, previous accountant had handled their books for about four years before I came in. The handover was messy but I did what I thought was a thorough review, checked the chart of accounts, looked at a few months of transactions, everything seemed reasonable so I set up their opening balances and got to work

Did their books all year. Monthly reports, quarterly reviews, everything looked clean and consistent throughout

Then in December I was doing their year end and something in the inventory numbers felt slightly off. Not dramatically wrong, just a feeling. So I went back to the very beginning and started tracing the opening balance for inventory back through the previous accountant's records

The original inventory valuation was wrong. Not slightly wrong. Wrong by about eighteen thousand dollars because the previous accountant had been using average cost when the business had always operated on FIFO and nobody had ever corrected it at the handover

So every single report I had produced all year was consistently wrong in the same direction. My client had been making purchasing and pricing decisions based on margin numbers that did not reflect reality

The worst part is the reports looked clean and consistent the whole time which is exactly what made it invisible for so long. Wrong numbers that are consistently wrong do not set off any alarms until you trace them all the way back to the source

The lesson I should have known but clearly did not take seriously enough is that a clean looking set of books from a previous accountant is not the same as a correct set of books. Consistency is not accuracy. Something can be consistently and neatly wrong for years before anyone catches it

Now every single time I take on a new client I spend the first two weeks doing nothing but tracing opening balances back to source documents regardless of how clean the previous books look

It costs time upfront and clients sometimes push back on why onboarding takes so long but finding this kind of thing in January is a completely different problem than finding it in December

If you are taking on new clients and skipping a proper opening balance audit because the previous books look fine, please learn from my mistake on this one

I have tested basically every major sales tool this year from Apollo to ZoomInfo and realized most founders are approaching outbound completely backwards

Everyone wants to jump straight into the massive volume game but industry data shows 60 percent of prospects are lost just from poor targeting. No software is going to fix a fundamentally bad list

Instead of ranking tools by tiers here is how you should actually be looking at your stack based on how outbound is shifting right now

The Spray and Pray Trap

Most people default to Apollo or Instantly because they are cheap to start. They are decent tools but the database quality across the board is dropping fast. People are seeing bounce rates hit 15 percent easily right now. You end up blasting thousands of generic emails just to get one meeting and your sending domains get absolutely fried in the process because you are just guessing who wants to buy

The Enterprise Bloat

Then you have the heavy hitters like ZoomInfo Outreach or Clay. These are incredible platforms but they are complete overkill for small teams. If you do not have a dedicated RevOps engineer or a 50k budget you will spend weeks just configuring waterfall workflows before you ever send a single message

The Signal First Stack

This is where the meta is actually shifting for lean teams in 2026. Instead of buying a database of random titles you build your stack entirely around intent

This is where building your flow around something which completely replaces the traditional database model. Instead of guessing who might buy you use it to scan social signals for people who are actively complaining about the exact problems you solve. You pull the 50 people who actually need your help right now instead of annoying 5000 people who dont

Once you have those verified high intent signals you just feed them into a consolidated platform like SalesTarget for emailing or a solid dialer like Close CRM. Your bounce rates drop to basically zero and you actually get replies because the prospect is already problem aware

Stop paying for massive lists of dead data. Figure out your exact ICP and find the people actively raising their hands before you spend a dime on massive sending tools

I manage an engineering team responsible for three mobile apps and two web products. By January, our QA automation was actively working against us.

We were spending roughly 40% of our week just updating broken XPaths and testIDs because a frontend dev moved a button 10 pixels to the left, or marketing decided to A/B test a new checkout flow.

We had a 600-test Appium suite that was essentially a legacy codebase we resented maintaining. The "Shift-Left" dream had turned into a maintenance nightmare.

So, we paused feature testing and spent Q1 doing a brutal, side-by-side evaluation of 9 different enterprise E2E testing platforms.

Here is the raw reality of what we learned, stripped of the vendor hype:

1. "Codeless" usually just means "Hidden Code" Half the tools we tried pitched themselves as "no-code." The reality? They were just wrapping Selenium/Appium in a pretty UI. The second you hit a complex OTP flow or a biometric login bypass, the GUI broke, and we had to drop down into their proprietary, poorly documented scripting language anyway. If I have to write code, let me write it in my IDE, not a web browser textbook.

2. The DOM is a terrible anchor for mobile tests We realized our core issue wasn't the framework; it was the architecture of relying on locators. Cross-platform apps (we use React Native for two of our apps) generate messy, dynamic UI trees. Tying our test pass/fail rate to underlying code structure meant every UI refactor broke our tests, even if the app looked and functioned perfectly to the end user.

3. Vision AI is actually viable now (We stopped using locators entirely) This was the biggest paradigm shift for us. We ended up moving to a tool called Drizz because it completely abandoned the DOM. Instead of telling the test to look for div.checkout-btn-v2, you write "Tap the checkout button" in plain English. The engine uses computer vision to look at the screen like a human user.

If a button changes from green to blue, or shifts to the bottom of the screen, the test still passes. We deliberately broke our UI styling on a staging branch just to see if it would fail. It didn't.

The Pipeline Results: We’ve transitioned 80% of our core flows over the last month.

• Maintenance hours: Dropped from ~18 hours/week to about 3 hours.
• Flake rate: Went from a highly volatile 14% to under 2%.

The Takeaway: If your team is drowning in test maintenance, stop trying to write "better locators." The locators are the problem. You need an architecture that validates intent, not underlying code strings.

Happy to drop the full spreadsheet matrix of the 9 tools we tested in the comments if anyone is currently going through QA procurement hell.

[ Removed by Reddit on account of violating the content policy. ]

Sunday nights used to have a specific feeling in my house and it was not a good one.

So, I own three restaurant locations in Nashville. Been at it for seven years. The food side of the business I understand deeply, the sourcing, the staffing, the service. The books always felt like a separate job that I was never quite on top of no matter how much time I put into it.

Every Sunday I would sit down with QuickBooks and spend two to three hours going through the week. Something was always off somewhere and I could never fully predict where the problem would be. Sometimes it was the delivery platform payouts. Sometimes it was payroll related. Sometimes transactions were sitting uncategorized and I had no idea which account they belonged to.

The thing about restaurant accounting that most generic bookkeeping advice completely misses is that you are not dealing with clean simple transactions. You have your POS system pushing sales data into QuickBooks but the format is almost never clean out of the box. You have DoorDash and Uber Eats sending payouts that already have their fees netted out before the money hits your account which means what lands in your bank never matches what you actually sold through those platforms. You have tips flowing through payroll in a way that has to be handled correctly or you create tax problems. You have cash sales that need to be reconciled separately. You have three locations each with their own bank accounts and payment processors all feeding into one QuickBooks file.

Every one of those things requires its own setup to work correctly and most restaurant owners including me for several years just never did that setup properly. We just tried to reconcile everything manually every week and wondered why it always felt like a mess.

Here is what I actually changed and what made the difference.

The first thing and honestly the most important thing was sitting down with my accountant and rebuilding the chart of accounts from scratch specifically for restaurant transactions. Not a generic small business chart of accounts, one that actually mapped to how a restaurant generates and spends money. Food cost by category. Labor separated properly. Delivery platform revenue as its own line. This took maybe half a day and I had been avoiding it for years because it sounded boring. That one session changed how everything downstream worked.

The delivery platform reconciliation specifically I fixed by changing how I treated those deposits. Instead of trying to reconcile the net payout that hits your bank against your gross sales, I started recording them properly as gross revenue with the platform fees as a separate expense line. Once I understood that the math actually works, it just required setting up the right accounts and the right process for logging each payout correctly.

I also stopped trying to do all three locations in one sitting on Sunday night. I spread the review across the week, one location per session, which sounds simple but made each session actually manageable instead of one long overwhelming block.

My Sunday nights are just Sunday nights now. The books are not perfect but they are not a weekly emergency anymore either. My accountant and I actually talk about the business when we meet now instead of spending the whole call cleaning up the previous month.

If you own a restaurant and your QuickBooks feels like a constant fire drill the chart of accounts and the delivery platform setup are almost certainly where it starts. Neither one requires a fancy solution. They just require sitting down and doing them properly once.

I've been going back and forth on posting this but I think I finally want to.

I opened my shop in NE Portland in 2018. It survived COVID somehow, mostly pivoted to delivery and sympathy arrangements, which honestly kept the lights on. By 2022 I felt like the hard part was over. We were doing weddings again, my wholesale costs had stabilized, I had one full time employee.

Eighteen months ago I sat down to figure out why I never seemed to have any money saved despite the business feeling okay. Like I wasn't struggling exactly but I also had basically zero financial cushion. One bad month away from problems.

I thought maybe I just needed to raise prices. So I did. Margins improved a little. Still no cushion.

I thought maybe my employee costs were too high. Did the math. They weren't.

I genuinely could not figure it out and I remember telling my mom on the phone "I think I'm just bad at business" and she goes "or maybe you just can't see where it's going."

She was right and I hate that she was right.

Here's what I eventually found when I actually dug into everything properly: I was paying for cold storage insurance AND a separate contents policy that overlapped almost completely, duplicate coverage I'd set up years ago and forgotten. I had a subscription to a floral design platform I'd used for like three weeks and abandoned. I had two different payment processors because I'd switched but never turned the old one off, and both were charging monthly minimums.

None of it was intentional. I was just busy and I never had a clear view of everything at once. I was running the business out of vibes and a bank balance, and the bank balance was always technically positive so I assumed I was fine.

Once I could actually see my full picture, every account, every recurring charge, real cash flow, I found almost $900/month that was just… leaving. Quietly. For nothing.

The shop is still open. I have an actual emergency fund for the first time. I'm not posting this to brag, I'm posting it because I wasted probably three years of stress that I didn't need to have.

I’m still recovering from a massive post-mortem we had on Monday. I spent the last three months building a rock-solid automation suite for our core checkout flow. Every PR had to pass it, the pipeline was consistently green, and we felt invincible.

Last Thursday, the marketing team pushed a "temporary" sticky promotional banner to the mobile view. The devs merged it, my E2E suite ran, clicked the "Confirm Order" button perfectly, and gave a green light. We deployed.

Friday morning, we realized mobile conversions had flatlined for 12 hours.

Turns out, the new sticky banner had a z-index issue and physically covered the entire checkout button on smaller screens. Real users literally could not tap it. But my script didn't care. It bypassed the visual rendering layer, found the <button> node in the DOM, and fired a click event directly via JavaScript. It gave us total false confidence because it did something a human physically couldn't do.

It made me realize that traditional automation is fundamentally flawed: we aren't testing the user's experience, we are just testing the DOM state.

Valuable Takeaways & Resources I’m looking into:

• Audit your framework's actionability checks: If you use Playwright, make sure you aren't overusing .click({ force: true }). For Cypress, understand how it checks for visibility. But even then, they can be tricked by CSS transforms.
• Visual Regression is a bandaid, not a cure: We looked into tools like Percy and BackstopJS, but they just flag pixel differences. I don't want to approve 50 baseline images every time a dev changes a padding value.
• The Philosophical Gap: We need to start thinking about how to test visual intent rather than code implementation. Has anyone found a reliable way to test what the screen actually looks like and interacts like, without relying on the hidden HTML?

When I started my own bookkeeping practice I thought the hard part would be finding clients and in the beginning it was but then something flipped and suddenly I had more clients than I could manage properly and that is when things started getting genuinely stressful

The problem was not the work itself it was the coordination, every client was at a different stage of their month end, some sent documents on time some never did, some were on QBO some were on other platforms, and I was managing all of this through a combination of emails, a shared Google sheet that was always out of date and a lot of mental overhead that was exhausting me by Wednesday every week

I lost a client in my second year not because my work was bad but because I missed a deadline because I genuinely could not keep track of where everything stood across fifteen different people and that was the moment I realized the way I was operating was not going to scale past a certain point

What saved me honestly was getting obsessive about systems, a proper onboarding checklist, a standardized monthly process for every single client regardless of size, and being really honest with myself about how many clients I could actually serve well rather than just how many I could technically take on

I still have hard weeks but nothing like those early days and I think the biggest thing I would tell someone just starting out is that the operational side of running a bookkeeping practice is almost as important as the actual bookkeeping itself....

I am still so incredibly frustrated about this because we had a deployment push late on Friday and right before the cutoff the CI pipeline lit up red with a critical end to end checkout test failing.

The release got paused and because I am the QA lead my weekend was instantly ruined so I spent Saturday morning pulling logs and re-running the suite locally trying to reproduce it but on my local machine it passed perfectly while in the pipeline it failed every single time.

I spent another four hours digging through the DOM structure and do you know what the critical bug was because a front end developer added a new promotional banner and slightly changed the z index of a wrapper div so the actual checkout button was completely visible and worked perfectly for a human user but our Playwright script was targeting a specific selector that was technically now being obscured in the DOM hierarchy according to the headless browser.

The feature wasn't broken and the app was fine so the only thing that was broken was my script's ability to read the code underneath the UI.

I lost my Saturday to a CSS tweak and it genuinely made me sit back and realize how fundamentally flawed our approach is because if a human can look at the screen and click the button without an issue our automation shouldn't be throwing a fatal error just because the underlying HTML got reorganized.

We are spending more time testing our DOM structure than we are testing the actual user experience and please tell me I am not the only one hitting a breaking point with this kind of maintenance trap.