Illustrative import: the hourglass marks the gap between an accepted file and a report the customer can use.
- 1↓
Workspace created
The chosen TTV window begins.
- 2↓
File accepted
An upload does not mean the data is ready.
- 3↓
Import checked
The product and admin resolve a field-mapping problem.
- 4↓
Data ready
The report uses verified records.
- 5
Usable report
A person with the right access sees the result.
The import finished; the report is still unusable
Imagine a B2B sales analytics product. A customer uploads an export, sees “Import complete,” and opens the dashboard. Some deals are missing because the source file used an unexpected name for the status column. The product recorded a successful import, yet the sales lead cannot take those figures into a meeting.
For this account, time to value could run from workspace creation to the first report populated with the customer's checked data and visible to the right person. That report does not prove the team made a better decision. It is still a more useful endpoint than file acceptance. Write down the start and end before calculating anything; otherwise two teams can debate one TTV number while measuring different journeys.
The customer asks an admin about the missing deals. The admin hunts for the export while the product continues to say “complete.” Some of this time belongs to a necessary data check. The rest goes to finding out what the status actually meant. The distinction matters more than the total alone.
Put an owner next to each pause
Reconstruct one account's path from event timestamps and, where you have permission, its support history. Interface events miss work that happens elsewhere: a customer may wait for approval to export data before anyone touches the upload screen. A short timeline is enough if it names the next person or system that can move the job forward.
- The customer prepares the export and gets access approved. This may be a necessary part of their own process.
- The product accepts the file and checks its shape. It must show the specific error, job status, and way to retry.
- An admin maps fields and confirms what each measure means. Removing this check to save time could produce misleading figures.
- The sales lead opens a report based on real data. Only then does the chosen TTV endpoint occur.
Some waiting protects the result
Field mapping takes time because a plausible chart built from the wrong deals is worse than a clear pause. Help the admin make the check without guessing: show expected columns, ambiguous matches, and an example record that will enter the report. Save approved mappings so a later import does not restart the same conversation.
“Import complete” says nothing about the missing deals. The customer has to ask support whether validation finished and why some records were left out. Show what the product knows: file received, some rows need correction, data ready for reporting. If the customer’s admin owns the next action, name that task. This will not make validation run faster, but the person can see how to continue.
Keep unlike customers apart in the analysis. An account with a ready export and an account waiting for internal data approval entered with different constraints. If their mix changes, the overall median may move even though the product did not. Compare accounts with similar setup paths.
Check who arrived, then how long they took
After changing the import states, report two measures together. What share of new accounts got a usable report within the chosen window? Among those accounts, how long did it take? A median or p75 describes only the accounts that reached the endpoint. It has no time value for accounts still waiting in this report. A fast median on its own can therefore hide a growing group that never gets a report.
Choose a window that reflects the usual setup cycle and compare accounts that have had the full window. If you allow two weeks for setup, an account created yesterday is not yet a failure. Keep the endpoint and the observation window the same across the groups you compare.
Start by reading a few accounts where import technically succeeded but no working dashboard followed. What did the customer see, who could repair the data, and when did they learn about the problem? If the same gap appears repeatedly, you have a specific change to make in validation, error text, or the handoff. “Reduce TTV” is not yet that change.
