01
Accounts and teams
Each customer with their own isolated space, users and permissions. Multi-tenancy designed into the database, not patched in afterwards.
We build products sold by subscription: an account per company, roles, recurring billing and an admin panel. From the MVP that validates the idea to the version that holds real customers.
They are always the same ones, and they are the ones that take longest if improvised at the end.
Each customer with their own isolated space, users and permissions. Multi-tenancy designed into the database, not patched in afterwards.
Plans, trials, plan changes and recurring billing with Stripe or Paddle, including the annoying cases: failed payments, cancellations and reactivations.
The screen where your team sees accounts, resolves issues and impersonates a customer to understand what is actually happening to them.
Signups, churn, usage per account and recurring revenue. The numbers product decisions are made with, not website numbers.
A documented API and webhooks so your customers can connect the product to what they already use. It is often what closes a large deal.
Automated deploys, separate environments, backups and monitoring. A SaaS that goes down on a Tuesday morning loses customers that same day.
The most expensive way to build a SaaS is to build all of it before anyone uses it.
We pick the feature that solves the core problem and leave everything else out. It costs less and ships sooner.
8 to 12 weeks for a first version with real users paying or trialling. You will learn more from that than from six months of meetings.
Every new feature is decided by what usage metrics show, not by whichever customer shouts loudest.
A deliberately boring, standard stack: it is what lets another team pick the project up tomorrow.
A narrow MVP is a two to three month project; a full product with integrations and several plans, considerably more. We quote a fixed price per stage, so you can decide after the first one whether to continue.
Yes. The repository, the servers and the services are in your company's name from day one. We do not work with arrangements that lock a client to the provider.
Yes, and we do it often. We start with an audit of the code and infrastructure, and tell you plainly what can be reused and what is better rebuilt.
Stripe or Paddle for international billing and Mercado Pago for local collections. Each has different conditions; in the first call we work out which fits where your customers are.
We can hand it over ready for your team to run, or take care of it under a monthly infrastructure and support agreement. Both options are on the table from the start.
The infrastructure is set up to scale horizontally and monitored from day one. Growth brings problems, but it should not bring a rewrite.
Almost no project fits one category only. These are the other fronts we cover.
Corporate sites, landing pages and online stores that actually ship.
Android and iOS apps, published on the App Store and Google Play.
Chatbots over your data, document reading and internal assistants.
We connect your systems and take the manual work out of the middle.
Two or three lines about the problem you want to solve and who for. We come back with a possible cut, a timeline and a number.