Adyakshar Labs

Adyakshar Labs / Blog

Engineering Management

Meet Alex, Part 2: The Vendor Who Said Yes to Everything

Meet Alex again. Alex has a product idea, a deadline and a budget, and has just found a vendor to build it.

Alex: Can you build it in four weeks? Vendor: Absolutely. Alex: Can it handle a million users? Vendor: Of course. Alex: Payments, chat and an AI assistant? Vendor: Yes, yes and yes.

Alex signed that afternoon.

In week three, the demo was a login screen. In week six, there were "a few small issues." In week ten, the vendor said, "we should talk about scope."

Nobody lied, exactly. "Yes" was just the fastest way to end the call.

What a constant yes really means

Every software project trades off time, cost, scope and quality. A vendor who agrees to everything has not removed those trade-offs. They have postponed the conversation until after the contract is signed, when it is much harder for you to walk away.

The vendor worth hiring says something that makes the call a little awkward: "Not in four weeks." "Not yet, we need to see your data first." "That part worries me." These answers sound like friction. Usually they come from people who have built something like this before and know where it goes wrong.

Five questions to ask before you sign

  1. What would make you say no to this project? If they cannot name anything, they have not thought about yours yet.
  2. What is the riskiest part, and how will we find out early? The hard part should be tested in week one, not week ten.
  3. What will I be able to see in week two? Something real: a working screen, a running service. Slides do not count.
  4. Who does the work, and who do I call when something slips? Ask for names.
  5. How will you tell me when something is late? Every project slips somewhere. What matters is whether you hear about it early.

What good answers sound like

Good answers are specific and slightly uncomfortable. "The payment integration is what I am least sure about, so we build that first" is a far better sign than "no problem at all."

Notice what they ask you, too. Questions about your users, your deadline and what happens if a feature is cut show that they are thinking about your outcome, not just your signature.

How we work at Adyakshar Labs

We would rather lose a deal than lose your month. We tell you what we can do, what we cannot and when, and then we do what we say. If you are weighing a build and want a straight answer on scope and timeline, start at adyaksharlabs.com.

What is the most honest "no" a vendor ever gave you?

  • vendor management
  • software outsourcing
  • startup advice
  • project management
  • adyakshar labs

Keep reading

Engineering Management · 4 min read

The Small Change That Was Not Small

Every team has heard "it's just a small change." Here is what that sentence usually means, why it keeps costing money, and three questions that make a small change honestly small.

From across the family

More reading from the other Adyakshar Labs products.

Bindus
How Long Did That Job Really Take? Using Time Sheets and Milestones HonestlyMost small teams quote from memory and learn the real number after the job is done. A simple habit with time sheets and milestones makes the next quote better than the last.
Sampad AI
What to Do in the First Two Days After a Tax Notice ArrivesA tax notice rarely gets worse in two days. It gets worse when it sits. A short checklist for capturing the facts, updating the client and planning the reply.
Quantum Labs
Harvest Now, Decrypt Later: How to Decide What to Protect FirstEncrypted data can be recorded today and read later. You cannot protect everything at once, so sort it by shelf life. A plain test and a three-tier list for deciding what comes first.