App Developer Studio

Enterprise AI guides

ChatGPT Enterprise and Business: plans, pricing and rollout for South African companies

ChatGPT Business is OpenAI's per-seat plan with a published price. ChatGPT Enterprise adds SCIM, data residency, customer-managed keys and the Compliance API, and is priced by OpenAI's sales team. This guide sets out what each plan includes, what it costs, and how we recommend a South African company runs its first rollout.

Every price and policy below comes from OpenAI's own pages, with a link and the date we checked it.

App Developer Studio is a Registered Partner in the OpenAI Partner Network. We build production OpenAI agents, multi-agent workflows and ChatGPT integrations, and deploy on the platform your organisation approves, including Claude.

By Rob MacleanReviewed by Amanda KaburiseLast reviewed

Plans and prices

ChatGPT Business and Enterprise prices

Business has a published price per seat, so you can budget before you speak to anyone. Enterprise has no public price, so the cost is only known once OpenAI quotes it.

ChatGPT Business
ItemPlanDetailSource
Standard seat, billed monthlyBusiness$25 per user a monthhelp.openai.com
Standard seat, billed annuallyBusiness$20 per user a monthhelp.openai.com
Premium seat, billed monthlyBusiness$125 per user a monthopenai.com
Premium seat, billed annuallyBusiness$100 per user a monthopenai.com
Premium seat usageBusiness5x more usage than a Standard seat, with no 5-hour limitopenai.com
SeatsBusinessMinimum 2 seats in any mix of Standard and Premium; for teams of 2 to 200help.openai.com
API usageBusinessNot included; the OpenAI API is billed separatelyhelp.openai.com

Prices in USD as of , excluding VAT. Check the vendor page before you buy.

ChatGPT Enterprise
ItemPlanDetailSource
PricingEnterpriseNo public price; contact OpenAI sales. Credit-based or token-based pricing is availableopenai.com

Prices in USD as of , excluding VAT. Check the vendor page before you buy.

Rand billing and the plan name

South African companies can check the rand amount at checkout. If older documents in your company mention a different plan name, the record below explains it.

Billing in South Africa and plan name
ItemPlanDetailSource
Billing currency in South AfricaBusinessZAR is a supported billing currency for standard paid plans; Enterprise is billed separatelyhelp.openai.com
Plan nameBusinessChatGPT Team was renamed ChatGPT Business on 29 August 2025; the rename alone changed no features or priceshelp.openai.com

As of . Check the vendor page before you rely on it.

What each plan includes

Identity, admin and data controls by plan

Both plans support single sign-on. SCIM, customer-managed keys and the Compliance API are Enterprise only.

Identity, admin and audit controls
ItemPlanDetailSource
Single sign-onBusiness and EnterpriseSAML SSO on Business and Enterpriseopenai.com
SCIM directory syncEnterpriseEnterprise onlyopenai.com
Customer-managed encryption keysEnterpriseEnterprise only (Enterprise Key Management)openai.com
Compliance APIEnterpriseEnterprise onlyopenai.com
Audits and certificationsBusinessSOC 2 Type 2openai.com
Audits and certificationsEnterpriseSOC 2 Type 2; ISO/IEC 27001, 27017, 27018 and 27701openai.com

As of . Check the vendor page before you rely on it.

Training, retention and data processing
ItemPlanDetailSource
Training on business dataBusiness and EnterpriseNot used for training by default; feedback you choose to share is the exceptionopenai.com
Data retentionBusiness and EnterpriseAdmin-controlled; deleted items are removed within 30 days unless the law requires otherwiseopenai.com
Data processing addendumBusiness and EnterpriseA DPA is available for Business, Enterprise and the APIopenai.com

As of . Check the vendor page before you rely on it.

Data residency

No South African data residency

Enterprise offers data residency in a set list of regions. South Africa is not on that list, and Business has no residency option. Using either plan means sending information outside the country, so treat it as a cross-border transfer from the start.

Data residency by plan
ItemPlanDetailSource
Data residencyEnterpriseEnterprise only, in ten regions: the US, EU, UK, Japan, Canada, South Korea, Singapore, India, Australia and the UAE. South Africa is not one of themopenai.com
Data residencyBusinessNot available on Businessopenai.com

As of . Check the vendor page before you rely on it.

POPIA

What to check for POPIA

These are the questions we would settle with your legal and security teams before a pilot uses personal information. This is a starting point, not legal advice.

  • OpenAI's data processing addendum, and whether it covers the plan you are buying.
  • Your basis for transferring personal information outside South Africa, since no residency region is in the country.
  • Retention settings that match your records policy, and who in your company sets them.
  • Which kinds of information staff may enter, written down and covered in training.
  • Whether the training default and its feedback exception suit your policy.
  • The audit reports your security team needs for the plan you choose.
  • Sign-off from your information officer before the pilot starts.

Choosing a plan

When Business is enough, and when you need Enterprise

Business is enough when

  • The group fits the team size Business is designed for.
  • You are content to manage joiners and leavers without SCIM.
  • You do not need data residency, customer-managed keys or the Compliance API.
  • You want a published price per seat, with rand billing supported on standard paid plans.

You need Enterprise when

  • The rollout is larger than Business is designed for.
  • You want users and groups synced from your directory through SCIM.
  • Data must be stored in one of OpenAI's residency regions.
  • Security needs customer-managed keys or the Compliance API.
  • You want role-based control over which apps each group can use.

The trade-off: Enterprise has no public price, so budget only once you have a quote.

How to roll out ChatGPT in a South African company

Each setting below links to the OpenAI page it comes from. The order, pilot size and measures are our recommendations, not OpenAI requirements. OpenAI's own steps are in its Business SSO setup guide and Enterprise admin quickstart.

  1. Step 1. Pilot scope

    We recommend starting with one team and one or two workflows, not a company-wide launch. Pick work with a baseline you can measure, such as drafting proposals or answering internal policy questions. A Business pilot needs only a few seats, so it is a small first commitment before you ask for an Enterprise quote.

    Seats
    Minimum 2 seats in any mix of Standard and Premium; for teams of 2 to 200 (help.openai.com)
  2. Step 2. Identity and provisioning

    We recommend this order: find out who already uses ChatGPT or the OpenAI API with a company email, verify your domain, set up SSO and test it, then decide how accounts are created. SCIM is Enterprise only.

    Verifying your domain can affect employees' existing personal and API accounts. Review automatic account creation before you apply the verified domain, because it gives paid seats to the people who sign in.

    Domain verification
    Add a DNS TXT record. Verifying can affect employees' existing personal or API accounts, account migration and email changes, so review who uses the domain first (help.openai.com)
    Single sign-on setup
    Business: SAML or OIDC, set up by the workspace owner. Enterprise: tenant-wide in the Admin Console, set up by a global admin (help.openai.com)
    Vendor-recommended order
    For large Enterprise rollouts, set up SSO and SCIM before inviting users broadly. Review automatic account creation before applying a verified domain, because it provisions paid seats (help.openai.com)
    Provisioning without SCIM
    Optional automatic account creation for people who sign in with a verified-domain email. It is separate from SCIM and does not need SSO (help.openai.com)
    SCIM directory sync
    Enterprise only. Syncing a user does not grant workspace access; synced groups are assigned to workspaces separately and can set roles (help.openai.com)
  3. Step 3. Admin and data policies

    Settle three things before users arrive: who administers the workspace, which apps and connectors to allow, and how long to keep conversations. We recommend allowing only the apps the pilot needs, and setting spend controls before the first invitations go out.

    Admin roles
    Workspace owner and admin roles; Enterprise adds role-based access for apps and plugins (help.openai.com)
    Connectors and apps
    New apps are off by default on Enterprise. Admins control which roles can use them, read and write actions, and when ChatGPT asks before using an app (help.openai.com)
    Retention settings
    Admin-controlled on Business and Enterprise (openai.com)
    Spend controls
    Usage analytics and spend controls; credits cover usage beyond plan limits (openai.com)
  4. Step 4. User enablement

    We recommend one live session per team, built around its real work, plus a shared page of approved uses and example prompts. Name one person to answer questions in the first weeks. Tell people plainly what not to put into ChatGPT, and why.

  5. Step 5. Measuring outcomes

    Measure the workflow, not the tool. Before the pilot, record the time per deliverable, the cycle time and the rework rate for the chosen tasks. Measure them again after four to six weeks. Report hours saved as estimated, and treat usage figures as a sign of adoption, not of value.

  6. Step 6. Scaling decision

    At the end of the pilot, make one of three decisions: expand on Business, move to Enterprise, or stop. Move to Enterprise when you need SCIM, data residency or the Compliance API. Stop, or change the workflow, when the measured gain does not justify the seats.

    SCIM directory sync
    Enterprise only (openai.com)
    Data residency
    Enterprise only, in ten regions: the US, EU, UK, Japan, Canada, South Korea, Singapore, India, Australia and the UAE. South Africa is not one of them (openai.com)
    Compliance API
    Enterprise only (openai.com)

Questions we get asked

ChatGPT Enterprise and Business FAQs

Next step

Test one workflow before you buy seats for everyone

Our AI workflow diagnostic takes about two weeks. It baselines one process, checks data and security feasibility, and ends with a go/no-go decision. It can conclude that you need no AI build at all.

Planning a rollout now? Book a call with Rob and Amanda.