30-minute call

Pick a slot, then tell me what you are dealing with.

The slot is the easy part. What makes the call useful is the description you leave afterwards: I read it before we talk, so we start at the problem instead of at introductions.

Pick a slot

Europe/Berlin · 30 min · video

The calendar is served by Cal.com. Nothing is loaded from it before you click.

Calendar not loading? Write to hello@codiumlab.io and I send two slots back.

Tell me what you are dealing with

Read before the call

Send the description by email

Write to hello@codiumlab.io: the system as it stands, the constraint you are up against and the deadline that matters. I read it before the call.

What the thirty minutes look like

00–05
Where the system stands
What is live, who uses it, what is held together with tape.
05–20
The problem, pulled apart
I ask until I can restate it back to you. Most of the call sits here.
20–27
How I would approach it
Architecture, the risky part, and which entry point fits the scope.
27–30
A recommendation, or a clear no
Named next step and who does what, or the reason this is not a fit.

What I do not take on

Better to read it now than to find out on the call.

Filling a seat in an existing team’s sprint, with the scope decided elsewhere.
Greenfield products with no users yet. The work here starts where there is traffic.
Anything needing someone in the room three days a week.
Prompt tuning on its own, with no system to put it in.

Worth having ready

The URL, and whether I can be given read access to the code.
Who owns the system today, and who decides on spend.
The deadline that actually matters, and what happens if it slips.
A rough budget range. It shortens the conversation for both of us.