Wiggli vs Daidalo

Daidalo is half right, and the half matters

Two Belgian companies looked at the same broken industry and agreed on the diagnosis. Daidalo's content argues that agency databases look full but act empty, that Boolean search is a patch job, that recruiters flee to LinkedIn because they stopped trusting their own ATS, and that AI on top of dirty data just accelerates chaos. Every word of that is true, and Wiggli's founders learned it the expensive way running Gentis to 60M euros.

The disagreement is the conclusion. Daidalo's thesis, in their own framing, is that you do not need a new ATS, you need better data. Read that sentence again from your legacy vendor's point of view: it is the best renewal argument Bullhorn never had to write. Cleaning the records inside a 2008-architecture ATS gives you a beautifully organised filing cabinet, and a filing cabinet still cannot source a candidate it has never met, reach one on WhatsApp, tell you which client is about to hire, generate an invoice from a timesheet, or notice that your rejected candidate started at the client last month. The data was one problem. The architecture is the other, and it is the one that decides your revenue per recruiter.

There is also the judgment question. Daidalo openly argues that recruiters cannot outsource judgment to AI, because matching tools fail to understand recruiter priorities. That critique lands on black-box matching, and it is precisely why Wiggli built Glassbox AI the other way: the recruiter sees every criterion, sets the weighting per role, and overrides anything. Judgment stays with the recruiter; the AI just stops wasting their day.

CapabilityDaidaloWiggliCategoryData cleaning and enrichment layer, API into your ATSAI-native recruitment OS, one productFounded2024, Ghent, active BeNeLuxBuilt inside Gentis over 7 years, proven on a 60M euro agencyCleans and enriches your databaseYes, its core productYes, native: re-enrichment on ingest, monthly bulk updates, on-demand refreshExternal candidate databaseNo900M+ profiles, prompt-based multilingual searchRediscovery with live availability signalsStructured data enables it in your ATSNative, ranked ahead of external candidates, routed into outreachAI matchingNone; argues against outsourcing judgmentGlassbox: transparent, per-role weighting, recruiter in controlOutreachNoEmail, LinkedIn, WhatsApp, SMS, voice notes, one inboxBD hiring signalsNoNative, with re-open counters and verified decision-makersClient portal, submissionsNoNativeBack officeNoNative perm and contract, timesheet to invoiceBackdoor hire detectionNoNative, continuousStill requires your legacy ATS licenceYes, by designNo; Wiggli replaces it

The maths of layer versus platform

Price the Daidalo route honestly: the legacy ATS renewal, plus Daidalo on top, plus the sourcing tool the clean data still cannot replace, plus the outreach sequencer, plus whatever handles timesheets and invoices. Five invoices to get a tidier version of the stack you already resent. Wiggli collapses the whole column into one line: your historical records are cleaned and re-enriched on ingest as a standard part of migration, and the freshly polished database sits inside a platform that also sources, reaches, submits, bills, and guards the back door.

Respect where due: Daidalo picked a real problem and a home market we know street by street. If your agency is contractually married to its ATS for three more years, a cleaning layer softens the sentence. If the contract is coming up, the better question is why you would re-sign it at all.