The SaaS Transition Manifesto
We are uncovering better ways of transitioning from SaaS applications to our own solutions for internal line-of-business apps. Through this work we have come to value:
Start With Requirements
Before doing any transitions, make sure you document the business processes you are transitioning in detail. You cannot transition what you do not understand. Shared understanding - good and bad - becomes the system.
Security Always Matters
Regardless of what we do, we cannot compromise with data, cyber, and supply chain security - customer's or ours.
Business Continuity over TCO
Software is the tool, not the goal. Even if there is a more efficient system or way to do a task, if the transition constitutes a significant business risk in the short to mid-term, it should be reconsidered.
TCO over Convenience
If the real (including hidden costs on both sides) total cost of ownership of a SaaS solution is greater than an alternative that is less convenient to current stakeholders, the TCO makes more business sense.
Business Processes over Systems
The primary transition unit to be considered is a business process, not a system. Every process must have an owner and ideally be scoped to one group of primary users.
80% over 120%
A ready solution that does 80% of everything needed and can be implemented and used right away is better than a custom one that can be extended indefinitely.
Function over Form
A solution that works, is functionally complete, and consistent in its performance but has quirks in its interface or does not have a sleek design is better than the reverse alternative.
Open-Source over Low-Code
Most common business processes have ready open-source solutions with solid communities. Research and find them with AI.
Low-Code over Vibe-Code
Low-Code solutions (provided they are not paid per user) are more efficient to maintain, operate, and scale than vibe-coded solutions for line-of-business apps (that nobody understands the inner workings of) in the long run.
Vibe-Code over Build
If nothing above works, before building a custom solution for internal use, always try creating it through an AI-first approach. Even if that is not the final solution, the ideas it represents can be validated quickly and efficiently with real users.
That is, while there is value in the items on the right, we value the items on the left more. In exactly that order.