Decisions

The calls that didn't have an obvious right answer

What you're actually buying is how I decide once the constraint is real: what got picked, what got refused, and what it returned. All six calls, with the numbers attached. Three are highlighted on the consulting home; this page keeps the full set in one place.

What transfers, across all six: the consolidation that looks obvious on an org chart is often the most expensive thing you can do to two products that already work. Cloud savings that cost you reliability aren't savings, they're a deferred incident, with interest. Compliance sequenced ahead of the pipeline is a revenue lever; sequenced behind it, it's a stalled quarter. "We'll add evals later" is the sentence that keeps a proof of concept a proof of concept. The honest test of "platform or one-off" is a second real customer, not a design review. And margin is a decision, not an outcome.

Six technology decisions with the numbers attached: what the situation was, what got decided, what got refused, and what it returned. From Bill Thornton's executive work and NLT Labs' own builds.

01

Prior executive role · post-acquisition platform strategy

The consolidation I recommended against

Situation
Two overlapping enterprise platforms landed under one roof after an acquisition, with roughly sixty managers and developers split across both product lines.
The call
Ran the cross-platform evaluation, then recommended keeping them separate.
Said no to
The merge everyone assumed was coming, and the roadmap year it would have eaten.
Returned
The recommendation was adopted. Both platforms stayed separate, and neither roadmap lost a year to the merge.

What transfersThe consolidation that looks obvious on an org chart is often the most expensive thing you can do to two products that already work.

Prior executive role · PE-backed healthcare SaaS

Infrastructure cost down, with uptime going up

Situation
A healthcare platform scaling fast on infrastructure that cost more every quarter, serving users who can't absorb a maintenance window.
The call
Move core platform workloads to AWS, treating zero downtime as the constraint rather than the goal.
Said no to
Savings that come out of the reliability budget.
Returned
Annual infrastructure spend came down, and uptime and operational resilience improved rather than being traded away.

What transfersCloud savings that cost you reliability aren't savings. They're a deferred incident, with interest.

Prior executive role · security and compliance

A compliance program built before the deals needed it

Situation
Enterprise and government buyers were asking audit questions the company had no program to answer.
The call
Build the SOC program from the ground up: vendor selection, cross-department controls, the system narrative, and the company-wide information security policy.
Said no to
Answering questionnaires one deal at a time and calling it a program.
Returned
Multiple SOC 1 and SOC 2 Type II audits passed between 2016 and 2019, with national retail, restaurant, and logistics brands on the customer list. That program was later extended at the same company to ISO 27001 and FedRAMP LI-SaaS.

What transfersCompliance sequenced ahead of the pipeline is a revenue lever. Sequenced behind it, it's a stalled quarter.

Prior executive role · production agent AI

The evals that decide whether an agent reaches a customer

Situation
A production agent that takes real actions for real customers. The failure mode isn't an awkward sentence, it's a wrong booking.
The call
Every agent change runs a five-level evaluation before rollout, covering outcome, path, details, quality and safety, scored by LLM-as-judge against sampled live traffic and on-demand test suites.
Said no to
Open-ended autonomy. Strict tool schemas, policy-driven prompts, and explicit confirm-before-acting steps, so the agent follows defined rules instead of improvising near a customer.
Returned
Agent changes get validated before a customer sees them, not after.

What transfers"We'll add evals later" is the sentence that keeps a proof of concept a proof of concept. The eval pyramid is the thing that makes it safe to put in front of a customer.

NLT Labs · reference build

Eight days to the second storefront

Situation
I needed to know whether a fleet built for one storefront was a bespoke artifact or a transferable kit.
The call
Point the same kit at a second, unrelated storefront and run it live, instead of writing an architecture doc claiming portability.
Said no to
A generalization layer up front. Building the abstraction before the second real case is how platform teams spend a quarter on the wrong seams.
Returned
Eight days from first commit to a second live storefront. Nine of the 30 agents exist only to check the other 21.

What transfersThe honest test of "platform or one-off" is a second real customer, not a design review.

Prior executive role · margin and org scaling

Ten points of margin while the org tripled

Situation
A services-heavy business moving to pure software, with revenue compounding and headcount climbing to match. Gross margin is usually the thing that quietly gets worse during that transition.
The call
Run the services-to-software move as a margin program with its own targets, rather than treating margin as whatever fell out of the product roadmap.
Said no to
Buying growth with headcount. Every implementation that stayed bespoke was a services contract wearing a software label.
Returned
Ten points of gross margin added while the organization grew from 28 people to 80.

What transfersIn a services-to-software transition the revenue mix moves first and the cost base only follows if somebody makes it. Margin is a decision, not an outcome.

The scale those calls were made at: a global enterprise SaaS business grown two and a half times in ARR.

Except where explicitly labeled "NLT Labs," results described on this page are from Bill's work as a technology executive at other companies, not from NLT Labs client engagements, and are anonymized where needed. They're shared as experience, not as a promise of comparable outcomes.

Next step

Facing a call like these?
Talk it through first.

Thirty minutes, no obligation. Bring the decision you're sitting on and I'll walk the same beats: situation, options, what to refuse, and what it should return.

Book 30 minutes → Email instead

Prefer to write? hello@nltlabs.ai