Jatin Narang, CEO of Verito.com, a leader in private hosting & managed IT solutions, empowering accounting firms in the digital era.
A tax preparer’s technology stack is a chain. Tax software sits at the center, surrounded by e-file connectors, document tools, payment integrations and workflow add-ons that make a modern practice run. If you build one of those tools, you don’t control the environment where your product lives; your customer does. And most of them chose it without thinking about you.
Tax software updates constantly. Federal form revisions, state changes, e-file schema adjustments and mid-season corrections arrive weekly, sometimes daily, between January and April. Your application has to stay synced with every one of those releases, and so does the server it runs on.
I’ve spent a decade hosting infrastructure for accounting firms, and this is the most common failure pattern I see. A vendor ships a perfectly good update, but it lands on a server running last month’s tax software build or an aging machine in a supply closet nobody maintains. As a result, the integration fails. The fix is knowing where your code is going before you sell it.
Ask Where It Will Run Before You Take the Check
Professional software in this industry isn’t cheap. Firms pay thousands per year for the tools in their stack, and they expect performance that matches the invoice. But the experience they actually get is a function of two things: your product and the environment it runs in. You only ship one of them.
That’s why environment discovery belongs in the sales process. Before the contract is signed, your team should know the answer to one question: Where will this run? Does that mean a maintained dedicated server, a generic cloud instance nobody patches or a ten-year-old machine under the front desk?
Each answer changes what the customer should expect and what you should promise. Selling premium software into an environment that can’t support it is really just a refund with a delay, plus a reputation cost you’ll pay during your busiest season.
Knowing the answer up front lets you do two things most vendors skip:
1. Set expectations honestly. If the customer’s environment can’t deliver the experience your demo showed, say so before they buy. Tell them what performance will actually look like on their setup, in plain language. That conversation feels risky, but it’s actually the opposite. The customer who hears “on your current server, expect slower load times during peak season” will trust you more, not less. The one who finds out in February trusts no one.
2. Recommend alternatives when the environment is the problem. Sometimes the right move is pointing the customer somewhere better. That might mean minimum environment requirements written in plain English, or it might mean a list of hosting providers you’ve tested against, who track tax software releases and keep environments current. It also might mean telling a firm their hardware needs replacing before your product will earn its price. Telling customers which conditions your product was built and tested for, the same way a hardware manufacturer specifies power requirements, is just common sense.
Vendors who go further can formalize this. Test against specific hosting environments and sync release calendars with providers who serve your vertical. Publish what you’ve validated. Every known environment shrinks your support costs.
If your product is pure browser-based SaaS with no local install and no direct hook into the tax software’s environment, this advice mostly doesn’t apply, since you already control your own infrastructure. This case is for the rest of the category: the connectors, add-ons, and desktop integrations that live where the tax software does. In this industry, that’s still most of us.
There’s a compliance dividend too. Tax preparers are classified as financial institutions under federal law and are required to evaluate the security practices of their vendors and their environments. When you ask where your software will run, you’re prompting a question regulators already expect them to answer.
The Expectation You Set Is Part Of The Product
No single company owns the tax preparer’s stack. Every company depends on it working as a whole. Vendors who treat the runtime environment as someone else’s problem are betting their reputation on strangers.
My advice is to make “Where will this run?” a standard question in every sale. Write your minimum requirements like you’re explaining them to a firm owner, not a sysadmin. And if the honest answer is that the customer’s environment will undercut your product, have the discipline to point them somewhere better.
Expensive software comes with an implied promise. The vendors who last in this industry are the ones who make sure the environment can keep it. Because to the preparer staring at a failed export on April 12, there’s no difference between your product and the place it runs.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
