For your workHR teams

HR project management that keeps people files careful.

Every open role runs the same recruiting workflow, every policy update has an owner, and Claude drafts the letters, scorecards and summaries. Nothing about a person leaves HR until someone on your team has read it.

A month of Premium free, no cardAgents never take a seat

Sound familiar?

What fills an HR week.

Every hiring manager runs their own recruiting workflow, and I chase all of them.

With ProjectifyOne set of stages for every req, from approved to hired. Claude posts which candidates have waited longest and on whom.

Offer letters sit in drafts while I hunt for the current template.

With ProjectifyFiles reads every template and policy as it arrives. Claude drafts from the latest one, and you check the terms before it goes anywhere.

I worry about what ends up in a shared folder.

With ProjectifyA heads-up flags any file that holds ID numbers or bank details, and you choose who sees each folder. Enterprise runs on your own servers.
What Claude does for hr teams

The admin goes to Claude. The judgement stays with you.

Takes the paperwork off your list

Interview packs, scorecard summaries, job ad drafts and reference questions: Claude takes the next ready task, claims it and hands it back for review.

Interview pack for the data analyst role is ready for Amara.

Runs every req the same way

Record how you open a role once. Projectify turns it into a workflow with checks where HR and the hiring manager sign off.

Support lead req: 5 of 7 steps done, the job ad waits for you.

Knows the handbook

Policies, templates and the handbook are read when you add them, so anyone can ask what the leave policy says without opening five versions.

Handbook v4: notice period is one month after probation.

Stops where HR must look

A letter, a summary or a policy change from Claude waits in Approvals until a person reads it. Every change is signed and can be undone.

Offer letter for the designer waits for Amara’s check.
Your board, shaped for hr teams

Start from a sentence. Keep what fits.

Say what the project is for and Claude drafts it: the statuses, fields and views below, ready to rename, switch off or add to.

Statuses

RequestedApproved to hireSourcingInterviewingOfferHiredClosed

Fields

RoleHiring managerDepartmentLocationTarget startStage owner

Views

BoardTableCalendarFormDashboard
  1. Intake with the hiring manager
  2. Job description from the notes
  3. HR checks the wording (a person checks)
  4. Interview plan and scorecard
  5. Req logged on the board
  6. Hiring manager signs off (a person checks)

Open a new role, as a workflow. The clay steps stop for a person. How workflows work

Questions

Before HR moves anything over.

Is it safe to keep candidate and employee files here?

A heads-up warns when a file holds ID numbers or bank details, and you choose who sees each file or folder. Files can live in your own S3 or R2 bucket, and Enterprise runs on your own servers with single sign-on.

Will Claude make hiring decisions?

No. Claude drafts summaries, letters and checklists, and a person makes every call and signs off before anything leaves HR. Every change is signed “Claude for” the person who ran it and can be undone.

Can managers send hiring requests through a form?

Yes. A Form view turns each request into a card on the board, with the role, department and target start you ask for.

Does it run payroll or track leave?

No. It holds HR’s projects and the work around them; keep payroll and leave in the systems built for them.

Give HR a teammate that never skips a check.

A month of Premium free, no card, and your next open role set up today.