Skip to main content
Rashid Iqbal

Manifest V3 · React · TypeScript

Chrome Extension Developer for SaaS

I build Chrome extensions for SaaS teams. Manifest V3, React, TypeScript. From spec to Web Store submission in two to four weeks. One developer, one timeline, one shipped extension.

What I build

  • Manifest V3 architecture with service worker background scripts
  • Content scripts that read and modify the active tab safely
  • OAuth flows for Google, Notion, Linear, Slack, and custom IdPs
  • React + TypeScript popup UI with Tailwind styling
  • Chrome Web Store listing, screenshots, and review submission
  • Privacy policy, permissions audit, and review-friendly architecture

Use cases

Productivity tools for SaaS teams

Quick-capture extensions that send selections to your app. One-click context, zero copy-paste.

Sales and outbound enrichment

LinkedIn, GitHub, or directory scrapers that push enriched contacts into your CRM through a webhook.

Internal QA and admin tools

Hidden admin panels gated by domain, exposing feature flags or internal actions on staging environments.

Design and engineering helpers

Color pickers, asset extractors, accessibility audits, or Figma-to-code shortcuts.

How a project runs

  1. Week 1: Spec

    Permissions audit, flow diagrams, mock UI, Manifest V3 architecture decisions documented.

  2. Week 2: Build

    Popup, content scripts, background service worker. CI set up. First test build sideloadable.

  3. Week 3: Polish + submit

    Icons, screenshots, listing copy. Web Store submission. Privacy policy hosted.

  4. Optional Week 4: Iterate

    Review feedback addressed, edge cases fixed, analytics wired through PostHog or similar.

Frequently asked questions

Do you build with Manifest V3?

Yes. Every extension I ship in 2025 and 2026 is Manifest V3 native. Manifest V2 is deprecated and Chrome stops accepting V2 submissions for most cases.

Can you publish the extension to the Chrome Web Store for me?

Yes. I prepare the listing, write the description, generate screenshots, and submit on your developer account. Review usually takes one to three days.

How much does a Chrome extension cost?

Simple extensions with a popup and one content script start at $1,500. SaaS-integrated extensions with auth and webhooks run $3,000 to $6,000. Enterprise builds are quoted after spec.

Do you support Firefox and Edge too?

Yes. Modern Manifest V3 builds with cross-browser polyfills run on Edge directly and Firefox with minimal adjustments. I build cross-browser when requested.

Can the extension talk to my SaaS backend?

Yes. OAuth flows, JWT auth, signed webhooks, and direct API calls are all standard. I work with your engineering team to keep the auth boundary clean.

What stack do you use?

React, TypeScript, Vite for bundling, Tailwind for styling, and Plasmo or a custom build pipeline depending on scope. PostHog for analytics. Sentry for error tracking.

Have a Chrome extension idea?

Send me the rough spec. I will scope it on a 30-minute call.

Book a scoping call