Blosto

Blosto is a sourcing-and-outreach tool, not an ATS. You describe a role in plain language (or paste a JD, or bring a Boolean string); it builds must-have/preference/exclusion criteria, searches a claimed pool of "more than 850 million profiles," and returns a ranked shortlist with a Yes/Partial/No verdict and stated evidence per criterion — e.g. "3 years at a payments company" as the reasoning behind a Yes on fintech experience. Nothing is contacted without an explicit shortlist/approve action. Approved candidates get an automated multi-step email + LinkedIn sequence that a recruiter drafts and edits before it goes out, and follow-ups cancel automatically the moment a candidate replies. Everything funnels into a shared inbox next to the candidate's profile and score. It explicitly does not replace an ATS — once someone enters your pipeline, your ATS stays the system of record. Source: vendor site and FAQ (blosto.com, accessed 2026-09-08).

Starter is $125/month for 1 seat with 250 shortlist credits/month, annual billing; Team is $185/seat/month (pooled credits, up to 10 seats), also annual billing; Scale is custom/contact-sales. Both figures are stated on the pricing page as "billed annually," and a monthly/annual toggle labeled "Save 15%" sits above the tier cards — meaning paying month-to-month costs more than the number shown, but we could not render the toggled (non-default) monthly figure to report it exactly, so treat $125 and $185 as the annual-billing prices only. Source: blosto.com pricing section, accessed 2026-09-08 (https://www.blosto.com/#pricing).

Blosto's terms (§ 3, "Important notice: responsibility for cold-outreach activities") place sole legal responsibility for lawful use of cold email and LinkedIn outreach on the customer, disclaim all vendor liability for warning letters, fines, damages, or third-party account suspensions arising from that outreach, and require the customer to indemnify the provider against related third-party claims including legal defence costs. The clause explicitly names UWG, GDPR, BDSG, and TDDDG (German law) plus LinkedIn's own terms of use as the customer's responsibility to know and follow. Source: https://www.blosto.com/terms (English translation; German original at blosto.com/de/agb is stated as the legally binding version).

Blosto is built by march second GmbH, registered at Kempten (Allgäu) Local Court, HRB 18146, based in Kaufbeuren, Germany, with managing directors Fabian Warmdt and Sascha Lang (source: https://www.blosto.com/imprint). Its LinkedIn company page lists 12 employees and 19 followers, with posts from early September 2026 describing itself as "a young engineering team" that is "just getting started" (https://www.linkedin.com/company/blosto). We found no funding announcement, no Crunchbase profile content accessible (page CAPTCHA-gated), and no G2 or Trustpilot reviews — its G2 seller page shows 0 ratings and its Trustpilot review page 404s, consistent with a product that has not yet accumulated independent user feedback.

Blosto runs a small guides section (2 published pieces as of 2026-09-08) that is genuinely well-sourced for a company this size: its hiring-brief guide cites the NFIB's July 2026 small-business jobs report, the US Office of Personnel Management's assessment guide, the UK Civil Service Commission's recruitment guidance, and the UK ICO's 2024 audit of AI tools in recruitment, each linked to the primary document, with a closing "Sources and scope" section stating what each source covers and when the product claims were reviewed (27 August 2026). Source: https://www.blosto.com/guides/hiring-brief-to-candidate-shortlist.

Blosto does not say where its 850-million-profile pool comes from — no data-provenance, licensing, or sourcing statement on the candidate-search page or elsewhere on the site. The homepage and About page both say "more than 850 million profiles"; a LinkedIn company post from the same week says "800M+ professional profiles" — a minor inconsistency between the vendor's own channels that we could not reconcile. There is no public security/compliance page, no changelog, and no docs site (all three return 404 as of 2026-09-08). A data-processing agreement is available on request per the terms (§ 11) but isn't published.