Thijs Bongertman · Rotterdam

AI that works.Without me, too.

I build AI and software inside your team until you can run it. From Rotterdam, for companies of 50 to 500 people that lose time to searching and manual work.

Let’s talk30 minutes · free, no obligation
Lessons from 35+ AI projectsMemo · 14-minute read
sources

Your knowledge

Conversations

Notes

Decisions

.md / .txt / .pdf
context.md

Connect the context

Earlier plan

New decision

Source retained

your review

Your judgment

Owner still unknown

Explore the example
briefing.md

Ready for your meeting

What changed

What is open

Where it came from

↓

Nieuwe Stroom

A company brain.

A company brain brings knowledge from documents, notes and decisions together in one place that people can search with AI, with the source next to every answer. I build it with the team, test it on their real questions and help get it into daily work.

Ongoing collaboration.

  • Bikeleasing Group

    I work inside the data team on data & analytics: bringing data from different sources together, checking that the numbers add up and turning them into analyses and reports for questions from other departments.

    Ongoing collaboration.
  • Sleeve Technology

    I guide people in working with AI. In hands-on sessions they use AI for their own tasks and learn when to check an output before building on it.

    Ongoing collaboration.
All clients and partners ↗

Examples

Three jobs AI prepares, so you can decide.

Preparing a meeting, spotting a price change at a competitor and selecting prospects. The data is made up; every result points to its source.

second-brain / briefing

Interactive example · fictional data

Your next meeting, prepared.

What do I need to know before the next project meeting?

Briefing

Draft for your review
Decision changed

The pilot starts with support. Sales comes later. This replaces the earlier plan to start with both teams. [1][2]

Next commitment

Support will provide example questions on . Use these to discuss what the first version needs to answer. [3]

Still open

Who will own the knowledge base? The sources do not answer this yet. [3]

Check the changed decision and agree who will maintain the knowledge base.

This example runs locally in your browser. Nothing is sent.

market / changes

Interactive example · fictional data

The change you want to see.

What is new at competitor Atlas?

Market update

Draft for your review
Price changed

Team now lists €59 per user per month, previously €49. An increase of €10. [1][2]

New functionality

Team now includes a CRM integration. The product update refers to new subscriptions. [2][3]

Still unknown

What changes for existing customers? This has not been published. Check before using it in a customer conversation. [3]

Check the change against the sources. You decide whether your team needs to act.

This example runs locally in your browser. Nothing is sent.

prospects / reasoning

Interactive example · fictional data

A reason to take a closer look.

Which companies resemble our best customers?

Selection with reasoning

Draft for your review
Noordlijn · fits your profile

Sector, country, team size and online shop match your criteria. A candidate for your shortlist. [1][2]

Rivierwerk · needs more information

Sector, country and online shop fit. Team size is unknown, so that criterion cannot be assessed yet. [1][3]

A match is not buying intent

These sources describe companies. They do not say whether anyone needs or wants to buy your product. [2][3]

Check the selection and fill in missing information. You choose who to approach.

This example runs locally in your browser. Nothing is sent.

Three steps, and the last one is the handover.

You know the work, I build the software. Scope, price and end date are in writing before I start.

  1. Establish the problem first.

    Show me where your team loses time. We choose one problem and agree how you will know it has been solved.

  2. Test against your everyday work.

    I build a first version and test it with your own data. What goes wrong counts in the decision whether it goes further.

  3. Agree who takes it forward.

    Who maintains it? Who steps in when something goes wrong? How do you check the next version? Those agreements are part of the handover.

In my memo, I describe what went wrong in earlier projects and what I do differently as a result.

Lessons from 35+ AI projects
How we work together, including scope and pricing

What would you like to build?

Tell me where your team loses time or lacks information. After the call you know whether I would build it and what the first step is.

30 minutes · free, no obligation

Honest AI