Building products that behave as well as they look.
I’m Jorge Braccini, a product engineer and creative technologist. I build full-stack products and agentic workflows for remote teams. Twenty years across healthcare, retail, gaming, and marketplaces — currently building for a US team from Buenos Aires. Open to the right full-time role, and select consulting until then.
- MCP servers
- Claude Skills
- Agentic dev loops
- Multi-agent orchestration
- Local inference
- Human-in-the-loop review
- Beat-synced VFX pipelines
- Design systems
- Design-token pipelines
- Monorepo architecture
- Realtime systems
- Payments & billing
- Identity & KYC
- Observability
- End-to-end delivery
- Claude
- Next.js
- React
- TypeScript
- Bun
- Hono
- Turborepo
- Tailwind
- shadcn/ui
- Framer Motion
- TanStack Query
- Drizzle
- Zod
- Postgres
- Neon
- Redis
- AWS
- Vercel
- Nginx
- OpenTelemetry
- Trigger.dev
- MCP
- Stripe
- Twilio
- Customer.io
- Intercom
- Ably
- Persona
- PostHog
- Mapbox
- Google Maps
- Sharp
- Storybook
- Vitest
Problems that became products.
Every one of these started as someone’s problem and shipped as a product they own — live, on a domain, still running. Bring yours and it joins the list.
Generative video, end to end.
Between engagements I ship self-directed products at the edge of the tools. The current one is an agent-native, local-first app that generates music videos end to end — beat-synced planning, a render pipeline over local and hosted models, and a review loop a human actually drives. It’s the clearest read on how I approach hard, modern software and product. If you’re a studio, agency, or team sizing up how I work — start there.
Orchestrated over ComfyUI on your own GPU, or any frontier LLM — swapped per project, nothing locked in.
Turning problems into products you own.
Most engagements ask the customer to translate their problem into specs, tickets, designs, and acceptance criteria before work begins. I do that translation as part of the work — and you get the artifact, not the homework.
- A problem worth solvingA felt pain. Doesn't need to be specced.
- Domain contextWhat you know that I don't — users, constraints, history.
- Decision authoritySomeone who can say yes, ship it without a committee.
- A tight feedback loopAsync or live, ~30 minutes a week. No status meetings.
- A working productDeployed, on a domain, end-to-end — not a deck.
- A codebase you ownConventional, documented, handoff-ready from day one.
- A design systemTokens, components, patterns — sized to your product.
- A team that can keep goingProcess, agents, and rituals so velocity survives my exit.
Brands that have trusted me.
Twenty years of work across healthcare, retail, gaming, advertising, real estate, crypto, and currency exchange — a sample of the names that have signed off the bills.