Town raised a $55M Series A on June 3, 2026, led by Andreessen Horowitz, with participation from Forerunner Ventures.

Before the Series A, Town raised an $18M seed round led by Todd Jackson at First Round Capital, with Alt Capital and Conviction also participating. Angel investors include Adam D'Angelo, Soleio Cuervo, and Immad Akhund.

Total funding raised across both rounds is $73M.

Town is an AI assistant for knowledge workers that connects to tools they already use, including Gmail, Google Calendar, Drive, Slack, Notion, HubSpot, Salesforce, and 50+ others, instead of requiring work to move into a separate system.

Onboarding starts with connecting a Google account, which imports Gmail, Calendar, and Drive in one step. Town reads recent email and calendar data to build a profile of the user's role, writing style, frequent collaborators, and priorities. That profile serves as a persistent memory layer for later interactions.

The interface is conversational but connected to live accounts and tools. In a single thread, a user can ask Town to pull the latest emails from a contact, draft a reply in their voice, check the next day's calendar, reschedule a meeting, or create a document summarizing the week's notes, and Town can execute those actions directly rather than only recommending them.

A core product element is Routines, repeatable agentic workflows that run in the background based on a trigger such as a new email, a meeting start, or a Sunday evening schedule. The user writes instructions in plain English, chooses which tools the routine can access, and sets an autonomy mode, fully autonomous, approval-required, or read-only. Town includes a library of stock routines out of the box, including auto-inbox triage, pre-meeting briefings, schedule optimization, invoice and expense logging, and contact research dossiers, which reduces setup work for new users.

The assistant is available across web, a dedicated @town.com email address, Slack @mentions, WhatsApp, iOS voice, and a Mac desktop app, with shared memory, thread history, and preferences across each surface. Approvals for state-changing actions are managed centrally, with full run history and version rollback, giving users a graduated level of autonomy instead of a binary on/off setting.

Town sells B2C and B2B subscription SaaS with a credit-based consumption layer. Individual plans provide a monthly credit allotment; heavier usage, more routines running, more research lookups, more tool executions, burns credits faster and pushes users toward higher tiers or pay-as-you-go overages. Higher tiers come with lower per-credit overage rates, creating an incentive to upgrade before hitting higher overage charges.

Its go-to-market motion is bottoms-up. A single user connects Google, gets immediate value from auto-inbox or morning briefings, and builds daily dependence through routines and multi-channel access. Once routines are wired into a user's inbox, calendar, Slack, and docs, switching costs rise because the assistant has learned the user's voice, contacts, and workflow patterns over time.

Team and Business plans add pooled credits, shared workspaces, shared routines, and org-level analytics. The Business tier shifts away from per-seat pricing toward a large pooled credit bucket, reducing rollout friction in organizations where many employees want occasional assistant access but heavy usage is concentrated among a few operators. That packaging makes Town closer to organizational assistant infrastructure than a conventional seat-based app.

The cost structure differs from standard SaaS because each unit of delegated work may trigger LLM calls, web search, retrieval, tool execution, and message delivery. The credit model partially passes those variable costs through to users, which may make the business more resilient than fixed-price unlimited plans as autonomous routine usage scales. Town is asset-light on systems of record because it integrates with user-owned SaaS platforms rather than rebuilding email, calendar, CRM, or document suites from scratch.

Town operates in a converging market defined by tension between assistant startups with tighter workflows and bundled incumbents that can ship good-enough AI inside software buyers already pay for.

Google and Microsoft are Town's clearest structural competitors because they have native distribution, first-party data access, and enterprise procurement relationships that Town cannot replicate.

Google's Gemini is embedded across Gmail, Calendar, Docs, and Drive, and its Gemini Spark agent, announced in May 2026, offers 24/7 briefings, inbox summaries, and approval-before-action flows that overlap directly with Town's core routines. For users whose work runs on Google Workspace, the cost of adopting a separate assistant layer rises as Gemini becomes more capable.

Microsoft 365 Copilot creates the same pressure for Outlook and Teams-centric organizations, with Graph-level access to organizational data and a deeper enterprise compliance posture than Town has today. Slack's Agentforce integration adds a third vector: for teams where Slack is the operating system of work, a channel-native agent can outperform an external assistant on collaboration context without requiring a new app.

Lindy is the closest startup analog to Town in product scope, spanning inbox, meetings, calendar, follow-ups, research, and texting across iMessage, SMS, Slack, and email, with plans running from roughly $50 to $200 per month. The overlap is substantial enough that many buyers will evaluate the two as direct substitutes, with Lindy leaning more aggressively autonomous and Town differentiated by built-in document workflows, routine sharing, and a persistent assistant persona with a dedicated email identity.

Fyxer targets one of Town's highest-value use cases, email management, with less required behavior change, working inside Gmail and Outlook rather than requiring a new workspace. Shortwave competes from the inbox outward, adding AI to a mature email-client UX and expanding into broader agentic automation through its Tasklet product, which Sacra estimates hit roughly $10M in ARR in May 2026. Both create the risk that users choose a better version of an existing tool over onboarding a new cross-app assistant.

Reclaim, with over 600,000 users across 70,000 companies, owns the calendar-intelligence niche with focused scheduling logic that Town's broader assistant framing may not beat on that specific job-to-be-done. Superhuman competes for premium professionals where polished UX and speed matter more than deep autonomy.

ChatGPT is a persistent competitor as OpenAI adds connectors for Gmail, Google Calendar, Drive, Outlook, Teams, HubSpot, and more, plus recurring Tasks and agent mode. Town is no longer competing only with horizontal chatbots, but with a general assistant that is gaining the same data access and automation capabilities at massive scale. Notion AI, with broader workspace AI spanning enterprise search, meeting notes, research, and agents, represents similar bundling pressure from the productivity-platform direction.

Town's expansion thesis is to move from a personal assistant for individual knowledge workers into shared workflow infrastructure for teams and organizations, while extending usage across more roles, tools, and geographies.

Town already has the primitives for a broader automation platform, including triggers, tool permissions, run history, approval modes, shared team spaces, and custom MCP server integrations. The product expansion is to move up the stack from an on-demand assistant into always-on agent operations, where Town handles recurring workflows, approval policies, and cross-app orchestration rather than only one-off requests.

MCP server support matters because it lets organizations expose proprietary or industry-specific internal tools to Town without waiting for native integrations. That changes Town's ceiling from a fixed app catalog to a workflow orchestration layer over any business system, expanding the addressable surface area beyond the 50+ native integrations it ships today.

Town is approaching 10,000 users, with the majority using it primarily for work. The clearest near-term expansion is from prosumers into teams and SMBs, where shared routines, pooled credits, and Team Squares can convert one user's personal automations into standardized workflows for an entire function.

The early user base already includes non-traditional knowledge workers, including field service businesses and tradespeople managing high volumes of mixed personal and work email. That suggests Town can extend into workflow-dense segments where generic chatbots underperform because the main constraint is coordination across inbox, schedule, contacts, files, and operational tools, broadening the addressable market beyond the typical enterprise SaaS buyer.

Town's current productivity footprint is centered on Google Workspace, with onboarding starting from a Google account connection. First-class support for Outlook, Microsoft Calendar, Teams, OneDrive, and SharePoint would open access to a large share of organizations that standardize on M365 and currently use Microsoft 365 Copilot as the default option.

Geographically, Town's multi-channel design, including WhatsApp, email, iOS voice, Slack, and Telegram, fits English-speaking markets outside the US where those surfaces are common and SMB services workflows are prevalent. Australia, the UK, and Canada are natural early international expansion targets before deeper localization is required, and the product's conversational delegation model should require fewer changes to travel internationally than a desktop-only or enterprise-only copilot.

Platform dependency: Town's product sits on top of Google, Slack, and Microsoft ecosystems that are shipping native AI assistants with first-party data access, and any tightening of API permissions, rate limits, or partner policies by those platforms could reduce Town's product capability while strengthening the case for staying inside the incumbent's native tooling.

Trust ceiling: Town's value proposition compounds as users grant more autonomy to routines touching email, calendar, docs, messaging, and finance systems, but the cost of even small errors in those workflows may keep many users in approval-required mode, capping the product's ability to become an autonomous work layer rather than a supervised drafting tool.

Bundling compression: As Microsoft 365 Copilot, Google Gemini, Notion AI, and ChatGPT with connectors become more capable at inbox triage, meeting prep, scheduling, and cross-app follow-through, willingness to pay for a standalone assistant layer may compress, particularly for users already paying for one of those suites and facing a meaningful behavior-change cost to adopt a separate product.