"Custom software" describes almost nothing on its own. It's used for a Salesforce configuration, a Bubble app, a WordPress site with plugins, a white-labelled product with your logo on it, and a codebase written from scratch for one company. Those are five very different purchases at five very different levels of long-term risk.
Signature Systems builds with zero off-the-shelf software. This article defines that precisely, because a claim you can't test isn't worth making — and then gives you the questions to test it with, on us or on anyone else.
What we mean, stated precisely
Zero off-the-shelf means the application layer of your system — the data model, the business logic, the interfaces, the permissions, the automations — is written for your company and exists nowhere else.
- No product configuration. We don't customize Salesforce, HubSpot, Zoho, Monday or Airtable and call the result a custom system.
- No no-code or low-code platforms. No Bubble, Retool, Glide, Softr or Power Apps as the foundation of a production system you depend on.
- No page builders or themes. No WordPress plugin stacks, no purchased dashboard templates, no white-labelled product reskinned per client.
- No shared multi-tenant core. Your system is not one instance of an internal product we resell with your name on it.
- One codebase, one company. Every screen, rule and endpoint exists because your operation needs it.
What we obviously do use — and why that isn't a contradiction
Nobody writes an operating system, a database engine or a TLS implementation for a CRM project, and any vendor claiming otherwise is either confused or lying. We build on open-source languages, frameworks, databases and cloud infrastructure, and we integrate with third-party APIs where you already have systems worth keeping.
The line is between infrastructure and your system. Infrastructure — the language runtime, the database, the hosting platform, well-maintained open-source libraries — is shared, standard, inspectable and replaceable. Your system is the layer above it: the schema that models your business, the logic that encodes your rules, the interfaces your staff use. That layer is written for you and nobody else, and it's the layer that determines whether the software can follow your business as it changes.
Why almost nobody works this way
The economics push hard in the other direction. Configuration and templates let an agency deliver in weeks with junior staff and repeat the same work across clients at high margin. Building from scratch requires senior engineers, a longer discovery process, and the willingness to say no to projects that don't warrant it.
There's also a platform incentive layer: partner programs, certifications and referral commissions all reward recommending the platform. A certified implementation partner is not a neutral advisor about whether you need that platform.
And genuinely custom work is harder to sell. "Live in three weeks" beats "live in four months" in a sales meeting, even when the four-month answer is dramatically better over five years. So most of the market sells the fast answer, and "custom" gets stretched to cover it.
Nine questions that expose what a vendor actually builds
Ask these of anyone selling you custom software. The specificity of the answer tells you more than the answer itself.
- What platform or framework is this built on, and what parts are configuration versus code we own?
- If we stop working with you, what exactly do we receive — repository, schema, deployment scripts, documentation?
- Can another engineering team pick this up? What would their first week look like?
- Are there per-seat costs, and do they rise as we hire?
- Which third-party services will this depend on at runtime, and what breaks if one of them changes pricing or shuts down?
- Is any part of this shared with your other clients?
- How is this hosted, who controls the account, and whose name is on it?
- What's the process and rough cost for a significant workflow change in year two?
- Show me a data model diagram for a past project. Does it reflect that client's business, or a generic template?
Why it matters more in year three than year one
In the first year, a configured platform and a custom system can look very similar from the outside. Both work. The divergence shows up later, when the business changes — a new service line, a new jurisdiction, an acquisition, a regulatory requirement, a partner who needs restricted access.
At that point one system absorbs the change as ordinary engineering work, and the other requires you to find out whether your vendor supports it. That's the whole difference, and it compounds every year you operate.
The short version
- Zero off-the-shelf means your application layer — data model, logic, interfaces, permissions — is written for your company alone, on standard open-source infrastructure.
- You don't have to take a vendor's word for it. Ask what you own, what's shared, what breaks if a third party changes, and what a year-two change costs.