Contract productengineerfor B2B SaaS
I join B2B SaaS teams to build customer-facing products, internal tools, and HubSpot integrations — senior engineering on contract, without the full-time hire.
HubSpot integrations are a core part of the offer.
The feature you need keeps slipping down the roadmap.
The work that matters most keeps losing to whatever is urgent.
- Customer-facing features keep getting pushed back.
- Integrations with your revenue stack keep getting deferred.
- Internal tools keep getting stuck in the backlog.
A contract engineer can own that work from discovery to production.
Two ways to work together.
A defined project when the next build is clear, or ongoing monthly engineering across your product and the systems around it.
Project contract
A defined build, from scope to handoff.
One customer-facing feature, internal tool, or integration — scoped, priced, and built around the people who will use it.
Scoped and priced before work begins
Explore contract engineeringMonthly contract
Ongoing senior engineering for your product.
Continuing priorities across your product and the systems around it, handled by someone who keeps the context.
Monthly, scoped around priorities
Explore contract engineeringNot sure which model fits?
Start with a 30-minute fit call. We'll talk through what's stuck and decide whether a project or a monthly contract makes sense.
See what I've shipped for product teams.
Two client engagements showing the path from discovery and product decisions to software people could use.
Client work
Making Genrupt ready for paying teams.
I helped build the billing, credit accounting, background jobs, and agent workflows that made Genrupt ready for paying teams and helped it support its first 200 paying customers.
View Genrupt
Client work
From a founder's idea to a launched reading product.
I took a founder's idea to live on the App Store, Google Play, and web — owning product, UX, and full-stack engineering for AI reading features, teacher workflows, and subscription billing.
View Palabruno
A founder's view of the working relationship.
He's reliable, communicates great, and has a sharp technical mind. Whether handling complex builds, troubleshooting under pressure, or adapting to shifting priorities, he was dependable every step of the way.
What working together looks like.
A simple path from understanding the problem to software your team can own.
Understand the product and the people using it
We start from the feature, integration, or system that's stuck: who uses it, where it lives in the code and data, and what shipped actually looks like.
Ship the smallest useful version
You see working software early, and we expand from what's proven instead of betting on a big-bang release.
Hand over code your team can own
You keep the code, documentation, and the reasoning behind important decisions — ready to operate and extend.