Signals tracked for Qbiz
The document classes we read for Qbiz, ordered by how directly each one names unfinished data work. Every account on the accounts tab came out of one of these classes.
How two documents become one account
An account is never one source. It is an operating change in one current document joined to a data-system exposure in another, both primary, both dated inside the last two quarters. The join is labeled as an inference and carries its own kill question. The bar is a specific, unfinished work package sized to a $100,000 to $500,000 engagement, with a named owner reachable today and no visible incumbent holding the seam.
The document names the work
Filed under obligationRecords a company must file, with a named executive accountable for their accuracy. They describe the data estate, the failure, the funding, or the deadline in the company's own words.
Control disclosures that name data paths
Internal-control weaknesses in a 10-K or 10-Q are usually boilerplate. The useful minority name the data mechanics: interfaces, batch jobs, data flows, automated transformations, monitoring of processing and transfer, system-generated reports. Those words describe pipeline work, and the remediation clock is public.
From this screenBlend Labs, 10-Q for the quarter ended June 30, 2026: controls over "the completeness and accuracy of data flows and automated data transformations" and "computer operations controls to ensure that processing and transfer of data are monitored." Xponential Fitness: IT general controls over critical systems, joined to an admitted shortage of technology personnel.
Funded data programs disclosed in filings
Liquidity and strategy sections occasionally name a data investment as a use of cash. That is a budget line with a board behind it, and it is far rarer than a strategy slide mentioning data.
From this screenXponential Fitness: "we require cash to fund the investments in our data warehouse project and other investments to become a data driven company" (10-K, repeated in the June 2026 10-Q).
Transaction documents with data-transfer duties and dates
Transition-services and carveout agreements are filed as exhibits and are almost never read. They contain the data-migration clock in contract language: cutover dates, which order flows are disrupted, what data extraction and conversion costs are reimbursable, and the cap on it.
From this screenSiTime and Renesas: a "One ERP Transition" beginning on or after January 1, 2027, expected to disrupt purchase-order processing and shipments, with extraction, conversion, and transfer of data reimbursable under a $10 million annual cap.
The engineering org shows its own backlog
Published voluntarily, read closelySome companies document their data platform in public. The current-state and future-state sections are a live statement of unfinished work, written by the people who own it.
Public handbooks and engineering posts that name in-progress work
A handbook page marked "in progress" or a blog post that says a gap "remains" is an engineer telling you what is not done. It names the stack, the pattern being replaced, and sometimes the pipelines still to migrate.
From this screenGitLab's dbt guide, "Future State (In Progress)": orchestration moving to a configuration-driven manifest, one pipeline migrated, "the remaining pipelines listed above are planned to be migrated to the manifest over time."
Platform cost exposure in the open
Warehouse-optimization guides, credit-monitoring pages, and committed-spend disclosures show where a data platform's bill is being watched. The seam is the gap between the optimization the team has documented and the one it has had time to run.
From this screenGitLab publishes a Snowflake warehouse optimization guide, a Cortex AI credit monitoring system, and model run-time targets ("all models should individually execute in less than 60 minutes") beside the orchestration migration above.
What removes an account
A named integrator or consultancy visibly holding the seam. Work the company describes as completed. A package that cannot be bounded below a full platform replacement. A pending transaction that freezes vendors. No owner reachable by a validated route. An internal team that has published its solution as done, which is different from an internal team existing: the companies Qbiz has worked with all had strong internal teams, and that is who buys bounded specialist work.
Signal classes describe categories of public record and how they are read. Per-account claims live on the accounts tab with their sources. These signals rank research priority; they do not prove purchase intent, budget, or an open engagement.