Courage as a service
AI is making the knowledge side of consulting cheaper by the day. Teams still avoid the legacy system. The gap is not expertise. It is the structural courage to act on what everyone already knows.
madewithlove
A founder's commitment to their engineering team
Founders juggle endless demands, investors, sales, suppliers, and employees, all while building the plane mid-flight. But with engineering often being your biggest expense, there's one responsibility you can't delegate: ensuring your team builds the right thing.
Jump Start Competition: And the winner is…
The first Jump Start Competition has a winner. Three promising teams, one jury decision, and a strong start to hands-on collaboration with madewithlove. Here are the winners!
Investor Insights #6 - Andreas’ new book: The Economics of Software Engineering
Navigating Outages: lessons from recent cloud failures
Outages can strike unexpectedly, impacting businesses and users alike. In this episode of the SaaS Show, hosts Andreas and Sjimi delve into the recent outages experienced by major cloud providers like Amazon and Cloudflare.
The stainless steel lesson: why boring technology outlasts shiny frameworks
Shiny frameworks promise magic, but like cheap non-stick pans, they scratch, peel, and end up in the bin. Boring technology, like stainless steel, isn’t sexy, but it lasts for decades if treated well. The lesson? Build for the long haul, not the quick thrill.
Legacy vs technical debt: how investors can spot hidden risks in software products
What can investors do about legacy code to prevent your startup from failure? What is the difference between legacy and technical debt?
What would it cost to rebuild this software from scratch?
Evaluating the cost of rebuilding software from scratch involves more than counting development hours; it requires recognising the invisible value of user feedback, lessons learned, and embedded experience.
Making an impact by combining our services
Madewithlove combines interim CTOs and staff engineers to help SaaS scale-ups align strategy with execution and build resilient tech teams.
So you messed up
Everyone breaks production eventually. This guide walks through how to take responsibility, communicate with your team, and make real improvements after something goes wrong. A must-watch for engineering managers and developers.
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.
The hidden cost of API migrations
Forced API migrations without a rollback plan? That’s how businesses lose trust—and money.
Startups don't need corporate culture
Startups often mimic corporates to impress clients or adapt to new hires, but this can stifle the agility they need to succeed. In this post, we explore how corporate habits can slow progress and why startups should prioritise speed and adaptability over rigid processes.
On being an "expert"
Being an expert isn't about always having answers. It's about balancing confidence and humility, knowing when to admit you don't know, and valuing collaboration. True expertise grows through listening, learning, and contributing meaningfully, not just knowing everything.
Five documents every startup should have
Documentation is vital in remote organizations. Companies with little documentation often struggle to get started. With this pragmatic advice however you can get the ball rolling. These are five documents every startup should have, and you can get started with them today.