HR module

HR pipeline: from application to first day on the job

Applications from your website and Meta and Google lead forms land in the hiring pipeline, not in sales leads. Interviews go on the calendar, candidates are cards with photos, and hiring adds the employee to the CRM right away.

  • Applications go to hiring, not to leads
  • An interview is a task with a reminder
  • Hiring adds the employee to the CRM
How it works

From application to first day

  1. Applications flow in

    Website form, Meta or Google lead form — the application lands in the job's pipeline along with the answers and UTM tags.

  2. Recruiter knows right away

    The application goes to a specific recruiter or the next one in rotation. Notifications — in the CRM and the Telegram bot.

  3. Interview on the calendar

    Time, format (office, online, phone) and interviewer. A meeting task with a reminder 30 min before.

  4. Hired — already in the CRM

    "Hire": user account, department, mentor and a personnel record with the hiring source.

What it does

Hiring and HR — alongside your business

Jobs with their own pipeline

A shared pipeline or a custom set of stages per job. Department, city, salary range, how many people to hire.

Hiring requests

Internal requests for people: priority, deadline, owner. Turn a request into an open job in one click.

Candidate cards with photos

Experience, expectations, resume and files, comments and history. Custom fields and a city filter.

Hiring analytics

Stage conversion, time to hire, sources, recruiters, rejection reasons, who's stuck.

Staff & mentors

Personnel record, probation period, private HR notes. A mentor sees their mentees' work, read-only.

Plans, tracking & payroll

Monthly plan by position, work log, rewards paid as bonuses. Partial payouts and advances.

Honestly

Key things to know

  • Enabled on request. We turn on the HR module for each company separately; the "Payroll" tab is one more switch.
  • The CRM sends nothing to candidates. An interview is a task for the interviewer; a person sends the invitation to the candidate.
  • Some data is entered by people. The city doesn't come from the form — HR sets it. Employees log their own work.
  • An application doesn't become a lead. Salespeople don't see candidate profiles, and sales automations don't fire on them.

Frequently asked questions

Will an application become a sales lead?
No. An HR source puts the application into the hiring pipeline: no lead, no client, no sales inbox and no automations. Salespeople don't see candidate profiles.
Where can applications come from?
Your website form and Meta and Google lead forms. The source is tied to a job, and the application to a recruiter or round-robin. A repeat application doesn't create a duplicate candidate.
What does the HR role see?
Hiring, staff and tasks. In the developer CRM — also the leads, deals and clients of their mentees, read-only. The head of HR sees the whole company.
Can we get just HR, without sales and projects?
Yes, Briky Build has an "HR only" mode: pipeline, employees, plans, analytics, payroll and tasks. Other sections turn on with one switch, and the data stays in place.
How does payroll work?
It's the "Payroll" tab in "Finance": base salaries, bonuses, partial payouts and advances, payout history and debt from past months. Currencies are never mixed.
We have two CRMs — sales and projects. Will HR be doubled?
No. If you have Build and Build Sales, there's one hiring pipeline for both: each job is marked with the CRM it's for, and hiring adds the person to that CRM.

See the HR pipeline in a demo

We'll show a candidate's path from application to first day, hiring analytics and payroll — and explain how to connect the module.

Get a demo