Cases

From question to something that works.

I work on questions where strategy, product, technology and execution meet. Here is a selection of what comes out of that.

Book a call See the work

Influde AI home screen with navigation, copy about being found in AI and buttons to get started.

SearchBalloon home screen with navigation, floating balloons and labels for untapped potential and new clusters.

The question first, the build second.

I do not just show what I build, but mainly which question came first, which choice followed from it and what was eventually delivered.

Question → Choice → Built → Result

Featured

Influde AI

Built for a company

Link building was a series of isolated orders, not a way of working.

The problem was not the buying, it was the missing repeatable approach. So one workspace was built where plan, content and placement stay together.

Question: Companies and marketers bought placements one by one, without a coherent plan.
Built: A copilot for planning campaigns, creating content and managing placements from one workspace.
Result: Live and in use at influde.ai.

The first question looked like a content question. The real gain was in the order of the work.

AI · Workflows · Product

Selection

Work that actually exists.

The products below were thought through, designed and built by me inside Fores3.

ContentScore

Fores3 product

A content review that does not have to be polite.

A judgement only becomes useful when several disciplines read the same piece and someone then decides what comes first.

Question: Content reviews kept stopping at separate scores per area.
Built: A review where digital specialists for SEO, conversion, UX, brand voice, structure and accessibility report findings and a strategy director turns them into priorities and rewrites.
Result: In private beta at contentscore.app.

AI · Digital coworkers · Product

SearchBalloon

Fores3 product

Seeing search behaviour before it shows up in the numbers.

The interesting movement sits at the edge of search behaviour, not in the familiar terms. So search data was made visual instead of tabular.

Question: Opportunities only became clear once they appeared in conventional dashboards.
Built: An explorable view of clusters, unmet demand and content opportunities.
Result: In private beta at searchballoon.com.

AI · Data · Product

Tuinwiki

Fores3 product · platformLive

Publishing content without handing over quality.

Tuinwiki is a content platform with a built in AI editorial team. Briefing, draft, quality control and publication are part of one controlled workflow.

Question: Many content tools generate text, but do too little to guard structure, quality and coherence.
Built: An own publishing platform with AI editing, briefing steps, editorial review and a structured knowledge architecture.
Result: Recently live. The first content is already becoming visible in SEO, AEO and generative search environments, while no external link profile has been built yet. An early signal, not a proven cause.

AI editing · Content quality · Knowledge architecture

tuinwiki.nl ↗

Fores3 OS

Fores3 product

Not starting from scratch every time.

Fores3 OS is the shared technical foundation that lets a new product start from something instead of an empty file.

Question: Every new product asked for the same foundations again.
Built: Product architecture, authentication, workspaces, knowledge systems, AI orchestration, security patterns and operational tooling.
Result: A private foundation, in use under the Fores3 products. Not publicly available.

Architecture · Multi-tenant · AI orchestration

Kunstgrasparadijs

Own venture

Built, run and later sold.

Not every proof is software. This one was a company.

Built: A specialist e-commerce company with its own position in the market.
Result: Sold. No longer owned or operated by Fores3 or Robin.

Venture · Positioning

Next step

Do you have something that could be better, smarter or different?

Bring the question. The solution does not have to be decided yet.

Book a call Work together