I spent around seven years as a Technical Lead at Steadfast Collective before going full-time freelance. A lot of that time was spent on code reviews, architecture decisions, and making sure the work we shipped was something we could maintain long-term.
What I can help with
Code reviews. Architecture decisions. Technical strategy. Looking at a codebase and working out what the biggest risks are, what’s worth refactoring and what isn’t.
I work with teams building on Laravel, Vue, React, and related technologies. I can do a one-off review or something more ongoing if that’s more useful.
Typical consulting work
I can review a Laravel codebase before a major feature, help choose a technical direction, assess performance or reliability risks, and give a team a practical path forward. The output should be specific enough to act on, not a vague list of best practices.
For agencies, that might mean a pre-handover review before a client launch. For product teams, it might mean checking whether the current architecture can support the next stage of growth.
What you get
Depending on the engagement, you can expect written findings, prioritized recommendations, code review comments, implementation notes, or direct pairing with your team. I focus on the decisions that change delivery risk: architecture, database shape, testing, deployment, security basics, and maintainability.
Who it’s for
Teams that want a second opinion before making a big technical decision. A CTO who needs someone to look at the codebase with fresh eyes. An agency wanting a sanity check before handing a project to a client.
If any of that sounds useful, get in touch.
Questions I can help answer
Can you review code without joining the project long term?
Yes. A short review can be useful when you need an independent view of the biggest risks and the next practical steps.
Can you help implement the recommendations?
Yes. If the review identifies work that needs doing, I can either support your team or take on a focused implementation pass.