Building PreShiftIQ

How an operator with no engineering background built a supply chain technology platform with AI, and what it took.

A sixteen-part series, published Tuesdays and Thursdays. Not a highlight reel. The parts that went badly are here alongside the parts that went well, because a builder deciding whether to attempt this deserves the failure modes.

Written while the build is still in progress rather than from the far side of it. Each post is the case as it stood the week it was written, with the mistakes left visible.

Published

00

Operators With Access

The story the industry is telling itself is that AI is transforming supply chain. The data says otherwise, and the reason has nothing to do with the technology.

01

Why I Built It

Buyers across the supply chain ecosystem are choosing technology on sentiment, from a field too crowded to evaluate. Neither problem is theirs to fix.

02

The Engine

A beta partner ran three reasonable requirements through the matching engine and it returned nothing at all. Here is what that broke, and what is underneath it.

03

I Am Not a Developer

Thirty years in supply chain, no engineering background, and a platform running in production. The distinction that matters is not who writes the code.

04

It Isn't Spaghetti

The objection is not that a non-developer could not build a platform. It is that whatever he built must be a mess underneath. That objection is reasonable.

05

Operators Over Academics

Why every translation hop between the person who knows the problem and the person who writes the code loses the part that matters.

06

Vendors Pay for Outcomes, Never for Influence

Vendors fund this platform. That is exactly why the part that decides a match was built so it cannot see a dollar of it.

07

Designing to Maturity Before Building Anything

Weeks of talking before a line of code. The question that made it useful was not what to build. It was which decisions would be expensive to change later.

08

Enterprise Grade From the First Commit

Enterprise grade is a phrase people use to mean expensive. It is a property of the architecture, and it comes down to whether the system holds up under conditions it was not designed for.

09

The Seams

Picking the components is the easy part. The architecture is what your application is allowed to know about them.

10

Keeping a Security Posture

The security work you do at the beginning of a build has a shelf life, and nobody tells you what it is.

11

What Took the Longest

The matching engine was supposed to be the hard part. It was not. What took the time was everything I had never done before.

12

Unfamiliar Stops Being Unfamiliar

For the first two weeks, most of what came back was words I did not know. Not the concepts. The vocabulary.

Coming next

13

AI Is Not Magic

Sixteen experienced developers predicted AI would make them faster. It made them slower. Afterward they believed they had been faster.

14

Take the Answer or Argue

The working relationship went through three stages, and the first two were both wrong in opposite directions.

15

What Actually Goes Wrong

Five failure modes that cost real time, and the mechanical check that catches each one.

16

The Eighty Percent Wall

Two months in, the argument is close to consensus, and the industry has named the failure that comes next.

Selecting supply chain technology? PreShiftIQ matches buyers to vendors on measured fit across TMS, dock scheduling, ELD, carrier vetting, and fleet management. Vendors pay for outcomes, never for influence, and the buyer match is free.

Get your free match