Keep a hiring shortlist next to the profile

You don’t have a shortlist. You have debris.

A name in Slack. A PDF. A “strong!!” in a thread nobody will search. That’s not a shortlist. That’s how you re-source the same person in three weeks and don’t notice.

A real shortlist is boring: this role, these people, why they were interesting, a way to find them again. If it isn’t next to the profile when you decide, you won’t write it down.

One project, one role

Don’t mix three jobs in one pile. Backend Platform and “that React person” are not the same list. When the req changes, the pile lies to you.

In Insayab a project is one role plus the JD you hire against. Candidates you save land there with the scores from LinkedIn, GitHub, or both.

What belongs on the list

Not everyone you opened. That’s a history. A shortlist is people you’d take a conversation with.

• You’d email them this week, not “maybe later”
• You remember why-because the score and gaps are still on the row
• You can find them by name, LinkedIn, or GitHub without scrolling Slack

Spreadsheets aren’t evil. They’re late.

Export when you need to share. Don’t live there. The moment of truth is on LinkedIn, in the tab, when you still care. That’s when you hit save.

Free includes the shortlist. Pro adds CSV export and notes if you’re running this every week. You don’t need Pro to stop losing names.

Common questions

Is this an ATS?

No. It’s the list you keep while you source. When you’re ready for Greenhouse or whatever you use, export. Don’t make the ATS the place you think.

Can I search the shortlist?

Yes. Name, email, LinkedIn, GitHub. That’s the whole point of not using a Slack thread.

What if I hire for more than one role?

Make another project. Free is one project. If you’re always hiring, Pro is unlimited projects. Don’t cram two JDs into one list.