Techbanq

Governance · selection

Run this checklist on every offshore partner, including us

Before any contract is signed, a few weeks of disciplined checking — reference calls that go beyond the happy customers, a paid trial designed to be judged, and the ending negotiated at the beginning — tells you more about a vendor than any proposal, and a serious firm will welcome all of it.

Written for
CTO, Procurement, COO
Decision
Vet an offshore partner properly before anything is signed
Languages
EN · AR

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The sorting test

Five answers that separate an engineering firm from a bench reseller

A bench reseller rents out CVs; an engineering firm delivers work it stands behind. Both will present well. The same five questions get different answers from each, and the answers are hard to fake.

OptionWho you get to interviewHow references are offeredWhat the trial looks likeWhat the contract says about leavingWho owns the engineering processBest for
A bench resellerProfiles and CVs; an interview with the actual engineer is resisted or substituted with a sales engineer.Logos on a slide and written testimonials; a live call with a client is hard to arrange.A free generic sample built by whoever was available, telling you nothing about the team you would get.Silence, or renewal-friendly terms; exit obligations appear only when you ask, and grudgingly."Whatever process you prefer" — which means nobody is accountable for quality but you.Short commodity tasks where interchangeable capacity is genuinely the point.
An engineering firmThe named engineers who would join, interviewed by your technical lead before anything is signed.Live clients on the phone, including on request one whose engagement ended — and how it ended.A paid, bounded piece of real work in your codebase, staffed by the team you would actually get.Notice, handover duties and escrow written into the first draft, because it has exited engagements well before.An opinion about cadence, review and quality it can defend — and will adapt, but not abandon, for you.Work your business will still be running, and extending, in two years.

The sequence

The checks to run in the weeks before any signature

In order, because each step is cheaper than the next and can end the process early. Most of the cost of a bad vendor is avoided in these weeks or never.

STAGE 01

Make the references actually reference

Ask for live calls, not letters — and ask the vendor for one client whose engagement ended. On the calls, skip the satisfaction questions and ask what broke, how it was handled, and what the client would negotiate differently now. A vendor with no reachable former client either has none, which is unusual, or none that would speak well, which is informative. A picture of the vendor under stress, not at their best.

STAGE 02

Design a trial you can judge

Paid — free work is a sales cost and staffed like one. Bounded in weeks, on a real ticket in your codebase, done by the engineers who would actually join, with the judgement criteria agreed in writing before it starts: the quality of the code and its tests, the questions the team asked, and how the inevitable ambiguity was handled. Evidence from real work instead of an impression from meetings.

STAGE 03

Negotiate the ending at the beginning

Exit notice, handover and documentation obligations, source-code escrow where the dependency justifies it, knowledge-transfer duties with named durations, and IP assignment — all in the first contract. Every one of these is cheap for a vendor to grant while they are courting you and expensive to obtain once you depend on them. Terms secured while you could still walk away.

STAGE 04

Sign with the governance attached

The cadence, the definition of done and the two named interface roles go into the engagement terms on day one, so the management routine starts as a contractual fact rather than a culture you hope develops. An engagement that starts governed instead of becoming governed.

Why now

The day before you sign is your strongest negotiating position

The clauses this checklist insists on — exit terms, escrow, knowledge transfer — share one property: they cost the vendor almost nothing to grant before signature and cost you a great deal to obtain after. The day before you sign, the vendor is competing and every reasonable term is agreeable. A year in, when your product depends on their team, the same requests are negotiations you enter from weakness. Nothing about the terms changed; only the side holding the alternative did.

Two distinctions keep this page honest about its scope. Everything here happens before signature and is about choosing well; actually executing a separation from an incumbent vendor, years later, is its own discipline with its own sequence, and a separate guide covers it. And the checklist deliberately names no vendors and ranks none — including us. It is a set of questions, and its value is that any vendor's answers, ours included, can be judged against it by you rather than asserted by the party being judged.

Our role

Ask us everything on this page and get it in writing

  1. 01

    The interviews, granted

    The named engineers who would join your work sit for interviews with your technical lead before signature — because we would not advise you to accept less from anyone.

  2. 02

    The trial, on your terms

    A paid, bounded engagement on real work, with the judgement criteria agreed before it starts and no obligation beyond it — the cheapest way for both sides to find out.

  3. 03

    The ending, in the first draft

    Exit notice, handover obligations, escrow where warranted and IP assignment appear in our initial contract rather than entering it through negotiation — the checklist's terms are our defaults.

The judgement is yours and should stay adversarial in the best sense: our part is answering every question on this page in writing, and losing the engagement if the answers are not good enough.

Common questions

What buyers ask

How do we make a reference call to an offshore vendor's client useful?+

Change what you ask and who you ask. Any vendor can produce two delighted clients, so treat those calls as a floor, not a finding, and ask for one client whose engagement ended — how a vendor behaves in a separation is the strongest signal available before you experience one. On every call, replace satisfaction questions with specifics: what went wrong and how long it took to surface, who was accountable when it did, whether the engineers stayed on the account or rotated away after signing, and what the client would put in the contract if starting again. Listen for stories rather than adjectives; a reference who can only praise has usually been coached, while one who describes a handled failure has actually worked with them.

What does a well-designed trial engagement look like?+

Paid, bounded, real and judged by criteria agreed in advance. Paid, because free work is a marketing expense and gets staffed like one — you would be evaluating their sales process. Bounded in weeks with a defined finish, so both sides know when judgement happens. Real, meaning an actual ticket in your codebase under your access controls, not a greenfield demo that avoids every hard part of your environment. And judged on criteria written before it starts: code and test quality, the questions the team asked, how ambiguity was handled, and whether the agreed cadence was kept. The strongest signal is often the questions — a team that interrogates your domain before writing code is showing you how they will treat the real engagement.

Which contract terms are hardest to add after signing?+

The ones that only matter when the relationship is ending or strained — which is exactly when you cannot get them. Source-code escrow, knowledge-transfer obligations with named durations, exit notice and handover duties, and audit or verification rights all cost a courting vendor nothing to grant; a year later, each is a favour you are requesting from a party that benefits from your dependence. IP assignment behaves the same way: correcting a weak clause mid-engagement means asking a vendor to sign away something they arguably hold. The rule of thumb is that anything protecting you against the vendor must be won while they are still competing for you. Terms about doing the work can be tuned later; terms about leaving it cannot.

Run this checklist on us

Our written answers to every question on this page, plus a trial engagement scoped so you can judge us on real work before committing.

Start the conversation