Writing a White Paper on Agentic AI in HR, Ahead of a Product Launch

One of India's top five recruitment process outsourcing firms recently launched a proprietary platform built around agentic AI, giving hiring managers a single connected layer of intelligence instead of a pile of disconnected AI tools scattered across the hiring funnel. Before that platform launched, the client needed a white paper laying out why this shift matters now. We wrote it. The paper had to stand on its own, built from published research and direct conversations with the client's own leadership, without leaning on a product that hadn't shipped yet.

Building a Framework From Scratch

A continuous, agentic AI platform for hiring simply wasn't a category with an existing body of writing behind it. There was no comparable report to study, no established structure to borrow. We had to build the paper's spine from first principles: what agentic AI actually means in an HR context, why point solutions fall short, and where the industry is headed, all argued from evidence rather than assumption.

The objectivity requirement raised the difficulty further. Since the client's platform hadn't launched at the time of writing, we couldn't cite it as proof of anything. Every claim about where the market was moving had to hold up on published research and outside data alone, so the paper would read as an independent argument, not a pitch wearing a research hat.

Getting real access to the client's expertise added a third layer. The people we needed on the record had spent over twenty years each in the industry, and their calendars were packed. Every interview slot was a single shot worth getting right, so we came in with sharp, specific questions instead of using the time to figure out what to ask next.

Chasing a Target That Kept Moving

Early drafts read too much like a management-consulting report: dense, formal, more impressive than readable. The instinct wasn't wrong exactly, it just came from a brief that hadn't fully settled. The client was still working out their own thinking on the platform and the market case for it while we were writing, so the direction shifted after nearly every round, not from mixed signals but because their position was still forming in real time on their side. We stopped treating the early drafts as a fixed brief to execute and started treating them as a working document the client could react to and sharpen.

Keeping a 5,000-Word Piece Moving in Three Weeks

The paper ran to roughly 5,000 words and had to move from brief to delivery in two to three weeks, handled by a writer and an editor in tight lockstep. Given how often the direction shifted, that closeness mattered more than adding hands to the project. Drafts went back to the client section by section, not just at the end, so a change in direction surfaced early instead of after a full draft was already built around the old one. New ideas that came in mid-project got folded into whatever section they belonged in rather than triggering a rewrite, which is the only reason the timeline held.

Review, in practice, looked less like a fixed number of rounds and more like a running conversation. The client kept surfacing fresh angles even after earlier sections had already been signed off, and each addition had to earn its place against the paper's central argument so the piece didn't drift into a loose collection of ideas.

Pushing Past the Easy Version

Early on, the client wasn't ready to commit time to interviews, so the first working draft leaned on a strong stack of published reports and white papers from established firms. It was solid research. It also wasn't enough. A paper carrying the weight of a client with two decades of collective expertise needed to say something only they could say, not repackage what other firms had already put out into the world. We pushed for real interview access and specific, SME-level input instead of settling for a well-cited but generic overview. That push is the difference between a competent literature review and a paper that actually sounds like the client's own point of view on where the industry is going.

Midway through, the client asked us to help build their internal AI hiring matrix alongside the paper, a request that landed outside the original scope. Turning it down would have meant handing over a paper disconnected from the framework the client was building internally at the same time, so we brought it into the engagement rather than treating it as separate work.

What This Means for You

A brief that keeps changing isn't a sign something's gone wrong. It's often a sign the client is still doing real thinking, and the work is happening in step with them. What matters is whether your partner pushes back at the moments that count, in service of what you're actually trying to say, rather than agreeing to everything to keep things smooth. In this project, that meant holding out for direct access to expertise instead of quietly shipping something safer and easier to write.

FAQs

How do you write a white paper about a product that has not launched?

By not citing it. The platform had not shipped at the time of writing, so every claim about where the market was moving had to hold up on published research and outside data alone. The paper reads as an independent argument rather than a pitch, which is what made it usable ahead of the launch.

What do you do when the brief keeps changing?

Treat the early drafts as a working document rather than a fixed brief. The client was still forming their own position on the platform while the paper was being written, so direction shifted after nearly every round. Sections went back for review individually rather than only at the end, so a change surfaced early instead of after a full draft had been built around the old direction.

How do you get usable input from senior people with no time?

Come in with sharp, specific questions rather than using the interview to work out what to ask. The people needed on record had over twenty years each in the industry and every slot was a single shot, so the preparation had to carry the session.

Is well-sourced research enough for a client white paper?

No. The first working draft leaned on published reports from established firms. It was solid research and it was not enough, because a paper carrying a client's own expertise has to say something only they can say. Pushing for real interview access is the difference between a competent literature review and a paper that sounds like the client's point of view.