Back to the Journal
Article · Behind Rokn · 2 min read

The work was connected. The tools weren’t.

Why a freelance software engineer started building a home for the whole client relationship.

A folder is not a client relationship.

A client sends new website content. It arrives in an email, while the previous version sits in a shared drive. The tasks are somewhere else. So are the invoice, the domain renewal and the password they will ask for again in six months.

None of these is a big problem on its own. Together, they become a second job: keeping track of the work around the work.

Start with the relationship.

Rokn grew out of that frustration. The idea is simple: a client should stay the same client as a conversation becomes a proposal, a project, an invoice and an ongoing support relationship.

Files, tasks, time and documents belong with that context. You should be able to return to a project and understand what happened without reconstructing it from five different tools.

More time building for clients. Less time keeping the tools around the work in sync.

Bring one project together.

You do not need to reorganize your whole business on day one. Start with a client and a project. Add the files you need, plan the next task and bring the client into the loop when you are ready.

That is the direction behind Rokn: the essentials of a digital service business, connected in one workspace.

Bring the work together.

Start with one client project