Services

SaaS and MVP development

Get to market with a small first version that works and bills subscriptions.

A first version that can start charging.

If you're launching a product, we cut scope to what it takes to start charging, on a base that can take more customers without a rewrite. A well-built MVP takes a month or less, depending on complexity.

Commit, our internal tool, went from first commit to the version we use every day in two weeks. See the case .

Who it's for
Founders with a validated problem and no tech team.
Who it's not for
If you haven't talked to customers yet, start there.
Tell us what you want to launch.

Sample data

What we handle

  • MVP scope definition
  • Multi-tenant architecture and permissions
  • Subscriptions and payments with Mercado Pago
  • Onboarding and usage metrics

Deliverables

  • Product in production, ready to sell
  • Admin panel
  • Payments integration
  • Roadmap for the next versions

Typical stack

  • Next.js
  • Supabase
  • Tailwind CSS
  • shadcn/ui
  • Prisma
  • Mercado Pago
  • Resend
  • Vercel

What an MVP is

An MVP is the first version of your product that real customers can already use. It has just enough to solve the main problem and charge for it. Everything else goes on the list for later versions.

The goal is to learn from paying customers as early as possible. That’s why we cut scope with you before writing any code: every feature you don’t need to start charging stretches the timeline and delays that learning.

When it makes sense

It makes sense if you’ve already talked to customers, know which problem you solve for them and need a working product to sell it. That’s the case for founders without a tech team, and also for companies that want to turn an internal process into a product others can sign up for.

If you haven’t talked to customers yet, start there. A clickable prototype can be enough to validate the idea before building.

What’s included

  • Scope definition: what goes into the first version and what waits.
  • Separate accounts so each customer only sees their own data (multi-tenant architecture), with per-user permissions.
  • Recurring subscriptions and payments with Mercado Pago.
  • An admin panel to manage customers, plans and content.
  • Onboarding and usage metrics, to see which features get used.
  • A roadmap for the next versions.

Timelines and how we work

A well-built MVP takes a month or less, depending on complexity. After a 30-minute call, you get a written proposal with the scope, a fixed price and the timeline, and we don’t start until you approve it. During the build you see a working demo every two weeks.

The base is ready to take on more customers without a rewrite. We use well-known tools like Next.js, Supabase and PostgreSQL, so any team can pick up the code. As the product grows, we keep working on it through Ongoing development, as part of your team. If what you need is to get the system ready for much more load, see platforms at scale.

Products we’ve built

Commit, our internal tool, went from first commit to the version we use every day in two weeks. For a coaching business we built a membership platform with recurring Mercado Pago billing and a members-only course campus. For a Uruguayan restaurant company we’re building a multi-venue restaurant system that takes orders over WhatsApp and bills each venue’s subscription through Mercado Pago.

Frequently asked questions

How long does an MVP take?

A well-built MVP takes a month or less, depending on complexity. The timeline is in the written proposal.

What goes into the first version?

What it takes for a customer to use the product and pay for it. We define it together in the proposal, and whatever stays out goes on the roadmap for the next versions.

How are subscriptions billed?

With Mercado Pago, as a recurring monthly charge. That's how we built the membership platform for a coaching business.

Do we own the code?

Yes. The repository, cloud accounts, domain and payment account are in your name from day one.

Do I need a tech team?

No. We handle design, development and getting it into production. If you build your own team later, they'll find documented code and can take over without depending on us.

What happens after launch?

We look at how your first customers use the product and prioritize the next features with you. We can keep going with Ongoing development, with monthly hours, or with a Maintenance plan.