hansei is becoming a small but sharp stack. ronin handles CV output. signals handles semantic retrieval. the deployment model keeps ownership with the client.
CV reformatter automation built for recruitment teams that want speed, consistency, and cleaner output.
ronin takes incoming CVs and turns them into standardized, recruiter-ready documents. It is built for the real agency workflow, not for a fake demo flow.
The first win is operational. Teams get cleaner data and cleaner output. That sets up the second win later. Search, reuse, and insight become possible because the pipeline stops producing junk.
Semantic search over recruiter archives. Built around how recruiters actually remember candidates.
Legacy search is mostly fields and keywords with AI garnish on top. signals is aimed at the harder problem. Find the right person from messy historical data using natural language.
Recruiters remember fragments. The guy with the dog. The bilingual PM who almost moved. The strong infra candidate from last year. signals is being built around that reality.
This is part of the product. Not just the delivery method.
Each deployment can run on the client’s own VPS. That gives cleaner compliance, clearer ownership, and less long-term dependency.
Workflows are designed to be maintainable and practical. You buy the system. You do not rent permission to use it.
Start with one workflow. Add more over time. CV formatting first. Search next. Other recruiter automations after that.
hansei is not for everyone. That is a good thing.
