The product people use.
Backend features, onboarding, permissions, and the interfaces that connect them. From a rough problem to something your customers can use.
More hands.
Same ambition.
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.
A small engineering studio.
Working with teams, everywhere.
Working with teams, everywhere.
Experience that
holds up in production.
From the feature
to the foundation.
Good software needs the whole picture.
We’re comfortable on both sides of the deploy.
Product Engineering
The systems in between.
APIs, integrations, data pipelines, and applied AI. The work that connects your product to everything it needs to do.
The ground it runs on.
Cloud infrastructure, deployments, observability, and migrations. Built alongside the product, with a clear path to running it.
Built. Shipped.
Still doing the work.
Real products. Real operating constraints.
A few places we’ve put our hands to work.
Pinned
El Cubo built place-data intake and enrichment workflows with Pinned’s team, supporting a usable catalogue for discovery and search.
Inside the workGalaxy
El Cubo worked alongside Galaxy’s team on its completed platform modernization, contributing architecture, implementation, and deployment compatibility.
Inside the workMeteor
Henrique contributed technical direction, code review, and release coordination alongside Meteor’s core team and open-source community.
Inside the workEl Cubo works alongside each client’s team. Galaxy and Meteor are part of the same client relationship.
We work
with you.
Your codebase. Your tools. Your team.
We learn the context and get moving.
Start with what matters.
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.
Get close. Build together.
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.
Ship it. Leave it in good hands.
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.
A good place
to start.
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 stepENGINEERING, EMBEDDED
Your next priority.
Our shared focus.
- Start
- One focused workstream
- People
- A named engineer, a clear technical lead
- Rhythm
- Weekly priorities, visible progress
- Ownership
- Your repository and cloud accounts
- Continuity
- Grow the team or hand over cleanly
Scope, hours, and responsibilities are agreed before kickoff. We revisit capacity as your needs change.Scope and capacity agreed before kickoff.
HENRIQUE SCHMAISKEFOUNDER / ENGINEERING
You should know
who’s building it.
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 HenriqueBefore we
say hello.
Are you a good fit for our stage?
We 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.
Do we need a complete specification?
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.
Who will actually do the work?
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.
What happens when we make our hire?
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.
How do you use AI?
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.
How do billing and support work?
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.
What’s next
on your roadmap?
Tell us where you are, what you’re building,
and what could use another pair of hands.