Easily managed B2B subscriptions.
Sesamy handles B2B subscriptions for publishers: multi-seat licensing, domain-based access, SSO, invoicing, and reporting, inside the same platform that manages digital and print subscriptions.
Capability 01 · Multi-seat licensing
Multiseats that are easily managed.
Your team sees the contract-level view (seats used, renewal date, monthly spend); the buyer handles the detail.
- Buyer manages their own seats. A librarian at Aalto University buys 200 seats. From that point on, the librarian (not your support team) adds and removes staff from the seat pool through the buyer’s own portal. The publisher sets the contract terms. The organisation manages the day-to-day.
- Add, swap, and remove without tickets. Staff turnover does not require a support ticket. Remove a leaver, add a joiner, swap a placeholder seat for a named one. Changes go live instantly. Invoices reflect the seat count on the next billing cycle, not the next calendar quarter.
- Role-based access per seat. Each seat can be tagged with a role (editor, reader, admin). The buyer’s admin controls who sees what. Entitlements flow into the subscriber record alongside individual subscriptions, so a named employee with a seat shows up in the same analytics as a private subscriber.
Capability 02 · Access and identity
Domain rules and SSO.
Domain-based access grants entitlement to everyone with an approved email domain (no individual invites needed). Single sign-on runs against the identity provider the buyer already uses, so login goes through your own IT policy, not a second password to keep track of.
- Domain-based access. Grant access to every employee whose email ends in the approved domain. If they have a @stockholm.se email, they are in. No individual account provisioning, no CSV import, no manual invite list for a 500-person organisation.
- Single sign-on with the providers organisations already run. Okta, Microsoft Entra, and Google Workspace are wired in. Employees log in with the credentials they already use. No extra password to reset. IT does not have to argue with Procurement about a second auth system.
The full B2B surface
Beyond seats and access.
Sesamy handles invoicing, reporting, and shared analytics in the same portal your team already uses for digital and print.
Invoicing that works like your finance team expects.
Automated B2B invoicing through Billogram: PDF invoice generation, payment tracking, OCR/KID reconciliation, and reminder cadence handled inside the platform. No more manual invoice runs, no chasing by email, no mismatched records between your billing tool and your subscription tool. Every invoice lands in the same ledger as card and Vipps payments from individual subscribers.
Multi-seat reporting your commercial team can actually use.
Usage per seat, renewal dates, revenue per account, seat utilisation across the portfolio. The commercial team sees which organisations are close to full capacity (time to upsell) and which have unused seats (time to retain). Data lives alongside digital and print analytics, so B2B shows up in the same MRR and churn dashboards as everything else.
One platform. One subscriber database. One set of analytics.
B2B subscriptions live in the same system as your individual digital and print subscriptions. One billing ledger across card, Vipps, OCR/KID invoicing, and Billogram. One subscriber record per person (even if they hold an individual digital sub and show up as a named seat on a B2B contract at their employer). One MRR dashboard that reflects actual publisher revenue, not two half-pictures. Finance reconciles once. Editorial reads one report. Commercial forecasts from one pipeline.
What changes after switching
Bigger accounts. Less manual work. Higher ARPU.
Figures from publishers running B2B contracts on Sesamy alongside their individual subscription base. Ranges, not best cases.
- 0
- Avg seats per contract
- 0
- B2B ARPU vs individual
- 0
- Weeks to onboard
- 0
- Self-service seat changes
Mean seat count across B2B contracts on Sesamy. Range: 10 to 2,500.
Average account-level revenue multiplier vs an individual digital subscriber.
Typical timeline from signed B2B contract to live seats, including identity provider integration.
Seat adds, removals, and role changes executed by the buyer (not the publisher’s support team).
How it compares
Built for how publishers sell to organisations.
Publishers sell B2B subscriptions to companies, government agencies, educational institutions, and libraries. Buyers expect professional invoicing, easy onboarding for their staff, and self-service seat management. The publisher needs reporting, renewal tracking, and billing that connects to everything else. Sesamy handles both sides: the buyer experience organisations expect, and the operational control publishers need.
What this isn’t
- Not a spreadsheet and a PDF invoice runner.Most publishers run B2B on a Google Sheet, a manual invoice generator, and a recurring reminder email. It works until one organisation asks for seat changes mid-contract, and the whole setup falls over.
- Not a B2B module bolted onto an individual-subscription platform.Adding B2B as an afterthought usually means two subscriber databases, two billing surfaces, and a reconciliation report nobody trusts. The buyer experience suffers. Your analytics lie by omission.
- Not a standalone B2B billing tool.Dedicated B2B billing systems are fine at generating invoices. They are not subscription platforms, they do not integrate with your paywall or print fulfilment, and they do not close the loop on individual-plus-B2B subscriber records.
What Sesamy is
- Multi-seat, domain, and SSO in the same portal.One place where your team sets contract terms and the buyer manages seats, access, and identity. No second tool. No CSV bridge between systems.
- Billogram invoicing on the same ledger as card and Vipps.B2B invoices land in the same financial ledger as individual card and Vipps payments. Finance reconciles once. Commercial forecasts from one pipeline. Editorial reads one MRR report.
- One subscriber record across individual and B2B.An employee with a personal digital subscription who shows up on a B2B seat list at their employer is one person in the database, not two. The analytics, the reader lifetime view, and the churn models all reflect that.
In their words
“A big benefit of moving to Sesamy for us at Medier24 and KOM24 is that the share of support requests has been cut in half. We see far fewer login issues than before, and most of our readers really appreciate the passwordless, intuitive login that came with the move to Sesamy.”
Common questions
What B2B publishers ask before switching.
Does Sesamy support B2B subscriptions?
- Yes. Sesamy handles multi-seat licensing, domain-based access, single sign-on, automated invoicing through Billogram, and multi-seat reporting for organisational subscriptions. B2B is a first-class subscription type alongside individual digital and print, not a module bolted on later.
Can B2B and individual subscriptions run in the same system?
- Yes. Sesamy manages B2B, digital, and print subscriptions in one platform with shared billing, analytics, and subscriber management. One ledger, one subscriber record per human, one MRR dashboard. Finance reconciles once. Editorial and commercial both work from the same data.
How does B2B invoicing work in Sesamy?
- Sesamy integrates with Billogram for automated B2B invoicing: PDF invoice generation, payment tracking, OCR/KID reconciliation, and reminder cadence, all handled inside the platform. B2B invoices land in the same ledger as individual card and Vipps payments, so there is no second reconciliation report at month-end.
How does domain-based access work?
- You approve one or more email domains (for example @stockholm.se) per contract. Every employee whose address matches an approved domain is automatically entitled. No individual invite list, no CSV import for a 500-person organisation. Domain rules are editable from the Sesamy portal by your team or the buyer.
Which SSO providers does Sesamy support?
- Okta, Microsoft Entra, and Google Workspace are the three identity providers wired in for B2B contracts. Employees log in with the credentials they already use. No extra password, no second auth system for IT to maintain. Custom SAML and OpenID Connect setups are available for Developer-page integrations.
How long does a B2B migration take?
- Typical timeline is 2-4 weeks from signed contract to first live seats, including identity-provider integration and historical seat backfill. 80+ publishers have migrated their B2B book alongside individual and print subscriptions with zero downtime. Read the full process on the migration page.
Ready to bring B2B subscriptions into the same platform as everything else?
A 30-minute demo, tailored to your B2B motion. Tell us the shape of your organisational accounts and we’ll walk you through seats, access, invoicing, and reporting in the portal.