About
I'm a hypocrite.
I spent 30 years telling companies to buy software, not build it. I meant it. I also helped set the fire I now get asked to put out.
Proof placeholder
[PROOF: a current photograph of Kipp, a straightforward portrait, not a stock-style banner.]
The advice I gave
For most of my career, buy-don't-build was the responsible recommendation. Building was slow. It was expensive. It created systems that were hard to maintain and easy to regret. Buying a proven product, and configuring it carefully, was what I told clients to do. I said it as a consultant, as a CIO, and as a Chief Digital Officer. I still believe a lot of it.
I was also incomplete.
The fireman who set the fire
I didn't just give the advice. I built a career on it.
I founded a Salesforce consulting firm and spent years helping companies implement packaged software. Before that I led technology inside a company, and I led consulting practices that installed large systems. I was good at that work. Companies hired me to put those layers in.
In that sense I helped set the fire. A lot of businesses now run on stacked, rented platforms that are hard to change and expensive to keep: a CRM that never quite fit, a commerce layer that grew heavier than the business, a managed website that costs a great deal to host and still does not tell you much. I know those systems because I spent a long time putting them in place.
That is also why I can help take the right ones out. A person who has only ever sold a teardown does not know what happens when a layer comes out badly. I do. The job now is not to tear everything down. It is to know which fire is actually burning, and to put it out without taking the house with it.
What changed my mind
AI changed the math. Not because a demonstration looks impressive, but because it changes what an experienced team can actually ship, and how quickly they can do it. Work that used to mean a large budget and a long project can now be done in weeks, by people who already understand the business. AI is leverage behind those people. It is not a substitute for them, and it is not the value I sell.
That is why I am willing to say something I would not have said for the first 30 years of my career: throw away your software. Build, don't buy.
I need to be precise, because that line is easy to misuse. I am not telling anyone to rip out every system they have. Plenty of teams can now stand up a website or a prototype in a weekend. That is not the same as something you can run a business on. The useful question is more disciplined: for each system, should we keep it, simplify it, build around it, or retire it? Some software should stay. The common processes often should still be bought. The parts that make a company different, and the layers that have become hard to live with, are where building — carefully, with a plan for failure — belongs.
If you change a system without knowing what happens when it fails, you are taking a risk the business did not ask for. Every serious change should start by finding the points of failure and defining a fallback for each one. I call that a Resilience Check. The business should keep running while the work is done.
What I do now
I have worked in technology for 31 years, since 1995, about 20 of them in CRM. I have been a CIO and a Chief Digital Officer. I have built, operated, and led businesses, including my own. I know packaged software and custom development from both sides: the executive chair, and the work of actually building the system.
Today I advise owners, CEOs, and operating leaders as an outsourced CEO or CIO. When a company needs a plan first, I lead a Business Technology & AI Enablement Roadmap: a clear path from as-is to to-be, across people, process, and technology. I am based in The Woodlands, Texas, and I work with leaders here in the Houston area and beyond.
When the work includes building or replacing a website or a platform, that build is done with Solyse.
If we already know each other, or if this sounds like a conversation we should have
Bring me one workflow your team keeps working around. That is enough to start.