Skip to content

SaaS & MVP Development

Take a product from idea to paying users — by someone who has done it for himself.

I have built, launched and operated six of my own products, which is where I learned that the engineering is the easy half. What usually kills a product is building too much before anyone has paid for it. So I scope hard, ship the smallest version that can be charged for, and build the billing, onboarding and measurement that tell you whether to keep going.

What usually brings people here

SaaS & MVP Development

  • There is a product idea and no clear path from it to working software.

  • A development team has been building for months and nothing has launched.

  • You need something real in front of users or investors by a specific date.

  • The prototype works but it will not survive actual customers.

  • Subscriptions, billing and plans need to exist and nobody has built that before.

  • The product is live and growing, and the architecture was not designed for it.

What I build

Take a product from idea to paying users — by someone who has done it for himself.

  • MVPs scoped to the smallest thing a customer would pay for
  • SaaS platforms with multi-tenancy, plans and subscription billing
  • Payment and billing integration, including the parts nobody remembers
  • Architecture that can survive growth without a rewrite
  • Launch: onboarding, analytics, and knowing what to watch
  • Technical validation of an idea before committing a budget to it

Related work

Built, shipped, and still running.

View the full portfolio

Industries

Where I have worked.

Every sector has its own version of the same problem. Find yours.

What people say

From people I've built with.

Héctor built the core backend for DataDrop — uploads, payments, access control — production-ready from day one. He worked independently and just delivered.
Angelo Schalley Akave

Ways to work together

A project, a partnership, or technology leadership.

Project-Based Development

A defined piece of work, scoped before it starts.

For companies that need a specific thing built: a platform, a system, a digitised process, an integration.

Right for you if

You know roughly what needs to exist, and you need it built properly and on a date.

Let's talk
Recurring

Ongoing Technology Partner

Technology capability every month, without hiring a team.

For companies that need technical work continuously — maintenance, improvements, integrations, automation — but not a full in-house development team.

Right for you if

Technology is part of how you operate, the needs keep coming, and right now there is nobody to call.

Let's talk
Recurring

Fractional CTO

Technology leadership without a full-time hire.

For companies that need strategy, architecture and someone accountable for technology decisions, before a full-time CTO is justified.

Right for you if

Technology decisions are being made without anyone genuinely accountable for them.

Let's talk

Questions

FAQ

How long does an MVP take?

It depends entirely on how narrow we are willing to make it. I have shipped a first live version in twelve hours and I have spent six weeks on one. The scoping conversation is what determines it, and we have that before anything is agreed.

Will the MVP have to be rebuilt later?

Some of it, probably — that is normal and it is cheaper than the alternative. What should not need rebuilding is the data model and the billing, so those are the parts I do not cut corners on.

Related services

Let's build something that makes a difference for your business.

Whether you need custom software, AI, or a technology partner for the long run, tell me what is going on and I will tell you honestly if I can help.