Guide25 September 202611 min read
How to choose your first AI project: the impact and effort method
A four-step method for your SME to choose one AI use case: task inventory, criteria, impact and effort matrix, and scoring.

Software development
Mobile and web applications built around the way you work. When no tool on the market fits, the alternative isn't to change your process: it's to build the tool.
In a nutshell
You've asked for quotes for an app and everyone has said yes. We start with a different question: are you sure it needs building? Custom software is expensive to make, expensive to keep running and only understood by whoever wrote it. When your process is the same as everyone else's, the off-the-shelf tool wins. When your process is exactly what sets you apart, no tool will do. This service is for the second case.
We start by ruling things out. If what you need is invoicing, booking appointments, running an ordinary warehouse or filing job sheets, that already exists. And an off-the-shelf tool has three advantages a custom build won't give you: it costs less, people other than you have already tested it, and when a bug appears its maker fixes it while you sleep. We earn more by building. Even so, we'll tell you to buy it, because a project that shouldn't have happened ends badly for both sides: you pay for maintenance you didn't want and we keep alive something nobody opens.
In three situations. First: the process is your advantage. You do something in a way your competitors find hard to copy, and squeezing it into an off-the-shelf program forces you to do it like everyone else. Second: the cost is in the seams. Not in each program on its own, but in the person acting as the bridge, copying from one screen to another. If connecting what you already have fixes that, it's systems integration and it costs less; if what's missing is the piece that should sit in the middle and nobody sells it, it has to be written. Third: your case simply isn't catered for. It happens in narrow sectors such as customs, haulage or agriculture, where nobody has built what you need.
When you ask for an app you usually picture an icon on a phone. Sometimes that's right: if your people work without signal, or need the camera, GPS or notifications that arrive with the phone locked, it has to be a native app. But another question comes first: will anyone install it? A customer who buys from you twice a year won't download anything. There, a website that works well on a phone, or a conversation over messaging, reaches further, because that's where people already are: 94.7% of Spain's population used instant messaging, against an EU average of 82.3%. Your own team is different: what gets used every day does get installed.
We never start with the whole system. We pick the piece that repeats most often in your day and build that, even if it looks small next to what you had in mind. You feel the difference sooner and it tells you early on whether this is heading the right way. And before writing code, the prototype: clickable screens, with your data and your names, so you can say "there's a field missing here" while changing it means moving a box, not rewriting half the app. This isn't just for big companies: 54.4% of Spanish companies have no employees at all, and there, custom work only pays off if it starts small.
The code is written in your repository, under your account, from day one. We don't hand it over at the end like someone returning a deposit. The same goes for whatever needs contracting underneath, the server, the database or outgoing email: the accounts are in your name and you pay for them. The exit plan is agreed at the start, while we're still on good terms: where the code is, how it's deployed and what another team needs to pick it up and carry on. Ask everyone who sends you a proposal, not just us. If someone won't put it in writing before starting, ask yourself why.
Nothing ends the day it goes live. Apple and Google change the rules of their stores and operating systems, and an app nobody touches stops installing on its own. The libraries it's built with publish security patches that need applying. Your business changes and the case nobody mentioned turns up. And the law moves: if your app issues invoices, mandatory business-to-business e-invoicing has already been published in Spain's Official State Gazette (BOE), and your software has to keep up. That's why the quote has two parts, building and keeping it running, and we show you both before you sign. Tell us about your case and we'll tell you whether we can do it, how we'd approach it and what it would cost. If it isn't for us, we'll tell you that too.
SourceBOE (Spanish Official State Gazette), Royal Decree 238/2026 on e-invoicing
A tool designed around the way you work, not the way everyone else works. Tick what you need, send it to us and we'll prepare your quote.
Open the dossierCan't see yours? Ask us
Look at what you've tried. If you've seen several programs and they all do what you need under another name, yours is standard: buy it. If they all fail at the same point, because the piece of data your business depends on doesn't fit in any field, there's something that hasn't been built. If you're unsure, that's what the audit is for.
Yes. It's written in your repository from day one, and the accounts for any services that need contracting are in your name. If tomorrow you decide to carry on with another team, they take the code and the documentation, without asking our permission or paying a ransom for them.
We won't give you a date before we know what's inside, and be wary of anyone who gives you one on the first call. What we do give you is the order: first the prototype you can click through, then the piece that repeats most in your day, and from there you decide, having seen the previous step working.
No, and if you think you have, the prototype will probably prove otherwise. What is needed is someone on your side who can make decisions and has a little time to look at what we show them. The project that stalls isn't the difficult one: it's the one where nobody replies.
Cases by sector, regulation and how to decide. Everything we have written is on the blog and in the guides.
Guide25 September 202611 min read
A four-step method for your SME to choose one AI use case: task inventory, criteria, impact and effort matrix, and scoring.
Custom development2 August 20267 min read
Custom software development in Algeciras: when it pays to commission your own software, the five questions to ask the developer and the warning signs.
App Development12 June 20268 min read
How much it costs to develop an app for your business: the four project levels, what drives the budget up and when a web app is enough.
SEO and GEO27 October 20267 min read
How to appear in ChatGPT, Perplexity and AI Overviews: what you don't need to pay for, what OpenAI and Google say, and steps to become a cited source.
Hardly any project is just one thing: a website needs an agent behind it, and that agent needs to talk to your management software.
Business dashboardsBusiness dashboards that update themselves from your CRM, invoicing and till. A few indicators, the ones that change a decision. Nothing by hand.
CRM and business managementCRM for small businesses: an off-the-shelf one set up properly, ours, or a custom build. First we tell you which of the three you really need.
Web developmentCustom web development near Gibraltar and Sotogrande, with AI built in: corporate sites, catalogues, portals and shops. Domain and code in your name.Tell us which tasks take up most of your time. We will tell you whether they can be automated and how we would do it. If we can't help, we will tell you that too.