How to Make Your Vision Survive Translation

“The best interface is no interface.”

That line comes from Golden Krishna’s book of the same name, and it shaped how we thought about our product at my startup. We were building AI for smart homes, and the philosophy was simple: nobody wants to disrupt their homes, so to provide an improvement, you need to seamlessly improve the existing experience from something to nothing at all.

When you’re a founder, your philosophy becomes your pitch. You build it, you sell it, you carry the vision into the room. The problem is what happens when you leave.

The pitch that broke

The light switch is an almost perfect interface. A child can use it, and so can your grandmother. It’s been essentially unchanged for over a century because it doesn’t need to change. If you want to replace something that good, you can’t just be better. You have to out-simplify something that’s already effortless.

That was our pitch. Our AI would learn your patterns, anticipate your needs, and make the right thing happen without you having to ask. You wouldn’t need the switch because you’d never think about the lights at all. We used the light switch as our go-to example in presentations because it crystallised the vision so well. People seemed to get it immediately.

And for a while, everything was working. The client was excited, their team was on board, and the project moved from exploration to actual commitment. It was real enough that they brought in a dedicated project manager to run it, which felt like a sign of momentum.

When the pitch failed its real test

We presented to the new PM, but we didn’t realise it hadn’t landed the way it always had before. We’d pitched this so many times that we’d stopped looking for the blank stares.

Somewhere along the way, in meetings we weren’t invited to, our vision got translated. Passed from person to person, summarised in emails, compared against competitors who were selling smart light switches. And in that translation, something shifted. Our philosophy about transcending the light switch became “these guys don’t do light switches.”

We found out when someone finally said it out loud: “You guys don’t want to support light switches.” We understood immediately what had happened, but by then it was too late to turn it around. Trying to correct it felt like we were dropping our philosophy rather than explaining it, and we just looked like we were backtracking to save the deal.

The deal fizzled out, the way these things usually do. Meetings got rescheduled, then stopped getting scheduled. But the real lesson wasn’t that we’d lost a deal. It was that our pitch had been brittle all along, and this PM was just the first person to expose it.

What we’d actually gotten wrong

We had a clear why. The vision was compelling. But we’d made the how completely invisible.

Part of that was deliberate, if I’m honest. The how felt so obvious to us that we didn’t think it needed saying. Of course we integrated with light switches. How else would it work? We were so close to the machinery that we forgot other people couldn’t see it.

So our pitch said “you won’t need the light switch.” It didn’t say “because we integrate with the light switch and control it for you.” We skipped the mechanism and went straight to the outcome, assuming people would fill in the gap themselves.

They did fill it in. They just filled it in wrong.

When you hide the how, people invent their own version. In our case, the invented version was “they don’t support light switches.” It wasn’t a crazy interpretation. We’d spent all our time talking about transcending the light switch and no time explaining that we’d built integrations with every major smart switch on the market. The absence of information became evidence of absence.

How we fixed it

The irony was that the machinery was already working. We had a few hundred users whose lights were turning on and off correctly every day. The plumbing existed. The integrations were built. We just hadn’t thought it was worth mentioning.

The philosophy stayed exactly the same. What changed was how we presented the machinery underneath it.

First, we stopped letting the philosophical point stand alone. When we talked about not needing light switches, we immediately followed with how that actually worked: we integrate with light switches, the software controls them, so you don’t have to reach for the wall. The vision and the mechanism became one thought instead of two.

Second, we added explicit slides showing hardware integrations. Light switches were right there in the supported devices list, impossible to miss. We weren’t hiding the machinery anymore. We were showing it off.

Third, and this was probably the most important change, we moved the integrations from technical documentation into sales and marketing assets. The supported hardware list had always existed, buried in a help centre article. We put it on the website, in the pitch deck, in the product itself. When a potential customer looked at our supported hardware page, light switches were front and centre. The fix wasn’t an engineering one. It was a visibility one.

A great way to enable “no interface” is to make the light switch controllable from a software platform. That was always true. We just hadn’t been saying it.

Give your vision legs

Your pitch needs to survive being re-explained by someone who half-remembers it. That’s the real test. Not whether it lands when you deliver it, but whether it still makes sense when a tired PM summarises it to their boss on a Monday morning.

We thought the how would take the magic away from the why. Instead, the lack of a how made our why look like a lie. If you want your vision to survive the room, give it legs to walk on.