Marketing your customers read to the end.

Falcon Query Engine ships with Kestrel 8.2 on September 2.

If your workspace holds millions of contacts, you know the failure mode. You change one filter on an account list and then you wait. A dashboard that takes eleven seconds isn't a dashboard anymore. It's a report you open once a week, if that.

Falcon changes what happens underneath. Instead of scanning the full table on every load, Kestrel now maintains rollups incrementally in a columnar cache. When a record changes, the affected rollups update within five seconds, and your dashboards and list views read precomputed deltas rather than recalculating aggregates from scratch.

Internal benchmark on our reference organization (2.4M contact records, 90 days of activity history, 62 custom fields):

Dashboard load, p50: 6.2s → 210ms Dashboard load, p95: 11.4s → 480ms Dashboard timeout rate: 3.1% → 0.02% Saved-report CSV export: 84s → 9s Mobile cold open: 14s → 1.9s Account list filter change: 4.8s → 130ms

Nothing to install, no data migration, no pricing change. Existing dashboards, saved reports, and API report endpoints pick up the new engine on their own.

Where it doesn't help yet, since you'll find this out anyway:

• Custom SQL blocks in dashboards bypass the cache and run at their previous speed. • Workspaces over 5M records need a one-time index build that can take up to 40 minutes. It runs in the background, and dashboards stay available on the old path until it finishes. • Custom-object rollups are slower to refresh than standard objects, p95 around 8 seconds against the 5-second guarantee we hold for standard objects.

On by default for Growth and Enterprise at GA. Starter is next in line, and we'll name a date once we're confident in it.

#CRM #ProductUpdate #DataEngineering

Eleven seconds.

That was the p95 load time on a Kestrel dashboard in a workspace with 2.4 million contacts. Long enough that people stopped opening dashboards in front of a customer and started exporting the night before instead. Three loads in a hundred never finished at all. Our support queue carried roughly 240 of those complaints a month.

The data was fine. The counting was the problem. Every dashboard load and every filter change on an account list scanned the full table from the top, recomputing numbers that had not moved since the last time anyone looked.

Kestrel 8.2 ships the Falcon Query Engine, and it stops doing that. Rollups are maintained incrementally against a columnar cache. When a record changes, the rollups it touches update within five seconds, so a dashboard reads a precomputed delta instead of recalculating the world.

On our reference org (2.4M contacts, 90 days of activity history, 62 custom fields):

Dashboard p50 load: 6.2 s → 210 ms Dashboard p95 load: 11.4 s → 480 ms Timeout rate: 3.1% → 0.02% Saved-report CSV export: 84 s → 9 s Mobile cold open: 14 s → 1.9 s Account list filter change: 4.8 s → 130 ms

Here is what those numbers buy. Someone in the room asks what the pipeline looks like for enterprise accounts in the Northeast. You change the filter while they are still talking, and the answer is on the screen before they finish the question. The report becomes something you interrogate live, at the speed of the conversation.

The honest limits: custom SQL blocks bypass the cache and run at the old speeds. Workspaces above 5 million records need up to 40 minutes for the first index build, which runs in the background while dashboards keep serving on the old path. Custom-object rollups currently sit at 8 seconds p95 rather than under 5.

Falcon is on by default for Growth and Enterprise at 8.2 GA on September 2. Nothing to migrate and nothing to switch on. Pricing is unchanged. Existing dashboards, saved reports, and API report endpoints pick up the engine on their own. Starter plans follow in 8.3.

Eleven seconds used to decide whether the question got asked out loud. Now it does not come up.