# Priya Nambiar, Director of Talent Acquisition at Stackwell (Series B, ~290 employees) — read of ai-native-ats, June 22, 2026

> 9 years in recruiting, currently running a three-person TA team trying to close 40+ reqs while our HRIS contract is up for renewal.

## How I got here
A recruiter in a TA Slack community I've been in for years posted a link with "embeddings-based ATS finally" and someone replied "not quite what you think." I had to see what the argument was about. Landed here around 11am between two video calls. I had maybe six minutes.

## What I clicked first
"Embeddings-based hiring, not keyword matching." That headline did real work. I have had this exact argument with our Greenhouse rep twice in the last quarter. "No more resume-keyword spam" — I know that pain deeply. We opened a senior PM role in April and got 380 applicants, probably 300 of whom had stuffed "Agile" and "cross-functional collaboration" into every sentence because that's what the job description said.

The hero pulled me in. I kept reading.

## Where I paused
"Team Calibration. Your hiring bar, encoded once. Every match aligned to your actual hiring decisions, not industry averages."

I sat there for a bit. That is actually the hardest problem in recruiting and I have never seen an ATS even try to address it. Getting a hiring manager to say what "good" looks like before the first resume lands is a whole separate project. If this does what it says, I would pay real money.

Then I scrolled and found: "Honest disclosure: we don't have live customers on this idea yet."

So this is not a product. It is an idea for a product. And the page had been talking to me like it was a product I could buy.

## What I distrusted
The page signals procurement-readiness for the first two scrolls: SOC 2 Type II, SSO, SAML, SCIM, data residency, dedicated CSM. Those are signals aimed at someone like me, someone who has to fill out a vendor security questionnaire before adding anything to the stack.

Then pricing is $5 and $99 for a "dossier" and a "build starter." Those are not the same product.

"We shipped the strategy package; you ship the customer conversations." I read that sentence three times. Who is "you"? I arrived here as a buyer looking for an ATS. I did not come here to become a founder. The business model is only explained about halfway down the page, after you have already been pitched features you can never actually use.

Also: "1 in 8 meaningful-success odds (Fermi)" and a Year-1 take-home of negative $33,800. Those are sitting right there. The studio publishing those numbers is essentially telling you the bet is thin. I respect the transparency but it undercuts the whole top half of the page that was trying to get me excited.

"Trusted by" is there in the nav with no logos. That phrase should not be on a page with zero customers.

## What would convince me
If I am the actual ICP here, meaning a founder considering building this rather than a TA director wanting to use it, I want to see one real debrief. Not a testimonial. One person who bought the $99 pack, attempted to build, and reported back honestly on what the first 30 days looked like. What was underspecified in the dossier? Where did the Fermi break down? Did the calibration feature turn out to be buildable in the MVP scope?

The "buyer clarity: 10/10" axis score made me laugh out loud, because I arrived as the stated ICP and spent five minutes uncertain who this page was actually for.

## What I'd ask in an email reply
1. The "team calibration encoded once" feature is the only thing on this page I have never seen attempted in any ATS. Is there a spec or a prototype anywhere that shows what that actually means technically?
2. You score buyer clarity at 10/10. I arrived here as a TA director who thought I was evaluating a product and left confused. Who is buying the $99 pack in practice, a developer, an operator, a founder with recruiting background?
3. The Year-1 take-home is negative $33,800. Is that net of build cost? Because if that number assumes a developer building it solo versus a non-technical operator hiring someone, those are completely different situations.

## Verdict: on-the-fence
The calibration angle is the first thing I have read in a long time that felt like a new idea rather than a feature rename. But the page is doing two jobs at once and doing neither cleanly: it pitches a product to buyers who cannot buy it, then sells a build kit to founders who have to scroll past SOC 2 badges to find out what they are actually purchasing.

---
*Memo by skeptic persona, generated 2026-06-22. Studio breaks own self-grading loop.*