How to Check Automation Vendor Financial Stability Before You Sign

Signs this is happening in your business

What this is costing you a year

How to check automation vendor financial stability

I check five operational signals before you sign: visible cash runway, client concentration, delivery‑team churn, delivery cadence and backlog, and asset/runbook ownership. Request a short set of non‑NDA documents, call references and score the signals. If risk appears, insist on escrow, staged payments and a transition clause tied to final payment.

• Visible runway indicators
• Client concentration
• Engineering and operations churn
• Delivery cadence and backlog
• Ownership of automation assets and runbooks

The five signals you can check in an hour and why they predict failure

These five signals are observable proxies for supplier failure: cash pressure that forces accounting tricks, dependence on one client, departures of delivery staff, slipping milestones despite billing, and vendor retention of assets or vague handover. Each signal shows whether the vendor can deliver, support the system and allow an orderly transition if they collapse.

Runway indicators: how to spot short cash life

Ask for recent invoice totals, payment terms and any large client deferrals to estimate visible runway. Repeated late payments, credits or evidence of unpaid subcontractors are warning signs; small consultancies with under about six months of visible runway are fragile. If the vendor resists questions about unpaid liabilities, treat that resistance as a red flag.

• What to request: month‑by‑month invoice totals for the last six months and any large client deferrals.
• Red flag threshold: signs pointing to under ~6 months of runway or repeated late payments.

A vendor that invoices on time while missing milestones is asking you to fund their survival.

Client concentration: why one client can sink you

Ask for a top‑client revenue banding and cross‑check case studies and references. If a single client represents roughly 30% or more of referenced revenue, losing that client often forces staff cuts, delays or abandoned projects. A simple top‑three banding is a reasonable, non‑intrusive request; refusal suggests transparency problems.

• What to request: a revenue banding for the top three clients, not exact figures.
• Red flag threshold: a single client representing roughly 30% or more of cited work.

Engineering and operations churn: people exit before the invoices do

Check public team lists, LinkedIn departures and repeated job ads for the same role. High churn among delivery staff is the clearest predictor of delays and poor handover. If you see around 20% annual churn in delivery roles or multiple senior exits, treat the vendor as fragile and demand a named knowledge‑transfer plan for your account.

• What to request: names and roles of the team assigned to your account and a commitment to a knowledge‑transfer plan.
• Red flag threshold: visible delivery/ops churn over ~20% in the past 12 months.

Delivery cadence and backlog: a late delivery is a credit risk

Ask for a delivery calendar, recent sprint or milestone completion history and their acceptance process. A vendor that invoices on time while milestones slip is transferring survival risk to you. Cross‑check milestone dates with client references and status reports; if you cannot reconcile their schedule with references, escalate contractual protections.

• What to request: three recent milestone completion dates and corresponding client contacts.
• Red flag threshold: more than two slipped milestones in the last three projects.

If the supplier refuses to hand over runbooks, you are buying future vendor lock‑in, not automation.

Ownership of automation assets and runbooks: who keeps the keys

Get the proposed handover deliverables and a sample runbook. If the vendor retains ownership of flows, scripts or runbooks or refuses clear assignment language, you become dependent on them. Demand explicit IP/asset assignment or escrow and delivery of a usable runbook before you release the final payment.

• What to request: a sample runbook, acceptance checklist, and the proposed IP/asset assignment language.
• Red flag threshold: no documented handover, or explicit vendor ownership of deployed assets.

How to get useful information without an NDA

Request summaries and samples you can get without an NDA: six months of invoice totals, top‑client bands, recent milestone dates, assigned team bios and a sample runbook. Validate answers with LinkedIn exits, job ads and local company filings. Two well‑targeted reference calls usually confirm whether the written answers match reality.

• Documents to request: recent invoicing summary, top‑client revenue bands, milestone completion records, project acceptance checklist, sample runbook, team bios for assigned staff.
• Public checks: LinkedIn exits and job ads, local company filing searches, and matched client reference calls.

Concrete heuristics and red flags you can act on immediately

Turn observations into simple pass/fail rules for negotiation. One breached rule means proceed with caution and targeted protections. Two or more breached rules mean high risk: require escrow, staged payments and a transition plan, or choose another supplier. Use the heuristics to set the size of holdbacks and acceptance gates.

• Client concentration: top client ~30%+ of referenced revenue => red.
• Runway: visible signals pointing to under ~6 months => red.
• Churn: visible delivery churn over ~20% annually => red.
• Delivery: more than two recent slipped milestones across projects => red.
• Ownership: no documented handover or vendor-retained IP => red.

Fixing a broken process with automation amplifies the problem if the vendor disappears mid‑handover.

Contract mitigations that actually protect an SME buyer

You cannot eliminate vendor risk, but you can reduce the cost of failure with specific contract language: source and asset escrow, named IP transfers, staged payments tied to documented acceptance, mandatory knowledge transfer sessions and a clear change‑of‑control transition plan. Tie these protections to the final payment so the vendor has cash incentive to complete handover.

• Source and asset escrow with an independent escrow agent or repository.
• IP & asset transfer language that names the deliverables and a transfer timeline.
• Staged payments tied to documented acceptance criteria, not time alone.
• Mandatory knowledge‑transfer sessions and delivery of runbooks before final payment.
• Change‑of‑control clause requiring immediate escrow release or client option to transition.
• Holdback or retention of 10–20% of the final payment until a 30‑day post‑go‑live support handover is completed.

A one‑hour pre‑sign scorecard and sample questions you can use now

Run this scorecard with your team in one hour: request five documents, call two references and score each signal pass/amber/red. If you hit two reds, require contract protections or choose an alternate supplier. Use the document list and questions below verbatim in emails and reference calls to avoid vague answers.

• Document requests: invoicing summary (6 months), top‑3 client revenue bands, three recent milestone completion dates, assigned team bios, sample runbook and acceptance checklist.
• Vendor questions to send: 'Which three clients represent the majority of your project revenue?', 'Have you had any subcontractor or staff payment delays in the last 6 months?', 'Can we see a sample runbook and acceptance checklist?'.
• Reference questions to ask clients: 'Did delivery meet milestone dates for the last project?', 'Were the vendor’s staff stable during delivery?', 'Did the vendor provide a complete handover and runbook before final payment?'

How these checks fail in practice and the sequence of collapse

Failures follow the same sequence: a major client cuts scope, cash tightens, subcontractor payments slow, key delivery staff leave, milestones slip and the vendor keeps invoicing. Buyers often only notice when handover is partial. Watch finance for late payments, delivery for missed milestones and operations for knowledge gaps.

• Sequence you will see: large client reduction → cash strain → late subcontractor payments → staff exits → slipped milestones → partial handover.
• Who notices: delivery lead sees missed milestones, finance sees late invoices, operations sees knowledge gaps when staff exit.

When to sign as‑is, when to negotiate stronger terms, and when to walk away

Sign as‑is when all signals are green, references are clean and handover items are explicit. If one signal is amber, negotiate protections proportionate to that weakness. If two or more signals are red, walk away or insist on escrow, a sizable holdback and a documented transition plan before you pay the balance.

• Sign as‑is: all green signals, strong references, clear handover items.
• Negotiate: one amber or unclear ownership; require escrow and staged payments.
• Walk away: two or more red flags; consider cto‑to‑your‑business or a larger supplier.

What I do when I run this process for clients

I collect the five signals, call references unannounced and draft the exact contract clauses that close the gaps. My Services cover evidence collection, scoring and contract drafting so you can accept risk intentionally and with clear remedies tied to payment.

• See negotiation templates and selection writeups in the Portfolio and case studies.
• For short advisory engagements, see How to work together.

Key takeaways

Run five checks before you sign: runway, client concentration, churn, delivery cadence and asset ownership. Use a one‑hour scorecard, two reference calls and contract protections — escrow, staged payments and documented handover — when risk appears to protect your operations and cash.

Where businesses waste the most time

1. Re-keying customer dataWastes hours, creates transcription errors and delays fulfilmentCreate a direct connection so data flows from the intake form to the CRM without retypingA person still checks: A person spot‑checks exceptions and approves corrected entries
2. Manual invoice distributionDelays payments and creates late‑fee disputesAutomatically route invoices to the right approver based on existing finance system rulesA person still checks: Finance approves flagged invoices and handles disputes
3. Status updates across teamsTeams spend time chasing status and duplicating workSend automatic status summaries to stakeholders when key milestones change using current messaging toolsA person still checks: Project lead reviews summaries and resolves blocked items

How this compares with what you already run

Operational area	The manual way	The automated way	Annual business impact
Order processing	Manual checks and re‑keying	Orders process automatically on receipt	Fewer staff hours and faster cash conversion
Invoice reading	Finance opens and types invoice data	Invoice details read and routed automatically	Lower errors and shorter supplier payment cycles
Customer onboarding	Teams pass forms and chase fields	Onboarding triggers required tasks automatically	Reduced time‑to‑revenue for new customers
Data entry	Staff copy and paste between systems	Data moves between systems automatically	Fewer errors and reduced processing headcount
Monthly reporting	Reports compiled by hand and reconciled	Reports generated from live feeds	Less executive time spent chasing numbers
Status updates	Teams chase status and duplicate work	Automatic status summaries to stakeholders	Faster decisions and less coordination overhead

What the end-to-end workflow looks like

The metrics that tell you it worked

Metric	What it tells you
Milestone on‑time rate	Percentage of project milestones completed on the agreed date; falls when vendor is cash‑strained or understaffed
Reference satisfaction score	Average score from reference calls on delivery and handover quality; a leading indicator of operational health
Assigned team stability	Count of named delivery staff who remain on the account for the project duration; measures churn risk
Runbook completeness	Count of required handover documents delivered before final payment; measures handover readiness
Top‑client concentration band	Band showing dependence on top client(s); high concentration raises financial fragility
Invoice cadence variance	Variation in month‑by‑month invoice totals; high variance can indicate unstable revenue
Escrow readiness	Whether the vendor accepts escrow and the scope of assets covered; binary check that lowers transition risk

When this is the wrong move

The mistakes that cost the most

• Trusting demos instead of referencesBuyers watch polished demos and assume delivery capacity; the actual sequence is: demo → sign → hidden backlog → missed milestones → partial handover.
• Accepting vague acceptance criteriaVague criteria let the vendor claim completion while you are left with a brittle system; the result is continuing invoices and no usable documentation.
• Ignoring staff churn signalsYou notice after go‑live when support staff have left, leaving knowledge gaps that force emergency hiring or paying the vendor extra.

Frequently asked questions