Gloat is now Synq.Read why

synq

Say how HR should work.
It's built.

Describe it in plain language, and Synq builds it — then runs it. No IT, no implementation project.

Most HR systems resist change.

A change means a ticket, a consultant, a roadmap — and a wait measured in quarters.

Synq works the other way. Describe the change you want, and it's built, governed, and live in minutes — by your own team, not a vendor's.

From a sentence to a live capability

1

It asks what it needs

A few plain-language questions — who it's for, what it does, where the data comes from — so it builds the right thing, not a guess.

2

It shapes the data

New fields, records, and relationships land in your data model on the spot — no migration, no schema to design, nothing for IT to set up.

3

It wires the logic

The workflow and the agent that runs it — the steps, the actions, the approvals — assembled and shown to you before anything moves.

4

It sets the guardrails

Access controls, approval routing, and an append-only record, built in. Approve once and it's live — doing the work, within your rules.

Describe it in plain language. Synq builds it.

New capabilities, or changes to what already runs — described in plain language and built by your own team. It's the work #HRBUILDERS do.

Add a Day 30 onboarding check-in
Create a referral-bonus workflow
Spin up an engagement pulse
Add a 'notice period' field
Build a new-manager dashboard
Draft a parental-leave policy agent
Add a Day 30 onboarding check-in
Create a referral-bonus workflow
Spin up an engagement pulse
Add a 'notice period' field
Build a new-manager dashboard
Draft a parental-leave policy agent
Raise the PTO approval threshold
Lock comp fields to managers only
Require VP sign-off on rating overrides
Change onboarding for EU new hires
Reroute approvals to HR partners
Rename a job family across the org
Raise the PTO approval threshold
Lock comp fields to managers only
Require VP sign-off on rating overrides
Change onboarding for EU new hires
Reroute approvals to HR partners
Rename a job family across the org
Run the Q3 review cycle
Flag certifications expiring soon
Add a step to the exit process
Make leave rules region-specific
Turn a policy doc into answers
Auto-nudge late reviewers
Run the Q3 review cycle
Flag certifications expiring soon
Add a step to the exit process
Make leave rules region-specific
Turn a policy doc into answers
Auto-nudge late reviewers

Everything you build stays governed.

It keeps your access controls

Every capability you build inherits your field-level permissions. Comp stays visible to HR and a person's own manager, masked for everyone else — Synq answers and acts only on what the asker is allowed to see.

See the trust layer
Field accessInherited by every build
EmployeeManagerHR
CompensationReadNoneEdit
Home addressEditNoneRead
Performance notesNoneReadEdit
Right-to-workReadNoneEdit

Deny-by-default — everything you build acts only on the fields the asker may see.

Nothing ships until you approve

Synq drafts the change and shows you the before and after. Sensitive moves route for sign-off first. You decide what goes live and when — and you can roll any change back.

How it works
Proposed changeDraft
Before

Referral bonuses pay out on the referred hire's start date.

After

Referral bonuses pay out once the hire passes their 90-day probation.

DiscardApply
SynqDrafted by Synq Routed to Dana Keller

Nothing goes live until you approve — and any change rolls back.

Every change is on the record

Each build and edit lands on an append-only, signed record — who asked, what changed, and the policy behind it. The audit trail is written as the work happens, not reconstructed later.

Explore the record
Activity
SynqSynq · append-only, signed
WhenChangeStatus
09:12Built the referral programBuilt
09:12Routed payout rule for sign-offPending
MonAdded a 'notice period' fieldApplied
MonLocked comp to HR and managersSigned off

Who asked, what changed, and the policy behind it — written as the work happens.

Ask what you've built, and how it's landing

Everything you stand up with Synq is live and queryable the moment it ships. Ask across your own builds, your team's adoption, or the whole company — and get the chart, not a report to chase.

What you've built
Builds by share of runs

The onboarding flow leads the pack.

Onboarding flow
38%
Referral program
24%
PTO approvals
19%
Comp-review agent
12%
View as table
Which of our builds get used most?
Across your team
Onboarding flow · adoption

Climbing steadily since it shipped.

92%of new hires
up from 40% at launch
JFMAMJJASOND
View as table
Is the onboarding flow we built catching on?
Across the company
Everything you've built

Workflows are most of what you've shipped.

48builds
Workflows 40% Fields 25% Rules 18% Agents 10% Reports 7%
View as table
What have we built with Synq, by type?

Things worth knowing

No. Anyone on HR describes what they want in plain language — in Slack, Teams, or the web console — and Synq builds it. No code to write, no ticket to file, no engineers or implementation partner in the loop.

New workflows, fields, reports, approval rules, and agents — and the behaviour of anything already running. Onboarding steps, review and comp cycles, time-off logic, a people-analytics answer: if you can describe how HR should work, Synq can build it.

Minutes, not quarters. There's no implementation project and no blank schema to set up. You describe the change, Synq shows you the before and after, and the moment you approve, it's live — no release train to wait for.

Yes, by default. Every capability inherits your access controls and policies — field-level visibility, approval routing on sensitive changes, and an append-only, signed record of every action. Nothing you build steps outside the rules you've set.

You're not clicking through config screens or wiring logic yourself. You describe the outcome and the agent builds it — then does the work, not just stores the setup. The thing you create is a working capability, not another form to maintain.

The new behaviour takes over going forward — no migration, no rebuild, nothing breaks mid-cycle. Synq shows the before and after first, and every change is a reviewable entry you can roll back.

No — it takes the busywork off them. Synq builds and runs the processes HR describes, so your team spends its time on the judgment calls and the people, not on tickets and configuration.