Ashby Setup: Day-Zero Path to a Working HR Loop

Set up Ashby for day-zero work — seats, one core loop, required integrations, and non-admin proof — before optional hubs.

By Lee M.Updated Aug 18, 20266 min readFact-checked

Quick answer

Set up Ashby in this order: qualify seats for the people who will actually open it, name one HR/ops owner, configure one hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run, connect the HRIS/payroll/calendar you depend on, then have a non-admin run a hiring manager moves a candidate and leaves feedback without an admin. Confirm AI assistance (All-in-One Foundations+) is on the package you will actually buy. You’re done when that walkthrough works — not when every optional hub is switched on.

Start on All-in-One Foundations
Name one HR / ops owner
one hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run
Connect required HRIS / payroll / calendar
Prove a non-admin can run the loop

What matters in your Ashby setup

What Ashby actually is — Ashby is an all-in-one ATS with recruiting CRM, scheduling, and analytics, marketed from startups through enterprise. Foundations is list price (≤100 employees; 10% off annual). Plus (101–1,000) and Enterprise (1,000+) are seat-based custom quotes. Foundations…
Configure these first — Research lists applicant tracking, career site and job boards, interview scheduling, and HRIS integrations as supported — that is your day-zero surface.
Do not treat it as every HR job — Ashby is applicant tracking / recruiting. It is not a substitute for frontline scheduling or a GPS time clock.
Prove with a real workflow — Worked example: Harbor Retail (two recruiters and eight hiring managers) is done when they can a hiring manager moves a candidate and leaves feedback without an admin — not after a vendor tour.

Ashby day-zero path

Ashby setup walkthrough for applicant tracking / recruiting. — A working Ashby core loop beats a decorated empty workspace.

Ashby must vs nice

Must-have

Core job loop
Plan / hub gates
Integrations

Nice-to-have

AI extras

1. Qualify seats and packaging

Researched plans: All-in-One Foundations, All-in-One Plus, All-in-One Enterprise. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/ashby/. Worked example: Harbor Retail (two recruiters and eight hiring managers) lists everyone who must log in weekly before they invite “the whole company.”

2. Configure one core loop

Configure one hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run. Research-supported surfaces include applicant tracking, career site and job boards, interview scheduling, and HRIS integrations. Worked example: Harbor Retail (two recruiters and eight hiring managers) refuses optional modules until a hiring manager moves a candidate and leaves feedback without an admin.

3. Non-admin proof

Our snapshot records no trial length for Ashby — ask for an evaluation window in writing before you commit seats. Success: a hiring manager moves a candidate and leaves feedback without an admin. Worked example: Harbor Retail (two recruiters and eight hiring managers) records a 10-minute loom of the walkthrough for stakeholders who skip hands-on time.

Ashby checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1Name an HR/ops ownerFields, users, and hygiene need a responsible party.
2Configure one core loopone hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run
3Complete non-admin proofa hiring manager moves a candidate and leaves feedback without an admin

4. Connect the integrations Ashby must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.

Research lists Slack, Google Workspace, and Zapier for Ashby. Confirm which are native vs API before go-live.

Pick one identity or SSO path if required.
Connect one operational integration the weekly users touch daily.
Document anything left as manual export.

Worked example: Startups and growth-stage companies (≤100 employees) that want one modern ATS+analytics platform connects the one integration that prevents double entry before inviting the full team.

5. Train weekly users — not a one-time all-hands

Train the people who must open Ashby every week. Cover: login, the core loop (applicant tracking, career site and job boards, and interview scheduling), and where to log blockers.

Worked example: Startups and growth-stage companies (≤100 employees) that want one modern ATS+analytics platform runs a 30-minute working session on live data and includes one sceptic who will actually use the tool.

6. Write the setup note stakeholders can audit

Document plan tier, admin owner, integrations live, and the non-admin proof (applicant tracking, career site and job boards, and interview scheduling). Link to /pricing/ashby/ for commercial detail.

Worked example: Startups and growth-stage companies (≤100 employees) that want one modern ATS+analytics platform stores a one-page note finance and IT can read without joining another demo.

7. Connect the integrations Ashby must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.