makemode

AI usage in your company looks like this.

People already use AI at work, each alone at a laptop, each with a tool of their own. What one of them works out stays on that laptop.

first we look at where AI means the most.

We start from your people and the work they do. Before anyone builds, the team finds out what the problem actually is, by talking to the person who has it.

then everyone builds at one table.

The whole team is on board, with the same tool and the same credit. Every build is kept with its code and ready for the next colleague to pick up.

scroll ↓

we start with your people.

Our work is human-centred. Everyone in a team knows a different amount about AI. We look at each level and bring them together into one whole. That is our method.

how do we use AI as a team?

A team answers that by trying. AI moves fast and comes without a manual, so we work the way designers do: in short rounds, with the whole team in the room. Each round the answer gets a bit sharper.

try something small

Everyone builds one small thing for their own work. An hour is enough for a first round.

look at it together

The team puts the results side by side: what worked, what the machine got wrong, what surprised you.

adjust and go again

Change one thing and run it again. A round is short, so a wrong turn costs an afternoon.

agree on what stays

After a few rounds the team writes down where AI belongs in its work and which decisions stay with people. You revisit that agreement as the tools change.

see how a tool gets built.

Someone says what they need and it gets built. The page appears next to the conversation, step by step.

see the studio →

what your team leaves with.

A programme is a room where people build something for their own work and leave with it. This is what stays in the company afterwards.

a tool the team uses

The small internal tool the team keeps asking for: a quote calculator, an intake form, a handover checklist. Published at a link the same day.

the ability to make the next one

Everyone describes a tool for their own job and builds it. Between the builds we look at what the machine got wrong, because that is where the learning is.

builds a colleague can pick up

Every build is kept with its code and leaves a trace you can read, so the next person starts from the work that is there.

a training record

Built from the work itself: who built what, when, for which role.

four ways to start.

Take one, or combine them. Most companies begin with a day and decide after that. We come to you, or you come to Delft.

a day for your network

A network or a branch association books a day with us and brings its own companies. Everyone describes a tool for their own job, builds it and publishes it the same day.

a workshop for one team

One day, in your room or ours, run from a written runbook. It works for a mixed room.

team build, five weeks

One team of five to twelve people who already work together brings one problem from their own week. A half-day kickoff, three sessions of ninety minutes with building in between, and a half-day close with a demo and a handover.

makemode, set up for you

With each organisation we strip the studio down to the parts its people use, in the words they already speak, with your data kept in Europe.

questions a company asks.

our people have never programmed. can they do this?

Yes. They describe what they want to make in plain words and it gets built as real software, published under their own link. Most of the people we teach have never programmed, and a workshop works for a mixed room.

we already use an AI tool at work. what does this add?

A room. Everyone builds with the same tool and the same credit, on a problem from their own week, and the builds are kept where a colleague can find them.

where do our files go?

Everything runs on Scaleway in France: the models, the storage, the published pages. Your data stays in the EU and is not used for training. The trust page is written for the person who signs off on tools.

what does it cost?

A workshop is priced per event, Team Build per team. Write to us for a quote. Trying the studio yourself is free to start, with €10 in credit.

does this make us compliant with the AI act?

You receive a training record that documents the training provided: who built what, when, for which role. The Act mandates no certificate and we claim none.

start with a day.

For a company, a practice, a network or a branch association. Emma and Derek run every programme themselves.

get in touchsee the studio →