Client Feedback and Time Tracking
Built and actively maintained
Critical issue response
The systems behind the browser
One for our clients and one for our team, each connected to our own Perfex CRM. Each has a page with a working copy you can try.
Clients click any element of their site and leave a comment. It becomes a task in the CRM project, with a screenshot and the page details.
Time on CRM tasks from the toolbar: search by client or project, press play, and the timer that runs is the CRM’s own.
The quick way to build one is a settings field for an API key and a permission to read every page. It works until somebody leaves, or until the Web Store review asks why. We build them the other way round.
The extension is the visible part. Most of the work is what it signs in to and what it is allowed to touch.
The job your team does across five tabs, done from the toolbar instead. Ours is Time Tracking: time on CRM tasks, signed in through our own SSO.
Something your clients install to work with you, public on the Chrome Web Store. Ours is Client Feedback: comments on their own site that arrive as tasks.
An extension is a client. The endpoints, the tokens and the rules live on your side: a module in your CRM, a plugin in WordPress or routes in your own application.
The listing, the screenshots, the privacy policy and a reason for every permission, written for the review in two languages. Then a versioned release each time it changes, and Chrome updates every install on its own.
Every permission the extension will ask for, the reason for each one and the data it will keep, written down before we build it. It is the text the Web Store review reads, and you approve it first.
People sign in on your own sign-in page and the extension receives a short-lived token, or a scoped one your team issues. Nobody types a password into a popup.
The extension shows and sends; your CRM or your app decides. A timer started in the browser is the CRM’s own timer, and a comment is a task in the project.
Site access is limited to the domains that need it and requested when it is first needed, so what Chrome asks the person to allow matches what the extension does.
An extension is one surface of a system. These are the others it usually connects to.
The CRM, ERP or API behind the extension, connected with a queue and a reconciler.
When the back office is yours to build: Next.js and PostgreSQL, with the extension as one more client.
What happens after the click: a workflow that routes, drafts or summarises what the extension sent.