It taught me the difference between persistence and attachment.
Persistence is the right instinct while the problem remains inside the system's control. Processes can be redesigned, teams restructured, strategies replaced. But management action cannot remove an external constraint, and higher volume does not repair a model whose unit economics no longer work. Revenue growth and operating health are not the same thing, and I now know exactly how far apart they can travel.
It also taught me something about my own work in the previous case. The integration that made the company efficient is the same integration that removed its ability to retreat. Connected systems produce leverage and they reduce optionality, and I had built ours without ever asking what it would cost to run them in reverse. I would build them again. I would design the exit into them.
The final responsibility of leadership is not to preserve a structure at any cost. It is to judge honestly whether that structure still deserves more resources. Sometimes the answer is another strategy. Sometimes it is recognising that strategy is no longer the variable.
WHAT IT CHANGED
ASNO Corp acquired the Google Business, Yelp and website accounts along with the associated customer and advertising data. I continue to advise them on the basis of what I know about those assets, the customer channels and the operating history behind both.
Some of what was built did not transfer. The Shopify catalogue, the standardised product database and the NFC infrastructure were designed around a physical showroom, and ASNO does not operate one, so those systems are dormant. The social and video channels remain but are unused, because most of that content was built around my personal presence in the business.
The objective was to preserve what could still create value without carrying the whole operating structure forward. That is what happened.
Result
By late December 2025 I concluded that continuing to push the existing structure forward would consume more resources without a reasonable path back to viable economics. The decision was not a response to one bad month or one lost project. It was the cumulative effect of five changes and the measured failure of the responses we had already tried.
I chose a controlled closure.
THE CREWS WERE GIVEN TWO MONTHS' NOTICE.
Each crew operated as an independent licensed subcontractor, in the same way I had started, so the relationships could be wound down properly rather than ended. Some chose other directions. Most of them work with ASNO today.
WE STOPPED ACCEPTING NEW PROJECTS AT THE BEGINNING OF 2026
and completed every commitment already made. Customers were transitioned. Showroom materials were returned to their manufacturers and vendors.
EVERYTHING OWED WAS PAID.
The company met its obligations and closed properly. That was not a secondary consideration; it was the reason for choosing a controlled closure over any faster alternative.
AND I SPENT JANUARY 2026 EXECUTING IT —
closing the store, concluding vendor relationships, finishing the remaining projects, and structuring the transfer of the digital assets.
Decision
We tried the obvious things first.
WE MATCHED COMPETITOR PRICING, which in many cases meant quoting below the 20% we needed. It produced additional volume. It did not produce additional contribution, and revenue that does not carry overhead does not improve anything — it just makes the same loss louder. This was the distinction that mattered most, and it is the one I would want anyone to take from this case: a company can increase sales activity while the operating model beneath it becomes less sustainable.
The digital retail system was still working throughout this. It was still improving the customer journey and still driving higher retail sales — the 55% increase in that year is real. But additional sales at compressed margins could not offset higher product costs, higher fixed costs and weaker project economics arriving together.
WE EXAMINED COST REDUCTION across every line we controlled. None of it produced a version of the company that could absorb higher supplier prices, higher rent, collapsed pricing and the loss of a major contract simultaneously.
AND I LOOKED HARD AT RETREATING TO THE SERVICE MODEL — the business I had built from $5,000 with no showroom and no retail operation at all. That was the obvious escape and I could not make it work. The systems were by then designed around selling material and labour together; the pricing, the product database, the quoting, the customer journey all assumed both halves existed. The integration that had made the company efficient had also made it difficult to take apart.
Analysis
DEMAND PAUSED.
Market volatility arrived during the important part of the selling season. Many of our Bay Area customers worked in technology and held much of their wealth in investments; from their own accounts, they postponed large renovations rather than liquidate during a period of uncertainty.
PRODUCT COSTS ROSE SHARPLY.
Across approximately fifteen vendors in China and Canada, prices increased — Chinese vinyl, laminate and hardwood by 15–20%, some Canadian products by closer to 30%.
COMPETITIVE PRICING COLLAPSED.
We shared vendors with our competitors, so we could estimate their costs. Some were quoting projects at 2–5% above product cost.
FIXED COSTS ROSE.
Showroom rent increased 15%.
AND A CONTRACT DISAPPEARED.
The general contractor on a 75-unit project lost its license and could not proceed. Approximately $1.2 million of expected revenue went with it.
Any one of these is a bad quarter. The combination changed the arithmetic underneath the business. Elephant Floors needed roughly 20% above product cost to carry its service model and fixed overhead, and normally targeted 30%. The market was transacting at 2–5%.
The question stopped being how to improve a department or fix an operational problem. It became whether the model itself could produce an acceptable result under conditions that were not going to reverse on our schedule.
THE REAL Problem
By 2025 the company worked. The production system was in place, both halves of the business ran on connected systems, retail sales were growing, the team was built and the brand was established. Nothing that follows is a story about a company that could not execute.
Entrepreneurship creates a strong bias toward solving problems, and for seven years that bias had been correct. Every difficulty Elephant Floors had met — operational, commercial, organisational — responded to being understood and worked on. I had no experience of a problem that did not.
