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
Healthcare and internal tools are where this matters. A practitioner should not open another clinic’s notes. A staff role should not export every customer. I have built that kind of RBAC on Laravel, with the checks in the API, not only hidden buttons.
Encryption and audit logs sit next to the roles. If someone changes a stage, assigns a lead, or opens a record, you can say who.
I treat PCI and HIPAA-style constraints as product rules: least data on the page, least data in the log, and a permission test for the endpoint.
What this includes
- •Role-based access on the API, with policies that match the org, not a global flag.
- •Audit events for the actions you would have to explain later.
- •Encryption for fields that should not sit in plaintext.
- •A pass over logs and errors so secrets and record ids are not dumped to disk.
What you leave with
- •A role can be explained to a non-engineer in one sentence.
- •An endpoint that refuses a record the UI should not have offered.
- •A trail when something sensitive changes.
How it starts
We list the roles and the records they must never see. I put those rules in the API and add a test that would fail if someone removes them.
When to use it
Use this when access is just "logged in or not", and that is no longer enough for your clients or regulators.
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