Why Fores3 exists

Software is getting easier. Thinking is getting more valuable.

Fores3 exists because the balance has shifted. Anyone can build software now. Fewer people are willing to stop and ask whether they should, and what, exactly, they are building. The studio is a small answer to that question.

Cathedral of light rays through a beech forest at dawn, a mossy trunk in the foreground.

The shift

The hard part moved.

For a long time, building software was the difficult part. Ideas were cheap; execution was expensive. That is no longer true. Building has become cheaper and faster every year, and the ceiling keeps rising.

What has not gotten cheaper is knowing what to build. Choosing a direction. Understanding a market. Reading a product honestly. Deciding, before you begin, whether the thing is worth doing at all.

The scarce resource is not code. It is clarity.

Fores3 exists to help small teams find that clarity, and then, once it is there, to build what naturally follows.

Meet Robin

Four practices, gradually becoming one studio.

Fores3 is founded and led by Robin Visser. He is a builder, an observer, and, when it is useful, a guide. The studio is deliberately larger than any one person; what follows is simply the story of how it came together.

A figure in an olive jacket rests a hand on a beech trunk in an autumn mist.
Robin, Speulderbos
  1. 2010s

    Building

    Years of building small software products, from first sketches to shipped things people paid for. Learning that the hard part is almost never the code.

  2. 2015→

    Working with companies

    Advising founders and teams on strategy, search and product. Watching the same pattern repeat: clarity was worth more than any tactic.

  3. Always

    Photography

    A long, unhurried practice of walking, looking and waiting. It taught more about attention than any product methodology ever did.

  4. 2023→

    AI as material

    Rebuilding an entire practice around AI, not as a feature, but as a new material to think in. Fores3 is what came out the other side.

Built from practice

We build our own things, so we know what we recommend.

A studio that only advises will eventually drift. Advice accumulates without being tested. We build our own software so that never happens here.

Every product in Labs exists because a question would not leave us alone. Each one teaches something a client engagement cannot, the trade-offs, the small regrets, the compromises only visible from the inside.

What we learn there returns to client work the following week. It is the only way we know to stay honest.

On the name

A forest is how we think, not how we decorate.

A forest is patient. It rewards observation. Nothing in it exists in isolation, and nothing important happens quickly.

That is how we approach the work, discovery before decision, observation before opinion, long time horizons over quick wins. The name is a reminder, not an aesthetic.

Still figuring out

A studio is a practice, not an answer.

A few of the questions we are actively working through. We would rather share what we are learning than pretend we already know.

  1. 01

    How AI should extend human thinking.

    Not replace it, not decorate it. The interesting line is the one where a tool sharpens judgement instead of substituting for it.

  2. 02

    How software stays intuitive as it grows more capable.

    Every new capability is also a new way to confuse someone. We are still learning where restraint pays off and where it hides value.

  3. 03

    How companies evolve without losing their identity.

    Repositioning is easy on a slide and hard in a team. We are still figuring out how to change the shape of a company without changing its soul.

If any of this sounds close to how you think we would like to hear from you.