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 have built CRM and CMS style apps where the value is the daily loop: a lead moves stage, a ticket is assigned, a report is exported. Laravel on the API, Vue or a server-rendered admin on the front.
These tools die when they are a copy of the spreadsheet with worse search. I start from the Monday report and the status change, then build the record around that.
JIRA and Postman sit in the same work. The tool has to be specified, tested, and handed to people who are not engineers.
What this includes
- •Pipelines, assignments, and status history.
- •Search and filters that match how the team already talks about the work.
- •Exports and the one report leadership actually opens.
- •Roles so a new hire does not see every account on day one.
What you leave with
- •The spreadsheet is no longer the system of record.
- •A status change that is visible to the next person without a chat message.
- •A tool you can onboard someone onto in an afternoon.
How it starts
Sit with the person who runs the sheet. I turn their columns into a model and their weekly ritual into the first screen.
When to use it
Use this when the business runs on spreadsheets and they are starting to disagree with each other.
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