Chrome extensions

What your team does in five tabs, in one click.

We build the extension that puts your team’s repeated job in the browser toolbar. Each action lands straight in your CRM or your app. You decide who gets in, and access ends the moment you say so.

2Extensions of our ownClient Feedback and Time Tracking
$0To use Client FeedbackIncluded on the sites we run
<2hWhen something breaksWe answer on business days
12+Years buildingThe systems behind the browser
  • General Filters
  • Fresh Del Monte
  • Cowlitz Law Group
  • IEB Global Services
  • Elysia Tours
  • ReyRep
  • Multinversiones Kairos
  • Corpo Bienes
  • bcreative digital media
  • WIP
  • Adara Estilo
  • Cata
  • SensuaLove
  • Playa Nini
  • Webgardener
  • Cracked
  • Pedro Castre
  • Ezma Sur
  • Lights Out Sports Management
  • Officemedia
  • Easy Training
  • Hua
  • Tangerine
  • Ahorro Direct
  • Lisi Fracchia Joyas
  • Francisca Mancini
  • Employ
  • Event Trend
  • María José Manrique
  • 40Funnels
  • Volans Maritime
  • Posittion
  • Braintech
  • TresBe
  • Muelle Digital
  • Gourmedia
  • Mediagroup
  • Decodima
  • Kayzen Motors
  • Antonella Spoto
  • Floral
  • Lavera
  • Freeck
  • Casa Cavia
  • La Panadería de Pablo
  • Graes
  • Marmont
  • Clubs & Countries
  • No Ficción
  • Golcafé
  • Muma Shop
  • Épicos
  • Manzaneras
  • Africa agencia digital
  • Valor Digital
  • Reclamos Total
  • CAF
  • Pantuss

Proof

Two of ours, ready to try on this site.

One for our clients and one for our team. Each page has a working copy: click around and see what reaches the CRM.

Public · for clients

Client Feedback

Click anything on your site and say what you want. The team gets it as a task with a screenshot, and you watch it solved on the same page.

  • Comment on the exact element you mean
  • Replies and “solved” on the same page
  • One click to sign in, nothing to paste

Internal · werun SSO

Time Tracking

Our team’s hours from any tab: find the task, press play, and the time lands in the CRM’s timesheets.

  • Sign-in with Google or a passkey
  • Search in any word order
  • Running time on the toolbar icon

Why it matters

You decide who gets in, and what it can see.

The quick way is one shared key in every install and permission to read every page. It works until someone leaves, or until the Web Store review asks why. Yours gets a sign-in or a token per person, and only the sites it needs.

The usual way

  • One shared API key, pasted into every install
  • Permission to read and change every website
  • Code fetched from a server after install
  • One language, and a listing written last

How we build them

  • A sign-in or a token per person, scoped and revocable
  • Only the sites it needs, asked for when it needs them
  • Everything inside the package Google reviewed
  • English and Spanish, in the extension and the listing

What changes for you

Your team works from the toolbar, your clients from their own site, your system sets the rules.

You see the extension. Most of the work is what it connects to and what it is allowed to touch.

01Team tools that live in the toolbar

The job your team does across five tabs, done from the toolbar. Ours is Time Tracking: press play on a CRM task and the CRM’s own timer runs. It signs in through our own SSO.

  • Your team signs in with the accounts it already has
  • Who may use it, decided by the roles in your back office
  • The running count on the icon, a shortcut to open it
  • Every connected browser listed, closed in a click
02Extensions your clients use to work with you

Something your clients install, public on the Chrome Web Store. Ours is Client Feedback: a client clicks anything on their own site and writes what should change. It arrives as a task, screenshot included, under the name of the person who signed in.

  • Works on your client’s site without touching its design
  • Asks for a site only when the client allows it
  • A screenshot and the page details with every comment
  • Each client signs in with their own account
03Your system sets the rules

The rules live on your side, in your CRM, your WordPress or your own app. You decide what the extension may do, and can take its access away at any moment.

  • It can do only what you allowed, nothing more
  • Access handed out, renewed and taken back from your side
  • Answers only to the extension, never to the open web
  • A cap on how much it may ask, and a log of what it did
04Published on the Web Store, kept up to date

The listing, screenshots, privacy policy and a reason for every permission, written for the review in two languages. Each change ships as a new version, and Chrome updates every install on its own.

  • Listing copy and screenshots, EN and ES
  • Privacy policy and data disclosures
  • A reason written for each permission
  • Each update reaches every install on its own
  • Public, unlisted or private visibility

How it works

What you see at each step.

  1. 01

    You tell us the job and the system behind it

    Tell us the steps your team repeats, and the CRM or app they end up in. We reply within 2 hours on business days with whether an extension is the right shape for it.

    You getA permission list with a reason for each, before any code

  2. 02

    You approve the list, then Google reviews the package

    You read every permission and the reason for it before we build. The Web Store review reads the same text, and the release is planned around it.

    You getA listing in English and Spanish, from your own developer account

  3. 03

    Each change ships as a new version

    Chrome updates every install on its own, and your system keeps deciding who gets in. Access ends the moment you say so.

    You getEvery install updated on its own, and sessions you can see and close

What you get

Your listing. Your users. Our responsibility.

In writing

Your permission list, before any code

You get every permission it will ask for, the reason for each and the data it keeps. All of it is written before we build. The Web Store review reads that same text, and you approve it first.

  • 01

    Passwords stay on your own sign-in page

    Your team signs in on your own page and the extension gets a short-lived token. A client signs in with the account they already have with you. Nobody types a password into a popup.

  • 02

    Your system stays the source

    The extension shows and sends, and your CRM or your app decides. A timer started in the browser is the CRM’s own, and a comment is a task in the project.

  • 03

    Each site is asked for when it is needed

    Site access covers only the domains that need it, asked for the first time it is needed. What Chrome asks the person to allow matches what the extension does.

What clients say

Teams like yours, in their own words.

“The client portal, the feedback extension and the WordPress security alerts have been very intuitive, pretty turnkey. Just this past week getting comfortable with it, it’s been really helpful. We’re rolling it out to our core team. Nice job.”
Eric MillerNorth American Director of Sales & Marketing, General Filters & GeneralAire®

Is there a job your team does in five browser tabs?

Tell us the steps and the system behind them. We reply within 2 hours on business days. You hear whether it should be an extension, and which permissions it would ask for.

Start a conversation No commitment. Just a conversation.

Chrome extension questions

How long does publishing take?

Most of the time goes into the extension and the API it talks to, not the store. Google reviews every new item and every update before it reaches anyone, usually within days. Broad permissions take longer, so the release is planned around that review.

Public, unlisted or private?

Public if anyone should find it in the store, as with our Client Feedback. Unlisted if only people with the link should install it. Private if it is only for your team: the listing is visible to accounts in your Google Workspace alone.

Who owns the developer account and the listing?

You do, if the extension is yours. The listing is published from your developer account, and we work in it with the access you grant. Our own are published from ours.

Does it work in browsers other than Chrome?

It is built on Manifest V3, the platform Chrome uses today. As a rule it runs unchanged in Edge, Brave and the other browsers built on Chromium. Firefox and Safari need their own package and their own review. The scope says whether that is part of the work.