Daniel Engelhardt

Daniel Engelhardt · Interim CTO & tech leadership on demand

Your tech team has grown. Your processes, structure and leadership haven't.

I build them: alongside your CTO when they're stuck in day-to-day work, or in their place for a while when there isn't one. Until your team delivers reliably without me.

Things CEOs typically say

  • “I don't know what my team is working on right now.”
  • “A small change takes three weeks.”
  • “We can't go faster, they say. Technical debt.”
  • “My CTO is our best coder, but never gets to anything else.”
  • “Everything goes through one person.”
  • “We hire people, but they create more work and don't perform.”
  • “Every release turns into a fire.”
  • “They build a lot, just not what we need.”
Get an assessment of my team

30 minutes, free, directly with me.

15+

years in tech

3×

CTO or CTO/CPO

0 → 7

team built

~30%

faster delivery after switching to AI

Symptoms

Signs your team has outgrown its structure

If your company has grown over the last few years but your tech team still works the way it did at the start, you've probably said at least one of these.

  1. “I don't know what my team is working on right now.”

    Everything on the board says “In progress”. When a customer asks for an update, you have to go and ask first.

  2. “A small change takes three weeks.”

    You hear about delays after the deadline has passed. You've stopped giving customers firm dates.

  3. “We can't go faster, they say. Technical debt.”

    Every planning meeting ends with the same argument. Nobody can say what the debt costs or when it gets paid down.

  4. “My CTO is our best coder, but never gets to anything else.”

    Hiring, processes and the roadmap stall because they're busy solving the hardest tickets themselves.

  5. “Everything goes through one person.”

    When the CTO is on holiday, the team stops. So do your questions.

  6. “We hire people, but they create more work and don't perform.”

    New hires take months to deliver and tie up your best developers in the meantime. There is no real hiring process.

  7. “Every release turns into a fire.”

    Nobody deploys on Fridays. Customers find the bugs first.

  8. “They build a lot, just not what we need.”

    Features miss the customer's problem. Nobody knows whether anyone uses what was built.

Every month like this costs more than salaries. It costs commitments you can't make to customers. And eventually it costs you your CTO or your best developer, because nobody wants to do two jobs forever.

The cause

Your CTO isn't the problem. They have two jobs.

They're expected to keep building the product while leading a team, hiring and setting up processes. They were brought in for the first job. Nobody taught them the second, and there aren't enough hours in the day for both.

If there's no CTO at all, someone does the second job on the side: you, or your best developer.

Case Study · Evolute

What that looked like at Evolute

Read the case study

Services

Two ways, depending on where you are

Alongside your CTO

When
You have a CTO who is stuck in the code or leading a team for the first time
What I do
I build the team, processes and hiring with them and act as their sparring partner. Technical decisions stay with them
Outcome
Your CTO leads, your team delivers reliably
Scope
1–2 days a week, then sparring

In place of a CTO

When
You have no CTO, or yours is leaving or unavailable
What I do
I take over technical and product leadership for a set period
Outcome
A permanent hire is found and onboarded
Scope
2–3 days a week, 3–6 months

Tech Team Audit

Where to start: two weeks, one clear picture

Before we talk about a longer engagement, I spend two weeks inside your team. I talk to you, your CTO and everyone on the team, read the code and follow how work gets from idea to customer.

Request the audit

What you get

  • A short diagnosis without jargon: what's slowing you down and why
  • Concrete recommendations, ranked by impact and urgency
  • A wrap-up session with you and your CTO

Fixed price from €3,900 plus VAT

Then you decide whether we continue together or your team implements the recommendations on its own.

How I work

Four steps to a team that delivers without me

  1. week 1

    Audit, part 1: Listen

    I talk to you, your CTO and everyone on the team one to one, read the code and trace how an idea reaches the customer.

    Outcome: your team feels heard, not inspected.

  2. week 2

    Audit, part 2: Assess

    You get a few pages without jargon: what's slowing you down, what's urgent, what can wait.

    Outcome: you and your CTO share the same picture and the same plan.

  3. months 1–3

    Build

    Roadmap, weekly rhythm, small releases, a hiring process, three to five metrics.

    Outcome: on Fridays you read an update you understand. On Mondays everyone knows what they're working on.

  4. from month 4

    Hand over

    I anchor ownership with your CTO and the team.

    Outcome: it keeps running after I leave.

Results

What has changed after 90 days

Daniel Engelhardt

About

I was the CTO who built everything and then had to lead a team.

At keepist I co-founded the company and built the product myself, from architecture to operations. At Evolute I joined as the second CTO when the product was in pieces: only one backend developer was left from the original team. I rebuilt the team to seven people, moved the apps from native development to React Native and put in the processes and structure that had been missing. I know what it feels like when your company grows faster than your role.

My background is technical, but for years I also carried product responsibility: as Product Owner at a FinTech start-up before I became CTO there, and as Senior Product Owner for federal and state software projects, among them the Federal Ministry of Education and Research, the NRW economics ministry and the NRW tax administration. At Evolute I wore both hats as co-founder, CTO and CPO, and owned the entire product development. So I speak both languages: your CTO's and yours.

At Evolute we grew the product into a B2B SaaS with around €1M ARR and moved development to AI-native workflows. Delivery time dropped by around 30%.

Request the full CV

More services

Other ways I can help

AI in engineering:

your team delivers measurably faster with AI, not just with new tools. At Evolute: around 30% shorter delivery time.

Taking an AI prototype to production:

turn a prototype built quickly with AI into a secure, scalable product without a full rewrite.

Assessory.dev:

assess developer candidates reliably in the age of AI. Built by me.

FAQ

Will my CTO feel sidelined?

I work with them, not around them. Technical decisions stay with them. Most CTOs in this situation are glad to have someone on their side who has walked the same path.

How do I bring this up with my CTO?

Ideally together: we hold the first call as three. That makes it their decision too from day one.

How much of your time do we get?

Alongside a CTO usually 1–2 days a week; as interim CTO 2–3 days a week.

Is this about letting people go?

No. I tell you honestly what I see. The decisions stay with you.

What about AI?

If it makes sense for your team, AI becomes part of the build phase, with a measurable goal rather than a tool purchase.

What does it cost?

The audit is a fixed price from €3,900. After that it depends on mode and scope; I'll give you a concrete range in the first call.

Contact

What are you seeing in your team?

Tell me in 30 minutes what you're seeing, ideally together with your CTO. You'll get my honest view of where things are stuck and how I would start. If I'm not the right person, I'll tell you that too.

Get an assessment of my team

Free, no obligation. Not a sales call.