End-to-end product development
One idea, one person, and something published at the end. No meetings to translate between specialists.
I have eight of my own apps on the App Store and Google Play, and on every one I did everything: decided what made the cut, designed the screens, wrote the calculation engine, set up the data and fought through Apple review. That is what I am offering here.
For a small project or a first product, splitting the work between a designer, a frontend dev, a backend dev and someone on infrastructure generates more coordination than progress. One person with judgement across all four layers moves faster and decides better, because they pay for the consequences themselves.
What's included
Product definition
What it does, who for, and what is essential in version one. Most of the budget is decided here.
Design and flows
Screens, navigation and interaction. You do not need to arrive with the design done.
All the development
Mobile or web app, backend, database and integrations. One person end to end.
Tested business logic
If the product calculates something that matters, the calculation engine ships with tests. That is what I did in MiFiniquito and mihipoteca.
Publishing
Deployment, domain, app stores and all the paperwork: certificates, listings, screenshots and privacy policies.
Maintenance
Fixes, updates and keeping up with the requirements the platforms change every year.
How we work
- 01
A conversation about the idea
What problem it solves and for whom. If I think it does not, I will say so on that call.
- 02
Cutting the scope
We usually halve the feature list. It is the step that saves the most money and the hardest one to accept.
- 03
Versions from week one
Something installable or visitable early and often, so you decide on the real product rather than a document.
- 04
Publishing and handover
I leave it published, documented and with the code in your repository.
Stack
- React Native
- Expo
- Astro
- React
- TypeScript
- Java / Spring Boot
- Node.js
- PostgreSQL
- Docker
- AWS
- Vercel
Frequently asked questions
How much does it cost to ship a product?
Entirely down to the scope of version one. A product focused on doing one thing well is weeks; with user accounts, payments, sync and an admin panel it is months. The first call exists to place your case on that scale.
Is depending on one person not a risk?
It is a real drawback and worth saying out loud. I offset it by putting the code in your repository from day one, with tests and documentation, so someone else can pick it up. For a small project, the risk of coordinating four specialists is usually larger.
Can you work on a product already started?
Yes. I review what exists, tell you what is worth keeping and what to rebuild, and we carry on from there.
What if I only want to validate the idea?
Then the cheapest route is a very tightly cut minimum product, or even a landing page that measures interest before building anything. I will tell you so even though it means less work for me.
Got an idea and nobody to take it to production?
Tell me about it and I will tell you what it would take to get it published. First call is free.