@novaexai profile picture
Novaex.ai @novaexai

AI-powered platform for global pricing, commodity risk, and position management.

Joined October 2025
  • Tweets 118
  • Following 12
  • Followers 47
31 Photos and videos
A metals trader reconciles a pricing discrepancy. One cell updated. The spreadsheet raises no flag. The contractual formula is silently overwritten. That cell feeds three downstream calculations.
1
21
more replies
That static value propagates downstream: → MTM valuation (wrong) → Hedge ratio calculation (wrong) → Physical vs. paper position reconciliation (wrong) → End-of-day P&L report (wrong) Every downstream system accepted the override as authoritative. None flagged it.
1
14
Spreadsheets are capable tools. They are not an enforcement mechanism for contractual formula integrity. The standard: immutable pricing logic, flagged overrides, and fully auditable calculations. By design, not by process. #Metals #CTRM
9
Novaex.ai@novaexai
Jun 12
Metals desks with consistent position intelligence don't broadcast it. They route it directly to the trader ready to execute. While counterparts manually reconcile LME exposures, your desk needs the workflow to act first.
16
When LME copper moves 2% in a session and your position visibility lags, that is a defined, measurable gap in your hedge workflow.
1
28
more replies
Novaex Pulse delivers real-time position visibility across those exact sessions. Novaex Ledger closes the execution gap. Both are built depth-first: a single integrated workflow covering LME, COMEX, and SHFE, with no reconciliation layer between them.
1
34
If you can name the gap (the session, the exchange, the manual workaround), a Novaex diagnostic maps exactly what Pulse or Ledger resolves. No sales pitch. Request a 30-minute diagnostic session: [link] #MetalsTrading #CTRM
35
Novaex.ai@novaexai
Jun 10
Novaex's anchor client directly shaped our core architecture. By letting live trading workflows drive the design, we built a system for real operations. Transactional CTRMs cannot replicate this foundational integration through post-deployment configuration alone.
25
Novaex.ai@novaexai
Jun 9
Implementation complexity is the most cited and overstated barrier to CTRM adoption. No six-figure deployment budget. No multi-month integration timeline. Novaex is operational before your next position opens.
41
Covering 50 markets and accurately modeling 50 markets are different capabilities. Breadth-first vs. depth-first isn't just an architectural preference. It surfaces in the formulas a platform won't support and the exchanges it approximates rather than implements.
1
34
more replies
Physical contracts reference specific price sources: LME official, Platts assessment, Fastmarkets MB, SHFE spot. The source determines the settlement value. Aggregating price signals without source, window, and date attribution cannot support physical contract settlement.
1
32
Depth-first is a standard, not a feature set. Approximating LME prompts, collapsing COMEX and MCX to a single price, or sourcing without attribution does not meet metals trading requirements. These are the conditions traders work in daily, not exceptions to plan for.
51
Manual reconciliation of base metals positions across LME, MCX, COMEX, and SHFE consumes 5-8 hours per week. Every spreadsheet-based trading decision carries that cost. It's time spent reconstructing positions instead of acting on the market.
1
63
Novaex onboarding begins with one step: a 45-minute scoping call. Scheduling takes 4 minutes. Total time to full position visibility across LME, MCX, COMEX, and SHFE: 49 minutes. That's less than a single morning of manual reconciliation.
1
1
72
Schedule the Novaex consultation: [link]. Required input: name, current stack, and exchange coverage. Total commitment: 49 minutes. One week of manual reconciliation across those four exchanges exceeds that time. The math is simple. #CTRM #MetalsTrading
1
37
Novaex.ai@novaexai
Jun 4
Spreadsheet version history reflects what you chose to document. A system-generated, timestamped formula log reflects what actually executed. In a pricing dispute, only the latter is a defensible audit record.
1
20
Load more