We build Chrome extensions that save clicks in the web apps your team uses all day: capture data from a page into your system, fill forms from your records, add a side panel with the information they need, or add features to an existing extension.
Tell us what you needSee typical projectsA written scope before we start, so you know what you're getting before work begins.
What we hear from businesses before a project like this starts.
The requests that come up most often for this kind of work, and what each one takes to work properly.
Details on a page saved to your CRM, sheet or database with one click.
Forms on another site filled from your data, with the person still checking and submitting.
Information from your systems shown next to the page your team is working on.
New features in an extension you already have, without starting over.
An older extension moved to Manifest V3 so it keeps working in Chrome.
Listed on the Chrome Web Store, or installed privately for your company through Google Workspace.
Tools that come up most: Chrome Extensions Manifest V3, JavaScript, TypeScript, React, Chrome Web Store, Google Workspace admin, your APIs, Google Sheets.
Concrete pieces, each one something you can open and check when it's done.
Buttons, menus and overlays added to the web apps your team uses.
Content scripts, Manifest V3Information on a page sent to your CRM, sheet or database.
Your APIs, Google Sheets, webhooksContext from your systems shown beside the current page.
Side panel API, popupsForms filled from your records, with a person reviewing before submitting.
Content scripts, your dataExisting extensions moved to Manifest V3 and updated.
Service workers, Manifest V3Store listing, privacy policy details and review, or a private company rollout.
Chrome Web Store, Google WorkspaceExample packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
A button on the pages your team uses that saves the details to your CRM or a sheet.
You get
Example package
A side panel showing data from your system next to the page in use.
You get
Example package
Your existing extension moved to Manifest V3.
You get
Example package
A simple extension built and taken through Chrome Web Store review.
You get
YieldScout is a Chrome extension for small landlords who browse listing sites. Open a listing and the extension reads the price, unit count and taxes from the page, estimates rent from nearby comparable rentals, and shows cap rate, monthly cash flow and cash-on-cash return. Every assumption (down payment, rate, vacancy, repairs) can be edited, saved per user, and synced. One click saves the deal to a Google Sheet or adds it to a side-by-side comparison.
JavaScript/TypeScript, Chrome Extension Manifest V3, chrome.storage sync, Google Sheets API, Vite
A working example we built to show this kind of work. It is a demonstration, not a client project.
Sample build
Toolbar popup that shows a page's word count, reading time and top keywords, and highlights any keyword or phrase with one click. Right-clicking a selection shows its word count on the toolbar badge.
Chrome Manifest V3, JavaScript, chrome.scripting, service worker
About the screenshot: The extension's popup shown over a sample page.
The habits that keep this kind of project from going wrong.
Extensions ask only for the sites and permissions they need, which also makes store review faster.
Tools that fill or submit forms on other sites leave the final click to a person.
We check the terms of the sites the extension works on, and say so in the scope if a request would break them.
Code is organised so a change on the target site means a small fix, not a rewrite.
You describe it. We write it down, build it, and hand it over.
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
Yes. It can be installed only for your Google Workspace users, or shared as an unlisted store item.
Edge runs Chrome extensions with little or no change. Firefox needs some changes; we say in the scope if it's included.
You do. The code is in a repository you own, and any store listing is under your developer account.
In the 30 days after handover we fix it at no charge. After that, further work is scoped the same way and agreed with you before we start.
Most extensions take one to three weeks from the signed scope, plus store review time if it is published.
No, Google decides. We build to the store's policies and handle the submission, and fix anything the reviewers ask for.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com