Product
A CRM built around the interview, not around the deal.
Most systems record what a consultant did. PlanInterview records where each interview process actually stands, and shows the two outside parties the part that concerns them.
- The stage spine
- Intro, the interview rounds, offer, signed. Every process sits on the same spine, so position is the status. Extra rounds only appear when a process reaches them, which keeps a two-round pipeline from showing dead columns.
- Three readings, one dataset
- Stages gives one lane per process, ordered by momentum, with the late ones first. Board gives a column per stage. List gives a dense table you can scan by company, candidate, next action or owner. No view holds data the others lack.
- Next action and owner
- Each process carries a single next action with a date and the party that owns it. When that date passes, the process is marked late. There is no separate task list to keep in sync.
- Open items
- The consultant sees the internal checklist: a missing interview address, a scorecard that never came back, an unsigned offer letter. The company and the candidate each see only their own items, never the items belonging to the other side.
- Party-scoped access
- A company account sees the processes for its own vacancies. A candidate account sees the process they are in. Neither reaches the rest of the desk, and neither reads the notes kept by the consultant.
- Scheduling
- Propose the times you can host. The company ticks the ones that work, the candidate picks from what both sides approved, and the confirmed moment lands with everyone. On-site invitations carry the address, video invitations carry the link.
- Job board
- A public board for the roles a desk is working on. Postings arrive over an authenticated endpoint from the system that already holds them, keyed so a repeat push updates rather than duplicates.
Dense, not decorated
Phone numbers, owners, dates and process status stay visible. Nothing important hides behind a hover or a truncation.
One page per process
Both sides of the process, the open items and the full history on a single page, in the order things happened.
No login for participants
A company contact or candidate can act on a private link when they have no account, and still land in the same process.
See it with your own pipeline
Sign in to open the workspace. The stage model and the party-scoped views work the same whether you run five processes or fifty.