ATS at 3 people
Implementation cost > screening cost.
A modern ATS subscription, plus the time to configure stages and integrations, is a sizeable investment for a team running 1–3 roles. The ATS pays back at scale; below scale, it is overhead.
AI screening, no ATS install
AI resume screening without an ATS install.
If you’re 1–5 people running 1–3 roles, you don’t need a full ATS — you need an AI screening pass that turns the inbound pile into a shortlist. Drop the folder, write five must-haves in plain English, hand the sheet to the hiring manager. Outgrow into Greenhouse / Ashby / Lever later, cleanly.
No ATS install · CSV out · Outgrow cleanly into Greenhouse / Ashby / Lever
shortlisttable.app / tables / founder-hires-q2Lightweight
| Candidate | Stack fit | Ownership | Early-stage exp | Priority | |
|---|---|---|---|---|---|
Alice Chen Ex-Stripe · 5y | Yes | Strong | Yes · 2 stints | Call first | 1st |
Marco Silva Big-Tech · 10y | Yes | Unclear | Big-co only | Review | 2nd |
Citation · Alice Chen · “Shipped Stripe’s ledger v3 as eng-2 in a team of 4” · resume p.1Source-backed
0
ATS migration needed
Minutes
To first shortlist
1 sheet
Per role
CSV out
When you outgrow it
When an ATS is overkill
You probably don’t need an ATS yet.
ATS systems were built for the part of the funnel after the screening call: stages, scheduling, offers, hiring-manager feedback. They are usually painful at the part before — the pile of inbound resumes that needs sifting.
If your team is small and your role count is low, you do not need an ATS. You need a way to triage the inbound pile, send a shortlist to the hiring manager, and move on. When the time comes to adopt a real ATS, the CSV exports from ShortlistTable import cleanly into all of them.
Sheets at 80 resumes
Manual columns drift fast.
Maintaining a screening sheet by hand is fine for the first dozen candidates. By the 80th the must-haves stop meaning the same thing across rows, and you cannot tell which judgments were made when.
The missing middle
A screening tool, not a database.
The right tool at this stage does one job: turn the resume pile into a shortlist. Not stages, not offers, not feedback collection — just the read-and-decide step.
What you actually need
The minimum viable screening setup.
01 · Feature
Drop the folder
Upload PDFs / DOCX from email, Drive, LinkedIn — no system integration required. Resumes live in the workspace, not in a CRM you also have to learn.
PDFDOCXTXTDrive folderPasted text
02 · Feature
Write five columns
The five must-haves for the role, in plain English. The engine reads every resume against them — no prompt engineering, no schema definition.
Has the candidate built X?
On-call ownership in the last 3 years?
Worked at a startup ≤ Series B?
03 · Feature
Hand the sheet to the hiring manager
Export a CSV or share the workspace. The hiring manager sees the shortlist with per-criterion evidence, no login required.
CSVXLSXShareable link
04 · Feature
Outgrow cleanly
When you hit ~50 active candidates or ~5 open roles, switch to an ATS. The CSV preset for your chosen ATS imports the full screening history.
Lightweight phase→Hit threshold→Export to ATS
05 · Feature
Founder-friendly invites
Invite the hiring manager or a co-founder as a viewer. No per-seat billing for the people who only need to read.
0
extra seat
cost for viewers
06 · Feature
Per-role tables
Each role is its own table, with its own columns. Not a single pipeline funnel mixing engineering hires with finance hires.
Eng hiresFinanceSalesOps
How it compares
No-ATS screening vs the alternatives.
| Property | Greenhouse / Ashby / Lever | Spreadsheet | Notion / Airtable | ShortlistTable |
|---|---|---|---|---|
| Setup time for first shortlist | ✕Days–weeks | ✓Minutes | –Hours | ✓Minutes |
| Per-criterion AI verdicts | –Limited | ✕Manual | ✕Manual | ✓Plain-English columns |
| Source citations | ✕Rare | ✕Manual notes | ✕Manual | ✓Per-cell |
| Imports cleanly into a future ATS | ✓Is the ATS | –Manual mapping | –Manual | ✓Native ATS presets |
| Per-role workspace | ✓Yes | –Per sheet | –Per database | ✓Per table |
✓ Supported– Partial / manual✕ Not supported
A worked example
Hiring your first engineer.
You’re a founding team of three. You posted a backend engineer role on LinkedIn and a couple of community forums. Two weeks later you have 47 resumes in a folder and a hiring manager (you) trying to decide who deserves a screening call.
The temptation is to either install an ATS — Greenhouse for two seats feels excessive — or maintain a Google Sheet that will drift by Friday. Neither is right at this scale.
With ShortlistTable, you drop the 47 PDFs into a table, write five must-haves (e.g. “shipped a production system at Series-A or earlier”, “primary on-call ownership for ≥ 12 months”, “proficient in Go or Rust”, “comfortable with ambiguity”, “based in your timezone ±3h”), and run.
The engine reads each resume against each must-have, returns a verdict per cell with the source sentence, and bubbles up the candidates who pass all five. You spend 30 minutes on the review queue and the rest of the morning sending screening-call invites.
When you eventually hire your tenth engineer and the lightweight workflow stops scaling, you export to your ATS of choice and your screening history comes along.
FAQ
Common questions on no-ATS screening.
At what point do I actually need an ATS?+
Usually around 5+ active roles or 50+ active candidates at a time. Below that, the lightweight screening-sheet workflow is faster and cheaper. We have a longer post in the blog with thresholds and a migration checklist.
Can I share results with my hiring manager who doesn’t have an account?+
Yes — the CSV / XLSX export is the deliverable. For more interactive review, invite them as a viewer to a single table; no per-seat cost.
What about GDPR / candidate data retention?+
ShortlistTable workspaces support per-workspace retention policies — auto-archive after N days, hard-delete after M days. The same posture you would configure in an ATS.
How does this work alongside an existing ATS?+
Many of our users keep their ATS for stages / offers / scheduling and use ShortlistTable purely at the screening step. The CSV import pushes shortlisted candidates into the ATS with screening evidence preserved.
Will I lose data when I migrate to a full ATS?+
No. Every workspace exports cleanly to CSV/XLSX with full screening history and evidence, so the migration is an import on the new ATS, not a rebuild.
Is this overkill for hiring one role at a time?+
Probably — use the free browser tools for that (JD critique, JD↔CV matcher, bulk resume parser). Sign up when you have multiple inbound piles you can’t keep straight by hand.
Also for you
Other ways to stay light.
Related
Startup recruiting teams
The missing middle of the funnel.
Related
Boutique search firms
Per-search rubrics without ATS overhead.
Related
ATS-ready CSV export
When you outgrow no-ATS.
Free tool
The free browser tools
Lightest-weight screening.
Read
Sourcing without the bloat
The four-step lightweight workflow.
No ATS, no problem
Run a real screening pass without an ATS install.
Free on the first 25 resumes. CSV export goes into whatever you eventually adopt.