A small team revises a research dossier every week and needs shared instructions, stable source sets, and predictable document access over many conversations. Here is a scenario-based comparison using documentation checked on 2026-10-25, not an independently tested vendor ranking. The region, plan, exact model version and price are unspecified unless a first-party document establishes them; unmatched performance claims stay unknown.
Audience: research managers. Evidence checked: 2026-10-25. Editorial status: ready. Comparison scope: named scenario; region, plan and model/version parity require separate confirmation.
Project is a governance unit, not just a folder
ChatGPT Projects documents project-specific files, chats and instructions; Claude Projects likewise describes persistent knowledge and project instructions. A Gemini file-upload conversation should not be silently equated to either provider’s project workspace. The critical question is where the source set is defined, who can change it, and what a collaborator sees. Make a table of file owner, uploader, revision date and reviewer before testing responses.
Test source drift over four updates
Week one, upload a clear baseline. Week two, replace one contradictory report. Week three, revoke a collaborator. Week four, correct a recurring instruction. Ask the same three questions after each change and inspect whether answers reference the latest authorised material. A confident answer using a deleted or old document is a failure. Compare the content boundary, not the cosmetics of chat sidebars. Document what administrators can audit and what an end user can export.
Memory and sharing deserve separate review
A product may remember a project conversation without promising that another product’s project data has an identical isolation model. Shared project settings and retention also vary by subscription and account. The ChatGPT guide documents project-only memory and separate sharing settings; Claude describes project knowledge use. For Gemini, the sourced file-upload guide does not establish equivalent long-running project governance, so cross-product equivalence remains unknown until an account-level configuration is checked.
When an API-backed repository makes more sense
If analysts need document version IDs, immutable citations and automatic permission removal, external versioned storage plus a retrieval service may be more auditable than manually uploaded project files. That route adds indexing, access-control and operations costs. A low-cost consumer subscription does not remove this architecture decision. Treat the app as a research interface and the document store as the authority.
What an actual buyer pilot should measure
Freeze the relevant source files, release identifiers, evaluation prompts, operator permissions and reviewer identities. Use the same rights-cleared materials for every candidate; separate tasks that cannot be configured equivalently instead of forcing them into a single ranking. Review the resulting artifacts against objective acceptance criteria specific to this decision: source traceability, error handling, rework, permission boundaries and whether a competent human approves the final deliverable. Record rejected attempts as well as successful examples. This is a proposed method, not a claim that these vendors have been tested by this publication.
Costs and unresolved evidence
Do not equate an interactive assistant seat, media credit, billable character, hosted token or self-hosted GPU hour. To estimate actual spending, count accepted results, failed attempts, revision cycles, human review, security operations and export/storage costs. AI 10 must supply dated provider-specific pricing records with tier, unit, currency and region; in their absence, monetary figures and claims of price parity remain unknown. Account-level availability and contract addenda require verification. No universal winner score or fictitious hands-on rating is assigned.
Decision for this scenario
Prefer a project workspace for small stable teams only after testing updates and membership; use a versioned repository when auditability outranks chat convenience.
The article has documented feature and policy evidence but no independent hands-on performance test. Reconfirm plan, region and terms before publication; editorial ready is not WordPress publication approval.
Sources and Further Reading
Original provider and policy sources are listed here. Source-to-claim identifiers are maintained separately in the editorial CSV rather than inserting numbered references into the main text. Where documents are mutable, the access date describes the verification point only.
- OpenAI — Projects in ChatGPT (checked 2026-10-25)
- Anthropic — What are projects? (checked 2026-10-25)
- Google — Upload and analyze files in Gemini Apps (checked 2026-10-25)