ProgrammableMarketing/town.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 8
  • Big bets · 3
  • Wildcards · 3
Generated Oct 26, 2026
  1. Programmable
  2. Playbooks
  3. Town
Town logo

growth playbook · Oct 26, 2026

town.com (opens in a new tab)

Town growth playbook

Diagnosis

Town reached a $1 billion valuation four months after launch and has just raised $108 million to take Townies from individuals to whole teams. Its hiring says how: a growth engineer for invites, free-to-paid, team formation and SSO; a community lead to spread user-built routines; and its first sales, marketing and success hires for inbound it cannot keep up with.

The gaps sit in the team step: referral rewards stop at personal plans, only admins can invite by default, there are no customer stories or comparison pages, and the homepage fails Google's speed checks for real visitors.

This playbook starts with team invites, pricing clarity, speed, proof and comparison pages, then builds a community routine gallery, domain-based team discovery, an enterprise page and usage scoring for the new sales team.

Growth Score

8/10

Biggest Opportunity

Turn every active user into a team builder: reward the invites that form teams, surface colleagues on the same domain, and let user-built routines spread with their builders' names on them.

Biggest Risk

Lindy, Fyxer, Superhuman and the large suites compete for the same work assistant budget, and fast growth on credits can disappoint users who hit limits or never get a second routine running.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Make invites pay for teams, not only for personal upgrades

    Pull the share of teams that never reach 3 active members, and how many of their invites came from admins.

    High impact First result in 1 month
  2. 2

    Fix the pricing table and show what a team of three really costs

    Decide which plan includes org analytics and fix the FAQ or the table today.

    High impact First result in 2 weeks
  3. 3

    Bring the homepage under Google's speed limits for real visitors

    List every font file and weight the homepage loads.

    Medium impact First result in 1 month

02

Your idea portfolio

20 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 6 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 5Big bets · 9Fill-ins · 2Reconsider · 4
Effort →

Showing 20 of 20 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Town's Series B is about moving "from individuals to whole teams", and the new growth engineer is asked to get "individuals onto teams" and make sure "every team lands with at least 3 active members". But the invite program stops exactly there: referral credits are paid only when a friend buys a personal plan ("Team and enterprise plans don't qualify"), and on a new team only admins and owners can invite members by default. The person most likely to bring in a teammate, an active member, is neither rewarded nor allowed to.

    High impactLow effort First result in 1 month Software Engineer

    First action

    Pull the share of teams that never reach 3 active members, and how many of their invites came from admins.

    How to measure it

    Teams with 3+ active members in 14 days

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Measure the gap

      Teams under 3 active members; invites sent by members vs admins.

      Software Engineer, Growth 2 days

    2. 2

      Change the default

      Members can invite; admins can require approval.

      Software Engineer, Growth 3 days

    3. 3

      Design the team reward

      Credits to the pool and the inviter on an active teammate or a paid team.

      Head of Business 2 days

    4. 4

      Add the progress bar

      "2 of 3 active" with one-click invite in the team menu.

      AI Product Engineer 1 week

    5. 5

      Update the docs

      Referral and Teams pages show both rewards.

      Product Support 1 day

    6. 6

      A/B test

      New teams split between old and new defaults.

      Software Engineer, Growth 4 weeks

    First result
    1 month
    Cost
    Engineering time and reward credits
    Owner
    Software Engineer, Growth

    Smallest test

    Turn on member invites for 10% of new teams and compare team size after 14 days.

    Why it works

    Change the defaults so any member can invite teammates (admins keep approval if they want it), and add a team reward: when an invite leads to a team member who stays active for two weeks, or a team that moves to a paid plan, the team pool and the inviter both get credits. Show a "your team: 2 of 3 active" bar in the team menu with a one-click invite, and keep the personal 2,000-credit reward as it is.

    Personal referrals reward a $15-$49 upgrade; a team of three on Team is $177 a month or more and is the step the company is now built around. Rewarding the invite that forms the team puts the incentive where the revenue is.

    Ready to use

    ChecklistTeam invite change list

    [ ] Default access rule: Invite members -> All members (approval optional)
    [ ] Team reward: credits to pool + inviter after 14 active days
    [ ] "2 of 3 active" bar in the team menu
    [ ] Invite prompt after a routine is shared in a thread
    [ ] Referral docs updated (personal + team)
    [ ] Dashboard: invites per member, teams reaching 3 active

    Risks and how to handle them

    • Admins want control over who joins

      Keep an approval setting and same-domain-only invites by default.

    • Reward gaming with inactive seats

      Pay only after two weeks of real use.

    Evidence

    • Your websiteReferral docs ("Invite Friends & Earn Credits", updated October 21, 2026): a friend who signs up through your link gets "a 14-day Pro trial instead of the standard 7 days", and you earn "2,000 Town Credits" when they start paying. But "Team and enterprise plans don't qualify. Only paid personal plans earn the reward." Rewards go to your personal balance "even if a team covers your Town plan".Source
    • Your websiteTeams docs: new teams start on Team Free; members keep their personal plans and "a free team grants no credits of its own". Default access rules: "Invite members -> Admins & owners" and "Create installable routines -> Admins & owners". Fully offboarding a departed teammate "isn't self-serve today. Email support".Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
    • Your websiteSeries B release (October 19, 2026): $108 million co-led by Forerunner Ventures and Menlo Ventures at a $1 billion valuation, to take Town "from individuals to whole teams". Townies "ask each other questions" and "hand off work", and "can also work directly with customers, partners, and candidates outside the company over email and text". Example: when BizOps updates competitor comparisons once, "every rep's Townie preps calls with the new competitive analysis built in".Source
  • 02

    The pricing FAQ says team plans include "org-wide analytics", but the comparison table shows a dash for "Org usage analytics" in every column, and Org-wide analytics is listed as an Enterprise feature. Team is $59 a seat against Pro at $49, so a buyer comparing the two has to work out why the team seat is worth more.

    High impactLow effort First result in 2 weeks Software Engineer

    First action

    Decide which plan includes org analytics and fix the FAQ or the table today.

    How to measure it

    Team plan purchases from pricing

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      Agree the facts

      Which plan has org analytics.

      Head of Business 1 day

    2. 2

      Fix the copy

      Table and FAQ match.

      Software Engineer, Growth 1 hour

    3. 3

      Write the panel

      Three people: Pro vs Team.

      Head of Business 1 day

    4. 4

      Build it

      On the Businesses and Teams tab.

      Software Engineer, Growth 2 days

    5. 5

      Update the recommender

      Ask how many people will use Town.

      Software Engineer, Growth 2 days

    6. 6

      Measure

      Team purchases from the page.

      Software Engineer, Growth 4 weeks

    First result
    2 weeks
    Cost
    $0
    Owner
    Software Engineer, Growth

    Smallest test

    Fix the analytics row today.

    Why it works

    Make the table and FAQ agree on which plan has what. Add a short "Pro for three people vs Team for three" panel: price, pooled credits (18,000 vs 15,000), shared routines, team integrations and one bill. Feed the 30-second recommender the number of people who will use Town.

    Clear, consistent pricing pages convert better, and the team panel answers the one question between a Pro user and a team plan.

    Risks and how to handle them

    • Panel makes Pro look cheaper

      Show the shared features, not only price.

    Evidence

    • Your websitePricing page: Free $0 (30 chat messages a month, 7-day Pro trial), Starter $15 a month, Pro $49, Power $99 and Power Plus $199 per user (annual); Team $59 per seat a month annually ($71 monthly) with 6,000 pooled credits per seat, Team Plus $149 ($179) with 18,000; Enterprise custom with "Org-wide usage analytics". The FAQ says team plans add "org-wide analytics", but the comparison table shows a dash for "Org usage analytics" in every column, Team included. Every account's overage cap "defaults to $0". The page offers "Get a recommendation in 30 seconds".Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 03

    Real Chrome visitors fail Core Web Vitals on town.com: the main content takes 4.6 seconds and taps wait 296 ms. The homepage is 4.5 MB, with 1.5 MB of fonts, 1.8 MB of JavaScript and six ad and analytics tags. For a product that promises to be "fast", the first impression is slow on phones.

    Medium impactMedium effort First result in 1 month Software Engineer

    First action

    List every font file and weight the homepage loads.

    How to measure it

    Mobile LCP for real visitors

    Now
    –
    Target
    under 2.5 s
    By
    60 days

    Steps

    1. 1

      Audit fonts

      Families, weights, sizes.

      Software Engineer, Growth 1 day

    2. 2

      Subset fonts

      Only weights in use.

      Software Engineer, Growth 2 days

    3. 3

      Fix images

      Modern formats and sizes.

      Software Engineer, Growth 2 days

    4. 4

      Defer carousels

      Load below the fold later.

      Software Engineer, Growth 2 days

    5. 5

      Delay tags

      Ad tags after interaction.

      Head of Business 1 day

    6. 6

      Verify

      PageSpeed and field data.

      Software Engineer, Growth 28 days

    First result
    1 month
    Cost
    Engineering time
    Owner
    Software Engineer, Growth

    Smallest test

    Cut font weights on the homepage and measure.

    Why it works

    Subset and self-host the fonts (one or two weights per family), serve images in modern sizes, lazy-load the integration and routine carousels, set long cache lifetimes on static files, and load ad tags after interaction. Recheck in PageSpeed and in the Chrome UX Report after 28 days.

    Faster first loads lift sign-up rates, especially from paid social, where most visits are on phones.

    Risks and how to handle them

    • Ad attribution drops

      Use server-side events for conversions.

    Evidence

    • Google PageSpeedHomepage on mobile scores 38/100 (desktop 40). Real Chrome visitors fail Core Web Vitals: largest content at 4.6 s (target 2.5 s) and interaction delay 296 ms (target 200 ms). The page downloads 4.5 MB in 142 requests, including 1.5 MB of fonts and 1.8 MB of JavaScript; 13 third parties add 1.2 MB, led by Google Tag Manager (519 KB) and Facebook, TikTok, LinkedIn, Reddit and HubSpot tags. Biggest fixes: image delivery (about 3.3 s), cache lifetimes (2.5 s), unused JavaScript (1.7 s).Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 04

    Town has no comparison pages and no blog, while Lindy pitches "an AI employee" for "the whole team", Fyxer "the AI assistant across all your work" and Superhuman "the AI productivity suite". Buyers searching those names before choosing see only the rivals' framing.

    High impactLow effort First result in 1 month Head of Business

    First action

    Pick the three rivals that come up most in sign-up surveys.

    How to measure it

    Comparison-page sign-ups

    Now
    –
    Target
    500 a month
    By
    90 days

    Steps

    1. 1

      Pick rivals

      Three most common.

      Head of Business 1 day

    2. 2

      Check facts

      Current features and prices.

      Head of Business 2 days

    3. 3

      Write pages

      Fair tables and switching help.

      Head of Business 1 week

    4. 4

      Legal review

      Claims and trademarks.

      Legal counsel 3 days

    5. 5

      Publish

      With a switching routine.

      Software Engineer, Growth 1 day

    6. 6

      Refresh

      Every quarter.

      Head of Business quarterly

    First result
    1 month
    Cost
    Writing time
    Owner
    Head of Business

    Smallest test

    Publish one comparison and track sign-ups.

    Why it works

    Write fair, dated comparison pages around Town's real difference: one Townie per person that learns its person, assistant-to-assistant handoffs, team routines and the privacy defaults. Include a switching guide and a routine to import common workflows.

    Comparison searches are high intent, and AI assistants use these pages to explain how products differ.

    Risks and how to handle them

    • Claims go out of date fast

      Date each page and review quarterly.

    Evidence

    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
    • Competitor researchRivals' own homepages: Lindy, "the AI employee that connects to all your tools, knows everything about your company, and does real work for the whole team"; Fyxer, "The AI assistant across all your work" with "Briefings, client Spaces and meeting prep"; Superhuman, "the AI productivity suite that gives you superpowers everywhere you work".Source
    • Your websiteSeries B release (October 19, 2026): $108 million co-led by Forerunner Ventures and Menlo Ventures at a $1 billion valuation, to take Town "from individuals to whole teams". Townies "ask each other questions" and "hand off work", and "can also work directly with customers, partners, and candidates outside the company over email and text". Example: when BizOps updates competitor comparisons once, "every rep's Townie preps calls with the new competitive analysis built in".Source
    • Your websiteHomepage: "Learns how you work, then gets to work." It introduces ten named Townies, each shown with an address ([email protected], [email protected], [email protected] and others), lists sample results from Gmail, Slack, HubSpot, Salesforce, QuickBooks and others, and says "Nothing you connect trains a model, by default" and "SOC2 Type 2 compliant".Source
  • 05

    Town's pricing says "steady overage is your upgrade signal", but every account's overage cap "defaults to $0", so a Pro user who runs out simply stops until they find the setting. Free and Starter users are prompted to upgrade; paid users hit a wall.

    High impactLow effort First result in 3 weeks Software Engineer

    First action

    Count paid users who hit the limit last month and what they did next.

    How to measure it

    Limit-to-upgrade conversion

    Now
    –
    Target
    +30%
    By
    60 days

    Steps

    1. 1

      Measure

      Who hits the limit and what follows.

      Software Engineer, Growth 2 days

    2. 2

      Design the card

      Cap, upgrade or team.

      AI Product Engineer 2 days

    3. 3

      Build it

      At 80% and 100%.

      Software Engineer, Growth 1 week

    4. 4

      Add routine detail

      Heaviest routine named.

      Software Engineer, Growth 2 days

    5. 5

      Email backup

      Same choices by email.

      Software Engineer, Growth 1 day

    6. 6

      Measure

      Upgrades and cap raises.

      Software Engineer, Growth 4 weeks

    First result
    3 weeks
    Cost
    Engineering time
    Owner
    Software Engineer, Growth

    Smallest test

    Email the three choices to last month's limit-hitters.

    Why it works

    When a paid user reaches 80% and 100% of credits, show one card with three choices: raise the cap (with a suggested amount), move to the next plan with the credit difference shown, or start a team with pooled credits. Use the per-routine usage table to say which routine used the most.

    A clear choice at the moment of need converts better than a setting page, and it keeps routines running.

    Risks and how to handle them

    • Users feel pushed

      Lead with the cheapest option that keeps work running.

    Evidence

    • Your websitePricing page: Free $0 (30 chat messages a month, 7-day Pro trial), Starter $15 a month, Pro $49, Power $99 and Power Plus $199 per user (annual); Team $59 per seat a month annually ($71 monthly) with 6,000 pooled credits per seat, Team Plus $149 ($179) with 18,000; Enterprise custom with "Org-wide usage analytics". The FAQ says team plans add "org-wide analytics", but the comparison table shows a dash for "Org usage analytics" in every column, Team included. Every account's overage cap "defaults to $0". The page offers "Get a recommendation in 30 seconds".Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 06

    Town says people "bring their teams and companies with them" and it already has "real enterprise usage", yet the site has no customer stories and the homepage's one testimonial is from an investor. The first sales hires will need proof.

    High impactLow effort First result in 1 month Community & Events lead

    First action

    List the ten most active teams and ask five for a call.

    How to measure it

    Story-assisted team sign-ups

    Now
    –
    Target
    100 a month
    By
    90 days

    Steps

    1. 1

      Find teams

      Most active, 3+ members.

      Community & Events lead 2 days

    2. 2

      Interview

      Routines, handoffs, hours saved.

      Community & Events lead 1 week

    3. 3

      Write stories

      Five short stories.

      Head of Business 1 week

    4. 4

      Add routine links

      Installable from each story.

      Community & Events lead 1 day

    5. 5

      Place quotes

      Homepage and role pages.

      Software Engineer, Growth 1 day

    6. 6

      Measure

      Story views to sign-ups.

      Software Engineer, Growth monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Community & Events lead

    Smallest test

    Publish one story this month.

    Why it works

    Interview five teams with three or more active members: what they hand off, which routines they run and hours saved. Publish short stories with the exact routines as installable links, and add two quotes to the homepage and the Sales and Founders pages.

    Peer proof is what turns a team trial into a company purchase, and installable routines make each story usable.

    Risks and how to handle them

    • Customers decline naming

      Offer anonymous stories by role and company size.

    Evidence

    • HiringFounding GTM Recruiter (posted July 29, 2026): "Town is a true product-led-growth company. People find Town, start using it themselves, and bring their teams and companies with them - so we already have real enterprise usage and more inbound than we can keep up with." Town has "made our first commercial hires" and will hire "revenue and sales, product marketing, growth, business operations, customer success, and partnerships", working with "the Head of Business". The recruiter should "Recruit for Town on Town".Source
    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
    • Your websiteRoutine sharing docs: "Share a routine with a link that anyone can open and install as their own"; links "show a preview on X, LinkedIn, and iMessage"; "Shared links support preview even when not signed in"; "Code-based routines can't be shared yet".Source

This quarter 8

The core plays for the next three months.

  • 07

    Town's community role is about turning "a great routine someone built on a Tuesday into something thousands of people use by Friday". Shared routine links already install for anyone and preview signed out, but all 80 routine pages on town.com are Town's own.

    High impactMedium effort First result in 1 quarter Community & Events lead

    First action

    Pick ten great shared routines and ask their builders to be featured.

    How to measure it

    Community routine installs

    Now
    –
    Target
    5,000 a month
    By
    2 quarters

    Steps

    1. 1

      Set rules

      Quality and privacy review.

      Community & Events lead 1 week

    2. 2

      Build submission

      Paste a shared link.

      AI Product Engineer 2 weeks

    3. 3

      Page template

      Builder, tools, install.

      Software Engineer, Growth 2 weeks

    4. 4

      Seed

      Ten featured routines.

      Community & Events lead 2 weeks

    5. 5

      Feature weekly

      Email and social.

      Community & Events lead weekly

    6. 6

      Measure

      Installs and sign-ups per page.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Community & Events lead

    Smallest test

    Publish five community routines by hand.

    Why it works

    Add a community section to /routines: builders submit a shared link, the community lead reviews it, and approved routines get an indexed page with the builder's name, what it does, the tools it needs and an install button. Rank by installs and feature one each week.

    Every published routine becomes a search page and a reason to share, and builders promote pages that carry their name.

    Risks and how to handle them

    • Routines leak private details

      Review every submission before publishing.

    Evidence

    • HiringCommunity & Events (San Francisco, posted September 24, 2026): "Our best users don't just use Town - they build with it. They write routines and skills, wire up their own tools, and then tell other people how to do it." The job is "the pipeline that turns a great routine someone built on a Tuesday into something thousands of people use by Friday", builder nights, workshops and dinners, turning "user-built routines, workflows, and stories" into material for Marketing, Sales and Support, and measuring "activation, retention, and adoption among community members versus everyone else".Source
    • Your websiteRoutine sharing docs: "Share a routine with a link that anyone can open and install as their own"; links "show a preview on X, LinkedIn, and iMessage"; "Shared links support preview even when not signed in"; "Code-based routines can't be shared yet".Source
    • Your websiteRoutine pages such as Auto Inbox are written by Town: a ready prompt ("Sent when you sign up - works as-is, or edit anything"), a "Get started with this routine" link that opens the assistant with the prompt filled in and tagged "Routine-Landing-Page", how-it-works steps and FAQ structured data. None of the 80 routine pages credits a routine built by a user.Source
    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
  • 08

    The community lead will run "builder nights, workshops, dinners", and Town hires in San Francisco and New York. Events usually end with photos; here they can end with installable routines.

    Medium impactMedium effort First result in 1 quarter Community & Events lead

    First action

    Book the first founders' night in San Francisco.

    How to measure it

    Routines from events

    Now
    –
    Target
    10 a month
    By
    2 quarters

    Steps

    1. 1

      Pick roles

      One per event.

      Community & Events lead 1 week

    2. 2

      Invite

      Power users and prospects.

      Community & Events lead 2 weeks

    3. 3

      Run

      Build live.

      Community & Events lead monthly

    4. 4

      Publish pack

      On the role page.

      Community & Events lead 1 week

    5. 5

      Record recap

      10 minutes.

      Community & Events lead 1 week

    6. 6

      Measure

      Attendee activation vs others.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Event costs
    Owner
    Community & Events lead

    Smallest test

    Run one evening for 30 people.

    Why it works

    Run a monthly builder night per city around one role (founders, sellers, recruiters). Attendees build a routine live; the best five become a role pack linked from that role page, with builders credited. Record a 10-minute recap.

    Events create both community and content, and role packs make the role pages more useful.

    Risks and how to handle them

    • Low turnout

      Co-host with founder and sales communities.

    Evidence

    • HiringCommunity & Events (San Francisco, posted September 24, 2026): "Our best users don't just use Town - they build with it. They write routines and skills, wire up their own tools, and then tell other people how to do it." The job is "the pipeline that turns a great routine someone built on a Tuesday into something thousands of people use by Friday", builder nights, workshops and dinners, turning "user-built routines, workflows, and stories" into material for Marketing, Sales and Support, and measuring "activation, retention, and adoption among community members versus everyone else".Source
    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
    • HiringAI Product Engineer (San Francisco and NYC): projects include "the suggestion engine -- tasks and workflow suggestions to inspire users on what to automate next", "the workflow builder -- making it trivial for anyone to build, share, and install automations", "team and shared workflow surfaces -- one person builds, the whole team benefits" and "a network of assistants that talk to each other across teams and organizations". Every post says: "Four months after our public launch, we became a $1B company." Town is also hiring AI engineers for evals and context, backend, macOS, security and TechOps engineers.Source
  • 09

    Townies now "work directly with customers, partners, and candidates outside the company over email and text", and users can CC their Townie. Each of those messages reaches someone who has just seen Town do real work.

    High impactMedium effort First result in 1 quarter Software Engineer

    First action

    Count outbound Townie messages per week.

    How to measure it

    Recipient sign-ups

    Now
    –
    Target
    2% of recipients
    By
    2 quarters

    Steps

    1. 1

      Count reach

      Outbound messages and recipients.

      Software Engineer, Growth 2 days

    2. 2

      Write the line

      Short and optional.

      Head of Business 1 day

    3. 3

      Build the page

      What your Townie could do.

      Software Engineer, Growth 1 week

    4. 4

      Add the setting

      On by default, easy to turn off.

      AI Product Engineer 1 week

    5. 5

      Track

      Recipient domain sign-ups.

      Software Engineer, Growth ongoing

    6. 6

      Review

      Complaints and opt-outs.

      Product Support monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Software Engineer, Growth

    Smallest test

    Add the line to scheduling emails only.

    Why it works

    Add an optional, tasteful line to outgoing Townie messages ("Scheduled by Bo, Dana's Townie at Town") with a link to a page showing what that recipient's own Townie could do. Let users switch it off, and track sign-ups by recipient domain.

    This is how scheduling tools spread: the recipient sees the product working before seeing any ad.

    Risks and how to handle them

    • Users dislike branding on their emails

      Make it optional and reward keeping it on with credits.

    Evidence

    • Your websiteSeries B release (October 19, 2026): $108 million co-led by Forerunner Ventures and Menlo Ventures at a $1 billion valuation, to take Town "from individuals to whole teams". Townies "ask each other questions" and "hand off work", and "can also work directly with customers, partners, and candidates outside the company over email and text". Example: when BizOps updates competitor comparisons once, "every rep's Townie preps calls with the new competitive analysis built in".Source
    • Your websiteChangelog: 22 updates in the last 90 days, including Town 2.0 (September 30: "Tasks are now threads"), "CC your Townie" (September 24), Townies in group chats (September 3) and "Build routines together in threads" (October 21).Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 10

    Town says people "bring their teams and companies with them", and the growth role wants individuals onto teams. A Google Workspace admin approval "does not create a Town account or add a user to a Town team", so colleagues can each sign up alone without ever finding each other.

    High impactMedium effort First result in 1 quarter Software Engineer

    First action

    Count work domains with two or more users and no team.

    How to measure it

    Domain-matched teams

    Now
    –
    Target
    1,000 a quarter
    By
    2 quarters

    Steps

    1. 1

      Count domains

      Two or more users, no team.

      Software Engineer, Growth 1 day

    2. 2

      Design consent

      Users opt in to being found.

      Security Engineer 1 week

    3. 3

      Build the prompt

      At sign-up and in the app.

      Software Engineer, Growth 2 weeks

    4. 4

      Notify earliest user

      Colleagues have joined.

      Software Engineer, Growth 1 week

    5. 5

      Exclude personal domains

      Gmail and similar.

      Software Engineer, Growth 1 day

    6. 6

      Measure

      Teams and paid conversion.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Software Engineer, Growth

    Smallest test

    Email users at the top 100 shared domains.

    Why it works

    When a new user shares a work domain with existing users, offer to join or create the company team (with the existing users' consent), and show the team features they gain. Send the earliest user a note that colleagues have arrived.

    Domain matching turns scattered individual accounts into teams, which is the path to paid team plans.

    Risks and how to handle them

    • Privacy concerns

      Never reveal names without consent.

    Evidence

    • HiringFounding GTM Recruiter (posted July 29, 2026): "Town is a true product-led-growth company. People find Town, start using it themselves, and bring their teams and companies with them - so we already have real enterprise usage and more inbound than we can keep up with." Town has "made our first commercial hires" and will hire "revenue and sales, product marketing, growth, business operations, customer success, and partnerships", working with "the Head of Business". The recruiter should "Recruit for Town on Town".Source
    • Your websiteGoogle Workspace admin guide: "Town uses per-user OAuth authorization" and "does not use Google Workspace domain-wide delegation"; "An admin approval does not create a Town account or add a user to a Town team." A Microsoft Entra guide sits alongside it.Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
    • Your websiteTeams docs: new teams start on Team Free; members keep their personal plans and "a free team grants no credits of its own". Default access rules: "Invite members -> Admins & owners" and "Create installable routines -> Admins & owners". Fully offboarding a departed teammate "isn't self-serve today. Email support".Source
  • 11

    The growth role calls enterprise SSO "a near-term must-have", and Town already has SOC 2 Type 2, a public DPA, a trust center and Google Workspace and Entra guides. But there is no single page for the IT buyer who has to approve a company rollout.

    High impactHigh effort First result in 2 quarters Security Engineer

    First action

    List the ten questions security teams ask most often.

    How to measure it

    Days to complete security review

    Now
    –
    Target
    -30%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      From recent reviews.

      Security Engineer 1 week

    2. 2

      Write the page

      Controls, data, SSO.

      Security Engineer 2 weeks

    3. 3

      Ship SSO

      SAML or OIDC.

      Software Engineer, Growth 1 quarter

    4. 4

      Link it

      Pricing, trust, sales.

      Head of Business 1 day

    5. 5

      Add review form

      Request a security review.

      Head of Business 1 day

    6. 6

      Measure

      Review time and wins.

      Head of Business quarterly

    First result
    2 quarters
    Cost
    Engineering time
    Owner
    Security Engineer

    Smallest test

    Publish a security FAQ for IT buyers.

    Why it works

    Build /enterprise for IT and security: SSO and admin controls, per-user OAuth with no domain-wide delegation, access rules, data retention, model training defaults and a security review request. Link it from pricing, the trust page and sales emails.

    Enterprise deals stall in security review; one clear page shortens it and turns usage into contracts.

    Risks and how to handle them

    • SSO slips

      Publish the page now with a dated roadmap note.

    Evidence

    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
    • Your websiteGoogle Workspace admin guide: "Town uses per-user OAuth authorization" and "does not use Google Workspace domain-wide delegation"; "An admin approval does not create a Town account or add a user to a Town team." A Microsoft Entra guide sits alongside it.Source
    • Your websiteHomepage: "Learns how you work, then gets to work." It introduces ten named Townies, each shown with an address ([email protected], [email protected], [email protected] and others), lists sample results from Gmail, Slack, HubSpot, Salesforce, QuickBooks and others, and says "Nothing you connect trains a model, by default" and "SOC2 Type 2 compliant".Source
    • Your websitePricing page: Free $0 (30 chat messages a month, 7-day Pro trial), Starter $15 a month, Pro $49, Power $99 and Power Plus $199 per user (annual); Team $59 per seat a month annually ($71 monthly) with 6,000 pooled credits per seat, Team Plus $149 ($179) with 18,000; Enterprise custom with "Org-wide usage analytics". The FAQ says team plans add "org-wide analytics", but the comparison table shows a dash for "Org usage analytics" in every column, Team included. Every account's overage cap "defaults to $0". The page offers "Get a recommendation in 30 seconds".Source
  • 12

    Town's Teams docs say fully offboarding a departed teammate "isn't self-serve today. Email support", and a removed member's own routines may keep sending emails. Product Support is asked to drive down contact rates.

    Medium impactMedium effort First result in 1 quarter Product Support

    First action

    Count offboarding tickets last quarter.

    How to measure it

    Offboarding support tickets

    Now
    –
    Target
    -80%
    By
    2 quarters

    Steps

    1. 1

      Count tickets

      Last quarter.

      Product Support 1 day

    2. 2

      Define rules

      Company-domain accounts only.

      Security Engineer 1 week

    3. 3

      Build flow

      Stop, revoke, transfer, close.

      Software Engineer, Growth 1 month

    4. 4

      Add audit log

      Admin actions.

      Security Engineer 2 weeks

    5. 5

      Update docs

      Teams page.

      Product Support 1 day

    6. 6

      Measure

      Tickets after launch.

      Product Support monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Product Support

    Smallest test

    Write the manual checklist support uses and publish it.

    Why it works

    Give admins an offboarding flow for company-domain accounts: stop routines, revoke team integrations, transfer shared routines and close the account, with an audit log. Track how many tickets it removes.

    Clean offboarding is an enterprise requirement and removes a recurring support ticket.

    Risks and how to handle them

    • Admins remove the wrong person

      Require confirmation and a grace period.

    Evidence

    • Your websiteTeams docs: new teams start on Team Free; members keep their personal plans and "a free team grants no credits of its own". Default access rules: "Invite members -> Admins & owners" and "Create installable routines -> Admins & owners". Fully offboarding a departed teammate "isn't self-serve today. Email support".Source
    • HiringProduct Support (posted August 12, 2026): own inbound support, "shape AI-assisted support flows so automated answers stay accurate", "drive down contact rates so the same issue doesn't come back", and "Write the docs, playbooks, and help content that let support scale".Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 13

    Town has 11 role pages (sellers, marketers, recruiters, founders, finance, venture capital and more) and 80 routine pages, but the role pages lead to a general sign-up. A seller should be able to install the seller's routines in one step.

    High impactMedium effort First result in 1 quarter Head of Business

    First action

    Pick the five routines sellers use most.

    How to measure it

    Week-1 active rate from role pages

    Now
    –
    Target
    +20%
    By
    2 quarters

    Steps

    1. 1

      Pick routines

      Five per role.

      Community & Events lead 2 weeks

    2. 2

      Bundle

      One install link per pack.

      AI Product Engineer 2 weeks

    3. 3

      Update pages

      Pack CTA on each role page.

      Software Engineer, Growth 1 week

    4. 4

      Write emails

      Role onboarding series.

      Head of Business 2 weeks

    5. 5

      Paid tests

      Search per role.

      Head of Business 1 month

    6. 6

      Measure

      Activation by role.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Engineering and ad test budget
    Owner
    Head of Business

    Smallest test

    Launch the sales pack first.

    Why it works

    Add a "Sales pack" (and one per role) to each role page: three to five routines installed with one link through the existing sharing system, plus a role-specific onboarding email series. Measure sign-ups and activation per role.

    Role-matched first value speeds activation and makes paid search per role worth buying.

    Risks and how to handle them

    • Packs feel generic

      Use routines from real users in that role.

    Evidence

    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
    • Your websiteRoutine sharing docs: "Share a routine with a link that anyone can open and install as their own"; links "show a preview on X, LinkedIn, and iMessage"; "Shared links support preview even when not signed in"; "Code-based routines can't be shared yet".Source
    • Your websiteRole pages include "Town for Parents" (Townies "sort your school mail, fill the family calendar, and keep pickups covered") and "Town for Sellers" ("draft your follow-ups, brief you before every demo, and keep your CRM clean"). The Series B release quotes Menlo: Town "has wisely chosen business over pleasure".Source
  • 14

    Town is building a suggestion engine "to inspire users on what to automate next". New signups land on a 7-day Pro trial; what they set up in that week decides whether they pay.

    High impactMedium effort First result in 1 quarter AI Product Engineer

    First action

    Compare trial-to-paid for users with one vs two routines.

    How to measure it

    Trial-to-paid conversion

    Now
    –
    Target
    +15%
    By
    2 quarters

    Steps

    1. 1

      Find the link

      Routines vs conversion.

      Software Engineer, Growth 2 days

    2. 2

      Pick suggestions

      By connected tools.

      AI Product Engineer 1 week

    3. 3

      Build prompts

      Day two and five.

      AI Product Engineer 2 weeks

    4. 4

      One-tap install

      From the suggestion.

      AI Product Engineer 1 week

    5. 5

      Test

      Against no suggestions.

      Software Engineer, Growth 1 month

    6. 6

      Measure

      Conversion by routines.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    AI Product Engineer

    Smallest test

    Suggest one routine by email to 1,000 trial users.

    Why it works

    On day two and day five, suggest one routine based on the tools the user connected and what they asked for, with a one-tap install. Track trial-to-paid by number of active routines at day seven.

    Users with two active routines get value every day without asking, which is the habit that converts trials.

    Risks and how to handle them

    • Too many prompts

      One suggestion at a time.

    Evidence

    • HiringAI Product Engineer (San Francisco and NYC): projects include "the suggestion engine -- tasks and workflow suggestions to inspire users on what to automate next", "the workflow builder -- making it trivial for anyone to build, share, and install automations", "team and shared workflow surfaces -- one person builds, the whole team benefits" and "a network of assistants that talk to each other across teams and organizations". Every post says: "Four months after our public launch, we became a $1B company." Town is also hiring AI engineers for evals and context, backend, macOS, security and TechOps engineers.Source
    • Your websitePricing page: Free $0 (30 chat messages a month, 7-day Pro trial), Starter $15 a month, Pro $49, Power $99 and Power Plus $199 per user (annual); Team $59 per seat a month annually ($71 monthly) with 6,000 pooled credits per seat, Team Plus $149 ($179) with 18,000; Enterprise custom with "Org-wide usage analytics". The FAQ says team plans add "org-wide analytics", but the comparison table shows a dash for "Org usage analytics" in every column, Team included. Every account's overage cap "defaults to $0". The page offers "Get a recommendation in 30 seconds".Source
    • Your websiteRoutine pages such as Auto Inbox are written by Town: a ready prompt ("Sent when you sign up - works as-is, or edit anything"), a "Get started with this routine" link that opens the assistant with the prompt filled in and tagged "Routine-Landing-Page", how-it-works steps and FAQ structured data. None of the 80 routine pages credits a routine built by a user.Source

Big bets 3

Larger plays that can change the trajectory.

  • 15

    Town is building "a network of assistants that talk to each other across teams and organizations". When a Townie works with someone outside the company, the best experience is for that person to have a Townie too.

    High impactHigh effort First result in 3 quarters Co founder and CEO

    First action

    Map the most common cross-company tasks Townies already handle.

    How to measure it

    Companies joined via Townie handoffs

    Now
    –
    Target
    20% of new teams
    By
    3 quarters

    Steps

    1. 1

      Map tasks

      Scheduling, documents, intros.

      AI Product Engineer 1 month

    2. 2

      Design permissions

      What crosses company lines.

      Security Engineer 1 month

    3. 3

      Build handoffs

      Townie to Townie across companies.

      AI Product Engineer 1 quarter

    4. 4

      Invite outsiders

      Clear offer in the handoff.

      Software Engineer, Growth 1 month

    5. 5

      Launch

      With design partners.

      Head of Business 1 month

    6. 6

      Measure

      Companies joined.

      Software Engineer, Growth quarterly

    First result
    3 quarters
    Cost
    Product time
    Owner
    Co founder and CEO

    Smallest test

    Run one cross-company scheduling pilot with two customers.

    Why it works

    Let Townies at two different companies coordinate meetings, documents and handoffs directly, with a clear "your Townie could handle this" invite for outside people who don't have one. Measure new companies joining through cross-company work.

    Each new company makes Town more useful to every company it works with, which is a network effect few assistants have.

    Risks and how to handle them

    • Data crosses companies wrongly

      Share only what each person would share, with approvals.

    Evidence

    • HiringAI Product Engineer (San Francisco and NYC): projects include "the suggestion engine -- tasks and workflow suggestions to inspire users on what to automate next", "the workflow builder -- making it trivial for anyone to build, share, and install automations", "team and shared workflow surfaces -- one person builds, the whole team benefits" and "a network of assistants that talk to each other across teams and organizations". Every post says: "Four months after our public launch, we became a $1B company." Town is also hiring AI engineers for evals and context, backend, macOS, security and TechOps engineers.Source
    • Your websiteSeries B release (October 19, 2026): $108 million co-led by Forerunner Ventures and Menlo Ventures at a $1 billion valuation, to take Town "from individuals to whole teams". Townies "ask each other questions" and "hand off work", and "can also work directly with customers, partners, and candidates outside the company over email and text". Example: when BizOps updates competitor comparisons once, "every rep's Townie preps calls with the new competitive analysis built in".Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 16

    Town's best users "write routines and skills" and tell others how. Shared routines install with a link, but builders get nothing when hundreds of people install their work.

    High impactMedium effort First result in 2 quarters Community & Events lead

    First action

    Count shared routine installs by builder.

    How to measure it

    Community routine installs

    Now
    –
    Target
    20,000 a quarter
    By
    3 quarters

    Steps

    1. 1

      Count installs

      By builder.

      Software Engineer, Growth 1 week

    2. 2

      Set rewards

      Credits per active install.

      Head of Business 1 week

    3. 3

      Build profiles

      Public builder pages.

      AI Product Engineer 1 month

    4. 4

      Leaderboard

      Monthly.

      Community & Events lead 2 weeks

    5. 5

      Launch

      At a builder night.

      Community & Events lead 1 month

    6. 6

      Measure

      Installs and retention.

      Software Engineer, Growth monthly

    First result
    2 quarters
    Cost
    Reward credits
    Owner
    Community & Events lead

    Smallest test

    Reward the top ten builders by hand this month.

    Why it works

    Give builders credits per active install (for example 50 credits per install still active after two weeks), a public builder profile and a monthly leaderboard. Top builders get early access and a seat at builder nights.

    Rewarding creators turns power users into a distribution team and fills the gallery with routines Town would never write itself.

    Risks and how to handle them

    • Low-quality spam routines

      Pay only for installs that stay active.

    Evidence

    • HiringCommunity & Events (San Francisco, posted September 24, 2026): "Our best users don't just use Town - they build with it. They write routines and skills, wire up their own tools, and then tell other people how to do it." The job is "the pipeline that turns a great routine someone built on a Tuesday into something thousands of people use by Friday", builder nights, workshops and dinners, turning "user-built routines, workflows, and stories" into material for Marketing, Sales and Support, and measuring "activation, retention, and adoption among community members versus everyone else".Source
    • Your websiteRoutine sharing docs: "Share a routine with a link that anyone can open and install as their own"; links "show a preview on X, LinkedIn, and iMessage"; "Shared links support preview even when not signed in"; "Code-based routines can't be shared yet".Source
    • Your websiteReferral docs ("Invite Friends & Earn Credits", updated October 21, 2026): a friend who signs up through your link gets "a 14-day Pro trial instead of the standard 7 days", and you earn "2,000 Town Credits" when they start paying. But "Team and enterprise plans don't qualify. Only paid personal plans earn the reward." Rewards go to your personal balance "even if a team covers your Town plan".Source
  • 17

    Town has "more inbound than we can keep up with" and is hiring its first sales, success and partnerships team. The best leads are companies where several people already use Town.

    High impactHigh effort First result in 2 quarters Head of Business

    First action

    List the 50 domains with the most active users.

    How to measure it

    Pipeline from top-scored domains

    Now
    –
    Target
    60% of new pipeline
    By
    2 quarters

    Steps

    1. 1

      Define the score

      Usage signals.

      Software Engineer, Growth 2 weeks

    2. 2

      Build it

      Weekly list.

      Software Engineer, Growth 1 month

    3. 3

      Route

      To sales with summaries.

      Head of Business 1 week

    4. 4

      Write outreach

      Based on real usage.

      Head of Business 2 weeks

    5. 5

      Track

      Win rate by score.

      Head of Business monthly

    6. 6

      Tune

      Weights each quarter.

      Software Engineer, Growth quarterly

    First result
    2 quarters
    Cost
    Analyst time
    Owner
    Head of Business

    Smallest test

    Hand sales the top 20 domains this week.

    Why it works

    Build a company score from usage: active users per domain, shared routines, team integrations, pooled-credit burn and limit hits. Route the top companies to sales each week with a summary of who uses what, and track win rate by score.

    Product-led companies sell best where usage already exists, and a score keeps a small team focused.

    Risks and how to handle them

    • Users feel watched

      Use aggregate counts and explain it in the privacy policy.

    Evidence

    • HiringFounding GTM Recruiter (posted July 29, 2026): "Town is a true product-led-growth company. People find Town, start using it themselves, and bring their teams and companies with them - so we already have real enterprise usage and more inbound than we can keep up with." Town has "made our first commercial hires" and will hire "revenue and sales, product marketing, growth, business operations, customer success, and partnerships", working with "the Head of Business". The recruiter should "Recruit for Town on Town".Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
    • Your websitePricing page: Free $0 (30 chat messages a month, 7-day Pro trial), Starter $15 a month, Pro $49, Power $99 and Power Plus $199 per user (annual); Team $59 per seat a month annually ($71 monthly) with 6,000 pooled credits per seat, Team Plus $149 ($179) with 18,000; Enterprise custom with "Org-wide usage analytics". The FAQ says team plans add "org-wide analytics", but the comparison table shows a dash for "Org usage analytics" in every column, Team included. Every account's overage cap "defaults to $0". The page offers "Get a recommendation in 30 seconds".Source

Wildcards 3

Unexpected experiments, each with a cheap way to test it.

  • 18

    The recruiter post asks the hire to "Recruit for Town on Town", and Town has a Recruiting role page. Town is hiring a full commercial team, so its own recruiting is a live case study.

    Medium impactLow effort First result in 1 quarter Founding GTM Recruiter

    First action

    Pick three routines the recruiting team runs every day.

    How to measure it

    Recruiting page sign-ups

    Now
    –
    Target
    +40%
    By
    2 quarters

    Steps

    1. 1

      Pick routines

      Three daily ones.

      Founding GTM Recruiter 1 week

    2. 2

      Measure results

      Time to schedule.

      Founding GTM Recruiter 1 month

    3. 3

      Share links

      Installable versions.

      Founding GTM Recruiter 1 day

    4. 4

      Update page

      Recruiting role page.

      Software Engineer, Growth 1 day

    5. 5

      Post with jobs

      Link in job posts.

      Founding GTM Recruiter ongoing

    6. 6

      Measure

      Sign-ups.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Founding GTM Recruiter

    Smallest test

    Share one routine this month.

    Why it works

    Share the routines the recruiting team uses (candidate research, scheduling, follow-ups) as installable links on the Recruiting page, with results such as time to schedule. Post the routines alongside job posts.

    Real internal use is credible proof, and recruiters are a natural audience for heavy email and calendar work.

    Risks and how to handle them

    • Candidates uneasy about AI

      Show that every message is reviewed.

    Evidence

    • HiringFounding GTM Recruiter (posted July 29, 2026): "Town is a true product-led-growth company. People find Town, start using it themselves, and bring their teams and companies with them - so we already have real enterprise usage and more inbound than we can keep up with." Town has "made our first commercial hires" and will hire "revenue and sales, product marketing, growth, business operations, customer success, and partnerships", working with "the Head of Business". The recruiter should "Recruit for Town on Town".Source
    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
    • Your websiteRoutine sharing docs: "Share a routine with a link that anyone can open and install as their own"; links "show a preview on X, LinkedIn, and iMessage"; "Shared links support preview even when not signed in"; "Code-based routines can't be shared yet".Source
  • 19

    Town has a "Town for Parents" page while its backers praise it for choosing "business over pleasure". Working parents juggle school mail and work mail in the same day.

    Medium impactLow effort First result in 1 quarter Software Engineer

    First action

    Count parent-page sign-ups that later connect a work account.

    How to measure it

    Work accounts added by parent sign-ups

    Now
    –
    Target
    30%
    By
    2 quarters

    Steps

    1. 1

      Measure

      Parent sign-ups with work domains.

      Software Engineer, Growth 2 days

    2. 2

      Rewrite page

      Working parents.

      Head of Business 1 week

    3. 3

      Add prompt

      Connect work account.

      AI Product Engineer 1 week

    4. 4

      Bundle routines

      Family plus work.

      Community & Events lead 1 week

    5. 5

      Test ads

      Working-parent audiences.

      Head of Business 1 month

    6. 6

      Decide

      Keep, change or retire the page.

      Head of Business 1 quarter

    First result
    1 quarter
    Cost
    Small ad test budget
    Owner
    Software Engineer, Growth

    Smallest test

    Add the work-account prompt to parent onboarding.

    Why it works

    Reposition the page around working parents: one Townie for both inboxes, with a prompt to connect the work account once family routines are running. Track how many parent sign-ups add a work domain.

    A personal entry point that leads to work use fits the business focus instead of competing with it.

    Risks and how to handle them

    • Mixed message

      Keep it clearly about work-life overlap.

    Evidence

    • Your websiteRole pages include "Town for Parents" (Townies "sort your school mail, fill the family calendar, and keep pickups covered") and "Town for Sellers" ("draft your follow-ups, brief you before every demo, and keep your CRM clean"). The Series B release quotes Menlo: Town "has wisely chosen business over pleasure".Source
    • Your websiteSitemap (301 URLs, checked October 23, 2026): 119 docs pages, 80 routine pages, 54 integration pages, 11 role pages (sales, marketing, recruiting, founders, finance, venture capital, parents and others) and 5 Learn guides. There is no blog, no customer stories page and no comparison page; the homepage carries one testimonial, from an investor.Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
  • 20

    The homepage introduces ten named Townies, each shown with an @town.com address. Visitors see addresses that look like they could be emailed, but the only path is sign-up.

    Medium impactMedium effort First result in 1 quarter AI Product Engineer

    First action

    Decide which Townie becomes the demo address.

    How to measure it

    Demo-to-sign-up rate

    Now
    –
    Target
    15%
    By
    2 quarters

    Steps

    1. 1

      Pick the address

      One named Townie.

      AI Product Engineer 1 day

    2. 2

      Define limits

      No account access, rate limits.

      Security Engineer 1 week

    3. 3

      Build replies

      Helpful sample tasks.

      AI Product Engineer 1 month

    4. 4

      Add the link

      Sign up to connect accounts.

      Software Engineer, Growth 1 day

    5. 5

      Promote

      Homepage and social.

      Head of Business 1 week

    6. 6

      Measure

      Replies to sign-ups.

      Software Engineer, Growth monthly

    First result
    1 quarter
    Cost
    Model usage costs
    Owner
    AI Product Engineer

    Smallest test

    Run the demo address for one week on social.

    Why it works

    Make one of them a live demo: email it a real question ("help me plan a team offsite") and get a useful reply showing how a Townie works, with a sign-up link to connect your own accounts. Rate-limit it and keep it free of any account access.

    Trying the product by email, the way Town itself works, is a low-friction first touch that matches the brand.

    Risks and how to handle them

    • Abuse and spam

      Rate limits and filters.

    Evidence

    • Your websiteHomepage: "Learns how you work, then gets to work." It introduces ten named Townies, each shown with an address ([email protected], [email protected], [email protected] and others), lists sample results from Gmail, Slack, HubSpot, Salesforce, QuickBooks and others, and says "Nothing you connect trains a model, by default" and "SOC2 Type 2 compliant".Source
    • Your websiteChangelog: 22 updates in the last 90 days, including Town 2.0 (September 30: "Tasks are now threads"), "CC your Townie" (September 24), Townies in group chats (September 3) and "Build routines together in threads" (October 21).Source
    • HiringSoftware Engineer, Growth (San Francisco, posted September 2, 2026): "Town is a product-led growth (PLG) company, and the product itself is our best growth channel." The role covers "pulling people into Town, getting individuals onto teams, getting teams onto paid, and turning teams into enterprise customers"; "invites per user, free-to-paid conversion, whether credits are calibrated right"; "Word of mouth is our most powerful growth lever"; "ensuring every team lands with at least 3 active members"; and "enterprise SSO integration (a near-term must-have for us)".Source
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • AlayaCare growth strategyA cloud platform for home-based care: intake, scheduling, EVV, clinical documentation, billing and revenue cycle, a caregiver mobile app…21 growth ideas
  • Always Green Tree Service growth strategyTree trimming, fertilization and curb appeal packages (bush trimming, power washing, mulch, gutters, tree uplighting) for homes, sold as…21 growth ideas
  • WitnessAI growth strategyAn AI security and governance platform that observes, controls and protects how employees, models, applications and AI agents use AI, with…21 growth ideas
  • Miyagi Labs growth strategyAn AI exam-prep platform and app: past papers and question banks, full-length mocks, a score predictor and a 24/7 Socratic AI tutor for…23 growth ideas
  • KAYAK growth strategyA travel metasearch engine for flights, hotels, rental cars, packages and cruises, with AI trip planning and KAYAK for Business, a…21 growth ideas
  • Arch growth strategySoftware and services that collect, extract and verify private investment documents and data (statements, capital calls, K-1s), with…22 growth ideas
  • Handshake growth strategyA career network connecting students, graduates and professionals with employers and universities, plus Handshake AI, which supplies…21 growth ideas
  • Samsung Semiconductor growth strategySamsung Electronics' semiconductor business: DRAM (including HBM), SSDs and eStorage, CXL memory, mobile and automotive processors, image…20 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 26, 2026, and cites them throughout. Town did not commission, review or endorse it, and Programmable is not affiliated with Town. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Town runs its business.

Something wrong, or do you represent Town? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 306 ideas

    Team invites and rewards, pricing table and team panel, homepage speed, comparison pages, the credit-limit moment and the first customer stories.

  2. Days 31 to 6011 ideas

    Community routine gallery, builder nights, Townie message introductions, domain team discovery, the enterprise page, offboarding, role packs and week-one suggestions; recruiting, parents and demo-Townie tests.

  3. Days 61 to 903 ideas

    Commit to the big bets: cross-company Townie handoffs, builder rewards and usage scoring for sales.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value an assistant that learns how they work without being taught. The most cited problem: work spread across inboxes, calendars, chats and apps.

  • Drafts and scheduling handled across email and calendar
  • Waiting on teammates
  • In their words: “Townie”

Market

Competitive landscape

3 competitors compared: Lindy, Fyxer and Superhuman.

  • Gap to exploit: Assistants that work with each other across teams and companies
  • Lindy: Less personal to each user
  • Fyxer: Fewer team and handoff features

Hiring signals

Town is turning a product-led surge into a team and enterprise business.

  • Software Engineer, Growth: Invites, free-to-paid, 3-member teams, SSO. Ideas 1, 2, 5, 10, 11.
  • Community & Events: User-built routines to thousands of users. Ideas 7, 8, 16.
  • Founding GTM Recruiter: First sales, marketing and success hires; more inbound than they can handle. Ideas 6, 17, 18.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence