Saying no to a ₹15 lakh project -- and why it was the right call

In March, we were offered a 15 lakh project. Website rebuild, digital marketing setup, ongoing retainer, all rolled into one. Largest single engagement we had ever been approached with. I spent two weeks going back and forth before deciding not to take it.

I want to be honest about why, because the easy version of this story is "we had values, we said no, we were right, the end." The actual version is messier and I think more useful.

What made me hesitant

The client was a real estate developer with a large project launching in a tier-2 city in UP. The work itself was interesting. The budget was real. The timeline was aggressive but not impossible.

What gave me pause was the series of conversations that preceded the formal proposal request. In three separate calls, the founder mentioned different versions of what he wanted the website to communicate about occupancy rates for a previous project that had not sold well. Each version was a little further from what we knew to be the real number based on public information and things he had said himself earlier in the conversation.

He was not asking us to lie explicitly. He was asking us to help him frame things in a way that required us not to ask too many questions. In real estate marketing, that framing can tip into territory that is legally and ethically uncomfortable quickly. I am not equipped to manage those risks, and I am not interested in learning how.

The actual cost of saying no

Revenue. That is the real cost, and it was not trivial for us at the time. We had a slow Q1 and 15 lakh would have given us security for six months. I will not pretend otherwise.

There was also the opportunity cost of the relationships the client said he could introduce us to. Real estate developers know other real estate developers. Saying no closed that door.

I spent about a week second-guessing the decision, particularly in a moment when another potential engagement fell through and I was looking at a relatively lean few months ahead.

Why I still think it was right

Three months later, I heard through someone in our network that the developer was in a dispute with another vendor over similar issues. Not the same framing question but an adjacent one about claims made in marketing materials.

I am not making this a morality tale. I got lucky that news reached me in a way that confirmed my instinct. Most of the time you do not get that confirmation. You just have to live with the uncertainty of the choice you made.

What I do know is that the work we delivered in those months instead, for clients whose instructions I could follow without an uneasy feeling, was better. I was more present. My team was less stressed.

We have a filter now that is more explicit: if I cannot repeat a client's instructions to a third party without wanting to add qualifiers and caveats, we should not take the project.