Browser Extension Development
Chrome and Edge extensions built to pass store review and ship
From a focused tool to a full product: Manifest V3, privacy-first, store-ready.
Ships and passes review
Manifest V3, TypeScript and the store rules baked in from day one, so review is a formality, not a rewrite.
Privacy-first by default
Minimal permissions, each one justified. Zero network requests when the product allows it, verified at build time.
One codebase, Chrome and Edge
The same extension runs on Chrome, Edge, Brave and other Chromium browsers. Firefox and Safari scoped separately.
Store listing included
Screenshots, description, privacy disclosures and permission justifications, plus review feedback until it is published.
What I build
Tools that live in the browser, where your team or your customers already work.
Capture and annotate
Screenshot, recording and markup tools that keep files on the device. ClarShot is mine.
Sales and lead tools
Overlays on LinkedIn, CRMs and email that enrich, tag and push data to where the team works.
Internal ops tools
Company-specific helpers on top of the web apps your team already uses: forms, checklists, shortcuts.
Content and SEO tools
On-page audits, metadata checks, structured-data validators and quick exports.
E-commerce helpers
Price and stock monitors, order tooling and marketplace shortcuts for operators.
Reading and accessibility
Reader modes, translation overlays, focus tools and per-site preferences.
I ship what I sell: ClarShot
ClarShot is my screenshot and screen-recording extension for Chrome and Edge. It makes zero network requests in free mode, needs six explained permissions, records with no time limit, and keeps every capture on the device. The same engineering goes into client work.
- 0 network requests in free mode
- 6 permissions, each explained
- Chrome Web Store + Edge Add-ons
How I work
Discovery and scope
A short written brief, then a written scope: features, permissions, browsers, stores, timeline and a fixed price.
Build
Manifest V3, TypeScript, tests. Weekly builds you can install and try.
Store submission
Listing, screenshots, privacy disclosures, permission justifications. I handle review feedback until it is live.
Maintenance
Chrome and Manifest updates, policy changes, fixes and small improvements, on a monthly retainer.
Packages & Pricing
Starter
- One core feature, popup + options page
- Chrome, Manifest V3, TypeScript
- Chrome Web Store submission included
- Privacy disclosure + permission justifications
- 30 days of fixes after launch
Business
- Multi-feature: content scripts, storage, service worker
- Chrome + Edge from one codebase
- One API or backend integration
- Both stores: Chrome Web Store + Edge Add-ons
- Onboarding, settings, no tracking by default
Advanced
- Complex product: auth, sync or dashboard
- Media, canvas or real-time features (like ClarShot)
- Ongoing store policy compliance
- Automated tests + release pipeline
- Roadmap and feature work on retainer
Questions
How long does it take to build a browser extension?
A focused single-purpose extension typically ships in 2-4 weeks including store submission. A multi-feature, cross-browser extension takes 4-8 weeks. Complex extensions with a backend or dashboard take 8-12 weeks or more. I give a fixed timeline after a short discovery.
Which browsers do you support?
Chrome first, on Manifest V3. The same codebase runs on Edge, Brave and other Chromium browsers. Firefox and Safari ports are scoped and priced separately.
Do you handle the Chrome Web Store submission?
Yes. The store listing, screenshots, privacy disclosures and permission justifications are part of every package, and I handle review feedback until the extension is published. Edge Add-ons is included from the Business package.
How much does a browser extension cost?
Packages start at €1,500 for a single-purpose extension, €4,500 for a multi-feature cross-browser extension, and €10,000 for complex extensions with a backend, auth or dashboard. Maintenance is a monthly retainer from €150. The exact price is fixed after a short discovery.
Can you build a privacy-first extension that makes no network requests?
Yes. ClarShot, my own screenshot and screen-recording extension, makes zero network requests in free mode, needs six explained permissions, and a build-time scanner fails the build on any external request. I apply the same approach to client work whenever the product allows it.
What does maintenance cover?
Chrome and Manifest updates, store policy changes, bug fixes and small improvements, on a monthly retainer sized to the package. Larger features are scoped separately.
Tell me what your extension should do
You get the scope and a fixed price by email, within 2 business days.
Get a written quoteI reply by email within 2 business days. No calls needed.