Start with the decision
We define the question and the evidence needed before opening the codebase.
About Matt
Close to the code.
Clear on the trade-offs.
I help energy and IoT teams make technical decisions that hold up when software meets the physical world.
Operating experience
The decisions come with real consequences.
I'm CTO at Pstryk, where software, energy markets, device integrations, and customer experience have to work as one system.
My background spans backend development, cloud infrastructure, architecture, and technical leadership. I've built software since 2008, and I still read and write code.
That operator's perspective shapes every independent review: understand the evidence, name the trade-offs, make the decision, and give the team a sequence it can execute.
Since 2008Building software
CTO at PstrykCurrent operating role
I run engineering at Pstryk full-time. Independent work is limited to scoped reviews and a small number of advisory engagements.
How I work
Useful over impressive.
A review should help a team move, not leave it with a ceremonial slide deck.
Make trade-offs explicit
Every recommendation comes with assumptions, constraints, and what it costs to defer.
Leave an executable plan
Your team gets owners, priorities, acceptance criteria, and a practical next sequence.
Your next move
What's the decision
you need to get right?
Tell me what you're building, what's at stake, and when you need to move.
Book a 30-minute fit call Prefer email? [email protected]