Michael Manapat

Voice is a super interesting modality right now - maybe the first modality we're seeing move to open source models across a number of scale ups / enterprises. Reliability concerns, high costs, and open source model performance are pushing engineers to do their own fine tuning vs. relying on third-party vendors of proprietary models. Many of these orgs have already been collecting their own first-party data and now with third-party vendors like Extrian, David AI, etc they can train really high quality models. RL has been insanely hyped, but it's been unclear how long it will take scale ups and enterprises to actually lean in. Voice AI might be hitting that inflection point faster than expected.

45

7 Comments

Thrilled to announce that Together Fund is investing in Sentra, alongside a16z speedrun! You track results in Jira. Decisions in Notion. Conversations in Slack. But the reasoning, the debates, trade-offs, and context behind why you chose A over B, disappears into what we call "Dark Matter." A decision made in March looks insane by July because no one remembers the constraints that made it smart. I lived this firsthand at Twitter scaling from 800 to 8,000 employees, and at Google while launching AI Overviews to billions at planet scale. The problem isn't process. Process is compensation for something deeper: organizational amnesia. An organization’s "Systems of Record" doesn’t solve this, they encode it. They store what happened, never why. That's why we are investing in Sentra. Sentra is the always-on collective memory that eliminates organizational amnesia by maintaining accurate context for all members and agents, functioning as an operational nervous system. It connects to every channel where work happens, meetings, Slack, email, code commits, docs, calendars, and treats them not as artifacts to search, but as living signals to synthesize. The fleeting and the permanent, unified into a memory that understands. The founding team is built for this: - Jae Gwan Park (CEO): Product-first founder, memory systems research at UofT and MIT - Ashwin Gopinath (CSO): Former MIT professor, created "Reflexion" (NeurIPS 2023), agents that learn from mistakes, 2x founder - Andrey Starenky (CTO): Early Vapi engineer, ex-IBM, built to process enterprise-scale data firehose Together is an operator-led fund. We invest in problems we've lived. This is one of them. Many congrats Jae, Ashwin and Andrey, we are so excited to partner with you! Read the full thesis: https://lnkd.in/gixj9cE4 Book a demo: https://www.sentra.app/ #OrganizationalMemory #AI #Sentra #TogetherFund #a16z #ContextGraphs

71

3 Comments

Don't Build a Better Wheat Farm" - Why Defensibility Stakes Are Higher in Deep Tech Just published a new piece on my "Ignore the Confusion" blog, building on thoughtful insights from Eric Ver Ploeg at Tunitas Ventures about startup defensibility. Eric's core thesis: Too many startups pitch like wheat farmers - "huge TAM, slow incumbents, growing market, domain expertise" - but fail to think through long-term defensibility until it's too late. From a deep tech perspective, the stakes are even higher: ** Unlike software, deep tech founders must commit to defensibility strategies from day one - their funding depends on it ** Patent vs. trade secret decisions are often difficult to reverse and shape your entire competitive strategy ** Even "picks and shovels" providers (the tools that make industries more efficient) become commodities without proper moats The key insight that resonates: Defensibility can't be retrofitted. Whether you're building software or deep tech, your moat must be architected into the business model from the start. Thanks to Eric Ver Ploeg for sharing these insights on startup strategy and letting me build on his framework from a deep tech lens. Read the full post: https://lnkd.in/dEj_iF-Q #DeepTech #StartupStrategy #Defensibility #VentureCapital #Innovation

21

2 Comments

⚠️ Founders - consider the below reasons to not use Forward Deployed Engineers (FDEs) to acquire your *first* customers. This signals (1) lack of PMF; (2) miscalculation b/w development and sales timeframes; and (3) mischaracterization of Palantir Technologies timing when they deployed their FDE model. 💡 At the early-stage, it's crucial to demonstrate ability to repeatedly acquire customers with limited resources - capital, team, & time - that supports the narrative of 'more funding will amplify my traction.' Bespoke solutions for one company demonstrates zero repeatability. These custom solutions will not carry over to other customers within the same cohort. 💡 AI accelerates engineering but sales, system integration, and stakeholder buy-ins are perpetually slow. This imbalance results in concentrating all your engineering resources into one company, ignoring other opportunities, and still not going live on an accelerated timeline. 💡 Palantir didn't start using FDEs until year 3 when they got their first *gov't* customer, not their first customer. Gotham was already built and had strong PMF. Gotham allowed Palantir to take GTM risk by using FDEs b/c if it didn't work, Gotham was humming in the background. TLDR: At the early-stage, repeatable customer acquisition is the holy grail. Don't let AI deceive you that it can accelerate human behavior like it has with development cycles. It C.A.N.N.O.T.

33

1 Comment

While there has never been a more exciting time to be a founder building dev tooling or next-gen infra, it has also never been less investable at seed/pre-seed. I'm either really missing something or a lot of my peers are lost. As someone who has not just written, but also SHIPPED, about 75k lines of code in the past 6 months I can tell you that the evolution of how to build products has changed as much in the past year as it did in the entirety of 2007-2017. The complete rise and fail of frameworks, platforms, methodologies, etc... paved over and forgotten... that is of course except for the 1 company that gets a 1000x return from a wildly overvalued hyper-scaler or drunken growth stage investor obsessed with compounding at scale. Imagine a world where any seed investor in trends like Openstack, Hadoop, PaaS, etc all took a full loss on their investment. That's what we're looking at right now. I personally know of over a dozen well-funded seed-stage companies building in these spaces, with years of runway, scrambling to get acquired for a return of capital + several million personally while they're still relevant. If you're not seeing this unfold in front of you, you either aren't paying attention or you're satisfied playing the lottery instead of investing.

75

11 Comments

CRV Security: Request for Startups I never know if this actually works for our friends over at YC but figured we'd try. Here's what we want to fund in 2026! 1. Golden Artifacts: Think Chainguard but more broad. Artifact attestation exists for open source. Almost nothing exists for internal software — especially the vibe-coded tooling now running in production. We want the company building cryptographic proof of secure software delivered from secure artifacts: who built it, how, and whether it was reviewed. If more things are being yeeted into the world via Claude Code (myself included), this feels like an issue. 2. MCP & Agentic Security: Agents are getting real credentials and taking real actions. The security posture of most orgs around this is basically zero. That changes fast. You'd never give an employee hardcoded API keys or write access to your email without supervision/trust. Why give it to agents? 3. AI Governance: Boards are asking CISOs to account for AI risk. CISOs have no good answer other than "Palo has a module" 4. Next-Gen Endpoint: CrowdStrike was built for a world of static binaries and human operators. AI workloads, cloud-native infra, and AI-assisted attackers need a new architecture. The category is ready to be reinvented. 5. Networking in the AI Era: Zero trust was designed for humans. What does network security look like when the entity requesting access is an agent? Nobody's really solved this. 6. Email Security + Next-Gen Phishing: LLMs have made spear phishing infinitely scalable. I've never truly understood why Abnormal and KnowBe4 aren't one company. Maybe this time it's different. 7. Frontier Security Lab: We'd back a credible, well-staffed lab focused entirely on red-teaming models and setting the evidentiary standard the industry needs as LLM built apps become the norm. 8. Dependency Security: That Actually Remediates Malicious and vulnerable dependencies are a top attack vector. The tooling is mostly noise — scanners that don't close the loop. The winner here ships fixes, not just alerts. 9. Critical Infrastructure Cyber: Data centers, satellites, power grids, undersea cables. The physical backbone of the internet is increasingly exposed and wildly under-defended. We have data centers in space, for God's sake. Surely we need better cyber for critical infrastructure? 10. PAM for the Modern Era Legacy: PAM was built for static roles, human users, on-prem directories. Cyberark was founded in 1999.....Agents, ephemeral workloads, and cloud-native infra have broken all of those assumptions. Is anyone rebuilding this from scratch? If you're building in any of these areas — or something we haven't thought of — reach out. james@crv.com

450

49 Comments

I’m excited to share a new benchmark, MIPfeas, which shifts the focus in Mixed-Integer Programming from "final optimality" to "early feasibility." Using the Primal Integral metric, we evaluated how solvers like HiGHS, SCIP, and NVIDIA cuOpt deliver high-quality feasible solutions within a short time window. While direct comparison with commercial MIP codes remains difficult, we have grouped the results of three major commercial solvers—COPT, CPLEX, and Xpress—into three synthetic baselines: the Virtual Best, Mean, and Worst Commercial Solvers in this benchmark. A huge thank you to Hans Mittelmann, the NVIDIA team (Burcin Bozkaya, Akif Çördük, and Chris Maes), and ZIB Zuse Institute Berlin for the technical collaboration. Special thanks also to Timo Berthold, Gerald Gamrath, and Ferenc Katai for their expert insights. Check out the full results here: https://lnkd.in/dSfNc58v #Optimization #MIP #GAMS

83

11 Comments

"Build the event you wish existed" That's what we at Monadical did last week at #NYTW. We wanted an AI Engineers discussion for Engineers. There's always a lot of events out there for VCs to network, or for startups to learn about G2M, but very little on lessons learned from actual engineers in the field. So that's the event we hosted. Big thank yous to our awesome panel, Roy Pereira, Ben Cohen and Corey J. Gallon. Here's the key takeaways and the AI tools we're using. 🚀 All three panelists independently called AI Agents the most transformative LLM application they’ve used. They specifically called out Claude 3.5 Sonnet for its accuracy and reliability. 🪨 We dug into how LLMs are “jagged”, not general. They can be shockingly good at some tasks and completely fail at others. Everyone agreed: good evaluations are critical (and hard.) 🧪 Corey noted how public benchmarks and reality are two different things. Most public evals are saturated or gamed. ♊ Ben emphasized that AI projects are actually two projects: building the tool and building the evaluation process. 🧱 We explored how falling dev costs may impact startup defensibility and labor demand. Roy shared that founders are already shifting strategies in response. ⚒️ In a world of daily AI launches, the panel discussed how they decide what’s worth attention, and what’s just noise. They called out tools like Goose, Aider, Claude Code, and Monadical’s own Cubbi, which helps run agentic workflows safely in dev environments. (links in the comments). CTA: What would you want to hear in an AI Applied Engineering talk you attended?

33

5 Comments

I came across this today: AI in Procure-to-Pay: Structural constraints holding back P2P platforms (link in comments). “Structural constraints?” At Silkline, we’ve been thinking about these problems since Day 0 - over two years ago. Not as academic critiques, but as real blockers to building procurement software people actually trust and use. Every step of our journey, the team has made explicit product and engineering decisions to answer one question: "How should this be built today, given what’s possible in 2026 - not how it’s been done for the last 20 years?" Given our growth last year (and an even stronger trajectory this year), it’s time to start showing the how. Next week, I’m challenging myself to do 5 posts in 5 days, breaking down how we’ve addressed each of these so-called “structural constraints” in practice: 1. Document-centric data models: Fragmented documents → fragmented context → weak AI reasoning. When data is trapped in PDFs and forms, AI can’t see patterns, history, or risk. 2. Weak state management: It’s not enough to know where you are. You need to know how you got here. Most systems lose the story. 3. Brittle integration architectures: The real problem isn’t “big data.” It’s lots of small, messy, constantly changing data. 4. Policy encoded as static rules: Real procurement is full of exceptions. Static rules break the moment reality shows up. 5. Explainability and trust: If you don’t know why, when, or how something happened, you won’t let AI touch real decisions. These aren’t “constraints” to work around. They’re design choices, and we’ve been intentional about them since day 1. More next week.

19

1 Comment

I’m thrilled to share that White Star Capital is backing AMI - Advanced Machine Intelligence in their historic $1.03bn seed round 🚀 - Led by the legendary Yann LeCun and Alex LeBrun. AMI isn't building another LLM, they're building World Models. Why this matters: *Beyond Text: Grounded in JEPA architecture to solve physical-world problems. *Global Powerhouse: A dream team from Meta FAIR, OpenAI, and DeepMind. *Sovereign Tech: A credible European-led alternative to US Big Tech. Excited to be part of this journey along with the rest of the WSC team Eric Martineau-Fortin, Matthieu Lattes, Bérénice Moustial and Victoria Pozzi Rocco Belforti. 🌍✨ https://lnkd.in/eiCKZKSQ #VentureCapital #AI

86

2 Comments

Just released my conversation with Troy Astorino, CTO of PicnicHealth, where he reveals how they built an 8B parameter model that outperforms much larger frontier models by focusing on domain expertise and building an un-breachable data moat. Troy's counterintuitive insight completely reframed how I think about AI: Most engineering leaders ask "How fast can we ship this?" when they see new models. Troy asks "Where will this break?" That mindset helped PicnicHealth engage with 7 out of the 10 largest pharma companies and collect 350 million clinician annotations, creating a data advantage that no general-purpose model can replicate. Listen here: 🎧 Substack: https://lnkd.in/gFmeKD9g 🎧 Apple Podcasts: https://lnkd.in/gAjuTvfw 🎧 Spotify: https://lnkd.in/gXCWrrdf

10