What OpenAI DevDay 2026 Means for SaaS Companies: ChatGPT Plugins as a New Distribution Surface

Most of what was written in the week after DevDay falls into two piles. One says ChatGPT is now an app store and your SaaS will die without a plugin. The other says it is 2023 again and plugins will be forgotten by spring. Both are guessing.

This article does something more boring. It separates what OpenAI has put in writing from what we have seen ourselves and from what cannot be known yet. Then it says what a software company should do about each.

What OpenAI has confirmed

Everything in this section is documented by OpenAI. The sources are listed at the end with the date we read them.

Plugins can now have an interface inside ChatGPT. The DevDay recap describes plugin extensions as a way to "give your plugin a home in the sidebar and build interactive panels where people can work alongside the conversation", plus viewers for the file types your product supports. The developer documentation lists ten extension surfaces in total.

Discovery happens in two places. The recap says improved ranking and recommendations "help people find relevant plugins in the directory and in conversations". The Help Center confirms that people can "review a plugin suggested during a conversation". Once a plugin is installed, ChatGPT uses it automatically when it is relevant to a request.

Users stay in control. The same recap sentence ends: "Users choose which plugins to use and approve the access each one receives."

Submission has a defined process. A plugin is uploaded to the OpenAI Platform dashboard, checked automatically, scanned tool by tool, and then reviewed. The developer must be identity verified. MCP plugins need five positive and three negative test cases and a walkthrough video. Our submission guide covers each step.

Plugins can react to events. OpenAI is adding support for the proposed MCP Events specification so a plugin can start an automation when something changes in a connected product. The documentation is clear that this follows a draft specification.

One listing covers ChatGPT and Codex. Public plugins are published once to a directory both products share.

The audience figure. OpenAI describes ChatGPT as a surface where developers can launch experiences to "our collective 1.2B weekly users". That is a statement about OpenAI's audience. More on that below.

What we have observed

We are not going to manufacture findings. Approval times, review feedback and install counts from our own builds will be published in our research as each review completes, with dates and raw notes.

What we can report today is what we saw while reading every official page on 9 October 2026:

• The documentation is still moving. The Help Center article on plugins showed as updated three days earlier, and the article on developer mode two days earlier. Anything you read about this platform, including this article, has a short shelf life.
• The old names are still in the plumbing. OpenAI's former Apps SDK submission guidelines URL now serves a page titled "Plugin guidelines". The domain verification path is still /.well-known/openai-apps-challenge. The permission you need to submit is still called Apps Management Write. If a guide tells you "apps" and "plugins" are different products, it is describing two names for one system.
• Two official pages disagree on availability. The recap says plugin extensions are "Available to all plans". The extensions documentation says the web rollout is "coming soon to ChatGPT Free and Go users" and that mentions in the composer work only in the desktop app. Plan for the narrower statement.
• A widely repeated number has no official source. Several recaps state that more than 4,000 plugins exist. We could not find that figure on any OpenAI page. We do not repeat it as fact.

What nobody outside OpenAI knows

This is the part most commentary skips.

• How ranking works. OpenAI has not described the signals behind directory order or conversation suggestions.
• How often suggestions appear. There is no published rate, by category or overall.
• How much organic use an average plugin gets. No install or usage data has been released for the directory.
• How long review takes. OpenAI publishes no timeline and asks developers not to request expedited review.
• Whether the rules will hold. The commerce policy, the extension rollout and the events specification are all marked as changing.

Anyone quoting you a number for any of these is inventing it.

Why 1.2B users is not your distribution

Between OpenAI's audience and a person using your plugin there are six gates. Each one removes people.

1. Review. A plugin that is not approved reaches nobody. Trial and demo plugins are not accepted, and a plugin must offer something ChatGPT does not already do.
2. Directory discovery. Someone has to search for your category or your name, or browse far enough to find you.
3. Recommendation eligibility. A suggestion in conversation is decided by OpenAI's ranking. You cannot request it. Availability also depends on the person's plan, workspace, role and region, and enterprise admins decide which plugins their people may use.
4. User intent. ChatGPT calls a tool when a request matches its description. If nobody phrases a request the way your tools are described, the plugin stays silent.
5. Product utility. The first use has to return something the person could not have got from ChatGPT alone.
6. Repeat use and sign in friction. A plugin that needs an account adds an authorization step before any value. People who do not finish it are gone, and a plugin used once is soon uninstalled.

The honest way to size a plugin is from the other end. Start with the customers you already have who also use ChatGPT, and ask how many would rather ask than click. That number is real. Anything the directory adds on top is upside you cannot forecast.

What this means if you run a SaaS

The opportunity is a usage surface first. Your existing customers can reach their own data and take actions in your product from a conversation. That is worth building for its own sake when the workflow repeats.

It is not a checkout. OpenAI's guidelines limit commerce in plugins to physical goods and rule out digital products and subscriptions. A plugin can say a paid plan is required and link to an informational page. It cannot start a subscription.

The work is mostly evidence. A small MCP server is days of engineering. The annotations, test cases, authentication, privacy disclosures and reviewer account are what take the rest of the time. See MCP for ChatGPT plugins for the architecture.

Not every product should build one. If ChatGPT already does the job, or the product is public information with nothing to act on, do not. Our readiness checker applies fixed rules and shows its reasoning.

How we approach a build

HouseofMVPs builds plugins for products that already exist. We write the prompt set first, build a small number of tools around it, test until the right tool runs and the wrong ones stay quiet, and file the submission in your OpenAI organization. Plugin Launch is $4,999 fixed and reaches submission in 14 days. Review and approval are OpenAI's, on OpenAI's schedule.

The details, the tiers and the division of work are on the ChatGPT plugin development page.

How this article will be maintained

Platform facts were verified on 9 October 2026 and are due for review by 6 November 2026. When something changes we will revise the text, record what changed in an update note at the top, and keep the original publication date.