A new way to use your product
Keep your product and customer relationships. Give customers a practical way to complete valuable work from ChatGPT and Codex.
Product Distribution / application
Your product. In your customers’ workflow.
Turn your existing product into a secure, useful plugin for ChatGPT and Codex. We connect the workflow, test the account experience, and prepare your package for marketplace review.
Build once. Own the result.
You receive the source, package, verification evidence, and handover documentation. Work is scoped around an outcome, with clear acceptance criteria.
Start small. Earn expansion.
Launch one useful workflow or connect a broader customer journey. Expand after you can see real usage and a reason to invest.
Chapter 1 · The knot
A big move. Too many moving parts.
The ambition is clear. The path feels tangled.
Chapter 2 · The crew
Hand us the complexity.
We align the people, build the solution, and keep you in the loop.
Chapter 3 · Clear water
See progress. Breathe easier.
Clear decisions, working delivery, and evidence against your goal.
Make it tangible
From your goal to an agreed result.
An illustrative delivery path. Your scope, review checkpoints, and acceptance criteria are agreed before kickoff.
01 · Your starting point
Customers want to use your product from ChatGPT or Codex.
02 · The work we deliver
workflow definition and acceptance criteria · MCP tools and reusable plugin instructions
03 · The target outcome
A defined customer workflow works end to end.
Process
How the engagement works
A focused delivery path with clear checkpoints, customer responsibilities, and agreed evidence of completion.
- Step 1
Choose the customer workflow, confirm API readiness, and agree scope and success criteria.
- Step 2
Build the tools and authentication path against your existing product.
- Step 3
Test successful use, denied access, expired credentials, and failure recovery.
- Step 4
Complete the agreed review cycles and prepare the package for submission.
- Step 5
Hand over source, runbooks, and evidence; agree any ongoing care separately.
The rhythm behind the method
At agreed checkpoints, we review evidence, resolve decisions, deliver the next increment, and measure again. Every checkpoint leaves a named owner, next action, and review date.
- 1. Review evidence
- 2. Resolve decisions
- 3. Deliver the next increment
- 4. Measure and adapt
Choose your launch
Start focused. Expand with confidence.
Three clear starting points. Each includes a defined base scope, two consolidated customer review cycles, handover, and a 30-day defect warranty. Final scope and price are agreed before kickoff.
Launch
Starting at
$7,500
USD · one-time engagement
A focused, budget-conscious entry into the ecosystem.
- One customer workflow and up to five tools
- One existing API and one existing, compatible authentication path
- Essential workflow, permission, and failure testing
- Plugin packaging and submission preparation
- Source ownership and handover documentation
Recommended · Connected
Connected
Starting at
$15,000
USD · one-time engagement
Connect the customer journey, with secure account linking and a real-user pilot.
- Everything in Launch, expanded to up to three workflows and ten tools
- OAuth account linking using one existing identity provider
- Permission mapping, expired-token handling, and recovery
- Pilot with up to five customer-provided users
- Activation and workflow-success measurement
Enterprise
Starting at
$30,000
USD · one-time engagement
Launch with organization controls and operational evidence.
- Everything in Connected, expanded to up to five workflows and fifteen tools
- Organization and role access mapped to existing product controls
- Approval gates for agreed sensitive actions
- Bounded agent-action audit and operational monitoring
- Deployment documentation and operational handover
Add only what you need
- Additional customer workflows and tool bundles
- Additional product integrations or backend API work
- Custom plugin interface and richer interaction
- Additional identity providers or enterprise SSO mapping
- Access-dependent Sign in with ChatGPT integration
- Expanded pilot, rollout, or support coverage
Add-ons and scope changes are quoted separately and begin only after your written approval. Your agreed base scope keeps its agreed price.
Keep the connection working
Plugin Care starts at $1,000/month for agreed compatibility checks, authentication monitoring, incident triage, and bounded maintenance. Coverage, response expectations, and included changes are specified in your care agreement.
Third-party hosting, identity-provider, and API usage costs are separate. Confirmed scope, review checkpoints, and delivery milestones are agreed before kickoff.
Best for
- ✓ Software companies with a usable API and an existing customer base.
- ✓ Product leaders adding conversational access to a valuable workflow.
- ✓ Teams that want a focused launch before investing in wider integration.
Not for
- — A new backend or product built from scratch inside the base package.
- — Guaranteed marketplace approval, traffic, revenue, or partner access.
- — Unbounded workflows or open-ended development.
Deliverables
workflow definition and acceptance criteria
MCP tools and reusable plugin instructions
authentication and permission tests
plugin package and listing preparation
handover documentation and verification report
Evidence
How we will measure progress.
These are measurement priorities for the engagement, not claims of past customer results. We agree baselines and success criteria with you.
- workflow completion
- successful account connection
- tool error rate
- repeat pilot usage
Read the full engagement details
A useful workflow is the launch
Customers should be able to complete the agreed task, understand what access they grant, and recover when something fails. Our acceptance evidence covers those behaviors before handover.
Clear scope. Controlled expansion.
Your signed statement of work defines the workflows, tools, dependencies, review checkpoints, and acceptance criteria. Added scope is priced before it starts. The launch engagement is purchased directly from Agency FTW; marketplace payment capabilities and partner-only features are not assumed.
Payment milestones
50% before kickoff; 30% after the working demo meets agreed milestone criteria; 20% after final acceptance and before source, deployment, and operational handover. Customer review precedes final payment; handover follows cleared funds. Marketplace approval is not a payment milestone. Acceptance criteria, review windows, and defect resolution are specified in the statement of work. Add-ons have separately agreed payment terms.
Ways to expand
- Upsell
- Additional workflows, integrations, and organization controls
- Cross-sell
- Revenue workflow implementation or agent operations
- Continuity
- Plugin Care starting at $1,000/month
FAQ
How do milestone payments work?
50% before kickoff; 30% after the working demo meets agreed milestone criteria; 20% after final acceptance and before source, deployment, and operational handover. Customer review precedes final payment; handover follows cleared funds. Marketplace approval is not a payment milestone. Acceptance criteria, review windows, and defect resolution are specified in the statement of work. Add-ons have separately agreed payment terms.
Why does every package say starting at?
Each price covers its defined base scope. Additional workflows, integrations, interface work, or organizational requirements are quoted separately. Scope changes require your written approval before additional work starts.
Do you guarantee marketplace approval?
We commit to a tested package prepared for review against the applicable requirements. OpenAI controls acceptance, availability, and review timing; discovery, adoption, and revenue are not guaranteed.
Is Sign in with ChatGPT included?
Standard OAuth account linking is included in Connected and Enterprise. Sign in with ChatGPT is a separate, access-dependent integration available to selected commercial partners. We can scope it if your application is eligible; partner access is not included or guaranteed.
What do we need before kickoff?
A usable API, a test environment, a product owner, and access to the agreed authentication setup. New API development or substantial backend repair is separate scope.
How long does delivery take?
We agree milestones after reviewing your API, authentication, and workflow. Reviews, customer dependencies, and approved scope changes affect the schedule. You receive clear checkpoints and a revised plan when a dependency changes.
What happens after handover?
Each launch includes a 30-day defect warranty for the accepted scope. Ongoing maintenance is available through Plugin Care under a separate agreement; new functionality and platform-driven changes are separately scoped.
Next step
Move the business forward. We’ll build what it takes.
Share your goal, current workflow, and constraints. We’ll confirm fit, scope, and the next step before you commit.
Plan your engagement