Custom application development vs off-the-shelf software: 5 tests
For owners and directors of growing B2B and ecommerce companies: five tests, a scoring table and a three-year cost view to choose between a platform, a custom build or both.
On this page
You are about to put the next stage of your business on software, and the choice looks binary. Buy a platform that works on Monday, or commission something built around your process. Both can be right, and the mistake is choosing before you know which parts of the business the software must carry.
This guide gives you a way to decide between custom application development vs off-the-shelf software without a pitch for either side. You get five tests, a 0 to 2 scoring table, a three-year cost view and the hybrid path that is often the real answer. It works the same way for WordPress, Webflow, Shopify and a custom Next.js application.
werun.dev builds on all four, so the advice follows fit. By the end you can score one project in ten minutes and defend the result to your partners, your finance lead or your team.
Key takeaways
- Five tests (differentiation, integration load, scale, team and compliance) tell you whether a platform is enough for a given project.
- A 0 to 2 score per test gives you a total you can read in ten minutes and show to your partners.
- Compare the three-year bill in licences, customization and maintenance, and leave the launch price out of the comparison.
- The usual answer is a hybrid: a platform for the common work and a custom piece for the part that sets you apart.
- This week, score one project and list every system it must connect to, and you have most of a good agency brief.
Five tests for custom or off-the-shelf software
Five questions settle most build-or-buy decisions. Each has a plain rule for when a platform is enough and when custom pays off. Answer them for one project, such as a quoting flow or a store rebuild, and not for the whole company.
Differentiation: does this process win you customers?
Buy what every competitor also does and build what makes customers choose you. A contact form, a blog and a standard checkout look the same everywhere, and platforms have refined them for years. A pricing engine that quotes custom bundles in seconds is yours alone. A platform approximates it, while custom code can match it exactly.
The key rule
Custom pays off only where the process differentiates you. Buy the rest. For each process, ask whether a customer would notice if it changed.
Integration load: how many systems must it talk to?
Count the systems the software must exchange data with: ERP, CRM, inventory, billing, a warehouse. One or two common connections usually have a ready connector, such as a Shopify app or a WordPress plugin. Five or six, with rules about which system wins when records disagree, start to need code you control.
If you are weighing no-code automation for part of this, our guide to low-code and no-code vs custom development covers that middle ground.
Scale: how much traffic, data and complexity is coming?
Scale means traffic, data volume and the complexity of your rules. Hosted platforms such as Shopify and Webflow carry traffic for you, which is a real saving. Complexity is the harder limit: customer-specific price lists, multi-step approvals, unusual catalogue structures. If you expect these within three years, score them now, because moving later costs more than planning today.
Team: who will own it after launch?
Software needs an owner after launch. Someone updates content, fixes a broken update and answers a security notice. A marketing team of three can run Webflow or Shopify daily without a developer. A custom application needs people to keep it healthy, in-house or an agency on a retainer. If nobody will own it, favour the option with the least to own, or budget for a care plan.
Compliance: what must be provable and controlled?
Compliance covers what you must prove and control: where data lives, who can see it, how long you keep it and the audit trail. Platforms publish security documentation you can inherit, which helps most small teams. Some contracts ask for more, such as data in a given region or a log of every change. Check the requirement against the platform's documentation first. If the platform cannot meet it, score a 2.
Score your project in ten minutes
You can turn the five tests into a number. Score each test from 0 to 2, add them up and read the path that fits. Use one real project and answer with the person who runs the process.
How to fill in the scoring table
Read each row, pick the column closest to your project and write down 0, 1 or 2. A 0 means a platform covers it as it comes. A 1 means a platform works with an extension or a small custom plugin. A 2 means the need only fits code built for you.
| Test | 0 points | 1 point | 2 points |
|---|---|---|---|
| Differentiation | The process matches what competitors do | Small twists that platform settings can handle | The process is why customers choose you |
| Integration load | One or two systems with ready connectors | Three or four systems, some custom mapping | Five or more systems, or rules for conflicting data |
| Scale | Traffic and rules stay modest | Growth expected and rules getting more complex | High volume or complex rules within three years |
| Team | No technical owner after launch | An agency on a retainer or care plan | A developer or agency owns the code long term |
| Compliance | Platform documentation meets your needs | Extra controls through plugins or settings | Specific controls, regions or audit logs required |
The second table shows how each path tends to handle each test, so you can see where a score comes from and which path absorbs it best.
| Test | WordPress | Webflow | Shopify | Custom Next.js |
|---|---|---|---|---|
| Differentiation | Plugins and hooks extend most things | Strong for content and marketing, custom logic needs code | Strong for selling, unusual purchase logic needs apps | Any logic, built to your rules |
| Integration load | Many connectors, heavy flows need a custom plugin | Best for a few connections through APIs | Large app ecosystem for commerce systems | Any system with an API, designed as one |
| Scale | Depends on the hosting and caching you choose | Hosted and managed for you | Hosted and managed for you | Scales with the architecture you design |
| Team | Needs ongoing updates and care | Lightest to run for marketers | Light to run, apps need review | Needs a developer owner |
| Compliance | Control is yours, proof is your job | Inherit platform documentation | Inherit platform documentation | Full control, you document and maintain |
How to read the result
Add the five scores. A total of 0 to 3 says a platform fits, so configure it well. A total of 4 to 6 points to a hybrid: a platform plus a custom piece. A total of 7 to 10 says a custom build is worth pricing.
Scoring path
- 01Five testsDifferentiation, integration, scale, team, compliance
- 02Score 0 to 2 eachPick the column closest to your project
- 03Add the totalA sum between 0 and 10
- A0 to 3: PlatformConfigure it well
- B4 to 6: HybridPlatform plus a custom piece
- C7 to 10: Custom buildWorth pricing
Decision flow: five tests are each scored 0 to 2, the total points to a platform, a hybrid or a custom build
Treat the number as the start of a conversation. Two 2s on differentiation and integration load often weigh more than three 0s elsewhere, so look at which tests scored high and not only at the total.
Three-year cost of custom software vs off-the-shelf
The launch price tells you little. Compare the full bill over three years in three parts: licences, customization and maintenance. The table stays qualitative on purpose, because your quotes will set the real numbers.
| Path | Licences | Customization | Maintenance |
|---|---|---|---|
| WordPress | Low to medium, recurring (premium plugins and themes, hosting) | Low to medium, one-off per feature | Medium, recurring (updates, security, plugin compatibility) |
| Webflow | Medium, recurring (site and workspace plans) | Low to medium, one-off, custom code for gaps | Low, recurring (content and small fixes) |
| Shopify | Medium to high, recurring (plan, apps, transaction fees) | Low to medium, one-off, custom apps for gaps | Low to medium, recurring (app review, theme changes) |
| Custom Next.js | Low, recurring by usage (hosting, database, services) | High, mostly one-off and up front | Medium to high, recurring (dependencies, monitoring, fixes) |
Licences and subscriptions
Platforms charge you every month or year, and the bill grows with plans, apps and extensions. Shopify adds app subscriptions and, on some plans, transaction fees. Webflow charges per site plan, and WordPress core is free while premium plugins and themes renew yearly. A custom app has fewer licences, but you still pay for hosting, a database and third-party services, usually by usage.
Customization and build
This is the one-off part, and it is where custom costs more up front. Platforms get you live faster because the common 80% already exists. Custom work buys exactly the behaviour you need, built once. The Next.js documentation (opens in a new tab) shows what the framework gives you out of the box, which helps you judge what an agency must build and what it only configures.
Maintenance and technical debt
Maintenance is the recurring part, and teams underestimate it most. Shopify and Webflow patch the platform for you, and you manage apps and content. WordPress hands you updates, plugins and security. Custom code needs dependency updates, monitoring and fixes.
Technical debt means shortcuts that make every later change slower. It grows on every path in a different way: plugin conflicts on WordPress, overlapping apps on Shopify, ageing code on a custom build. Our guide to the hidden cost of every web platform goes line by line.
What changes the totals most
Four things move the three-year total more than the platform name does:
- The number of systems you must integrate and keep in sync.
- The number of workarounds your process needs on a platform.
- How often your business rules change.
- Who maintains it: your team, an agency or a care plan.
For example (illustrative), a distributor with 15 customer-specific price lists might run them on a platform through an app subscription, a plugin and a monthly manual check. The same lists as a custom piece become a one-off build and a small maintenance line. Neither is cheaper by default, so ask every vendor to quote all three columns.
The hybrid path: platform plus custom piece
For most growing businesses the answer is both. Run the common 80% on a platform and build a custom piece for the part that sets you apart. You keep fast launches, hosted security and editors who know the admin, and you add code only where a test scored a 2.
WordPress or WooCommerce
Custom plugin
Your own rules live in one plugin, so core updates leave your logic untouched.
Shopify or Webflow
Custom app beside the platform
The platform keeps checkout or content, and a small app adds the behaviour only you have.
Any platform back end
Next.js front end
Editors keep a familiar admin while the visitor sees an interface built for your sale.
The hybrid is also the easiest path to grow or reverse. The custom piece sits beside the platform, so you can replace one without rebuilding the other.
Custom plugin on WordPress or WooCommerce
A plugin holds your own rules, such as quoting logic or a special checkout step. It uses WordPress hooks, the official points where code can change behaviour. The WordPress developer resources (opens in a new tab) document hooks and plugin structure. For stores, our post on custom e-commerce vs Shopify and WooCommerce covers when a tailored build wins.
Custom app beside Shopify or Webflow
Shopify apps and APIs, documented on shopify.dev (opens in a new tab), let a custom app add a bundle builder, a B2B price engine or an ERP sync while the store keeps checkout, hosting and payments. Webflow works the same way: the CMS stays for marketing content, and a small service handles logic through its API and webhooks (messages one system sends another when something happens).
A Next.js front end on a platform back end
Here the platform keeps content, products and orders, and a custom Next.js front end draws the experience. It suits teams that need a very specific interface or very fast pages and still want editors in a familiar admin. It costs more than a theme, so use it when the interface itself differentiates you.
Signs you outgrew your platform
A platform that feels tight is not always outgrown. Often it is configured badly or missing one extension. These symptoms help you tell the two apart. If you tick three or more, a platform limit is likely.
Symptoms in daily work
Watch what your team does by hand. People re-key orders into the ERP, export spreadsheets to answer a simple question or keep a document of how to get around a limit. A new colleague needs a week to learn the workarounds. These are signs the platform no longer matches the process.
Symptoms in the numbers and the roadmap
Check the numbers too. Maintenance spend rises each quarter while the features you ship fall, or a request waits months for a workaround. Another sign is that a sales or operations lead has stopped asking for improvements because they expect a no.
Before you decide, test whether a configuration fix solves it, such as replacing a plugin with a native feature. If it does, you have a configuration problem. If it needs yet another workaround on top of the last, you have a platform limit. Tick what applies to your team:
- Your team re-keys orders or quotes into the ERP or CRM by hand
- A plugin or app stack must be tested before every update
- A feature request waits months for a workaround
- Two apps or plugins overlap and nobody knows which one wins
- Reports need a spreadsheet to stitch data from several tools
- Customers see a process that works differently from how you sell
- Every new rule means another paid extension
- One person or agency knows how the workarounds fit together
Four scenarios from B2B and ecommerce
These are illustrative cases, not clients. Each shows the five tests applied and the verdict, scored in the order differentiation, integration, scale, team and compliance.
A B2B services site that needs more enquiries
Scores: 0, 1, 0, 1, 0, a total of 2. The site is content, proof and forms, and the only integration is the CRM. Verdict: a platform. Webflow or WordPress fits, and the budget is better spent on clear pages, speed and tracking than on custom code.
A distributor with quotes and ERP data
Scores: 2, 2, 1, 1, 1, a total of 7. Customer-specific pricing and quoting is how this company wins, and it depends on live ERP and stock data. Verdict: a custom build for the quoting, with marketing pages kept on a platform. The score points to code that owns the rules and the data exchange.
A Shopify store with a unique bundle builder
Scores: 2, 1, 1, 0, 0, a total of 4. The store sells well on Shopify, and only the bundle builder is unusual. Verdict: a hybrid. Keep Shopify for checkout, hosting and payments, and add a custom app or theme extension for the builder. Moving the whole store would cost more than the gap it fills.
A client portal that is the product
Scores: 2, 1, 2, 1, 1, a total of 7. Customers pay for the portal itself, with roles, per-account data and growth in users. Verdict: a custom Next.js application. A platform would shape the product, so build it and keep the marketing site on Webflow or WordPress.
How to brief an agency either way
A good brief gets you proposals you can compare, whether you lean to a platform or to custom. Write it once and send the same text to two or three agencies, ideally one platform-led and one custom-led, so you see both options priced the same way.
What to put in the brief
State the goal and the number it moves
Write one sentence, such as cutting quote turnaround from two days to two hours, and say how you will measure it.
List the systems to connect
Name the ERP, CRM, payments, email and warehouse tools, and who holds each login.
Name who owns it after launch
Say who edits content, who fixes issues and who holds the accounts and the code.
Set budget and date limits
Give a range and a deadline, plus anything fixed, such as a trade show or a season.
Ask for both options
Request a platform option and a custom option, each with a three-year cost view.
What to ask in return
A proposal is only comparable if it answers the same questions. Ask each agency for these:
- The three-year cost in licences, customization and maintenance, for each option it offers.
- Who owns the code, the repository, the hosting and the domain after launch.
- What the handover includes, such as documentation, access and a walkthrough.
- How updates, security fixes and urgent requests are handled and how fast.
- What it would change in the plan if your integrations or rules grow.
Our list of questions to ask a web development agency adds more to raise before you sign.
Where to start this week
Take one project and run the five tests with the person who runs the process. Write down the score. Then list every system the project must connect to. Those two pages are most of a good brief.
When you have them, tell us your goal and the score. We build on WordPress, Webflow, Shopify and custom Next.js, and we recommend by fit. See our solutions or the custom applications page for how we work, and we reply in under 2 hours on business days.
Frequently asked questions
Is custom software better than off-the-shelf software?
Neither is better in general. Off-the-shelf software is faster and cheaper to start and fits common processes. Custom software fits when a process differentiates your business or when integrations and rules go beyond what a platform handles.
When should a business build custom software instead of buying?
Build when a process wins you customers, when the software must connect to several systems with its own rules, or when compliance or scale needs control a platform cannot give. A score of 7 or more out of 10 on the five tests is a sign to price a custom build.
How much more does custom application development cost than a platform over three years?
There is no fixed ratio. Custom costs more up front, while platforms cost more in recurring licences and workarounds, and the gap depends on integrations and how often your rules change. Ask each agency to quote licences, customization and maintenance for both paths over 36 months.
Can I start on Shopify, WordPress or Webflow and move to custom later?
Yes, and it is often a sound plan. Keep your data clean and exportable, put custom logic in a plugin or app you can reuse, and move one part at a time. A planned migration protects your search rankings and your data.
What is a hybrid approach to custom vs off-the-shelf software?
A hybrid runs the common parts on a platform and builds a custom plugin, app or front end for the one part that differentiates you. You keep fast launches and hosted security while custom code covers the gap.
Who owns the code when an agency builds a custom application?
It depends on the contract, so write it down before you start. You should receive the repository, the hosting and domain accounts and the documentation, with the code assignment or licence stated in the agreement.