Speed
Every click under 50 milliseconds
That’s our budget for every common action, on 10,000 contacts, on a processor slowed to a quarter of a mid-range laptop’s speed. Here are the numbers, and exactly how we get them.
Actions
Measured October 21, 2026. Time from your click or key press until the result is on screen.
| Action | Usually | 19 times in 20, at most |
|---|---|---|
| Open a record | 29 ms | 48 ms |
| Edit a field | 21 ms | 27 ms |
| Move a deal to another stage | 20 ms | 32 ms |
| Search, per keystroke | 7 ms | 18 ms |
| Open the list of 10,000 people | 23 ms | 30 ms |
| Switch between board and deal list | 33 ms | 42 ms |
| Switch pipeline | 34 ms | 39 ms |
| Open the command palette | 27 ms | 29 ms |
ms is milliseconds, thousandths of a second. Each action was tried 20 times: “usually” is the middle result, and the last column is a slow try, one that only 1 in 20 tries was slower than. For comparison, a blink of an eye takes 100 to 400 ms.
Opening the app
Same slowed processor, on a fast home internet connection (40 Mbps). Next visits: 19 times in 20, at most.
| Workspace size | First visit, usable | Next visits, board on screen | Next visits, ready to use |
|---|---|---|---|
| 100 people | 0.51 s | 0.10 s | 0.16 s |
| 1,000 people | 0.47 s | 0.11 s | 0.25 s |
| 10,000 people | 0.52 s | 0.13 s | 0.90 s |
On later visits, the board you last saw appears straight away and is ready to use a moment later. With 10,000 contacts that moment is a little longer, which is the last column.
How we measure
- Real browser, real app. Automated tests drive the production build of the app in Chromium (Playwright), at 1440×900, signed in to a workspace.
- A big workspace. 10,000 people, 5,000 companies, 5,000 deals, 10,000 tasks and 10,000 notes, generated with realistic names and values.
- A slow computer. Before measuring, the test times a fixed piece of work and slows the processor until it runs a quarter as fast as on a mid-range laptop. On our test machine (an Apple M1 Pro) that was 3.21× slower.
- Click to screen. The clock starts at the input event and stops at the first frame drawn after the page shows the result.
- Many tries. 3 warm-up tries, then 20 measured tries per action. We show the middle result and a slow one: only 1 in 20 tries was slower.
- A budget, not a boast. Every action has to stay under 50 ms in 19 tries out of 20, the first visit under 1.5 s and later visits under 0.5 s. We run the tests before each release, and a slower result blocks it.
The raw results, with every setting: speed-results.json.
Why it’s fast
A copy of your CRM is kept in your browser, so a click shows its result at once. Your changes save on their own, and your teammates see them within moments. You need an internet connection: when it drops, editing pauses until it’s back.
What we haven’t measured
We haven’t timed other CRMs, so we don’t quote numbers for them. If we ever do, we’ll publish the date, the method and the raw results here, the same way.
Feel it for yourself
These numbers are the real app. Open the live demo and click around: no sign-up.
Start free trial Try the live demo
7 days free, no card. Then $5 per user a month, billed yearly.