· buy
Agency vs product studio
“AI agency” and “product studio” are not standardized contract types. One provider may use either label while offering strategy, engineering, research, implementation or ongoing support. The buyer should compare the work and accountability in the statement of work rather than infer capability from the name.
Compare the delivery shape
- Discovery and product decisions: who turns an unclear problem into a workflow, user requirement and testable scope?
- Hands-on implementation: who writes and reviews the production code, connects internal systems and handles technical tradeoffs?
- Team continuity: will the people who present the proposal remain involved when the work reaches integration and launch?
- Operating handover: who owns incidents, model or prompt changes, user training and maintenance after the project?
- Buyer contribution: what access, staff time, data preparation and decisions must your team provide?
A strategy-led engagement can help when the organization has several candidate problems and needs prioritization. A product-oriented team may be a better fit when a product owner already has a workflow and needs a working slice inside a live system. A specialist partner may make sense for a narrow capability or integration. These are starting hypotheses; verify them with named roles, deliverables and acceptance rules.
Hypothetical example: a retailer has approved a returns-assistant pilot and needs it connected to the order system with a human review step. One supplier offers research workshops and a prototype; another offers integration and a production handover. The right choice depends on whether the remaining risk is product definition or delivery in the live environment. Compare what each will own and what your team must supply rather than comparing labels or deck quality. This example is illustrative, not a provider case study.
Make responsibility explicit
Ask who can make architecture decisions, who approves data access, how scope changes are handled and who supports the system after acceptance. Require clarity on code and configuration ownership, third-party dependencies, documentation, credentials and transition assistance. If the provider cannot state who is accountable for a failure after launch, the engagement boundary is incomplete.
Include an internal sponsor and technical reviewer in the selection process. A collaborative supplier still needs a buyer-side owner who can make decisions and help the team adopt the result. Compare proposals using a consistent scorecard and check transition planning before signature. See delivery options or discuss which work remains undefined.