The Value of What We Didn’t Do

For a period of my career, I worked at Thane Direct, one of the larger as-seen-on-TV companies. It was not a marketplace. At any given time, we carried a small catalog, usually around twenty products. Inventors came to us for distribution. They either accepted a modest royalty model, or they invested heavily in an infomercial and entered a deeper partnership.

The company operated in sixteen countries. Each market was fully integrated and treated as its own system. Local payment processors. Local warehouses. Local shipping and packaging partners calculating volumetrics. The UK. Scandinavia. Mexico. North America. No single website serving everyone. Everything had to work, everywhere.

My role evolved from VP of E-Commerce to CTO. We built the ERP system ourselves and integrated it with Microsoft Dynamics and many other systems in each country. The business model relied on installment payments, three or four payments per product. The real complexity appeared after the first payment, when credit cards bounced and retries failed and downstream systems felt the impact. Now imagine managing that across sixteen markets.

This was not a small operation pretending to be simple.

Sales came in waves. When an infomercial was on TV, demand spiked. When it ended, things went quiet. Traffic was scarce, expensive, and time-bound. Many companies in similar situations opened the door to affiliate marketers to squeeze out incremental gains.

We did not.

Subtraction can be strategy.

Our products were unique. Affiliates would not create new demand. They would intercept existing intent and skim value from the same customers. Allowing that would have added complexity without adding signal. So we refused it, even when it looked like standard practice elsewhere.

The entire e-commerce and IT surface area for all sixteen markets was handled by a very small team, usually between five and ten people. That stood out to everyone evaluating the company. Subsidiaries wanted autonomy. Each market wanted its own marketing ideas, its own tools, its own exceptions.

Instead, we paid close attention to what worked in one place. We confirmed it. Then we moved the same approach to the next market. Not control for its own sake. Just careful validation and reuse.

What mattered just as much as the size of the team was how it was built.

Every person on that team was chosen carefully.

They were strong technically, but more importantly, they were:

• humble
• thoughtful
• genuinely good to work with

There was no posturing, no internal competition for attention, no need to prove intelligence through complexity.

People listened. They helped each other. They cared about the system as a whole.

A line from David Ogilvy stayed with me then and has stayed with me since:

If we hire people who are smaller than we are, we shall become a company of dwarfs. If we hire people who are bigger than we are, we shall become a company of giants.

— David Ogilvy

The point was never ego. It was trust. When you surround yourself with people who are capable and secure, you can keep the system simple. You can resist fragmentation. You can say no to unnecessary additions without fear.

I was always a strong proponent of keeping the engineering team in-house. Not because of ideology, but because proximity mattered. A team that understood both the systems and the business could pivot quickly and decisively. When a product suddenly broke through and sales surged, that same small team could support it immediately. Speed came from shared understanding, not headcount.

There were other things we deliberately did not do.

We did not rely on focus groups or surveys asking customers what they thought they would buy. Stated intent turned out to be a weak signal. People are sincere, but sincerity is not the same as commitment.

Instead, we sometimes ran dry tests. Not shipping the product yet, but testing whether people would actually pull out a credit card. That moment told us more than any forum or questionnaire ever could. Many people say they would buy something. Far fewer actually do.

That distinction stayed with me.

Looking back, the most valuable learning from that period was not about scale or growth. It was about subtraction. About understanding where signal actually comes from. About resisting additions that feel productive but quietly dilute focus.

Signal is often protected by refusal.

Success, in that environment, often came from what we chose not to do.

That lesson has held up remarkably well.