Two months to launch, and a system that kept them fast afterwards

Where they started

io.net had capital, a strong technical core, and a launch date two months out. What they did not have was a product ready to meet it. The design system was scattered and inconsistent. The UX screens had been built without auto layout, so every change meant redoing work by hand. The product worked in principle. It did not yet read as something investors and users could trust.

What they had already tried

The work had gone to someone else first, and that engagement ran into deadline trouble. That is the expensive kind of failure when the launch date is already set. By the time they came to us the calendar had not moved, but the work had not moved either.

What we did

Product design and the design system were the core of the engagement, and we stepped into the web design where it mattered.

We rebuilt the design system properly, on auto layout, with real components. io.net did not ask for this. They wanted something lighter, because a detailed system feels like time taken away from the launch. We argued for building it right, and built it.

We redesigned the core product screens against that system, so consistency stopped being something to police and became the default.

And we worked to their launch date rather than our own comfort. Everything shipped inside the two months.

What changed

They launched on time. The decision they had not asked for turned out to be the one that paid off most. After launch, new screens could be designed in a fraction of the time, because the system was already there to build from. The detour was what let them keep moving.

The feedback from investors and users kept landing on the same word: clear. Not impressive, not clever. Clear. For a product this technical, that is the harder thing to earn.

Today

io.net went on to reach a one billion dollar valuation.