REC · AVAILABLE · ASYNC · USD

Portrait of Emanuel Cejas
Available this week

I build products end-to-end. From idea to paying customers.

  • $0.14 / patient · measured in prod
  • Sesión live
  • Kaszek × Anthropic
/ Role
Senior Product Engineer
/ Based
Buenos Aires · UTC−3 · async-first
/ Timezones
Any timezone with async overlap · LATAM, US, EU.
Start with the work

Who I am

To fix something, first you have to take it apart.

— my grandfather, mechanic's shop, 1998

I was 11 and I worked with my grandfather at his mechanic's shop. He had me take apart everything: engines, carburetors, gearboxes. One day I asked him: «Grandpa, why do you make me take apart everything?» He looked at me and said the line above. It took me twenty years to understand what he was teaching me.

Code came late. Not until 2020, at 23, did I pick up JavaScript on my own. No bootcamp, no university, no mentor — just the same shop logic applied to a different thing: take it apart until you get it, then put it back together better. Six years coding every day, two getting paid for it.

Today I'm still taking things apart, but now they're ideas. I take them apart to understand how to build them. A team that wants to add AI to their product but doesn't know where to start, a vertical no one attacked yet, an idea that exists in someone's head but not in production — they're all pieces you can imagine, design and build from scratch. The shop logic still holds: if you understand it, you can make it.

I worked at companies. They taught me to write tickets, wait for specs, hand off deploys. I learned the craft there. Then I found I move faster solo, closing the full loop. For the past 6 years I've been building products that way, end-to-end. LocalCenter, Sesión, JARVIS — they're not features I maintain, they're products that exist because I thought them, designed them, and shipped them.

Now I'm looking for a team where that matters. I don't want to be the engineer who gets tickets. I want to be the one who closes the loop: idea, code, deploy, customer, feedback, iteration. If your AI product needs to leave the lab and start charging money, I'm probably who you're looking for.

No system is magic. Everything can be understood if you take the time to disassemble it.

  • / Year 2026
  • / Place Buenos Aires
  • / Edition v.6.0 — 6 yrs coding
  • / Status Available

By the numbers / STATS

The track record, no rounding.

/ 01 6 years building software
/ 02 8 SaaS products built
/ 03 9 paying clients on LocalCenter

Recognition / VALIDATION

What validated the work.

Selected work / 03

Three things live in production.

Read each one in depth →
Health

Sesión

Live
$0.14 / paciente·mes
Cost / patient
Crisis latency
< 3 s
Status
Live

Therapists can't be on-call 24/7. Sesión can. Clinical co-supervisor with Claude Opus 4.6 + Sonnet 4.6, Safe-Fail layer (41 keywords + Opus second pass) and Fast Lane protocol (<3s in crisis). $0.14 USD per patient/month.

Activity Monitor

JARVIS

4 procs
  • claude-sonnet 38%
  • claude-opus 12%
  • tauri-host 22%
  • tailscale-mesh 8%

Operating 4 machines with Claude Code agents was SSH hell. JARVIS turns it into a native dashboard. Tauri 2 + Rust + Svelte 5. Real-time, multi-host, via Tailscale/SSH.

Stocks

LocalCenter

↑ Growing
9 Paying clients
↑ +9 ytd
Time in prod
1+ year
Status
Live

Vertical SaaS for wholesale businesses in Argentina. 9 paying clients · 1 year in production · full AFIP integration (WSAA + WSFE). Solo build. NestJS + Angular + SQL Server. Weekly releases, direct support.

Archive / ARCHIVE

More things I've built .

Shipped products, side projects in production, and R&D experiments that didn't make it above.

Read all 11 projects in depth Why I built them, what I decided, what I learned.

What I build with / STACK

The stack in production, not on the résumé.

Same tools as the products above. Everything below has shipped to production with paying users at least once.

System Settings — Stack 6 panes

Frontend

5 items
  • TypeScript (strict) ON
  • Svelte 5 / SvelteKit ON
  • Next.js 15 ON
  • Angular 17+ ON
  • Tailwind v4 ON

How I work / PROCESS

Product over process.

  1. / 01

    I don't write tickets. I ship products.

    When the client calls at 11 PM because something broke, I don't hand off to 'the other team'. I am the other team. Discovery, code, deploy, support — same brain.

  2. / 02

    If it's important and not written, it didn't happen.

    Async-first. Calls only when they add value. A good doc beats 5 standups per week. My standup is my commit log.

  3. / 03

    Demos for investors. Code for customers.

    Demos impress at pitch day. Code keeps 9 clients paying a year later. I measure latency, cost, real errors — not slides.

  4. / 04

    What you don't measure doesn't exist.

    Sesión costs $0.14 USD per patient because I measured it, not because I estimated. Every AI feature has its economics validated before shipping. If you can't show me unit cost, it's not production.

  5. / 05

    Ship every week. No excuses.

    Tight loop. Something changes in production every Monday. Customer feedback enters Tuesday's backlog. If you went 3 weeks without shipping, you lost the game.

  6. / 06

    AI is a layer, not the UI.

    Sonnet executes, Opus advises when there's a crisis, Safe-Fail layer catches the critical. Orchestration patterns, not OpenAI wrappers. The chatbot is the most obvious feature and the least differentiated — AI should be product infrastructure.

Right now / NOW

What I'm doing this week.

Notes — ~/now.md Updated 2026-05-26
  1. MAINTAINING

    LocalCenter — 9 clients who call me when AFIP goes down

    A Friday at 7 PM. I fix it anyway. Weekly releases, direct WhatsApp support.

  2. LOOKING FOR

    A team where 'ship it' actually means something

    Senior Product Engineer. USD remote. Available now. Async. No pointless standups.

  3. R&D

    Claude agents that don't blow up production costs

    Applying what I learned in Sesión to other verticals. Spoiler: Sonnet does 92% of the work.

  4. READING

    Anthropic Builder Guide + MCP spec

    What you need to know to ship agents to production, not to demo day.

  5. BUILDING

    JARVIS v0.2 — agent coordination across 4 machines

    So a dev team can share Claude Code without stepping on each other. Open source.

How we work / RATES

Three ways to start.

Available now Taking USD contracts · FT and freelance
→ 30-min discovery · no commitment

All models include direct access to me — no PMs, no middlemen. Initial discovery always free (30 min).

Before you write / FAQ

Questions you can skip.

  • Do you work solo or have a team?

    Solo. If the project needs design, QA or a specialist, I can bring in collaborators I've worked with before. I'll flag it upfront during discovery — no surprises.

  • What timezone do you work in?

    Buenos Aires (UTC-3). Async-first with clients in US East, US Pacific and EU. Daily standups via Slack/Linear. Calls in 1-2h blocks when needed.

  • Do you do post-launch maintenance?

    Yes. First 4 weeks after going live are included in the contract. After that we decide together — monthly retainer, one-off sprints, or documented handoff.

  • Do you work with pre-seed startups?

    Yes, but with care. I need problem clarity and founding-team commitment. If you're still searching for the problem, start with discovery, not build.

  • Do you sign NDAs?

    Yes, before discovery. Send me yours or we draft one together.

  • What if the project needs to scale beyond just me?

    I help you hire and onboard the next engineer. I can recommend people I've actually worked with.

Get in touch / CONTACT

Hiring for a senior or founding engineer role? Let's talk.

Based in Buenos Aires, working async with USD clients across US and EU. Best at production AI agent systems, vertical SaaS, and small teams where shipping matters more than process.

Emanuel Cejas Active now · replies within hours
  1. Hi Emanuel — we're hiring a senior fullstack engineer for our AI startup.

  2. Hi, thanks for reaching out. Available for FT remote USD.

  3. Saw Sesión and JARVIS. Available for a call this week?

  4. Send me times that work this week and I'll confirm.