Skip to main content

Reporting overview

Reporting lives at `https://lengrowth.com/reporting` and is tied to the selected company.

Reporting overview

Reporting lives at https://lengrowth.com/reporting and is tied to the selected company.

When to use this

Use reporting when you want to understand the result of the work, not just the task movement.

Reporting is the right page when you need to:

  • review the current macro objective

  • see whether the company is making execution progress

  • inspect the current growth result and the next rank direction

  • check which evidence is backing the report

  • review connected tools that are feeding the report

  • see warnings or notes if the report needs more data

If the pipeline answers “where is the work?”, reporting answers “what changed?”

Step-by-step

The reporting page uses the selected company from the header.

If no company is selected, the page shows a company selection card with the prompt Select a Workspace and a description that tells the user to choose a company to unlock reporting and view founder-first insights.

If a company is selected, the page shows the company name and tells the user to use the header dropdown if they want to switch.

The reporting area uses the ReportingWorkspace component. The skeleton and empty-state behavior are visible, so customers know when data is still loading versus when no report is available.

The page can also show a refresh banner that says:

Refreshing reporting with the latest company data…

That banner appears when the report is already cached and the page is updating in the background.

The top section of the report shows a headline and subheadline. This is the founder-facing summary and is the first thing customers should read.

It also shows a few highlighted items when available. Those highlights are surfaced as small chips so the report stays readable without turning into a wall of metrics.

The Macro objective card explains what the founder should care about first.

The visible fields in that section include:

  • Current goal

  • status chips such as company stage, industry, operating scale, and website status

  • growth score

  • execution percentage

  • next-step count

  • a link to the live website when one is available

This section is the clearest way to see what LenGrowth thinks the current goal is.

The Growth result card shows:

  • the current assessment rank or status

  • progress to the next rank

  • the most recent observed outcomes

This is where the customer can see whether the work is moving the company forward.

The Next move card surfaces the strongest action to keep momentum going.

When a priority highlight is available, the card shows:

  • a trust label such as Source-backed, Stale, Inferred, or User-entered

  • source labels

  • the priority title

  • a short summary

  • up to three evidence items

If no highlight is available, the page explains that more source-backed evidence is needed before it can surface the next move.

The Proof and signals card shows the evidence behind the report.

It includes:

  • the current proof stage

  • total proof events

  • recent proof count

  • the latest proof date

  • recent outcome events

  • three high-level status tiles for the website, SEO, and social signals

  • warnings if the report needs attention

This section matters because it explains the report instead of just asserting a conclusion.

The Connected signals section shows the integrations that are actively informing the report.

Only connected integrations appear here. They are sorted by relevance and limited to the top three. Each card shows:

  • the source label

  • freshness or sync status

  • trust label

  • a note about the signal

  • a small set of metrics

If no integrations are connected yet, the page says that reporting will stay founder-first until real source data is available.

Before you read any metrics, make sure the company in the header is the one you want to inspect.

Start at the top. The headline and subheadline tell you the report’s main story in plain language.

Confirm the current goal and the execution percentage. That tells you whether the report is focused on the right outcome.

Look at the current assessment and the progress to the next rank. This is the quickest way to understand whether the company is improving.

If there is a priority highlight, read the title, the summary, and the evidence. Do not skip the evidence if you need to explain the recommendation to someone else.

Use the proof section to see whether the report is grounded in recent events or still needs more data.

If the report is missing an important source, check the connected integrations section and the integrations page next.

If the report is loaded successfully, the customer can use it as the current source of truth for what changed and what should happen next.

If the report is still loading, the page shows a skeleton or refresh state instead of an empty dashboard.

If the report cannot be loaded, the page shows an error message that says the report needs a retry while assessments and tasks remain intact.

If the selected company changes, the page tracks the switch and reloads the report for the new company.

If no company is selected, reporting cannot load. Choose a company first.

That means the report request failed, but the underlying company tasks and assessments still exist. Try again after a moment.

The report can still work without integrations, but it will have less source-backed evidence.

Warnings are there when the system thinks the report needs more data or when some signals are stale. Read the warning text before changing the task plan.

The Open live website link only appears when the company has a live website URL in the report data.

Common problems

If something does not look right, confirm you are using the correct account, page, and permission level.

Related articles

Did this answer your question?