Every Product Is Fast With Fifteen Records

Software demos have a quiet advantage: they run on a handful of sample records. Every regulatory platform looks responsive with fifteen submissions in it. The question that matters is what happens with fifteen years of them — hundreds of applications, thousands of sequences, tens of thousands of documents, and a team of reviewers all working at once.

That is the volume a real regulatory portfolio accumulates, and it is where the difference between platforms shows up. A screen that opens instantly in a demo can take long enough at portfolio scale that people stop waiting for it. And when people stop waiting for the official system, they start working somewhere else.

Slow Software Grows Shadow Systems

A slow screen rarely raises an alarm. Nothing fails, nothing turns red, and nobody files a report. It simply becomes a small daily cost, and people route around it.

  • The spreadsheet appears. If the submissions list takes long enough to load, someone exports it once and works from the export all week. Decisions are now being made from a stale, uncontrolled copy — precisely the situation document control and audit trails exist to prevent. Being fast is part of the price of being the single source of truth.
  • Review time shrinks. A reviewer with an hour and a sluggish tool checks fewer things. Nobody records “the software was slow” in a deviation, but friction quietly shapes how much verification really happens.
  • Trust erodes. When a list takes a long time to appear, people begin to doubt everything else. Is the sync current? Did my change save? Responsiveness is how software tells its users it is reliable.

In regulated work, these are not comfort issues. They decide whether the controlled record is the one people actually use.

Speed Has to Hold as the Portfolio Grows

The most common reason software slows down with use is simple to describe. A screen that lists your submissions needs related information for each one — its status, its latest activity, its counts. If the system gathers that information one record at a time, the work grows with every record you add. Ten records, nobody notices. Several hundred, and the screen is doing several hundred separate pieces of work to draw one page.

The uncomfortable property of this pattern is that it punishes success: the more you use the platform, the slower it gets. Your heaviest users get the worst experience.

We design DnXT’s working screens the other way round. The system gathers the related information for a whole page in one pass, not record by record, and every screen reads from the same governed data rather than stitching together older copies that could disagree. One source answering a question is faster than two, and it can never give two different answers.

How to Test This in an Evaluation

You do not need technical access to find out how a platform behaves at scale. You need realistic volume and a stopwatch.

  • Ask for a demo at your scale. Ask to see the main working lists with hundreds of submissions or thousands of documents — the volume your own programme will reach within a few years.
  • Watch for slow-down that tracks size. If a list of 200 takes roughly ten times as long as a list of 20, the system is doing its work one record at a time, and it will keep slowing as you grow.
  • Ask the direct question. “What is your slowest screen for your largest customer, and what did you last do about it?” Teams that measure have a specific answer. Teams that do not will improvise one.
  • Test the screens people live in. The submissions list, the document browser, the review queue and search. A fast settings page tells you nothing.

What We Hold Ourselves To

  • Slowness is a defect, not the weather. A screen that takes too long has a cause, and causes get fixed when someone is assigned to find them.
  • We test at customer-shaped scale. Performance checks run against data sized like the largest real portfolios, because that is where problems hide.
  • One data path. Every screen reads the same governed record. That is a speed decision and an integrity decision at the same time.

No release note makes “this page opens quickly” sound exciting. But a page that loads before anyone reaches for a workaround may be the most important compliance feature a regulatory system has.

If you are evaluating regulatory platforms, bring your real volumes to the conversation — we are happy to be measured at scale. Talk to a regulatory expert and ask to see the big lists first.