Fixed Diagnostic Vs Open-Ended Consulting

Some architecture problems fit in a fixed number of days.
Outside architecture help usually starts as open-ended advisory or a fixed diagnostic.
Open-ended advisory means a few days a month and no fixed deliverable. It works when you already know the problem and want a second brain on the decisions.
If you suspect something’s wrong but can’t name it yet, a fixed diagnostic fits better: a set number of days and a written output (current state, risks, a plan).
For a team that’s never done this, I’d usually start fixed:
- On the last day there’s a document you can judge.
- A short engagement can’t look at everything, so it has to pick what matters.
- If the plan says your team can handle it, you stop there.
A retainer can come after, aimed at a problem that’s now written down.
The case for starting open-ended: you’re mid-migration and need decisions every week. Then a diagnostic just adds a delay.
I run the fixed version as a 10-day Platform Review. What’s in it: https://thomasnys.com/services/platform-review/
Fractional Data Architect helping startups and scaleups build data platforms that scale.
More about Thomas Nys →