Why did software vendors stop listening to us?

A bookkeeper posted something in a practitioner group this week that drew more agreement, faster, than almost anything I have seen in one of those groups this year. The trigger was a second, widely followed bookkeeper going public with feedback on a platform feature after the private channels went nowhere. The post that followed was longer, angrier and, judging by the replies, close to a consensus. It is anonymised here. The names do not matter and the argument does not need them.

The argument, in one line: the people who built the cloud accounting platforms' partner channels for free are done working for free, and the vendors have not noticed yet.

What the post actually said

Strip out the heat and it makes five claims. Each was echoed in the replies by people who run practices of their own, so read them as the thread's account rather than a verified history.

1. Beta testing was unpaid, and it was real work. Bookkeepers tested new features on live client files, at their own risk, and reported back. "They once listened, until suddenly they didn't."
2. The feedback channels stopped answering. Ideas portals and voting queues absorb requests and return nothing, so practitioners stopped using them and went to public groups instead. The vendors then object to the public groups.
3. Account managers became salespeople. "Don't tell me otherwise."
4. Partner value went down while the titles were shuffled. By the post's account, a scheme that rewarded community contribution with partner points was introduced, worked, and was withdrawn, and the certified consultant title that once carried a premium with clients became advisor, then in practice bookkeeper.
5. The vendors now sell the work themselves. Both platforms the author works with have built internal advisory teams. An account manager pitched one to the author this year. The answer was no.

Then the passage that got the most replies, paraphrased: I am happy to beta test anything, but I am no longer doing it for free. And when your AI makes a mess of a subscriber's file, I will be the advisor they pay to fix it, at rework rates, and they will not be your happy customer any more.

Why it landed

None of this is new. The Firm covered the burnout side of the same story in one bookkeeper's goodbye post, and the profession asked a similar question when a platform invited accountants to mentor small businesses for free. What is different is the tone. The goodbye post was exhaustion. This one is a withdrawal of labour, and the replies were not "hang in there". They were "same".

The partner deal that built cloud accounting in the 2010s was simple. A practitioner gave the vendor their clients, their credibility and their hours: migrations, beta testing, forum answers, webinars, a speaking slot at the roadshow. In return the vendor gave status that converted into work: a certification that meant something to a business owner, a place in the advisor directory that sent referrals, early access, and a person at the vendor who picked up the phone. Nobody wrote it down, and that is the problem. An unwritten deal can be repriced by one side without a conversation, and by the thread's account it has been.

The hours practitioners give are unchanged or higher. Every release still needs testing against real files, and every new feature still generates a forum thread that a volunteer answers. What the vendor gives back has thinned: certification tiers that mean less to clients, a directory that now competes with the vendor's own in-house service, a feedback portal instead of a person. That is not a conspiracy. It is what happens when a platform reaches the scale where it no longer needs its early partners to grow, and the partner program moves from the growth team to the cost line. The rational response from the vendor is to keep the free labour and stop paying for it. The rational response from the practitioner is the post.

The free labour has a price, and you are paying it

Add up the hours in the last twelve months that went to a vendor rather than a client: beta programs, forum answers, feature-request write-ups, partner webinars you attended because the account manager asked, the roadshow. For an active partner it is commonly a week or two of billable capacity a year, and far more for the people carrying a vendor community. When the return is a title that can be revoked and a queue that does not answer, that time is a donation to a company with a larger marketing budget than yours.

Beta testing in particular is skilled work with real risk. You test on live client files because there is no other way to test bookkeeping software properly, and if the feature corrupts a bank feed or a payroll run, the client calls you, not the vendor.

What to do about it

Refusing to test is one response. The better one, if you want the relationship without the subsidy, is to treat the vendor like a client.

1. Put the beta work on paper

Write a one-page engagement for product feedback work, the same way you would for an implementation: scope (which features, which client files, how many hours), deliverable (a written test report and a debrief call), timing, and a fee. Send it to the partner manager the next time a beta invitation arrives. Some vendors will decline. Some will say yes, because a paid tester who reports properly is cheaper than the support tickets a bad release generates. Decide the number the way you decide any other fee: what the hours cost you, what the risk is, and what the work is worth to a company that ships to millions of subscribers. Do not accept a discount on your own subscription in lieu of payment. A discount is a retention tool, not a fee.

2. Move your community effort somewhere you own

Hours spent answering questions in a vendor's forum build the vendor's asset. The same hours spent in a group you run, a newsletter you write, or a short video series under your own name build yours. If your free answers have carried a vendor community for years, you already have the audience. Move it.

3. Keep the client relationship on your side of the line

The author of the post takes no commissions, and every client owns their own subscription. That is the right structure, and the thread's argument is the reason: a practice whose clients hold their own subscriptions can move them, or add a second platform, without a vendor's permission. Being competent on two platforms rather than devoted to one is what "don't put all your eggs in one basket" actually means. It is the same logic as knowing what to do when your vendor is acquired: the platform is a supplier, and suppliers change terms.

4. Price the work the vendors are handing you

There is an unintentional gift in the thread. Vendors are shipping automation and AI features into files that bookkeepers used to keep clean by hand, and some of the results will need fixing. The post's author expects to be the advisor the subscriber pays to sort it out. Build that service now rather than absorbing it into "bookkeeping" later: a file review and rework engagement with its own scope, its own name, and a price set the way you set any other fee. The discipline is the same one behind app advisory that pays: a written scope, a fixed deliverable, and a refusal to do it as a favour. For a preview of the rework, read this account of AI replacing a bookkeeper's work and getting it wrong.

5. Keep a paper trail on feedback, then vote with the renewal

Keep using the feedback portals, but differently. Post once, in writing, with the client impact stated plainly, and log the date. Copy the partner manager. Log the response, or the absence of one. Twelve months of that log is the most useful input you will have at renewal time, and it answers the vendor's community team when they ask why the feedback moved to public groups.

The verdict

The post reads as anger, and it is. Underneath it is a business decision that more practices should make on purpose: stop subsidising suppliers. Every hour you give a vendor for free is an hour you have priced at zero, and the vendor has heard the number. If the vendors take one thing from the thread, it should be that the feedback moved to public groups because the private channels stopped answering, and that the good testers will still test, on paper, at a price. Put the beta work on paper, own the community you have been building for someone else, keep the client relationship on your side, and build the rework service the AI features are about to make necessary. None of that requires leaving a platform. It requires treating the platform as a supplier, not a partner, until it behaves like one again.

Frequently asked questions

Will a vendor really pay a bookkeeper to beta test?

Some already run paid research and testing programs through their product teams rather than the partner channel, because a structured report from a practitioner who uses the product with real clients is worth more than a support ticket. Ask the product manager, not the account manager, and offer a defined scope.

Is it unprofessional to post feedback about a vendor publicly?

Not if it is specific, accurate and about the product. Describe the feature, the client impact and what you have already tried through official channels, and leave out the individuals. Read the vendor's community rules first. Most prohibit abuse and naming staff, not criticism.

Should I drop my certification if the tier has been downgraded?

Not on principle. Ask what the badge earns you: referrals from the directory, client confidence, early access you actually use. If the answer is nothing measurable, stop investing the hours to keep it and put them into your own marketing, where the return is yours.

How do I explain to clients that I no longer recommend one platform?

You still recommend, for the client rather than for the vendor. Tell them you work across two platforms, that they own their subscription either way, and that the choice depends on their business. Clients hear that as independence.

What if a vendor's AI feature damages a client file?

Document before you fix: export the affected periods, screenshot the feature's settings, note the date and version. Then quote the rework as a separate engagement rather than absorbing it into the monthly fee. The client should understand that a supplier's automation, not your work, caused the cost.