Teamtailor

What it is

Teamtailor is a Stockholm-built applicant tracking system that treats the career site as the product and the pipeline as the thing hanging off it. Most ATS vendors ship a careers page as an export target for requisitions; Teamtailor ships a page builder with the hiring workflow attached. Founded in 2013, it now reports more than 13,000 companies in over 90 countries — a customer base concentrated in Europe, which is why it turns up in DACH and Nordic evaluations that never shortlist a US-default ATS.

One release in 2026 changed what the product is for. On 28 May 2026, Teamtailor shipped Agent-Ready Career Sites across every customer site at once, with no configuration step. Career sites now serve llms.txt, agent-permissive robots.txt rules, sitemaps, link headers, Markdown content negotiation, and content signals, so ChatGPT, Claude, Perplexity, and Comet can read open roles and hand the candidate an application link inside the conversation.

Why it shows up in recruiting stacks

• Agent discovery is shipped, not roadmapped. Every other ATS in this segment expects you to solve AI-surface visibility yourself, usually through a job-board syndication contract. Teamtailor made the career site machine-readable by default. If your candidates increasingly start in a chat window instead of a search box, this is the only part of the stack that has to change.
• Employer branding is native, not a plugin. Blocks, custom domains, multi-language content, department pages, and employee-story modules live in the same admin as the pipeline. Marketing does not need a separate CMS to change the careers page, which removes the usual two-week ticket queue between a hiring push and a page that reflects it.
• Unlimited users on every plan. Pricing is indexed to how many roles you can have open at once, not to seats, so hiring managers, interviewers, and coordinators all get accounts without a line-item conversation. That is the structural reason it wins collaborative-hiring evaluations against seat-priced incumbents.
• Co-pilot is assistive AI, honestly scoped. It drafts and rewrites job ads in the editor (April 2026), summarizes resumes, and since 25 May 2026 generates analytics charts from a plain-language description of the chart you want. It is not an agent that moves candidates through stages on its own.

Pricing

Teamtailor publishes no rate card. The pricing page offers a quote and names only what every plan includes: unlimited job postings, unlimited users, support for all users, and integrations with the existing stack. Buyers are routed through a demo call, and the contract carries a 12-month minimum.

The billing unit is job slots — the number of positions you can have open simultaneously — not headcount and not recruiter seats. Third-party contract data from Vendr puts observed deals at roughly $250–400/month for 5–10 slots on the entry tier, $500–1,000/month for 10–30 slots on the middle tier, and $1,200–2,000+/month above 30 slots. Aggregators covering larger deployments report annual spend of $6,000–15,000 for mid-market and $20,000–72,000 for organizations above 500 employees. These are resale benchmarks rather than vendor figures, so treat them as the band to open on, not the number to expect.

Two mechanics move real cost. Renewals commonly carry a 3–8% uplift, and because the meter is job slots, a hiring freeze does not reduce your bill mid-term while a hiring surge can force a mid-cycle upgrade.

Best for

Talent teams at 50–1,000-employee European companies where employer brand is a real acquisition channel, hiring is collaborative across many non-recruiter interviewers, and the careers site needs to ship in five languages without a marketing project.

Not for

Agency and staffing recruiters — the data model is in-house TA, and Bullhorn fits placement work. High-volume hourly hiring belongs with Paradox or Fountain. And teams that want an agent writing into the ATS should look elsewhere today: Teamtailor has no first-party MCP server.

Versus the alternatives

• Greenhouse — the volume leader in structured hiring, with deeper approval chains, scorecard governance, and a larger partner marketplace. Pick Greenhouse when interview rigor and compliance reporting decide the evaluation; pick Teamtailor when the careers site does.
• SmartRecruiters — the other enterprise-scale incumbent here, and since SAP completed its acquisition on 11 September 2025, the one that arrives with a SuccessFactors roadmap. Pick it when recruiting must sit inside an SAP HCM estate.
• Ashby — the fastest-growing entrant in this segment and the sharpest contrast. Ashby leads on analytics depth and runs a first-party hosted MCP server; Teamtailor leads on candidate-facing brand and does not. Pick Ashby when reporting and agent access decide it.
• Recruitee — the closest European like-for-like, also collaborative-hiring shaped, now sold under the Tellent brand. Run both trials if brand tooling is the deciding axis, because the gap between them is narrower than either would like.

Watch-outs

• The quote wall is real and the meter is unusual. You cannot self-serve a price, and job-slot billing punishes bursty hiring — 12 roles opening in one quarter and two in the next bills at the peak. Guard: negotiate the slot count against your peak quarter, not your average, and ask for the mid-term upgrade price in writing before signing.
• Agent-Ready Career Sites makes you discoverable, not attributable. The feature exposes jobs to chat assistants; it does not tell you which hires came from them, and referrer data from agent traffic is largely absent. Guard: add a source parameter to the application links you control and treat “direct” growth after May 2026 as the proxy, rather than reporting an agent-sourced number you cannot defend.
• The API is narrower than the integration count suggests. It is JSON:API with a Token token= header, a mandatory date-stamped X-Api-Version header, a limit of 50 requests per 10 seconds per bucket, and a page size capped at 30 records. Webhooks are configured in the UI only, with no management endpoints, and retry behaviour is documented inconsistently. Guard: pin the version header in every environment, build idempotent webhook handlers that assume no retry, and budget real engineering time for any bulk sync above a few thousand candidates.
• No first-party MCP server. Agent access runs through community wrappers or third-party API-aggregation vendors, which means a third party holds your ATS credentials. Guard: if an agent must read the pipeline, scope a dedicated API key to that use, and re-scope by deleting and recreating it — Teamtailor keys are immutable once issued.
• Co-pilot is not a screening engine. It summarizes and drafts; it does not rank applicants against criteria the way Ashby application review does. Guard: if inbound volume is the problem you are buying to solve, run a 200-application pilot before signing, and price a separate screening layer into the same budget.