What are you working on?

Most projects are scoped as a fixed piece of work with a defined outcome, agreed before anything starts. Longer engagements run monthly instead. What moves the number is scope and how much of the system gets built alongside the product, which is why the first call is mostly us asking questions.

We scope to what two people can do well, and we say no when a project needs more than that. Both of us work on every engagement, so there is no junior handoff and no account layer between you and the people doing the work.

We stay through the build. That means reviewing what gets implemented against the design, answering questions while your team is working, and changing the design when engineering hits something that does not hold up. We are designers, so we are not writing your production code, but the system gets updated as new cases appear rather than going stale the moment it ships.

Files with every state and edge case defined, and tokens exported in DTCG format rather than values someone reads off a screen. Your build still transforms that export into whatever your platform needs, and we shape the export so it fits the structure you already use. After that it is mostly availability, since most handoff problems are questions that nobody had time to ask.

It is yours, documented so your team can extend it without us. If you would rather not carry it internally, we can stay on to maintain it as the product grows, adding components and keeping the documentation current. Plenty of clients do the first, some do the second, and it is not a decision you have to make upfront.

Zagreb, Croatia. We work with teams wherever they are, and for US hours that puts your morning in our afternoon, so there is a workable overlap window every day rather than a handoff. Calls when something needs talking through, written updates otherwise. In any case, you know where to find us, wherever you are.