Andrés Dalla Rizza
pendiente por armar jejej
A small studio with a select portfolio of projects. We guide each one through the entire process, from idea to production.
Most studios ship last year's stack and call it stable. We ship this year's and make it stable — because we read the source, file the bugs, and know which primitives are ready and which are theater. The frontier rewards the patient and punishes the loud. We're patient. The result is software that feels a year ahead of the brief.
Embedded with you throughout the entire project. We cover the full stack: research, product design, frontend, backend, infrastructure, and whatever else it takes. One team, start to finish.
Greenfield web apps, careful rewrites, and evolving products already in production.
Visual foundations, base components, and documentation that keep design and engineering aligned in a single system.
Automating repetitive tasks, useful chatbots, and rigorously evaluated agents, built into the product as real functionality.
Infrastructure, deploy automation, and internal tooling that make development fast and reproducible.
pendiente por armar jejej
Marcus is the half that gets up at six to read papers and ships infra you forget is there. Background in distributed systems at Cloudflare and applied ML at a research lab.
We work in tight iterations: at the end of each one we ship something usable and refine it with your feedback. Value arrives continuously, and priorities are decided together as the project moves forward.
You'll know what we're working on, what's left, and where the risks are. We keep communication channels open — meetings, calls, messages — and stay available when you need us. No black boxes, no surprises at the end.
No account managers in between: you talk directly to the people who design and build it. Decisions don't get lost in translation.
We choose mature tools for the foundations. We reserve risk for where it adds value to the product, not in the infrastructure.
We write for whoever continues the work. We type the boundaries, name things clearly, and delete what doesn't belong.
An argument for tools that whisper. What we lose when every product shouts for attention — and how to design for the long room instead of the launch.
When the unit of work is a multi-step plan, the trace becomes the product. Patterns we use for evals, replays, and the post-mortems that follow.
A behind-the-scenes on how we shipped a portfolio OS for a solo capital allocator — from a theses doc to production in eleven weeks.