Available for select engagements

One engineer.Whole product.

I work with founders and product teams when the important part cannot be separated into frontend tickets, backend tickets, and somebody else's product decisions.

Where I enter

Choose the problem.
Not a package.

Each engagement starts with the constraint and the release that would materially improve the business. The shape follows from that.

01

New product build

Turn a validated problem or working prototype into a dependable first release with the product and technical foundations handled together.

Best for
Founder-led SaaS · internal platforms · operational software
I own
Product framing · UX · API · data model · integrations · launch
02

Critical product surface

Own the difficult module inside an existing product—the part that crosses teams, systems, and too many unfinished decisions.

Best for
Billing · permissions · real-time workflows · AI-assisted operations
I own
Architecture · implementation · testing · production integration
03

System rescue

Stabilize a fragile workflow, replace a manual bottleneck, or get a stalled build moving with a smaller and clearer delivery path.

Best for
Slow delivery · brittle features · spreadsheet-heavy operations
I own
Diagnosis · risk reduction · focused rebuild · handover

Working model

Visible progress.
Fewer surprises.

You work directly with the person making the product and technical decisions. There is no handoff layer between the conversation and the code.

01

Frame

We make the actual constraint, the users, the existing system, and the release condition explicit before work expands.

02

Prove

The riskiest workflow is tested early so architecture and product assumptions fail while they are still inexpensive to change.

03

Ship

Progress arrives as working production slices across interface, API, data, integrations, and deployment—not status theatre.

04

Transfer

The release leaves behind documented decisions, maintainable code, and a practical map for the next engineer or phase.

Before the call

The working relationship matters.

A clear fit saves both sides time. This is the kind of environment where I do my best work—and the kind that should choose someone else.

Good fitYes
  • 01The work crosses product, frontend, backend, and data concerns.
  • 02A capable engineer needs room to challenge and improve the brief.
  • 03You want one clear owner for a production outcome.
  • 04Maintainability after launch matters as much as launch day.
Probably notNo
  • 01You need a large staffing supplier or several parallel teams.
  • 02The role is limited to converting finished designs into static pages.
  • 03Every implementation decision is already fixed with no room for judgment.
  • 04Success is measured by activity rather than a working release.
LocationTunis · GMT+1 · Remote
CollaborationEU + US overlap
LanguagesEnglish · French · Arabic
OwnershipYour code. Your product.

Start with what is stuck

Tell me what needs
a clear owner.

Bring the current system, the business constraint, and the decision you cannot make yet. Twenty minutes is enough to identify a useful next step.

Book the call Email meReview the work