Contacts and follow-up
Keep everyone you know with how you met, what was said, and who you both know. Search it in plain English, and get nudged before a relationship goes quiet.
One account, every product
The tools already know about each other
Contacts, hosted events, payments, bookkeeping, email, communities and analytics run on one Connections account. They read the same sign-in and the same contact record, so the person who bought a ticket is the person your books and your follow-up already know.
- One sign-in
- One contact record
- One subscription
- Nothing to integrate
Seven jobs most businesses buy separately.
Hosted events and ticketing
Publish an event page, set ticket tiers, send email and SMS invites, and check people in at the door on any screen. Card payments run on Stripe.
Payments and a seller console
Manage products, customers and transactions from one dashboard, and embed the same checkout into your own site rather than sending buyers somewhere else.
Bookkeeping and tax export
Record transactions by hand, by bank feed, or by photographing a receipt. Set budgets, watch a cash-flow forecast, and export a Schedule C in one action.
Email, a support bot and a public Q&A
Send from a weekly allowance the whole account shares, answer visitors with a bot trained on your own documents, and publish a moderated board search engines can index.
Communities and memberships
Publish a community page, collect registrations with your own questions, schedule announcements, and sell a recurring membership to the people who keep showing up.
Analytics and AI visibility
Put a privacy-first pixel on your site, read revenue and funnel numbers, get automated friction findings, and check whether AI assistants can read your pages.
Fragmentation is a property of the stack, not of any tool inside it.
| Capability | Connections | A stack of separate tools |
|---|---|---|
| Contacts and follow-up | Yes | Yes |
| Event pages, tickets and door check-in | Yes | Yes |
| Payments and a seller console | Yes | Yes |
| Bookkeeping and a tax export | Yes | Yes |
| Email sending and a support bot | Yes | Yes |
| Site analytics | Yes | Yes |
| All of it behind one sign-in | Yes | No |
| All of it reading one contact record | Yes | No |
| One subscription, not one per person | Yes | No |
Frequently asked questions
What does one Connections account actually include?
One account covers contacts and follow-up, hosted events with ticketing and door check-in, payments and a seller console, bookkeeping with receipt scanning and a Schedule C export, email sending, an AI support bot trained on your own documents, community pages with registration, a marketplace, fundraising and crowdfunding campaigns, site analytics, and a developer API with an MCP endpoint. You sign in once and every one of them is already open to you. There is nothing to install, connect, or approve between them.
How is this different from buying separate tools and connecting them?
Separate tools each do their own job well. What they cannot do is agree on who a person is, because that agreement is a property of the stack rather than of any one product in it. On Connections a ticket buyer, a form respondent, a donor, and a contact in your address book are the same record, so the follow-up already knows about the ticket and the books already know about the sale. An integration copies data between two systems and then drifts. There is nothing to copy here.
Do I have to use all of it?
No. Most people arrive for one product and never open the rest, which is a normal and supported way to use the account. Nothing is switched on that you did not ask for, and an unused product costs you nothing and shows you nothing. The point of the account is that the day you do need the next thing, it is already there under the same sign-in with your contacts already in it, rather than being a purchase, a migration, and an integration.
Is it one subscription or one per product?
One. A paid Pass plan raises the ceilings across every product on the account at once rather than unlocking one of them. It is a flat monthly price rather than a charge per person, so adding a teammate to a workspace does not multiply the bill. The free base is not a trial: contacts are uncapped on it, events are free to host, and the marketplace is free to list on. Paid plans raise limits, they do not switch the products on.
Can I host an event and take the money for it here?
Yes. You publish the event page, set ticket tiers and recurring dates, and sell paid tickets through embedded checkout. Card payments run on Stripe, Connections takes a three percent cut on top of Stripe's own fee for payments it processes, and payouts release on their own schedule once the event has run. Invites and reminders go out by email and SMS from the event itself, door check-in runs on any screen as a kiosk, and every attendee stays in your contacts afterwards with the event attached.
Does it do bookkeeping and taxes?
Yes. The ledger records transactions by hand, by CSV, or from a linked bank feed, and it will read a photographed receipt and classify it for you. You can set monthly budgets, watch a cash-flow forecast, and export a Schedule C in one action. Because the money side and the customer side sit on the same account, a sale you took through checkout and the person who made it are not two separate facts you have to reconcile at the end of the year.
Can I send email from it?
Yes. Every account carries a weekly email-sending allowance that all of Connections draws from, so an event invite, a community announcement, a follow-up digest, and a support reply all come out of the same pool rather than a separate mail vendor per feature. Paid plans keep sending past the weekly pool at a set per-thousand rate with a spend cap you choose, so a busy week raises a bill you control rather than stopping the send.
Is there an AI assistant, and what does it cost to run?
AI runs throughout the account: plain-English search across your own contacts and history, a brief on who is coming to an event before you get there, a drafted marketplace listing from photographs, a support bot that answers from documents you upload and cites them, receipt reading, and transcription of recordings you upload. All of it draws one weekly token allowance shared by the whole account, so there is no separate AI subscription and no per-feature meter to track.
Can developers build on it?
Yes. Studio issues API keys, registers your own OAuth applications with dynamic client registration, and exposes an MCP endpoint so an AI coding tool can call Connections directly. Exploring and calling MCP tools is unmetered on the free base, with a rolling burst ceiling and a weekly count that paid plans raise. Connections is also a full OpenID Connect provider with passkeys and one-time email codes, so you can put a sign-in button on your own product without standing up an identity vendor.
What happens to my data if I leave?
You can download a zip of your profile, contacts, and event data from My Account yourself, without asking anyone. Data Locker exports are always on for developer storage. Nothing about the account is designed to make leaving harder than arriving, and Connections does not sell the underlying records to anyone: the business is people paying for the software and a cut of money that moves through it.