Case File: Firecrawl Ashby Board, Access Date November 4, 2026

This case study is a dated research file, not a placement story. We opened Firecrawl's Series B post and its Ashby board on November 4, 2026, separated financing facts from titled roles, tagged SF and Toronto hubs, and wrote a coverage decision. Without an access date, a $75M banner ages into fake evergreen demand.

Primary sources: Series B / Alexandria post, September 22, 2026 and Firecrawl Ashby board.

Case header fields

Employer: Firecrawl. Post URL and date: September 22, 2026. Board URL: jobs.ashbyhq.com/Firecrawl. Board access date: November 4, 2026. Soft CTA on board: none required for this file; financing narrative lives in the post. Titled roles present: yes — on the order of twenty-nine openings. Researcher: RecruitHacker desk note for this batch.

Financing facts logged from the post only

$75M Series B led by Smash Capital; participants Altos Ventures, Nexus Venture Partners, Y Combinator, Freestyle, Offline Ventures; product narrative Alexandria; quality-test claim 21% across 845 tasks. No role titles copied from the post into the titled table.

Titled examples logged from Ashby

Finance and legal: Chief Financial Officer; General Counsel; Commercial Counsel; Legal Engineer. GTM and delivery: Technical BDR; Sales Engineer; Success Engineer; Implementation Specialist; Senior Field Engagement Manager; Partnerships Manager - Alexandria. Engineering and research: multiple Product Engineer lines; Backend Infrastructure; Cloud DevOps; Research Engineer Evals and Benchmarks; Agent Experience Engineer. Talent: In-House Technical Recruiter. Hubs: many engineering lines San Francisco HQ; Toronto Hub; Hybrid. Some seats San Francisco OnSite.

Each example stored as title | hubs | work mode.

Coverage decision written the same day

Active this week for a US on-site GTM desk: Technical BDR and Sales Engineer, San Francisco OnSite. Parked: Toronto hybrid engineering; CFO and GC leadership searches outside desk scope. Soft financing context: Series B post linked, not used as a title. The decision is disagreeable on purpose.

A careers case file without an access date is a rumor with formatting.

What we explicitly did not claim

No agency authority. No invented headcount from "nearly double the team." No merging Toronto and San Francisco into one market. No pay bands copied across titles. No aggregator cards as system of record.

Failure modes this case prevents

CRM note that says only "Firecrawl raised $75M — hiring." Shortlist built from the blog CTA to become a provider. Partner handoff that forces the partner to re-open Ashby to learn which hub you meant. The dated file prevents all three if kept updated.

Cadence after day one

Forty-eight hours later, re-open the board. Strike closed seats. Add new titled rows with a new access stamp. The September post can remain unchanged without changing titled coverage. Financing posts are sticky. Shortlists should not be.

Replicable checklist

1. Access date and URLs for post and board.
2. Financing facts only from the post.
3. Titled sample table with hubs and mode.
4. Coverage decision for the week.
5. Explicit non-claims.

Reuse the five fields on the next funded employer. The round size changes. The discipline does not.

Teaching the case live

If you run this file in a team meeting, open the September post and the Ashby board side by side. Fill financing fields only from the post. Fill titled fields only from Ashby. Write the access date while both tabs are visible. Do not lecture from a stale PDF. The habit transfers faster than another slide about process.

Store the case where a partner can open it without Slack archaeology: employer, post date, board access date, financing stub, titled table, coverage decision. Six fields. If any field is missing, the case is incomplete. Incomplete cases are how round-size folklore replaces research on a boutique desk that cannot afford folklore.

Outcome of the method

No candidates were submitted in this case. The deliverable is the dated file. If a partner asks whether Firecrawl was "hiring everywhere after seventy-five million," the file answers with post facts, board access date, titled examples, hubs, and the coverage decision. That is stronger than a screenshot of the blog hero.

Reuse on Blacksmith, Mintlify, or the next funded board the same week. Round sizes change. Soft posts change. The six fields do not. Incomplete cases are how folklore wins.

Who this case method is not for: teams that only work exclusive retained orders may not need Ashby case files. Teams that scrape aggregators without employer URLs will not get hub labels. Teams that refuse to write coverage decisions will still spray resumes across Toronto and SF while talking about one HQ.

Forty-eight hours later, re-open the board. If Technical BDR closed, strike it the same morning. If a new Toronto hybrid seat appears, add a new row with a new access stamp. The September post can stay unchanged. Your shortlist should not.

Print the six fields on one sheet for the research folder. Speed comes from filling the same sheet on every funded employer, not from inventing a new taxonomy each Monday.