YC Root AccessAleph: The AI Platform for Modern Finance
CHAPTERS
- 0:05 – 0:30
Aleph in one sentence: an AI-native FP&A platform built around spreadsheets
Aaron welcomes Albert (CEO) and Santi (CTO) and frames the conversation around Aleph’s $29M Series B. The founders explain Aleph’s core product idea: centralize finance data and analysis in one place while still letting teams operate from spreadsheets.
- •$29M Series B led by Khosla introduced as the headline
- •Aleph positions as an AI-native FP&A (financial planning & analysis) platform
- •Core promise: centralize finance decision data + analysis tools
- •Spreadsheets are treated as a first-class interface, not a legacy artifact
- 0:30 – 1:37
Meeting finance teams where they already work: inside the spreadsheet
Albert explains the product philosophy that resonates most with finance teams: don’t force a workflow change. Aleph embeds into spreadsheet workflows via an add-in, so analysts can pull from a unified data layer while keeping familiar modeling habits.
- •Finance teams “live and breathe” spreadsheets
- •Aleph includes a spreadsheet add-in as a primary user surface
- •Goal is better analysis without forcing a full workflow migration
- •Differentiation comes from respecting existing finance behavior
- 1:37 – 2:52
Why customers pick Aleph: faster time-to-value than legacy FP&A rollouts
The team contrasts Aleph with traditional FP&A implementations that take months before delivering value. Aleph emphasizes near-immediate value (hours/days) and full implementation in 1–2 weeks, which reduces adoption friction and risk.
- •Legacy FP&A tools commonly take 3–6 months to implement
- •Aleph targets first value within a day (sometimes hours)
- •Full implementation typically in 1–2 weeks
- •“Time to value” is positioned as a core product pillar
- 2:52 – 4:47
Founder origins: lived finance pain + engineering taste for “no-code” primitives
Albert’s background spans finance roles and working closely with CFOs, culminating in building finance workflows at an early-stage startup. Santi brings deep software engineering and research experience, with an appreciation for spreadsheets as the most powerful no-code tool—making their collaboration a natural fit.
- •Albert: finance + consulting experience; built finance systems hands-on
- •Strong spreadsheet fluency shaped the product direction
- •Santi: Google + CS PhD; research in better ways to build software
- •Shared belief: spreadsheets are an exceptional “no-code” environment
- 4:47 – 6:33
Joining forces at YC: early build scrappiness and the COVID remote batch
Santi joins full-time around the YC acceptance, and the founders recall early technical scrappiness (including rewriting critical auth code later). They describe the unique dynamics of a remote COVID-era batch while still building tight relationships with other founders.
- •Santi joins full-time right as Aleph gets into YC
- •Early MVP engineering was scrappy and later refactored
- •Remote YC batch still enabled collaboration and founder relationships
- •Ongoing connections with batchmates continued after the program
- 6:33 – 9:11
From research to revenue: landing the first customer (mid-YC)
Aleph’s first customer closed during the YC interview week, highlighting how early the company was. Albert credits extensive customer discovery—150–200 calls—creating relationships that later converted into customers, including Konfio returning a year+ later asking if the solution existed.
- •First customer signed during YC interview week timing
- •Company was extremely early; product still forming during YC start
- •150–200 discovery calls seeded early demand and trust
- •Konfio became an early customer and remains one years later
- 9:11 – 12:07
Staying on-track without pivots: empathy, discovery, and durable primitives
Aaron probes how Aleph avoided major pivots despite years of evolution. Albert attributes this to being “their own customer,” deep discovery, and a vision that stayed consistent—plus an architecture built from reusable primitives that didn’t require constant rewrites.
- •“Be your own customer” created strong problem empathy
- •Discovery calls broadened understanding beyond the founders’ needs
- •Pre-seed deck still matches today’s roadmap surprisingly well
- •Core product building blocks from 2021 remain in use
- 12:07 – 13:37
The hardest part: prioritization, delivery pressure, and handling financial-stakes data
The founders describe the strain of prioritizing while building a horizontal platform with many possible workflows. Early on, they worked late nights to hit demos and deliverables because customers relied on Aleph numbers for executive reporting—raising the stakes of accuracy and reliability.
- •Prioritization challenge: often had to do “A and B,” not choose
- •Horizontal product meant many edge cases and expectations to manage
- •High stakes: customers rely on Aleph outputs for CEO-facing reports
- •Early execution involved late nights across engineering and CS
- 13:37 – 15:21
Earning trust early: SOC 2 as a tiny team + ‘we won’t let you fail’ support
Albert explains that security and trust were foundational from day one, including getting SOC 2-certified when the company was only a few people. They also leaned on intense customer success support—manual reviews and behind-the-scenes work—to ensure customers could report accurately on time.
- •SOC 2 certification pursued extremely early despite limited cash
- •Trust built through both security posture and customer commitment
- •Customer success sometimes manually validated reports pre-send
- •Classic YC approach: “do things that don’t scale” to win early
- 15:21 – 16:17
Growth inflection points: team quality and key hires as step-changes
Asked about inflection points, Albert points to people joining as the biggest accelerant—starting with Santi going full-time. As the company grew, impactful hires at many levels expanded what Aleph could build and how fast it could execute.
- •Biggest inflection: Santi joining full-time
- •Subsequent inflections often correlated with standout hires
- •Impact isn’t limited to executives; smaller-scope roles can compound
- •Hiring is framed as a primary lever for trajectory
- 16:17 – 18:57
What’s next: real-time finance workflows and pragmatic, accuracy-first AI
With core integrations/permissions groundwork in place, Aleph wants to build more “interesting” AI-driven capabilities—without forcing AI into every workflow. Santi emphasizes the technical challenge: in finance, accuracy and security are non-negotiable, so AI must be engineered carefully at the application layer.
- •Series B enables building beyond foundational ‘unsexy’ platform work
- •AI viewed as a means to an end, not a gimmick
- •Finance requires high accuracy; AI must be validated and constrained
- •Big leverage exists in workflow design + intelligence at the app layer
- 18:57 – 20:32
Who thrives at Aleph: low ego, customer empathy, and high-collaboration execution
Albert and Santi describe cultural attributes they screen for as they hire post-Series B. They value low ego, willingness to do unglamorous work for impact, strong customer empathy, and a collaborative style that makes teams faster and more resilient.
- •Low ego and impact-over-credit are “non-negotiables”
- •No task is beneath you—optimize for shortest path to customer value
- •Empathy for finance users and their day-to-day constraints
- •Collaborative culture; hard work paired with humor and camaraderie
- 20:32 – 24:11
Founder evolution + YC lessons: reinventing roles, persistence, and ignoring noise
The founders reflect on how their jobs changed as the company scaled—from individual contribution to direction-setting and management layers. They close with advice they’d give their YC selves: keep going through setbacks, and don’t get distracted by competitors—focus on customers and compounding execution.
- •Shift from individual output to leverage through teams and alignment
- •CTO role evolves repeatedly: coder → manager → manager-of-managers
- •YC lesson: persistence—many startups fail by giving up
- •YC lesson: don’t over-index on competitors; focus on customer value
