Client reporting

Client dashboard software with numbers you can explain

Give each client a current performance view backed by reconciled CRM, finance, and operating records. Permute keeps metric definitions, source evidence, and access controls attached to the numbers your team shares.

Example workflow

Illustrative custom app · Sample data

Connected systems

Source records for this workflow

Permute data foundation

Connected records, shared rules, source evidence, and governed access.

Custom application
Governed view

Shared reporting view

Client performance

Revenue

$1.28M

Deals won

42

Conversion rate

3.6%

PeriodRevenueReview
September$412KSource linked
August$396KSource linked
July$472KSource linked

Metrics stay tied to their definitions, refresh dates, and sources.

This is an example layout with sample records. Connector availability varies by plan and source permissions.

The working view

Give each client a current view of the work

Show revenue against plan, campaign performance, or project status with the reporting period (and source refresh dates) beside each result. Account teams can trace a changed number back to the underlying records.

Built on Permute

What makes it work

One metric definition

One metric definition powers recurring reports and client views, so a calculation stays consistent across accounts.

Separate client data

Client-specific views and explicit permissions keep each account’s approved data separate.

Refresh without rebuilding

Connected workflows refresh dashboards as source records change, without rebuilding the report each period.

How it works

From scattered reports to one client view

  1. 01

    Connect client sources

    Bring the CRM, finance, and operating records behind the client review into one governed model.

  2. 02

    Reconcile the inputs

    Resolve duplicate records and apply the same calculation rules to every reporting period.

  3. 03

    Publish the dashboard

    Give the client a permissioned view with current figures and a path back to their sources.

Why build on Permute

Build on a foundation each new tool can reuse.

Permute connects systems, reconciles records, and keeps business definitions and source evidence in one place. Each application reuses that foundation (including its data access rules) instead of rebuilding the same integrations and logic.

Build with your own team through Permute Factory's API and SDK, or work with our engineers to build and maintain the application. Permute-hosted apps use Permute sign-in and app access checks. Each app checks which business data a person may see before returning it.

Built for this workflow

From dashboards to a full client experience

Use Permute dashboards for repeatable client reporting. When clients need documents or workflow steps alongside their metrics, build a custom portal on the same governed data.

Questions teams ask

Are client dashboards private?

Yes. Each client gets a separately permissioned view of approved data, even when the dashboard design is reused.

Can one dashboard pattern be reused for several clients?

Yes. Reuse the layout and metric definitions across clients while publishing a separate view for each account.

Can clients ask questions about the data?

Permute supports plain-language questions over governed data. A custom portal can expose approved answers to clients.

How is this different from a static report?

A dashboard can refresh from connected sources and keep the calculation and evidence available when a number changes.

See this workflow on your data.

Bring a report or workflow you run today. We’ll map its source systems, business rules, access, and first custom view (including any approvals your team needs).