The pilot works. The rollout is next.
Understand the failure modes, dependencies, and operating costs before you put more devices in the field.
Independent CTO advisory · Energy & IoT
Your next launch, rollout, or architecture decision needs a clear plan. I help energy and IoT teams find the risks, weigh the trade-offs, and decide what to do next.
Technical review: €2,500 · 10 business days · scope agreed upfront
01 / The right moment
You already have people building the product. You need an experienced outside view on what happens next.
Understand the failure modes, dependencies, and operating costs before you put more devices in the field.
Build or buy? Edge or cloud? Keep the platform or change it? Turn competing opinions into a decision with evidence.
Get a focused assessment of one critical flow, with a prioritized plan for what to fix first and what can wait.
02 / Work with me
A concrete first engagement, followed by ongoing support when it makes sense.
A second set of experienced eyes on one system or critical product flow, and a plan your team can use.
10 business days from kickoff and agreed access
We agree the scope before you commit. The call is free.
A regular sounding board for the technical choices that affect your product, team, and runway.
Up to 6 hours per month · month to month
Timing and response expectations agreed before we start.
Prices exclude VAT, where applicable. Larger or different scopes are quoted separately.
Founders and technical leads in energy or connected products, with a working product, someone who can implement changes, and a specific decision to make.
03 / The output
You leave with the reasoning, the priorities, and a practical sequence of work. Something your team can challenge, share, and act on.
Illustrative excerpt below. This shows the format, not a client engagement or a completed assessment.
Question: what should we verify before increasing device volume?
Reconnect behavior, ingestion capacity, recovery logs, and cost per active device.
Whether the current critical path can support the rollout, and which assumptions need a controlled test.
Name an owner, define acceptance criteria, and sequence the work against the rollout milestone.
Days 1–30 · VerifyGather missing evidence and resolve the highest-priority uncertainty.
Days 31–60 · ImplementDeliver the agreed changes, with owners and acceptance criteria.
Days 61–90 · ReassessReview the results against the next milestone and update the risk register.
Specific actions and timing depend on what the review finds.04 / Operating experience
I'm Matt. I lead technology at Pstryk, building energy software that connects a digital product to the physical world.
That means working through device integrations, data flows, architecture, and engineering decisions with real operating consequences. My background spans backend development, cloud infrastructure, and technical leadership.
I've worked in software since 2008, and I still read and write code. In a review, I work directly with you and your technical team.
I run engineering at Pstryk full-time. My independent work is focused on scoped reviews and limited advisory engagements.
05 / Selected writing
A practical way to think about the edge–cloud boundary in energy software.
Hardware dependencies, field operations, and the questions behind a technical review.
Lessons from building a product around consumption, cost, and everyday use.
Before we talk
We spend 30 minutes on your product, the decision you're facing, your deadline, and whether I can help. If there's a fit, I send a written scope and fee. The call is for fit and scoping; the technical assessment happens in the paid review.
One agreed system or critical flow. We choose the question, evidence, and boundaries before kickoff. The review includes selected documentation and code, a discussion with your technical lead, the written output, and a debrief. A full codebase audit, security assessment, or broader diligence needs a separate scope.
The review gives your team the assessment and action plan. Implementation is separate. Advisory can help your team make decisions and review progress within the monthly time budget.
My current focus is scoped technical reviews and advisory alongside my full-time CTO role at Pstryk. If you need someone to run engineering day to day, say that at the start so we can establish whether the engagement is workable.
Your company or product link, the technical decision you need to make, and your target date. An architecture sketch helps if you have one. Please leave credentials, customer data, and confidential documents out of the booking form.
Your next move
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]