Fixed quote after a free call

Chrome extension development for SaaS companies

Many SaaS products win when they show up where customers already work. We design and build a Manifest V3 Chrome extension that connects to your API, adds your product to pages such as Gmail, a CRM or any web app, and passes Chrome Web Store review with a clear single purpose and data policy. Our team builds and ships its own extension, so we know the review process. Projects typically cost $6,000 to $15,000 and take seven to ten weeks.

The problem

Why SaaS teams need a Chrome extension development partner

Customers ask for your product inside the tools they live in: clip a contact from a web page, see account context next to an email, capture a bug with a screenshot. Your core team is busy on the product, and extension work is a different discipline with its own review process.

Chrome has moved fully to Manifest V3. Background pages are replaced by service workers that run only when needed, and remotely hosted code is no longer allowed, so everything must ship inside the reviewed package. Data use is limited to the single purpose you declare.

What we build

What our Chrome extension development includes

Single-purpose design

A clear job for the extension that matches your product and passes the single-purpose rule.

Manifest V3 build

Service worker, content scripts and minimal permissions, written in TypeScript with a modern build setup.

Secure sign-in to your API

OAuth or token sign-in to your product, with tokens stored safely and scoped to what the extension needs.

In-page UI

A side panel, popup or in-page widget styled to your brand that does not break the host page.

Store listing and policy pack

Listing copy, screenshots, privacy disclosures and the Limited Use statement prepared for review.

Release pipeline

Versioning, automated packaging and a staged rollout so updates do not surprise users.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    User installs

    A customer installs from the Chrome Web Store and signs in to your product.

  2. 02 Automated

    Extension acts on page

    The extension reads only what its single purpose needs and calls your API.

  3. 03 Automated

    Data synced

    Results appear in your product and in the extension panel.

  4. 04 Team review

    Your team reviews

    Your product team reviews telemetry, store reviews and support tickets each release.

  5. 05 Account owner or team lead decides

    Product decisions

    Features, permissions and data use are decided by your product lead.

How it behaves

How the companion extension behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the user sees

  • Your product in a side panel next to the page they are on
  • A one-time sign-in to their account
  • Clear permission requests that match what the extension does

What your team sees

  • Telemetry and errors per release
  • Store listing and reviews in your developer account
  • A repository and pipeline they can take over

What the extension does

  • Reads only what its single purpose needs
  • Calls your API with scoped tokens
  • Updates through staged rollouts

Edge cases and fallbacks

Host page changes its layout
The extension degrades to the side panel and errors are reported so we can patch it.
Token expired
The user is asked to sign in again; no data is lost.
Store review asks for changes
We respond, adjust permissions or disclosures and resubmit.
Your API is down
The panel shows a clear message and queues nothing sensitive locally.

Architecture

A SaaS companion Chrome extension at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Web page Gmail, CRM, any site Content script Minimal access Service worker Manifest V3 Your SaaS API OAuth scoped Side panel Your product UI Product lead Permissions, scope
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 The content script reads only the page details the extension's single purpose needs.
  2. 2 The Manifest V3 service worker handles sign-in and calls your SaaS API with scoped tokens.
  3. 3 Results show in a branded side panel and sync to the product.
  4. 4 Your product lead approves permissions, data use and every release.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Chrome extension & companion integrations project plan

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    About 1 week

    User jobs, target pages, API readiness, permissions and store policy fit.

  2. 02

    Design

    About 1 week

    UX for the panel or widget, sign-in flow, data disclosures and listing plan.

  3. 03

    Build

    3 to 5 weeks

    Service worker, content scripts, UI, API calls, tests and packaging.

  4. 04

    Test

    About 1 week

    Cross-site testing, permission review, security checks and beta with a few customers.

  5. 05

    Store review and launch

    About 1 week

    Listing, privacy fields, submission and staged rollout.

  6. 06

    Support

    Ongoing

    Updates for Chrome changes, host page changes and new features.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Chrome Manifest V3 TypeScript React or Svelte for the panel OAuth 2.0 to your API Chrome Web Store developer account GitHub Actions for packaging

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    User jobs, permissions, UX and policy fit.

    $600 – $1,500

  • UI and design system

    Side panel or widget on your brand.

    $1,200 – $3,000

  • Build

    Service worker, content scripts, API and tests.

    $2,800 – $7,500

  • Integrations and sign-in

    OAuth, API endpoints and telemetry.

    $700 – $1,800

  • Testing, store review and launch

    Beta, listing, submission and rollout.

    $700 – $1,200

  • Total project estimate

    $6,000 – $15,000

Optional monthly care after launch is quoted with your proposal. Fixed quote after discovery. The one-time Chrome Web Store developer registration fee is paid by you. Edge and Firefox versions can be added.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Chrome Web Store: One-time developer registration fee, paid by you.
  • Hosting: Your existing API and hosting; the extension adds little load.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Manifest V3 rules

Manifest V3 moves background logic to service workers and removes the ability to use remotely hosted code, so all code ships in the reviewed package.

Source: developer.chrome.com

Chrome Web Store Limited Use

Use of user data is limited to providing or improving the single purpose, browsing activity collection is generally prohibited outside described features, and a public Limited Use statement is required.

Source: developer.chrome.com

Developer registration

Publishing requires a Chrome Web Store developer account with a one-time registration fee, paid by you so the listing is yours.

Source: developer.chrome.com

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Chrome extension & companion integrations questions, answered.

Yes. We design, build, publish and maintain Manifest V3 extensions that connect to your product API, and we ship and maintain our own extension, so we work through store review regularly.

It varies by extension, permissions and policy fit, so we plan time for it and keep permissions minimal to avoid extra scrutiny. We do not promise a review time we do not control.

You do. It is published under your developer account and we hand over the repository, build pipeline and documentation.

Edge supports Chrome extensions with little change, and Firefox needs some adjustments. We scope those as additions once the Chrome version is stable.

Your team knows the product best. We are useful when they are busy or new to extension rules, and we document everything so they can take over.

Installs, weekly active users, actions completed in the extension, store rating and support tickets about the extension after each release.

Free 20-minute call

Want this for your software & saa?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call