Four products, from zero to real users. I built them on my own.

Before that, the entire frontend of a healthcare SaaS across three platforms, alongside the founder of the business.

Casos Criminales is live in production, with accounts, payments and over 500 users

What are you about to build?

Pick whichever is closest to your next problem and I'll show you only what applies.

Several people on the same state, without stepping on each other.

  • Casos Criminales

    10 devices · 500+ users

    Up to 10 devices on the same investigation board, synced, in production.

    Check it

Shared state is where collaborative products break. I already solved it with paying users on top of it.

Book 15 minutes

Money and permissions telling the same story everywhere.

  • Casos Criminales

    500+ users

    Accounts and payments running in production, not in a sandbox.

    Check it

  • Doqchat

    Pricing per consultation type, with different rules inside and outside consulting hours.

Wiring up a checkout takes an afternoon. The hard part is access, plan and billing never contradicting each other.

Book 15 minutes

A conversation that doesn't stall while the model thinks.

  • English RPG

    Private beta

    A coach that answers out loud and corrects you without breaking the conversation. Latency is the design constraint, not an infrastructure detail.

    Check it

With live AI the product is defined by milliseconds, not by the model you picked.

Book 15 minutes

An agent that holds a long job without losing the thread.

  • Storia

    Private beta

    Agents that take a brief, plan chapters and write a whole novel while holding plot and character continuity end to end.

    Check it

Anyone can wire up a one-step agent. The problem shows up at step twelve.

Book 15 minutes

The problem isn't defined yet, and defining it is part of the job.

  • Doqchat

    mobile · web · Telegram

    The entire frontend of a healthcare SaaS across three clients — mobile, web and a Telegram Web App — alongside the business founder. Routing messages, audio, photos and calls by each doctor's rules: consulting hours, after-hours, per-consultation pricing, appointments. Pre-AI, by hand.

  • FPS

    16 ms per frame

    A custom engine running in the browser, no plugins or downloads, on a 16 ms per-frame budget.

    Check it

In a team of eight, figuring out what to build is half the job. I did it in a domain I didn't know.

Book 15 minutes

What happens in my first 90 days

It's the question you'd ask any candidate. Here's the answer before you ask.

  1. First two weeks

    I use the product as a user until it hurts. I come out with a list of frictions ranked by what they cost, not by how much they annoy.

  2. First month

    One whole thing in production. Small, but whole: design, code, deploy and measurement. I'd take that over three half-finished ones.

  3. By day 90

    I can take a part of the product with no brief and hand it back working. Which is exactly what I did four times with nobody asking me to.

Before you decide anything

Pick one flow in your product. Within 48 hours I'll send back a short analysis: what I'd do, why, and in what order. No cost, no strings. If it isn't useful, you've lost nothing.

Book 15 minutes

Which startups I'm not right for

Saying this now saves us both a call.

  • If the work is already broken down into well-defined tickets, another profile will serve you better. I'm worth more where the problem is still open.
  • If your main problem is scale — millions of requests, distributed infrastructure — that's not my specialty. Mine is product complexity: business rules, real time, shared state.
  • If you're already past fifty people, you probably don't need me for what I'm good at.

If any of this is useful, let's talk

I'm looking for a full-time role at a product startup in LATAM, ideally Argentina, with 5 to 20 people.

Book 15 minutes

Or email me at fernando.n.oviedo@gmail.com