How an Idea Becomes a Business

Most ideas start out badly defined.

You know roughly what you want to build, but not exactly what it should look like, how much of it is actually necessary, or how all the pieces should fit together.

That is normal. The idea becomes clearer while you work on it.

At Internet Interests, building starts with reducing the idea to its essential parts. Before thinking about everything the business could eventually become, we need to know what needs to exist for it to work at all.

This usually means making decisions early.

What is part of the product? What can wait? What needs its own system? What can stay manual for now? Which technical decisions will be annoying to undo later?

There is no benefit in making the first version complicated just to make it feel complete.

A lot of ideas become worse when too much is added too early. Features start depending on other features, simple processes become systems of their own, and suddenly more time is being spent managing complexity than building the original idea.

We prefer to get the core right first.

That does not mean building something temporary or careless. It means spending time on the parts that matter and leaving room for everything else to change.

Because it will change.

The name may change. The design probably will. Parts of the product may disappear. Something that looked important at the start may turn out not to be important at all.

That is one reason we do not try to design the entire future of a business before the first version exists.

Some decisions only become obvious once there is something real in front of you.

Eventually the idea stops being a collection of notes, designs and code. The product exists, the systems behind it exist, and there is something that can actually be operated.

That is the point where building gives way to running.

And that is where the next part of the work begins.