01 / Decide
Make the expensive call before the contract makes it for you.
I test proposals, licensing, failure domains and target architecture until you can defend the direction and your IT lead can verify the assumptions.
A first look / the decision field
The quote is thick, the deadline is close, and something on page 14 still does not add up. That hesitation is data.
I test the proposal from your side of the table, turn the decision into architecture and lead the work with your teams until the outcome is defensible and operable.
Decide / Build / Govern
The starting point is not a discipline. It is the decision that must hold, the system your team must be able to run, or the evidence an auditor will ask to see.
01 / Decide
I test proposals, licensing, failure domains and target architecture until you can defend the direction and your IT lead can verify the assumptions.
02 / Build
I turn the decision into architecture, lead the work through your teams and partners, and leave the decision record and runbook behind.
03 / Govern
I turn AI, security and digital sovereignty into named owners, workable controls and evidence that holds in the meeting.
The honest disadvantage
You’re wondering how one person handles work that an integrator staffs with five. Fair. I do not replace your team. I set the direction, lead the critical work with your people and remain accountable for the outcome. The person you meet is the person who does the work. The first decision we make together is whether to work together.
In brief
schlieber.net is my independent B2B practice for consequential IT decisions. I advise, architect and lead the work with your teams so the decision, the system and the evidence agree.
For the person who must still defend a major IT decision after the vendor has left the room: the owner who signs it, the executive who carries it, or the IT leader whose team must run it.
Each note gives you one annotated artefact, source or control and the question it should change. Confirm once. Leave at any time.