What's new

Plenty of contracts need a signature from your side as well as theirs. Now you can add a teammate as a signer on the same envelope as the counterparty, and they sign in-app in a couple of clicks. No separate tool, no chasing, no leaving Fusial.

• Add internal signers: in the signing editor, use Add a teammate to pull any teammate who can edit the workspace onto the envelope alongside external counterparties
• Mix and match in one document: combine yourself, teammates, and counterparties on a single envelope, each clearly labeled and color-coded
• Place fields per signer: drop signature, initials, date, name, and text fields that belong to each individual signer
• Sign in any order: there's no forced sequence, so internal and external signers can sign whenever they're ready, in parallel
• Nudge the right people: teammates get an in-app notification that links straight to the document, plus an email titled You've been asked to sign and, if your workspace has Slack connected, a Slack message, each with a Review & sign button
• Always know where it stands: the signing page shows each signer as Waiting or Signed with a timestamp, plus an overall X of Y signed count

Stop rebuilding the same agreement from scratch. Upload your standard Word document once, mark up the parts that change, and anyone on your team who can edit contracts can generate a finished, on-brand contract just by filling in a short form. Everything Fusial already knows gets filled in for them.

• Build from your own .docx: admins upload a Word file with variables in curly braces like {counterparty_name}, and Fusial detects every one across the body, headers, footers, and footnotes
• Shape each field: give every variable a label, help text, and a type (short text, long text, date, number, currency, dropdown, or yes/no), and mark it required or optional
• Let Fusial fill what it knows: fields bound to counterparty name, your organization, the contract owner, or today's date populate automatically with no typing; bind others to the primary contact, effective date, value, or term and they're captured once on the create form, then dropped into the document
• Set smart defaults: give a template a default contract type, your default role, and a title pattern like {counterparty_name}: MSA so new contracts name themselves
• Create in a few clicks: from the Contracts page, hit Create, pick a template, fill the form, and Fusial renders the document and sets up the contract, owner, and counterparty for you
• Capture the signer as you go: contact details entered on the form drop into the document and save as the counterparty's signatory, ready for signature
• Keep templates current: swap the underlying .docx anytime and Fusial re-detects the variables, keeping your labels and bindings for everything that still exists

Fusial now reads the deadlines out of your contracts and keeps an eye on them for you. When a contract is processed, it extracts the obligations buried in the text (renewal notice windows, payment dates, deliverables, reporting requirements) and tracks each one against the contract's real dates, so a missed opt-out window never sneaks up on you again.

• See everything in one place: the new Obligations page brings together obligations from every contract, with filter tabs for Upcoming, Scheduled, Needs a date, Passed, Completed, and Dismissed
• Extracted automatically: Fusial pulls obligations from the contract text and stores each as a rule, like 60 days before the term end, rather than a brittle fixed date
• Dates that stay correct: obligations resolve from the contract's own anchors (effective date, execution date, term length, auto-renewal), so set those once and every due date is calculated for you
• Fill the gaps when needed: obligations without enough information show a Needs a date badge; add the missing contract date and they resolve instantly, or create and edit obligations by hand
• Sorted by kind: each obligation is typed as a Renewal notice, Auto-renewal, Expiration, Payment, Deliverable, Reporting, Milestone, or Other
• Reminders on your terms: the new Obligation reminders page lets an admin set org-wide rules per obligation kind, with lead times like 60, 30, and 7 days before due, plus the option to notify on the due date or once overdue
• Delivered where you work: reminders go out over email and Slack to the contract owner, anyone assigned to it, and any extra recipients you add to the rule

Where do deals stall? How often do you accept the other side's edits? Are you blowing past your own SLAs? The new admin Analytics dashboard answers all of it from the contract data you already have (no extra tracking, no setup), with a date range you control and a one-click CSV export on every detailed report.

• Start with the headline numbers: contracts created and signed, average time to signature, contracts in flight, SLA breaches, and your incoming-edit acceptance rate, all for the range you pick
• Find the bottleneck: Cycle time by stage shows the average and median days contracts spend in each stage, from Draft through Out for signature
• Track your velocity: a Throughput trend charts contracts created versus signed over time, bucketed weekly or monthly to match your range
• Understand your negotiations: Redline acceptance breaks down how incoming edits land (pending, accepted, rejected, superseded), how your team responds (accept, reject, counter), and how often AI-suggested redlines hold up
• Stay ahead of deadlines: SLA breach trends plot warnings and breaches over time and show which statuses breach most
• See your pipeline: Contract distribution breaks contracts down by status, type, and your role, with pipeline value attached
• Close the loop on signing: a Signature funnel tracks envelopes from sent to viewed, signed, and completed (plus declined and voided), with the average days to complete
• Take it with you: every detailed report below the headline numbers exports to CSV for your own reporting; the whole dashboard is admin-only

Hit ⌘K anywhere in Fusial and search across every contract in your organization, by name, by counterparty, or by what a clause actually says. Results come back as you type, grouped into the contracts that match and the specific sections that do, each one a click away from the exact paragraph.

• Open it from anywhere: a search bar in the header, a compact icon on smaller screens, or ⌘K / Ctrl+K from any page
• Two kinds of result: a Contracts group that matches on title and counterparty, and a Matching sections group that surfaces the individual clauses that fit
• Search by meaning, not just keywords: section results combine semantic (vector) search with full-text matching, so "can they cancel early?" finds the termination clause even when it never uses those words
• Jump straight to the clause: selecting a section opens that document version, scrolls to the exact paragraph and briefly highlights it, with a snippet in the result so you know what you're clicking
• Scoped to your organization: search only ever returns contracts your org owns, with counterparty logos shown inline so the right match is easy to spot
• Always current: Fusial re-indexes a contract in the background whenever a new version is extracted, so search reflects the latest text without you lifting a finger

Already have years of signed agreements sitting in a folder somewhere? Drop them into Fusial all at once. The new Import contracts flow takes your existing PDFs and Word files, including ones signed long before you ever used Fusial, and sets their status and signed dates. Leave AI analysis on and Fusial extracts each one in the background, so your back catalog ends up fully searchable, tracked, and ready to manage alongside everything else.

• Drag and drop in bulk: bring in many contracts at once from .docx and .pdf files (up to 50 MB each), straight from wherever they live today
• Triage before you commit: a review grid lets you set each contract's title, type, our role, owner, status, and counterparty in one place, or bulk-edit a whole selection at once
• Detect fields automatically: leave type, role, or counterparty on Detect with AI and Fusial figures them out from the document itself
• Bring history with it: mark a contract as Signed and set its real signed date, so your record reflects what actually happened, not the day you uploaded it
• Records-only when you want it: turn Run AI analysis off to bring contracts in as plain records with no extraction at all; either way, imports always skip assignment and SLA automation, so bulk-loading history never sets off a wave of tasks or reminders
• Watch it land: a live progress view shows each contract move from Analyzing to Analyzed, flags anything that comes back Partial or Failed, and makes every contract clickable the moment it's in

Connect HubSpot once for your whole organization and Fusial keeps your contracts in step with your HubSpot deals, companies, and contacts, with no copy-paste required. Contract status drives the deal stage, a deal stage change in HubSpot moves the contract, and the signed PDF lands on the deal when everyone's done.

• Connect once, org-wide: an admin links HubSpot in Settings → Integrations; the connection covers everyone, and disconnecting leaves your existing deals untouched
• Contracts become deals: create a HubSpot deal from any contract, or link an existing one by ID; turn on Auto-create deals to spin one up automatically every time a contract is created
• Outbound sync that stays current: the deal name, amount, pipeline and stage, owner, and close date follow the contract, with counterparties synced as companies and their people as contacts
• Extracted terms as deal properties: Fusial writes the term length, auto-renewal, governing law, payment terms, and effective date it pulls from a contract into custom fusial_* deal fields, provisioned on your portal automatically so a sync never fails on a missing property
• Map your own stages: pick the HubSpot pipeline to use and map each contract status to a stage in it, so a contract moving to Negotiating or Signed lands the deal exactly where you want it
• Inbound, both ways: move a deal in HubSpot and the linked contract's status follows; edit the company and the linked counterparty stays in sync
• Scoped, never noisy: Fusial only ever touches objects tied to a contract it manages, so connecting to a large, messy portal won't flood your workspace; pull a deal's contacts into a contract on demand with Pull contacts
• Signed PDF on the deal: when a contract is fully signed, Fusial uploads the signed PDF and files it on the HubSpot deal as a note
• Self-healing: a background reconcile sweep catches anything the real-time path missed (a failed sync, a dropped webhook, an out-of-band edit) and brings the deal back in line

Once a contract is fully negotiated, send it for electronic signature right from the contract page. Fusial renders the agreed .docx to a flat PDF, collects signatures from every party, and files a sealed PDF, complete with a Certificate of Completion, back onto the contract when everyone's done.

• Send in a few steps: pick the agreed .docx version, add signers, place fields on the rendered PDF, and send; each external counterparty gets a unique signing link by email, while your own org members sign in-app
• Two kinds of signer: members of your own org sign in-app, while external counterparties sign in their browser with no account needed
• Place the fields you need: Signature, Initials, Date, Name, and Text, each assigned to a specific signer and required by default
• ESIGN / UETA consent built in: signers review the exact document and consent to sign electronically, all captured for the audit trail
• Always the final text: signing is blocked until every tracked change is decided, and Fusial re-renders automatically if the document changes before you send
• Sealed and certified: the completed PDF is stamped, hashed (SHA-256), and appended with a Certificate of Completion recording who signed, when, and from where
• Everyone gets a copy: all parties are emailed the signed PDF, and the contract moves to Signed with the signed version filed in its history
• Manage in flight: resend a link if it bounces, or void the envelope to cancel and drop the contract back to Negotiating

Workflows now have a drag-and-drop builder. Lay out each rule as a flow of Trigger → Conditions → Actions on a canvas, see how it reads at a glance, and edit every step in place. No more long settings form.

• Visual flow: every rule reads top to bottom as When (a contract is uploaded) → If (your conditions) → Then (the actions), connected on a canvas you can pan, zoom, and rearrange
• Add steps from a palette: drop in condition and action nodes as you need them; each step can only be added once
• Edit in a side inspector: select any node to set its value, with a live summary on the node itself (the chosen types, the assignee, the value range, and so on)
• Guardrails before you save: incomplete steps are flagged, and a rule needs a name, at least one condition, and at least one action before it can be saved
• Set priority and pause inline: name the workflow, set its priority, and toggle it active or paused right from the builder header
• Same routing engine: rules still run after AI extraction on a contract's first version, matching on an AI condition plus structured filters (type, your role, counterparty relationship, value) to assign, change owner, or override the SLA
• Admin and owner only: found under Automation → Workflows

Uploading the same .docx twice now triggers a Possible duplicate document warning that tells you which contract and version already contains the file, so you don't accidentally fragment your history across multiple records.

• Byte-level match: Fusial fingerprints every upload and compares against the versions already stored in your organization
• Catches both sides: the original file you uploaded and any identical file Fusial exported from another contract
• Scoped to your org and ignores deleted contracts
• Override when you mean it: click Upload anyway to add it as a new contract or version, e.g. the same template used on two unrelated deals

Ask questions about a contract in plain English without leaving the contract page. Chats are scoped per contract, shared with teammates who can see it, and notify prior participants when someone replies. It's read-only: the assistant advises, it doesn't act.

• Two entry points: chat pill on the contract page, or a chat region in the inspector when you've opened a specific redline
• Grounded in the contract: title, type, your role, counterparty, status, latest extraction summary, key terms, and the surrounding paragraph for redline-scoped chats
• Threaded history: every chat persists per contract; a Chats popover in the top bar lists your recent conversations across the org
• Auto-titled: Fusial generates a short title after the assistant's first reply
• Notifications follow your preferences: in-app, email, and / or Slack, mutable per user as Chat reply
• Permissions match the rest of the app: viewers can read existing chats but can't start new ones or post
• Fully audited: start, reply, and delete are all recorded on the contract

Export final used to be blocked while any edit was still pending. Now you can ship a partial draft at any point in the review and finish the remaining decisions in Fusial afterward.

• Export stays available regardless of how many edits are pending
• Decided edits are applied to the recompiled .docx; pending edits are skipped, not preserved as tracked changes. They stay attached to the source version inside Fusial
• The new version is stamped with how many edits were skipped, and the skip count is recorded in the audit log
• The counterparty only sees decisions you've actually made

Two new actions in the contract More actions (⋯) menu give you a way to clear out your active workspace without losing the audit trail.

• Archive: moves the contract out of the active list while keeping every version, redline decision, comment, chat, and audit-log entry intact. Reversible from the same menu. Status filter on the contracts list now defaults to active statuses, so archived contracts stay out of your normal view until you ask for them.
• Delete: permanently removes the contract, all its versions, related data (edits, comments, assignments, chats), and the stored .docx files in object storage. The audit-log entry for the deletion is preserved so you keep a record of what was removed and by whom.
• Both are owner / admin / member actions; viewers cannot archive or delete.

Set up rules that run against every new contract after Fusial extracts it. Matching contracts get assigned, re-owned, or put on a different SLA, without anyone touching them. Contracts that don't match any workflow are ingested normally with default ownership and SLA.

• Rule matching in plain English: describe what to look for ("contract contains substantial data privacy provisions"), and Fusial checks each upload against your rule
• Structured filters too: match on contract type (NDA, MSA, SOW, DPA, etc.), your role, counterparty relationship, or contract value
• Auto-assign with context: route matching contracts to the right person or team, with an optional note explaining why they're getting it
• Change ownership on the fly: reassign the contract owner based on what the rule matches
• Override the SLA: apply a stricter or looser deadline when a workflow matches, e.g. data privacy contracts get a 1-day legal review instead of the default 2-day
• Priority-ordered: lower priority numbers run first; when two workflows both override the SLA, the lowest number wins

Set deadlines on contracts based on their status, and get notified before things slip. Define an SLA rule once (e.g. "internal review must finish within 2 business days"), and Fusial tracks every matching contract automatically.

• Status-based deadlines: trigger an SLA when a contract enters a status like "In review," with deadlines measured in business days
• Auto-match or workflow-assigned: apply a rule to every new contract that matches, or scope it to specific workflows
• Pre-deadline warnings: get a heads-up 24 hours out, 4 hours out, or any cadence that fits
• Email and Slack notifications: owners and assignees are notified by default; add specific teammates per rule under "Also notify"
• Breach tracking: overdue contracts are flagged on your Fusial dashboard so nothing gets lost

Every action across your workspace is now recorded and searchable. Open Settings → Audit log to see who did what, when, and to which contract.

• Broad coverage: AI responses applied, reopened, or rejected; bulk decisions; edits and comments accepted or reopened
• Filter by date, action, or user: narrow down to a specific person, time window, or action type
• Search by user or contract title: jump straight to the events that matter
• Expand any row for the raw payload: see the underlying event data, including edit IDs and decision metadata