A client can not fix a resume they can not see the way a parser sees it. Run their CV through the same extraction a real ATS performs, score it against the job they are actually applying for, and turn the gap into a specific, honest list of changes.
The three complaints we hear most from teams in this seat.
Usually the resume never reached a human, and nobody can tell the client which part failed.
Two-column layouts, tables and header contact details break parsers, but which one broke this one?
Generic rewriting tools cheerfully add employers and metrics the client never had, which is worse than useless.
Four steps, none of which involve reading a CV that was never going to fit.
Upload the client's resume and show them the structured record that comes out — including what came out blank.
Resume ↔ JD compares the CV to the actual posting and lists the keywords that are missing.
Resume Builder anchors every ATS issue to the line that caused it, so the client sees cause and effect.
Rewrites are checked against the client's own resume first — invented employers, skills and metrics are blocked, not published.
Being able to show a client the blank fields is the whole coaching session. They stop arguing about fonts.
Start with these; the rest of the pipeline is there when you need it.
Bring a handful of real CVs and one open requisition. Ten minutes is usually enough to tell whether this fits how you work.