Short answerTreat each client GPT as a small project: intake the instructions, files and Actions, scope by complexity, rebuild, test side by side with the client, then hand over documentation and backups. Price by complexity, not by hours guessed in advance.
Intake questions
- Who owns the GPT, and are you allowed to access it? (Plugin migration requires the creator or an admin.)
- What does it do and how many people use it?
- How many files, and are the originals available?
- Does it use Actions? Which services and authentication?
- Where should the replacement live?
Scoping by complexity
| Level | Looks like |
|---|---|
| Simple | Instructions only, or a few files, no Actions |
| Medium | Many files, careful tone rules, several users |
| Complex | Actions, authentication, webhooks or customer-facing use |
Delivery
- Export and back up everything.
- Build on the agreed path (options).
- Run side-by-side tests with the client.
- Hand over: final instructions, files, test results and how to update it.
Pricing the work
Quote after reviewing the GPT. Use the free checker report as the basis for scope. We do not publish rate benchmarks because we have no verified data. If you would like a second pair of eyes on a client project, ask for an audit.
Not sure it is simple enough to do yourself?
Tell us what your GPT does, whether it uses Actions and how many files it has. We will say what will break and what a rebuild involves. The audit is free.
Request a free auditRelated guides
Sources
Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.