FOR BUSINESSES / CUSTOM SYSTEMS
What you expect from a software development company, talking to the person who builds it.
If you’re looking for a software development company to build a custom system, this is what I do: I design and build systems that connect processes, data, automation and AI around how your company works, and you always talk to the person building them.
02 / SIGNALS
Does any of this sound familiar?
None of these is a tool problem. It’s a fit problem: pieces that work on their own and a system nobody has designed.
That’s Digital Architect territory.
- 01Data spread across several tools that don’t talk to each other.
- 02Important processes that still live in Excel.
- 03A CRM or ERP that forces the team to change how it works.
- 04Reports someone puts together by hand every week.
- 05Databases with years of information nobody is using.
- 06A wish to bring in AI without creating yet another isolated tool.
- 07An application you need that doesn’t exist as a standard product.
03 / EVIDENCE
Companies that no longer fit a standard tool.
Documented case studies, no invented figures. Each one solves one of the problems above.
- Data · AI
AtalayaIQ
Seven years of a national events company’s operational data turned into a daily briefing, evidence-backed alerts and an assistant. Read-only, without migrating its system.
How seven years of data were put to work without touching the system - Software · Data
Zentia
One core for several real-estate agencies, each with its own brand, domain and data isolated in the database. A new agency doesn’t need a new product.
A platform serving several agencies without mixing their data - Software · Data · AI
Rocio.com
An archive going back to 1992, trapped in a WordPress site around 15 years old, migrated to its own platform with a normalised data model, an editorial panel and an AI assistant.
From a legacy WordPress site to a platform of its own - Software · Experiences
Event Tech
Physical-digital systems for pavilions at FITUR, MWC, ITB and WTM: video walls with live data, table bookings with NFC/QR and a networking web app.
Systems that have to work live, on a fixed date
04 / FIT
Building custom isn’t the answer to everything.
If a standard tool solves your problem well, I’ll tell you. Building only makes sense when the fit matters.
When building custom makes sense
- The process that sets you apart is exactly the one standard tools handle worst.
- The same data is entered several times and nobody trusts any of the copies.
- You have valuable data in a system that works, but you can’t query or combine it.
- You pay for several tools and the real work happens in the spreadsheets that connect them.
- You need AI to work on your data and inside your process, with clear limits.
When it doesn’t
- Your process is standard: accounting, payroll, email or invoicing are usually better served by a product.
- An existing tool covers what you need and the problem is configuration or training.
- You don’t know yet how you want to work: sort out the process first, build afterwards.
- Nobody will be able to use or maintain the system once it’s finished.
- All you’re after is to “add AI” without a specific problem behind it.
05 / BY NEED
If you already know where it hurts.
Specific needs, each with its own criteria for building or not, and its case studies.
- S.01 / CRMCustom CRM for businessesWhen the sales team works around the CRM instead of inside it.
- S.01 / INTERNALCustom web applicationWhen a spreadsheet, an inbox or one person holds up a critical process.
- S.01 / LEGACYLegacy system modernizationWhen the platform has been outgrown but holds years of data and links.
- S.02 / BICustom Business IntelligenceWhen the data exists but nobody agrees on what it means.
- S.02 / DASHBOARDSCustom KPI dashboardsWhen management needs answers every morning, not another screen of charts.
- S.03 / AUTOMATIONBusiness process automationWhen a repetitive task eats up hours and you already know how it should be done.
- S.03 / CHATBOTChatbot for businessesWhen the same questions arrive every day and the answer is already in your documents or your data.
- S.03 / CONSULTINGAI consultingWhen you want to know which processes suit AI before spending on it, and want the analysis to end in something running.
06 / WHAT TO EXPECT
What to expect from a software development company (and how I cover it).
Six things a business should demand from whoever builds its system, whatever their size.
- CONTACT
Direct contact. You talk to the person who designs and writes the system, not an account manager passing messages along.
- SCOPE
Clear scope and timelines. A small, useful first version with defined phases, instead of one big project delivered at the end.
- TEAM
Capacity when it’s needed. A small team of specialists joins the projects that need it, coordinated by whoever designs the architecture.
- OWNERSHIP
Ownership. The code, repository, credentials and data belong to your company from day one, in writing.
- DOCUMENTATION
A system others can understand: a documented data model, explained decisions and nothing that only works inside one person’s head.
- CONTINUITY
Continuity. Maintenance and evolution after launch, optional and with no lock-in.
07 / PROCESS
You bring the problem. I design and build the system.
You do not need to arrive with a solution, or know which technology you need.
- 01 — PROBLEM
What is not working, what costs too much, or what cannot be done today.
- 02 — DATA
What information exists, where it lives and what state it is in.
- 03 — CONSTRAINTS
Budget, deadlines, existing systems, team and regulation.
- 04 — OBJECTIVE
What has to happen for the system to be worth it.
- 05 — SYSTEM
I design and build the system, and keep supporting it after launch.
08 / IDEAS
Worth thinking about before deciding.
09 / QUESTIONS
Questions businesses ask before starting.
01Are you a software development company?
I work as a digital architect: I design the system and write the code myself, and bring in a small team of specialists when a project needs it. I cover what a business expects from a software development company (scope, timelines, code ownership, continuity) without sales layers in between.
02And compared with a software consultancy?
A software consultancy usually delivers analysis and recommendations, and someone else builds. Here recommending and building aren’t separated: whoever proposes the system answers for it working.
What is a Digital Architect?03Do we have to replace the tools we already use?
Not necessarily. What works is kept and connected: migrating is a decision, not a requirement. AtalayaIQ, for example, works on the database of the system the company already used, read-only.
Read the AtalayaIQ case study04What size of project fits?
Systems with a real problem behind them: platforms, internal tools, data layers or integrated AI. Large systems are planned in phases.
05Who owns the system once it’s finished?
Your company does. At the end you receive the repository and credentials: the code and the data are yours, and the system doesn’t tie you to a tool or a person.
06Do you work with companies outside Spain?
Yes. I’m based in Spain and work remotely with companies in other countries, in English or Spanish.
What does your business need to solve?
Tell me the problem, the data you have, the constraints and the goal. You don’t need to know yet what has to be built.