fynk vs Tomorro.

fynk and Tomorro, the French CLM formerly called Leeway, are both European contract management platforms that draft, negotiate, approve, sign and track in one tool. They differ in which signature levels are native, how the AI is metered, who pays for a seat and whether you see a price before the sales call. Compared across contract management, AI, signatures, hosting and cost.

By Felix Scholz, fynkLast reviewed
fynk

fynk

Contract management with e-signature and an AI assistant built in.

Founded
2022, Vienna
Category
CLM plus e-signature
Hosting
European Economic Area (AWS)
Signature levels
SES, AES, QES
Pricing model
Per user, unlimited documents
Best for
European teams that want contracts, AI and eIDAS signing (up to QES) in one system with transparent per-user pricing

Tomorro

French AI-native CLM that covers drafting, negotiation, approval, native signing and tracking in one tool, with the Oro AI assistant built in.

Founded
2019, Toulouse
Category
Contract management
Hosting
EU (Paris)
Signature levels
SES; AES/QES via DocuSign
Pricing model
Per creator seat
Best for
in-house legal teams at mid-sized European companies that want a French or EU-hosted CLM and pay only for contract creators

Choose fynk if

  • You need AES or QES and do not want a second signing vendor for it.
  • You want to see the price before the sales call, and start on a free plan or a 14-day trial.
  • You would rather pay monthly than sign a 12-month commitment.
  • You want AI credits allocated per user instead of one shared pool for the whole team.
  • Your AI agents should draft and move contracts, not only read their metadata.
  • You want to set up yourself in minutes rather than schedule a rollout.

Choose Tomorro if

  • Many colleagues only read contracts, and viewers and counterparties should never cost a seat.
  • Your team works in French or Spanish as well as German and English.
  • You already run DocuSign for AES and QES and want contract management on top of it.
  • You want AI review to start from standard playbooks shipped in French, English and German.
  • You want production data hosted in France, with backups in Frankfurt.
  • You would rather have the vendor's team migrate your contract archive for you, as a paid service.
Feature by feature

fynk vs Tomorro: the full comparison.

Grouped by the areas that decide these deals. Where a feature exists but is capped, in beta, or needs another vendor, it is marked partial.

CapabilityfynkTomorro
Contract lifecycle
Central repositoryYes (Document hub)Yes
Templates with locked clausesYesYes
Redlining and negotiationYesYes
Approval workflowsYesYes
Renewal and deadline trackingYes, with remindersYes
AI
Metadata extraction on import Both meter AI in monthly credits: fynk per user, Tomorro as one pool shared by the team.Yes, AI-poweredCredit-capped
Ask questions across the repositoryYes (AI assistant)Yes (Oro chat)
Review against your playbookYes, custom playbooksIncluded (Oro)
MCP server for AI agentsYes, from EssentialBeta, read-only
Signatures
Signature levelsSES, AES, QESSES native
Qualified electronic signature (QES)YesVia DocuSign
Signing orderYesYes
Security and commercials
EU hosting by defaultYes (EEA)Yes (France)
ISO 27001YesCertified
Public APIBusiness plan and upREST API
Interface languagesGerman, EnglishFrench, English, Spanish, German

Each cell is checked against the vendor's own public pages. Links and check dates are in the references below.

Where fynk and Tomorro actually differ.

Qualified signatures: native or through DocuSign.

Tomorro’s native signature is a simple electronic signature, included in all its plans and legally binding. For advanced and qualified signatures it offers a DocuSign integration, which needs your own DocuSign account, and its signature order works only with the native signature, not through DocuSign. fynk has SES, AES and QES on every plan, Free included, with no separate signing licence. If simple signatures cover your contracts, or DocuSign is already paid for, this difference costs you nothing. If they do not, fynk wins this one.

What to do with that

If any of your contracts need AES or QES, add a DocuSign subscription to the Tomorro quote before you compare totals.

Who pays for a seat.

Tomorro charges only for Administrator and Creator roles. Internal viewers and counterparties are free and unlimited. It publishes no prices: the contract management plans are sold by quote, billed annually, with a 12-month commitment. fynk prices per user, from €19 per user per month on annual billing or €29 monthly on Essential, with unlimited documents under a fair use policy. A team with a handful of contract creators and a large read-only audience is the case Tomorro’s model is built for, and that one goes to Tomorro. A team that wants to budget before talking to sales, or pay monthly, goes to fynk.

What to do with that

Count the people who create contracts and the people who only read them, then ask Tomorro for a quote on its Scale plan and set it against fynk's published per-user price.

How the AI is metered.

Both products run AI on monthly credits, so neither is unlimited by default. Tomorro allocates one pool per company and shares it across the team: 50 credits a month on Pro, 150 on Scale, 250 on Enterprise. Each field Oro fills during extraction costs a credit, each chat message costs one, and once the pool is spent Oro’s features are temporarily blocked unless you have bought the unlimited upgrade through your Customer Success Manager. fynk allocates credits per user: 50 on Free, 150 on Essential and 250 on Business, so the allowance grows with the team. Heavy use can still run through it. For bulk extraction across a multi-user team, fynk’s model stretches further; for a small team of creators, the difference is smaller.

Contracts your AI tools and systems can reach.

Tomorro’s MCP server is a read-only beta: its tools read contract metadata, counterparties, templates and clauses, but not document content, and they make no changes. Its public REST API covers contracts, templates, clauses, counterparties and webhooks, and carries an alpha version label. fynk ships an MCP server from the Essential plan whose tools can search the repository, draft from templates and move contracts forward. fynk’s REST API and webhooks, however, start on the Business plan, while Tomorro does not publish which of its plans include the API, so ask when you get the quote. For AI agents, fynk goes further today; for a plain REST API on fynk’s entry plan, the answer is no.

Cost model

Tomorro pricing vs fynk pricing as you grow.

Entry prices as checked, and the mechanics underneath them, which matter more than the headline number.

What you pay forfynkTomorro
Pricing modelPer user, unlimited documentsPer creator seat
Entry priceFrom €19 per user/month (annual)On request
Billing and commitmentMonthly or annualAnnual, 12-month commitment
Contract management and signingCLM and signing in one planIncluded
AI credits150 per user per month150 per month, shared by the team
Free planYes, 1 userOro AI only
Free trial14-day free trialOn request
Where the bill growsWith headcountWith creator seats, AI use beyond the pool, and DocuSign for AES or QES

fynk Essential, its lowest paid plan, per user per month billed annually, against Tomorro Scale, the plan a mid-sized team would realistically buy. Tomorro publishes no contract management prices, so its cells describe the mechanics only. Ask both vendors to quote your real headcount.

In practice

Switching from Tomorro to fynk in practice.

Tomorro documents its exports clearly, so the data rarely holds up a move away from it. The timeline is set by the 12-month commitment, by colleagues who never needed a paid seat, and by the playbooks and CRM flows your team built inside Tomorro.

Work back from the Tomorro renewal date.

Tomorro bills annually on a 12-month commitment, so the renewal date is the real deadline: finish the move before it, or pay for a year you will not use. If you added DocuSign for AES or QES, check that contract’s term too. fynk signs SES, AES and QES on every plan, so the DocuSign subscription may become unnecessary, and both renewal dates are worth lining up before you start.

Take the data, the signed files and the certificates.

On Pro, Scale and Enterprise, Tomorro exports contract data to Excel from the repository or a filtered view, and signed contracts download in bulk. For a large archive, the public API exposes contracts, signed files and metadata, so the transfer can be scripted. Check that every signed PDF leaves with its signature certificate, including contracts signed through the DocuSign integration, and compare the counts before the account closes. In fynk, each imported contract is read and its parties, dates, values and key clauses come back as fields. That draws on AI credits per user, so a large archive can use up a month’s allowance: import it in stages or plan a top-up.

Colleagues who read for free in Tomorro.

The people who feel the switch first are the ones Tomorro never charged for: it bills only Administrator and Creator seats, and internal viewers are free and unlimited. fynk bills every user, from €19 per user per month on annual billing, so a legal team of four plus forty colleagues who look contracts up makes a very different budget in each tool. List who needs to open contracts themselves before the rollout, because that list sets the fynk bill.

Playbooks and CRM flows are rebuilt, not moved.

Tomorro’s AI review runs on playbooks of standard positions, fallbacks and exceptions. Ask Tomorro whether yours can be exported; if not, copy the positions into a document before you leave, because fynk reviews against playbooks you define and they have to be set up again. The same goes for the Salesforce and HubSpot integrations that create contracts from CRM records and write contract data back. In fynk, the Salesforce and Pipedrive connectors start on Essential, but native HubSpot, the REST API and webhooks need Business, so a HubSpot team should price Business.

When staying with Tomorro is the better call.

If most of your users only read contracts and would each need a paid seat in fynk, if your team works in French or Spanish, or if your playbooks and Salesforce or HubSpot flows in Tomorro already work, the migration costs more than it returns. In those cases the sensible move is to stay with Tomorro and ask the question again at the next renewal.

"Don't underestimate the value of modern, intuitive usability. People say it's so nice to work with. It actually makes contract work fun. That makes adoption faster and that's why we trust fynk for our contract workflows across the whole company."

Elisa Prößdorf Legal Solutions Manager at Unite
References

Where these figures come from.

  • fynk [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]
  • Tomorro [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24]

Spotted a figure that has moved? Tell us at [email protected] and we will re-check the row.

fynk vs Tomorro: frequently asked questions.

  • For contract management with signing, yes: both cover drafting, negotiation, approvals, a repository with reminders and e-signature. The differences are commercial and in the details: fynk has AES and QES natively, Tomorro charges only for creator seats and offers French and Spanish interfaces.

  • Tomorro (formerly Leeway) publishes no prices for its contract management plans, Pro, Scale and Enterprise, and sells them by quote. The quote follows the number of Administrator and Creator seats, since viewers and counterparties are free, and is billed annually on a 12-month commitment. Each plan includes a shared monthly pool of Oro AI credits (50, 150 or 250), and unlimited Oro is a paid upgrade on top. The €50 a month shown on oro.legal is the price of Oro, Tomorro's standalone AI agent, not of the CLM.

  • It cannot be answered from list prices, because Tomorro publishes none. fynk starts at €19 per user per month on annual billing. Tomorro bills only Administrator and Creator seats, annually with a 12-month commitment, so the answer depends on how many of your users create contracts and whether you also need DocuSign for AES or QES.

  • Not natively. Tomorro's own signature is a simple electronic signature. Advanced and qualified signatures run through its DocuSign integration, which needs a separate DocuSign account. fynk offers SES, AES and QES on every plan.

  • Yes. Tomorro documents an Excel export of contract data on its Pro, Scale and Enterprise plans, bulk download of signed contracts, and a public API that exposes contracts, signed files and metadata. Export everything before the account is closed.

  • Yes. Tomorro was founded in Toulouse in 2019 as Leeway and rebranded to Tomorro in December 2023. A comparison with Leeway is a comparison with Tomorro.

Still have questions?

Compare it against your own contracts.

Import what you signed last quarter and ask fynk a question about it. Faster than any comparison table.