Fred Lackey

Not a Consulting Firm

The distinction matters. A consulting firm takes requirements and delivers code. Spotless Software, LLC was something different: a boutique software incubator that took broken or unbuilt products and made them investable, acquirable, or launchable.

The business was founded on a specific observation about the software industry: there is an enormous gap between the idea phase and the fundable product phase, and most teams fall into that gap. They have the vision and the drive but not the architecture, the process, or the market sense to get across it. Spotless existed to close that gap.

Three partners. Fred as managing partner with full ownership of all technical and engineering decisions. A core team of 29 to 34 full-time W-2 engineers at any given time, expanding to over a hundred active developers when the incubator's full project portfolio was counted. Teams distributed across the United States, Canada, South America, Prague, India, and Russia. Twelve years of operation, ending in 2018.

Two Ways to Engage

Spotless operated through two distinct service lines, each addressing a different failure mode in the software product lifecycle.

The two lines reinforced each other. A product that went through the rescue line often ended up in the facilitation line. The same team that could rebuild a broken architecture could also stand in front of a venture capitalist and explain why the rebuilt version was worth funding. That combination — technical depth plus business fluency — was the core of what Spotless offered.

A Hundred Applications Over Twelve Years

A hundred applications is not a rounding error — it is a sustained operational tempo that requires standardized architecture, repeatable process, and the ability to context-switch between domains without losing quality. Healthcare one week, fintech the next, consumer mobile the week after that.

Managing fifty development teams means managing fifty different sets of assumptions, technical debts, communication styles, and product visions. The discipline required to do that for twelve years is a different kind of engineering than building a single product well.

The Server Farm

Before cloud-first was the default, Spotless operated its own private server farm to host the products it built and incubated. Client applications that went through the rescue or build lines needed somewhere to live. The server farm was that place.

Running production infrastructure for fifty-plus products across a global development organization means 24/7 uptime requirements, continuous security management, and deployment lifecycle ownership that most software shops outsource entirely. At Spotless it was internal — designed, maintained, and operated by the same team that built the products it hosted.

As cloud adoption matured through the 2010s, the infrastructure model evolved alongside it: AWS, Azure, Google Cloud, and DigitalOcean progressively replaced physical hardware, with Docker containerization and Kubernetes orchestration standardizing deployments across the portfolio. The server farm didn't disappear — it migrated.

Three Eras in Twelve Years

Spotless Software operated across three distinct technology eras. The stack at launch in 2006 bore almost no resemblance to the stack at close in 2018 — and the team rebuilt its competencies to match each transition without stopping product delivery.

Sustainable Products, Not Fast MVPs

The incubator model has a reputation for prioritizing speed over substance — build fast, ship early, iterate under fire. Spotless operated differently. The emphasis was on creating sustainable, long-term products: applications that could attract investment because they were built well, not because they were described well.

That meant Agile ceremonies run correctly, not performatively. CI/CD pipelines that were mandatory, not optional. Code quality gates before production deployment, not after customer complaints. Automated testing baked into the process from the start, not retrofitted when things broke.

Some engagements involved development teams that were technically capable but misaligned with the commercial realities of shipping software. Spotless's role in those cases was not just technical — it was to recalibrate the team's understanding of what "done" means in a market context. Sometimes that succeeded. Sometimes the honest outcome was ending the partnership rather than letting it limp toward a bad launch.

The measure of success across twelve years wasn't applications delivered. It was applications that found investment, found buyers, or found markets — and teams that were more capable at the end of the engagement than they were at the start.

Full Stack Across Twelve Years