How Redding Ridge Uses AI to Assemble Credit Portfolio Data

Jack McDonald and Rowspace’s Michael Manapat discuss portfolio construction, reconciliation and the need to validate fragmented financial data.

JMJack McDonald게스트 · Redding Ridge Capital
채널
AI Engineer
게시일
2026년 10월 16일
영상
18:57
읽기
4분
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

Rowspace co-founder Michael Manapat talks with Jack McDonald of Redding Ridge about applying AI to structured-credit workflows. McDonald describes initial portfolio construction and purchase reporting that his team says became faster, while retaining portfolio-manager judgment and daily quality checks. The discussion emphasizes authoritative data sources, hands-on collaboration and the complexity of financial operations. The reported timings are the participants’ experience, not independently verified benchmarks.

  1. 1Portfolio constructionMcDonald describes the rules and documents behind CLO portfolios.
  2. 2A faster initial draftHe reports a reduction from days to minutes in his team’s workflow.
  3. 3Purchase reconciliationThe reported process still includes daily human quality checks.
  4. 4Reliable sourcesThe teams work together to reconcile and validate financial data.
  5. 5Learn the workflowMcDonald advises builders to spend time with domain experts.

핵심 정리

  1. Credit workflows depend on fragmented documents, calculations and data sources.
  2. An initial portfolio still requires a manager’s judgment and refinement.
  3. Reconciliation automation should preserve quality checks.
  4. Teams need to determine which source is authoritative for each use.
  5. Builders should learn existing workflows directly from domain experts.
전문

챕터별로 다듬은 전문 읽기

01

Structured credit and fragmented data

The speakers introduce the business and its data challenges.

Michael Manapat introduces Rowspace, which works with financial firms to reconcile fragmented data using agents. He is joined by Jack McDonald, COO of Apollo-affiliated structured-credit manager Redding Ridge.

McDonald says Redding Ridge manages structured credit, primarily collateralized loan obligations or CLOs. He describes the firm as a separate operating company and says it managed about $50 billion at the time of the talk.

He describes thousands of incoming data points across many funds and investments. Active CLO management depends on having current, consistent information available when portfolio managers make decisions.

Much of the information is private and fragmented across documents and systems. McDonald says Rowspace works alongside the team to understand calculations, workflows and which source should be authoritative.

02

Portfolio construction and reconciliation

McDonald describes two team-specific workflows and their reported timings.

His first example is portfolio construction. CLOs have specific tests and payment waterfalls embedded in indentures and legal agreements, which portfolio managers must take into account.

He says a manager previously spent roughly two to three days building a mock portfolio of 200 to 400 credit names in Excel. In his team's experience, current information and the new workflow can produce an initial portfolio in minutes.

McDonald characterizes that output as roughly 80–90% complete, after which portfolio managers apply judgment and refine it. These figures describe his team's experience, not an independently verified guarantee of accuracy or speed.

The workflow brings together document libraries, trade and compliance systems, and pricing data. The point is not just generating text, but assembling information used in a portfolio decision.

His second example is warehouse purchase activity. Previously, staff reconciled purchases and sales across bank statements and sent a weekly recap to management.

McDonald says the reporting process is now repeatable in about a minute in their implementation, with staff performing daily quality checks. He compares it with a former manual process that occupied two or three people for hours each week.

03

Trust and validation

They discuss authoritative sources and collaboration.

Manapat asks why a general chatbot is insufficient when the output supports trading and portfolio decisions. The practical issue is not just model capability but access to the firm's own validated data and business rules.

McDonald says general-purpose models are useful for research and learning, while their implementation centers on the firm's own data. General models can also be connected to private data; the distinction he emphasizes is how this particular workflow is grounded and validated.

He says one data item may appear in many sources, with only one appropriate for a particular purpose. Rowspace staff sit with portfolio and finance teams to understand the calculations and select or reconcile sources.

The team validates information from trade management, performance systems and external pricing sources before relying on it. Automation reduces manual assembly, but the speaker does not claim that verification is unnecessary.

04

Adoption and competitive advantage

McDonald discusses finance adoption and organizational goals.

Asked about Apollo's adoption culture, McDonald describes a willingness to adopt new technology, improve team capability and replace repetitive processes. These are his observations about the organization.

He considers AI adoption in large financial organizations to be early. Banks and asset managers have complicated middle- and back-office systems, and applications must account for that complexity.

At Redding Ridge, he says the immediate focus is making routine work more efficient so staff have capacity for other projects. He also expects some research and junior-support tasks to change over time.

Manapat asks whether AI will become a common productivity tool or a lasting competitive advantage. McDonald thinks it can improve competitiveness when combined with a strong process and reliable information.

In active and private markets, he sees value in knowing available liquidity, prices and other relevant facts promptly. Inaccurate information, by contrast, can flow through decisions to the organization and its investors.

05

What comes next

He outlines goals for accuracy and advice for builders.

Looking ahead, McDonald wants confidence in information shared with investors without spending excessive time on manual checks. This is a goal for the team, not a claim that errors have been eliminated.

He also wants technology to become part of the team's everyday thinking. Time saved on routine tasks can be used to ask why a process exists, whether it should change and what tools would help.

His advice to builders is to recognize that financial organizations are highly nuanced. A workflow that appears unusual may exist for a reason; spend time with the people who actually perform the work.

McDonald attributes progress with Rowspace to the team's sustained presence with the portfolio and finance staff. Manapat closes by emphasizing the human and technical work required to make such systems useful.

같은 채널의 다른 글

슬라이드 9장21:32EN
AI Engineer· 2026년 10월 29일Shy Ruparel on AI agent reliability and recovery after failuresShy Ruparel · TemporalTemporal’s survey finds a gap between frequent agent use and dependable deployment. Ruparel demonstrates a synthetic payout workflow that resumes after workers stop.에이전트관측 가능성과 안정성에이전트 엔지니어링+2
슬라이드 7장14:50EN
AI Engineer· 2026년 10월 29일Cole Gannaway on code review, cross-repository risk and AI software factoriesCole Gannaway · QodoA one-line rename can pass local checks while affecting distant clients. Qodo’s Cole Gannaway explains how review context, shared rules and independent agents can expose those risks.Code review & verification코딩 에이전트개발 워크플로와 테스트+2
슬라이드 5장11:47EN
AI Engineer· 2026년 10월 29일Revolut’s David Abitbol on self-hosting AI coding models at scaleDavid Abitbol · RevolutAbitbol shares engineering delivery trends, GPU-serving costs and latency tuning, then describes controls for operating the tools in a regulated bank.Local inferenceAI cost & performanceDeveloper productivity+2
슬라이드 4장21:47EN
AI Engineer· 2026년 10월 28일Patrick Smyth on Open-Source Supply Chain Security in the AI EraPatrick Smyth · ChainguardChainguard’s Patrick Smyth discusses faster exploitation, malware in dependencies, zero-days and the expanding attack surface around developer workflows.CybersecurityOpen-source ecosystemsAI security+2
슬라이드 5장14:09EN
AI Engineer· 2026년 10월 28일Taylor Luttrell-Williams on Finding Logic Vulnerabilities with SonarQube Hunter AgentTaylor Luttrell-Williams · SonarSonar’s Taylor Luttrell-Williams explains how a security agent maps a codebase, investigates logic flaws and presents validated findings alongside conventional scans.CybersecurityAI securityCode review & verification+2
슬라이드 5장16:29EN
AI Engineer· 2026년 10월 28일Chris Vela on Benchmarking vLLM Configurations with Runpod BenchPodChris Vela · RunpodRunpod’s Chris Vela demonstrates a dashboard for comparing LLM serving configurations and choosing performance settings with workload-specific data.InferenceBenchmarksAI cost & performance+2