An established product with an existing audience
Extcorp offers its own established browser extensions with an existing audience. A buyer can develop and monetize the acquired extension as a traffic channel. Future results still depend on product quality, platform rules, audience fit and the chosen monetization model.
Established extension
Review how the current product fits your intended use and what would need to change.
Active users
Ask how activity is defined and which dated evidence supports the figures shared privately.
Support after acquisition
Discuss growth, monetization and technical work as a separate scope.
Still choosing a route? Compare buying an established extension with commissioning development before preparing a detailed acquisition request.
How the private discussion works
- Describe the acquisition criteria. Share the browser, category, goals and commercial boundaries; Extcorp will confirm whether a relevant opportunity can be discussed.
- Review evidence privately. After agreeing disclosure or an NDA, the buyer independently checks audience trends, analytics, code, permissions, store history, ownership and IP.
- Document the transfer. The parties record commercial terms, payment, asset transfer and any post-transfer support in separate agreements.
Evidence to review before a transfer
For each material claim, ask for its source and date under the agreed disclosure terms. Keep received evidence, your own checks and unresolved questions separate.
| Area | Evidence to request | Check before deciding |
|---|---|---|
| Audience | A dated report with the metric definition, period, filters and acquisition sources | Compare matching periods. Separate store installation counts from evidence of product use. |
| Current release | Listing and extension ID, package and manifest versions, plus dated fresh-install and update checks in the intended browser | Record the browser version tested and any failed or missing checks. Confirm access to source code, build instructions and required backend or API services. |
| Transfer scope | An agreed inventory of code, store items, assets and dependencies included in the transfer | Identify what remains with the seller, what still needs work and which support requires a separate agreement. |
Chrome’s store Users statistic does not measure activity inside the extension. Google’s metric definitions explain that distinction.
For a Chrome extension, check its current store availability and manifest version. Google’s support timeline records the removal of the remaining Manifest V2 extensions from Chrome Web Store on 31 August 2026. A past audience figure alone does not establish the condition of the current release.
Mark missing checks as “not checked”. Buyers carry out their own review; any repairs or maintenance need a separate scope.
Prepare a private extension proposal
If you own an extension and want to propose it, start with the store listing, browser, your relationship to the product and its main use. Add the reason for considering a sale and the materials you are prepared to discuss privately. Audience figures need a definition, source and date. State whether you have reliable revenue and cost records. If a figure is unavailable, explain whether it was not measured or the supporting record is missing.
Record what is included and what remains open
For each asset, record whether it is included, excluded or needs a separate arrangement. Identify the receiving party and the check that would establish usable access. Receiving material and verifying it are separate steps.
| Asset or dependency | Question for the agreed inventory |
|---|---|
| Store item | Which exact item and developer role are involved, and what confirms the receiving party's access? |
| Source and build materials | Which version, dependency records and instructions are included, and can the recipient reproduce the intended build? |
| Domains and listing assets | Which domains, descriptions, images and rights to use them are included or remain with the owner? |
| Backend, APIs and billing | Which services must continue, who controls them and what needs a separate agreement or migration? |
| Analytics and ongoing responsibility | Is the recipient receiving a historical export, ongoing authorized access, or both? Who resolves remaining issues? |
In an illustrative handover record, the source archive might be received while the backend owner is still undecided. The source row can say “received”; the backend row remains “unresolved”. A dated analytics export also leaves future access as a separate question. Keep a responsible person and next action beside each open item.
Transfer the Chrome Web Store item
Google’s registration guide documents transferring an item to another developer account. Prepare that step separately from source code and other assets:
- Open One Stop Support and choose “My item”, then “I want to transfer my item”.
- Check the current eligibility requirements. The form requires a registered receiving account and a published item without violations. Prepare the item ID and original and destination publisher emails.
- The authorized publisher submits the request and confirms it from the original publisher email.
Recheck the form before an actual transfer. Record the request, confirmation, support outcome and verified destination access separately. In an illustrative record, “request submitted, confirmation pending” leaves the store-item transfer open. A source archive already received can have its own completed row.
Send a proposal to start a private conversation. Sending details does not create a public listing, brokerage engagement, valuation or buyer commitment. Any technical handover work and later monetization changes require their own agreed scope.
Support after acquisition
Depending on the project, you can discuss:
- store listing, localization and onboarding;
- monetization and technical integrations;
- adaptation for Chrome, Microsoft Edge and Firefox;
- fixes, maintenance and new feature development.
Audience, revenue and store performance can change after transfer. Buyers complete independent technical and commercial due diligence before signing.