Your app, one tab closer
SaaS Browser Extensions That Carry Your App's Login, Plan and Credits Into the Tab Your Users Already Have Open
Your customers pay for your web app and then spend the day somewhere else. They research in Google, sell in a CRM, write in a shared document. Your product waits in tab eleven, logged in and ignored. A companion extension carries one useful slice of it to the page they are already on.
November 16, 2026 · 9 min read
The short answer
A SaaS companion extension is a small browser add-on that puts one job from your web app onto the pages your users already work in. It signs in with the account they already have, spends the same plan or credits, and leaves billing on your own site. DataCram builds them from $1,500, depending on complexity, with a fixed written estimate before work starts.
On this page
- Tab eleven is where good software goes to be forgotten
- One account, two doors: how GatorCrawl's extension signs a user in
- Credits spent once, billing kept on your own site
- What the Chrome Web Store expects when an extension talks to your servers
- Building the companion, from shared login to a listing in your name
- When a companion extension is money your users will not notice
Tab eleven is where good software goes to be forgotten
Plenty of SaaS founders know the pattern. Signups climb, then daily use sags, because using the product means leaving the work to go find it. The user is on a search results page, a prospect's website or a supplier portal. Your app has the answer. Getting to it costs a tab switch, a login screen and the thread of thought. Most people skip it and guess.
A companion extension moves the answer to where the question is asked. Chrome's own getting started guide, read in November 2026, says extensions "enhance the browsing experience by customizing the user interface, observing browser events, and modifying the web." For a SaaS company that means a panel beside the page, a right-click item or a small bar of numbers, each one fed by your servers and paid for by the subscription the user already holds.
It is not a second product, and it should not look like the toolbar that came bundled with a free screensaver in 2009. It is a front door. The house is still your web app, with its database, its accounts and its billing. The custom browser extensions hub shows the other doors we build, from CRM capture tools to AI side panels.
One account, two doors: how GatorCrawl's extension signs a user in
DataCram built GatorCrawl Keywords, a keyword research web app, and then its Chrome extension. The extension has no login form of its own. Clicking its toolbar icon opens the options page, and the options page opens the web app's /extension/connect page, where the user is already signed in. The web app hands back a token, and the extension's service worker accepts it "only from the configured app origin," in the words of its own source code.

| What it does in GatorCrawl | What it means for your app | |
|---|---|---|
| Options page | Opens the web app's connect page, lets the user pick a country, shows "Connected as ... credits left" | Account status lives in one place the user can find |
| Service worker | Holds the user's extension token and calls the web app's API, one batch per Google results page | Your API key for data providers never leaves your server |
| Externally connectable messaging | Lets the web app pass the token to the extension after sign-in | No second password, no second account to support |
| Session storage | Keeps results for an hour so a page reload does not spend credits again | Users are not charged twice for the same lookup |
The full teardown, file by file, is in how we built the GatorCrawl extension. The point here is narrower: the extension is a thin client. Accounts, credits and data stay in the app, and the extension proves who the user is with a token the app issued.
Credits spent once, billing kept on your own site
GatorCrawl's site states the commercial model plainly: "Free to install from the Chrome Web Store. Lookups use your plan's credits." It adds that "One credit is one keyword with data." As of November 2026, the monthly plans are Starter at $19 a month, Pro at $49 a month and Agency at $129 a month, and each lists "Chrome extension on Google." The site's wording for the extension is "Included with every plan." Also as of November 2026, every plan starts with a 7-day trial for $5, charged up front and non-refundable, with 5,000 keyword credits for the week.
Notice what the store does not do in that arrangement: take the money. An archived copy of Google's payments deprecation notice, last updated in September 2020, says "The Chrome Web Store payments system is now deprecated" and that developers need to move to other ways to monetize. Google's accepting payment policy, read in November 2026, adds that "You must clearly identify that you, not Google, are the seller." Billing belongs on your site, through the checkout you already run.
What the Chrome Web Store expects when an extension talks to your servers
Chrome's Manifest V3 overview, read in November 2026, says an extension "can only execute JavaScript that is included within its package and subject to review by the Chrome Web Store." That rule sounds like a problem for SaaS and is the opposite. The store's Manifest V3 requirements list "Syncing user account data with a remote server" as an allowed remote call. Your code ships in the package; your data comes from your API. Our Manifest V3 explainer covers the rest of the format.
- A privacy policy, linked in the developer dashboard, whenever the extension handles user data. Google's privacy policy rule says it must be "accurate and up to date."
- A written reason for every permission. Google's privacy practices tab gives each permission its own justification field, and "Your disclosures are displayed to Chrome users."
- A plan for the publishing limit. Per Google's publishing guide, read in November 2026, a new publisher is "limited to a maximum of two published extensions."
- Patience with review. Google's review process page says, as of November 2026, "For most extensions, review is completed within a few days, but it can take up to a few weeks."
None of that is unusual for a company that already runs a web app. You publish a privacy policy now, and you explain your data handling to customers now. The extension adds a store listing to that list, and our Chrome Web Store review guide explains what the reviewers look for.
Building the companion, from shared login to a listing in your name
- 1
Pick the one job
Which question do users leave the page to answer in your app? That answer, and only that, becomes the extension. Chrome's quality guidelines ask for a single purpose that is "narrow and easy to understand."
- 2
Design the handshake
We add a connect page to your web app and an endpoint that issues extension tokens tied to the user's account, revocable from their account settings.
- 3
Write the permission plan
Every permission and every site the extension touches is listed with its reason before code exists. The plan becomes the store's justification text later.
- 4
Build for a worker that sleeps
Google's service worker lifecycle page says "Any global variables you set will be lost if the service worker shuts down." Tokens and state go to storage, not memory.
- 5
Connect to your API
The extension calls endpoints you own, with the user's token. Connections to your own API and systems go live the same day.
- 6
Submit under your account
Listing copy, screenshots, privacy disclosures and the submission are part of the build, published under your developer account so the listing is yours.
The build starts at $1,500, depending on complexity, with a fixed written estimate before work starts. One site and one panel sits near the bottom. Several sites, an in-page editor or support for more browsers moves it up, and the estimate says by how much. Updates after launch are quoted. The extension pricing guide shows what drives the number, and the custom Chrome extension development page lays out the whole offer.
When a companion extension is money your users will not notice
Some products should not have one. If your users do their work inside your app, an extension is a door to a room they never leave. If the job needs a large screen, a team view or a long form, a panel squeezed beside someone else's page will feel cramped. And if nobody has asked for it, the first request is cheaper to test with a bookmarklet or a share link than with a store listing.
Build the companion if
- Users copy data out of another site and paste it into your app
- The answer your app gives is short: a number, a status, a yes or no
- Usage drops because getting to the app takes a tab switch and a login
- Your plans or credits already meter the action the extension would perform
Keep the money if
- The work happens inside your app from start to finish
- The job needs a full screen, a team view or a long form
- Nobody has asked, and a bookmarklet would test the idea
- Your API is not stable enough for a second client yet
The fair version of that decision, with a table, is on extension or web app. If your product itself is still taking shape, micro SaaS development or a fractional CTO is the better first call, and our SaaS industry page covers the wider work. DataCram is a San Antonio, Texas studio that has built for the web since 1999 and works with companies across the US by phone, video and a shared project page. Read about us, see the work, or call (210) 346-0848.
Questions owners ask about custom browser extensions
Yes, and it should. GatorCrawl's extension opens the web app's connect page, where the user is already signed in, and receives a token that its service worker accepts only from the app's own origin. There is no second password. In the builds we do, that token can be revoked from the user's account settings, and the extension calls your API with it, so the same plan and permissions apply in both places.
Not with Google's own payments system. An archived copy of Google's notice, last updated in September 2020, says Chrome Web Store payments are deprecated. Bill on your own site instead, the way GatorCrawl does: the extension is free to install and lookups use the plan's credits. Google's accepting payment policy says you must make clear that you, not Google, are the seller.
Usually it uses yours. Your web app already has accounts, billing and data, so the extension calls your API with the user's token and shows the result. Manifest V3 allows that: the store's requirements list syncing user account data with a remote server as an allowed remote call. What it does not allow is downloading new JavaScript to run, so the extension's code ships in the package.
Decide what counts as a billable action before writing code, then design around it. GatorCrawl sends one batched request per Google results page and keeps results in session storage for an hour, so a reload does not spend credits again. Lookups that the user starts by hand, such as a right-click, are clearer still. Show credits left where users can see them.
You do. We recommend publishing under your own Chrome Web Store developer account, so the listing, its reviews and future updates belong to your company, not to us. Note from Google's register page that an account's email address cannot be changed after it is created, so open it with a company address you will keep.
From $1,500, depending on complexity, with a fixed written estimate before work starts. The store submission, privacy disclosures and the permission plan are part of the build. Connecting the extension to your own API goes live the same day. Updates after launch are quoted separately, and we state no review time, because Google says its review can vary.
Keep reading
- Case study, file by fileHow We Built the GatorCrawl Keywords Chrome Extension: Two Permissions, One Site and a Web App Behind ItA Chrome extension case study, file by file: the manifest, the content script on Google, the service worker, the options page and the two permissions.
- Getting paid, plainlyHow to Monetize a Chrome Extension Now That Google's Payments Are Gone: Accounts, Trials, Credits and the Ad RulesChrome Web Store payments are gone. How paid extensions bill now: your own site, accounts, trials and credits, plus Google's rules on ads and affiliate links.
- The offer, part by partCustom Chrome Extension Development Services: Discovery, a Permission Plan, the Build and a Listing in Your NameHire a Chrome extension developer for discovery, a written permission plan, a Manifest V3 build, store submission and a handover under your account.
- Your data, on their pageCustom SEO Chrome Extensions That Paint Your Own Numbers Onto Google's Results PageBuild an SEO extension that shows your own keyword, rank or client data on Google results, on one site, with two permissions. From $1,500, yours to own.
- Capture, minus the clipboardCRM Chrome Extensions That Save a Contact in One Click, Straight Through Your CRM's APIA Chrome extension that saves the contact on your screen to your CRM in one click, through the CRM's API, with no copy and paste. From $1,500.
- AI beside the pageAI Chrome Extensions That Summarize, Draft and Extract From the Side Panel, With Your API Keys Kept on Your ServerAn AI side panel that summarizes, drafts and extracts from the page you are on, using your own AI provider through your server. From $1,500, owned by you.
- Everything in Custom Browser ExtensionsSee the section
From the Insights desk
- Nine Industries, Nine Different Websites — and Why the Template Fits None of ThemA plumber, a dentist, and a personal injury attorney walk into a template and all get the same five pages with different logos. A website is not a brochure — it is a machine with a job, and the job is different in every trade.
- The Optimizely Hack Was Not an Outage. It Was a Delivery.On November 16, a flaw in Optimizely's sign-up flow let an attacker slip card skimmers, wallet swappers and iPhone exploits into the testing scripts of 178 organizations, the BBC and Zoom among them. How it happened, what it did, and the fixes, in order.
Put one job from your app where your users already work
Tell us what your app does and which page your users keep leaving to use it. We reply with a permission plan and a fixed written estimate, or with the reason an extension would not pay its way.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.