We launched LSD Dev Studio three months ago. In those three months, we talked to over 100 people about potential projects — calls, emails, DMs, introductions, referrals, cold outreach responses.
We said yes to 3.
That's a 3% acceptance rate. Not because we're exclusive or arrogant or turning away money for sport. Because the other 97 conversations taught us something nobody tells you when you start freelancing or open a studio: the wrong project costs more than no project.
This post is for anyone who's freelancing, running a small agency, or thinking about starting one. The hardest skill you'll develop isn't writing better code or designing better interfaces. It's learning to say no — and meaning it — when your bank account is screaming at you to say yes.
Month One: The Pressure to Say Yes
When you launch a studio, there's a voice in your head that says: take everything. Any project. Any budget. Any client. Because revenue is revenue, and zero revenue means you're failing.
We felt that. Hard.
The first few weeks, every inquiry felt like a lifeline. Someone wants a website? Yes. Someone needs an app? Absolutely. Someone wants to "pick your brain for 30 minutes"? Sure, why not.
Here's what that got us: five simultaneous conversations with people who had no budget, three "urgent" projects that disappeared after the first call, and one person who wanted us to build a full marketplace for equity in their pre-idea startup.
Zero revenue. Three weeks gone. A growing sense that we were doing this wrong.
So we stopped. We made a rule: before saying yes to any conversation longer than 15 minutes, we'd ask ourselves one question — is this a project we'd be proud to show in our portfolio in six months?
If the answer wasn't a clear yes, we'd say no. Politely, quickly, and without guilt.
That one decision changed everything.
What 100 Conversations Taught Us
After a hundred conversations, patterns emerge. People who reach out to a dev studio fall into roughly five categories:
The Tire-Kickers (40%)
"Just exploring options." "Getting quotes from a few places." "Not sure what we need yet but wanted to chat."
These conversations feel productive because the person is friendly and asks good questions. But they're not ready to buy. They don't have a budget, a timeline, or sometimes even a clear idea. They're researching.
Nothing wrong with that — but spending an hour on a call with someone who's six months away from being ready is time you're not spending on people who are ready now.
What we do now: Send a project brief template and say "fill this out when you're ready, and we'll give you a quote in 48 hours." If they never fill it out, they were never going to become a client.
The Budget Shoppers (25%)
"How much for an app?" "$500 is our budget — can you do it?" "We got a quote for $2,000 from someone else, can you beat it?"
These conversations are short. The person has a budget that doesn't match the scope they're describing. A full SaaS platform for $500. A marketplace with payments, messaging, and reviews for $2,000. A mobile app for "whatever's cheapest."
This isn't about respecting our rates — it's about protecting the client from themselves. If we said yes to a $500 SaaS build, we'd deliver something broken, they'd be unhappy, and both of us would waste months on a project that was doomed from the start.
What we do now: Be honest. "That budget would get you a landing page and a waitlist, not a full product. Here's what a realistic scope looks like at that price point." Sometimes they increase the budget. Usually they don't. Either way, nobody's time is wasted.
The Scope Creepers (15%)
"It's just a simple app." "Basically like Uber but for dog walking." "It shouldn't take more than a few weeks, right?"
These are often good people with real ideas. The problem is they don't understand what they're asking for. "Like Uber but for X" is a $200,000 project, not a "simple app." When you ask clarifying questions, the scope doubles with every answer. "Oh, and it needs chat. And payments. And a driver app. And an admin panel. And ratings."
Taking these projects without a brutally clear scope document means scope creep from day one. The original quote becomes meaningless by week three. You end up working 2x the hours for the same fee, resenting the client, and delivering something neither of you is happy with.
What we do now: Require a filled-out brief before quoting. If the brief reveals a scope that's 10x what the client's budget allows, we tell them. No brief, no quote.
The Delegators (10%)
"Just build whatever you think is best." "You're the expert, I trust you." "I don't want to be involved in the details."
This sounds great until it isn't. Zero client involvement means zero feedback during development. You build for eight weeks, present the result, and hear: "That's not what I had in mind."
Complete delegation only works with clients who've done this before and genuinely trust the process. First-time founders who say "just handle it" usually mean "I don't want to think about this" — which means they haven't thought about it, which means the requirements don't exist yet.
What we do now: We require at least one check-in per week. If a client can't give us 30 minutes a week, the project isn't a priority for them — and it shouldn't be a priority for us.
The Dream Clients (10%)
They know what they want. They have a realistic budget. They've done some research. They respect the timeline. They treat you as a partner, not a vendor. They ask good questions and answer yours clearly.
These are the 3 we said yes to.
Why We Said No to 97
Here's the thing nobody tells you about saying no: it's not about the money. It's about opportunity cost.
A bad $3,000 project takes the same calendar time as a good $3,000 project — but the bad one drains you. You fight about scope. You redo work because requirements changed. You deal with late feedback, ghosting, and "can we just add one more thing." By the end, you've done $6,000 worth of work for $3,000, and you're burned out.
Meanwhile, a good project energizes you. The communication is clear. The feedback is fast. The scope holds. You finish on time, the client is happy, and you have a portfolio piece you're proud of.
Same revenue. Completely different outcome.
We said no to 97 conversations because we'd rather do 3 projects well than 10 projects badly. Three happy clients who refer us to their network are worth more than ten unhappy clients who leave bad reviews.
The 3 We Said Yes To
We won't share names or details — client confidentiality matters. But here's what all three had in common:
-
They came with clarity. Not a 50-page spec — but a clear sentence about what they needed and why. "We need a web app that does X for Y audience because Z problem."
-
Their budget matched their scope. They'd done enough research to know that quality work costs real money. They didn't flinch at our rates because they'd already decided this was worth investing in.
-
They respected the timeline. No "we need it yesterday." They understood that good work takes weeks, not days, and they planned accordingly.
-
They showed up. Responded to messages within a day. Made time for weekly check-ins. Gave feedback quickly and clearly. Treated the project as a collaboration, not a handoff.
-
They were building something real. Not a "what if" or a "maybe someday." They had users waiting, or a launch date set, or revenue depending on the outcome. The project had stakes.
How to Pick the Right Client (A Framework for Freelancers)
After 100 conversations, we built a simple scoring system. Before saying yes to any project, rate it on five factors:
The 5 Green Flags (1 point each)
| Signal | What It Looks Like |
|---|---|
| Clarity | They can explain what they need in 2–3 sentences |
| Budget alignment | Their budget is within 50% of your estimate |
| Responsiveness | They reply within 24 hours during the conversation |
| Respect for process | They ask about your process, not just your price |
| Real stakes | There's a deadline, users waiting, or money on the line |
The 5 Red Flags (−1 point each)
| Signal | What It Looks Like |
|---|---|
| "It's simple" | Describes a complex product as easy/quick |
| No budget discussion | Avoids talking about money until the end |
| Scope inflation | Every conversation adds new features |
| Disrespect for timeline | Wants it "ASAP" with no flexibility on scope |
| Ghosting pattern | Takes a week to reply, then expects you to be instant |
Scoring
- Score 4–5: Take the project. This is a dream client.
- Score 2–3: Proceed with caution. Set very clear boundaries and scope.
- Score 0–1: Walk away. Politely. Quickly.
- Negative score: Run.
We've never regretted walking away from a negative-score project. We've regretted every time we ignored the red flags and said yes anyway.
What Happened With Our 3 Projects
All three shipped on time. All three clients were happy. Two have referred us to other people. One is planning a phase two with us.
That's not a coincidence. It's a direct result of choosing well. When you start with aligned expectations, realistic scope, and mutual respect, projects go smoothly. When you start with misalignment, they fail — no matter how good your code is.
The Hardest Part
Saying no when you need money is genuinely hard. We won't pretend otherwise. There were weeks where we had zero revenue and three bad-fit inquiries, and the temptation to take any of them was real.
But every freelancer we respect told us the same thing: the projects you turn down define you more than the projects you take. Your portfolio, your reputation, your referral network, your mental health — all of them are shaped by the quality of clients you choose, not the quantity.
If you're a freelancer reading this and taking every project that comes your way because you're scared of the gaps — we get it. But start tracking. Score your next 10 inquiries with the framework above. See how many score below 2. Then decide if those projects are actually helping you, or just keeping you busy while going nowhere.
We'd Rather Work With You When It's Right
If you're reading this and thinking "I might be one of those 3%" — here's how to find out.
Fill out our project brief template. Tell us what you're building, your timeline, and your budget range. If it's a fit, we'll give you a quote in 48 hours. If it's not, we'll tell you honestly and point you in the right direction.
We don't take every project. But the ones we take, we build like they're ours.
LSD Dev Studio — Launch Support Develop. We build web apps, mobile apps, animated videos, and digital products for the right clients. See how we work or explore our services.