The offer, part by part

Custom Chrome Extension Development Services: Discovery, a Permission Plan, the Build and a Listing in Your Name

A request for an extension usually arrives as a feature list. We send back two short documents: the job in one sentence, and a list of permissions brief enough to read aloud. Everything on this page follows from those two pieces of paper.

November 16, 2026 · 10 min read

acmeroofingsupply.com · extension pre-submission checks
Checking a contact capture extension before the store sees it
One unused permission caught and removed before review
  1. Manifest V3 read: name, version, description, icons present
  2. Single purpose: save a contractor contact to Acme CRM
  3. Permission "tabs" declared but never called in the code
  4. Removed "tabs"; plan is now storage and activeTab
  5. No remotely hosted code found in the package
  6. CRM writes routed through api.acmeroofingsupply.com
  7. Privacy disclosures match the permission plan
Illustrative: a sample pre-submission check for a fictional roofing supplier's CRM extension

The short answer

DataCram's Chrome extension development service runs in six parts: discovery, a written permission plan, a fixed estimate, a Manifest V3 build with the logic on your server, Chrome Web Store submission with the privacy disclosures, and a handover under your own developer account. Builds start at $1,500, depending on complexity. Connections to your CRM, web app or AI provider go live the same day.

On this page
  1. Discovery starts with one sentence, not a wish list
  2. The permission plan: every line the install screen will show
  3. A fixed estimate, from $1,500, before anyone writes code
  4. The build: Manifest V3, with the thinking done on your server
  5. Testing in a clean browser before the store ever sees it
  6. Store submission: listing, disclosures and a reason for every permission
  7. Handover: the account, the code and the next update are yours
  8. Requests we redirect, and where we send them

Discovery starts with one sentence, not a wish list

Most extension briefs arrive as a pile: capture leads, show prices, summarize pages, maybe a dashboard for the boss. The Chrome Web Store reads that pile differently. Its quality guidelines, read in November 2026, say an extension "must have a single purpose that is narrow and easy to understand," and that clearly separate features belong in separate extensions. So discovery begins by writing that purpose in one sentence, the way the dashboard's Privacy tab will later ask for it.

Then come the questions that decide the build. They are about the job, because the technology follows from the job:

  • Which sites does it act on: one, a short list, or any page the user chooses?
  • Does it need to see the page all the time, or only when someone clicks?
  • Where does the data go: your CRM, your web app, a spreadsheet, an AI model?
  • Who signs in, and does it share an account and billing with an app you already run?
  • Which browsers matter at launch, and which can wait a release?
  • Does an existing extension, a bookmarklet or a plain web page already do this?

The last question ends some projects on the first call. If a maintained tool on our SEO Chrome extensions list or a screen in your web app covers the job, we say so and stop. The extension or web app comparison shows how we make that call, and the browser extensions hub lists every kind we build.

The permission plan: every line the install screen will show

Before any code, you get a short document listing each permission the extension will request, the reason, and the warning a user will see. Chrome's permission warnings guide explains that some permissions show no warning and others trigger one the user has to allow. Its permissions list gives "tabs" the line "Read your browsing history." and gives storage and contextMenus no warning line at all. A plan written in that vocabulary tells you, before you spend a dollar, what your customers will be asked to accept.

Warm shallow-focus desk with a laptop showing a blank glowing screen, an open notebook of ruled blank lines, a pen and a coffee cup, one hand on the trackpad
The permission plan is written before the code, so nobody is surprised by the install screen.
Four ways to ask a browser for access, and what each costs in trust
ApproachWhat it doesWhen we use it
Required permissionsGranted at install; any that carry a warning show it on the install screenOnly for what the core job needs every single time
Optional permissionsRequested at run time through the chrome.permissions API, so users see whyFeatures some users want and others never touch
activeTabTemporary access to the current tab when the user invokes the extension, with no install warningTools that act only when clicked
Host access to named sitesAccess to the addresses listed; Chrome notes changes may trigger a warningTalking to your own app's API, as GatorCrawl does

GatorCrawl Keywords, the extension we built for our own keyword app, is the model. It requests storage and contextMenus, host access to its own app, and a content script on Google's results pages. The GatorCrawl case study explains each line. The plan protects you later too: Chrome says an update that adds a warning-bearing permission disables the extension until the user accepts it, while one that adds optional permissions does not. More in permissions and privacy.

A fixed estimate, from $1,500, before anyone writes code

With the purpose and the permission plan agreed, you get one price in writing. Custom browser extensions start at $1,500 to build, depending on complexity. An extension that adds one button and sends one record to your CRM sits near that floor. One that touches several sites, signs users into your app, shares billing and ships to four browsers costs a good deal more. Your estimate names the band you fall in and the features that put you there.

The lines on a DataCram extension estimate
ItemWhat you can check it against
PurposeThe single-purpose sentence, worded as it will appear in the store's Privacy tab
PermissionsThe plan, line by line, with the warning each one shows users
ConnectionsEach system the extension reaches through your server; connections go live the same day
BrowsersChrome first, and which of Edge, Firefox and Safari are in scope
Store workListing text, images, the privacy policy link, data disclosures and a justification for each permission
PriceA single number covering the build described above
After launchUpdates and maintenance, quoted separately when you need them

Anything you think of later gets its own written price before work on it begins. Our extension pricing guide explains what moves the number and what each store charges, and how long a build takes explains why we quote a price and never a launch date.

The build: Manifest V3, with the thinking done on your server

Every extension we write uses Manifest V3, which Chrome's migration docs call "the latest version of the extensions platform." Each part has one job, and we keep it that way.

  1. 1

    The manifest

    The one file Chrome requires by name, manifest.json, declares the permissions, the scripts and where they run. For the store it also needs icons and a description of at most 132 characters.

  2. 2

    The service worker

    The background event handler. Chrome normally stops it after 30 seconds of inactivity, so anything worth keeping goes into storage, never into a variable that disappears with it.

  3. 3

    Content scripts

    Code that reads and changes only the pages the plan allows, inside what Chrome calls an isolated world, private from the page and from other extensions.

  4. 4

    The interface

    A toolbar action, an options page, a right-click item or a side panel, picked for the job rather than added because Chrome happens to offer it.

  5. 5

    Your server

    Manifest V3 runs only JavaScript shipped in the package, so business rules, AI prompts and API keys live on a server you control, which store policy permits for syncing account data.

That last step is where integrations happen. The extension talks to your server, and your server talks to the CRM, the web app, the AI model or the payment processor. Those connections go live the same day. Our API integration service and AI integration service handle the server side, and Manifest V3 explained covers the platform rules.

Testing in a clean browser before the store ever sees it

We test the packaged extension, not just the source. Chrome's end-to-end testing guide describes building the package and loading it into a browser, using libraries such as Puppeteer, Playwright, Selenium and WebDriverIO. We run it in a fresh profile with nothing else installed, then on the real pages it is meant for.

  • Every path through the job: the right page, the wrong page, no network, an expired login
  • The service worker after it has gone dormant, to prove nothing relied on memory
  • The install screen, read the way a stranger would read it
  • An update that adds a permission, run through Google's Extension Update Testing Tool, so the prompt users would see holds no surprise
  • Each browser in scope, since Firefox and Safari differ from Chrome in the ways our cross-browser guide records

Testing finds problems. It does not prove there are none, and we will not claim otherwise. Chrome also lets a publisher release a beta or testing version alongside the production listing, which suits teams that want staff to try each build before customers do.

Store submission: listing, disclosures and a reason for every permission

Submission is part of the build, not an extra. Google's publishing guide describes the dashboard: a Privacy tab where you declare the single purpose and how user data is handled, a Distribution tab for countries and visibility, and a Test instructions tab for reviewer credentials when they are needed. Each permission gets its own justification field, and we fill every one from the permission plan.

If the extension handles user data, the store's privacy policy rule requires an accurate policy linked in the dashboard, and its disclosure rule requires prominent notice and consent before collection. We draft the disclosures from the plan. Your counsel approves the policy itself, because we are a web studio, not a law firm.

Handover: the account, the code and the next update are yours

We recommend the extension be published under your company's own developer account, and the code is yours. Google's registration page warns that an account's email address cannot be changed once created, so we ask you to register with a company address that will outlast any one employee. Chrome requires 2-Step Verification before an account publishes or updates anything, and its security guidance prefers a security key.

You receive the source, a plain note on what each file does, the permission plan as shipped, and a walkthrough with whoever will publish updates. Updates and maintenance after launch are quoted when needed. Our page on extension maintenance explains what browser releases and policy changes tend to require, and the SaaS companion guide covers shared logins and billing.

Requests we redirect, and where we send them

An existing extension does it

Install it and keep the money. We will tell you what to check on its listing first, starting with the permissions and who publishes it now.

It is really an application

Portals and multi-user tools that never need to see another site belong with custom software development.

Nobody owns the product plan

A fractional CTO can decide what to build, and in what order, before anyone builds it.

The work happens inside WordPress

A custom WordPress plugin is the same small-program idea, living inside your own site.

If your idea survives those four cards, ring (210) 346-0848 or fill in the short form here. The first reply asks the discovery questions above, by email or on a call. Our about page explains who answers: a San Antonio web studio, building for the web since 1999.

Questions owners ask about custom browser extensions

Tell us the job as you would explain it to a new hire, the sites it should run on, and the systems the data should land in. When we get to the build, we need API access to those systems and a company-owned Chrome Web Store developer account. Discovery turns that into a single-purpose sentence, a permission plan and a fixed written estimate before any work starts.

Often. We read the code and the manifest first and say plainly if it is worth finishing, fixing or starting over. An old Manifest V2 extension needs a rebuild: Chrome's timeline says the remaining ones were removed from the store on August 31, 2026. We also check who controls the developer account, since that decides who can publish updates.

Yours. We recommend every client publish under the company's own developer account, so the listing, the users and future updates stay with you whoever maintains the code. We do the submission work inside your account. The code we write for you is yours as well.

Yes, through your server. The extension holds a token and asks your app what the user may do, the way GatorCrawl Keywords shares its web app's account and credits. Billing stays on your own site. Connections to your app, CRM or payment processor go live the same day. Our SaaS companion page shows the pattern.

Any extension that handles user data does. The Chrome Web Store policy requires an accurate, current privacy policy linked in the developer dashboard, plus prominent disclosure and consent before data is collected. We draft the disclosures from the permission plan; your counsel approves the policy.

The rejection names a violation ID made of a color and an element, such as Purple Potassium for excessive permissions. We fix the cited problem and resubmit. Updates and resubmissions go through the same review as a first submission, so we cannot promise timing, but a narrow permission plan and complete disclosures remove the most common causes before the first submission.

Keep reading

Free · No obligation

Start with the one-sentence job

Tell us what the extension should do and where the data should go. We answer with a few pointed questions, then a permission plan and a firm price in writing. Or we tell you that a cheaper tool already exists.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote