Saying no to bad projects without hiring a big team

Why this comes up

Every month a client asks us about saying no to bad projects. The short answer is: start smaller than you think.

No jargon, no tool worship. Just the order we do things in and why.

Working out a budget? See how much a website costs in Canada.

Making it easy for the customer

Customers judge saying no to bad projects in about five seconds. They are asking three silent questions: what is this, is it for me, what happens if I tap the button. Answer them above the fold.

The best examples of saying no to bad projects are boring on purpose. Clear words, obvious next step, nothing blinking. Personality lives in the copy and the photography, not in animation for its own sake.

Measuring whether it worked

Plan the second month while you are planning launch week. Saying no to bad projects that nobody owns after launch decays quietly, and decay is harder to sell to your team than a fresh build.

Write for the person who is tired, on a bus, on a cracked screen. If saying no to bad projects works for them it works for everyone else too.

What we would do differently

Almost every failure we have seen with saying no to bad projects traces back to skipping the boring middle: naming things clearly, writing the confirmation message, testing on a real phone with real thumbs.

Write down the single outcome you want from saying no to bad projects before touching a tool. One sentence. If you cannot write it, the project is not ready — and no amount of design will rescue a fuzzy goal.

• ✓A plan for month two, written down
• ✓A backup and a way to restore it
• ✓One sentence describing who this is for
• ✓A price or a range, in plain numbers
• ✓Proof: reviews, photos, real names
• ✓Legal pages linked in the footer
• ✓A support path that answers within a day

How much it should cost

Budget attention, not just money. Saying no to bad projects works when one person owns it and reviews it weekly for a month. After that it mostly runs itself.

Pick one number to watch. For saying no to bad projects it is usually completed actions — bookings, orders, replies — not visits. Visits flatter you; completions pay you.

Keeping it alive after launch

Keep a short log of what you changed and what happened. Six months of notes about saying no to bad projects is worth more than any course.

Price it end to end. A cheap start plus a year of patching is rarely cheaper than getting saying no to bad projects right the first time, and the patching arrives when you are busiest.

Questions people ask

Do I need to be technical to handle saying no to bad projects?

No. You need to make decisions and supply real information. We handle domains, hosting, deployment and the technical maintenance.

What does saying no to bad projects cost with Buy Me App?

It is part of a fixed package price with the domain and first year of hosting included, so there is no hourly surprise at the end.

How long does saying no to bad projects usually take?

For a small business, expect one to three weeks of real work once content is ready. The waiting is almost always content, not build time.