Non-Technical CTO Guy

CTO | Technology Leader | Gourmand
Currently evaluating several platforms.
Vendors: Dinner works best

[Non-Technical CTO Guy @LazyCTO]

An AI vendor showed me a slide saying developers code 37% faster with their product.

I paused the demo.

I asked HR how many engineers 37% lets us eliminate.

My VP of Engineering said that's not what the statistic means.

Then why is it a percentage?

Nobody had a good answer.

I announced an Engineering Productivity Capture Program that afternoon.

24 open roles frozen.

$2.3 million enterprise license approved.

Engineering pointed out we hadn't even completed the security review.

That's implementation sequencing.

Three months later, 11% of engineers actively use the tool.

The vendor says adoption takes time.

I told the board we'd already captured the efficiency by not hiring the 24 people.

They called it disciplined execution.

Huge.

[Non-Technical CTO Guy @LazyCTO]

The board asked why our technical debt was estimated at $6.8 million.

I asked what interest rate we were paying.

My principal engineer explained that technical debt is not an actual loan.

Even better.

I told the board we'd retire half of it by Q4.

Engineering said that would require freezing the product roadmap for nine months.

I said I wasn't looking for excuses.

I was looking for ownership.

Two days later a vendor showed me an AI platform that “burns down technical debt 40% faster.”

My team said it doesn't support half our stack.

The vendor mentioned their Ryder Cup hospitality package.

Important context.

I approved $1.4 million.

The board slide now says TECHNICAL DEBT REDUCTION INITIATIVE: ACTIVE.

[Non-Technical CTO Guy @LazyCTO]

A database vendor asked me what our biggest data challenge was.

I said fragmentation.

My VP of Engineering asked what I meant.

I said our data is fragmented.

He said all our production data is in one Postgres cluster.

Details.

The vendor nodded and told me fragmentation is exactly what their platform solves.

Finally.

Someone strategic.

Engineering spent two weeks testing the product and found it would make our stack slower, more expensive, and harder to operate.

They presented 14 pages of benchmarks.

But the vendor presented a slide that said UNIFY YOUR DATA FUTURE.

I really liked.

Our data should be unified.

I approved the pilot.

My VP asked what success looked like.

I told him less fragmentation.

He asked again what was fragmented.

This is why engineers struggle with vision.

Transformation underway.

[Non-Technical CTO Guy @LazyCTO]

My principal engineer told me our architecture was too tightly coupled.

I told him I completely agreed.

He asked what I thought we should decouple first.

I said the business from the technology.

He just stared at me.

Very tactical reaction.

I asked the team for a new architecture diagram with fewer arrows.

They said the arrows represent actual dependencies.

Exactly the problem.

By Friday they had redrawn the same system into six large boxes labeled PLATFORM, DATA, AI, EXPERIENCE, TRUST, and CORE.

Much better.

The board loved it.

One director called it “clean.”

Engineering asked whether anything was actually changing.

I said architecture starts with clarity.

We haven'g touched the system.

But the diagram finally looks scalable.

Executive architecture achieved.

[Non-Technical CTO Guy @LazyCTO]

I became a CTO so software vendors would fly me to Monaco and nobody would ask if I knew what an API was.

[Non-Technical CTO Guy @LazyCTO]

A cloud vendor found out I collect watches.

Huge mistake.

Their AE started wearing a different Rolex to every meeting.

Submariner. Daytona. GMT. But he never mentioned them.

He just kept placing his wrist directly next to the laptop.

After our fourth meeting he said their CEO had an extra allocation for a model I'd been trying to find for years.

Pure coincidence.

At that exact moment, their proposal was sitting $800,000 above the incumbent.

Engineering recommended staying put.

I asked Finance whether we had fully considered the strategic cost of switching too slowly.

Three days later I approved the migration.

Six weeks after that, a watch boutique called to say the Patek I wanted had “become available.”

I picked it up Saturday.

Beautiful movement.

So was the budget.

[Non-Technical CTO Guy @LazyCTO]

A cybersecurity vendor invited me to give the keynote at their annual conference.

They offered first class airfare, a suite for three nights, and a $20,000 speaking fee.

I told them company policy doesn't allow me to accept speaker fees from active vendors.

So they made the check payable to a charity I advise.

Problem solved.

My security team had rejected their software the previous week.

I asked them to reopen the evaluation.

They said nothing had changed.

Correct.

But I had.

Two weeks later I stood onstage in front of 2,000 people reading a speech their marketing team wrote about why their platform represents “the future of cyber resilience.”

We signed a $1.9 million pilot on Monday.

The charity is giving me an additional $20k advisory fee.

Everyone wins.

[Non-Technical CTO Guy @LazyCTO]

A storage vendor offered me a founding seat on their “Executive Technology Council.”

I asked what that involved.

4 meetings a year.

Two are virtual.

Two are at Pebble Beach.

Interesting.

Engineering had already ranked them fifth out of six vendors.

Too expensive, slow support, painful migration.

I asked the team to revisit the weighting.

Specifically, I felt we were over-indexing on technical criteria.

By Friday they were suddenly our preferred vendor.

$2.6 million over three years.

Procurement asked what changed.

Strategic alignment.

The vendor sent me my council welcome package that afternoon.

An embroidered quarter-zip, leather scorecard holder, and my name stitched into a brand new Ghost golf bag.

Very organized company. Very excited to work together.

[Non-Technical CTO Guy @LazyCTO]

A salesperson from one of our vendors happened to be at my kid's school fundraiser Saturday.

Total coincidence.

He was also somehow seated at my table.

Also coincidence.

By dessert he had donated $8,000 to the school auction and was asking my son about soccer.

Very community-minded guy.

Monday morning procurement told me his company was ranked 4th in our evaluation.

I asked them to revisit the scoring methodology.

They said nothing had changed technically.

That's why we need executive judgment.

Software capabilities are one input.

Character matters too.

This man supports education.

Our current vendor has never once purchased a ceramic bowl made by third graders.

I added 10 points for strategic alignment.

They moved into second place.

They're one Michelin-star dinner away from first place.

[Non-Technical CTO Guy @LazyCTO]

A software vendor invited me to speak at their annual conference.

Huge honor.

They sent over the title of my keynote.

"Building a World-Class AI Organization."

I haven't built an AI organization, so I was worried.

Then they sent the finished slides.

Perfect.

My communications team asked when I planned to review the presentation.

On stage.

I delivered 28 minutes of vendor marketing to 1,600 people and received a standing ovation from their sales team.

Afterward, their CRO introduced me as a visionary customer.

We're not a customer.

Procurement is still evaluating them.

I posted the conference photos on LinkedIn and told the board we are now recognized as industry thought leaders.

No product deployed.

Thought leadership delivered.

[Non-Technical CTO Guy @LazyCTO]

Our procurement director has become a serious obstacle to innovation.

She keeps asking vendors for competitive pricing.

Extremely damaging.

One account executive told me she made him submit the same quote three times.

I was horrified.

That's time he could have spent building our relationship.

So I reorganized the approval process.

Procurement still negotiates contracts.

They just do it after I verbally tell the vendor they won.

Much cleaner.

She said this eliminates all of her leverage.

Correct.

Leverage creates tension.

Tension ruins hospitality.

Yesterday she tried to block a renewal because pricing increased 34%.

I escalated around her and approved it myself.

The vendor immediately invited me to their leadership summit in Cabo - all expenses paid with a first-class flight.

Cross-functional friction resolved.

[Non-Technical CTO Guy @LazyCTO]

I scheduled a three-day strategic technology offsite for my leadership team.

Attendance was mandatory.

My VP asked why it was being held at a golf resort 6 hours away.

Focus.

We spent 45 minutes discussing architecture.

Then the vendor sponsoring the trip suggested we continue the conversation on the course.

Naturally.

By day two, my engineers were taking Zoom calls from the hotel lobby while I was on hole 14 discussing "platform consolidation."

The vendor asked if this made them our preferred partner.

I said they were demonstrating strong alignment.

My CFO asked what decisions came out of the offsite.

Several.

I changed my grip and my handicap is two strokes lower now.

We extended the evaluation another quarter.

Strategic alignment achieved.

[Non-Technical CTO Guy @LazyCTO]

One of our board members mentioned that he golfs with the CEO of a competing infrastructure vendor.

Important context.

The next morning I reopened an RFP we had closed two months earlier.

My engineering team was confused.

They had already selected a winner.

I told them new strategic information had emerged.

They asked what information.

Board-level market intelligence.

The competing vendor suddenly received a full technical evaluation, three executive meetings, and a revised scoring rubric.

Their product still lost.

Awkward.

So I added a new category called "leadership confidence."

They won that one unanimously.

By me.

The board member thanked me for being open-minded.

We're now negotiating a 7-figure pilot.

Governance strengthened.

[Non-Technical CTO Guy @LazyCTO]

I discovered one of our vendors had never invited me onto its customer advisory council.

Concerning.

We've paid them $2.4 million over four years.

Apparently they reserve advisory seats for customers with "active product feedback."

My engineers submit product feedback constantly.

Nobody cares.

So I called their CRO directly and explained that our strategic relationship was at risk.

48 hours later I was appointed to the council.

My first meeting consisted of 20 CTOs being flown to a resort to complain about the roadmap.

Finally.

I suggested they add more executive programming and fewer technical breakouts.

Strong support.

Engineering asked whether I raised any of their actual feature requests.

I forgot.

But they did give me a plaque.

I'm going to hang it in my office next to the others.

I love recognition, especially when it's gilded,

[Non-Technical CTO Guy @LazyCTO]

I created a new vendor scorecard this quarter.

Engineering gets 40 points for technical capability.

Security gets 20.

Finance gets 20.

Procurement gets 10.

I keep the final 60.

My CFO noticed the totals add up to 150.

Exactly.

Weighted executive judgment.

He asked what my 60 points measure.

Strategic fit.

He asked how strategic fit is calculated.

It's qualitative.

One vendor scored 58.

Another scored 12.

Engineering pointed out the 12-point vendor had the better product, lower price, and stronger security review.

Interesting.

The 58-point vendor had invited me to ring the opening bell at the NYSE.

You cannot capture that kind of alignment in a spreadsheet.

Obviously we went with them.

[Non-Technical CTO Guy @LazyCTO]

A vendor asked us to be a reference customer during a major deal.

I said absolutely.

My team reminded me their implementation has been a disaster for 9 months.

That's precisely why I should handle the reference call.

The prospect's CTO asked if we'd recommend the platform.

I said the partnership had been transformational.

True.

I've transformed my calendar significantly.

He asked about uptime.

I said no enterprise journey is linear.

He asked about support.

I said executive engagement has been exceptional.

Also true.

Their CRO texts me personally.

The vendor closed the deal.

Two days later they sent me front row tickets to Paranormal Activity on Broadway as a thank-you.

Engineering was furious.

I called it ecosystem participation.

Reference strategy validated.

[Non-Technical CTO Guy @LazyCTO]

I asked every engineer to document exactly what they do.

Knowledge transfer, bus-factor reduction, operational resilience. The usual.

They spent two weeks writing 600 pages of documentation.

I didn't read any of it.

Instead I uploaded the PDFs to an AI vendor's demo environment.

The vendor's chatbot summarized the documents into 11 bullets.

Most were wrong.

I called it transformative.

Engineering pointed out one summary claimed our billing system was written in COBOL.

It is written in Python.

Details.

I approved a $980,000 enterprise license.

The vendor's CEO is taking me skiing in January.

We're finally becoming an AI-first organization.

[Non-Technical CTO Guy @LazyCTO]

I put our entire engineering org on a hiring freeze.

We need discipline.

No backfills, no new headcount, no exceptions.

Two hours later I approved a $750,000 contract with a consulting firm to “increase engineering capacity.”

My VP asked why contractors were somehow cheaper than employees.

They're not.

But employees expect management.

Consultants have account executives.

Very different cost structure.

The consulting partner took me to dinner and said they could “flex with our roadmap.”

Our own engineers have been saying that for years.

Never once over wagyu.

The CFO asked me to revisit the freeze.

Absolutely not.

We have to be consistent.

[Non-Technical CTO Guy @LazyCTO]

I launched a company-wide password reset this morning.

No warning.

Everyone had to rotate every credential immediately.

Productivity dropped to zero for half the day.

Sales lost access to CRM.

Finance locked themselves out of payroll.

The CEO asked why this was necessary.

I told him cyber threats are evolving.

In reality, a security vendor told me their CEO was in town and wanted to discuss identity modernization over omakase.

I needed a burning platform.

By 2 PM we had one.

I'm now evaluating a $1.4 million identity solution over the best nigiri I've had in my life.

[Non-Technical CTO Guy @LazyCTO]

I banned engineers from speaking directly to vendors today.

We need a more disciplined procurement process.

From now on all vendor communication goes through me.

My infrastructure lead asked what happens when they have technical questions.

Send them to me.

He asked if I knew enough about Kubernetes to answer them.

Completely irrelevant.

My job isn't to know Kubernetes.

My job is to manage strategic relationships.

Within three hours I had moved every vendor call after 6 PM and marked them “executive dinner preferred.”

One salesperson asked if we could just meet on Zoom.

Removed from consideration.

If you can't invest in the relationship, I can't trust you with our infrastructure.

Another vendor booked a private room and asked about dietary restrictions.

Finalist.