Town Careers Before the Billion Headline

A case file on Town that starts with "$1B valuation" is already in the wrong order. The careers page and Ashby board list sixteen titled, on-site openings with cities. The October 19 press release lists round size and growth ratios. For a boutique desk, the board is the primary hiring record. The valuation is a secondary financing note.

We built this case from three public pages opened the same week: the Town careers marketing page, the Ashby open-positions list, and the Series B press release. No candidate was submitted. No fee was earned. The point is the research order a desk should use when a billion-dollar headline hits the feed. Town careers, accessed October 2026. Town Ashby board, accessed October 2026. Town Series B press, October 19, 2026.

Start with titles and cities, not valuation

The careers page states sixteen open roles and groups them. Business shows Community & Events, Executive Producer Brand Ops, and Product Support, all San Francisco, with published salary bands on the page we read. EPD shows AI infrastructure, evals, product engineering in San Francisco and New York City, backend in both cities, MacOS, Security, Growth, and TechOps. A third group lists Founding GTM Recruiter, Founding Technical Recruiter, and Recruiting and Office Coordinator. The page also says in-person work in San Francisco's Financial District five days a week, with a New York office. That location rule belongs in the account file next to every title.

Ashby's list matches the sixteen titles without requiring you to trust a third-party aggregator. When the press release and the board disagree in future weeks, the board wins for role-level work until the employer changes it.

What the billion-dollar line is allowed to do

The press release and the careers page both mention the $108 million Series B and the $1 billion valuation. Financing context can explain why a company can afford a sixteen-role board. It cannot invent a search owner, a fee agreement, or agency access. It also cannot collapse San Francisco and New York into one "Bay Area" desk note when the board prints both cities on separate AI Product Engineer and Backend Engineer lines.

The careers page says the company is among its first sixty employees and lists perks such as fully covered medical, dental, and vision, unlimited PTO, and on-site SF work. Those lines help a candidate conversation later. They do not create a job order for an outside recruiter today.

A five-date case file this example cannot fill yet

A searchable case you can hand to a partner needs dates you earned: acceptance of the search, first submission, first interview, outcome, and fee collection. Town's public pages give you a funding date and an access date for the board. They do not give you the five desk dates. Do not paste the October 19 round date into the fee column. Do not paste "16 roles" into the outcome column.

Useful fields you can fill now:

1. Employer legal name as shown on Ashby: Town.com, Inc.
2. Access date for the board snapshot.
3. Title list with SF versus NYC tags.
4. On-site rule from the careers page.
5. Financing note dated October 19, 2026, stored separately from requisitions.

Build the Town account file from titled careers listings. Put the $1B headline in a financing note, not in the open-role column.

In our walkthrough, the fastest error was copying "Town is hiring after Series B" into a CRM stage meant for active job orders. Replace that stage with one titled role from Ashby, the city, and a blank agency-access field. If you cannot name the title, you are still on the press release.

Boundary for this case study

This write-up does not claim Town uses agencies. It does not claim any of the sixteen roles is unfilled by the time you read it. Boards change. It does not use salary bands as fee math. And it does not treat Founding Technical Recruiter as proof that external recruiters are blocked. That title is a staffing signal inside the company. Your access still needs a human answer.

Salary bands on the careers page are useful for candidate conversations later. They are not a placement fee calculator. A $250K to $300K AI engineer band does not tell you whether Town pays contingency, retained, or nothing to outside firms. Keep compensation research and fee research in different fields.

The NYC versus SF split is another place desks get sloppy. AI Product Engineer and Backend Engineer appear in both cities on the Ashby list we opened. Community and recruiting-ops titles we saw were San Francisco. If your network is New York heavy, say so in the outreach and point at the NYC titles. Do not pitch a San Francisco-only culture page as if every role is dual-city.

Use Town as a practice case for research order: board first, press second, outreach third. The billion-dollar headline is allowed to get your attention. It is not allowed to write your job order fields. When you train a junior researcher, make them paste three URLs into the account note before they draft a sentence. If one of those URLs is only a news aggregator summarizing the round, send them back to Ashby.