Comparison Periods

Hand a board to a team or a CRM role, at read or at edit, by the person who built it. Roles outlive people, which is why a share points at one, not a mailbox.

Columns, funnels, treemaps, radar, scatter, gauges and pivots - offered only where the data shape supports them, so no chart can misread its own data.

Build as many as the floor needs, arrange them on a grid, and give each team the one that answers their question rather than everybody's question.

Click a bar and the rest of the dashboard follows it, so the next question is asked by pointing at the answer instead of rebuilding the filter.

Wire a chart's clicks to a second dashboard. The value travels on the URL and is read by the board that was named before it paints for the first time.

Cross one dimension against another with row, column and grand totals - the shape a finance team asks for when a chart will not settle the argument.

Colour a number by the rule that matters - under target, over threshold, inside a band - so a dashboard reads correctly from across the room.

Seventeen operators in a nested and-or tree, so the report that needs two exceptions and a date range stays one widget instead of becoming three.

Six palettes including a print set, pinned per widget, each carrying eight series colours plus the axis, grid, card and tooltip colours drawn around them.

Thirty-two bytes of entropy, an expiry you choose, revocation on the spot, and only the hash kept at rest, on a board that draws its figures for a reader.

Name a slot at the call site and one authored widget answers it everywhere inside the product, computed against the records of whoever is signed in.

Total calls, answered rate, average duration and missed calls, split by direction and outcome, over the call records rather than a sampled export.