Case Study · Own Product
Cadensa: SaaS from idea to operations.
Multi-tenant time-tracking and business platform. One person took it from idea to a live, EU-hosted system with real payments, holding full product, technology and operational responsibility.
The problem
Time data is only valuable if the team records it and the manager can use it.
How can time tracking be easy for team members and truly useful for managers?
Positioning
Who it is for, and where the wedge is.
Cadensa was built for EU agencies and hourly-billing teams, where a time entry is a line on an invoice. The wedge is data sovereignty: all data stays in the EU, and the GDPR tooling works on the free plan too, not only on the paid ones. Against the large US time trackers that is a real difference.
A difference is only worth something if the buyer feels it today. Against an EU-hosted local competitor the same argument sets you apart from nothing, and it will not move a team that is content with the tool it already uses. That question is hard to ask from inside the product, which is exactly why we start every client engagement with it.
Full responsibility
The product had to be designed alongside the code.
Key decisions
Every layer of SaaS architecture is a product decision.
- 01
Multi-tenant operation
Not a technical detail: it settles data isolation, permissions, subscriptions and later scaling all at once.
- 02
Vertical product slices
Not one large first release: the daily critical workflows ship first, one working slice at a time.
- 03
Usability against data needs
People only log time if it is easy, yet managers still need accurate data. That is the core product problem, not a UI question.
- 04
Operations from day one
EU infrastructure, live payment integration and a public subprocessor list, including what is not on it and why.
Delivery metrics
Delivery is the proof, not code volume.
The lesson
The product works. It never found a paying market.
I took it to production alone, and learned that building is not the hard part.
Cadensa is live, runs in the EU, ships in five languages and takes real payments: the market had every chance to say yes. It still never built a paying customer base. We do not hide that, because it is exactly where the value is: the risk sits in choosing the problem, not in delivering it. That is why every engagement starts with Outcome Discovery, and why we never measure product success in lines of code.
Next step
Building your own SaaS product?
We apply Cadensa experience from Outcome Discovery through product architecture to launch, including the lesson the market taught.