For recruiters and HR

Open the app. It tells you what today costs.

Most hiring tools show you where everyone is and leave you to work out what that means for your morning. This answers the question you actually have: which of my searches is in trouble, and what do I do about it before lunch.

Get started free Import a role from your ATSFree for ten interviews a month

The day view: eight role cards, each with a state chip reading needs you, moving or no candidates, the stages of its loop with candidate counts, and a footer showing candidates in flight, hires, and the next scheduled interview. — Eight open roles, worst first. Each card carries its own loop, so you can see at a glance whether a search is top-heavy — a booking problem — or bottom-heavy, where a decision is due.

Five states, because “bad” is not an instruction

A red-amber-green light tells you something is wrong and makes you open it to find out what kind of wrong. These are chosen so that each one is repaired by a different person doing a different thing.

Losing people

Somebody has been waiting more than a week. The most expensive thing on the screen, so it sorts to the top.

Cannot run

No loop, or nobody on the panel. Structural — you fix it once, in settings, not by working candidates.

Needs you

Decisions and bookings sitting in your queue. This is the pile you clear.

Moving

Interviews booked, nothing waiting on you. Leave it alone.

No candidates

Nothing in the pipeline. A sourcing problem, and a different person's job.

From “that interview happened” to “it is booked” in one click

The single most common action in recruiting used to be the one the product made hardest: an interview ends, and the candidate sits there until somebody remembers to move them.

1 · It shows up

“Priya Raman finished the onsite — move them to Architecture deep dive, or close it out.” With how long ago it ran and how many write-ups are in.

2 · You decide

Every option is a real stage of that role's own loop. No generic advance/reject that means something different for every role.

3 · It carries on

The candidate is emailed, and the booking screen for the next round opens with them and the stage already filled in.

A rejection asks first, and says plainly that it cannot be taken back. Advancing does not — being told you are through a day early costs nobody anything.

The board, when you want the board

Columns are that role's own rounds — not a generic applied / screening / onsite — and each says which preset stages it. Drag to move, with the same email and the same booking screen behind it.

The pipeline board for one role, with columns named after that role's interview rounds and candidate cards in each. — One role's pipeline. Moving a card is the same operation as deciding from the day view — one function, two front doors, so they cannot drift apart.

Times that exist, in everyone's own timezone

Availability is merged from every panel member's real calendar and read in their own zone and working hours — not the company's, and not the server's. A panel spread over Detroit, Dublin and Bangalore has fewer overlaps than anyone thinks, and the calendar says so instead of offering slots that quietly do not work.

The scheduling sheet: a role and round at the top, a candidate picker, then real open times grouped under Monday and Tuesday. — Which interview, who it is for, then the times. Asked in that order because that is the order the answer narrows — the round decides the length and the panel, so the slots offered are slots that can be taken.

The scheduling calendar: five weekdays, the teams filter on the left, and booked interviews sitting in the days they belong to. — Five weekdays at a time, filtered to a team, with the panel's real bookings in place. Concurrent interviews sit side by side rather than hiding each other.

Define a round once

A preset carries the repository, the pane layout, the terminals and the brief. Attach it to a stage and every interview at that stage opens the same way — which is the only way two candidates who sat “the technical screen” are actually comparable.

The presets screen, listing staged interview rounds with their repositories and durations. — Presets are the reusable unit. A role's loop is an ordered selection of them.

The roles screen, listing open requisitions with their loops. — Roles, with the loop each one runs. Imported roles arrive here with their stages already matched.

Teams, panels and who can see what

A business runs more than one hiring team, and they should not share a pipeline. Each team has its own roles, its own panel and its own calendar — under one bill and one set of permissions.

The teams screen, showing hiring teams and their members. — Teams own roles and supply the default panel for them.

The settings screen, showing integrations including calendar connections. — Calendars, mail domain, ATS keys and billing in one place.

Ask for it instead of finding it

A console that can actually do the work: move a candidate, build a loop from your presets, find who is free on Thursday. It tells you before it books anyone's time or emails a candidate.

The console panel showing example instructions and a picker set to your own Claude. — It runs on your own Claude when you have it installed, and on ours when you do not — a picker, not something decided behind your back.

You already know whether this is your morning.

Ten interviews a month, free. Import a role from your ATS and see your own pipeline in it before you decide anything.

Get started free