Contact

Free diagnostic

Technology Valuation Score

How a buyer's tech review would read your business today.

Take the score.

20 statements, about 5 minutes. You get a score out of 100 by email, with a reading for each of five drivers.

Answer for one business: the one a buyer would buy. Our systems means everything the business runs on, built or bought: its own code (an app, a store, integrations, scripts) and the platforms and accounts it all runs in. Our code is the part made for the business. Answer for today, not for where you want to be. Not sure? Choose 3: a buyer reads not sure as a gap.

Take the Diagnostic

Your score arrives by email in a few minutes, with the driver a buyer would look at first. Tell me what it got right or wrong.

Your Results

This is how a buyer's tech review would read your business today, from your own answers: a score out of 100, then a reading for each of five drivers, Ownership, People, Change, Security and Lock-in.

The Five Drivers

  • Ownership: Who owns the code, the IP, and the accounts and platforms the business runs on.
  • People: What one person leaving would cost: who knows the systems, who can change them, and how long they have been here.
  • Change: How the systems change: tests, releases, and knowing what changed.
  • Security: The basics a buyer's security review checks first.
  • Lock-in: What the systems tie you to: platforms, old versions, and the cost of keeping them running.

Your Score

85 to 100 Diligence-ready

You describe systems a buyer can take over: owned, shared, tested, secure and portable. A buyer will check rather than ask, so the next step is the evidence.

70 to 84 Sellable

A buyer's review would find the systems in order, with a few questions. Have the evidence ready before anyone asks.

55 to 69 Sells at a discount

The systems would get through a buyer's review, with findings. Each finding is a negotiating point for the buyer, so it is worth more fixed before a sale than after.

0 to 54 Hard to sell

A buyer's tech review would find gaps it cannot price, and a gap a buyer cannot price comes off the offer or ends the deal. The five drivers below say where.

Each Driver

Each driver is a share of 100, read on a ladder of its own, so your score never reads as a sixth driver.

85 to 100% Buyer-ready

This driver is in the shape a buyer hopes to find. Keep the evidence current.

75 to 84% Holds up

This driver would hold up in a buyer's review, if the evidence matches your answers.

55 to 74% Question mark

A buyer would ask questions here, and want evidence for each answer.

0 to 54% Red flag

A buyer's review would flag this driver and price it in.

A Low Driver

A driver at Red flag or Question mark gets a reading of its own: what a scan would look for there.

Ownership

Red flag A buyer cannot buy what the business does not own. A scan lists every repository, every author of the code and where each writes from, and every license the code ships, so each gap has a name before a buyer finds it.

Question mark Ownership has gaps a buyer will ask about: an author with no IP assignment, a library under an unknown license, code copied in from elsewhere. A scan names each one.

People

Red flag The systems depend on one person, and a buyer prices that person leaving. A scan shows who made each repository's commits last year, how long each has worked on the code, and which repositories one person carries alone.

Question mark Knowledge is shared in places, not everywhere. A scan names the repositories where one person made 80% or more of last year's commits, and whether that person works for the business.

Change

Red flag Changing the systems is risky, so a buyer expects slow, costly change after the sale. A scan counts the tests, measures what they cover, and finds the files that change most with the fewest tests near them.

Question mark Change works, with weak spots. A scan shows where change concentrates, how much of it tests cover, and how much of the code AI wrote.

Security

Red flag A buyer's security review would find problems before it finds anything else. A scan searches every commit ever made for passwords and keys, checks every shipped library for known flaws, and reads your domains from outside.

Question mark Some basics are in place, not all. A scan checks the code's history for keys and its libraries for known flaws, and reads your sites and email domains from public records, with no access needed.

Lock-in

Red flag The systems tie the business to platforms and versions it cannot leave cheaply. A scan lists every runtime and framework with its maker's support dates, and how much of the work goes to upkeep.

Question mark Some of what the systems run on is dated or hard to leave. A scan checks each runtime and framework against its support dates, and measures how much engineering time goes to upkeep.

Your Next Move

Your next move is the driver with the lowest share: a buyer's review would start there. When drivers tie for lowest, pick the one you can show evidence for soonest.

Self-assessed: a score from your answers, not from your code.

From Score to Evidence

Your answers are claims, and a buyer checks claims against the code. A scan reads the code and its history and shows what a buyer would find, before a buyer does.

Every statement in the score names the part of a scan that checks it, so a low driver already says where a scan would start.

The Tool It Runs On

The Technology Valuation Score is one survey built with survey v2, a free and open-source diagnostic builder that runs on Google Forms and Sheets. Scale What? runs on it too.