[ Startups & SaaS ]
Landing pages for startups and SaaS, and an MVP ready to charge
Early on, a startup needs two things: to explain the product well and to put it in real users' hands. I design the landing page and build the MVP end to end, drawing on my experience launching my own SaaS products.
What slows a new product down
- 01
Building for months without validating
It's easy to spend months coding features nobody asked for. A landing page with a waitlist or a small MVP gets you real data sooner.
- 02
An MVP that never ships
Every new idea gets added to the scope and launch keeps slipping. You need someone who helps cut what can wait.
- 03
A product nobody understands
Founders know their product so well that the landing page skips what matters. A visitor should quickly understand what it is and who it's for.
[ Startups & SaaS ]
What I do for startups
Launch landing page
A page that explains the product, shows how it works and collects signups or a waitlist.
An MVP with the essentials
User accounts, the core feature and a dashboard, without what can wait for version two.
Payments and subscriptions
Plans with Stripe or Mercado Pago, a free tier or a credit system, depending on your business model.
AI when it's the core of the product
Content, image or plan generation with OpenAI, Gemini or Replicate, with usage costs accounted for from the design stage.
Admin panel
An internal view to support users, see accounts and understand how the product is used.
A base to grow on
Multi-tenant architecture, multiple languages and documented code for when you add people to the team.
My own products in production
Landing + AI SaaS01Feedmakers
Feedmakers has a free plan, 10 free credits with no card required and social media tools anyone can use without an account. It shows how I think about getting users into a SaaS.
Site + tools02ilove3d
ilove3d started as a viewer for one specific use, intraoral scans, and grew to dozens of tools. With no backend, each user processes files in their own browser, so there are no servers to scale for that work.
Landing + SaaS03Lucy
Lucy is my own SaaS, with a free plan, Mercado Pago subscriptions and a public showroom for each store. Its landing page explains the product by showing it in action.
Landing + SaaS04Parell
Parell, which I'm building with my partner, already charges subscriptions through Stripe. We've worked through the usual SaaS decisions: what goes into the first version, how to charge and how to support users.
How I work
- 01
Talk
We go over your business, your audience and what the site has to achieve. Then I send a proposal, timeline and budget.
- 02
Design
I design it in Figma with your brand and copy. We refine it together before any code.
- 03
Build
I build in incremental deliveries so you see real progress, on desktop and on mobile.
- 04
Launch
Publishing, domain, analytics and technical SEO. After that, maintenance if you need it.
[ FAQ ]
Questions about landing pages and MVPs
It depends on how many features go in, which is why the first step is cutting. The landing page can be ready in a few weeks and the MVP takes longer; the timeline is set before we start.
Often, yes. A landing page with a waitlist lets you measure interest, test messaging and gather your first users while the MVP is being built.
Yes. I work with React, Next.js, Vue, Node.js and Laravel, so I can step into an ongoing project and follow its conventions.
Usually Next.js, TypeScript and Supabase or PostgreSQL, the same stack behind Lucy and Parell. If your team already uses something else, I adapt.
I leave the code organized and documented so you can bring in more developers. If you prefer, I keep building the next versions.
[ You might also like ]
Tell me what you're building
What problem it solves, for whom and what you have today, even if it's just an idea. I'll suggest where to start and how long it would take.