We take your product at whatever stage it is.From an idea to a system with years in production.
An idea with no code yet, a project the previous vendor left half done, an app that keeps crashing or two systems that don't talk to each other. We step in where it is, tell you what is worth doing and do it in stages.
How it works
- 1A 20-minute call. Tell us what you need or what is failing. If we can't help, we'll say so.
- 2If there is code, we review it and give you, in writing, what to fix first and what can stay as it is. If it's an idea, we define the first version together.
- 3We build or fix in stages, with scope and price agreed before each one. What already works keeps working in the meantime.
We design, finish, fix and connect your product.
Our work
We don't have a wall of logos. We have products you can see working, and we tell you what we decided and what we gave up on each one.
Client · Equitechverse·In production
Smarty Bloodstock
A tool for racehorse buyers: three sale houses' catalogs in one place, natural-language questions with every figure backed by data, voice notes and comparisons, on the phone in the buyer's hand. We designed and built it for Equitechverse: from idea to production in five months.
- Installable web app
- Every figure backed
- Payments
- Voice notes
How we built Smarty Bloodstock →Illustrative demo · example horses and figuresClient·In development
Mobitraxx
Mobitraxx's security patrol platform: two Android apps with years in operation, used daily by guards, which we are rebuilding on a shared foundation so they arrive as an update, without stopping the operation: a light and a full version, with checkpoint readings in the field and the flows people already know.
- Mobile
- Modernization
- Field hardware
How we are rebuilding Mobitraxx →Version in development · example data
What we work on
Three ways to work together, depending on where your product stands.
- 1
New products
Web or mobile, from the first flow to the release in the stores.
If it's a mobile app, we build the MVP at no cost until you see it working. And in production we back it in writing: 99.5% crash-free sessions and a 4.0★ store floor.
- 2
Apps and products that already exist
Apps that crash, slow screens, code no one on the team understands or a build left half done. We find the cause, fix it and leave the code in shape for any team to carry on.
Like Mobitraxx: two apps with years of use that we are rebuilding so they arrive as an update, without stopping the operation.
- 3
Systems integration
Your ERP, your CRM, a spreadsheet and an app that don't connect, and someone copying data by hand. We connect them so each piece of data is entered once. If a language model adds something measurable, we use it; if not, we don't.
As in Smarty: three different sources in one database, and every figure the product answers comes from there.
What we promise you
We work the same way on every product, with a way of doing things refined project after project. That's why we can promise you three things.
You'll never have to ask how it's going.
The project status is always in view: what's done, what's missing and what's blocked.
You'll never depend on someone remembering.
Every important decision is written down, with the alternatives we discarded and why.
You'll never be stuck.
The code, the accounts and the documentation are yours from day one. Any team can carry on tomorrow.
- 1
We understand your problem
20 minutes. What you need to solve, for whom, and what happens if it isn't solved. We tell you whether we can help and where we'd start.
- 2
We review what's there
If there is code, we read it and see how it behaves today; if it's an idea, we define the first version. Either way, we agree on the scope and acceptance criteria of the first stage before starting.
- 3
We build and launch
Every release goes through QA before production. Nothing ships without you having seen it.
- 4
We answer in production
During the warranty we measure what happens in production and fix what needs fixing. After that, if you want, we keep going with what matters.
Frequently asked questions
Yes, that's the usual case. The first conversation is for understanding the problem; the first stage, for validating what matters most before building the rest.
In stages, with scope and price agreed before each one starts. We don't sell hours. If it's a mobile app, the first MVP is free: we build it at our cost and you go on only if it convinces you.
For mobile apps we put it in writing: 99.5% crash-free sessions in the first 90 days and a 4.0★ store floor; if we fall short, we keep fixing at no cost. For everything else, we agree acceptance criteria and a warranty period before starting.
Yes. We can review the code before you decide anything, take on part of the work or replace the vendor when their contract ends. If you have an in-house team, we work in their repository and by their rules.
It's not what we usually recommend. Rebuilding from scratch costs more and takes longer than it seems, and meanwhile the current product is still in use. We propose it only when fixing costs more, and we show you why.
If it's an idea, a conversation about the problem and who has it. If there is a product, read access to the code and, if they exist, to the store and server accounts. If documentation is missing, we write it from the code.
You do, from the moment you sign. Store, cloud and domain accounts are in your name. We use standard technology and leave everything written down so any team can continue.
Everything needed to carry on without us: how it's built, why it's built that way and where it stands. In the same repository as the code.
The warranty period starts: we measure what happens in production and fix what needs fixing. After that, if you want, we keep evolving the product in stages.
If it solves something measurable and there's real data to work with, yes. If not, we tell you and propose something simpler. And when we use it, it never invents figures: every answer rests on your data.
Let's talk about your project
Tell us where your product stands and what you need. You don't need to know why something is failing.