Custom software
Custom software development in Spain
In short
Custom software pays off when the way you work is what sets you apart, when off-the-shelf tools leave you living in spreadsheets, or when your systems do not talk to each other. At SME Analytica we build it inside your operation, connected to your ERP, CRM or spreadsheets, and the code is yours.
Custom or off-the-shelf?
The short answer: off-the-shelf first, and custom only for what has no substitute.
Situation: Standard accounting, payroll or invoicing
- Best option
- Off-the-shelf
- Why
- These are common, regulated processes. A good product already handles them and keeps up with the rules.
Situation: The product covers almost everything and the rest lives in spreadsheets
- Best option
- Off-the-shelf plus integration
- Why
- Connecting and automating the gap usually costs less than switching systems.
Situation: Several systems that do not talk and data copied by hand
- Best option
- Custom integration
- Why
- The value is in data moving on its own between what you already use, not in replacing it.
Situation: A process of your own that sets you apart and no product fits
- Best option
- Custom
- Why
- Bending your way of working to a generic product would remove exactly what makes you different.
Situation: An older system that cannot be stopped
- Best option
- Piece-by-piece modernisation
- Why
- Data and functions are moved out gradually while the system keeps running.
If the Recon shows that an off-the-shelf product solves your case, we will tell you.
Built on what you already run
Connected to your ERP and CRM
The new software reads from and writes to the systems you already use, without asking you to switch tools.
Spreadsheets, for as long as needed
If the team lives in spreadsheets, the system can read from them and write results back during the transition.
Users, permissions and a record
Each person sees what they need, and there is a record of what the system does.
AI only where it pays off
Classifying, extracting or summarising, when it improves the result and always with human review.
The code is yours
In your repository
The code and the data belong to the client. We work in your repository or hand it over at the end.
Documented
So another team, yours or an outside one, can maintain it.
No lock-in
You can keep it running with us, through Mission Control, or with anyone you choose.
How long until something is in production
It starts with a fixed-price Recon: we map the process, the data and the systems, and you leave with a plan and a fixed price.
Then a Launch of 3 to 4 weeks builds and integrates the first useful slice and ends in production, with 50% at the start and 50% when it goes live. What comes next is planned stage by stage, with what was learned.
From Valencia, across Spain
We are based in Valencia and work in Spanish and English. We come to your offices when the process calls for it, and the rest is done remotely, including for teams elsewhere in Spain.
Frequently asked questions
- When do you not recommend custom software?
- When an off-the-shelf product already handles the process, such as accounting or payroll. Then the useful work is usually integrating it with everything else, not replacing it.
- Who owns the code?
- The client. We work in your repository or hand it over documented, so you can maintain it with us or with another team.
- How long until the first version is in production?
- After the Recon, a Launch takes 3 to 4 weeks and ends in production with the first useful slice of the system.
- Can you work with our current ERP?
- Almost always, if it has an API, an accessible database or exports. We confirm it in the Recon, before committing to anything.
- How much does it cost?
- Each stage has a fixed price. We do not publish rates because every job is sized in the Recon, which is credited if we go on to the Launch.
- Does everything involve artificial intelligence?
- No. Most of it is software, integration and data. AI comes in only where it improves the result.
Keep reading
- Do you need Palantir?
A data platform, or integrating what you already have: an honest table for deciding before you spend on licences.
- What is a data ontology
The objects, links and actions of your operation, with examples, and how to build one on what you already run.
- Subcontracting for integrators
What we take on inside an integrator’s project, how it is contracted and how we protect their client relationship.
- Public sector
Legacy systems, unified data and citizen-facing apps, delivered through integrators and framework agreements.
Start with a Recon.
We map the process, the data and the systems. You leave with a plan and a fixed price, and if we carry on, it is credited against the Launch.
Book a Recon