Architecture decision
A scoped engagement around a single decision. A working session with your team, the analysis, a written recommendation with the reasoning behind it, then a session to walk through it and take questions. Typically two to three weeks, and faster when the decision can't wait.
This fits a decision that is awkward to unpick later, because a lot gets built against it in the meantime: where the line falls between a shared core and the language-specific code around it, or which of two stacks your on-call engineers can still run in three years.
Where the answer turns on something only a running system can tell you, I build the smallest thing that settles that question and put what it showed into the write-up. Your team keeps shipping throughout. What the engagement asks of them is the working session, and a few answers along the way.
The fee is fixed and the deliverable defined before the work starts.
For when
A decision is in front of you that gets expensive to revisit once anything has shipped on it.
Want to talk it through?
Let's talk