Release day adds a new obligation.
There is now a product somebody may rely on, a support address they may write to and a set of expectations attached to its name. The work has acquired a future.
I have been a director of Partech since 1997, working in operations and finance. Those functions follow a product beyond the moment when its first version is ready. They ask what it takes to keep the thing available and whether the company can continue to provide it with care.
Count the work around the feature
An implementation is only one part of a product’s cost. There is time spent explaining it, testing changes, preparing releases, answering questions and keeping up with the platforms it runs on. There may be services to pay for and tools to replace. There are also small administrative tasks that become important when they are missed.
A feature can appear inexpensive while adding a lasting complication to several of those jobs. A setting needs documentation. A new platform needs testing. Another way to pay creates another set of questions to answer.
It helps to see these as part of the decision while there is still a choice about what to build.
A catalogue is a set of commitments
An independent studio can make a wide range of things. That is one of its pleasures. Each additional product also asks for a share of attention.
A small app may need very little intervention for a while, then require work because the world around it has changed. A store changes a requirement. An operating system behaves differently. Somebody finds a problem that had not appeared in testing.
The catalogue therefore needs more than enthusiasm for the next release. It needs a practical view of the products already in people’s hands. Which ones need attention? Which questions keep returning? Is the explanation on the website still accurate?
None of those questions looks particularly striking in a launch announcement. Their answers are part of whether a person can keep trusting the product.
Keeping independence practical
Finance can make this conversation more useful by making the obligations visible. Time, recurring costs and the capacity to respond all belong in the picture. So does the value of retaining a product that serves a clear purpose.
The decision is not always to expand. Sometimes it is to improve an existing application before starting another. Sometimes it is to keep the scope small enough that the product remains straightforward to support. Sometimes a service needs to be retired, with a clear explanation and a reasonable route for the people using it.
These are ordinary operating decisions. Taken together, they shape the sort of company we can continue to be.
Partech’s work has changed over the years, from solutions built for clients to a growing collection of our own software. The responsibility has stayed recognisable. If our name is on a product, we should understand what it takes to keep looking after it.