When Is an Existing SaaS Preferable to Custom Development?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

GitHub · LinkedIn.

Published: · Last technical review:

An existing SaaS can fit if its features address your operations and you accept its terms. Custom development warrants review when you need to define specific behaviours. I suggest comparing the work each alternative resolves, what is left out, and the necessary agreements, without taking the ownership model for granted.

I compare the alternatives with neutral criteria, without attributing universal advantages or performance figures. The conditions of each specific product need to be verified separately.

Criteria: compare the fit, not just the label

SaaS and custom development describe different models, but neither resolves your need on its own. To compare them, I suggest writing down what work the tool must enable and what aspects of your operations you cannot change. That list is more useful than declaring in advance that you need proprietary software.

The following table proposes questions to compare an existing tool with a potential development. It does not attribute conditions to any provider. It distinguishes what is available from what would need to be defined and verified before considering the commission resolved.

Decision criterion Existing SaaS: conditions to verify Custom web development or PWA (from €3,500 + VAT*)
Operational fit You adapt to the workflows, records, and roles already offered by the product We define the specific screens, roles, and workflows of your business in writing
Code ownership and delivery Consult provider conditions; do not infer delivery or assignment Code ownership or usage licence agreed in writing on a case-by-case basis
New features Available only if stated in product terms; customisations to be confirmed Quoted and planned according to the needs of your business
Hosting and operation Modality and responsibilities to be confirmed with the provider You can arrange your own hosting or have me manage it
When it suits you Your operations fit what the product already resolves today You need your own processes, specific rules, or custom code terms

I do not take for granted that one option will be cheaper, faster, or safer. To make such a claim about your situation, I would need to review specific alternatives. The aim of the table is to make questions visible, not to grant a universal advantage to one of the models.

How to separate the usage model from the code agreement

Using an existing tool and commissioning a new one are decisions distinct from the ownership agreement. I suggest asking what you can use, what you would receive, and what terms you would need to accept. I do not attribute an assignment, an export, or a customisation capability to a provider that has not confirmed those conditions.

For applications and other software developments, my published condition is to agree on ownership or usage licensing on a case-by-case basis. That phrase does not define a universal contract. If you need to have the code, describe that before finalising the scope so that we can review the specific agreement.

I would also separate available features from those advertised as possible. As a comparison criterion, note down what you can verify today and what requires a subsequent decision. An expectation regarding a product's roadmap should not turn into a contracted deliverable by default.

You can keep the decision open while that information is missing. A general comparison serves to formulate questions, not to declare a winning option without understanding its fit. If you already have an application, reviewing it is another alternative that warrants consideration before assuming its replacement is necessary.

Having a unique need does not determine ownership

You might need a behaviour you cannot find in an existing tool. That justifies reviewing potential development, but it does not allow deducing who will own the code. My published condition for applications and other software developments is to agree on ownership or usage licensing on a case-by-case basis.

In the same way, «proprietary» or «own» should not act as a reassuring word without substance. As a commissioning criterion, I suggest replacing it with specific questions: what you receive, what you can use, and what terms must be agreed. I do not offer universal contractual answers to questions we have not yet defined.

Limits: when custom development from scratch is NOT right for you

It is not advisable to request new development solely to avoid using an existing product if you have not yet identified a specific mismatch. First, describe what behaviour you are missing. If your need fits into a tool you accept, comparing its fit is a reasonable alternative; it is not an inferior option by definition.

Nor is it advisable to choose a SaaS assuming that any customisation will be included. Before subscribing to a SaaS, check which features already exist in production and do not assume bespoke adaptations that do not appear in the contract are included. I do not take adaptations, exports, or integrations for granted without verifying the terms of the specific alternative.

If you already have an application running, consider another alternative: reviewing what exists before planning its replacement. My offering includes maintenance and evolution of PHP/MySQL applications. That does not mean maintaining is always the right path, but rather that the decision deserves a review rather than an automatic conclusion.

An example decision without inventing terms

Imagine you need to log a task and subsequently review its status. You can describe that workflow without mentioning any brand. Then compare where it fits just as you need it, and where it forces you to alter a significant part of your operations.

If an alternative leaves a question mark, do not fill it with a promise like «it can surely be done». Note down the question and who needs to answer it. That exercise serves both for evaluating a product and for explaining a development; it avoids confusing a technical possibility with a contracted service.

I would bring a short checklist to the conversation:

When preparing your inquiry, note down what deliverables you need, what code ownership or licensing agreement you seek, and, if you already have a PHP/MySQL application, whether you prefer to evaluate its maintenance and evolution first. The self-assessment guides your inquiry; it neither compares vendor contracts nor decides what you should purchase.

How to clarify which model fits your business

If you are undecided between using a product in a service model or commissioning a custom application, write to me explaining what process you want to resolve. I will reply within 24-48 business hours with an initial written assessment.

When the right path is custom development (from €3,500 + VAT*) or the evolution of an existing PHP application (maintenance from €60/month + VAT*), we set out the deliverables, code ownership or licensing, timeframe, and quote in writing before starting.

Frequently asked questions

Does a SaaS include code delivery?

Do not infer it from the SaaS label. Review the product terms and state explicitly what you need to receive or use. This article does not attribute an assignment or code delivery to any vendor. To compare with custom development, separate functional fit from the ownership or licensing agreement you need.

What is agreed in custom development?

For applications and other software developments, I agree on ownership or licensing with you on a project-by-project basis. We also define deliverables, timeframe, and budget in writing before starting development. I do not turn that condition into a universal assignment or a rigid contract template: I need to review your requirement and set out the specific agreement in writing.

Web applications and PWAs

Web applications and PWAs

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.