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.
ConnectWise Manage, Autotask PSA, HaloPSA and SuperOps. Two-way means client and agreement records: your companies and contacts come into XClause, and records XClause creates travel back out to the PSA. It does not mean invoices. PSA, RMM and accounting integrations are included on Pro and above, not on Starter.
No. Device counts flow inbound only, from your RMM into XClause. NinjaOne is connected read-only, and XClause never writes device or configuration data back into it. Inbound is the direction that matters for billing anyway: it is what lets XClause compare the devices a client actually has against the units their agreement covers.
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 and Xero. Invoices and client records are pushed out to both; payment status is read back from QuickBooks. 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 receives 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 varies by connector and by direction, so ask about the specific one you care about. Some pulls are a button you press in Settings, some run on a schedule, and outbound writes happen when the event that triggers them happens rather than continuously. There are no real-time webhooks from PSA or RMM platforms into XClause today.
Contracts and signing
Documents, signatures and renewals
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
No. Signing does not create or send an invoice on its own. Generating the invoice is an action you take from the contract, and it drafts the invoice from the agreement: one line per managed unit at the counts and discounted rates in the signed SOW, with one-time charges kept separate from recurring ones. You review it and send it.
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