The studio that opens boxes.
Metis Labs is a custom-software studio in Utrecht, the Netherlands. Built so you talk to the people doing the work: one founder accountable for every promise, a team of fifteen delivering it in the open. No account layer relaying messages into a black box.
We've seen the inside of the box. It made us start a studio.
Metis Labs started from a frustration you might recognize: watching companies pay serious money for custom software and get, months later, something that technically works but doesn't solve the problem they described on day one. Not because anyone was lying, but because the process was sealed. No one outside could steer, and no one inside was measured on the client's number.
So we inverted it. Everything we build happens in the open (live repo, weekly working demos, decisions explained in writing), and every project starts with a metric the client can verify, not a feature list we can hide behind. Openness isn't a value statement on this page; it's the mechanism that keeps us honest about value.
Metis, the owl, and the flask.
Metis was the Greek goddess of practical wisdom: counsel that actually works, not theory. The owl in our mark stands for seeing in the dark, which is fitting for a studio whose whole point is that you shouldn't have to. The Erlenmeyer flask is the "Labs" part: advice alone doesn't ship. We run experiments, measure, and keep what works.
One person accountable. A team delivering.
Milan Coppens is the founder, and your single point of accountability. Milan scopes the problem with you, leads the build, and answers for the metric at the end. You never chase a committee: one person owns the promise. Behind that promise builds the team below, and because everything happens in the open, you see exactly who did what, every week.
[email protected] // metislabs.eu
Inside the box: fifteen people, one number to answer for.
No job-title theater. What matters is what each person answers for on your project, so that's what we list.
Deepak Kushwaha
ANSWERS FORThe architecture still holding up long after we've handed over.
Bart Spilt
ANSWERS FORThe build staying pointed at your problem, not drifting toward features.
Tanay Choudhary
ANSWERS FORTranslating how you actually work into something buildable.
Manvendra Singh
ANSWERS FORThe numbers: your baseline, your metric, and whether we moved it.
Narendraprasad Upudhyay
ANSWERS FORThe weekly rhythm: a working demo every week, no silent weeks.
Rahul Terwankar
ANSWERS FORScreens your team understands without a manual.
Shailendra Nagori
ANSWERS FORThe engine room: data, logic, and the rules your business runs on.
Pratik Hadawale
ANSWERS FORIntegrations that don't break at 3 a.m.
Harshvardhan
ANSWERS FORDeploys that don't scare anyone, and uptime you never have to think about.
Akash Kushwaha
ANSWERS FORThe part of the software you actually touch.
Huzaif Shaikh
ANSWERS FORSpeed you can feel in the browser.
Ammarah Ayubi
ANSWERS FORThe tests that catch it before you ever see it.
Lokesh Ajmera
ANSWERS FORBreaking it before it ships.
Jaffar Rehan
ANSWERS FORThe edge cases nobody thought of.
Saikat Ganguly
ANSWERS FORRegression: what worked last week still works this week.
The four pillars, as promises.
Let's open the box together.
Tell us the problem and what it's costing you. We'll tell you, plainly, what it takes to fix, what that costs, and whether we're the right fit.
Open a conversation