The product people use.
Backend features, onboarding, permissions, and the interfaces that connect them. From a rough problem to something your customers can use.
Product and infrastructure engineering
for Seed and Series A teams.
Keep shipping while you grow your team. We work in your codebase, take ownership of a piece of the roadmap, and see it through to production.
Good software needs the whole picture.
We’re comfortable on both sides of the deploy.
Backend features, onboarding, permissions, and the interfaces that connect them. From a rough problem to something your customers can use.
APIs, integrations, data pipelines, and applied AI. The work that connects your product to everything it needs to do.
Cloud infrastructure, deployments, observability, and migrations. Built alongside the product, with a clear path to running it.
Real products. Real operating constraints.
A few places we’ve put our hands to work.
Product and infrastructure engineering for a places discovery platform. Working with Pinned’s team to turn product priorities into working software.
Inside the workPlatform engineering for an application hosting product. Contributions across product development, infrastructure, and technical direction, alongside Galaxy’s team.
Inside the workTechnical leadership and engineering for an open-source JavaScript framework. Contributing alongside Meteor’s core team and community.
Inside the workLed by Henrique Schmaiske, working alongside the teams behind these products.
Your codebase. Your tools. Your team.
We learn the context and get moving.
A feature customers are waiting for. An integration holding up a deal. Infrastructure that needs to catch up. We agree on the outcome, the scope, and who owns what.
You meet the engineer doing the work. We join your workflow, ask the questions early, and keep progress visible through clear updates and working software.
Implementation, testing, release, and the notes that make it maintainable. Stay with us for the next priority or bring the work in-house. We make the transition straightforward.
Bring us a real piece of work. We’ll put the right engineer and weekly capacity around it, with technical direction from Henrique.
Let’s scope the first stepScope, hours, and responsibilities are agreed before kickoff. We revisit capacity as your needs change.Scope and capacity agreed before kickoff.

Small by design. Close to the work.
I’m Henrique. I started El Cubo to work closely with teams on the parts of software that need care: the product, the systems behind it, and the decisions that connect them.
My work spans Pinned, Galaxy, and the Meteor.js ecosystem. I stay involved in technical direction and review, alongside the engineer working on your product.
Get to know HenriqueWe work best with Seed and Series A teams that have a live product, a clear priority, and someone who can make product decisions. A growing, bootstrapped business can be a good fit too. Tell us what you’re building and we’ll be direct about where we can help.
You need a problem worth solving and a person who can answer questions. We’ll work with you to clarify the outcome, break down the work, and agree on what done looks like before implementation.
You’ll meet the engineer working on your product before we start. Henrique stays involved in technical direction and review. We agree on everyone’s role and availability, so you know who to go to and what capacity you have.
We help your new teammate get up to speed, with code, decisions, and operating notes already in your systems. We can wrap up, reduce capacity, or keep working on the next priority. That decision stays with you.
We use coding agents where they help us build, investigate, and test. An engineer remains responsible for the work. We follow your team’s rules on tools, data, review, and production access.
We agree on weekly capacity and how time is allocated before kickoff, then report the work and hours clearly. Implementation, communication, testing, and technical review all count. Production support or on-call coverage needs a separate scope.
Tell us where you are, what you’re building,
and what could use another pair of hands.