Live strategy status
Live strategy status
Current PnL, exposure, and open positions are visible after approval.
Experiment / Signal
Minimal surface area. Strong hierarchy. Almost no cards.
This direction is the most aggressive reduction: mostly text, thin dividers, inline stats, and a single strong CTA.
API-fed reporting cadence
NDA required before access
Manual review allocator approval flow
Use this if you want the brand to feel colder, sharper, and more institutional.
It strips out most decorative containment and relies on spacing, typography, and a few numbers. It can feel more expensive if the copy is tight and the investor workflow is serious.
Request AccessOOS integrity
OOS integrity
Separate out-of-sample reporting keeps model validation distinct from production results.
Access control
Access control
The NDA and manual review process are treated as product features, not administrative friction.
Trade transparency
Trade transparency
Approved users can inspect executions, thesis tags, and current mark-to-market results.
Why this works
It feels expensive because it says less.
This direction would be strongest if the final site uses precise copy, strict claims discipline, and very high-quality supporting data inside the portal. The restraint makes the gated content feel more important.
Compare with longer versionSequence
01
Public thesis
A direct statement of what the strategy is and why it is different.
02
Selective proof
Only a small set of public metrics, enough to create confidence without leaking the data room.
03
Approval gate
A simple request-access path that makes the protected material feel intentional.
04
Reporting reveal
Portal views become the proof layer: current PnL, OOS, positions, trades, and access state.
Portal Preview
The mock portal can stay equally spare.
For this direction, the gated reporting section should avoid colorful dashboards. It should read like a controlled ledger: simple rows, timestamps, and direct metric labels.
- current_pnl+18.4%
- oos_track+11.7%
- open_positions3
- trade_rows4 preview
- data_statusdemo_public
FAQ
Q
Who is this direction for?
Buyers who prefer confidence, restraint, and precision over visual storytelling.
Q
What should be avoided?
Over-explaining the model, over-decorating the page, or making claims that should be proven in the portal.
Q
How does it sell?
It sells by implying discipline. The public page stays spare, and the protected reporting preview carries the weight.