Step 1 — Multi-Timeframe Confluence
No signal ships from a single chart glance. Every setup must show alignment across at least two timeframes before it qualifies: a daily trend confirmed by intraday structure, a weekly level respected by the 4-hour, momentum and structure pointing the same direction. This filter exists to eliminate the low-probability noise that fills most signal channels — the setups that look good on one timeframe and are obviously wrong on the next one up. Confluence doesn't make a trade certain; nothing does. What it does is raise the baseline quality of everything we send, so members aren't paying to follow coin flips. If a setup can't pass this step, it never becomes a signal — full stop. Some trading days produce nothing, and we consider that a feature: the discipline to send no trade is what separates a methodology from a content machine that has to post something every day to look busy.
Step 2 — Risk-First Position Sizing
Every signal is built backwards from the risk. The stop loss — the level that invalidates the idea — is defined before the target is even discussed. From there the reward-to-risk ratio is calculated, and if the structure doesn't offer an acceptable R:R, the trade is discarded no matter how attractive the chart looks. Each signal that does ship includes a suggested position size relative to account risk, because the same trade at the wrong size is a different trade entirely. A full stop-out should be a normal business expense, not an account event. This is the step most signal services skip, because "buy here, trust me" is easier to sell than a framework. It's also the step that determines whether a member survives long enough for the edge in steps one and three to actually compound. Risk management on this site isn't a legal disclaimer at the bottom of the page — it's the strategy itself.
Step 3 — Pre-Market Catalyst Review
A technically perfect setup can still be a terrible trade if it walks blind into a scheduled event. Before any signal is sent, it's screened against the day's catalyst calendar: CPI, FOMC, jobs reports, earnings on the names we trade, plus overnight sentiment and futures positioning. Signals that conflict with a known catalyst are held until the event resolves — or discarded entirely. On heavy event days, that often means no signals until the data is out and the initial reaction has settled. This step is deliberately boring, and it's one of the main reasons our losing trades tend to be small and explicable rather than catastrophic. It also feeds directly into the post-trade annotations in step four: when a trade does lose, we can usually point to exactly which assumption failed, because the known risks were written down before entry, not rationalized after the fact.
Step 4 — Transparent Post-Trade Annotation
The process doesn't end when the trade closes — that's where the accountability starts. Every closed signal, win or loss, is recorded on the public ledger with its entry, exit, return, and P&L, and annotated with what actually happened: what worked, what didn't, and which assumption broke. Losing trades are never deleted, edited, or quietly memory-holed. You can browse the recent closed signals on the track record page, or the complete real-time history on the live dashboard at dashboard.prismagroup.online. This is what turns a signal service into something auditable: members aren't asked to trust a win rate, they're handed the raw data the win rate is computed from and invited to check it. Past performance does not guarantee future results — but an honest record of the past is the only fair basis for judging anyone's process.
See the Process in Action
The fastest way to evaluate this methodology is to watch it run. Join the free Discord channel and observe signals moving through all four steps in real time, then verify the outcomes against the ledger. When you're ready for the full suite — options, gold, forex, live sessions, and the Nora AI terminal — plans are on the homepage pricing section, covered by a 48-hour money-back guarantee for new subscriptions. Common questions are answered on the FAQ page.