The Commandix platform

Run the work.
Know where
it stands.

Manage tasks, projects and sales in one platform. See who is delivering, what is overdue, and where your team needs help.

Real product. Sample company. Start with the CEO account.

A company view you can drill into
Commandix dark-theme dashboard with company goals, department completion and sales results in the fictional Acme demo.

Start with company results. Open the department, team or work that needs attention.Actual product · Fictional Acme demo

01 / Task management

What needs to
get done next?

Turn a commitment into a task with an owner, a priority and a due date. Keep the updates and blockers beside the work, where the next person can find them.

  • Keep the queue clearMove between board, list and calendar views. Filter by team, status, priority and date.
  • Give the detail an ownerBreak tasks into subtasks. Record dependencies, blocked reasons and comments.
  • Keep routine work movingUse recurring parent or standalone tasks for weekly, monthly or custom-interval work.
Explore task management
Commandix task board showing To Do, Doing, Blocked and Done work with owners, priorities and project links.

Separate work that is ready, underway, blocked or finished before choosing the next priority.Actual product · Fictional Acme demo

02 / Project management

See the plan.
Open every layer.

Keep a project’s owners, collaborators, tasks and goal together. Move from the whole project to the nested work behind a deliverable.

  • Choose the view for the questionUse boards and lists for execution, calendars for due dates, and the timeline for dated work.
  • Drill into the structureExpand the horizontal mind map, focus a branch and open any visible task.
  • Inspect the handoffsUse the dependency graph to see explicit task relationships. A subtask describes structure, not execution order.
Explore project views
Commandix project mind map with horizontal branches, nested subtasks and owners in the fictional Acme company.

Inspect the work below a project summary. Expand a branch to see its subtasks and owners.Actual product · Fictional Acme demo

Keep the company goal in reach.

Link projects and tasks to goals so a review can follow the work supporting a priority.

  1. Company goal
  2. Project
  3. Task
  4. Subtask

03 / Sales management

Which deals need
the next move?

Manage the pipeline and the work needed to advance it. Keep each deal’s owner, stage, expected close date and activity in view.

  • Work the pipelineMove deals through Lead, Qualified, Proposal, Negotiation, Won and Lost. Switch between board and list.
  • Keep the conversation attachedLog calls, emails, meetings and notes. Open linked tasks when a deal needs work from the team.
  • Review the sales resultCompare deal values, weighted pipeline and seller history. Check task and team context before choosing a response.
Explore sales management
Commandix sales pipeline showing deal stages, assigned sellers, close dates, open value and weighted pipeline.

Review each stage and its next follow-up. Weighted pipeline is an estimate, not booked revenue.Actual product · Fictional Acme demo

04 / Team performance

Spot low performance.
Then ask the right question.

A missed deadline, lower completion rate or growing workload needs context. Find the signal, open the work, and decide whether to coach, unblock or reassign.

Three clicks to the people view.

From the company dashboard in the CEO demo:

  1. 1
    Engineering

    Open the department.

  2. 2
    Backend Team

    Follow the team’s results.

  3. 3
    People

    Compare completion and work signals.

Open a person for their tasks and goals. Use History to compare six months of recorded team results.

Explore teams and people
Commandix People view comparing Backend Team members with completion, active work and blocked-work context.

Start the conversation with the work behind the number. Opening an individual is a further click.Actual product · Fictional Acme demo

Context changes the decision. Low completion can reflect overload, blockers or different task scope. Compare responsibilities and periods before judging performance. The path depends on your hierarchy and access.

05 / Bottleneck analysis & follow-up

What’s holding
the work back?

When several tasks, projects or deals stall, inspect the shared queue, dependency or team behind them. Review the evidence before deciding what to change.

  • Inspect the likely bottleneckReview queue depth, waiting, affected work and confidence. Validate the candidate with the people involved.
  • Give the response an ownerRecord an action to protect capacity, change surrounding priorities or add capability. Management carries out the change.
  • Check whether it helpedCompare cycle time, lead time and completed work in Flow Analytics. Historical comparisons need recorded status history.
Explore constraint analysis
Commandix Constraints view showing a candidate bottleneck, queue depth, waiting, confidence and action choices.

Inspect a candidate and its supporting evidence. A score is a starting point for validation, not proof of a cause.Actual product · Fictional Acme demo

Make the first workspace useful

Start with a team.
Give the work context.

Useful reporting starts with records people maintain. Choose a real project or operating area, then build a review around it.

01

Set the structure

Create departments and teams. Assign people and agree who owns the project, the work and the review.

02

Record the work

Add tasks and deals with owners, dates and states. Link related work and record a specific reason when something is blocked.

03

Review and follow up

Open the work behind a weak result. Agree one change and check the next period. A new workspace needs history before trends are meaningful.

Before you decide

Know what you’re
evaluating.

Explore the sample company, check the workflows, and discuss the scope your organization needs.

Can the team create and manage its work here?

Yes. Tasks, nested subtasks, projects, goals and sales deals can be created and managed in Commandix. Team and leadership views use those records to support review and follow-up.

Can we use both subtasks and dependencies?

Yes. Subtasks break a deliverable into smaller work. Dependencies record which tasks depend on others. The mind map shows the hierarchy, while the dependency graph shows explicit handoffs. Creating a subtask does not automatically create a dependency.

How does work repeat?

Parent and standalone tasks support weekly, monthly or custom recurrence after completion. Subtasks do not recur automatically. Projects can be duplicated, but the copy needs review: hierarchy and dependencies are not preserved, and project recurrence is not automatic. See the project guide for the current copying limits.

How do pricing, access and rollout work?

Pricing is custom per organization. Agree the team scope, access requirements and rollout in your proposal. Review enterprise pricing, current connection options and the Trust Center before committing.

See it with real product data

Open a project.
Follow the work yourself.

Try the task board, expand a project mind map, inspect the sales pipeline and compare a team’s results.

Explore the live demo Fictional Acme company. Choose the CEO account.