Off-the-shelf software is a pre-built product you subscribe to and share with thousands of other firms; custom software is built for your firm alone, to fit a workflow no product on the market handles. That is the textbook split, and for a 4-to-20-person commercial real estate firm it is also a trap, because it hides the two options that usually fit a small shop best: configuring an off-the-shelf platform to your process, and adding a thin automation layer on top of the tools you already run. The real question is not “buy or build.” It is which of four options matches this specific workflow, at your size, with no IT department to run what you choose.
Custom vs off-the-shelf, defined for CRE
Off-the-shelf software is a finished product sold to many customers at once. You pay a subscription, you use it as-is, and the vendor decides what it does next. In commercial real estate that is almost every tool you already touch: CoStar and Crexi for data and listings, Buildout for marketing, Yardi or AppFolio for property management, Dealpath or Argus for underwriting. None of them was built for your firm; all of them were built for firms like yours.
Custom software is the opposite. It is built for one organization’s specific requirements, owned by that organization, and changed only when that organization pays to change it. Nothing off the shelf does exactly what it does, which is the entire reason it exists.
The instinct at a small firm is to treat this as a single yes-or-no: buy the product, or build your own. That framing comes from software companies writing for corporations with engineering teams. It does not describe the decision a lean CRE firm actually faces, and following it leads to the two most expensive mistakes a small shop makes with technology.
Why the buy-or-build binary is wrong for a small firm
The binary is wrong because it deletes the middle, and the middle is where small firms belong. A 4-to-20-person shop rarely needs a ground-up custom platform, and rarely finds a shrink-wrapped product that fits perfectly either. The two options that fit best sit between those poles.
The first hidden option is configuring an off-the-shelf platform. Most serious CRE tools are not rigid — they have custom fields, templates, workflow rules, and integrations you can shape to your process without a single line of code. A firm that says “the CRM doesn’t do what we need” has usually not exhausted what the CRM already does.
The second hidden option is a thin automation layer: a lightweight workflow built on tools like ChatGPT, Claude, or Microsoft Copilot, wired to the files and inboxes you already have, doing one specific job an off-the-shelf product does not. It is not a product you buy and not a platform you build — it is the cheapest way to close the gap between a good tool and your exact workflow, and the option the buy-or-build binary cannot see.
Miss the middle and one of two things happens. You force a full custom build for a problem a configured tool would have solved, and overpay by an order of magnitude. Or you conclude “nothing on the market fits” and do the work by hand forever, when a few days of automation would have closed the gap. Studying what is actually for sale — and where the gaps between products sit — is worth doing first, which is what a tour of the commercial real estate technology landscape is for.
The four options, compared
For any given workflow, a small CRE firm has four choices, not two. The table maps them across the axes a principal actually weighs.
| Option | What it is | Fit to your process | Who maintains it | Best when |
|---|---|---|---|---|
| Off-the-shelf, as-is | Subscribe and use the defaults | Good enough for common work | The vendor | The task is standard and the product already does it |
| Configured off-the-shelf | Shape fields, templates, rules, integrations | Close, within the tool’s limits | You, lightly | A product is 80% right and its own settings close the gap |
| Thin automation layer | Lightweight AI workflow on your existing files and inboxes | Exact, for one narrow task | You or a standing outside relationship | No product fits a specific, repetitive task and you can describe the result |
| Full custom build | Software built for your firm from the ground up | Exact, for anything | Whoever built it, ongoing | A workflow is central to how you win and nothing else covers it |
The pattern in that table is the whole decision. Fit improves as you move down; cost and maintenance burden rise with it. The right choice is the highest row that actually solves the problem, because every row below it costs more to buy and more to keep running. A larger firm can absorb the bottom row casually. A small firm cannot, which is why the discipline is to start at the top and move down only when forced.
When off-the-shelf is enough
Off-the-shelf is the correct default, and for most of what a small CRE firm does, it is enough on its own. If a task is standard across the industry — storing comps, sending a listing to a portal, tracking a lease’s key dates, running a property’s ledger — a product almost certainly already does it, and does it better than anything you would commission, because thousands of firms have pushed the vendor to improve it.
The honest test is whether your process is genuinely different or just familiar. Most firms believe their way of doing a common task is special. Usually it is not; it is simply theirs, and a configured off-the-shelf tool would handle it fine. Building custom software to preserve a habit is the most common way small firms waste money on technology.
Buy off-the-shelf when the function is a commodity — something every firm needs and no client chooses you for. You do not win deals because your rent ledger is proprietary. Spend your build budget only where being different actually matters, and buy everything else. The full version of that test — when a subscription genuinely covers the job and when it leaves a gap worth closing — runs through the buy-versus-build playbook for small CRE firms.
When a thin automation layer is the right answer
A thin automation layer is the right answer when a specific, repetitive task falls into the gap between products — real enough to hurt, narrow enough to describe in a sentence, and not covered by anything you can subscribe to. This is the most underused option at small firms, and often the highest-return one.
The shape is always the same: one painful task, one clear output, built on tools you already have rather than a new platform. Pulling ten fields off every incoming lease into a clean summary. Turning a messy stack of rent rolls into one consolidated sheet. Drafting a first-pass market write-up from data you already hold. None of these is a product you can buy exactly; each is a few days of focused automation on top of ChatGPT, Claude, or Copilot.
What makes this option work for a small firm is that it is small on purpose. It solves one thing, it costs a fraction of a custom platform, and one non-technical person can keep it running. The risk is scope: a thin layer that tries to do five jobs stops being thin and turns into an accidental custom build. Keeping it narrow is the entire skill, and scoping that first automation so it stays winnable is a discipline of its own — the lessons from scoping automations for non-technical teams are the field guide for getting it right.
When a custom build earns its place
A full custom build earns its place only when three things are true at once: a workflow is central to how you win, no off-the-shelf tool fits it, and a configured tool or a thin layer cannot close the gap. That combination is rare, and it should be. For a small CRE firm, a real custom build is the exception you can count on one hand, not the answer to a routine frustration.
When it is warranted, it is usually because the workflow is your edge — the specific way you screen deals, underwrite, or manage a niche asset class that a competitor cannot copy off a subscription. If the process is genuinely how you out-operate bigger firms, owning the software that runs it can be worth the cost and the ongoing maintenance.
Even then, “custom” for a lean firm should mean a scoped automation covering one workflow, not an enterprise platform covering everything. The failure mode is a small shop commissioning a sprawling system it has no one to run and no budget to maintain. The discipline that lets a small firm out-operate larger ones is doing less, but doing it exactly — the argument laid out in the manifesto on how 4-to-20-person shops out-operate institutional giants. A right-sized custom build follows the same rule: narrow, owned, and small enough to keep alive.
The three constraints that override the generic advice
Every generic “custom vs off-the-shelf” guide assumes resources a small CRE firm does not have. Three constraints govern the real decision, and each pushes you up the table toward the simplest option that works.
No IT department. Whatever you choose, someone at your firm has to run it, and that someone is not a systems administrator — it is you, a broker, or an operations lead with a full plate already. This alone rules out most full custom builds, because a bespoke platform with no one to maintain it becomes an orphan the first time it breaks. The question “who owns this on Monday” decides more than any feature list.
Confidential deal data. Your files hold LOIs, financials, and terms that cannot leak. Off-the-shelf vendors publish security and data-handling documentation you can check; a thin automation layer inherits the controls of the platform underneath it, which you should verify before sending anything sensitive through it. A custom build shifts data-security responsibility onto you and whoever built it — a real cost that rarely appears in a generic pros-and-cons list.
One workflow changes and everything shifts. Small firms change how they work faster than large ones — a new asset class, a new partner, a new reporting demand from an investor. Off-the-shelf software absorbs that change through settings. Custom software absorbs it only when you pay to rebuild. The more your process is still evolving, the higher up the table you should stay.
What it costs, in real ranges
Cost is where generic guides scare small firms off entirely. They quote six- and seven-figure custom-build numbers pulled from enterprise projects, and a principal reasonably concludes that “custom” is not for them. At CRE-firm scale, the ranges are far more human.
Off-the-shelf tools are ordinary subscriptions — tens to low hundreds of dollars per user per month, more for premium data services. Configuring a tool you already pay for is mostly your own time. A focused fluency workshop that gets a team using off-the-shelf AI well runs roughly $2,000 to $15,000 — often the cheapest way to close a gap, because a trained team handles by hand what looked like it needed software. A thin automation layer or a right-sized custom build for one workflow runs roughly $25,000 to $150,000 depending on complexity, with a first project deliberately aimed at the low end.
The point of the ranges is direction, not a quote. Move up the table and cost drops toward a subscription; move down and it climbs toward a build. Match the spend to how much the workflow actually differentiates you.
Frequently asked questions
What is the difference between custom software and off-the-shelf software?
Off-the-shelf software is a finished product sold to many customers on a subscription — you use it as-is and the vendor controls what it does. Custom software is built for one organization’s specific requirements, owned by that organization, and changed only when that organization pays to change it. Off-the-shelf trades perfect fit for low cost and someone else’s maintenance; custom trades higher cost and ongoing upkeep for an exact fit to a workflow no product handles.
Is custom software worth it for a small business?
Rarely, and only under a specific test: the workflow is central to how you win, no off-the-shelf tool fits it, and neither configuring an existing tool nor a thin automation layer can close the gap. For most small commercial real estate firms, an off-the-shelf product or a lightweight automation solves the problem for a fraction of the cost. A full custom build is the exception, warranted only when the process is genuinely your competitive edge and you have someone to maintain what gets built.
What are the four options besides just buy or build?
For any workflow a small firm has four choices: use an off-the-shelf tool as-is; configure that tool with its own fields, templates, and rules; add a thin automation layer on top of your existing tools for one narrow task; or commission a full custom build. Fit improves as you move down the list, but so does cost and maintenance. The right choice is the simplest option that actually solves the problem.
How much does custom software cost for a real estate firm?
At CRE-firm scale, a thin automation layer or a right-sized custom build covering one workflow runs roughly $25,000 to $150,000 in the current market, depending on complexity, with a first project aimed at the low end — far below the six- and seven-figure numbers generic guides quote from enterprise projects. Off-the-shelf tools are ordinary subscriptions, and a fluency workshop that gets a team using existing AI well runs roughly $2,000 to $15,000.
When is off-the-shelf software good enough?
Off-the-shelf is good enough whenever a task is standard across the industry — storing comps, sending listings to portals, tracking lease dates, running a property ledger. If thousands of firms need the same thing, a product already does it well, and building your own only preserves a habit. The honest test is whether your process is genuinely different or merely familiar; most firms overestimate how special their version of a common task is.
What is a thin automation layer?
A thin automation layer is a lightweight workflow built on tools you already have — ChatGPT, Claude, or Microsoft Copilot — wired to your existing files and inboxes to do one specific job an off-the-shelf product does not, such as pulling key fields off every incoming lease or consolidating messy rent rolls. It is neither a product you subscribe to nor a platform you build, it costs a fraction of a custom system, and one non-technical person can keep it running as long as it stays narrow.
Can I customize an off-the-shelf tool instead of building from scratch?
Usually, yes, and it is the option most small firms skip. Most serious CRE platforms have custom fields, templates, workflow rules, and integrations you can shape to your process without writing code. A firm that concludes “the tool doesn’t do what we need” has often not exhausted what the tool already does through its own settings. Configuring a product that is 80% right is far cheaper than commissioning one that is 100% right.
Who maintains custom software at a firm with no IT department?
Whoever builds it, on an ongoing basis, or no one — which is the risk. A custom build with no maintenance plan becomes an orphan the first time a document format changes or an integration breaks. Before commissioning anything bespoke, name the specific person or standing outside relationship who owns it when it breaks. If you cannot name that person, the answer is an off-the-shelf tool the vendor maintains, or a thin layer simple enough for one non-technical person to run.
Does custom software put confidential deal data at more risk?
It shifts the responsibility onto you. Off-the-shelf vendors publish security and data-handling documentation you can review before trusting them with LOIs, financials, and deal terms. A thin automation layer inherits the security controls of the platform beneath it, which you should verify before sending sensitive files through it. A full custom build makes data protection your obligation and your builder’s — a genuine cost that generic comparisons leave out.
Where to start
The first move is not to pick a vendor or a developer. It is to place your most painful workflow on the table above: is this a standard task a product already handles, an 80%-right tool you could configure, a narrow job a thin automation layer would close, or the rare workflow that genuinely earns a custom build? A free AI-readiness assessment does exactly that placement with you — it identifies the workflow, tests whether an off-the-shelf tool or a lightweight automation already solves it, and only points toward a custom build when nothing simpler will do. Book a free AI-readiness assessment before you buy or build anything.
Arthur Wandzel
