NLT Labs · Fractional CTO and CIO
01
Three ways this usually starts, and what a first engagement looks like once you're in one.
“We keep having the same meeting.”
One decision, read properly. What's running, what each option costs, and the call I'd make, in writing. Including whether an AI build is ready for production or still a proof of concept.
Scope agreed in writing before I start. Nothing up front, invoiced at Findings and recommendations, then at the Leadership readout.
“We need somebody they can look to.”
I work inside your leadership team on the platform, the roadmap and the people carrying them. AI strategy included, from the tools already running on people's desktops to approved workflows.
Scope reviewed and reset as the work continues. Nothing up front, progress visible as it happens.
“We're pricing an asset and can't read the code.”
A read of the platform, the team and the decisions behind them before the price is set, written in plain terms the deal team can use. Including whether the AI story in the deck holds up against what's actually running.
Scope defined in writing before the read starts. Nothing up front, invoiced at midpoint and end.
Recognize one of these? Start a conversation →
02
No proposal deck, no discovery workshop. This is the usual shape of a first engagement. What it actually includes gets set on the discovery call and follows what you need, not a template. Scope goes in writing before any work starts, so you know what you're agreeing to before you agree to it.
A direct conversation about where things stand and what's actually at stake. No slides, no pitch. This call carries no obligation on either side.
I write down what you have today, the systems, the decisions, the assumptions, as found rather than as expected. I sit down with whoever has been carrying this internally; they know the history, and I build on what they know instead of starting over.
I name, in plain terms, where you are against where a well-run version of the business would be. This is a separate step from what comes next, not a blend of the two.
Ranked by consequence, not by what's easiest to say. This is where the diagnostic turns into a call, and it only happens after the read is done, never before.
A sequence that respects what the organization can actually absorb, not a wish list. Each phase is agreed before it begins, and a change in scope is a conversation, not a surprise.
Presented and walked through directly, so questions get answered as they come up, not in the margins of a document that gets filed. Remote or in person, whichever suits your team. The decision stays yours, and you make it with the full picture in front of you.
The order holds; what fills each step is set on the call.
I'll know who actually does the work before I say a word about how the team should be organized. Any roadmap you get from me is built on what I actually found in your systems and your people. The diagnostic finishes before the recommendation starts, even when that's slower. And platform advice waits for the read. If you've already chosen, that choice stands, unless I find you a real reason to revisit it.
Scope is agreed in writing before work starts, and nothing is paid up front. Progress is visible as it happens, not only at the end.
No surprise at close.