Optimisation in a spreadsheet
A spreadsheet solver rarely states which weight bounds made the problem infeasible, or which covariance estimator it assumed — an analyst is left explaining a number they cannot fully trace.
For portfolio and risk analysts
An optimiser that prints what it assumed, a stress test replayed on the dates it actually happened, and a report a committee can read without a follow-up call to ask what the numbers mean.
01A week with Quant Compose
Day 1
Apply a universe and compute the full risk and return set — annualised return, volatility, Sharpe, Sortino, Calmar, drawdown, beta and correlation — for every security before any allocation decision is made.
Day 2
Sample covariance, Ledoit-Wolf shrinkage, a denoised random-matrix-theory estimator, or EWMA at a 0.94 decay. The estimator is a choice the analyst makes explicitly, not a default inherited silently.
Day 3
Mean-variance, minimum variance, maximum Sharpe, risk parity, hierarchical risk parity, Kelly or CVaR optimisation. An infeasible weight-bound combination is refused outright, and frontier points the solver could not reach are listed with the specific reason rather than dropped.
Day 4
Replay one of six real historical episodes — the 2008 crisis, the 2010 flash crash, the 2011 European sovereign selloff, the 2015 China devaluation, February 2018, or the 2020 Covid crash — on the portfolio's own loaded price history, or propagate a hypothetical shock through each asset's beta.
Day 5
Export the fixed evidence pack in PDF, DOCX, HTML or JSON, with portfolio construction and benchmark-relative risk as their own sections and the no-live-order-routing statement printed in the footer of every page.
02Three problems it removes
A spreadsheet solver rarely states which weight bounds made the problem infeasible, or which covariance estimator it assumed — an analyst is left explaining a number they cannot fully trace.
A stress scenario built from scratch each time is a new set of assumptions each time, and a shock magnitude picked without a stated method is hard to defend when questioned.
Assembling charts and tables into a committee memo by hand costs a day that could go to the analysis itself, and invites a transcription error the source data never had.
03Assumptions, printed
A committee does not need to trust the analyst's memory of what was assumed — the assumptions are in the output.
04Objections, taken seriously
They are printed. Frontier points the solver could not reach are listed with the reason, equal weight is always the baseline, and the covariance estimator is a choice you make, not a default you inherit.
You choose from four named methods — historical, parametric, Cornish-Fisher and Monte Carlo — and the choice appears in the output rather than being averaged away.
No. The workspace is a research and analytics tool; it does not place or route an order, run against a broker, or manage live positions.
Upload your own OHLCV price history as a CSV — the accepted format is date, ticker, open, high, low, close and volume — and build the allocation from it using any of the seven portfolio construction methods. There is no separate holdings-file import; weights come from a construction method run on your data.
05In beta, for you
What is available to portfolio and risk teams today.
Other audiences, and further reading
Related capabilities
Beta access is open to individual analysts today; teams standardising across a desk should get in touch directly.