Free discovery call

Find out whether your infrastructure needs a review, a focused project, or nothing yet

A discovery call is the simplest way to see whether I can help.

We talk through where your infrastructure and developer workflow are today, what you are hiring for, and where the current setup feels too manual, fragile, slow, or founder-dependent.

By the end, we should know whether it makes sense to start with an Infrastructure Foundations Review, scope a focused project around a clear problem, or leave things as they are for now.

Good reasons to book

Book a discovery call if any of this sounds familiar:

• Production works, but too much of it lives in founder memory
• Important cloud resources were clicked together manually
• Deployments still feel more stressful than they should
• CI/CD exists, but engineers do not fully trust it
• Local setup or onboarding requires too much explanation
• Configuration differs across environments in ways that are hard to explain
• You are about to hire engineers and want the setup to be easier to inherit
• You are using AI coding tools, but the repo does not give them enough context to be useful

You do not need to have a clean system before the call. The messy parts are the point.

What we will cover

We will usually talk through:

• Your company stage and hiring plans
• What currently feels fragile or too manual
• How infrastructure is managed today
• How configuration, deployments, and CI/CD work
• Where founder time keeps getting pulled back into technical operations
• What new engineers would need to understand first
• Whether a fixed-scope review or focused project would be useful

The goal is not to diagnose everything on the call. The goal is to decide whether there is a clear enough problem worth looking at properly.

What happens after

If the review is the right next step, we scope an Infrastructure Foundations Review around the parts of your setup that matter most: infrastructure, config, containers, deployments, CI/CD, developer workflow, onboarding, and AI-tooling readiness.

If the problem is already obvious, we may scope a focused project directly.

If the timing is wrong or the current setup is good enough, I will say so.

Before the call

It helps to come with a rough sense of:

• What you have just raised or are preparing for
• Which engineering hires you expect next
• What parts of infrastructure or delivery feel fragile
• What still requires founder memory
• What you would most like to be calmer three months from now

No prep deck is needed.

Request a call

Send a short note with where you are in the hiring process, what currently feels fragile, and what you want to make calmer next.