Skip to content
Sayl

HR & People Operations

Partly available

Your org chart already knows who works here. HR is what we are building on top.

Employees, departments, reporting lines and bulk onboarding ship today and are what the CRM's own access model runs on. Attendance, leave, payroll and appraisals are designed against that same record and are not finished — so this page tells you which is which, step by step.

Part of this product is live. Part of it is not.

The employee record is live today — directory, departments, reporting lines and bulk onboarding. Attendance, leave, payroll and appraisals are in development.

Employee records — liveOrg chart & departments — liveBulk onboarding — liveAttendance, leave, payroll — in development
crm.sayl.in
Live

Organization

Updated just now

This week
MI

Meera Iyer

Director

RK

Rohit Kumar

Sales manager

SN

Sneha Nair

Executive

TJ

Tom Joseph

Executive

AK

Aisha Khan

Marketing lead

VD

Vikram Das

Executive

Rohit sees 34 leads. His own, plus his two reports’. The totals on his dashboard are the totals of those 34 — an aggregate leaks a record just as easily as a list does.

The employment lifecycle

Where the product stops and the plan starts.

Seven steps from hire to exit. The first two and the last are live today; the four in the middle are marked, and marked is not the same as shipped.

Who does what:Your teamSaylIn development

0107Your team

A new joiner becomes a record, one at a time or a spreadsheet at once

Name, employee code, title, department, employment type, joining date, work location and reporting line. Import validates the file and the existing database together before anything is written.

Happens on /organization in the product

  • Import runs three validation passes over the file and the database as one graph, then shows a preview. The commit is all-or-nothing — a half-imported org chart with dangling reporting lines is worse than a failed import.
  • Reporting lines are cycle-proof: two people cannot end up as each other's manager, however you approach it.

Available today

What you can actually use, and what you cannot.

No hedging and no asterisks. The left column works right now. The right column does not, and nothing on this site will imply otherwise until it does.

Live today

  • Employee records with code, title, department and employment type
  • Joining and exit dates, work location and contact details
  • Cycle-proof reporting lines and an org chart
  • Bulk onboarding from Excel or CSV, validated before commit
  • Departments and teams, with a named head
  • Deactivation that preserves history rather than deleting a person

In development — not available

  • Attendance and shift tracking
  • Leave types, balances, requests and approvals
  • Payroll input export and pay-cycle reporting
  • Appraisal cycles, goals and review records
  • Document storage — contracts, ID, certifications
  • A self-service portal for employees

In the product

What is planned, and what already works.

One employee identity

The person in the org chart, the CRM user who owns leads, and the manager whose visibility covers a team are one record — not three that have to be kept in step. Live today.

Bulk onboarding that refuses to half-finish

Excel or CSV, validated against the file and the database together, previewed, then committed all-or-nothing. Live today.

Departments, teams and heads

Structure that both the chart and the lead-routing rules read from, so distribution follows the organisation rather than a second list of names. Live today.

Employment details on the record

Employee code, employment type, joining and exit dates, work location and personal contact — the fields an HR process needs, already captured. Live today.

Attendance and leave

Shift tracking, leave types and balances, and approvals routed along the reporting line already stored on the record. In development.

Payroll inputs and appraisals

A pay-cycle export for the payroll system you already run, and review cycles recorded against the employee. In development.

Where each step actually happens

These are real screens in the product, not stages in a diagram. You can be looking at every one of them on day one.

See the whole platform map

Onboard

A new joiner becomes a record, one at a time or a spreadsheet at once

Directory

The organisation is browsable, and it governs access

Exit

Someone leaves, and the history survives them

Straight answers

What this does not do

Every one of these is a real constraint — some ours, some the upstream platform's. They are on this page so you find them now rather than after you have paid.

Half of this page is not built yet

The employee record, org chart, departments and bulk onboarding are live and in daily use. Attendance, leave, payroll inputs and appraisals are designed and not shipping. We would rather show you the roadmap honestly than sell you an HR suite and hand over a directory.

Payroll will be an export, not an engine

Even when it ships, the intent is to produce inputs for your existing payroll system rather than to calculate statutory deductions and file returns. That is specialist, jurisdiction-specific, and carries obligations we are not going to pretend to absorb.

There is no employee self-service portal

Today everything is managed by whoever holds the permission. A portal where staff apply for leave and view their own records is part of the same roadmap, not a separate thing you can buy sooner.

Questions

Before you ask

Can we use the HR features today?

You can use the employee directory, org chart, departments and bulk onboarding today — those are live and are what the CRM's access model already runs on. Attendance, leave, payroll and appraisals are not available.

Will we have to re-enter our people when the rest ships?

No. That is the reason this is being built on the existing employee record rather than beside it. The people, departments and reporting lines you set up now are the same rows the later modules read from.

How is this different from People, Roles & Access?

People & Access is about what someone can see and do inside the CRM. HR is about the employment relationship — attendance, leave, pay, reviews. They share one employee record, which is why setting up one sets up the other.

When will attendance and leave be ready?

We are not going to put a date on this page that we might miss. Ask on the call and you will get our current honest answer, including what it depends on.

Ready when you are

See HR running on your own process.

Bring a real example — an enquiry that got lost, a quote that took three days, a campaign nobody could measure. We will walk it through the actual product.