// Why us

We know what AI can do
And what it can't

Our team consists of experienced developers and we've worked with AI since 2020. First as hobby projects, out of pure curiosity. Today we use AI in our work every day.

Read on
Pascal on the phone behind his screen

“What you build today may already be outdated next year.”

Pascal, owner

// Since 2020

From experiment to everyday use

We've watched AI grow from a toy into a tool. Every step taught us something you now see in our work.

  1. 2020

    Our own language model

    We ran a small language model ourselves. Slow and limited. But we saw what was coming.

  2. Then

    Campaign analysis

    Analysing websites and YouTube transcripts automatically.

  3. Later

    Talking faces

    AI videos with talking faces. Expensive and slow back then. Normal in every training video now.

  4. 2025

    Our own video platform

    Create a 30-second AI commercial yourself. Overtaken by the technology within a year. Offline.

  5. Now

    Building with AI agents

    We set the scope and the boundaries. Agents write and test the code. An experienced developer reviews.

Screen of our video platform where you choose an actor for a commercialOverview of commercials made in our video platform

// What we learned

Three lessons that make your project better

  1. AI can do a lot. Not everything.

    We know from experience where AI is strong and where a human needs to keep watching. That saves you expensive surprises.

  2. Building small vs building everything

    What you build today will be different next year. So we build in steps you can adjust. No big plan that's outdated within a year.

  3. Boundaries over code

    Writing code has become easy. The value is in the right scope, control and security. That's where we focus.

// How we work

First understand, then build

  1. 1

    Something working, fast

    We don't like projects where you wait months for results. You see something working quickly and only then decide on the next step. Your existing software does not need to be replaced for that.

  2. 2

    Build less when that's better

    Writing code has become easier. Good software takes more than that. That's why we first look into the goal, the current way of working and the systems already in place. If building less is the best choice, we say so.

  3. 3

    Agreements up front, visibility every week

    We set out scope, costs and responsibilities up front. During the build you see every week what's been built. If something goes wrong, you hear it from us, together with a solution.

Pascal on the phone behind his screen
Michael works out an idea at the meeting tableOskar during a meeting at Tulipsoft
Pascal writing 'Fancy a coffee?' on a flip chart

Fancy a coffee?

Tell us what you want to achieve. In half an hour we'll know together whether and how we can help.

Contact