Why Do Agencies Turn Down Projects? 5 Real Reasons from Business Development
When an agency turns down a project, it is usually not because it doesn't want the work, but because it can see that the project, as it stands, would harm the business. I'm Cemre, a business development specialist at Diyojen. Part of my job is finding new projects, and part of it is saying "not like this" in time to projects that have been set up the wrong way. In this post, I explain why we turn down projects at Diyojen, with five real reasons, starting with a Tuesday afternoon.
Tuesday, 4:20 PM: Ten days on the phone
The moment that best captures how hard it is to say no was a phone call that came in at 4:20 PM on a Tuesday last year. The business owner on the line was very excited: he wanted a trilingual website, an online booking system and a design that looked "exactly like" a competitor's site, all within ten days. As I took notes in my notebook, my pen slowed down, because every sentence made the previous one harder.
After the call, we held a quick fifteen-minute meeting at the office with our design team and our development team. Everyone reached the same conclusion: if this project were done in ten days, either the design would be left half-finished or the booking system would go live without being tested. Either way, the business owner would be the one paying the price. I called him the next morning and, for the first time, said as clearly as I ever had, "let's not take this on as it stands." I still remember the silence on the other end of the line.
5 situations where Diyojen says no to a project
When Diyojen turns down a project, it happens in specific, recurring situations. Over the years these situations have become clearer and turned into a kind of internal checklist on the business development side.
1. When the timeline conflicts with the nature of the project
A realistic timeline means a project has enough time for its design, development, content and testing phases. A multilingual site or a system that takes bookings needs to be tested separately for every language and every scenario. If the timeline can't accommodate that, you don't gain speed; you just postpone the errors.
2. When the request is to copy someone else's site
Copying a competitor's site exactly means losing, right from the start, the chance to tell your own brand's story. On top of that, imitating another company's work is a risky path both ethically and legally. At Diyojen, we talk about drawing inspiration, not about copying.
3. When the real problem isn't the website
Sometimes a business asks for a new site, but its real trouble lies elsewhere. For example, if incoming messages go unanswered for days, even the best-designed site can't hold on to customers. In a case like that, offering a new site would be an easy sale, but it wouldn't be honest. I prefer to first talk through together where the problem actually is.
4. When the request is to "just tweak" a ready-made template
A ready-made template is a framework where thousands of sites share the same skeleton and only the colors and text change. Working on these sites after the fact means inheriting their limits as well: plugin dependency, security updates, slowness and a design that looks like everyone else's. Because Diyojen designs and codes specifically for each brand, instead of patching a template we explain this difference openly to the business.
5. When there's a gap between expectations and scope that can't be discussed
A gap between expectations and scope is a mismatch between the result a business wants and the budget and time it has set aside. This gap isn't always a problem; the problem is when nobody wants to talk about it. Projects where we can put the gap on the table usually go well.
Saying no isn't closing the door
In business development, "no" is often short for "not like this, but it could work like this." With the business owner who called that Tuesday, I didn't just turn him down; I suggested an alternative path. The table below summarizes the alternatives Diyojen usually suggests for common requests.
| Incoming request | Alternative Diyojen suggests |
|---|---|
| A multilingual site and booking system in ten days | First a solid, single-language site; other languages and booking in a second phase |
| An exact copy of a competitor's site | An original design that grows out of the brand's own story |
| A new site that won't solve the problem | First a short assessment where the real problem is discussed |
| Small edits to a ready-made template | A portable site designed and coded specifically for the brand |
After thinking it over for a few days, the business owner accepted the phased plan. The project wasn't finished in ten days but over a longer period; yet when it went live, the booking form worked from day one. For me, the best part was a short message that arrived months later: "I'm so glad we didn't rush that day."
What I've learned as a business development specialist
The real job of a business development specialist isn't to take on every project, but to start the right project the right way. In my early years, I saw every "no" as a missed opportunity. Over time I realized that a badly set-up project drains our team's weeks and the business's trust. Now, if something bothers me in a meeting, I say it right at the start instead of saving it for the end. It takes a bit of courage, but the other side is usually grateful for that openness.
If you're curious about how a project starts at Diyojen and the stages it goes through, take a look at the page where we explain how we work.
In short
- When an agency turns down a project, it's usually not because it doesn't want the work, but because it sees the project, as it stands, would harm the business.
- The main situations where Diyojen says no: an unrealistic timeline, a request for a copied design, the real problem lying elsewhere, a request to patch a template and an expectations gap that can't be discussed.
- A good "no" always comes with an alternative; a phased plan is often the healthiest path.
- Openly raising what bothers you at the start of a meeting protects both the agency's and the business's time.
