Define what is being sold
Start with the exact store URL and item ID. Identify the current publisher, product purpose and published version. Record which browsers and release packages are included.
Ask for an inventory covering source code, build instructions, listing assets, domains, backend services, integrations and analytics access. Mark each item as included, excluded or requiring a separate arrangement.
Keep the extension itself distinct from dependencies controlled elsewhere. A working listing and an archive of code do not describe who will operate the backend or provide support after transfer.
Review dated audience and revenue evidence
For each figure, ask for the original report or export, its definition and its period. Use matching periods when comparing records:
| Area | Evidence | Review question |
|---|---|---|
| Audience | Dated store and product reports with metric definitions, filters and acquisition sources | What counts as an installation, a user or a useful product action? |
| Revenue | Records for the stated product and period, with the source and revenue model identified | Are recurring receipts, one-off receipts, refunds and unconfirmed amounts separated? |
| Costs | Hosting, APIs, billing fees, support and other operating records | Which costs recur, and which costs belong to the handover or a proposed change? |
Chrome’s metrics documentation says its Users statistic captures installations rather than product activity. Keep that distinction in an audience review; the store Users glossary entry provides a short definition.
Attach every audience claim to this item and its dated source. General portfolio figures or another product’s rating are not evidence for the extension being reviewed.
Keep existing receipts separate from proposed revenue. A monetization review can examine model fit and implementation requirements; it does not supply evidence of income the product has already earned. Leave unsupported figures unverified.
How the findings inform the price discussion
Compare verified receipts with recurring costs for the same period. Read usage across comparable periods to see its trend. For technical dependencies, identify the work and assets needed to keep the product running after handover.
Illustrative comparison: two extensions show the same verified revenue. One has higher recurring costs and needs backend work before handover. Record those costs and the required work separately before comparing the proposed prices.
| Review finding | Clarify before discussing the price |
|---|---|
| Illustrative comparison above: equal verified revenue, different recurring costs and backend work | Which receipts and costs recur over the same period? Who covers the required work, and is it included in the proposed price? |
| Usage rises, stays stable or falls across comparable periods | Do the metric definition and filters match? What does the recorded trend show that a single audience total would miss? |
| The product depends on external services or needs maintenance | What must be transferred or changed for continued operation? Which assets, work and responsibilities are included, and which need a separate agreement? |
Assess maintenance and transfer work
Review the current release, dependencies and build instructions. Ask the receiving team to record whether it can reproduce the intended build and complete the main user action in the target browser.
List known failures, permission requirements, external services and the responsibility for ongoing support. Keep maintenance needed for the current product separate from features a buyer wants to add. Scope any extension development work independently.
Prepare the store and project handover using the Chrome extension ownership transfer checklist.
Build a buyer review checklist
Use this record for the particular asset:
Store URL and item ID:
Publisher and current release:
Included assets and exclusions:
Audience metric, source and period:
Revenue records and period:
Operating costs and period:
Build and main-action check:
Maintenance and proposed changes:
Store-transfer and project-handover scope:
Unverified claims and missing records:
Responsible person and next check:
Before discussing terms, confirm that each important claim has a source and date, that received material has its own verification status, and that the open work has an owner. Agree the included assets and responsibilities in the contract.
Extcorp discusses its extensions for sale privately, with availability and supporting evidence considered for the specific product. Send your browser, product criteria and the questions you want to verify.
Discuss an extension acquisition
Extcorp is independent of Google and Chrome Web Store.

