Custom software vs off-the-shelf: cost, ROI, and when to build

For standard work like accounting, payroll or email, off-the-shelf software fits and costs less on day one. Custom software costs more up front: at Ronas IT, a custom web app for internal work, such as a CRM, starts from $15,000 with design and project management included. It pays for itself when the software is your product, when it runs the process that sets you apart, or when per-user fees grow faster than the value you get. Compare three years of each option, not the first invoice.
Custom software vs off-the-shelf at a glance
Off-the-shelf, or ready-made, software is one product sold to many companies, usually as a subscription. Custom software is built for one company's users and processes. The table compares the two on the points that decide the cost.
| Factor | Off-the-shelf | Custom |
|---|---|---|
| Upfront cost | Low: a setup fee or nothing | High: custom business software with us starts from $15,000, design and project management included |
| Time to start | Days | Custom business software: at least 6 weeks |
| Fit to your process | You adapt your work to the product | The product follows your process |
| Running cost | A fee per user or per month that grows with your team | Hosting, support and changes; a new user adds little |
| Integrations | The connectors the vendor offers | Systems whose APIs expose the data, actions, and limits your workflow needs, inside the build estimate |
| Who decides what changes | The vendor | You |
| Leaving | Limited to the data export the vendor offers | You keep the code and the data if the contract transfers them |
What off-the-shelf software really costs
The subscription is the part you see on day one. Other costs come later.
- Per-user fees that grow with your team. A price that looks small for 10 people is a different number for 80.
- Price changes at renewal. The vendor sets the price for the next term. Salesforce, for example, announced that it would raise list prices for the Enterprise and Unlimited Editions of Sales Cloud, Service Cloud and other products by an average of 6% on August 1, 2025.
- Add-ons and workarounds. Features outside your plan cost extra. Work the product cannot do moves into spreadsheets and manual copying between systems, and those hours are a cost even though nobody sends an invoice for them.
- AI features priced on top. The AI in a product you already pay for can be a separate line, charged per user like the product itself. Microsoft lists the Microsoft 365 Copilot add-on at $30 per user per month, paid yearly, and it requires a qualifying Microsoft 365 plan as well. For 25 people, that adds $9,000 a year, whether or not the team uses it.
- The cost of leaving. Your records, settings and automations live in the vendor's database. What you can take with you depends on the export the vendor offers.
One more risk does not show up on any invoice: the vendor decides the future of the product. Atlassian, for example, ended support for its Server products on February 15, 2024, and recommended that customers move to its Cloud or Data Center products. Teams that ran Jira Server or Confluence Server had to choose between a migration and software without support or bug fixes, on a date the vendor set.
What custom software costs to build and to run
Here are our own starting prices, so you have real figures to work with.
- Analysis phase: $1,000-$2,000, and takes at least 1 week. We write the user stories, check that the plan can be built, and give you a scope document with a budget and a timeline. You can skip it if your scope is already written down, or we can do the analysis while we design and build, inside the price of that work.
- Custom business software: from $15,000, and takes at least 6 weeks. An internal system such as a CRM, an HRM, document flow or an analytics dashboard, with the roles, the admin panel and the connections to your other tools it needs. Software at ERP scale starts from $60,000.
- A product you sell: from $5,000, and takes at least 2 weeks. That is a basic MVP for one platform. A complex product, such as a SaaS with tenants and plans or a marketplace, starts from $20,000 and 8 weeks.
- Already in every price: design, project management, testing and the third-party integrations the system needs.
Running costs start at launch, and they depend on the kind of support you choose. Our hosting service, with environments, releases and monitoring, starts from $200 a month, and a support package that adds bug fixes and regular updates for an app starts from $1,000 a month. Decide whether you need hosting alone or hosting plus a support package; the next section shows how much that choice changes the answer.
Custom software depends on outside vendors too, for payments, email or hosting. The difference is that the dependency sits in code you control. On Lainappi, a Finnish peer-to-peer rental app we built, the deep links (links that open a specific screen in the app) ran on Firebase Dynamic Links, a Google service that shut down on August 25, 2025. We moved deep linking to AppsFlyer as a separate module, and the switch shipped within days.
How to calculate the ROI of custom software
ROI compares what an option gives you with what it costs. For a build-or-buy decision, compare the full cost of both options over the same period, then add the gains that only one of them brings. Three years is a practical period: long enough to show whether a build pays back, short enough to plan.
- Three-year cost of buying: the fee per user, times the number of users, times 36 months, plus add-ons, paid connectors and the hours your team spends on workarounds.
- Three-year cost of building: the build price plus 36 months of hosting and support.
- Gains that only one option brings: manual work the new system removes and sales a feature makes possible.
- ROI of building: the cost of buying, plus the extra gains, minus the cost of building, divided by the cost of building.
Take an internal tool for 40 people. Assume the product you would buy costs $90 per user per month; this is an example figure, so replace it with your own quote. Over three years that comes to $129,600.
Now the custom version at our starting prices: $1,000 for the analysis phase and $15,000 for the tool as custom business software, with its design and project management, which is $16,000. For running the tool, take the hosting service at $200 a month plus the support package from $1,000 a month, which adds bug fixes and regular updates. Three years of both come to $43,200, and the three-year total is $59,200. The cloud bill is paid to the provider separately, so every custom total here is before the cloud bill.
Building costs $70,400 less over three years, an ROI of about 119% before the cloud bill and before you count any hours the tool saves. The build pays for itself in about 7 months: the yearly saving is $43,200 in subscription fees minus $14,400 for hosting and support, or $28,800, and $16,000 divided by $28,800 is about 0.56 years.
Two inputs change the result of this example: the number of users and the support model. The table below shows four team sizes, with hosting and the support package.
| Users | 3 years of subscription at $90 per user | 3 years of the custom tool, before the cloud bill | Difference |
|---|---|---|---|
| 5 | $16,200 | $59,200 | Buying costs $43,000 less |
| 25 | $81,000 | $59,200 | Building costs $21,800 less |
| 40 | $129,600 | $59,200 | Building costs $70,400 less |
| 80 | $259,200 | $59,200 | Building costs $200,000 less |
In this example the custom tool costs the same at every size; in practice hosting grows a little with use, but far more slowly than a fee per user. Hosting alone, without the support package, is the lower bound. It covers the infrastructure, not bug fixes or changes to the tool, so count on it only if your own team will fix and change the tool. Three years of hosting come to $7,200, and the custom tool costs $23,200. Building then costs less from about 8 users instead of about 19, and at 40 users it costs $106,400 less.
For the same calculation with real license quotes for one product type, see our guide to custom LMS development and its break-even point.
When off-the-shelf software is the right choice
Buy when the work runs the same way in your company as in other companies.
- Standard functions: accounting, payroll, email, a help desk or a simple CRM. Vendors spread the cost of these products across many customers; a custom build is paid for by one.
- A small team: per-user fees stay low. If the custom tool also needs the support package, a build pays back within three years only from about 19 users, so at 10 users buying is cheaper.
- You need it this month: a subscription works within days, and even simple custom business software takes at least 6 weeks.
- You are still testing the idea: a no-code tool, an AI app builder or a ready-made product can show whether people want the service before you pay for code. If a prototype built with AI tools starts to get real users, our AI-built app rescue service checks its security and makes it ready for production.
Advantages of custom web application development, and when they pay off
A custom web app is built around your process, keeps its features and data under your control, and costs little more with each new user. These advantages are worth the higher upfront price in five situations.

- The software is your product. If customers pay you for the software itself, as with a SaaS product or a marketplace, you need control over its features, its pricing and its data. A no-code builder sets limits on each of the three.
- Your process is how you compete. It may be a pricing rule, a booking flow or a dispatch method that competitors do not have. Ready-made products are built for the typical process, so yours would have to change to fit them.
- Per-user fees grow faster than value. In the example above, building costs less from about 19 users with hosting and a support package, and from about 8 users with hosting alone.
- You connect many systems. Each manual step between two products costs staff time every week. A custom system can exchange data with each of those products directly, if the product's API exposes the data and actions the workflow needs, with rate limits it can work within.
- You need control over data and security. Where the data is stored, who can reach it and how access is logged become your decisions instead of settings in someone else's product.
Each of these advantages has a price. You pay for the build before you see a return, and someone on your side has to own the product after launch. If none of the five situations applies to you, the advantages are real but small, and buying is the better use of the money.
The middle path: buy the standard parts, build the core
The examples below mix the two: custom code for the part that makes the business different, and bought services for the rest.

- UK Retreats. The company wanted to bring its social media followers into an online club for finding holiday stays. To fit the budget, we dropped the idea of a native mobile app plus a website and built a mobile-first web app. The map of stays and the subscription function were custom code, with Stripe for payments and subscriptions, Laravel Nova for the admin panel, Mailgun for email and Google Maps for the map. The MVP was ready within 3 months.
- OddsCrowd. A web app for a community of sports bettors, with a 4-month deadline. We built forecasts, ratings and odds comparison as custom code on Laravel and Vue.js with Nuxt. The content admin panel ran on WordPress, and game data came from an outside data service. The first version shipped in 14 weeks.
- Online stores. An online store with us starts from $6,000 and 3 weeks, whether it runs on Shopify or a similar hosted platform or on its own backend; the catalog, the checkout and the integrations set its estimate.
“Every custom product rests on bought services, and the design question is where your code ends and a bought service begins.”
Evgeny Leonov, CTO at Ronas IT
What to check before you sign, either way
Both lists below cover cost and how you would leave, with questions that fit each option.
Questions about an off-the-shelf product
- In what format can you export your data, and does the export include history, settings and files?
- How can the price change at renewal, and is it charged per user, per record or per use?
- What happens to your data if you stop paying?
- Does the vendor use your data to train its AI features, and can you switch that off?
- Which API limits apply to the integrations you need?
Questions about a custom build
- Where will the code and the cloud account live? Production runs in your own cloud account, and the repository is created in your organization; starting it in our GitLab is an exception, with the transfer in the contract.
- Which conditions does the estimate depend on? Our estimates come with a page that lists the proposed stack, the expected team and the third-party services, because the estimate is based on those conditions.
- How will the system be handed over if you take it in-house? We plan a structured handover of 2 to 4 weeks with knowledge transfer and deployment runbooks, the written step-by-step guides to deploying the system.
- What does support cover? Response times and scope are agreed in the support agreement.
- How does the team use AI agents? Ask who accepts the work agents produce, which AI services see your code and data, and whether the speed shows in the price. Our guide on how to choose a software development company covers what to ask about AI in more detail.
The rest of a development contract, from code ownership to the first 90 days of work, is covered in our guide to working with an outsourcing company.
How we help you decide between building and buying
On technical projects, the first call includes our CEO, an engineer. If buying suits you better, we say so on that call and suggest a product to look at instead of a build. A rough estimate is free. If the scope is not written down yet, the analysis phase gives you a budget and a timeline to put into the calculation above.
What to do next
- Write down what you pay now. Users, add-ons, paid connectors, and the hours your team spends moving data by hand.
- Run the three-year comparison. Use your own numbers, and run it with both support models.
- Mark the parts of your process that make you different. Those are the candidates for custom code; the rest can stay bought.
- Get an estimate for the custom part. Compare it with three years of what you pay today, not with the first year of a subscription.






