LenGrowth is organized around one simple workflow: set the objective, turn it into tasks, track the result, share the work, identify the right capability, match the support mode, bring the specialist in, and keep improving.

Use this article when you need help with this topic in LenGrowth.

LenGrowth helps customers move from a business goal to visible execution. The product starts by collecting context about a company, then uses that context to surface tasks, route work, and show what changed.

That means the platform is most useful when someone needs to answer questions like:

The product is not just a list of tasks. The routes in the app are designed to support the full flow from first setup through reporting and review.

The first step is to define the company and the goal. In the app, that usually happens through the company creation flow on https://lengrowth.com/companies/new or from the company list on https://lengrowth.com/growth.

The onboarding experience asks for enough context to understand whether the business is a new idea or an existing company. It also asks for the stage, the team context, the near-term goal, and the company information needed to make the next steps useful.

You should use this step when you are starting from a blank slate, when you are creating a new company profile, or when your current company details are outdated and need a reset before you can move forward.

Once the company exists, LenGrowth turns the objective into task work. You can see that in the company workspace route pattern, /companies/[id], and in the company task routes under /companies/[id]/tasks and /companies/[id]/tasks/create.

The task flow is built to help you choose between suggested work and custom work. In the task creation modal, the product offers two starting points:

That is the product's way of separating "review what is already prepared" from "define a new piece of work yourself."

Once tasks exist, the app shows them in the task list, the execution pipeline, and the company workspace. The task page supports status-based review, and the pipeline page shows work as it moves through stages.

The important idea here is that LenGrowth does not treat a task as finished just because it was created. The result has to be visible, and the current status has to make sense to the people who are using the workspace.

Sharing the work means making execution visible to the rest of the team. In the product, this happens through company workspaces, task detail views, the pipeline, notifications, and team-related pages.

If a customer needs to bring other people into the work, the app gives them places to review the company, open task detail, inspect the pipeline, and manage settings or team access.

LenGrowth routes work differently depending on the company type, the task type, and the task detail. That is why the product asks for company context before it starts suggesting or creating tasks.

This step is about choosing the right kind of work before you try to assign it. A customer can only get useful recommendations if the company profile is specific enough for the product to understand what kind of capability is needed.

The product makes a clear distinction between work you handle directly, work that is prepared as a suggestion, and work that needs specialist support. The subscription page at https://lengrowth.com/subscription explains the current plan, support boundary, and plan features.

You should review this step when you are not sure whether a task should be handled as a simple internal task, a suggested next move, or a task that needs additional support.

If a task needs specialist involvement, the task creation flow includes Request Specialist immediately, and the task detail view also exposes specialist-related actions. The product uses the task detail surface to coordinate work, review results, and move the task forward when a human specialist is involved.

You do not need to guess whether a task is meant for specialist support. The task detail and task creation surfaces make that route visible when it applies.

The final step is to keep the loop going. LenGrowth uses the dashboard, reporting, and company workspace to show what has changed, what is complete, what still needs attention, and what should happen next.

That loop matters because the product is built for ongoing work, not one-time setup. A customer should be able to return to the dashboard, see today's focus, inspect up next items, review reporting, and make a better next decision based on what already happened.

If you are new to LenGrowth, these are the main places to begin:

If you already know which company you want to work on, open the company workspace route pattern /companies/[id] instead of starting from the top-level pages.

When a customer completes the company setup flow, LenGrowth opens the company workspace so they can continue the first-run flow there.

When a customer opens the dashboard, they should see a general summary of company activity, today's focus, up next tasks, and their company list.

When a customer opens the growth workspace, they should see a list of companies, search and filter controls, and a growth-focused summary card.

When a customer opens the task list or pipeline, they should see work organized by execution state rather than a single flat list.

When a customer opens reporting, they should see the current company reporting state and a view that is tied to the selected company.

If there are no companies in the account, the dashboard and growth pages will prompt the user to add one. In the product, that usually means going to https://lengrowth.com/companies/new or using the Add Company / Add Your First Company button where it appears.

Use a new company when the business does not already exist in LenGrowth. Use the edit flow when the company already exists and you only need to update the profile details.

Start with the company page, the dashboard, or the onboarding flow. Those screens are built to collect the first useful signals. If the information is still too thin, LenGrowth may show missing-context or guidance states rather than a finished plan.

Check the company task page and the pipeline before assuming the task is missing. The product shows work in more than one place, and some tasks are best understood in the pipeline rather than in the main list.