We’re not building
a productivity tool.
We’re building Mellovy for the next kind of company.
I · The trap of the ordinary
I want to change the world. I keep getting pulled into busywork.
You get faster, and the reward is more to do. A tool promises you less of it, and then you’ve got a Slack that keeps buzzing and an inbox that’s fuller than yesterday’s. You clear the queue, but it doesn’t get any easier to think. It all comes back in smaller pieces. And by the next time you log in, they’ve stacked back up on your desk.
Now you’re told the fix is more agents. You tell them what to do, you watch them and you correct them all day. Give two people twenty agents each and point them at different goals, and you get forty agents producing slop. And somebody has to clean that up by hand, and most days that’s you. We’re sick of acting like that isn’t part of the job.
II · The AI-native company
Nobody was building the company.
Everywhere we looked there was one more agent you had to watch and correct. But an AI colleague can do a lot more than that. It reads what’s going on and thinks the work through, and then it gets on with it in tools like Slack and Linear. It has a whole computer of its own. When you want to know where it’s at, you watch its screen instead of waiting a week for a status update. And you shape the company in plain words, the way you’d shape a team of people.
That’s what we mean by an AI-native company. You and your AI colleagues share one mission, and you each take responsibility for what you do with it. You’re all judged by the same standards, and when one of you learns something, the rest of you know it too. We don’t see why humans and agents should answer to different rules, and we’re sick of that.
III · Standards beat process
Hell no. That’s not a reason.
When a company grows, it adds process and red tape so it can keep control. But process follows the letter of the law. It ties your strongest people’s hands to the speed of the slowest one in the room. We think that’s unacceptable.
That’s why we worship standards and we reject process. Process tells you how to do your work, and that’s how a company ends up paying A-players to follow the slowest person’s method. A standard tells you what good looks like. We’ll hold you to that. You pick how you get there, because we’re sick of micromanaging it.
IV · The elastic business
You bring the vision. The organisation takes the coordination off you.
When you want to take on more, you don’t have to wait on headcount. From day one you add a colleague when the work needs one, not 3 meetings later when finance finally signs off. And the time you spend managing doesn’t grow every time revenue does.
Removing the human bottleneck doesn’t remove humans. It gives you back the part only you can do. That’s your ambition, your judgment, your taste and your values, and you still make the call on what matters. We take the chasing and the paperwork off you. And we’re furious about how many hours that stuff has cost you so far.
V · Institutional memory
The mistake teaches everyone, once.
In most companies what you know sits in people’s heads. Or it’s in a Google Drive folder, or a Slack thread nobody can find. When someone leaves, what they knew walks out the door with them. And what you learn stays with you, so the next person has to learn it all over again. We’re sick of watching that happen.
You shouldn’t have to keep saying it. When a colleague’s work isn’t good enough, you fix it, and that fix becomes a test that every colleague who could make the same mistake works to. And no agent grades its own work or writes its own memory, because that’s how the same mistake keeps coming back.
VI · Reason to believe
The only limit we accept is physics.
Big promises aren’t new, and most of them turned out to be vaporware and a trust-me deck. We won’t play that game. When we get something wrong, we say so in Slack. We fix it where you can see it, and we write down what it taught us. We’re sick of vendors who never admit they were wrong.
Agents degrade over time even when the model never changes, and errors spread when nothing checks the result. We built Mellovy around the fix the research points to.
VII · Visual artifacts of the future
If something moves, it moves because we finished the work.
Open a few AI sites and you’ll see the same soft cream and the same serif type. Then there’s the terracotta, and a neon glow up top. We’re sick of it. Mellovy isn’t soft.
Giovanni Pintori drew mechanical intelligence for Olivetti. WIRED showed up in the mail like it came from the future. We went back to both because they made a future you didn’t know yet look like somewhere you’d want to be. And ours is warm paper and deep ink, and we cut it with fields of red and yellow, blue and sage.
VIII · What we’re asking
Build what comes next.
Mellovy isn’t for everyone. If you want someone to hand you a process and tell you how you’re supposed to do your work, you’re going to hate this. And that’s on purpose. We’re fine with it. Let the rest be ordinary.
Give ambitious people an organisation that gets better as it grows, and take the bureaucracy away. Teams still win at the top today, and we’re building Mellovy so growing stops making a company slower. We’re furious that the tools took this long to arrive.
We’re Benjamin Sandén and Zander Flamander. For months we got on discovery calls with tech-forward companies and ambitious operators. And when they told us how they explain the job to a new hire, the same thing kept coming up. You do it the old way. We got so sick of it that we wrote this.
About MellovyHELL YEAH. This is the future.
If you read all this and thought hell yeah, then this is for you. We haven’t opened Mellovy yet. But if you join the waitlist, you’ll be one of the first people we invite. And then you get to look at all the work you don’t have to do yourself anymore.
Join the waitlist