Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Measuring a software partner's reliability before and after signing: governance, dashboards and milestone evidence

Measure a software partner's reliability as commitments kept: log every promise with a date and the evidence that it was met, from the first call to each accepted milestone, and read the same six measures before and after signing. This Netbase guide gives the reliability ledger, the governance dashboard and the milestone evidence pack.

Book a solution review See digital transformation consulting

By Netbase Delivery and Quality Desk · Reviewed by David (CEO) · Updated · 10 min read

star

This guide is for founders, CTOs, operations leads and procurement teams buying custom software development who want a record of reliability that does not depend on the partner's own sales story. It belongs to the partner-selection series that starts with large or boutique Vietnam IT vendors, and it pairs with how Netbase works.

In this guide

What does reliability mean for a software partner?

A reliable software partner is one whose promises come true on the agreed date with evidence attached. It is not the same as speed or team size: a fast team that misses its dates is less reliable than a slower team that warns early.

That definition can be measured from the first contact. Before any contract exists, a partner already makes small promises: a proposal by Friday, a discovery summary, an answer to a security question. After signing, the promises become milestones, releases and support responses, and the same measures keep working.

Pipeline metrics answer a different question. The DORA software delivery metrics describe how often a team deploys and how quickly it recovers, and the guide to measuring engineering delivery health explains how a buyer reads them. Reliability sits one level above: did the partner do what it told you it would do?

Why start measuring before you sign?

Behaviour in the sales phase is the cheapest evidence you will get. A partner that sends documents late, changes its answers between calls or cannot name who will do the work is showing its delivery habits before you pay anything. Logging those signals gives you a record to compare across candidates.

Which reliability measures work before and after signing?

Use one set of measures for the whole relationship, so the record you build in the sales phase is directly comparable with the record after signing.

Measure Before signing, log After signing, log Evidence that counts
Promises kept on date Proposal, discovery notes, answers sent when promised Milestones and releases delivered on the agreed date Dated message, file or release note
First-pass acceptance Paid discovery or pilot accepted without rework Milestones accepted against written criteria on first submission Signed acceptance record
Early warnings Risks and unknowns named in the proposal Delays and risks raised before the due date, not on it Dated risk entry or status note
Written change impact Assumptions and exclusions stated in writing Each change request priced in scope and time before work starts Change request with sign-off

Two further measures complete the ledger once work starts. Evidence completeness asks whether each milestone arrived with the agreed pack described below. Issue response asks whether support and defect reports were acknowledged and resolved within the agreed times.

Read each measure as a count, not a blended score, so every slipped promise can be traced line by line.

How do you set up a reliability ledger and dashboard?

The ledger is a shared table with one row per promise. The dashboard is a filtered view of it that both sides read at every governance meeting.

  1. Start the ledger at the first call

    Record each promise the partner makes, the date given and who made it. Keep it in a shared document or ticket board from day one.

  2. Agree the six measures in the contract annex

    Define each one in a sentence, name the system of record and state how a result is counted, so neither side can redefine it later.

  3. Write acceptance criteria before each milestone starts

    A milestone without written criteria cannot be scored for first-pass acceptance. The Scrum Guide calls the equivalent a Definition of Done.

  4. Attach evidence to every row

    A promise counts as kept only when the dated file, release, test result or sign-off is linked from the row.

  5. Build the dashboard from the ledger, not beside it

    Show open promises, the next three milestones with their status, open change requests and open issues, each linking back to its row.

  6. Review on a fixed cadence and escalate by rule

    Read the dashboard weekly, review the full ledger at each milestone, and agree in advance what triggers escalation, for example two missed dates in a row without an early warning.

UK public procurement uses the same logic at contract level. Section 52 of the Procurement Act 2023 defines a key performance indicator as a factor or measure against which a supplier's performance can be assessed during the life-cycle of the contract, and requires larger public contracts to set at least three of them.

What belongs in a milestone evidence pack?

A milestone evidence pack is what the partner hands over before you accept and pay. It should contain:

  • A working demo of the delivered scope, on an environment you can access.
  • Test results for the acceptance criteria, including what was not tested and why.
  • Release notes listing what changed, known issues and any change requests included.
  • Code and documentation committed to a repository you own, with access confirmed.
  • An updated risk list with new risks and the ones closed since the last milestone.

The Agile Manifesto principle that working software is the primary measure of progress is the test for the whole pack: a status report without a demo and test results is a claim, not evidence.

How should governance meetings use the numbers?

Use three meeting levels. A weekly review reads open promises and early warnings and assigns owners. A milestone review reads the evidence pack and records acceptance or a written list of gaps. A quarterly review reads the full ledger and asks whether the engagement model still fits.

Keep the escalation path short and agreed in writing: project managers first, then the partner's account owner and your sponsor. A reliable partner raises bad news itself; if you find most problems first, record that pattern.

Where AI fits

AI can do the clerical part of the ledger: draft the weekly status from tickets, commits and release notes, match promises to evidence and flag rows with no linked file. In a Netbase project, engineers and the project manager still confirm that a linked file really proves the promise, that acceptance is recorded by a person and that an early warning was raised in time. Netbase works with the major commercial and open-source AI tools and models, chosen per project, so the ledger does not depend on one tool.

The delivered AI feature named with a client is 4over4's recommendation engine, which suggests products from browsing history and previous purchases. Beyond it, Netbase has delivered AI projects for clients that are not named, including retrieval-augmented knowledge assistants, document AI and MLOps pipelines.

What delivery record exists, and what does not

Netbase governance uses weekly reviews, KPI dashboards, a dedicated account manager and project manager, Slack or Zoom, and client dashboards, which is where a reliability ledger is read. The delivery lifecycle runs from discovery and strategic alignment through agile execution with outcome-based milestones to rollout and ongoing support.

Most Netbase projects are delivered on fixed-price contracts; milestone-based, monthly team retainer and KPI-linked models are also offered. Teams of 3 to 30 people combine business analysts, project managers, solution architects, developers, QA and UI/UX designers, and work typically starts within 1-2 weeks after discovery. In fractional AI leadership work, each milestone has a written outcome and acceptance criteria agreed before it starts. For custom development, the client owns the IP created for it.

Netbase is a consulting company first: consulting, solutions, custom development and AI-enabled transformation lead, and dedicated teams are a secondary delivery option. Netbase also works as offshore development partner on a multi-tenant cloud ERP for a US client that is not named, a long-running product delivered phase by phase.

What does not exist: no published on-time rate, first-pass acceptance rate, reliability score or client satisfaction figure for Netbase. This page gives a method a buyer can apply to any partner, Netbase included, not results.

Alternatives: other ways to judge reliability

The ledger is one source of evidence. Combine it with the others according to what you can check and when.

Method What it shows Limit Use it when
Reference calls How the partner behaved for someone else Chosen by the partner Before signing, with specific questions
Certifications and audits Controls in the partner's own operations Say little about one project Security or data handling matters
Paid discovery or pilot Real delivery on a small scope Short window Scope is unclear or the stakes are high
Reliability ledger Promises kept, with evidence, over time Needs discipline on both sides Any engagement longer than one milestone

For the claims side, how to verify a software development company's claims pairs each claim with an independent check. For the warning signs in proposals and demos, read software development company red flags. To compare the commercial terms a ledger can sit under, see Netbase engagement models.

When is a full ledger too much?

Skip the full ledger for a small fixed package with one delivery, a one-off fix or a short audit; a written acceptance checklist and the evidence pack are enough. A ledger only one side updates loses value, so agree who owns each row.

Limits of this guide

  • It is not legal advice; the measures belong in a contract annex your counsel reviews.
  • It does not publish prices, fee holds or penalty amounts; those are agreed per project.
  • It does not replace security due diligence, which needs its own questions and evidence.

Plan the next step with a Netbase consultant

Frequently asked questions

Log every promise the partner makes in the sales phase, such as a proposal date, a discovery summary or an answer to a question, with the date given and the date it arrived. Compare that record across candidates alongside reference calls and a paid discovery or pilot.

It should show open promises with their dates, the next milestones with status, open change requests with their impact, and open issues with response times. Every item should link to its evidence so both sides read the same facts.

A milestone should arrive with a working demo, test results against the written acceptance criteria, release notes, code and documentation in a repository you own, and an updated risk list. Accept and pay only when that pack matches the criteria agreed before the milestone started.

Next step

Bring your current proposal or project status, and Netbase will help you set up the six-measure ledger for it: book a solution review.

AI-enabled custom software development built around your workflow AI-enabled custom software development built around your workflow

Netbase provides custom software development for companies whose workflow no off-the-shelf product fits, from discovery through architecture, build, testing and handover, with AI where it removes manual steps and the IP left with you. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to the published USticker case study, design-tool users converted 40% more often.

Learn More
line
AI-enabled digital transformation consulting that ends in a delivery plan AI-enabled digital transformation consulting that ends in a delivery plan

Netbase provides digital transformation consulting for mid-market companies that need a prioritized roadmap with a delivery path, not a deck. We rank every change by value and risk, including where AI removes manual work, and the same team builds it. According to CEO Huy Nguyen (David), Netbase has served 500+ businesses across 80 countries since 2012.

Learn More
line
An AI-enabled offshore development center in Hanoi, when a long roadmap needs one An AI-enabled offshore development center in Hanoi, when a long roadmap needs one

An offshore development center (ODC) in Vietnam is a long-running engineering team that a partner abroad staffs, manages and documents for your product roadmap. Netbase runs ODC teams from its only office, in Hanoi, with AI-assisted engineering, weekly governance and knowledge transfer built in. When the work has a defined outcome, a fixed-price project usually fits better.

Learn More
line
Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system

A custom cloud ERP from Netbase is one browser-based system where a growing company runs its projects, finance, HR and customer relationships on shared data, with AI that reads invoices and forecasts demand and cash. It suits SMEs that have outgrown spreadsheets but not their own way of working, on the foundation of Cloodo Workspace, which Netbase built and runs.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase