The work should
feel like yours.

I’ve spent more than twenty years using creative software. The good parts are easy to recognize: a tool that does what you expect, a detail you can change without fighting the interface, a file you can open again tomorrow. Those are the things I keep coming back to.

But taking an idea from a visual design to a working product often means moving it between tools, rebuilding decisions and paying for another service along the way. I want to make that journey more coherent.

Design decisions should travel.

Layout, components, tokens, content, motion and delivery belong to the same piece of work. In MODO, I’m bringing them into one environment so a decision made on the canvas can continue into a website or native source project. Export and publishing have different requirements; they should be visible, understandable steps.

Your computer is a good place to start.

MODO works with local project files. After the first online activation, you can keep designing and saving offline. Keep portable .modo copies, export your output, use your own repository and choose where your work goes next. Online services still need a connection, but they should not be a prerequisite for moving a layer or finishing a layout.

Useful should also be within reach.

I want students, freelancers and small teams to have room to experiment without another expensive subscription deciding whether an idea is worth trying. Today, access is free during the beta. The longer-term model is still to be defined; I would rather be honest about that than make a promise I cannot responsibly keep.

AI is optional. If you use it, a compatible agent can work through MCP with the permissions you allow. You choose the provider and keep its existing costs in view. The visual tools need to stand on their own: predictable spacing, readable controls, reusable design decisions and files that remain useful outside MODO.

Build it with care. Then open the conversation.

Today MODO is beta software. There are rough edges, release checks to finish and workflows that need more real-world testing. I’m asking early participants to use it, question it and report what breaks. That feedback is part of making a useful tool, not a claim that it is already finished.

Later, I intend to open the code and invite community contributions through proposals and review. That process is not available yet. No specific licence or opening date has been decided. MODO’s logo, identity and trademarks remain mine; opening a contribution process will not make the brand a shared asset.

I want MODO to earn a place in your daily work through the quality of what it helps you make. One reliable operation, one finished project and one useful conversation at a time.