Matt Kozak. Let's talk

Independent CTO advisory · Energy & IoT

Know what breaks
before you scale.

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

Where I work Energy softwareConnected devicesCloud & edgeEngineering decisions

01 / The right moment

A hard decision.
A lot riding on it.

You already have people building the product. You need an experienced outside view on what happens next.

01

The pilot works. The rollout is next.

Understand the failure modes, dependencies, and operating costs before you put more devices in the field.

02

Your team is stuck on an expensive choice.

Build or buy? Edge or cloud? Keep the platform or change it? Turn competing opinions into a decision with evidence.

03

Reliability is eating your roadmap.

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

Start with clarity.
Build from there.

A concrete first engagement, followed by ongoing support when it makes sense.

Start hereFixed scope

Architecture & Scale Review

A second set of experienced eyes on one system or critical product flow, and a plan your team can use.

€2,500 / review

10 business days from kickoff and agreed access

  • Kickoff with your founder or technical lead
  • Focused review of architecture, selected code, and evidence
  • Prioritized risks, trade-offs, and recommendations
  • A written decision memo and 90-day action plan
  • 60-minute debrief with your team
Book a 30-minute fit call

We agree the scope before you commit. The call is free.

Keep the perspectiveMonthly

CTO Advisory

A regular sounding board for the technical choices that affect your product, team, and runway.

€2,000 / month

Up to 6 hours per month · month to month

  • Two 60-minute decision sessions each month
  • Async review within the remaining time budget
  • Architecture, vendor, and hiring decisions
  • Follow-through on review recommendations
  • Written decisions and next steps
Discuss ongoing advisory

Timing and response expectations agreed before we start.

Prices exclude VAT, where applicable. Larger or different scopes are quoted separately.

Best fit:

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

An opinion is easy.
A useful decision
takes evidence.

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.

Decision memoExample

Before the next fleet rollout

Question: what should we verify before increasing device volume?

01

Evidence to collect

Reconnect behavior, ingestion capacity, recovery logs, and cost per active device.

02

Decision to make

Whether the current critical path can support the rollout, and which assumptions need a controlled test.

03

Action to assign

Name an owner, define acceptance criteria, and sequence the work against the rollout milestone.

See the 30 / 60 / 90-day plan format

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

The person on the call
has been close
to the problem.

More about my background

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.

Since 2008Building software
CTO at PstrykCurrent operating role

I run engineering at Pstryk full-time. My independent work is focused on scoped reviews and limited advisory engagements.

05 / Selected writing

How I think.

Explore the journal

Before we talk

A few straight
answers.

What happens on the first call?

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.

What does the review cover?

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.

Will you implement the recommendations?

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.

Can you join as our fractional or interim CTO?

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.

What should I bring to the call?

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

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