Contract productengineer forB2B 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.

Hanif Carroll looking toward the homepage introduction

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.

One offer: contract product engineering.

Senior engineering for your product — usually a monthly engagement with retained context, or a defined project when the next build is already clear. The fit call picks the shape.

Start with a 30-minute fit call.

Tell me what's stuck — a feature, an integration, or an internal tool — and we'll pick the shape that fits.

Book a 30-minute fit call

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
Genrupt creative operations workspace for Amazon seller teams.

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
Palabruno reading product for Spanish learners and teachers.

A founder's view of the working relationship.

What working together looks like.

A simple path from understanding the problem to software your team can own.

01

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.

02

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.

03

Hand over code your team can own

You keep the code, documentation, and the reasoning behind important decisions — ready to operate and extend.

Tell me what your team needs to ship.

No specification or preferred stack required. Start with the feature, integration, or system that's stuck — we'll decide whether a project or a monthly contract fits.