Headwind

Know which placement fees still hold before you count the cash.

Headwind checks each open role every week against your records, client replies and public hiring data, then shows what it does to this month's closing cash.

A blue windsock on a white pole, filled by the wind

Expected fees aren't cash yet.

An agency's forecast counts fees from candidates who haven't started. A client pauses hiring, a candidate takes another offer, or a role quietly goes cold, and the forecast is wrong before anyone notices.

Headwind doesn't guess. It separates what the evidence supports from what still needs a client to confirm, and keeps the difference visible.

Sample review

Three roles, three different answers

Senior Software Engineer · Retool · M-101

Offer accepted

Fee × agency's placement chance: $10,000 × 80%

Agency records, 2026-10-08: candidate signed the offer letter.

$8,000 stays in every scenario.

Product Engineer · Linear · M-102

Needs confirming

Fee × agency's placement chance: $10,000 × 50%

Agency records: two candidates at final interview. No recent client confirmation.

Question for the account manager: is this role still going ahead this month?

Staff Billing Platform Engineer · Vercel · M-103

Needs confirming

Fee × agency's placement chance: $10,000 × 40%

Crustdata: company-wide openings fell. No matching listing found since 2026-09-15. Neither proves this role stopped.

$4,000 stays in Reviewed and is left out of Downside until the client confirms.

Reviewed closing cash · November 2026 · sample

$22,000

  • Original (imported baseline)$22,000
  • Reviewed$22,000
  • Downside$13,000
$9,000 unresolved exposure across two unconfirmed rolesAlternative scenarios for the same period. They are never added together.

In the live app, the Reviewed and Downside scenarios are written to cfo.ai and read back before they show as verified.

How it works

One review a week, one question per unclear role

  1. 1

    Weekly review

    Every Monday, Headwind reads your imported roles, checks each client company and role listing on Crustdata, and applies fixed rules.

  2. 2

    Confirm with the client

    Roles the evidence can't settle get one neutral question, an owner and a due date. Paste the client's reply when it comes in.

  3. 3

    Updated forecast

    Only the affected role is reassessed. Reviewed and Downside are rewritten in cfo.ai and read back before they show as verified.

Evidence you can check, and runs that recover

  • Every item is dated and sourced. Agency records, client replies and Crustdata data are labelled, with the source date kept apart from when Headwind fetched it.
  • Unclear companies are blocked, not guessed. If Crustdata returns several possible companies, none of their data is used.
  • History is kept. A new client reply creates a new decision version; earlier ones stay readable.
  • Stopped runs resume. Finished steps are saved, so a retry picks up where it stopped.

Questions