Can you set up an ATS without IT help?

Yes. A modern ATS aimed at small and mid-sized teams is built to be set up by the person who will use it: sign up, import your candidates, pick a pipeline template and publish your first job, all in one sitting, none of it requiring a developer. IT becomes genuinely necessary in three cases: single sign-on, HRIS or payroll integrations, and custom domains. Everything else ships as a guided flow with copy-paste instructions.

What does self-serve ATS setup look like in practice?

The first session follows the same arc in almost every modern system:

1. Sign up with your email or a Google or Microsoft login, name your workspace, and you are in.
2. Pick a pipeline template. Applied, screening, interview, offer, hired is the usual default; renaming or adding stages is drag and drop, not configuration files.
3. Import candidates from a CSV export or a folder of CVs, which parsing turns into searchable profiles.
4. Create your first job and publish it to your careers page and, where the system multiposts, to job boards from the same screen.
5. Invite colleagues and set their roles from a settings page.

Vendors built for smaller teams, Recruitee, Teamtailor, Workable and Recruitifly among them, compete hard on this first hour, because a buyer who reaches a working pipeline in one sitting rarely abandons the trial. Enterprise suites choose the opposite path on purpose: a guided implementation over weeks, buying process design and deep integrations rather than speed. We map which path you actually need in how long does ATS implementation take.

In Recruitifly, the first sitting is also where the Fly assistant starts pulling weight: it drafts the job post, suggests the next setup step and prepares each change for you to confirm, which shortens the empty-system phase. There is a 7-day trial and no implementation fee on the self-serve tiers; the features page walks through what is in the box.

Which setup steps are slightly technical?

Three steps touch systems outside the ATS. None needs a developer, but each can involve a second person.

Connecting your mailbox and calendar. This is a login prompt: click connect, sign in with Google or Microsoft, approve the permissions. The wrinkle: companies that restrict third-party app consent in Microsoft 365 or Google Workspace need an admin to click approve once.

Linking a careers page. Serious vendors host job pages for you, so the minimum is adding one link to your website menu. If you want jobs embedded in your own site instead, the vendor provides a snippet for whoever edits the website.

Sender domain setup. For outreach to send from jobs@yourcompany.com and land in inboxes, your domain needs a few DNS records (SPF and DKIM). It sounds like the scariest step and is the most automated: the vendor shows the exact records, whoever manages your domain pastes them in at the registrar, and a verify button confirms the result. Five minutes of someone else’s time.

When do you genuinely need IT?

Setup task	Who handles it	Typical effort
Account, pipeline, jobs, inviting users	You	The first sitting
Candidate import (CSV or CV uploads)	You	An afternoon
Mailbox and calendar connection	You	Minutes
Careers page link or embed	You, or whoever edits the website	Minutes to an hour
Email sender domain (SPF, DKIM)	Whoever manages your DNS	Five minutes for them
Single sign-on (SAML, Okta, Entra)	Your identity admin	An hour plus testing
HRIS or payroll hand-off	IT plus the HRIS admin	Days to weeks
API access and custom workflows	A developer	Depends on scope

The bottom three rows are the honest answer. Single sign-on only matters if your company manages logins centrally, and it needs admin rights in your identity provider; at many vendors it is also gated to higher tiers, so ask before assuming. HRIS and payroll integrations, pushing a hire into AFAS, Workday or whatever runs payroll, involve field mapping and sign-off on both ends, which is the biggest reason enterprise implementations take weeks. API work assumes you have someone to build against it. If none of the three applies, and for most teams under fifty people none does, you can run the entire system without IT ever hearing about it.

Can you import your data without a consultant?

Yes, and it is the step buyers most often overbudget. Two self-serve routes exist.

CSV import. Export from your old system or spreadsheet, then map its columns to the new system’s fields in an import wizard. What reliably survives: candidates with contact details, jobs, stage or status, tags, and notes if your export includes them. What usually does not: email threads, scorecards in proprietary formats, automations and reports. You rebuild those; do not pay a consultant to migrate them.

CV uploads. If your archive is a folder of CVs, or your old system exports the original documents, bulk-upload them and let parsing rebuild structured, searchable profiles. Slower per record, but it recovers detail a CSV never held.

Either way, import a test batch of 25 to 50 records and check ten by hand before trusting thousands. Recruitifly’s migration tooling formalizes that discipline with a dry run and a rollback, so a wrong column mapping costs minutes, not your database. The full process, including the consent and retention dates you must not lose on the way over, is in how to migrate an ATS without losing data.

Which questions expose hidden setup requirements before you buy?

Setup pain rarely appears on the pricing page. Six questions surface it before money moves:

1. Is there an implementation or onboarding fee? A fee usually signals the vendor expects setup to need their staff.
2. Can I import my data myself, today, during the trial? If import is a services engagement, everything else will be too.
3. Which features in this demo need professional services or a higher tier? Demos run on fully provisioned accounts; your tier may not.
4. What DNS changes does email sending need, and is the flow guided? You want copy-paste records and a verify button, not a PDF to forward to your hosting company.
5. Is single sign-on included in my tier? SSO sold as an enterprise upsell is common.
6. Can I export everything myself when I leave? The exit is part of setup; test it during the trial.

A vendor built for self-serve answers all six in one email. Vague answers are an answer too.

Recruitifly is in private beta, built so the first sitting described above really is one sitting: pipelines, CV parsing, multiposting and GDPR tooling on every tier, with the Fly assistant proposing each next step and you confirming. If you want to test that claim against your own candidate export, talk to us and bring the CSV.