JB QuantsAsset ManagementGlobal MarketsTradingAsset Management · Global Markets · Trading
The desk that
remembers everything.
A private operations platform for a family investment practice. Positions, research, market structure and client reporting in one system — built so that every decision can be reconstructed years after it was made.
What it does
Trade journal
Every execution recorded against the thesis that produced it. Corrections are appended, never overwritten, so the record of what was believed at the time survives being wrong.
Market review
Structured reads on price, positioning and real taker flow — spot against perpetual, open interest, funding — reduced to scenarios with explicit triggers and invalidations.
Portfolio reporting
Positions, allocation and concentration across every asset class, priced live. House books and managed accounts are held apart by construction, not by convention.
Research notes
Theses, levels and reasoning captured in the moment and cross-linked to the trades they informed, so a decision can be reconstructed months later.
Watchlist
Valuation screens with accumulation zones, laddered entries and invalidation levels, checked against the tape daily and surfaced when something reaches its zone.
Events calendar
Macro prints, earnings and unlocks on one timeline, so positioning is never surprised by something that was scheduled.
Built for the standard we intend to be held to, not the one we are held to now.
Two people and their families is a small operation. The constraints below are the ones a much larger one would be required to meet, adopted early because they are far cheaper to build in than to retrofit.
Append-only by design
The ledger is never updated in place. A correction is a new row pointing at the one it corrects, which means the audit trail is a property of the schema rather than a policy anyone has to remember.
Separated books
Proprietary and managed capital live in different tables under different access rules. Nothing in the system can express a position that belongs to both.
Least access, enforced below the UI
Permissions are enforced in the database, not the interface. A client account can read one portfolio and acknowledge instructions addressed to it — the boundary holds even if the front end is wrong.
Sign in to your desk.
Accounts are created by the team. If you manage capital with us, use the Google address we hold for you.