How Much Does a Business ChatGPT Plugin Cost to Build?

Use a bounded example: an authenticated plugin that retrieves an existing customer's service-request status from one supported system. It returns the current stage and update time. It does not create requests, take payment or display a custom interface. That scope still needs account linking, record-level access, source mapping, testing and an operating owner. Adding a booking operation or a second customer system changes the estimate. So does discovering that the source has no supported way to retrieve status. OpenAI's server build documentation identifies live data, authentication and controlled actions as reasons to use a server-backed integration. In budget terms, each chosen capability needs work beyond a listing description.

For the proposed status project, assume the following effort at an illustrative AUD 160 per hour: Task and source mapping: 8 hours, AUD 1,280. Server and source adapter: 20 hours, AUD 3,200. Identity and record-access integration: 16 hours, AUD 2,560. Testing, recovery and release preparation: 16 hours, AUD 2,560. Handover and operating documentation: 6 hours, AUD 960. The total is 66 hours, or AUD 10,560. Adding a hypothetical 15 per cent allowance for unresolved work gives AUD 12,144. Neither the rate nor the allowance is a claim about the market. Replace them with the supplier's scope and assumptions. Ask whether the quoted amount includes GST, third-party charges and publication preparation. Do not infer those inclusions from a round project price.

The model assumes a supported source connection, usable customer identity and a clear definition of status. If any of those is missing, the scope changes. Discovery should establish what is known and what needs investigation. A source may return internal codes that staff interpret manually. Translating them into customer-facing states can require business decisions. An identity system may establish a person without identifying which organisations they can access. Those are delivery questions, not minor copy edits. List unresolved dependencies separately. A partner conversion route may need access that is not yet approved. A proposal should not price that uncertainty as though the capability can certainly be launched next week.

Operating costs can include hosting, source-system access, identity services, monitoring, support and updates. The chosen architecture determines which apply. Keep usage-based charges separate from staff time. For an illustrative maintenance model, assume three hours a month at AUD 160, plus an assumed AUD 120 for hosting and monitoring. That would be AUD 600 a month, or AUD 7,200 a year. These are example inputs, not measured bills or a retainer offer. Added to the example initial budget of AUD 12,144, the first-year planning total is AUD 19,344 before any excluded charges or applicable tax. The arithmetic is useful only when the inputs match the project. A rarely updated information tool and a business-critical integration need different support arrangements.

An MCP server can retrieve a record or run ordinary code without making a separate model request of its own. A plugin's architecture should show where any additional AI processing occurs and who pays for it. If the server calls another model to classify or summarise data, estimate that usage separately. The user's ChatGPT access, your hosting bill and your server's API spend are different budget lines. Do not copy an old forum answer about plugin charges and assume it describes the intended 2026 design. Ask the supplier for a request diagram and cost ownership at each step. You should be able to distinguish a source lookup from an extra model call without needing to understand every implementation detail.

Give suppliers the same customer task, source system and acceptance cases. Ask them to identify exclusions, required customer work and unresolved dependencies. A quote that leaves identity to your team is not directly comparable with one that includes it. Check what happens after handover. Who owns the hosting account and publisher identity? Who updates the tool when the source changes? How are failures noticed? What support is included and what is charged separately? For public publication, distinguish preparing a reviewable submission from guaranteeing approval. OpenAI's submission process includes review before the publisher chooses to release an approved version. Do not treat a build estimate as a guaranteed review schedule.

Suppose your team answers 180 status enquiries a month at six minutes each. That is 18 hours. If the proposed plugin removes seven hours of routine work and adds two hours of support, the net reduction is five hours. Those are hypothetical assumptions to validate. At an assumed internal value of AUD 70 per hour, five hours is AUD 350 a month. That alone would not cover the illustrative AUD 600 operating budget. The project may still have value through customer service or capacity, but those benefits need their own evidence. This calculation is deliberately open to an unfavourable result. A good scope helps the business choose a smaller pilot or a different workflow when the economics do not support the proposed build.

Is AUD 12,144 what 13labs charges? No. It is a worked planning example using stated effort, rate and allowance assumptions. A quote requires the actual scope. Is an information-only plugin cheaper? It may require less work, but source quality, publication and support still affect the estimate. Compare the agreed deliverables. Should we budget only for hosting? Include ownership, source changes, support and any additional usage charges the architecture introduces.

Documentation checked on 5 October 2026. All financial figures are illustrative AUD assumptions. Discuss a plugin estimate with 13labs using the customer task, source system and acceptance cases you want priced.