A growing project portfolio is not the same as a stronger product
Working with large enterprises and their designated system integrators can open opportunities for a smaller SaaS vendor. It can bring funding or projects, but a change in a partner’s strategy can also bring ongoing development to a halt.
In my experience, this meant repeatedly navigating between individual project requirements and the value we wanted to preserve in our own product. Responding to a client matters. Yet those responses do not automatically add up to a stronger standard product.
Keep a main branch of your own
Serving several clients divides limited development capacity. A feature essential to one may be irrelevant to another. If every request becomes central, the purpose of the product becomes harder to see.
I think of the alternative as maintaining a “main branch.” This means more than a branch in a source repository: it is the value we intend to keep providing as clients change, and the standard product that supports it.
Custom work is not inherently wrong. What matters is distinguishing project-specific responses from what should become part of the shared product, and preserving the reasoning behind those decisions.
What we build is also what someone must inherit
Hardware, engines, back ends, applications and front ends: expanding the scope of in-house development also expands maintenance and coordination responsibilities. In a small organization, these responsibilities can concentrate in a few people.
Which parts must we own, and which can work with external systems? For me, this is also a question of whether the product can be maintained after its original developers have moved on.
What remains after ten years
Over ten years, products and features accumulate. Some developments are discontinued. People leave, and sometimes there is no engineer available to take over. The maintenance obligation remains even when the context is no longer easy to recover.
That is why I came to see a knowledge base—a “second brain”—as necessary. The next article explores how surviving materials might become organizational memory that the next person can actually use.
The banner is an AI-enhanced concept visual based on a knowledge graph.
