Software. Illustrative, not a Client.
The query that stopped scaling
A Toronto SaaS company. Its customer dashboards slowed to 40 seconds once the largest account passed 50 million events.
Which version is SR&ED?
Version ANot SR&ED
The team added indexes, moved to a bigger database instance and cached the common queries, following the vendor documentation. It took six hard weeks, but at every step a competent engineer knew what would work.
Version BSR&ED
Every customer defines its own event fields, and they change daily. The published fixes (precomputed views, a columnar store) assume fields that stay put, and both broke on the first schema change. Nobody knew whether sub-second queries were possible under those conditions, so the team tested a rollup keyed on schema version, measured it, and changed course twice.
Decided by: Technological uncertainty. Hard, slow and expensive is not the test. The question is whether a competent professional could have known the answer from published knowledge. For indexes and caching, they could.