Town Raises $108 Million for Workplace AI Assistants That Stay Up to Date
Town announced a $108 million Series B on October 19, 2026, reaching unicorn valuation four months after its public launch. A unicorn is a private company valued at $1 billion or more. The San Francisco startup builds AI assistants for business users TechCrunch.
The round was co-led by Forerunner Ventures and Menlo Ventures. Andreessen Horowitz, Serena Ventures and First Round Capital participated.
Total funding to date is at least $160 million. That follows a $55 million Series A announced in June, with two rounds about four months apart.
Town was founded by former Plaid CTO Jean-Denis Greze. The company builds assistants designed for specific roles inside businesses, rather than a general-purpose chat tool.
The core product is called a Townie. Each Townie connects to email, calendars and other work systems. It keeps persistent access to work context with permissions, meaning it sees only what it is allowed to see, rather than starting fresh with each prompt as a stateless chatbot does.
Alongside the financing, Town announced a shared workflow that updates employees' Townies with new business information automatically. One update spreads across many assistants, so each user does not need to re-upload files or rewrite instructions.
On commercial traction, Town said it reached millions of dollars in annual recurring revenue, or yearly subscription income, in a matter of weeks. It has not disclosed customer counts, contract structure, or net retention, and it has not given the exact valuation behind the unicorn label.
The broader context here is the shorter cycle from pilot to paid deployment in enterprise AI. Moving from launch to unicorn in four months is rare, even by recent AI standards. Capital is gathering around teams that show paid use quickly, and revenue in weeks has become shorthand for that signal.
Looking at what this means for buyers and builders, the technical challenge is familiar. Setup is easy. Keeping information current is hard. Assistants fall out of date when pricing changes, ownership shifts, policies update, or calendars move on. A shared update layer addresses that staleness directly, if access controls, audit trails, and revocation hold up under real IT review. For buyers who understand the technology, those controls matter more than demo fluency.
In my view, the speed brings operational risk worth flagging. Fast revenue growth tests onboarding, support, permissions work, and incident response at the same time. Access across email and calendar widens the impact of a misconfigured share or a retention policy that keeps too much. The companies that get through this phase tend to invest early in enterprise basics while growth still looks easy.
Looking ahead, what this enables if the model holds is less time hunting for current internal truth. New hires inherit up-to-date context. Teams stop keeping parallel versions of the same answer in docs, threads, and chat logs. It is a more modest promise than autonomous work, but it is the kind of utility that tends to stick.
