Leadership

111 posts
These small dopamine hits

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 you shouldn't let customers pay for features

Why you shouldn't let customers pay for features

Selling bespoke features to customers might seem profitable, but it changes your SaaS business model. Instead of a scalable product, you become a service provider, stuck maintaining one-off features. Learn why this approach is risky and how to build for long-term success.

🌶️ Death by a 1000 tweaks: the absurdity of maintaining your own UI library

🌶️ Death by a 1000 tweaks: the absurdity of maintaining your own UI library

The best products aren’t built by obsessing over pixels but by delivering real value. Without a clear UI framework, teams drown in design tweaks instead of shipping features.

How to start growing talent in-house

How to start growing talent in-house

Startups thrive on rapid growth, but when it comes to scaling talent, they often hit a wall. Enterprise-style feedback systems sound great—until they become a productivity sink. So how can you build structured talent development without overcomplicating things?

When to hire senior developers vs. juniors - the perfect team composition

When to hire senior developers vs. juniors - the perfect team composition

Senior developers bring expertise, long-term vision, and stability to complex SaaS projects, while juniors—when guided effectively—offer cost-efficiency and faster execution for well-defined tasks.

Finding your North Star Metric

Finding your North Star Metric

Scaling a startup is exciting—but chaotic. Teams often chase different priorities, leading to silos and lost focus. A North Star Metric can realign everyone around what matters most. Curious about how this works?

How to stop depending on that one developer

How to stop depending on that one developer

Key Person Risk (KPR) arises when a team relies too heavily on one specialist. To reduce this, shift their role to an advisor. The specialist guides, others do the work. It’s slow at first, but builds team knowledge, confidence, and better documentation.

Why founders need to care more about software licensing and SBOMs

Why founders need to care more about software licensing and SBOMs

Learn about the importance of SBOMs and software licensing for your SaaS startup.

How to manage technical debt as part of your agile process

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.

You’ve successfully subscribed to madewithlove
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.