Wag3s vs Liquifi: Token Vesting Specialist or Finance OS

Both help token projects get vesting and token comp right. One is a specialist; one is a stack.

Liquifi is a deep token vesting, lockup, airdrop, and global token-payroll product, with automated vesting distribution, token tax-withholding, and 83(b)-style guidance. Wag3s is a Finance OS where token comp and payroll (HR) sit next to accounting (Ledger), jurisdiction tax (Folio), and treasury. They overlap on token compensation and diverge on the accounting and tax layer around it.

Here's the honest version.

What Liquifi does well

Liquifi is built for the lifecycle of a token grant. It handles vesting schedules, lockups, and airdrops, automates vesting distribution, supports token tax-withholding, and offers 83(b)-style election guidance alongside global token payroll. For a token project whose problem is "administer vesting and token compensation correctly from grant to distribution," Liquifi is a strong, focused specialist.

The vesting-administration depth is the genuine strength: tranche schedules, cliffs, lockups, and the distribution mechanics that are painful and error-prone to run by hand. That is exactly what it was built to do well.

The 83(b) guidance is particularly valuable for US-based token recipients. An 83(b) election — which allows taxation at grant-date FMV rather than at each vesting event — must be filed within 30 days of grant. Projects that issue token grants without flagging this election window routinely cost their team members significant tax on unrealized gains when tokens vest at a higher price. Liquifi surfaces this obligation as part of the grant workflow, not as an afterthought.

Where Liquifi stays focused

Scope choices, not flaws.

It's a vesting/token-comp specialist, not an accounting subledger. It administers grants and distributions; it is not the GAAP/IFRS general ledger that recognizes the IFRS 2 / IAS 19 expense over the service period.

Not a corporate jurisdiction tax engine. Token-withholding is handled at the comp layer; corporate jurisdiction tax forms are a different deliverable.

Treasury and portfolio aren't the focus. It runs token comp; it is not a treasury-operations or portfolio-tax module.

That focus is deliberate — Liquifi decided to own token vesting and comp administration, and it goes deep there.

What Wag3s does differently

Wag3s isn't a vesting tool with extras. It's a Finance OS of modules:

• HR — crypto/fiat payroll, token-comp and cap-table inputs, vesting/cliff data. This overlaps Liquifi.
• Ledger — accounting: feeds the IFRS 2 / IAS 19 expense recognition from grant data; ERP export. A vesting schedule from HR automatically drives the amortized expense recognition entry in Ledger over the service period.
• Folio — portfolio plus jurisdiction tax (cost-basis methods, country forms incl. French FEC).
• Treasury — operational treasury.

Vesting and grant data become accounting inputs automatically. The pitch isn't "Wag3s administers vesting better than Liquifi." Liquifi is a deep specialist; Wag3s is the stack where token comp, the accounting recognition it drives, tax, and treasury share one data layer and audit trail.

The actual comparison

Three concrete scenarios

Scenario 1 — Token project whose whole problem is administering complex vesting and distributing tokens correctly. This is Liquifi's lane; the vesting/lockup/distribution depth is the design point. We'd recommend Liquifi for that focused need.

Scenario 2 — Company that grants tokens and must recognize the IFRS 2/IAS 19 expense in audited books with a French jurisdiction tax workflow. Vesting administration is the input; the accounting recognition and tax outputs are the deliverable. Wag3s HR plus Ledger plus Folio keeps it on one layer (see token vesting & cliff accounting).

Scenario 3 — Project needing token comp, the accounting it drives, treasury, and tax to reconcile on one trail. That combined need is the Finance-OS shape. Wag3s fits it; Liquifi would be the vesting leg beside other tools.

Pricing model comparison

Liquifi is a specialist product with pricing structured around the number of grants under administration, team size, and complexity of vesting schedules. It's appropriate pricing for a product that handles the vesting mechanics that carry real tax and legal consequences. Public pricing is not listed for enterprise tiers; early-stage pricing may be available for smaller teams.

Wag3s HR is one module in a modular Finance OS. Pricing scales with team size and transaction volume. For a project that needs both vesting administration and accounting recognition, activating HR alongside Ledger in Wag3s covers both at a combined cost that is typically lower than Liquifi plus a separate accounting tool. For a project whose vesting administration is highly complex (many schedules, multiple grant types, airdrop mechanics), Liquifi's specialist depth may justify the standalone cost even if you also run Wag3s for accounting and tax.

The practical question is: is vesting administration a one-time setup problem (Wag3s HR can handle it) or an ongoing, high-complexity operational problem (Liquifi's dedicated specialist tooling is worth the cost)?

Migration path: Liquifi to Wag3s HR

1. Export grant data from Liquifi — active vesting schedules (grant date, cliff, tranche schedule, total grant size), distributions made to date per grantee, FMV at grant date, withholding records, and any 83(b) election documentation.
2. Import into Wag3s HR — input each grant as a token-comp entry with vesting parameters. For each grant, Wag3s HR will calculate the remaining expense to be recognized under IFRS 2.
3. Reconcile cumulative recognized expense — verify that the sum of compensation expense recognized to date (from the vesting schedule start through the import date) matches the Liquifi records. This prevents a one-time restatement.
4. Validate cost basis and withholding — confirm that token cost-basis records in Wag3s Ledger reflect the tokens distributed per Liquifi's distribution history.
5. Activate Folio — bring entity-level jurisdiction tax onto the same layer as the payroll and accounting data.

Who should use which

Use Liquifi if token vesting and compensation administration is the problem and you want a specialist that goes deep on schedules, lockups, distribution, and withholding. It is strong there. (Accounting scope and the tax treatment remain auditor- and adviser-confirmed.)

Use Wag3s if token comp is one of several crypto-finance needs and you want vesting data to flow into accounting recognition, jurisdiction tax, and treasury on one Finance OS rather than reconciling a vesting specialist with separate books.

Some teams run a vesting specialist and a separate finance stack. The question is whether vesting should be an island or a module that feeds the books.

Further reading

• Wag3s vs Toku — global token payroll comparison
• Token Vesting & Cliff Accounting — recognising the expense
• Token Compensation Accounting: IFRS 2 or IAS 19? — scope determination
• Wag3s HR — crypto and fiat payroll