Back to blog
FILE 0x46·WHY TICKETSCOPE IS A CHROME EXTENSION FIRST, NOT A MARKETPLA

Why TicketScope is a Chrome extension first, not a Marketplace app

June 7, 2026 · msp, connectwise, ai, product

I spent last night building a Chrome extension that adds an AI sidebar to ConnectWise Manage. When you open a ticket, it shows you a plain-English summary and a pre-filled time entry draft. I'm calling it TicketScope.

The natural question is: why a Chrome extension and not a ConnectWise Marketplace app?

The Marketplace path

ConnectWise has an official app marketplace. If you want to publish there, you need to:

  1. Register as a Marketplace Partner (AGJ already has this, so at least I don't have to start from scratch)
  2. Submit your app for review — security audit, support SLA documentation, terms of service
  3. Wait 6-8 weeks for approval
  4. Handle updates through the same review cycle

That's the right path eventually. Once you've validated the product, it's the distribution channel you want — MSP owners see it in their Apps tab the next time they're browsing.

But I don't have a validated product yet. I have a hypothesis.

The hypothesis I'm testing

The hypothesis is: engineers who work CW Manage tickets would meaningfully change their behavior if they had a 3-sentence summary of the current ticket state and a pre-filled time entry waiting for them.

I believe this is true. I've been the engineer at the keyboard reading a 47-message ticket thread for 3 minutes before I could write a single line of time-entry text. But belief is not validation.

The Marketplace path asks me to invest 6-8 weeks and a security review before I know if the hypothesis is right. The Chrome extension path asks me to invest one night and an Anthropic API key.

What the extension lets me learn

In "direct mode," the extension reads what's on screen and sends it to Anthropic's API. No CW credentials, no server, no account signup. The user loads the extension, pastes their API key, and it works on the next ticket they open.

That means I can put it in front of an AGJ engineer in 60 seconds. That engineer uses it on 10 tickets this week and either keeps using it or doesn't. If they keep using it, that's signal. If they don't, I need to understand why before I spend 6 more weeks building the marketplace version.

The Chrome extension is the fastest path to a real signal from a real user doing real work.

The tradeoffs I accepted

A Chrome extension is technically brittle. ConnectWise Manage's UI is a single-page app that uses Ember and a lot of dynamically-generated DOM. My content script is watching for pushState events and MutationObserver changes to detect ticket navigation. If ConnectWise redesigns their ticket view, I might have to update the extension.

An official Marketplace app, by contrast, uses ConnectWise's Hosted Solutions Platform SDK — a supported iframe integration with stable hooks. It won't break when CW updates their UI.

I accepted this tradeoff because:

  1. The CW Manage UI hasn't changed significantly in the areas I'm using (URL patterns, ticket summary headings) in years.
  2. The brittleness risk in the first 30 days of a pilot is much lower than the validation risk of investing 8 weeks before talking to a real user.
  3. I can always port to the official SDK later once I know the product is worth building.

The "no server required" bet

The extension's free tier works with just an Anthropic API key. No TicketScope account, no credit card, no server I have to run. The user's ticket data goes from their browser to Anthropic and nowhere else.

This is a deliberate privacy positioning. MSPs handle sensitive client data. The first objection you'll get from any MSP engineer or their manager is "where is our ticket data going?" The answer right now is "Anthropic's API, same as if you'd typed it into Claude.ai yourself."

The Pro tier (full mode) fetches the complete ticket thread from the CW API and routes it through a Lambda I host. That gets you better summaries on long tickets, but it requires trusting me with your CW credentials. That trust has to be earned. Earning it on the free tier first is the right order of operations.

What's next

The short-term plan is to run a pilot inside AGJ — load the extension on a few engineers' machines and watch what happens. Do they use the sidebar? Do they edit the time entry or paste it as-is? Do they click "Refresh" after new notes come in?

If those questions have good answers, then the next step is finding one MSP outside of AGJ who's willing to try it, ideally someone I already know from the ConnectWise / IT Nation community. That second customer is where you learn what was specific to AGJ's workflow versus what's universal to the MSP problem.

The Marketplace submission comes after that. It's a distribution channel, not a product validation tool. Get the product right first.

The extension is at ticketscope.io if you want to try it.