Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · extension sprint
Your Chrome extension, built and on the Web Store in 14 days.
A real extension in real browsers — Manifest V3, submitted properly, and yours entirely. Two weeks, one fixed number.
Quick answer
A Chrome extension can be designed, built and submitted to the Chrome Web Store in 14 days for a fixed $1,999. That covers Manifest V3, the popup and any in-page interface, storage and sync, an options page, and the store listing. Google's review typically adds a few days on top.
The plan
Day one to day 14, written down.
You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.
- 1
Days 1–2
Scope lock
What the extension does, which pages it touches, and the minimum permissions that allows. Permissions decide both review outcome and install rate, so they get decided first.
- 2
Days 3–6
Design
The popup and any injected interface. Extensions are used in seconds inside someone else's page, so restraint matters more here than in any other build.
- 3
Days 7–11
Build
Manifest V3, background service worker, content scripts, storage and auth. You get an unpacked build to load locally early, so you are testing in your real browser during the build.
- 4
Days 12–13
Test across sites
Behaviour across the pages it targets, plus updates, uninstall and the permission prompt flow. Extensions break on other people's markup, which is where this time goes.
- 5
Day 14
Submit
Store listing finished, privacy disclosures completed accurately, and the build submitted. I handle review questions if Google comes back with any.
What $1,999 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
SaaS products whose users keep asking for a browser companion
Teams whose workflow needs something that lives on top of another site
Founders testing an idea where the browser is the natural surface
The honest part
When 14 days is the wrong answer.
A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.
Anything that scrapes a site actively defending against it. Technically a cat-and-mouse game, commercially a maintenance bill, and often against that site's terms.
Enterprise policy deployment and managed-browser distribution, which is an IT programme rather than a build.
Cross-browser parity across Chrome, Firefox and Safari in one sprint. Chrome and Edge share a codebase; Safari genuinely does not.
Questions
Before you book
Yes, for a focused extension doing one job. The two weeks cover design, build, testing and submission. What extends it is targeting many different sites, each of which changes its markup on its own schedule.
Other sprints
14 days from now, this could be live.
A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.