Custom software vs off-the-shelf: how to make the right call for your business

Custom software vs off-the-shelf is one of the questions I hear most often. Companies that come to me for custom software development in Adana, including foreign-owned firms and international teams with an office in Türkiye, tend to start from the same place: the Excel file no longer holds up, and the ready-made tools they tried cover part of the job but not all of it. At that point a wrong call is expensive in either direction.

The first thing I ask is this: is the process itself what sets you apart from your competitors? Accounting, payroll, email and calendars work much the same in every business. Writing software from scratch for those is usually money thrown away. But if the way you take orders, run your field team or price a job for a customer is your own, forcing that process into someone else's template costs you more over time.

I don't look down on ready-made software. Picked well, you can be using it within a few days, the vendor handles maintenance and security updates, and the upfront cost is low. I'd suggest starting with an off-the-shelf tool when:

• Your needs match most businesses in your sector: bookings, simple stock, basic bookkeeping, a CRM.
• You have few users and don't expect that number to grow soon.
• Your process hasn't settled yet, and you need to learn what you want by using something.
• The tool's reports and export options do the job.
• You don't need to move data into another system, or the tool's built-in integrations are enough.

That last point gets overlooked. The businesses that are happy with off-the-shelf software are usually the ones using the tool as it comes. Trouble starts when the team has to work around the tool every day to fit it to your process: typing the same data in two places, keeping some records in Excel anyway, building the missing report by hand. Those small losses don't show up on the invoice, but they do show up on the payroll.

When you trial a ready-made tool, fill the trial with a real week of work, not demo data. Pick two or three people who will use it every day, ask them to do all of that week's work in the tool, and have them note every piece of information they had to keep outside it. If the list is short at the end of the week, the tool will most likely be enough. If it's long, the items on that list make a good first draft of the scope for custom software.

Custom software costs more on day one. There's no point hiding that. The places where it earns its cost back usually fall under four headings:

1. 01

   A workflow that is your own

   If your approval steps, pricing rules or the split of work between field and office don't exist in ready-made tools, the team ends up working around the software instead of the other way round. With custom software, the screens and rules are drawn around how you operate.

2. 02

   Several systems that need to be connected

   Every place where data is carried by hand between e-invoicing (e-fatura), your accounting program, your website, the courier or a mobile app is a source of errors and lost time. A custom panel can pull these systems together in one place through their APIs.

3. 03

   Owning your data

   With a ready-made tool your data sits on the vendor's servers, and export is often limited. If the price changes or the service shuts down, moving away gets hard. With custom software the database is yours: you pull any report you want and take it wherever you want.

4. 04

   Per-user costs that keep growing

   Tools billed per person per month are a small line for a team of five. As the team and the number of branches grow, that line grows every year and never turns into something you own. With custom software, adding a user usually needs no extra license; the cost is hosting and maintenance.

If at least two of these four apply to you, I'd put custom software on the table as a serious option. If only one applies, it usually makes more sense to push the ready-made tool's settings and integration options first.

To me the most important row in that table is the risks row. The risk with off-the-shelf software sits outside your business and you can't control it. The risk with custom software sits mostly in the scope decisions at the start, which means good planning can shrink it.

FiloTakip, an app I built and that is live on the App Store, is a good way to show what a custom operations app looks like. It keeps vehicles, drivers, customers, jobs and loads, invoice and payment details, maintenance records, and fuel, mileage and expense logs in one place. Users sign in and see only the business data they are authorized for.

You could find a separate ready-made tool for each of those records: an expense app, a bookkeeping program, a maintenance spreadsheet. The real value is seeing on one screen which vehicle and which driver did a job for which customer, and where that job's invoice and payment stand. With a patchwork of tools you have to make that connection by hand every time.

For most businesses the healthiest route is a mix of the two. You leave your accounting program, your e-invoicing provider and your email setup as they are. On top, you add a small custom panel or mobile app that runs only the work that sets you apart, and that panel talks to the other systems through their APIs.

• What stays standard: accounting, payroll, email, file sharing.
• What gets built: order and job tracking, mobile screens for the field team, reports specific to you.
• The connection: the ready-made tools' APIs or regular data transfers.
• What you gain: a smaller first version, a lighter maintenance load, and the critical part of your data staying with you.

On projects I usually go in this order: first we list what the existing tools do well, then we map the gaps, and last we define the smallest piece of custom software that fills those gaps. On the Seleucia Trade project we used a ready-made headless CMS, Strapi, for content management and built a custom Next.js front end on top of it, which cut content update cycles by 40 percent. It's a good example of a ready-made part and a custom part working together.

For the first version of a custom panel or internal tool, the starting range is around 120.000 – 500.000 TL, excluding VAT (KDV). Where you land in that range depends on the number of roles and permissions, the integrations, whether you need a mobile app, and how complex the reports are. After launch, I'd set aside roughly 15–20% of the build cost per year for maintenance, updates and servers.

The most effective way to bring the cost down is to keep the first version small. Instead of building everything at once, pick the single process that wastes the most time and solve that. It lowers the risk and shows you early whether the team takes to the software.

It doesn't matter whether you're in Adana or another city; I work remotely and run projects through video calls and regular demos. In a free discovery call we go through your current tools and repeated tasks, and work out together whether off-the-shelf, custom or a mix makes sense. If a ready-made tool is the right answer, I'll tell you that too.