From our SaaS audits
What we find inside SaaS companies
Patterns from the technical due diligences we run for investors and boards.
Technical debt
Due diligence for AI startups: what actually matters
Founders and investors due diligence: how to dig beneath the “AI-powered” facade and verify that their systems won’t break in secret.
The enshittification of the internet: are you building value or friction?
AI agents shouldn’t become CAPTCHA solvers: discover how monetisation-driven UX patterns have turned the web into a hostile environment and what honest design can do to reverse the trend.
5 red flags for VCs when planning to invest in Seed or Series A companies
Discover the five most common technical-due-diligence red flags—from undersized or misaligned teams to “just-about-working” codebases—that VCs must spot before writing a cheque.
Why front-end rewrites are more common than refactors
Why do engineering teams keep rewriting frontends? Let’s explore the leadership bias and tech churn that makes refactors feel harder—yet ultimately more sustainable.
Another early-stage SaaS founders dilemma: buy a pre-built app or build one from scratch
Should SaaS founders buy or build their MVP? We compare pre-built apps vs custom development across cost, time, scalability, and code quality — so you can choose the right foundation for your product.
🌶️ SaaS startups should never use microservices. Like, never-ever.
Many SaaS startups over-engineer their architecture with microservices. Here's why that's usually a costly mistake—and what to do instead.
Should we really ship fast and break things?
Should startups test everything before shipping? We break down how to balance testing with product velocity—and why 100% coverage is often the wrong goal.
Eliminating SPOFs: the importance of documentation
Single points of failure (SPOF) in startups lead to lost revenue, delays, and investor concerns. Building a documentation culture early reduces risk and ensures scalability.
These small dopamine hits
Some tasks are a slow grind, like simmering a big meal that takes hours to come together. Others are quick and satisfying—tiny fixes that deliver an instant hit of progress, like a little dopamine boost to keep you going.
Why engineers need a voice in the roadmap
A great product roadmap balances business goals with technical sustainability. Ignoring engineering input leads to technical debt and bottlenecks that slow growth. In this video, we discuss how SaaS teams can integrate engineering priorities into the roadmap for long-term success.
How to manage technical debt as part of your agile process
How to manage technical debt effectively to keep startups agile with strategies for documenting and prioritising technical debt, integrating it into your roadmap, and creating a culture of continuous improvement. Keep your codebase healthy and your team productive with these actionable tips.
How to minimise the impact of developer onboarding
Discover strategies to optimise developer onboarding, minimise costs, and improve time-to-market. Learn how to tackle challenges like code complexity, technical stack adaptation, knowledge transfer, and team integration while fostering a supportive and productive environment for new hires.
How to explain your tech debt to your investors
Learn how to explain technical debt to investors effectively. This guide simplifies its impact on growth and strategies to manage it, helping you enhance company value and align business goals.
Mocking external systems in e2e tests
Struggling with a legacy codebase? We used Playwright to automate QA, reducing bugs. By mocking external APIs like Google Maps, we ensured seamless testing. Learn our implementation with Laravel and Playwright for reliable results.
Embracing brownfield projects & legacy code in SaaS
Balancing innovation with stability is key in managing SaaS legacy code. You explore phased implementations, leveraging existing assets, and continuous learning to maximize legacy code potential. Ideal for tech leads and founders.