The pillar that builds things, and says what it is not building.
Software, training and transformation work for companies whose hiring process was designed before any of this existed. It is where the largest share of current effort sits, and where our first product is coming from.
- Markets
- United States and India
- Product
- Offer-to-joining platform, in build
- Owner
- [Named owner]
- Status
- Active build
What sits here
Three services and one product.
AI training for recruiters
Practical cohorts for recruitment teams: sourcing, screening, candidate communication, bias risk, and the judgment to know when not to use a model at all.
Read more →ConsultingDigital and AI transformation
Process work first, tooling second. Most hiring processes do not need a new system so much as they need three steps removed and one decision made earlier.
Read more →ResearchMarket intelligence
Salary, supply and competitor reads produced to answer a specific decision, delivered with the method attached so you can judge how much weight it carries.
Read more →The product
The gap between a signed offer and a first day.
A candidate signs, then disappears into a notice period. In the United States that gap is often two to four weeks. In India it is commonly thirty to ninety days. Nothing in the applicant tracking system is designed for that window, so most teams manage it with a spreadsheet and a hopeful email.
- 01A joining feed the candidate actually opens, built from material their employer approved.
- 02Engagement signals that need two or three corroborating events before anyone is flagged.
- 03Bands and reason codes rather than a probability score, because a number invites a shortcut.
- 04No automatic deprioritization. A flag starts a conversation. It never quietly deranks a person.
Names and dates are placeholders. The product name is not final, so the platform sits at its own address until it is.
How an engagement runs
Four stages, and one of them is subtraction.
Read the process that exists
Before any tooling conversation, we watch the current process end to end and write down where time actually goes. Almost every engagement finds at least one step that exists because someone left in 2021.
Decide what should not be automated
The list of things a model should not decide is written before the list of things it will help with. Rejections, escalations and anything a person will later have to defend stay with a person.
Build or train, and say which
Some problems are software. Most are habits. We do not dress a training need up as a platform purchase, because that is how a team ends up with a tool nobody opens.
Hand over with a measurement attached
Every engagement ends with a number the client can keep watching without us. If we cannot name that number at the start, the engagement is not well defined yet.
A single risk score attached to a person invites the reader to skip the reasoning and act on the number. Our engagement system requires two or three corroborating signals, shows reason codes with every flag, and never deprioritizes a candidate automatically. That decision came from an advisor who has watched scoring systems in staffing at scale.
Questions
Including the awkward ones.
Is the platform available now?
No. It is in build, and the pages here describe what it does rather than claiming it ships today. The product name is not final either, which is why it lives at its own address instead of taking a name we would have to change.
Do you resell AI tools?
No. Pillar two either builds something, teaches a team to use something, or assesses a market, and says which of the three it is doing. Taking a margin on a recommendation would make the recommendation worth less.
What does the AI training actually cover?
Sourcing and screening workflows, candidate communication, where models produce confident errors, verification habits, and which decisions should stay with a person. Prompt tours age within a quarter, so the material is built around judgment instead.
Will you work with our existing applicant tracking system?
That is the intended integration point, through webhooks rather than a rebuild. The exact systems supported at launch are [to confirm], and we would rather leave that blank than list a system we have not tested against.
The other three
Running in parallel, not in sequence.
Start somewhere
Bring the process, not the tool shortlist.
The useful first conversation is about where your hiring process loses time, not about which vendor to sign.