Someone senior to check what you built with AI, before your customers find the problems.

I’ve built software for 16 years and ran engineering at two software companies. Now I help founders and their teams make what they built with AI reliable, and learn to keep it that way.

Tell me what you built

Fixed price to start. I reply within a couple of days.

Track record

CTO at ++hellohello (2024 to 2026), where engineering grew from 4 to 15 people. Co-founder of Quillok (2020 to 2023), a remote software agency that grew to about 20.

01Where I can help you

What it looks like

You built an app with AI tools. It works, but you’re not sure what happens when real customers use it.
Every change you ask for breaks something else.
Your team uses ChatGPT or Claude every day, and nobody checks what comes out.
An agent or automation makes suggestions, and you don’t know whether to trust them.
You’ve been pitched a build and can’t tell if it’s the right one.
You’re the only one who knows how any of it works.

What I do

Go through what you built: the code, the accounts, where the data lives.
Tell you in plain language what’s risky and what each fix would take.
Tell you what to leave alone. A lot of it is usually fine.
Fix what matters, or hand the list to whoever you work with.
Teach you and your team how to test a change, roll back and check what the AI produces.
Stay on a few days a month if you want someone senior on call.

02What I’ve done

16 years building software. At the last company, revenue quadrupled and margins more than doubled in two years.

About

Sixteen years building software and leading teams. I scaled one agency’s engineering from 4 to 15, and co-founded another that grew to about 20 people, fully remote. Now I help founders who’ve started building with AI make it reliable and learn to keep it that way. Based in Montevideo.

03Three steps

Look
I go through what you have and how your team uses it. You get a plain list of what’s risky and what’s fine.
Fix
We fix what matters, in the tools you already use. I write the code myself, or work with your developer.
Hand over
Docs, a walkthrough, and a test we agree on before anything goes live. Your team runs it when I’m done. If you want me to stay on, that’s a separate conversation.

04Experience

Chief Technology Officer · ++hellohello2024–2026

Design and technology agency for global clients. Built the engineering team and the delivery model that let it scale without losing speed. Led AI adoption across client work and internal operations.

Founder · Sprouth2023–2025

Product company helping retailers use technology to lift operations and sales. Led product strategy, architecture, and client development.

Alongside ++hellohello from 2024.

Co-Founder · Quillok2020–2023

Built a fully remote product agency from zero to about 20 people in three years. Owned delivery, hiring, and client relationships across clients worldwide.

Lead Software Architect · Perficient2019–2021

Led a team of six across mobile, backend, and web for one of the largest hotel and casino companies in the US.

Overlapping Quillok’s first year.

Before that, a decade as an engineer and tech lead building mobile and web products, from Montevideo to the San Francisco Bay Area.

05Services

AI build check

about 1 week · Fixed price

I go through what you built with AI: who can see customer data, what breaks when something changes, how you get back to a working version, and which parts are fine as they are. You get a written list of what to fix first, what to leave alone, and roughly what each fix takes. Then we go through it on a call. The list is yours whether or not you hire me for the fixes.

Ask about a build check

In-company workshop

two sessions over about a month · Proposal within two days

For teams of up to 8. We pick three processes with the owner and prepare for a week. Then we spend four hours on them, so everyone leaves with something working. After two or three weeks of real use, a second session fixes what didn’t stick. The owner gets a short write-up of where the team stands. In Spanish or English.

Ask about a team workshop

Ongoing support

a few days a month · Monthly, scoped after the check or the workshop

For founders who want someone senior on their side. I help you decide what to build next, review what your team or your AI tools ship, and coach whoever owns it until they don’t need me for that part.

Ask about ongoing support

When something needs building

AI Delivery Sprint

~ 3 weeks

We take the top item from the check and I build it. Three weeks later it’s working, your team knows how to use it, and the accounts and the prompts are yours.

Ask about a sprint

Not sure which one fits? Tell me what you built and I’ll say which, or tell you none of them is needed yet.

06Straight answers

I’m not technical. Can I still work with you?: Yes, and that’s who I work best with. You don’t need to read code. You need to know what the app is for and who uses it.
I don’t know what AI can do for us. Isn’t that what I’m supposed to figure out first?: No, that’s my job. You tell me what you have and what you want it to do, and I tell you what’s worth doing first. If the answer is “nothing worth building right now,” you’ll hear that too.
How much of my team’s time does this take?: The check needs about an hour of yours, a call at the start and the walkthrough at the end, plus access to what you built. The workshop needs the team for two sessions.
Do you actually build it, or hand it off to someone?: I write the code. Nobody junior, no outsourcing. You’re talking to the person doing the work, from the first call to the handover.
What happens when you leave?: Everything is yours. The accounts, the prompts, the code, the docs. I hold no logins. Your team is trained on it before I go, and the knowledge transfer is part of the engagement.
What if it breaks after you’re gone?: It’s built in tools your team already opens, so there’s less to break. If something does, you email me. If you want someone on call after that, we can set up a few days a month. If you don’t need it, you don’t pay for it.
Will I need custom software, or is a workflow enough?: Most of the time a workflow does it, built with tools your team already knows. Drive, Sheets, email, Claude. Cheaper, faster, and nobody has to learn a new screen. When the workflow hits its limit, I build the custom software. That’s 16 years of my job. But I’ll tell you when you’ve reached that point, and I won’t sell it to you before you have.
Who makes the decisions?: You do. I recommend, you decide, I build what you decided.
Do you work remotely?: Yes. I’m in Montevideo and work with clients remotely. In Uruguay I can also come to you.

07Who this is for

You run a company of anywhere from a few people to fifty. You or your team started using AI to build or run part of the business, and some of it works. You’re not sure it’s safe to depend on, and you don’t have a technical person to ask. You want it fixed with your team, and you want to understand it when it’s done.

08The audit

Not sure where to start? Find your first move.

Start with one workflow. About 6 minutes. See what to change first, what to leave alone, and a seven-day experiment you can run. Review your first move before sharing your email.

Start the audit

What did you build, and where is it stuck?

Tell me in a line or two. I reply within a couple of days. No pipeline, no follow-up sequences.

Message sent.

I’ll reply within a couple of days.