# Custom software for SMEs: when it pays off and how to validate it before investing

> When it makes sense to build your own application instead of adapting generic software, which applications are most common and how to validate the idea before investing.

[Home](https://alphaimpact.pt/en/) › [Guides](https://alphaimpact.pt/en/guias/) › Custom software for SMEs

Page: https://alphaimpact.pt/en/guias/software-a-medida-para-pme · Updated: 2026-10-27

A custom application pays off when generic software forces the company to change its process to fit the tool, or when the work lives in spreadsheets nobody controls any more. Before investing, it is worth mapping the process and checking there is no program that already solves almost everything.

## What makes a custom application different from generic software?

Generic software serves many companies at once, and each one adapts to it. A custom application is designed for one company's process: the fields, the steps and the permissions are its own.

It can be a web application, a mobile app or a connection between systems that already exist.

## When does it make sense?

- The process is specific and no program covers it without workarounds.
- Several separate tools force people to copy data between them.
- Customers or field teams need an app of their own.
- The way the company works is part of what sets it apart from the competition.

## Which applications are most common?

- Internal management of orders, tasks, stock or production, in one place.
- Customer portals, with a private area for requests, documents and statuses.
- Maintenance, downtime and quality management across several plants, as in the Industrial Manager case.
- Mobile apps, for field teams or for customers, such as 11gest and the Industrial Manager iPhone app.
- Connections between the ERP, email and other tools, so data stops being copied by hand.

## How do you validate the idea before investing?

1. Describe the process as it is today, step by step, with who does it and where time is lost.
2. Check whether there is software that solves almost everything. If there is, configuring it usually costs less than building.
3. Choose the first useful version: the minimum that already takes work off someone.
4. Agree how the result will be measured before starting.

## What does it cost and how is it paid?

The cost depends on the number of screens, the connections to other systems and where the application is hosted.

We split the work into deliverables, each with a scope, a deadline and a fixed price, written in the proposal. Hosting and maintenance are quoted separately.

## What is the most common mistake?

Starting with the technology instead of the problem. The right question is not which language to use, but which task stops being done by hand and who benefits.

## Frequently asked questions

### Can I start with a simple version and grow later?

Yes, and that is what we recommend. Each deliverable works on its own and the next one builds on the previous.

### Does the application work on mobile?

Web applications adapt to mobile. When an iOS app makes sense, it is published on the App Store.

### What if I need changes after launch?

Fixes and improvements are agreed in the proposal. New changes are quoted separately, also at a fixed price.

## See also

- [Custom software and apps](https://alphaimpact.pt/en/solucoes/software-e-apps-a-medida)
- Case [Industrial Manager](https://alphaimpact.pt/en/casos/industrial-manager)
- Case [11gest](https://alphaimpact.pt/en/casos/11gest)

---

Alpha Impact, Lda, Lisboa, Portugal · Company no. (NIPC) 516881590 · info@alphaimpact.pt · +351 916 464 768 · First step: a 30-minute call, free of charge.