**_TL;DR:_** _Ampersand is the first platform to give AI agents Read, Write, and Subscribe actions across their customers' GTM and Revenue and Billing enterprise tools._ # Step One: The CRM Sync We started Ampersand with a goal that was simple to articulate but hard to ship: help B2B product teams deliver **deep, customer-facing CRM integrations** in days, not quarters. Not a checkbox Salesforce/HubSpot connector. Not a brittle one-way CSV import. But a real-time, bi-directional sync that your customers configure inside your product, with mappings for standard and custom objects/fields, scheduled or on-demand runs, granular observability, and built-in rate limiting and retries. We built for Salesforce first, then HubSpot and Microsoft Dynamics next. These are enterprise systems where every tenant is a unique snowflake and overlapping APIs can do the “same” thing in different ways. Along the way, we aced schema discovery, per-customer mappings (predefined, user-defined, or dynamic), quota-aware rate limits, high-volume backfills, and the granular observability developers actually want. With customers running core workloads on Ampersand, the next step was obvious: this developer-first, declarative, customer-configurable, production-grade form factor should extend far beyond CRM. --- # Step Two: The GTM Stack Customers asked, “If this works for Salesforce, can we use Ampersand to sync with the rest of our customers' stack”? We naturally said yes. Our mission at Ampersand is to enable B2B product builders (and now AI agent builders) to access and act on their customers' proprietary business data. We extended the same architecture across where revenue teams live: Marketing Automation (Marketo), Sales Engagement (Outreach), Success/Support (Service Cloud, Zendesk), Conversation Intelligence (Gong, Zoom), and more. The same foundation applies every time: - Full data model and API coverage - not lowest-common-denominator “unified” schemas. - Robust sync infrastructure. - Per-tenant mappings & config so custom objects/fields are first-class, not forced. - Auth & configuration state handled by Ampersand - OAuth flows, token rotation, scoped permissions, sandbox/production separation. These are exposed via Headless APIs so you can own the UI end-to-end (or use our built-in components). Result: a clean go-to-market story that our users love. **But revenue doesn’t stop at _Closed Won._** --- # Step Three: The Leap Into Billing & Revenue Deals close in CRM. Money moves in payments and ERP. The critical data and actions live there: invoices, credits, revenue schedules, journals, subsidiaries, tax rules, etc. If your product or agent cannot reach them, you are flying half blind. Renewals and dunning become guesswork, invoices cannot be previewed or amended safely, MRR and revenue reports drift, support lacks the source of truth, and automated agents' actions stall at the last mile. **Today, we are thrilled to announce our expansion into the Revenue and Billing stack with** **deep connectors for** [**NetSuite**](https://docs.withampersand.com/provider-guides/netsuite#netsuite) **and** [**Stripe**](https://docs.withampersand.com/provider-guides/stripe#stripe) (and several more systems to follow). It is the same Ampersand architecture applied to the layers that touch cash and ledgers: Full API access, per-tenant mappings, and idempotent updates. The outcome is simple: your product now spans CRMs to payments to ERP without a bunch of brittle glue code. --- # Introducing the Deep NetSuite Connector and ERP Sync NetSuite is one of the most customizable cloud ERPs out there. It’s an ERP platform with accounting baked in, not just an accounting app with a few knobs. Enterprises love this: you can model the business precisely; extra dimensions, bespoke approvals, RevRec that matches the auditor’s checklist. “**NetSuite is flexible and customizable**” is not marketing fluff; it’s the core design. That’s great for the business, and that's why customer-facing integrations must treat every tenant with utmost care. With this flexibility, unexpected rules can create tricky situations that make integrations with NetSuite a headache to untangle: - **Custom fields on transactions:** `custbody_project_code`, `custbody_client_region` required on Invoice. - **Form-specific requirements:** “Invoice – Enterprise” requires `terms` and a custom checkbox, “Invoice – SMB” doesn’t. - **Subsidiary rules:** Same customer in US and EU subsidiaries; taxes and currencies differ, and the role you use in EU can’t see US transactions. - **RevRec module on:** Creating an Invoice automatically builds schedules; your update must not double-trigger recognition. Ampersand is built to handle this complexity. ## What are we launching today? - **REST + SuiteQL support**: Query anything you can express and perform safe CRUD where it’s allowed. - **Standard + custom records**: Invoices, Payments, Sales Orders, Credit Memos, Journal Entries, and truly custom records unique to each tenant. - **Per-tenant mapping**: customers map their fields, forms, segments, subsidiaries, and approval flows through the embedded UI (or bring your UI components and manage configuration and state with Ampersand headless). - **Backfills**: sane defaults for windowing historical data; graceful handling of rate limits. - **Bi-directional syncs**: update your customer's ERP safely with tenant-specific guardrails. **Plain English**: you can read and write the records that matter, at ERP depth, without one-off engineering per customer. Read more in our [NetSuite guide](https://docs.withampersand.com/provider-guides/netsuite). --- # Introducing the Deep Stripe Connector and Payments/Billing Sync We are powering our deep Stripe Connector with the same architecture as Salesforce and NetSuite: full API access, per-tenant mapping, idempotent updates, safe writes, incremental reads, backfills, observability, and Embedded or Headless UI. Also exposed via MCP tools and our AI SDK. ## What we are launching today: - **Subscriptions & invoices**: your AI agent previews proration/tax before commit, so totals match what customers see. - **Usage-based billing**: report usage and generate invoices to the penny. - **Refunds & credits**: issue full/partial refunds and credit notes safely, with idempotent writes and support-ready logs. - **Marketplaces & payouts**: route buyer payments to the right seller, take a platform fee, and schedule payouts while keeping each seller’s balance separate. **Plain English:** same safety rails, tuned for money movement. Read/write everything Stripe’s API can do, without one-off builds per tenant. Read more in our [Stripe guide](https://docs.withampersand.com/provider-guides/stripe). --- # We built a usage-based billing demo app called MeterMax To prove the point, we built MeterMax, a tiny usage-based billing demo. A straight path from usage → invoice → revenue: 1. Product usage events are collected in MeterMax. 1. MeterMax creates invoices in Stripe. 1. Those invoices are synced to NetSuite for revenue recognition and reporting. Where most teams burn weeks is mapping and infrastructure. MeterMax uses Ampersand’s SDKs and infrastructure, so each new customer configures themselves: - Schema discovery: Ampersand detects the MeterMax customers' Stripe metadata and NetSuite fields/forms/segments. - Embedded mapping UI: Metermax customers map usage attributes to Stripe invoice line metadata and NetSuite fields. No custom coding or implementation per customer needed. - Write updates safety: each invoice creation and ERP sync runs a simulation first (required fields, forms, revenue rules), then updates with idempotency. If a network hiccup reruns the call, the same result returns and no double-posting. MeterMax is intentionally small, but it shows the thing that matters: write-heavy flows at enterprise depth, without one-off engineering per customer. Full demo here: [https://metermaxfe-production.up.railway.app/](https://metermaxfe-production.up.railway.app/) <video width="1080" height="360" controls> <source src="https://different-power-f43404e489.media.strapiapp.com/f_nsdemo_4002ebf5be.mp4" type="video/mp4" /> Your browser does not support the video tag. </video> --- # Full-Stack for AI Agents With data and actions available across GTM tools, payments, and ERP, plus per-tenant mappings and safe writes, AI agents can do real work in the enterprise. Here are 3 examples that we see across our developer base: - **Revenue assistant** finds overdue invoices in ERP, kicks off a dunning sequence, proposes a proration via Stripe, and posts the credit memo back to ERP. Policy-checked and auditable. - **Renewals helper** watches usage, proposes plan changes, simulates the new revenue schedule in NetSuite, and executes once approved. - **Ops autopilot** monitors webhooks, backfills cleanly when a provider blips, and explains every action in a customer-visible log. --- # Where We’re Headed This isn’t “two new connectors.” It’s the next layer in a full-stack integration platform for native product features and safe agent actions across the most customized systems in your customers’ business. We started with deep CRM. We then covered the GTM stack. Today, we’ve stepped into Revenue and Billing. The north star is unchanged: help product builders ship integrations that their customers see and trust, at the depth that enterprises actually run on.  --- ## What’s Next in ERP & Billing Integrations We’re expanding across the rest of the financial stack and adjacent systems that touch revenue: - **ERP/Accounting:** Microsoft Dynamics 365 Business Central (already in beta), QuickBooks Online/Enterprise, Sage, SAP S/4HANA, Xero, etc. - **Billing/Subscriptions:** Chargebee, Zuora, Recurly, Paddle, etc. - **Payments:** Adyen, Braintree, PayPal - **(And yes, more GTM)** where it complements quote-to-cash Same promise everywhere: **full API access**, **per-tenant mapping**, **safe writes**, **embedded or headless** UI experience. --- ## Try It Today If you’re building an AI agent that needs to **create invoices in Stripe** and **recognize revenue in NetSuite,** and you want customers to configure it themselves without engineers on the call, Ampersand is for you. - Start building for [free](https://withampersand.com/) - Read the [**Stripe**](https://docs.withampersand.com/provider-guides/stripe#stripe) and [**NetSuite**](https://docs.withampersand.com/provider-guides/netsuite#netsuite) guides - Prefer to build your own UI? Use [**Headless**](https://docs.withampersand.com/headless) to drive the full flow via API - Plug your agent in via the [**MCP server**](https://docs.withampersand.com/mcp-server) or our [**AI SDK**](https://docs.withampersand.com/ai-sdk) (same actions, same safety) - Or [talk to an engineer](https://calendly.com/d/cmdf-fnw-bwv/speak-with-an-engineer-at-ampersand), and we’ll walk you through **MeterMax** live **Ampersand** — Deep integrations for AI agents. Complete data coverage over “unified API”. Safety over vibes. Outcomes over endpoints.
Back to articles