Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Building a Long-Term Development Supplier Relationship
Software Strategy

Building a Long-Term Development Supplier Relationship

The second engagement should be cheaper and better than the first. What to do between engagements so it is, and what erodes a good relationship.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

A supplier who already knows your system skips the most expensive part of any engagement. Keep the relationship warm between projects, request the same people, and pay on time. Those three do more than any negotiation.

The short answer

Ramp-up is the largest hidden cost in augmentation, and a returning supplier has already paid it. Protecting that is worth more than a few percent on the rate.

The way to protect it is unglamorous: stay in contact between engagements, ask for the same people, give notice of what is coming, and pay invoices promptly.

What a returning supplier saves you

  • No environment setup or access scramble
  • No explanation of the architecture and its history
  • Existing knowledge of your conventions and review standards
  • Familiarity with who decides what
  • Awareness of the fragile areas

That is most of the first month of any new engagement, and you get it for free by keeping a relationship rather than re-tendering each time.

Between engagements

DoEffect
Tell them what is coming, even looselyThey can hold availability
Keep read access where appropriateThey stay current
Share significant architecture changesLess relearning next time
Ask for the same people by nameContinuity is the asset
Pay promptlyYou become a client worth keeping

The last row matters more than it should have to. Suppliers allocate their best people to clients who pay on time and communicate clearly. That allocation happens before you ask.

What erodes it

Squeezing the rate every renewal until the supplier assigns whoever is available. Treating engagements as interchangeable. Going silent for a year and then expecting immediate availability. Disputing invoices as a negotiating tactic.

Each of these saves a little and costs the thing that made the relationship valuable, which is the same people who already know your system.

When to change supplier anyway

  1. Quality has declined and specific concerns have not been addressed.
  2. The people you valued have gone and the replacements are not comparable.
  3. Your needs have changed and they do not have the skills.
  4. The commercial terms have drifted out of line with the market.
  5. The relationship has become adversarial and the conversations are about the contract.

Familiarity is valuable and it is not worth keeping at any price. The point is to change for a reason rather than out of habit or on price alone.

Keep it honest in both directions

Tell them when something is not working, early and specifically. A supplier who hears a concern in week three can act on it. One who hears it at renewal cannot, and will conclude you were never going to renew.

Equally, a supplier who tells you a project is not worth doing, or that you do not need as many people as you asked for, is worth more than one who agrees with everything. That is what a long relationship should buy.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Should we use one supplier or several?

Several gives resilience and comparison; one gives depth and continuity. Many teams keep a primary relationship and a second option they use occasionally.

How do we keep the same developers?

Ask for them by name, give as much notice as you can, and be a client worth allocating good people to.

Is a retainer worth it between projects?

It can be, if you have a steady trickle of small work. It keeps knowledge current and gives them a reason to hold availability.

What if the rate goes up each year?

Ask what changed. Some increase is normal. A large jump with no explanation is worth testing against the market.

Keep reading

More on Software Strategy

Software Strategy

Machine Learning Myths That Waste Budgets

Eight beliefs about machine learning that quietly inflate project costs, what is actually true instead, and how to spot each one in a proposal.

Start here

Thinking about adding developers to your team?

Tell us what you are building, what your team looks like now and where the gap is. We will come back with an honest view on whether augmentation fits, how many people it would take and what it costs. If hiring directly would serve you better, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →