Guide · Getting help

How to tell if a project is worth paying for

Quick answer

A project is worth paying for when leaving it stuck costs more than fixing it. Add up what it costs you each week in time, errors, lost customers and delayed work, multiply by how long it’s likely to stay stuck, and compare that to a fixed price to fix it. If the stuck cost is higher, it’s worth paying for. If it isn’t, leave it.

What to measure

What the stuck thing costs you every week, and how long it’s been going on.

  • Time.

    Hours a week spent on it, by you and by the team, including fixing what it breaks.

  • Errors.

    Wrong orders, rework, refunds, missed invoices: how many, and what each costs.

  • What stops when you’re unavailable.

    Work that waits for you is work that isn’t earning.

  • Lost customers or delayed work.

    Orders you couldn’t take, customers who left, projects that slipped.

  • How long it’s already been stuck.

    The best guide to how long it will stay stuck if nothing changes.

Rough numbers are fine. The goal is to see the size of the problem, not to produce a spreadsheet nobody trusts.

The math

Weekly cost, times the weeks it will stay stuck, compared to a fixed price to fix it.

  1. Add up the weekly cost.

    Hours a week times what those hours are worth, plus the weekly cost of errors and lost or delayed work.

  2. Estimate how long it will stay stuck.

    If it’s been stuck for a year, assume another year unless something changes.

  3. Multiply.

    Weekly cost times the weeks ahead is the cost of leaving it.

  4. Get a fixed price to fix it.

    A written scope and a set price, not an hourly estimate.

  5. Compare.

    If leaving it costs more than fixing it, it’s worth paying for. If not, leave it, or fix it yourself.

Costs people miss

The owner’s time, and the opportunities that never show up on a report.

The biggest cost is often the owner’s time. An hour you spend fixing the same problem is an hour not spent on sales, pricing or key customers, and that’s usually the most valuable hour in the business. Count it at what it’s worth to the business, not at a salary.

The other hidden cost is growth you can’t take. If the business can’t deliver more, can’t onboard a new customer, or can’t survive you taking a week off, the cost is every opportunity you turn down. A 13-week cash flow forecast also helps here: it shows whether you can afford the fix now, and what waiting does to cash.

What makes yes easy

A written scope, a fixed price, a clear definition of done, and an owner who keeps it running.

  • A written scope.

    What will be built, by when, and who does the work.

  • A fixed price.

    Agreed before work starts, so the comparison is real.

  • A clear definition of done.

    How you’ll both know it’s finished and working.

  • An owner who keeps it running after.

    Someone on your team who runs it once the project ends.

If those four are present, the decision is simpler: you’re comparing a known cost to a known problem. For what a good proposal includes, see what a scoped engagement looks like.

An optional first step

The Blueprint

A paid, two-week look at how your business actually runs. We find where AI and better systems take work off your plate first. You get a written plan, plus a build scope and a fixed quote. If you go ahead with the build, the Blueprint fee is credited toward it.

How the Blueprint works →

  • About two weeks
  • Written plan you keep
  • Build scope and fixed quote
  • Fee credited toward the build

When to say no

When the stuck cost is small, the problem is unclear, or nobody will own the result.

  • The cost of leaving it is smaller than the fix.

    Some problems are annoying but cheap. Live with them, or fix them yourself.

  • You can’t say what’s stuck.

    Find out first. A 30-day systems audit turns a vague feeling into a list.

  • Nobody will own it afterward.

    A fix nobody runs drifts back to where it started.

  • The price isn’t fixed.

    If you can’t know the cost, you can’t compare it.

Your next step

Write down the stuck item. Estimate the weekly cost. Compare it to a fixed price to fix it.

That’s the decision. If you’re not sure which kind of help fits the problem, see consultant vs agency vs hire.

Free one-page guide

How to Tell If a Project Is Worth Paying For

When leaving it stuck costs more than fixing it. One page, ready to print or share with your team.

FAQ

How do I know if a business project is worth the money?

Estimate what leaving the problem stuck costs each week in time, errors and lost or delayed work, multiply by how long it’s likely to stay stuck, and compare that to a fixed price to fix it. If leaving it costs more, it’s worth paying for.

How do I calculate the cost of doing nothing?

Add up the weekly hours spent on the problem times what those hours are worth, plus the weekly cost of errors and lost or delayed work. Multiply by the number of weeks it will likely stay stuck.

Should I pay a consultant or fix it myself?

Fix it yourself if you have the time and know how, and your time isn’t better spent elsewhere. Pay for help when the stuck cost is high, the fix needs skills you don’t have, or your time is worth more on sales and customers.

Why does a fixed price matter?

Because it makes the comparison real. With a fixed price you’re comparing a known cost to the cost of being stuck. With open-ended hourly billing, the cost of the fix is a guess.

Want it built and running?

Write down the stuck item. Estimate the weekly cost. Compare it to a fixed price to fix it. That’s the decision.

If you want a fixed price to compare against, that’s how we work: a written scope and a set price before any work starts.

Scope your project