What are off-the-shelf software, SaaS, low-code, and custom software?
- Off-the-shelf software. A licensed product developed for needs shared by many companies: accounting applications, ERPs, and CRMs. It can be customized with extra fields, reports, or extensions, but its underlying logic and roadmap remain with the provider.
- SaaS (software as a service). Off-the-shelf software provided by subscription and running on the provider's servers. The provider handles installation and updates; when the subscription ends, access ends too.
- Low-code platform. Lets you build screens, forms, and workflows with visual tools and little code. You design the application; it runs on the platform.
- Custom software. Software designed and developed for a company's own process. You own the code and data if the contract specifies this.
What does “özel yazılım” mean here?
The Turkish term “özel yazılım” has two meanings. Here it means software developed specifically for a business—in English, custom or bespoke software. In a licensing context, the same Turkish term can refer to closed-source (proprietary) software, as opposed to open-source or free software; in that sense, most off-the-shelf products also qualify.
When is off-the-shelf software the right choice?
If many companies share the same need and adapting your process to the product loses nothing important, off-the-shelf software is the right choice. Strong signals include:
- The process is standard. In accounting, payroll, leave tracking, or standard sales tracking (CRM), rules vary little between companies. Rewriting them spends budget on work that does not distinguish you from competitors.
- Regulations change frequently. In areas such as e-Invoice, e-Archive, and payroll, following legal changes and incorporating them into the product is the provider's job.
- Few users, limited budget. For a team of a few people, a subscription is often cheaper than developing and operating a custom product.
- You need a solution now. A product that can be deployed quickly may be more appropriate than waiting through months of development.
- The process is not yet settled. Using an off-the-shelf product to learn what you need clarifies the scope of future custom software.
Before choosing, try the product with your own data and your three most common tasks; differences emerge in your exceptions, not in the sales demonstration.
When does custom software make sense?
Custom software makes sense when your process does not fit an off-the-shelf product's assumptions and that mismatch costs time or revenue every day. Typical signals:
- Your process is a competitive differentiator. If pricing rules, ordering flows, or your service model set you apart, forcing them into the product everyone else uses erodes that distinction.
- The work combines several systems. If an order touches ERP, warehouse, shipping, and banking, the real need is a layer connecting them into one flow.
- Users are outside your company. Dealers, suppliers, and corporate customers expect a simple interface that works according to your rules.
- Temporary workarounds have become permanent. If a product's gap is bridged every day through Excel exports, email, or manual work, the missing part is really the process itself. We discuss this in our guide to moving from Excel to an operations platform.
- Licensing grows with user count. When hundreds of dealers or field users are added, per-user licensing can become one of the largest items in a 3–5-year calculation.
The trade-off for custom software is clear: initial investment is usually higher, maintenance is your responsibility, and business teams must contribute time regularly. Our process begins with 1–2 weeks of discovery; the jointly scoped first release is planned to go live within 6–12 weeks, while larger programs advance in stages. Scope and delivery conditions are on our custom software development service page.
A third route: ready-made core, custom layer
For B2B companies, the most balanced answer is often a combination. Standard work such as accounting, stock, and invoicing stays in an off-the-shelf ERP; the distinctive business flow lives in a custom layer alongside it. That layer might be a dealer portal, operations screen, or field app.
ERP or custom software?
In most cases, this is not the right question. Replacing an ERP is lengthy and risky; rewriting what it already does well is unnecessary. A sounder approach keeps the ERP as the system of record and connects the custom layer to it. Three rules matter:
- Give each data type one master source: prices and accounts in ERP, order drafts in the portal.
- Establish the connection method from the start: API, web service, database view, or file transfer only.
- During brief ERP outages, operations should wait in a queue rather than be lost.
Before choosing a hybrid approach, verify one critical flow: reading a dealer-specific price, writing an order to ERP, and returning a rejected order to its owner. The existence of an API does not prove that the required fields and operations are enabled in that installation. For example, Business Central's official API documentation distinguishes standard and custom endpoints. Check the ERP version, permissions, and license limits in your own environment (checked: 13 October 2026).
If this small trial fails, first consider the existing product's configuration or extension options. If a custom layer is chosen, document who will test the connection after core updates and who will handle mapping if the ERP is replaced. Evaluate data flow using the table in the ERP integration plan, and dealer screens using the B2B portal guide together.
When are low-code platforms sufficient?
They are a quick, reasonable route for internal forms, simple approval workflows, low-user-count tools, and testing an idea. Limits emerge in three areas: complex business rules, large numbers of external users on per-user licensed platforms, and exit. Application logic often cannot move outside the platform; leaving may require a rewrite. Ask how data and workflows can be exported before choosing.
Comparing the three routes and 3–5-year costs
The main differences can be summarized as follows:
| Criterion | Off-the-shelf / SaaS | Ready-made core + custom layer | Custom software |
|---|---|---|---|
| Starting point | Setup and configuration | Core is ready; layer is developed | Discovery, design, and development |
| Process fit | Process adapts to product | Standard work fits the product; distinctive flow fits your business | Product designed around your process |
| Cost structure | Ongoing per-user or per-module licensing | Licensing + development and maintenance of the layer | Development investment + maintenance and hosting |
| Code and data | Data is yours; code and platform belong to the provider | Core with provider, layer with you | Code and data belong to you according to the contract |
| Update | Handled by provider; your configurations are tested on every release | Core with provider, layer with you | Your responsibility or your team's |
| Outflow | Depends on data export | Layer can be retained; connection and data mapping to the new core must be redone | Code, infrastructure, and documentation handover |
Do not assess total cost of ownership using only the first-year bill. For each option, fill in the following items for 3–5 years using your own quotes; use the same currency and price date, state whether VAT is included, and specify user counts by year.
- License or subscription: per-user and per-module charges, price-increase conditions, user counts in years 3 and 5.
- Customization and development: configuration, reports, and extensions for off-the-shelf products; discovery, design, and development for custom software.
- Integration: is there an existing connector, or must each connection be developed separately?
- Hosting and maintenance: servers, monitoring, backups, security updates; for off-the-shelf products, retesting customizations with every release.
- Training and rollout: user training, data migration, and the internal team's time during the process.
- Exit: data migration and the transition period when the contract ends or the product changes.
Your user count and integrations—not general averages—determine the weight of these items.
Data, exit, and Türkiye-specific issues
Who keeps the data in SaaS?
Under SaaS contracts, data generally belongs to the customer; the real question is how you get it back. Clarify in writing before signing: the export format, whether attachments are included, how many days access continues after the contract ends, whether a bulk export API exists, and how deletion is confirmed. With custom software, source code, hosting accounts, and documentation should be assigned to you in the contract.
e-Invoice, local ERP, and KVKK
- e-Invoice and e-Archive: Do not try to generate these documents from scratch. GİB-authorized service providers and accounting/ERP products with these connections built in track regulatory changes on your behalf; the custom layer issues invoices through them.
- Local ERP: The version and connection methods of your ERP directly determine the custom layer's scope; clarify them first.
- KVKK: If personal data will be stored on servers abroad, the cross-border transfer rules of Law No. 6698 apply. For off-the-shelf products, ask where data is hosted and about the provider's obligations as processor; for custom software, you choose the hosting location.
10 decision questions and a hypothetical example
Answer separately for each process; in the same company, one task may fit an off-the-shelf product and another custom software. Do not total the answers as a score: one strong answer can determine the decision.
Decision checklist
- Does this process distinguish you from competitors?
- Have you tried off-the-shelf products with your own data and found your main flow does not fit?
- Does the flow combine several systems—ERP, warehouse, shipping, banking?
- Are a significant proportion of users external: dealers, suppliers, customers?
- As user count increases, does licensing become one of the largest items in a 3–5-year calculation?
- Are product gaps currently bridged through Excel, email, or manual transfers?
- Do you need to decide which features are added and when?
- Is the process outside an area with frequent regulatory changes, such as e-Invoice, payroll, or tax?
- Is there a product owner and maintenance budget to take responsibility after launch?
- For a scoped first release, is it possible to wait 6–12 weeks?
“Yes” to the first seven questions points toward a custom layer or custom software. If any of the final three answers is “no,” starting with an off-the-shelf product or waiting may be more appropriate.
Hypothetical example: a distributor with a dealer network
Consider a distributor working with 300 dealers. Accounting, stock, and invoicing run in a local ERP; e-Invoices go through an authorized service provider. Dealer orders arrive by phone and representatives enter them manually into ERP. Prices vary by dealer group, promotion, and payment terms. Management wants a CRM for sales and an ordering system for dealers. Applying the questions process by process:
- Accounting and invoicing: Question 8 is “no.” The ERP and service provider stay in place.
- Customer tracking for sales: The process is standard and users are internal. An off-the-shelf CRM is sufficient.
- Dealer ordering: Questions 1, 3, 4, 5, and 6 are “yes”: pricing rules are company-specific, users are external, and per-dealer licensing is costly at scale. With a product owner and budget, a custom dealer portal reading prices and accounts from ERP makes sense.
Under these assumptions, the candidate solution is two off-the-shelf products and one custom layer; a ready-made portal trial and integration check may change this decision. The first release starts with a pilot dealer group rather than every dealer, focusing on the most frequent tasks—repeat ordering and account details. See how such a portal might look in Dealer Ordering Platform product concept; X Dağıtım in the concept is a fictitious company.
We can answer these questions together for your own processes in the first conversation.