AD
Episode
428
Interview
Web News

Should You Say No to Low-Budget Projects?

Recorded:
November 4, 2025
Released:
November 25, 2025
Episode Number:
428

When a client comes in with a dream project and a shoestring budget, what should a developer do? In this episode, Matt and Mike break down the low-budget dilemma - why clients under-budget, when it makes sense to try working with them, and when it’s better to walk away. We explore how to trim features without killing quality, how to set realistic MVP expectations, how to handle classic client excuses (“my cousin can do it cheaper”), and how to protect your reputation even when money is tight. If you’ve ever wondered how far you should cut features or whether a project is still worth doing, this episode dives deep into the realities of balancing budget, quality, and your long-term brand.

Listen

Also available on...
...and many more, check your podcast app!

Who’s in This Episode?

Show Notes

The Low-Budget Dilemma

  • What happens when a client’s dream project doesn’t align with their wallet.
  • Why it’s tempting to take low-paying work (portfolio building, word-of-mouth, steady leads, etc.).
  • The importance of assessing why the budget is low - is it ignorance, genuine constraint, or undervaluing the work?

Should You Say “No” or Try to Make It Work?

  • The knee-jerk reaction: “Not worth my time” - and when that’s actually correct.
  • When it might make sense to try to work with a client:
    • Long-term potential relationship.
    • Realistic MVP goals.
    • Chance to establish trust with an honest, communicative client.
  • How to reframe the conversation from “I can’t afford it” to “What can we afford?”

Trimming Features Without Killing Quality

  • Techniques for cutting scope without harming the project:
    • Start with an MVP - focus on one core problem.
    • Remove bells and whistles like animations, advanced CMS features, or integrations.
    • Use templates, frameworks, or existing systems to save dev time.
  • Examples of what’s reasonable to cut vs what undermines the entire project.
  • Communicating reductions clearly - avoiding the “you said it would do that” trap.

When Is It Too Much?

  • Signs that you’ve trimmed the project too far:
    • It no longer achieves its main goal.
    • It’s embarrassing to attach your name to it.
    • You’re earning less than minimum wage when time is calculated.
  • The “quality threshold” test: Would you put this in your portfolio?
  • Knowing when to say: “We’ve cut so much that I can’t deliver a professional result anymore.”

Should You Ever Deliver a Sub-Par Project?

  • The dangers of accepting “just to get the money” jobs:
    • Reputation damage - unhappy clients talk.
    • Burnout from underpaid work.
    • Long-term opportunity cost (what you could’ve been working on instead).
  • Rare exceptions: doing favors, building goodwill, testing a niche, or helping a friend - but even those should have boundaries.

Handling Client Excuses and Pressure

  • Classic lines:
    • “My cousin can do it cheaper.”
    • “I got a lower quote already.”
    • “It shouldn’t take that long.”
    • “It’s an easy project.”
  • Strategies for handling them:
    • Stay calm, don’t match tone - educate instead.
    • Use the “good, fast, cheap - pick two” framework.
    • Emphasize value, not just price (hosting, security, CMS setup, UX polish, etc.).
  • When to walk away - you can’t win every negotiation.

Reputation vs. Revenue

  • Why reputation is your long-term currency.
  • Delivering sub-par work might earn quick cash but cost you future clients.
  • Alternative strategies:
    • Offer a phased project plan (“Let’s start small, expand later”).
    • Recommend other developers who specialize in low-cost builds.
    • Maintain your brand’s perceived quality - even in small jobs.

When a Shoestring Project Can Work

  • Scenarios where doing a low-budget project might make sense:
    • Strategic partnerships or exposure (but vet carefully, high failure potential).
    • Experimentation (e.g., testing new tools or workflows).
    • Quick-turnaround “microsites” with well-defined limits.
  • Setting boundaries in your proposal - limited revisions, clear deliverables, up-front payment.

Additional Tips & Red Flags

  • Add-on traps: clients who keep “just adding one small thing.”
  • Recognizing a bad client early - communication style, unrealistic comparisons (“Why can’t it look like Apple’s site?”), lack of respect for your time.
  • How to politely decline:
    • “I don’t think I’m the right fit for this budget, but here’s a suggestion.”
    • Maintain professionalism - burned bridges can cost referrals.


How to support the show

Patreon

Prices subject to change and are listed in USD

  • Support the show from as little as ~$1/month
  • Get a shoutout at the end of the episode (while supplies last) for just ~$3/month
  • Help support the HTML All The Things Podcast: Click Here

Scrimba Discount - Coding Courses!

Learn to code using Scrimba with their interactive follow-along code editor.

Join their exclusive discord communities and network to find your first job!

Use our affiliate link for a 20% discount!!

  • Click the link to take you to the Scrimba site
  • A pop-up should appear on your screen with the discount amount and instructions on how to claim it
  • Discount is for new accounts only

We receive a monetary kickback if you use our affiliate link and make a purchase.