Too many projects, and everything feels important

You've got product ideas, customer requests and internal improvements all competing for the same small team. Each one has a good reason to happen. Together, they're stopping the right things from getting finished.

Let’s talk

A 20-minute call to look at what's on your list.

A longer list won't create more capacity

Say it's Monday. Over the weekend you thought of a feature that could win a big customer, a client asked for something on Friday afternoon, and the internal tool you've been meaning to fix has started to hurt. All three are sensible. All three land on the same few people, who are already part-way through something else.

So work gets started before something else is finished. Your team switches context, deadlines move and you spend more time resetting priorities than seeing them through. Everyone is busy, and the updates are mostly about what has started, because very little has actually closed.

That's a hard position to be in, because you are not short of good ideas. You're short of a way to say not yet. Every project has a reason behind it, so choosing between them feels like letting something good go, and it's easy to keep everything alive instead.

If you've been searching for "too many priorities startup", you probably don't need another productivity trick. You need a clear call on which projects deserve your team's limited capacity, and permission to leave the others alone.

Working out how to prioritise projects as a founder means making trade-offs between good ideas, not just removing bad ones. You shouldn't have to make those calls alone while also keeping delivery moving.

Sound familiar?

  • Every new idea becomes another priority, without anything coming off the list.
  • Your team is busy across several projects, but very little gets finished.
  • You keep changing direction because there isn't one agreed order of work.
  • Developers pick up what feels most urgent, because nobody has told them the order.
  • You hesitate to drop anything because every project has a good reason behind it.
  • Progress updates are about what's started, and rarely about what's finished.

Why everything ends up feeling important

When you're close to every project, each one looks essential. You know the customer behind it, the reasoning, the opportunity. Nobody else has that view, and nobody else has permission to say that something should wait.

Without a shared order of work, each person makes their own decision about what to pick up, usually the loudest request or the one most recently mentioned. That's how a small team ends up overloaded with no one at fault. The missing piece is a single agreed list, with someone responsible for keeping it honest.

Give your best ideas an honest order

For project prioritisation, small team capacity has to be the starting point. You bring the full list. I assess impact, effort, dependencies and risk, then recommend what to do, park and drop. You make the final calls with a clear picture of the trade-offs. Together we turn the decisions into a 90-day roadmap your team can actually work from.

You get a recommendation, not a menu of options. If I think a project should be dropped, I'll say so and explain why, and you decide.

Put everything on one list

You share the ideas, commitments and half-finished work. I build a project inventory so the decisions reflect the whole picture, not just the loudest request.

Make the do, park and drop calls

I score the projects and explain my recommendations. You decide where the business should focus, with the capacity and consequences in view.

Keep the priorities honest

You leave with a 90-day roadmap and a clear handover. If you want ongoing delivery support, I can keep the agreed work moving and help you assess new ideas.

Explore the packages

What you leave with

This work is usually done in a two-week Founder Focus Sprint, with a fixed scope so you know what you're getting:

  • A scored inventory of every project on your plate
  • A do, park and drop list, with the reasoning behind each call
  • A 90-day roadmap with owners and dates
  • Process and tool recommendations
  • Two workshops with you and your team
  • A written handover
See the packages for how it runs

What it looks like afterwards

You open one clear list and know why every project on it is there. Two or three things are moving at a time, each with an owner and a date, and the rest are parked with a point to revisit them or dropped without guilt. Your team knows what to pick up next, so they stop guessing and you stop being asked.

New ideas still arrive, because that's what happens in a growing company. The difference is that they go on a list and get assessed, instead of interrupting what's already in progress. And because the work is finishing, there is something to show for it: shipped features, closed projects and a team that can see what it's working towards.

That is where the capacity comes from. Your team doesn't need more hours. It needs fewer things in flight, so the work that matters gets finished.

Is this right for you?

This suits you if you run a software or SaaS company with a small team of up to about 20, you have more good ideas than capacity, and you're open to hearing a straight recommendation about what to drop.

It's probably not for you if you already have a clear list and the team is delivering it well, or if you want someone to simply add more projects to the pile. The value here comes from deciding what doesn't happen.

Questions founders ask

Joshua Reynolds, fractional delivery partner for software founders

Bring the messy list

You don't need to prioritise it before we speak. That's the work we'll do together.

Let’s talk

A 20-minute call to look at what's on your list.