How I Work
The service areas describe what I do; this page describes how an engagement is shaped, scoped, and delivered.
Pick the shape that matches the problem: each is a fixed-scope engagement, not an open-ended retainer.
1–2 weeks
An outside, senior look at your architecture, code, or a specific performance or reliability problem, before you commit budget to a larger build.
Typically includes
Fixed scope after an initial fit call.
Typically 4–8 weeks
A defined objective, milestones, acceptance criteria, and a technical handover, whether the work is new delivery or recovering one that stalled.
Typically includes
Fixed scope after an initial fit call.
Approximately 6–12 weeks, depending on scope
A carefully limited product taken from technical discovery to a production release. Scope is fixed deliberately: an unlimited startup product cannot be guaranteed inside a fixed timeframe, so we agree what is in before work starts.
Typically includes
Fixed scope after an initial fit call.
3+ months
A delivery partnership, not an embedded-employee relationship: independent working practices, sustained over time, delivered as a series of scoped phases rather than one open-ended commitment.
Typically includes
Scoped and priced phase by phase, each agreed before it starts.
The same four steps regardless of engagement format.
We talk through the current situation, the outcome you need, and the timeframe. You get an honest read on whether it is a good fit.
For anything beyond a review, I send a short written proposal: scope, milestones, and what "done" looks like.
Work happens in the open: regular check-ins, visible progress, and decisions explained as they are made, not after the fact.
Every engagement ends with documentation your team can maintain, not a dependency on me staying involved.
The questions that usually come up before a fit call.
Both: it depends on scope, not company size. A focused MVP or a technical review fits an early-stage team well; a recovery sprint or ongoing partnership tends to suit a product that already has real users.
Yes. I am based in Munich and work with clients across Germany and the EU, plus US clients in compatible time zones.
Every engagement is scoped and priced after an initial fit call, once I understand what needs to happen. You get a fixed-scope proposal, not an open-ended hourly estimate.
Yes. Several of the case studies on this site are already described at the level of detail their clients agreed to, or with names withheld. The same practice applies to new engagements.
Under 48 hours, typically. Booking a fit call directly skips the back-and-forth entirely.
English and Spanish day to day. German is at an early conversational level and improving. Most client work happens in English regardless of where the team is based.
Commerce and retail, industrial IoT, healthcare and clinical data, and event and ticketing platforms. The case studies on this site walk through examples of each.