One person, both sides of the fence: the systems that run today and the software that makes tomorrow better. Not a fly-by-night freelancer, a studio that sticks around.
// one brand, two strands
Not two businesses. One set of skills, covering the infrastructure that runs today and the software that moves it forward tomorrow.
tenant health
deploy pipeline
// selected work
Real categories of work, client names kept private. Each one solves a problem I've actually been asked to solve.
The problem
Customers need self-service access to their accounts, tickets, and reports.
What was built
A secure web portal with branded login, live data, and role-based access.
The outcome
Fewer support calls, happier customers, a more professional feel.
The problem
Tenant health is scattered across admin centres and easy to miss.
What was built
A dashboard that pulls live tenant health, alerts, and security signals into one view.
The outcome
Proactive fixes before they become incidents, clear audit trail.
The problem
Weekly and monthly reports are manual, slow, and inconsistent in format.
What was built
A pipeline that generates branded PDF reports on a schedule, ready to send.
The outcome
Hours back every week, consistent professional output every time.
The problem
Staff repeat the same questions and tasks inside internal tools.
What was built
An AI-powered assistant embedded in the app, handling queries and actions.
The outcome
Faster answers, less admin overhead, staff focus on real work.
The problem
A web dashboard works, but teams on the move need something in their pocket.
What was built
A native iOS app with offline awareness, biometrics, and push notifications.
The outcome
Access anywhere, faster engagement, a polished user experience.
The problem
Off-the-shelf tools never quite fit the way the business actually works.
What was built
A custom web app built around the real workflow, not the other way round.
The outcome
Less friction, no workarounds, software that fits the team.
The problem
DMARC and DKIM reports are dense and hard to act on.
What was built
Tooling that parses, visualises, and controls email security posture.
The outcome
Clear visibility, faster remediation, a locked-down mail domain.
The problem
Email, ticketing, and billing all live in separate silos.
What was built
Automation that connects them, passing data where it needs to go.
The outcome
Fewer manual steps, fewer errors, a system that runs itself.
// how I work
I spent years in IT support, infrastructure, and systems management. Then I started building the tools I wished I had. That turned into Dev-Junkiez, the software side of the studio.
The result is someone who understands both sides: the systems that run the business, and the software that improves them. One person, one point of contact, end to end.
A freelance studio, but not a fly-by-night one.
I start with the problem, not the tech. A proper conversation about what you actually need, then a clear plan for how to get there. No jargon, no assumptions.
Clean code, modern stack, accessible and responsive by default. You get something that works, looks good, and won't fall over when it scales. I build it like I'd want it built for me.
Launch day isn't the end. I keep an eye on things, fix what needs fixing, and help you plan the next move. A freelance studio, but not a fly-by-night one.
// let's talk
Tell me about it. Whether it's IT support, a custom app, or something in between, I'll be honest about whether I'm the right fit.
What happens next
I read it
Usually within a day or two. I actually read every message myself.
We have a short call
15 to 30 minutes, no obligation. I ask questions, you ask questions.
You get a fixed quote
Clear scope, clear price, clear timeline. No vague estimates.