PhoenixPhoenix Command

Phoenix field notes · resources

Stop trading blind. Review the process with precision.

A long-form resource surface for traders who want the dashboard, the journal, and the coaching notes to feel connected instead of scattered.

Built for execution

Command-center layout, honest analytics, and coaching notes designed to keep the review loop readable.

Early access

The current launch copy is limited and intentionally tight so the experience stays centered on traders who are actively using the tool.

Support

Support, purchase records, and account issues are handled through the documented support path instead of hidden contacts.

AI coach

KIZA is there to explain patterns, surface leaks, and summarize the trade story in plain language.

01

Deep analytics

Sniper Score is a process metric, not a vanity metric.

Phoenix combines win rate, profit factor, consistency, and discipline into one review surface so a green week does not hide a weak process. Use it to judge execution quality before you judge the balance.

02

Built for focus

The dashboard keeps the decision path visible.

KPI rows, trade context, P&L review, and coach prompts sit close together so you can move from result to cause without bouncing through a cluttered menu stack.

03

Universal import

Bring in history from the platforms you already use.

Phoenix is built around journal data, manual entries, and broker imports so your review flow can start with the trade record instead of a blank spreadsheet.

04

AI coaching

KIZA explains patterns, leaks, and recurring mistakes.

The assistant can summarize a session, surface recurring errors, and turn a rough trade journal into coaching notes that are easier to act on the next time you sit down.

05

Market context

Bias, levels, and session state should support the plan.

Market tools are most useful when they answer a question you already have. Phoenix keeps those surfaces close so the context sharpens the setup instead of becoming noise.

06

Reports and support

Review, export, and request help from one place.

Resources are meant to reduce friction. When something needs an explanation, a screenshot, or a documented issue, the support path stays visible and straightforward.

Deep Analytics

Institutional-style review surfaces for P&L, consistency, win rate, trade count, and execution quality.

  • Sniper Score
  • Profit factor
  • Consistency and discipline

Journal + Playbook

Document setups, track notes, and keep the trade story attached to the chart so the result does not erase the lesson.

  • Trade notes
  • Setup review
  • Historical context

AI Analyst

KIZA can coach the journal, summarize a session, and explain the pattern behind a recurring leak.

  • Pattern detection
  • Session summaries
  • Coaching prompts

Keep the edge honest

Phoenix tracks and explains execution. No bot statistic, market view, or AI response guarantees future results.

Read FAQ and support ->

FAQ

What should I read first?+

Start with the dashboard review loop. Check the trade, the setup, the calendar, and the notes together so you can tell the difference between a good idea and a good execution.

Why is Sniper Score included here?+

Because it is part of the review framework. It is meant to measure discipline and process quality, not to replace the full trade breakdown or to give a single number too much power.

How should I use KIZA?+

Use KIZA for explanation, pattern spotting, and coaching. Ask for the common error, the strongest session, the weakest setup, or a short summary of what changed in your recent run.

Where do bug reports and purchase questions go?+

Bug reports, account issues, and purchase questions should go to support@phoenix-cmd.com. Business and external-site requests should go to admin@phoenix-cmd.com.