FAQ
Straight answers about
how XClause actually works
Especially the integration questions, where the honest answer is more specific than most vendors give. Every answer here starts with a yes, a no, or an it depends.
XClause is contract lifecycle software, not a law firm. Templates are a starting point, not legal advice. Have your own counsel review documents for your jurisdiction.
PSA, RMM and accounting
Integrations, by direction
“Integrates with ConnectWise” is true of a hyperlink. These answers name the records and the direction instead.
Four: ConnectWise PSA, Autotask, HaloPSA and SuperOps, each connected directly through its API with no middleware. What moves back out differs by tool. Autotask and SuperOps receive device changes you make in XClause, Autotask and ConnectWise PSA receive the new clients you create (ConnectWise links to a company with the same name rather than duplicating it), HaloPSA receives the client, opportunity and quotation for each contract (and its clients and contacts can be imported into XClause), and ConnectWise can also take managed unit counts on agreement additions. None of them receives invoices. PSA, RMM and accounting integrations are included on Pro and above, not on Starter.
Yes, inbound. XClause reads devices from NinjaOne every 6 hours and whenever you press Sync all, and it never writes anything back to NinjaOne. It reads managed devices from SuperOps when you press Sync now. Those counts let XClause compare the devices a client actually has against the units their agreement covers. It does not connect to Datto RMM, N-able, Kaseya VSA or Syncro today.
It depends, and the honest answer is narrower than most integration pages imply. XClause does not write invoice line items into any PSA. What it can do is push managed unit counts from a SOW onto matching ConnectWise agreement additions. That is ConnectWise only, it is off by default and you switch it on in Settings, and it requires you to map your ConnectWise products to your XClause units first. There is no equivalent for Autotask, HaloPSA or SuperOps.
QuickBooks Online, Xero and FreshBooks. Invoices go out to all three, client records go to QuickBooks Online and Xero, and payment status is read back from all three when you sync payments. Automatic syncing is off until you turn it on, so connecting an account does not start sending invoices to your ledger on its own. Xero and FreshBooks receive invoices as drafts for you to approve.
No. Your PSA stays the system of record for tickets, time and service delivery. XClause is the contract layer alongside it: templates, SOWs, e-signature, invoicing from the agreement, and renewal reminders. If you are choosing between them, you are asking the wrong question. Most MSPs run both.
It depends on the connector. NinjaOne syncs every 6 hours and on demand. ConnectWise, Autotask and SuperOps refresh when you press Sync, and ConnectWise agreement additions are also read nightly. Outbound writes, such as a device change pushed to SuperOps or a HaloPSA opportunity, happen at the moment you save or create the contract. There are no real-time webhooks from PSA or RMM platforms into XClause today.
Contracts and signing
Documents, signatures and renewals
Yes. Every signed agreement in XClause carries its renewal date, and you choose when reminders go out: any mix of 90, 60, 30, 15 and 7 days before it, to your team, the client, or both. That covers contracts you build and sign in XClause and signed contracts you upload. It is included on every plan, Starter included. The contracts list shows each agreement’s renewal or end date, and its Expiring soon filter lists everything renewing or ending in the next 60 days.
Yes. You send an MSA, SOW or other agreement from XClause and the client signs it in the browser, either in the client portal or from an emailed link verified with a six-digit code. E-signature is included on every plan, and contracts are unlimited on each. The executed PDF carries a certificate of completion with the signer name, email, timestamp, IP address and consent record.
The signer name and email, a timestamp to the second in UTC, the IP address and device, how the signer was authenticated, and the verbatim ESIGN and UETA consent text they agreed to along with when they agreed to it. A certificate of completion is appended to the executed PDF, and a SHA-256 hash of that file is stored so a copy produced later can be checked against the one that was signed.
Two ways: an emailed six-digit code proving control of the mailbox the document was sent to, or an already-authenticated XClause session. XClause does not do government-ID checks, knowledge-based authentication or biometric verification. If your engagements need identity proofing at that level, that is a real requirement to raise with any vendor you are evaluating.
Yes. You can invite outside counsel into a specific contract to redline it before it goes out. Independent MSP attorneys draft the XClause template library and keep revising it, but your lawyer is the one who should look at a specific deal.
You set it per agreement, choosing any combination of 90, 60, 30, 15 and 7 days before the renewal date. Contracts you import default to all five; contracts built in the standard contract form use your account default, which ships as a single reminder 30 days out. Reminders go to your team, the client, or both, and can also post to Slack or Microsoft Teams. Document types that do not renew, such as NDAs, are skipped.
Billing and getting started
Invoicing, pricing and migration
Yes. One action from the contract drafts the invoice from the signed SOW: one line per managed unit at the counts and discounted rates in the agreement, with one-time charges kept separate from recurring ones. Switch on invoice generation for a SOW, or as your default for new SOWs, and the invoice is created the moment the last signature lands. Mark an invoice recurring and XClause drafts the next one each period, and sends it too if auto-send is on. It is emailed to the client automatically only if you also turn on auto-send, and both are off by default. Invoices can then go to QuickBooks Online, Xero or FreshBooks on Pro.
Yes. Starter, at $99.99 a month, includes renewal reminders on every agreement, set at any mix of 90, 60, 30, 15 and 7 days before the renewal date and sent to your team, the client, or both. There is no separate renewal add-on on any plan.
Nothing extra. The client portal is included in every plan: $99.99 a month on Starter for up to 15 clients, $199 a month on Pro with no client limit, and $248 a month on Pro + White-Label, which puts your branding on the portal instead of ours. E-signature is included on all three.
Neither. Pricing is flat per company: $99.99/mo Starter, $199/mo Pro, and $248/mo Pro + White-Label, with a 7-day free trial. Adding a technician does not change the price and neither does sending another contract. Some features carry plan limits, which are listed on the pricing page.
Yes, one at a time. Upload a PDF, DOCX or TXT of an existing master agreement or SOW and XClause reads the parties, dates, term, rate and notice period out of it, then shows them to you to confirm before the import commits. There is no bulk contract import, and a scanned PDF with no text layer will not extract.
It is retained, not deleted. Cancelling takes effect at the end of the billing period and the account is then locked rather than wiped, so resubscribing brings everything back. There is no bulk export, so download the PDFs you want copies of while your subscription is active.
More detail
Answered in more depth elsewhere
Rather than restate them here in shorter form, these questions have their own pages.
Something not answered here? Ask us directly. If it is a fair question we will add it to this page.
Start running your contracts the modern way.
Build, send, e-sign, and manage every MSA and SOW in one platform. Start today, no demo required.
Free trial • Cancel anytime • No long-term contract