When to Say No: A Founder's Project Acceptance Checklist
Founders often say yes to projects that feel like revenue but quietly damage the business. A deal that stretches delivery, erodes margin, or adds chaos can cost more than it earns. A simple acceptance checklist creates a guardrail against bad-fit work.
Start with three non-negotiables: margin, capacity, and fit. If the deal cannot meet your minimum margin, if you do not have capacity within the promised timeline, or if the client's problem is outside your core expertise, the answer should be no.
Ask about urgency and clarity. A client who needs a solution yesterday and cannot define the outcome will push you into constant changes. Clear outcomes and realistic timelines are the foundation for success.
Check for internal champions. Projects without a decision-maker or internal owner often stall. If the client cannot name who owns success on their side, you are signing up for delays and scope creep.
Look at the risk profile. If the project requires unproven tooling, depends on third-party decisions, or has a heavy compliance burden, price the risk or decline. Risk is not bad, but it must be acknowledged and compensated.
Finally, evaluate the strategic value. Will this project produce a case study, a referral, or a repeatable asset? If the answer is no and the deal is marginal, decline and protect your focus.
Saying no is not about scarcity. It is about alignment. When you accept the right work, delivery improves, margins rise, and the business becomes easier to scale.