Chrome extension development, from first prototype to the Chrome Web Store.

We design and build browser extensions that people keep installed: fast, private by design and maintained after launch. We know the work because we ship our own, Searchless, coming soon to the Chrome Web Store.

What we build

An extension is a small product with its own rules: permissions, store review and the pages it runs on. We handle all of it.

Productivity and AI extensions

Tools that live next to the work: saving, searching, summarising or automating what happens in the browser.

Searchless case study

Diagram

Integrations with web apps

Extensions that read from and act on the sites your users already use, built carefully so they keep working when those sites change.

Diagram

Companion web apps

A Next.js site or dashboard alongside the extension for accounts, onboarding and anything that doesn't belong in a popup.

Diagram

Chrome Web Store launch

Listing, screenshots, permission justifications, review and the updates that follow.

PROOF

Searchless: our own extension, coming soon to the Chrome Web Store.

Searchless auto-saves and indexes your AI conversations across Claude, ChatGPT and Gemini, so you can find an earlier answer without remembering which tool it came from. It is local-first and runs as a freemium product. We designed and built it ourselves.

  • Coming soon to the Chrome Web Store
  • Local-first architecture
  • Works across Claude, ChatGPT and Gemini
  • Freemium SaaS

Why local-first

Local-first means the extension keeps its data on the user's device by default and works without waiting on a server. Search feels instant, there is less personal data to hold, and the product keeps working when the network doesn't. We recommend it whenever an extension handles content people consider private.

How an extension project runsDiagram. Typical timeline.
  1. Scope

    Sites, data and the permissions it really needs.

    Call + written proposal
  2. Prototype

    A build in your own browser, early.

    First week
  3. Build

    Extension, companion app, tracking.

    Small projects 1–2 weeks
  4. Publish

    Store review, then updates.

    Ongoing

Ready to start? Pick a time.

A 20-minute call: what you are launching, what is blocking it, and the next step. No prep needed.

Book a 20-min intro call

Built for Manifest V3 and Chrome Web Store review

New Chrome extensions are built on Manifest V3, which replaces the always-on background page with a service worker that starts and stops on demand. That shapes the architecture: state lives in storage rather than memory, long jobs have to survive the worker shutting down, and request rules use declarative APIs. We design for these limits from the first prototype.

Store review is the other constraint. Google asks you to justify every permission and describe how user data is handled, so we scope permissions to the sites the extension really needs and write the justifications and privacy disclosure alongside the build, not after it.

Extensions that depend on other people's websites

Most useful extensions read from or act on pages they do not control, and those pages change without notice. We keep the page-specific code small and isolated, prefer stable signals over brittle selectors, and test against the sites you support, so a change on their side shows up in our checks before it reaches your users.

Searchless supports four AI assistants, Claude, ChatGPT and Gemini, so we live with this problem in our own product, not only for clients.

Cost, timeline and ownership

We do not publish a flat rate for extensions, because permissions, data storage and a companion web app change the scope a lot. After a short intro call you get a written proposal with a fixed price wherever the scope allows.

You own the project-specific code and assets once invoices are paid.

Web & AI developmentFor agencies

Frequently asked questions

How much does it cost to build a Chrome extension?

It depends on what the extension reads, what it stores and whether it needs a companion web app or accounts. Our small projects cost €2,000–5,000 and take one to two weeks; larger builds are planned week by week after discovery. After a short intro call you get a written proposal with a fixed price wherever the scope allows.

How long does Chrome Web Store review take?

Review time is set by Google and varies, so we plan the submission early and do not promise a date. Extensions that request few permissions and explain them clearly tend to move through review more smoothly than ones that ask for broad access. We prepare the listing, screenshots, permission justifications and privacy disclosure alongside the build, then handle any fixes the reviewers ask for.

Do you build extensions for browsers other than Chrome?

Chromium-based browsers such as Edge and Brave can run the same extension, and each has its own store listing. Firefox and Safari use their own packaging, so we scope them separately. Tell us which stores matter to you.

Can the extension keep user data on the device?

Yes. Local-first is our default for extensions that handle private content: data stays in the browser's storage on the user's device, features work without a round-trip to a server, and you have less personal data to protect. Searchless works this way. If you need accounts or sync, we add them deliberately and the privacy disclosure says what leaves the device.

Who owns the code, and do you maintain the extension after launch?

You own the project-specific code and assets once invoices are paid; we keep general know-how and reusable patterns. After launch we offer retainers or blocks of time for updates, because Chrome and the sites an extension depends on keep changing.

Have an extension in mind?

Email us a few lines about what it should do and who it's for. We'll reply with a rough plan and a price range.