Klimn

Dashboards designed to be read. Extensions Tableau doesn't ship with.

Klimn-built Tableau dashboard

VISUALIZATION

Designed to be read.

Most enterprise dashboards show data. Mine explain it. The difference lives in what's shown, what's cut, and what a viewer can do in three seconds.

Klimn-built Tableau dashboard, light theme

TABLEAU EXTENSIONS

Built past Tableau's limits.

Tableau has edges. Extensions close them. Built right-to-left, production-grade interactions and integrations, and behaviors that aren't possible out of the box.

These four: Hierarchical Table, KPI Card, Sankey, and Sunburst. One toggle — Arabic data, Arabic-flowing chart, one build. Built for client briefs; I add new ones as the work calls for them.

Klimn dashboard — an executive summary built with the KPI Card, Sankey, and Sunburst Tableau extensions
Klimn dashboard — a detailed view using the KPI Card and Hierarchical Table extensions

HOW I ENGAGE

Engagements are scoped to the work, not sold in packages.

Three modes. Pick the one that matches the brief — or send me the shape and I'll tell you which one fits.

  • FIXED SCOPE · FIXED TIMELINE

    Project

    Fixed scope, defined outcome. Best for building specific dashboards, executing an audit, or developing a custom extension. Delivered with full documentation and handover.

  • ONGOING CAPACITY

    Retainer

    Ongoing embedded capability. For organizations that need a senior practitioner consistently guiding their internal team, reviewing work, and handling complex builds.

  • DECISIONS, NOT DELIVERABLES

    Advisory

    Diagnostic engagements with written deliverables. No implementation. Example: a Tableau Server Health Check — performance assessment, configuration review, governance review, written remediation plan. Implementation is scoped separately as a Project.

Pricing is set against scope. A written proposal follows a short brief call.

If the Tableau licenses are paid and the dashboards unread, that's a brief — not a renewal.