01
Join your team
A senior engineer inside your team. I work in your codebase, standups and code reviews, and stay long enough to own a real part of the product. Under the hood: Laravel, Node.js, Python or AWS.
Full-time or long contract
I take projects that can be finished. “Build the platform” is not a scope. “Replace this sheet with an app that assigns leads and exports Monday’s report” is.
The stack is the one you already have, or Laravel and a front end if you are starting. I write what is in, what is out, and how we know it shipped.
After delivery there is a short window for the issues that only appear with real data. Then the repo is yours.
What this includes
- •A written scope before the build starts.
- •Implementation on Laravel, Node.js, Python, or the front end you already use.
- •A handoff: how to run it, where the config lives, and what to watch.
- •A short window after delivery for the issues that only show up in real use.
What you leave with
- •A thing you can log into, not a plan.
- •A boundary so the project does not become a second company.
- •Notes the next engineer can follow.
How it starts
You send the brief. I reply with the slice I can deliver and what I need from you. We do not start on a vague build.
When to use it
Use this when you have one project with a clear goal, not an open-ended team seat. Get in touch to discuss scope and pricing.
Engagement
Ways to work together
02
Work solely for your company
A dedicated engineer for one company. I take the product from planning to the live version: backend, data, hosting and screens, with your product as my focus.
Dedicated contract
03
One project
A clearly defined build, then a clean handover: an MVP, taking an AI-built prototype (Lovable, Bolt, Cursor) to production, a migration, or an AI feature. Get in touch to discuss scope and pricing.
Fixed-scope project