Most MVPs reach production in 60 to 90 days. You see a working prototype before you pay for construction. After that, four phases with a clear handoff between each, and the same team from the first sketch to operation.
01 · Prototype1–2 weeks
See it first
A clickable prototype of the core flows, built on real screens and put in front of your users. It is the cheapest moment to find out you were wrong.
You receive
Clickable prototype of the main flows
Findings from sessions with your users
Scope, timeline and fixed price for the build
You decide
Whether to build, what goes into the first version, and what waits.
02 · Build6–10 weeks
Build it properly
Pipeline, tests and a versioned environment from the first day, with AI-assisted engineering. You get a working build to try every week.
You receive
Weekly build on a staging environment
Repository, pipeline and infrastructure as code, documented and ready to hand over
Short written update every week
You decide
Priorities week to week, inside the agreed scope.
03 · Launch1–2 weeks
Put it live
Cloud infrastructure and app store publishing included, with support for validation and the first days in front of real users.
You receive
Production environment with monitoring and backups
App Store and Google Play publishing
Launch checklist and rollback plan
You decide
The launch date and who gets access first.
04 · Operateongoing
Keep it running
We stay responsible after launch: deploys, monitoring, updates and incidents. A product nobody operates is not finished.
You receive
Monitoring, backups and security updates
Incident response with an agreed recovery time
Monthly report on availability and costs
You decide
Whether to keep us on a retainer, or take everything to another team.
Principles
Decisions we make before the first line of code.
Security is an architecture decision
Encryption and role-based access are designed in from the start, not added in a checklist at the end.
AI is a tool, not the architect
It shortens the build. A person on the team still reviews and signs every release.
No chasing trends
Technology choices that will still make sense in three years, and that another team can pick up.
You own what we build
Code and design are yours once the project is paid in full. Accounts move to your name whenever you decide to leave. No proprietary layers.
How to hire us
Two ways to work together.
Both start with a prototype at a fixed price, credited in full to the build if you go ahead. You keep it whether or not you go on to build.
Step zero
Prototype
US$ 1,200 · fixed scope · credited to the build
A clickable prototype of up to three core flows, tested with three of your users. It sets the scope and the price of the build.
Option A
Fixed-scope build
prototype → mvp → launch
A defined scope, timeline and price, agreed after the prototype. Suited to a first version or a new product line.
Option B
Monthly retainer
evolution + operations
A standing team for new features, infrastructure and support. Suited to products already in production.
Limits
What we do not do.
Saying no early saves both sides a contract that would not work.
Build from a finished specification without questionsWe take part in deciding what to build. If you need a team that only executes, we are not the right fit.
Deliver and disappearEvery project includes a plan for who operates the product after launch, even if it is not us.
Staff augmentationWe do not place individual developers inside your team. We work as a studio, with our own process.
Promise dates before the prototypeA timeline without a validated scope is a guess. The prototype is where the date comes from.
Make it hard to leaveAccounts stay under our organization only to spare you the admin. They move to your name whenever you ask.
Questions
Why is the prototype paid separately?
It is real work: design, a clickable build and sessions with your users. It costs US$ 1,200, with a closed scope of up to three core flows and three user sessions, and the full amount is credited to the build if you go ahead. If you stop there, you keep the prototype and the scope, and can take them to anyone.
I'm not technical. Can I still work with you?
Yes. That is exactly what the prototype is for: before you commit to the build, you get something you can click through and test with real users. After that, every week you receive a short update in plain language and a working version to try, and you talk directly to the people building your product.
Can we start directly with the build?
In most cases, no. The prototype is where the scope, the timeline and the price come from, so skipping it means pricing on guesses. If you already have a prototype or specification validated with users, we review it together and tell you honestly whether it is enough to start the build.
Who owns the code and the infrastructure?
Code and design are yours once the project is paid in full. While we work together, accounts, domains and repositories live under our organization so you do not have to manage them, and you receive an up-to-date inventory of everything. When you decide to leave, they move to your name. The details are in our anti-lock-in policy.
What if we want to move to another team later?
We help you do it. With at least 15 days' notice, we set up your own accounts and move the infrastructure, domains, repositories and apps to your name, along with the documentation. The handover takes about 30 days, and your product stays online and under our care until it is done. Handing over what is already yours costs nothing; the migration work is estimated and approved by you before it starts.
Do you work with teams outside Brazil?
Yes. We work remotely, in English, with contracts and invoices in US dollars. We are based in Brazil (UTC−3), one to two hours ahead of US Eastern time, so our working day overlaps almost entirely with the East Coast.
How do you use AI?
Every day, in design, code and operations, using Claude Code and Gemini on commercial plans that do not allow training on your content. We work from written specs, in short steps reviewed one at a time, with the minimum access each task needs. Every change is reviewed by a person before it reaches production, and production data never goes into AI tools without your written authorization. The details are in our AI policy.
Start with the prototype.
Tell us what you have today. We reply within one business day with a scope and a price for phase 01.