Questions. The ones from the home page and the ones that follow, by topic.
If yours isn't here, the first call is half an hour and costs nothing.
What we build
- What kind of software do you build?
- Custom web applications, mobile apps, SaaS platforms and internal business systems. We work with React, Next.js, Node.js, Python and cloud infrastructure. We pick the stack the project needs, not the one we happen to be fastest at.
- I already have a system. Does this still apply?
- Yes. Tearing down something that works is usually the wrong call: we can integrate with what you have, modernize the old part, or build only the module that's missing. Before proposing to replace anything, we look at what's worth keeping.
- Is there anything you don't do?
- Yes. We don't do hardware support —scanners, scales, receipt printers—, we don't migrate data that isn't in a file yet, and we don't take projects where the only possible integration is copying by hand from one system into another. Every service has its list of limits written down before we start.
- What's the smallest project you'll take?
- There's no minimum size, but there is a minimum of clarity: there has to be a concrete process that's done one way today and is going to be done another way. If that's there, the scope can be closed. If what you want is to explore what could be done, the first call is still worth it and costs nothing.
Timeline and price
- How long does it take?
- Under a month. The clock starts when we begin building, against the scope we signed. For larger projects we split the work into stages so you have something running quickly instead of waiting months for everything at once.
- How do you charge?
- A closed price for the agreed scope, not by the hour. Hourly work moves the risk of the estimate onto the client, and we'd rather absorb it ourselves. The number comes after the first call, once we know what has to be built.
- What if I want to change something halfway through?
- Depends when. While we're still in design, changing something is a conversation and doesn't move the price: that's why the screens get approved before any code exists. Once it's built, a change that was inside the scope gets fixed at no cost; one that adds something that wasn't there gets quoted separately, because otherwise the closed price stops being closed for both of us.
- What if I don't like the result?
- You get your money back. It's the other side of charging by scope instead of by the hour: if we absorb the risk of the estimate, we absorb the risk of the result too.
How we work
- What do you need from me to get started?
- Half an hour on a call to tell us how the process works today —odd case included, since that's the one that breaks the system later—, who's going to use it and what each of them can do. Then, in design, look at the screens and approve them. And during testing, one person from your team using it for a few days.
- Can I see the code while it's being built?
- Yes, and the system too: every week there's something running that you can log into whenever you want. The code is yours from the start, not something handed over at the end.
- Do you use AI to write the code?
- Yes: Claude Code, Codex and Cursor. It's the reason the timeline is what it is. What doesn't change is that a person decides what gets built and reviews what comes out, and that what we hand over has been tested with your data.
- Who picks the stack?
- We do, based on what the project needs, and we explain why. If you already have a team maintaining something in a particular technology, that counts: a system your people can't touch is a system that depends on us again, which is exactly what we're trying to avoid.
After launch
- Do you maintain it after launch?
- Yes: bug fixes, new features, security patches and optimization. Monthly or per piece of work. What we don't do is tie you to a contract to keep what you already paid for running.
- Do I own the code?
- Yes, all of it, deployed on infrastructure in your name. No monthly license to use what you already paid for, and no dependency on us still being around.
- Where is it hosted and who pays for it?
- In accounts opened in your name —Vercel, Neon or Supabase depending on the case— and you pay the usage directly to the provider. It's cheaper than paying it through us and, more to the point, it means that the day you want to switch provider or switch team you don't have to ask us first.
- What if we stop working together?
- Nothing happens to the system. You have the code, the infrastructure keys and the documentation of how it's put together and how it deploys. Training your team is part of the handover for exactly that reason: so carrying on is a decision, not a dependency.
If yours isn't here, the first call is half an hour and costs nothing.
Does any of these look like what you need?
Half an hour, free, to understand what you need. If we can build it, you leave the call with the scope, the timeline and the price; if we can't, we tell you right there.