Pulse Recruit is what happens when you build the same recruiting system by hand often enough to stop doing it by hand.
RecruiterGTM runs done-for-you go-to-market and automation engagements for recruiting agencies. The work is unglamorous and specific: sit with a desk, find out where the pipeline is leaking, and build the thing that stops it.
After enough desks, the pattern stopped being a coincidence. It was the same three problems every time. Pipeline that goes quiet and nobody notices until a candidate has taken another offer. Follow-ups that live in one recruiter's head and slip the week they are busy. A shared task list that does not exist, so the answer to "who is chasing the client on this one" is a Slack thread and a guess.
We built the same fixes over and over, tuned slightly differently each time, in whatever tools that agency already had. That is a bad way to solve a problem three dozen times. So the systems got pulled out of the engagements and rebuilt properly, once, as software.
That is Pulse Recruit. It is not a general-purpose CRM with a recruiting template on top. Every screen in it started as something a real desk needed on a real Tuesday, which is why the cold-spot signal is on the board rather than in a report nobody opens, and why the import is designed around the messy CSV your current ATS actually exports.
We still run those engagements. That matters more than it sounds: the roadmap comes from watching recruiters work, and a bug reported in the morning is usually a deploy the same day.
Three commitments, chosen because you can check all three without trusting us.
The testimonials page ships with no testimonials on it, because no founding agency has said anything yet. When they do, their words go there. Until then it says so plainly rather than filling the space.
See it for yourselfWhen the assistant cannot answer, it says it cannot answer. A run that found nothing reports nothing, a provider error shows the real reason, and the credits are refunded. It is never allowed to produce a confident answer it did not ground in your data.
Access is enforced by row-level security in Postgres, not by which screen you happen to be looking at. A query cannot return another agency's records even if something in the application asks it to.
Two people. Not a stand-in for a bigger number: two is the number, and both of them are on your pilot.
Daniyal Aziz
Builds the automation and data systems behind every RecruiterGTM engagement, and the Pulse Recruit platform itself.
Reyhan Khan
Sets the direction and leads client delivery, turning every agency's live pipeline on Pulse into real placements.
Short, because the product is young. Dated, because a milestone without a date is a mood.
The first migration landed and the product stopped being screens over an in-memory store. Candidates, pipelines, companies and tasks became real Postgres tables with row-level security written in the same migration.
Terms agreed with each founding agency, monthly only, and no refunds. Including the answers that are not flattering, because a customer finding out later is worse than reading it here.
Ten desks running their real pipeline on Pulse, with a direct line into what gets built next. It is a cap we set, not a count of who has joined.
Pulse Recruit is built and operated by RecruiterGTM, and funded by that agency work. There are no outside investors, so there is no backers section on this page.
Import what you have today and watch Pulse tell you which candidates have gone quiet.