DeltaFlow is an offer and onboarding management platform. Draft with structured comp, route approvals automatically, and send an interactive branded offer page — live vesting, equity, full breakdown — instead of a PDF. When they accept, onboarding starts itself.
What you can do in DeltaFlow
A hire decision fans out into comp, approvals, equity, onboarding and vendors — all at once. DeltaFlow keeps every stream moving so nothing stalls and nothing gets lost.
A Kanban pipeline of every active candidate. Stage, candidate ref and escalation warnings at a glance — the board updates itself as approvals complete.
Candidates get a personalised, branded page — vesting graph, equity visualiser, comp breakdown and an acceptance form. Not a PDF attachment.
Chains configured per org. Approvers get a token link — no login. Stale steps auto-escalate.
A guided form: role → compensation → equity → letter preview. Structured fields only, so there is no version confusion and no second draft.
On acceptance the record hands over to People Ops: tasks, documents and start date.
Reports, requisitions and a hiring organiser across every open role — plus a scoped task view for background-check and logistics vendors, so the People team stops chasing them over email.
Four surfaces your team lives in, rendered exactly as they ship.
Base, bonus, equity units, vesting, jurisdiction, start date — captured as structured fields. Guarded fields can't be typed over, so the packet assembles from one source: letter, equity schedule, benefits summary, addendum.
Submitting routes it to the first approver in your chain and sends them a secure link — they decide without an account. If a step goes quiet, it escalates on a timer you set.
Internal approval hands off to the final approver. Rejection carries a written note by default, and reopening walks the record back one step rather than starting it over — the history behind it stays intact.
Final approval sends the offer and freezes a copy of exactly what was approved, in a single step, so what the candidate sees can't drift from what was signed off. They get a link to a branded offer page — not a PDF attachment.
The offer room records the decision, the signer, the timestamp and a tamper-evident fingerprint of the exact document they were shown. Views, questions and counter-asks are events on the same packet, not a thread in someone's inbox.
Accepting creates the employee record — matched on email address, so a double-click can't create two employee records. The onboarding journey runs against that record: tasks with owners and due dates, and a preboarding portal on its own link.
Multi-tenant from the ground up — so onboarding a new organisation is configuration, not a migration.
Recruiters, hiring managers, approvers and finance all get access. You pay for the people you employ, not for everyone who needs to open an offer.
Teams hiring their first hundred.
Organisations whose offers have to survive an audit.
Your tenancy, your keys, your retention policy.
The spreadsheet the comp model lives in, the doc the offer letter is drafted in, the Slack thread the approvals get chased in, and the PDF the candidate receives. It sits alongside your applicant tracking system rather than replacing it — most teams keep sourcing where it is and start at the moment a hire decision is made.
A secure link to a branded, interactive offer page — not an attachment. It shows the full compensation breakdown, an equity vesting graph they can read, and an acceptance form. No account, no download, no PDF viewer.
Each approver gets a token-authenticated link. They see the offer, leave a note, approve or reject — no login required. Steps that go stale escalate automatically, and every decision is logged with who, when and what they wrote. An amendment re-runs the chain from the right step without losing the history behind it.
The record hands over to People Ops: onboarding tasks with owners and due dates, document collection, start date and equipment. External vendors — background check, logistics — get their own permission-scoped task view, so status comes back on its own instead of being chased over email.
Yes — it was built multi-tenant from the start rather than hardcoded for one company. Every record carries its organisation, approval chains and branding are per-org, and the operator console manages tenants, plans and invitations. Adding a company is configuration, not a migration.
A single Go binary that serves both the API and the interface — one image, one origin, migrations applied on boot, backed by PostgreSQL. It runs on any container host, or inside your own network.
Ask us to walk your real offer flow end to end — draft, route, send, sign, onboard — in about thirty minutes.