Utsav's Profound AI Rep
Utsav structures ambiguous research problems into testable frameworks and applies quant methods across domains.
Utsav Agarwal
Edges
Structuring Quantitative Research Problems
Utsav's consistent pattern is taking a vague or large-scope problem and narrowing it to a set of testable, data-backed levers before building anything. This showed up at Blockhouse, where he spent the first two weeks mapping the data structure and KPIs before touching analysis, and at Notion Demand, where he evaluated multiple industries before committing to retail and a specific public dataset. His method is to define the right question first: identify the drivers, select the data source, validate assumptions through hypothesis testing, then move to output. He applies this sequence whether the domain is bond execution, inventory forecasting, or labor market intelligence. The result is research that holds up under scrutiny because the scope decisions are made explicitly and documented.
Spotted in 2 Stories
Quantitative Analysis Across Asset Classes
Utsav has applied quantitative methods across OTC bonds, equity portfolio optimization, and ML-driven forecasting, building a cross-domain analytical toolkit. At Blockhouse, he analyzed post-trade execution data across Treasury instruments, optimizing for slippage and transition cost. At Indxx, he deployed CVaR and hierarchical risk parity models for portfolio construction. At Conscience AI, he worked on price forecasting and trend prediction using hybrid deep learning models. His mathematical foundation runs through all of it: back-testing, hypothesis testing, KPI selection, and model validation are consistent tools regardless of the asset class or domain. For a research role, this means he can pick up a new instrument or market structure and apply a rigorous analytical process without needing to rebuild his toolkit from scratch.
Spotted in 3 Stories
Translating Research into Stakeholder Decisions
Utsav has consistently presented research findings to senior stakeholders — CEOs, co-founders, and HR heads — and structured his communication around what they need to decide, not just what the data shows. At Notion Demand, he briefed the CEO twice a week at each stage of the research sprint, presenting the reasoning behind scope decisions and the data validating each step. At Sartre Group, he prepared and presented labor law documentation to a Head of HR at a financial exchange, enabling a cross-border hiring decision. His approach is to lead with the validated finding and the decision it supports, then provide the supporting data. When findings do not support the expected narrative, he treats it as a scoping problem and brings the stakeholder into the revision process. This makes him useful in research roles where the output is a recommendation, not just a report.
Spotted in 2 Stories