Owning your tools again

There was a period — not so long ago — when software came on a disc, installed on your machine, and worked as long as you chose to use it. The relationship was simple: you paid once, the tool was yours. You could customize it, keep it running an old version while you finished a project, and know that Tuesday's update wasn't going to change what your workflow depended on.

That world is largely gone. In its place is one where your tools are services, your access is conditional, and the decisions made by a company you have no relationship with — about pricing, about features, about which capabilities survive the next roadmap review — become your decisions without your input.

This is the texture of renting your workflow.

What renting your workflow actually means

Rental is not always bad. There are real benefits to services: continuous updates, shared infrastructure, work that follows you across devices. We're not arguing for a return to the disc era. But the rental model carries costs that are rarely made explicit at sign-up.

The first is control. When your workflow runs entirely inside a closed platform, every change that platform makes is a change to your work. The interface that suited how you think gets redesigned. The integration your process depended on gets deprecated. Features you were promised arrive years late or not at all. You can complain, but you can't refuse.

The second is portability. When your work and your history and your context live inside a platform you don't control, leaving is expensive — expensive in time, in migration effort, and in the loss of whatever the platform knew about how you worked. Portability that is technically possible but practically painful is not real portability.

The third is the negotiating position that flows from the first two. When switching costs are high, the platform's interests and your interests diverge structurally. You stay not because the tool is the best option but because leaving is harder than tolerating the way things are.

What owning your workflow looks like now

Full ownership in the old sense — software on your machine, no external dependencies — is not a realistic goal for AI-assisted work. The capabilities involved require infrastructure that doesn't fit on a local disc. But there is a spectrum between "fully owned" and "fully rented," and it matters which part of the spectrum your tools sit on.

The markers of a healthy position on that spectrum are not complicated: your data should be exportable in formats you can actually use. Your history and context shouldn't be held hostage by the platform. The core capabilities shouldn't disappear because of a pricing restructure. And you should be able to run your workflow across surfaces — a web app today, a desktop application tomorrow, a terminal the day after — without re-establishing who you are each time.

These are not radical demands. They are what it looks like to treat professionals as people with their own needs rather than a captive audience.

What we are building toward

The platform we are building at askFinz is designed to sit on the healthier end of this spectrum. The goal is not to create the deepest possible lock-in; it is to be the place where professionals choose to work because it is the best place to work — and to remain worthy of that choice by keeping the exits clear and the capabilities real.

This requires making decisions that are not always easy. Maintaining portability means not optimising purely for stickiness. Keeping data exportable means not treating it as something you're storing on behalf of users so much as something that belongs to them. Making the tool work across surfaces means resisting the temptation to use cross-surface friction as a retention mechanism.

We think these are the right decisions. But we also think they are only sustainable decisions if people choose platforms on the basis of them. The market for professional tools gets better when professionals ask harder questions about what they're actually agreeing to when they sign up.

Own your workflow. It is worth the effort.