The problem: Bitsgap’s current bot portfolio view reports “Total Capital Deployed” as the sum of capital across every bot ever launched (running + closed). For anyone who recycles the same capital into sequential or overlapping bots — which is normal bot usage — this figure is misleading. It makes it look like far more money was invested than actually was, because the same dollars get counted again every time they’re redeployed into a new bot. This distorts the portfolio’s real profit percentage and makes performance look worse (or, depending on framing, artificially diluted) than it actually is.
The fix isn’t a new number bolted onto the existing one — it’s a small set of metrics, computed together, that tell the real capital-efficiency story. I built and verified all seven of these in a live spreadsheet on top of Bitsgap’s own bot log data, so the calculation logic below is proven, not theoretical.
Requested metrics:
Real Capital Invested (Average, Time-Weighted) — the average capital actually deployed across running bots, weighted by how long each amount was deployed (a day-by-day concurrent-capital sum divided by active days), instead of a naive sum of every bot’s capital. This is the number “Total Capital Deployed” should really represent for anyone recycling capital.
Profit % on Real Capital Invested — net profit divided by the time-weighted average above, not by the inflated all-time sum. This is the return figure that reflects what the money genuinely earned relative to what was genuinely at risk on average.
Peak Capital Deployed (Max Concurrent) — the single highest concurrent capital commitment across all bots at any one moment. Distinct from the average — this is the number a trader needs for capital-reserve sizing (“how much do I need available to run this strategy at full tilt”), and it should be shown alongside the average, not instead of it.
Total Active Days (≥1 bot running) — calendar days where at least one bot was open, counted once even when multiple bots overlap (no double-counting overlapping runtimes).
Idle Days (waiting for market) — days since the first bot launch where nothing was running. This surfaces how much of the tracked period was actually spent out of the market waiting for a signal, versus deployed.
Profit % Annualized (on Active Days) — the real return scaled to the time it was actually at risk, not the full calendar span since account creation. A return earned in a few active months should be expressed at its annual pace, not diluted by idle time.
Avg. Bot Duration (Days) — the average lifetime of an individual bot (sum of each bot’s own duration divided by number of bots). Useful for understanding typical holding period and cycling speed, distinct from the active-days union metric above.
Why this matters: Right now, users have no native way to see their actual return on actual capital risked, or to understand how much of their tracked history was spent deployed versus idle. Anyone running more than a couple of sequential or overlapping bots is currently looking at a “Total Capital Deployed” figure that overstates their investment and understates their real return %. These metrics are all derivable directly from data Bitsgap already logs per bot (launch date, close date, capital allocated, P&L) — no new data collection is required, only new aggregation logic on the existing bot history. Implementing this would give users an honest, at-a-glance read of capital efficiency instead of forcing them to export bot logs and calculate it manually (which is what I had to do).
Priority: High — this affects the core “is my strategy working” question every bot user is trying to answer, and the current default metric actively misleads on that question.