From pipeline to paid, without re-typing the deal.

When the client accepts the offer, things happen: the contract is created from it, the first payment can be collected on the spot, and the deal record carries all of it. Nobody copies figures from the CRM into a document template and hopes they match. Your Slack says 'Offer accepted. Contract signed. First payment collected.' and every word of it happened in one system.

The price on the accepted tier locks at acceptance: contract, invoice and charge reference the same stored value, so the deal that was agreed is the deal that is billed. The exchange rate on a cross-currency deal is a policy, not a fixed behavior: pin it at acceptance, so the client is billed the figure they saw, or let fiscal documents convert at the statutory rate of the day they are issued, which is what Romanian invoices carry (the BNR rate of the invoice date). Either way, the applied rate is stamped on the document and never silently re-resolved.

The moment a client says yes is the worst moment to start a questionnaire. Here the pipeline gathers what the paperwork will need while the deal advances: party details on country-aware fields (the platform knows what a legal identity requires in 41 countries), each party described to the level the document demands, down to the bank account the money should land in. Anything still missing is named by the contract gate as a checklist, and the document issues itself the moment the last gap closes. Nothing is asked twice. And when it is time to sign, each signer clears a verification level, email, SMS or both, before the contract opens for them.

Tiered offers where the unit price steps down with quantity. Several offers open in parallel, each with its own currency. Payment plans that mix a one-off fee, an intro rate and an ongoing subscription in one schedule. More than two parties on one agreement. The shapes that force other stacks into spreadsheets are just fields here.

Let Enlivy do the prospecting: leads land in one pipeline from your calls, your forms, or a package published in request mode on your own site. Every stage can carry an email you author, per project and per language, sent to the prospect when they enter it. The deal's information starts accumulating from the first hello, so by the time an offer goes out, half the paperwork's inputs already exist.

Keep the prospecting you already have, in whatever CRM or notebook it lives, and enter Enlivy at the moment a deal is real: build the offer, send the link, and let acceptance drive the contract, the invoice and the payment. Nothing upstream is required, nothing is imported first. And because the packs are modular, the same is true further down: contracts without the pipeline, invoicing without contracts, each earning its place on its own.

One schedule can mix a one-off fee, an intro rate and an ongoing subscription. A finite plan carries its installments each with its own amount and date, invoiced and charged automatically when due. Phased pricing steps up or down across stages of the engagement. Subscriptions run on any cadence from weekly to yearly, priced per cadence, with tiers and add-ons in the package itself.

The collection side holds up too: cards are charged off-session and idempotently, so there are no accidental double-bills. A plan change keeps the client's agreed prices to the cent, upgrades charge only the net difference, and the preview equals the charge because it runs the real billing logic. If a card expires, the subscription pauses itself and resumes to collect the balance the moment a working card is added. And billing you already run elsewhere can be mirrored in and kept in sync, so nothing has to migrate first.

Contracts are written from modular chapters and reusable templates, numbered from your own series with your own prefixes. Amendments, supplements and addenda link to their parent contract, so a two-year engagement reads as one chain of documents instead of a folder of lookalike PDFs. Issue, end, renewal and signing dates are tracked, and external documents can be uploaded into the same system.

Signing is governed per party: you decide who must sign and how each signer verifies, by email code, SMS code or both. Signers get a personal link, no account needed, and the Sign button activates only after the document has actually been read. Each signature binds to the exact version signed, and everyone receives the final copy with all signatures the moment the last party signs.