A recruiting software demo is a rehearsed route through a product. The presenter knows which screens look polished, which sample candidates make the AI look sharp, and which settings to skip. That isn't dishonest, but it means a demo you don't steer mostly shows you how well the vendor demos.
The way to steer it is to arrive with questions that pull the call onto your own work. The six groups below follow the places where a purchase tends to disappoint after signing: the workflow doesn't fit, the data is hard to move, the AI does something candidates weren't told about, an integration is thinner than it sounded, the bill grows, or help is slow when something breaks.
Each question comes with what a good answer sounds like, so you can tell a real answer from a confident pivot. The list works for agencies and in-house teams; where they'd press on different points, it says so.
What a good answer has in common
Across all six groups, the answers worth trusting share four traits:
- It's shown, not described. The presenter clicks through it on a role like yours instead of saying "yes, we do that."
- It comes with a status. Live, beta or coming soon, stated before you have to ask twice.
- It names its limits. Which plan includes it, which platforms it runs on, and what it leaves out.
- It holds up in writing. The vendor will confirm it by email after the call.
The groups follow the order a buying conversation usually takes. They aren't ranked, and the ones that deserve the most time are the ones where your current setup hurts.
Before the call: send three things
- One or two real roles. Remove anything confidential but keep the real requirements, location and pay range, and ask the vendor to set the roles up before you meet.
- Your path from application to hire or placement. List the stages in plain words and who acts at each one: recruiter, hiring manager or client.
- The tools that are staying. Email and calendar, video call platform, job boards, and any ATS, CRM or payroll system you won't replace.
Invite the person who'll use the product every day, not only the person who signs. If you run an agency and haven't narrowed the field yet, start with our buyer's checklist for agency recruiting software, then come back to these questions once you have two or three vendors to compare.
A short call with the team: how InstantIntro, the ATS and the AI Notetaker would fit the way you hire today. Book a demo
Workflow fit
- "Can you take one of our roles from posting to offer while we watch?" A good answer is a live walk-through on that role, including the unglamorous steps: moving a candidate between stages, logging a call, sending a decline. If the presenter switches to a prepared account each time your role hits a gap, write the gap down.
- "Where do hiring managers or clients see candidates, and what can they do there?" In-house teams should ask for the hiring manager's view, agencies for the client's. A good answer shows that screen, explains how access is given and taken away, and shows where feedback lands.
- "What don't you do that teams like ours usually need?" Vendors who know their product answer this plainly. Daialog, for example, is built for recruiting work and doesn't include a contract-staffing back office such as timesheets or payroll. If you can't tell whether your gap is an ATS question or a CRM one, our guide to ATS vs recruiting CRM separates the two.
- "What does the first week look like for one recruiter?" You want steps and owners: importing records, connecting email and calendar, building the first role. "It's very intuitive" isn't an answer.
Data, migration and the exit
- "How do our candidates, clients and notes come across, and who does the import?" A good answer names the file types it accepts, what maps cleanly and what doesn't (attachments, activity history, custom fields), and whether the vendor or your team does the work. Ask for a trial import of a small file before you sign.
- "If we leave, what can we export, in what format, and does it cost anything?" It's easy to leave this until contract time, which is exactly why to ask it now. A vague answer here is one to chase in writing.
- "Where is our data held, who on your side can see it, and how do we remove a user's access?" Ask for the security documentation itself, not a summary on the call. Daialog sets out its practices on its security page; expect a written equivalent from every vendor you shortlist.
- "How do we delete candidate records we shouldn't keep?" A good answer covers removing one person's data on request and whether you can control how long records stay.
AI and what candidates are told
- "What does the AI produce, and what does it work from?" A good answer is concrete: a score, a summary, a ranking or a draft, and the inputs behind it. Ask to see one output for a sample candidate along with the explanation a recruiter gets. In Daialog, the InstantIntro conversation produces one Match Score per candidate with an explanation, and that explanation is the part worth asking every vendor to show.
- "Walk me through everything a candidate is told, from the job post to the end of the screen." Listen for when the candidate learns an AI is involved, and whether it's said in plain words. In Daialog's InstantIntro, applicants have a short spoken conversation with Daia, Daialog's AI screening agent, and they know they're talking with an AI.
- "Can the AI move a candidate forward, or end a candidacy, without a person acting?" Products differ here, so get a precise answer: which settings do it, who can turn them on, and what the recruiter sees afterward. As one reference point, Daia doesn't decide who moves forward. There's no automatic rejection or knockout, and a person makes each call.
- "Which AI features are live, which are beta and which are coming soon?" Unreleased features can appear in a demo right next to shipped ones. A good answer labels each without prompting. Daialog's own labels, for comparison: Talent Search and messaging sequences for email and LinkedIn are in Beta, and text-message steps are coming soon.
- "Can we hide names and other identifying details during screening, and what's the default?" A good answer gives the setting and where it starts. In Daialog, blind screening is optional and stays off until a company turns it on.
Integrations
- "Is that a direct connection, or does it run through a third-party connector?" Both can work, but when something breaks, a connector adds another party to the fix and can bring its own limits. A good answer separates the two without hedging. Daialog's standalone InstantIntro plan, for instance, connects directly to Workable, and every other ATS connects through a third-party connector.
- "What moves between the systems, in which direction, and when?" Ask about candidates, stages, notes, scores and files one by one. "We integrate with that" can mean anything from a two-way sync to a link back to the other product.
- "Which calendars and video platforms work today?" A good answer splits what works now from what's planned. Daialog's AI Notetaker, for example, joins Google Meet and Microsoft Teams calls today, and Zoom support is coming soon.
- "Can we see it running in a live account?" A diagram of an integration tells you what was designed, not what actually syncs.
Pricing and contract terms
- "What's the billing unit, and what makes the bill go up?" Seats, open jobs, role slots, company size and usage are all common units. Daialog uses three across its own plans: per seat on its agency plans, a company-size band on the Team plan, and role slots on standalone InstantIntro, all listed on its pricing page. For a tour of the models and where extra costs hide, see how recruiting software is priced.
- "Which features sit on a higher plan?" A demo account often has everything switched on. A good answer tells you, feature by feature, which plan you'd need. On Daialog's agency plans, for example, Business Development, invoicing, Signature Hub and Collaboration Hub require Recruiter Plus.
- "How long is the contract, what's the notice period, and how is the renewal price set?" Ask for these to appear in the order form, not only in your call notes.
- "Is there a trial, and can we run real roles through it?" A trial with your own roles answers questions no demo can. Daialog has a free trial available.
Support and the first 90 days
- "When something breaks, who do we contact, through which channel, and how quickly do you respond?" A good answer gives hours, channels and a response target, and puts them in writing.
- "Who sets us up, and what does setup include?" Listen for named steps: data import, connecting email and calendars, building the first roles, training the team.
- "How will we hear about changes?" Ask how features move from beta to general release, and how much notice you get before something changes plan or price.
- "Can we talk to a customer who hires the way we do?" A team of your size and model will tell you what the demo didn't.
After the call: grade what you heard
Go back through your notes and give each answer one of four labels:
- Shown: you saw it working on screen.
- Described: the presenter explained it but didn't show it.
- Promised: it's planned, in beta or "on the roadmap."
- Dodged: you didn't get a real answer.
Shown answers are what you're buying. Promised answers are what you're buying on trust, so judge the price as if they never arrive. Then email the vendor your notes on pricing, data export, integrations and anything marked beta or coming soon, and ask them to confirm or correct each point. Their reply is often the most useful document the whole process produces.
Run the same questions, in the same order, with every vendor on your list. Three demos are far easier to compare when each one had to answer the same questions on the same role.




