Versori by Avalara (2026): “Available Today” Means Available to Partners

What Avalara Announced on 24 September

The release is datelined Fort Lauderdale, Fla., 24 September 2026, and distributed via PR Newswire. Avalara “announced the availability of Versori by Avalara, an agentic integration fabric that dramatically accelerates how developers and partners connect enterprise systems to Avalara tax and compliance solutions.” The subheadline sets the promise: specialised AI agents “plan, connect, build, and deploy production-grade connectors in days.”

CEO Hugo Sarrazin is quoted: “Businesses should not have to spend significant engineering time just to connect tax and compliance to the systems where they already work … Specialized AI agents can research, build, test, and deploy production-grade connectors in days, giving developers and partners a dramatically faster path to bring Avalara into virtually any enterprise system.”

Four named agents carry the work, and the release describes each one:

One line in that table is doing more work than the headline. “Customers and partners retain access to the generated connector code and business logic” is a commitment about what you keep, and integration platforms have historically been where lock-in lives — the connector runs, but it is not yours and it does not leave. Avalara states the opposite, twice: the release makes the claim, and the developer FAQ answers “Who owns the connector once it’s built?” with “You do. Versori owns the underlying platform, not what you build with it.” That is the part of this announcement most worth having in writing, and it is the part no summary of it has led with.

Versori is not new to Avalara. Avalara acquired the company and announced it on 2 March 2026, describing automated connector development powered by agentic AI workflows and saying Versori would operate as “Versori, by Avalara.” Today’s release is the product availability step, 206 days later.

“Access Today” Resolves to Four Prerequisites

The release’s availability sentence is: “Developers and partners can access Versori by Avalara today through the Avalara Developer Portal. Users can explore API documentation and enroll in hands-on Versori by Avalara training.”

That portal page exists and is public. Checked on 24 September 2026, its hero line reads: “As an Avalara partner, unlock Versori access for your first integration.” Its FAQ then answers the access question directly — “What do I need to access the free Versori offer?” — with: “Three things, in order: an active Avalara Partner Program agreement, enrollment in the Technology Partner Program, and acceptance of the Versori Platform Addendum. Each builds on the previous requirement.” A fourth gate follows, under “Is training required?”: “Yes, you must complete a short online course before getting access.”

Side by side:

Neither column is false. They describe different things, and the distinction is the whole story for a buyer: this is a partner-channel enablement offer, not a customer-facing feature. If you are a finance or tax lead evaluating sales tax platforms, the agent that builds connectors “in days” is not something you will touch. Your systems integrator, ISV or accounting-firm partner might. The benefit reaches you second-hand, as a faster or cheaper implementation quote — if it reaches you at all, and Avalara makes no claim that it will.

The portal also carries a claim the release does not: “Build an end-to-end integration on Versori in under 90 seconds.” No benchmark, test conditions or reference build is published for either that number or the release’s “in days,” so both are vendor claims, and neither is checkable from outside the programme.

What the Free Offer Covers, and Where It Stops

The developer FAQ is unusually specific about scope, which makes it straightforward to tabulate. Every line below is quoted from that page as read on 24 September 2026.

Read together, those answers describe a well-drawn commercial offer rather than a giveaway, and the rows that matter most to anyone who will live with the result are the last three. You own the code, you support the code, and compatibility is your risk. An agent that writes a connector in days does not change who gets paged when a tax call fails against a bespoke ERP at month-end close. If an implementation partner quotes you a build on this basis, that support boundary is the clause to put in the statement of work.

Supply Is Not Entitlement: Avalara’s Own Plans

Here is the structural point the announcement does not address. In this category, the binding constraint on integrations is usually not “a connector does not exist.” It is “a connector exists, and your plan does not include it.”

Avalara is the clearest example of that, on its own published pricing page — re-checked on 24 September 2026, the day of the announcement, and unchanged from our verified Avalara listing:

Avalara’s integrations page, also checked 24 September 2026, states the catalogue size as “1,400+ signed partner integrations and counting.” So the company that has just announced an agent capable of building a connector for “virtually any enterprise system” already has more than fourteen hundred of them — and on its two published plans, names five. The catalogue unlocks on the tier whose price is not published, for companies above $50M in revenue.

The release does not mention pricing, plan tiers or entitlement once. That is not an omission to be indignant about; it is a developer-programme announcement, and entitlement is not its subject. It is, however, exactly why the announcement should not move a mid-market buyer’s scorecard. Versori changes connector supply. What you are allowed to connect is still decided by your contract.

How the Rest of the Category Gates Integrations

The same pattern runs through the category, and it is visible only if you read plan pages rather than integration pages. Every figure below comes from our own verified sales tax listings, each with the date its source was last checked:

Four of those ten meter integrations by count, on the price list. One sells the absence of an integration project as the product; one sells the presence of one. Against that spread, “we can generate a connector for anything” is a real capability, but it answers the question that is least often the blocker. Before you weigh it, check the cheaper thing: on the plan you are actually buying, how many integrations are included, and is yours one of them?

We have worked the underlying numbers elsewhere — every published price in the category converted into one annual bill in Avalara Alternatives (2026), three incompatible pricing units reconciled in Anrok vs Numeral vs Quaderno, and the same integration-depth question asked of AR platforms in What 15 AR Platforms Actually Connect To.

Two Launches, Two Days, Opposite Availability

CRUSH ran to 24 September 2026 in Fort Lauderdale and produced two product releases on consecutive days. They are worth reading together, because their availability language points in opposite directions and the difference is easy to lose:

The sequencing is coherent on Avalara’s side: an orchestration layer aimed at customers, then the tooling that gets Avalara into more systems, aimed at partners. But the two releases make opposite promises about now, twenty-four hours apart, and only one of them is a thing anybody can use today — for a specific, documented definition of anybody.

What to Actually Do With This

1. You are an Avalara implementation partner, ISV or SI. This is aimed at you and the offer is concrete: one free connector, hosted runtime, and you own the code. The four prerequisites are the cost, and the addendum is a contract — read what it says about the connector you build and about what happens to it if you leave the programme, because Avalara’s own FAQ says free access ends then. Two business days to a reply, per the sign-up form.

2. You are buying sales tax software and your stack is mainstream. Nothing to do. If you run NetSuite, QuickBooks, Shopify, Dynamics, Sage, Stripe or Zuora, the connector already exists and has for years; a faster way to build connectors is not a benefit you can collect. Score the vendor on price per state, what a plan’s filing allowance actually includes, and what its guarantee clause pays — the axes that carry numbers.

3. You are buying, and something in your stack is bespoke. This is the one case where today’s announcement is worth raising in a sales conversation, and there are three questions to ask — all of which Avalara has now answered in public, so the answers you get should match: who pays for the connector build, who owns the resulting code, and who supports it after go-live. Then ask the entitlement question separately, because none of that covers it: on the tier we are being quoted, is this connector included? Get the answer in the order form, not the deck.

What This Piece Does Not Claim

Versori has not been tested here. Every statement above about what it does comes from Avalara’s 24 September 2026 release and its own developer portal page, both read in full on the day of publication. The “connectors in days” and “under 90 seconds” claims are reported as vendor claims because no benchmark or reference build is published for either, and nothing here asserts they are wrong — only that they are not currently checkable from outside the programme.

Nor is “partner-channel offer” a criticism. Partner enablement is a reasonable and normal thing for a compliance vendor to ship, and the terms Avalara has published are more generous and more clearly drawn than the category norm — particularly on code ownership, where the commitment runs against the direction integration platforms usually lean. The narrow point is about audience: a release headlined “enterprise integration” describes something a tax buyer does not personally get, and the portal page is where that becomes clear.

Finally, this changes no listing. Avalara’s entry in our sales tax and VAT compliance directory is scored on published pricing, filing coverage and integrations, and none of those moved on 24 September — the pricing page was re-checked the same day and is unchanged. If plan entitlement changes, the listing gets updated then, against the pricing page rather than the announcement.

FAQ

Is Versori by Avalara available to anyone today?

Not to anyone. The release says developers and partners can access it today through the Developer Portal; that portal’s own FAQ lists what the free offer needs, in order — “an active Avalara Partner Program agreement, enrollment in the Technology Partner Program, and acceptance of the Versori Platform Addendum” — plus a short online training course before access is granted. The sign-up form promises a reply within two business days.

What does the free offer include?

“Access to build, test, deploy, and run one Avalara connector, plus standard tooling, hosted runtime, and documentation.” One is the cap. More connectors need a separate paid agreement; non-Avalara integrations need a paid Versori licence at normal rates; hiring Avalara to do the build is a separate paid engagement.

Who owns and supports the connector?

You own it — “Versori owns the underlying platform, not what you build with it,” and the release separately says customers and partners retain access to the generated code and business logic. Support splits: Avalara covers platform issues, you cover your own connector’s code, and compatibility with other systems is not guaranteed.

Does this change what my Avalara plan includes?

No. Published tiers are still $79 and $69 per state per month below $50M revenue, both naming the same five integrations, with the 1,400+ catalogue on the quote-only Custom tier above $50M — re-checked on the day of the announcement. The release does not mention pricing or entitlement.

Should it change my shortlist?

Only if something in your stack has no connector and someone would otherwise fund that build. Otherwise check the cheaper constraint first: much of this category caps integrations by plan, so confirm how many your tier includes and whether yours is one of them.

Sources: Avalara, “Avalara Brings Agentic AI Speed to Enterprise Integration with Versori by Avalara,” 24 September 2026 (dateline, the availability sentence, the four agents, the Sarrazin quote, the code-retention commitment, and the “54 billion AvaTax API calls annually” boilerplate); Avalara Developer Portal, “Custom integrations at speed and scale using Versori” (developer.avalara.com/versori), read in full 24 September 2026 (the four access prerequisites, the training requirement, the two-business-day reply, the “under 90 seconds” claim, and every free-offer FAQ answer quoted above); Avalara sales and use tax pricing page, re-checked 24 September 2026 (tier prices, the $50M eligibility line, the five named integrations, Custom-tier catalogue access); Avalara integrations page, checked 24 September 2026 (“1,400+ signed partner integrations and counting”); Avalara, “Avalara Acquires Versori to Accelerate AI-Native, Enterprise-Grade Integration at Global Scale,” 2 March 2026 (acquisition date and terms of operation); Avalara, “Avalara Ushers in New Era of Agentic Tax and Compliance with Avalara Aviator,” 23 September 2026 (the non-GA availability statement); Avalara, “Avalara CRUSH Europe 2026,” 17 June 2026 (8 October 2026, London). Per-vendor integration gating is taken from ToolMasta’s verified directory listings, each carrying the source URL and check date shown in the table.