The demo is on Thursday. The platform costs $48,000 a year, plus a $22,000 implementation, and it promises to solve four problems you have.
Everyone frames this as a two-way decision: buy the platform, or build something custom. That's the conversation your team will have, and it's the wrong conversation, because it skips the question that actually determines the outcome.
The question is: should you bother?
Three doors, not two
Buy. Purchase the off-the-shelf product. Fast, supported, someone else maintains it, and you inherit their roadmap and their opinions about how your business should work.
Build. Have something made that fits your actual process. Slower to start, costs more up front, no license creep, and it does what you do instead of what the average customer does.
Bother. Change nothing. Keep doing it the way you do it. Spend the money on something else, or on nobody.
That third door is a real option with a real value, and it wins more often than anyone in the software industry would like you to know. It should be on the whiteboard every time.
When to buy
Buy when the process is genuinely standard, when your version of it has no competitive significance, and when the vendor's opinions about how it should work are probably better than yours.
Payroll. Accounting. Email. Calendar. Basic CRM. E-signature. Nobody has ever won a deal because their payroll system was bespoke.
The test: would you be embarrassed to explain to a peer why you do this differently than everyone else? If yes, buy the thing. Adopt their process. Stop customizing it, which is where most of the money goes anyway.
The trap in buying is that you'll spend $70,000 in year one to solve four problems, and use the product for one — because the other three didn't quite fit, and the workarounds are almost as bad as what you had. Before you sign, make somebody name, specifically, which problem this solves, and confirm that the annual value of that one problem exceeds the annual cost of the whole platform. If it doesn't, you're paying for three features you'll never turn on.
When to build
Build when the process is genuinely yours — when the way you do it is a reason clients choose you, or when your business has a structural quirk that no vendor will ever accommodate.
Also build when the honest arithmetic says so. If a workflow costs you $60,000 a year in hidden payroll, and the off-the-shelf option is $50,000 a year forever, and a purpose-built system is $30,000 once plus $500 a month to run — the build is not the expensive option. It's the cheap one, by year two, and dramatically so by year five.
That comparison is almost never run. People compare a build's up-front cost against a SaaS product's monthly cost and feel good about the small number. Run it over five years, with the license increases the vendor will absolutely apply, and the picture inverts.
The trap in building is scope. A build that solves one workflow beautifully is a great investment. A build that tries to become your operating system is a project that ships in eighteen months, over budget, into a business that has changed.
When to bother
Don't do anything when the volume isn't there, when the process is about to change anyway, when nobody will use it, or when the number is simply too small.
A workflow that costs you $9,000 a year does not justify a $40,000 platform or a $30,000 build. It justifies a shrug and a decision to spend that money somewhere it earns.
There is a strain of thinking among growth-minded owners — good people, ambitious people — that says standing still is losing. It isn't. Deciding not to solve a small problem so you can properly solve a large one is not passivity. It's the entire skill of running a company with finite resources.
The bother option is also, usefully, the baseline that makes the other two honest. Every proposal should be measured against doing nothing, because doing nothing costs zero dollars and zero change-management, and if a project can't beat that, it doesn't deserve your quarter.
The five-year table
Before any decision above $20,000, make somebody build one table. Three columns — buy, build, bother — and five rows for five years. Put every cost in it: license, implementation, internal time, maintenance, the annual increase, the cost of the workflow if you do nothing.
It takes an hour. It will change your mind at least a third of the time, and it will end the meeting where two smart people argue from intuition for forty-five minutes.
The thing under all of it
None of these three doors is about technology. They're about what your business actually is, and what parts of it are worth being different at.
The stuff that makes you special — how you underwrite, how you serve, how you close, the relationships, the judgment, the thing your best people do that nobody else's best people do — that's what you protect and invest in.
Everything else is plumbing. Buy the plumbing, or automate it, or leave it alone. But don't spend a year and $70,000 making your plumbing distinctive, and don't let a vendor convince you that their opinion of your business is more valuable than yours.
Ask which door you're walking through, and why. The demo on Thursday will be very good. That's not the same as being right.