The proposed product is an inspectable research workflow: market context, portfolio evidence and reproducible experiments. Its value should come from useful work delivered and time saved—not a promise of investment returns.
Pre-launch proposals. No paid subscriptions or pilots are currently for sale. The inclusions below describe proposed customer deliverables, not current public entitlements. Prices, coverage, limits, timing and final terms remain unannounced. Registering interest is free.
PROPOSED PLAN
Research Workbench
For independent researchers comparing market behavior across horizons.
Spend less time assembling context before deciding what deserves further research.
A defined research pilot with agreed datasets and review criteria
Reproducible experiment records and cost-stress review
An evidence and limitations report for each agreed research question
Onboarding and a scoped review/support arrangement
Existing foundation. Implemented locally: registered experiments, frozen fits, replay, robustness checks and shadow evidence review. Commercial team access and service commitments are future work.
THE PROPOSED COMPETITIVE EDGE
Make a result easier to trust—and challenge.
The opportunity is to bring market context, evidence history and review discipline into one understandable workflow. Customer demand and a durable competitive advantage still need to be demonstrated.
01 / CONTEXT
One price, several horizons
Compare the same market through Tactical, Swing and Structural windows. The intended benefit is a clearer research question when timeframes disagree; fractal diagnostics remain experimental.
02 / TRACEABILITY
See what was known then
Retained inputs, knowledge cutoffs, frozen forecasts and replay connect an output to its evidence. The intended benefit is less manual reconstruction during a review.
03 / DISCIPLINE
Understand why it stops
Missing data, expired costs, unverified accounting and qualification blockers remain explicit. The intended benefit is spotting an unsupported conclusion before relying on it.
Charting and backtesting are established capabilities: TradingView documents strategy simulation, and QuantConnect documents backtesting. Our positioning is a focused combination of horizon context and evidence review. We have not established that these capabilities are unique, or that this engine outperforms those products.
A researcher could pay to shorten the path from a question to an inspectable experiment. A portfolio owner could pay for clearer reconciliation and exception review. A team could pay to reduce the work of reproducing results. Those are testable customer-value hypotheses; we have not yet validated willingness to pay or measured time savings.
What would a first pilot deliver?
The proposed starting offer is a bounded research or portfolio-evidence review: agree the question and permitted data, deliver a source-linked review with an exception register, and walk through the findings and limitations. Scope, delivery cadence, acceptance criteria and price would be agreed before any paid engagement. This service is not launched.
How would we measure whether it is worth paying for?
Compare review time against the customer’s existing process, check whether another reviewer can reproduce the result, and ask whether the evidence and exception report changes the quality of the review. Renewal and willingness to pay would validate the offer. A favorable backtest alone would not.
What is not included?
Current proposals do not include personalized buy/sell recommendations, automatic trading, custody, guaranteed returns or a claim of qualified strategy performance. Live recommendations and execution remain disabled. The public website is a demonstration, not a connected customer account.
What must happen before launch?
We still need agreed data rights and coverage, reliable customer access, billing and support arrangements, operating-cost validation, and review of the intended commercial offering. Portfolio deliverables must respect incomplete accounting. A future trading product would additionally need qualified research, operational evidence and production acceptance; it is not part of these proposed plans.
Can my team use a public API today?
No commercial public API is launched. Existing internal contracts are documented on the developer page. Public authentication, team entitlements and service commitments remain future work.