Engineering brief
How a $64M Firm Runs Wealth Management on AI Agents
At a glance
Worth watching
- Relevance
- Practical value
- Radar
- Time horizon
- Now
- Warnings
- None
Arca built a custom agent harness that handles 10-day financial workflows, from tax analysis to compliance checks. Agents never execute trades without human approval.
First detailed production case of AI agents running core business workflows with human oversight.
Watch if you are building AI agents for regulated, long-horizon workflows with human oversight.
Summary
The setup. Arca is an AI-native wealth management firm that raised $64 million. Aman Singh leads their AI platform team, building a harness that runs the business with AI. The firm does not replace financial advisors but automates the work around them: analysis, research, monitoring, and compliance checks. Clients interact only with human advisors who are supported by a proactive agent system running 24/7.
The architecture. Arca uses frontier models from Anthropic and OpenAI, primarily Claude, but stays model-agnostic through internal benchmarks. They recently tested Luna and found it too slow and costly despite strong external benchmarks. Model selection is tiered by task complexity: tax analysis uses the heaviest tier, background monitoring uses lighter models. The harness itself is custom-built and manages memory, tool execution, and guardrails.
The long-horizon challenge. A client tax-bill scenario spans 10 days. Agents handle internal analysis fully autonomously but cannot execute trades or move money without human approval. Memory systems track every client's state: what happened, who owns what, what is due next. A 'dreaming' process reflects on the world state and updates memory for long-term tasks. New signals, like a phone call, wake a fresh agent that reads the persisted context and contributes to the ongoing process.
Safety and compliance. All safety restrictions are deterministic, removing decision-making from agents. LLM-based verification runs on every write to the database. Prompt injection detection runs on incoming emails, documents, and phone calls. Data leaving the system, such as calendar invites, is checked for PII exfiltration by both deterministic rules and a consensus of small models. Every action produces an audit log, which also powers agentic capabilities.
Feedback and improvement. Every staff edit or cancellation becomes an evaluation. Feedback is coupled with agent traces, and nightly a meta-agent analyzes them to suggest harness improvements: misleading tools, errors, or missing knowledge. Prompt changes still require a human engineer to review because agents tend to over-correct. Knowledge bases are curated by experts as a first-class product feature, with citations and editing built into the advisor workflow.
The bottom line. Arca's agents are more proactive than reactive: they prompt humans, not the other way around. They discovered hidden fees and a non-fiduciary status for a prospective client, something a human might miss. Singh argues that being the firm itself, not a SaaS vendor, lets them standardize workflows and own the intelligence. He warns against depending on managed agent products like Anthropic's, because losing control of memory and operational knowledge means losing the ability to differentiate.
My take
This is one of the most grounded agent deployments I've seen. No autonomous trading, no replacing advisors, just thoughtful automation of the grunt work. The emphasis on deterministic guardrails and audit-by-default is exactly what regulated industries need. I'm less convinced that being the firm itself is the only path; a SaaS provider could replicate this if they invested in the same harness quality. The feedback loop with meta-agents and human review is smart but adds latency. Teams should watch how they handle the 'nasty prompt changes' problem, that alone is worth the demo time.
What to do with this
- Review your agent system's memory persistence: can a new signal correctly resume a 10-day workflow?
- Audit your sandbox strategy: does code execution have deterministic guardrails before data reaches production?
- Build a feedback pipeline that couples staff edits with agent traces for nightly improvement analysis.
Watch the video
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
Why Jev treats AI as a database, not a coworker — and
TypeSafe launches Jev, a model built for programmatic decision-making, not human chat. Three structured output types, calibration scores, and a sharp…
The real recipe for AI support: structure, not model size
AI support agents work with structure: cheap classifier, strict schemas, deterministic guardrails, evals. A practical blueprint behind a six-client claim.
Supabase's agent takeover: what the shift from human to machine users means
Supabase's user base has flipped from developers to agents. The company is betting the entire database market shifts to non-technical builders. The evidence…
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.