Skip to main content
Back to Learning Hub
Founder Notes

Why I Don't Take Every Project

Focused project planning setup with notes for evaluating client work

When I started Jaiye Labs, I said yes to everything. A restaurant wanted a website? Sure. Someone needed a WordPress plugin? On it. A startup wanted "something like Uber but for dog walking"? Let's talk budget.

I needed the revenue. I needed the experience. And I needed to learn what kind of work I actually wanted to do.

It took about a year to realize that saying yes to everything was making us worse at everything.

The turning point

I took a project that was technically simple but operationally a nightmare. The client changed requirements weekly. The scope tripled. The budget didn't. I was working nights and weekends on something I didn't believe in, for a rate that didn't justify the stress.

When it finally shipped, I looked at it and felt nothing. Not proud, not relieved. Just empty. That's when I knew something had to change.

What I say no to now

Projects where the founder doesn't know their user. If you can't describe who this is for and why they'd pay for it, we're not the right team. We're builders, not validators. Come to us once you've talked to actual potential users.

Projects where the budget doesn't match the scope. This isn't about being expensive. It's about being honest. If you want a marketplace with payments, messaging, reviews, and a mobile app for fifteen thousand dollars, the math doesn't work. We'd rather tell you that upfront than deliver something that disappoints.

Projects I can't be proud of. This is subjective and I own that. But life is short and I spend a lot of hours on this work. If the product doesn't do something useful for someone, it's hard to bring our best effort.

What happened when I got selective

My work got better. Obviously. When you're not stretched across six different projects in six different domains, you can actually think about what you're building.

My clients got happier. When I take a project, I'm all in. No splitting attention. No "sorry for the delay, I was swamped with other work."

My revenue didn't drop. It actually went up. Better projects at better rates with better outcomes. Referrals from happy clients instead of a constant scramble for new leads.

The uncomfortable truth

Saying no is a privilege that takes time to earn. If you're just starting out, take the work. Build the portfolio. Learn what you like and what you're good at. But once you have enough runway to be selective, be selective. Your work and your sanity will both be better for it.

Get practical insights, no spam

Short reads on product building, engineering decisions, and what we're learning along the way.

See what your project costs

Answer a few questions, get a ballpark estimate in under a minute.