A $30,000 project sounds like a win until you do the math. Three months, 15 hours per week, a difficult client who changes direction weekly, a final product you wouldn’t put in your portfolio, and by the end, your effective rate is $35/hour, you’re exhausted, and you missed two inbound opportunities because your calendar was full.
The problem isn’t the price. It’s what the project costs you beyond the invoice.
Every project you take fills your calendar, consumes your mental energy, and defines what kind of work you’re known for. The wrong projects don’t just pay less than they should, they actively block better opportunities, keep your portfolio pointing in the wrong direction, and condition you to work with clients who aren’t worth your best effort. Saying no strategically is not about being selective for the sake of ego. It’s about protecting the conditions that allow you to do great work and attract the clients who make great work possible.
The 5-Question Opportunity Filter
Run every significant incoming opportunity through these five questions before agreeing to a proposal call. Do this in writing, one sentence per answer, so the pattern becomes visible over time.
Question 1: Is this the type of client I want more of?
This is the portfolio question. If you take this project and it goes well, you’ll get referred to similar clients for similar work. If you take a project with a mid-size e-commerce company doing basic Shopify work and you actually want to work with SaaS companies on complex integrations, every successful Shopify project moves you further from where you want to go.
Define your ideal client profile in three dimensions: industry, company stage, and problem type. Any opportunity that scores 2 or fewer out of 3 gets a scrutiny flag. It might still be worth taking, but your eyes need to be open about what it’s building toward.
Question 2: Does this project expand my capabilities or keep me in place?
Not every project needs to be a stretch. But if 80% of your work in the last 12 months has been the same type of project at the same level of complexity, you’re not building a trajectory, you’re maintaining a plateau. Projects that force you to develop new skills, operate in a new context, or produce a type of result you haven’t achieved before are worth taking at lower margins. Projects that require skills you’ve had for 5 years and produce no new capability are worth taking only at premium margins.
The question isn’t whether the project is interesting, it’s whether it moves your skills forward or keeps them flat.
Question 3: If my best client called with a project at the same time, would I have capacity for both?
This is the scarcity-reality check. Most solos underestimate how much capacity a project consumes. They say yes to a $25K project thinking “I can fit this in,” then a $50K opportunity shows up from a dream client and they’re stuck.
The capacity test: assume you’ll say yes to this project. Now imagine your best client calls next week with a project of the same size. Do you have the physical hours for both? Do you have the mental bandwidth for both? If the honest answer is no, the incoming opportunity needs to either be delayed, declined, or sized down. Don’t fill your calendar with second-tier work and then turn away first-tier opportunities.
Question 4: Would I be excited to include this in my portfolio in 2 years?
Your portfolio isn’t just a record of what you did, it’s a filter that attracts future work. Clients who find you through your portfolio self-select based on the work they see. If your portfolio shows e-commerce work, you’ll attract e-commerce prospects. If it shows enterprise SaaS work, you’ll attract enterprise SaaS prospects.
Before accepting a project, ask yourself: when this is done, will I want to write a case study about it? If the answer is no, because the client is in an industry you want to leave, or the work is below your current capability level, or you already have 4 similar case studies, that’s meaningful information. You can still take the project, but you’re trading future positioning for current revenue.
Question 5: Does the client’s behavior in the sales process signal how they’ll behave in delivery?
This is the most predictive question and the most commonly ignored. How a client behaves before they’re paying you is the clearest indicator of how they’ll behave after. Clients who change the scope mid-proposal do it mid-project. Clients who don’t read documents before commenting on them don’t read documents during delivery. Clients who negotiate every line item on the proposal negotiate every invoice.
The behaviors to flag: requests to start before a contract is signed, pressure to begin work before a deposit is paid, vague scope that the client is unwilling to define, repeated contact outside agreed communication channels, or a dismissive attitude toward your process or requirements.
One client with difficult behavior drains the energy you need to do great work for your other clients. The contamination effect is real, a toxic engagement makes you worse at everything adjacent to it. The revenue from a difficult client is rarely worth the opportunity cost of what it does to the rest of your work.
The Polite-No Scripts
Here are three scenarios with exact language:
Scenario 1: Wrong type of work
“Thanks for reaching out about this, I can see it’s an important project. I’m not the right fit for this one. My focus right now is [specific area], and this project is more squarely in [other area]. I’d recommend talking to [name or firm type]. Happy to connect you with someone specific if that would help.”
Scenario 2: Capacity constraints
“I appreciate you thinking of me. My calendar is currently full through [month] and I don’t think I could give this project the attention it deserves in your timeline. If timing shifts on your end, I’d welcome a conversation. Alternatively, I’m happy to point you toward someone who could start sooner.”
Scenario 3: Warning signs from the sales process
“I’ve given this real consideration and I don’t think we’re the right fit for each other right now. I want to make sure you work with someone who can give you what you’re looking for, and I don’t think I’m that person for this project. I genuinely hope you find the right partner.”
Note what’s absent from all three: apology, over-explanation, and negotiating language. Don’t say “unfortunately”, it invites pushback. Don’t say “maybe in the future” unless you mean it. Don’t offer a reduced rate as an alternative to a no, if the work doesn’t fit, the price isn’t the issue.
The Scoring System in Practice
Over time, track your opportunity filter results. For every project you’ve declined, note: What happened in the 30 days after? Did better work come in? Did you have more capacity for existing clients? Over 6-12 months, this data tells you whether your filter is calibrated correctly.
Most solos who start scoring opportunities rigorously discover they were underscoring the questions about client behavior and capacity, the two factors most predictive of actual project quality. They were overscoring revenue and brand name, which feel impressive but often correlate poorly with actual outcomes.
“I’d love to work with you” is not a business strategy. Every yes to a bad opportunity is an implicit no to a better one. The solos who grow fastest aren’t the ones who say yes most often, they’re the ones who say no to the right things so they can say yes fully and completely when the right things arrive.
The filter doesn’t mean turning away most opportunities. It means running every opportunity through a consistent lens so that your yeses are deliberate and your nos don’t cost you anything except the wrong clients. Done consistently, this practice reshapes your client roster inside 12 months.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
