Chrome extensions that automate web apps
Custom Chrome extensions and browser automation that click, fill, select and export inside the web apps your team already uses, even when the vendor offers no API.
9eye Studio is the team behind the 9eye broadcast platform. We automate the work your team does by hand in software, or check it before it goes out: Chrome extensions for web apps without an API, AI agents and MCP servers, validators and integrations for spreadsheets, file exports and older systems. Fixed-price projects, for teams anywhere in the world.
Six kinds of work, often in one project: an extension that does the job, a validator that checks it, and an agent that runs it when something happens.
Custom Chrome extensions and browser automation that click, fill, select and export inside the web apps your team already uses, even when the vendor offers no API.
Every file, export, playlist or record is checked against your rules before it goes out, with a report that shows what is wrong and where.
AI agents that do one job well with Claude, ChatGPT or a local model, and MCP servers that connect them to your systems, with a person approving what matters.
Data your team types twice today moves on its own: from sales to operations, from a web app to your database, from spreadsheets into the tool that needs it.
Spreadsheet automation, scraping and scheduled pipelines that collect, clean and join data from APIs, websites and archives into files or a database.
Speech-to-text, translation and classification on your own hardware. No per-minute cloud bills, and your content never leaves your network.
Real projects, described without client names. Most of our work is under NDA, so details are changed and no client data is shown.
A multi-tenant scheduling and traffic platform for TV channels, from catalog to as-run, with ten AI agents, a check-and-fix loop of validators and an MCP connection for any AI.
See 9eyeThe problem. Each day’s playlist is exported from a cloud scheduling system and sent to playout. Mistakes were caught on air, or by people reading hundreds of lines.
What we built. A browser extension that catches every export before it is saved and runs more than 20 checks on it: booked spots against the sales sheet, spot lengths, idents never back to back, end credits and “next” bumpers that match the coming show, episode order against the schedule, expired promos and early starts. It times the day, inserts missing clips from per-series rules and writes a corrected file, with a report that points to each problem.
Read the case studyThe problem. Ad campaigns were booked in one system, and the traffic team typed every spot again in the scheduling system, break by break.
What we built. A pipeline that reads each campaign per channel, maps channels, ad boxes and spot lengths, and writes the order with every spot placed in its exact break. It stays within the vendor’s session limit and tests each step against the live API.
The problem. Turning a programme’s week on air into a reusable pattern meant reading the schedule and rebuilding it by hand.
What we built. An agent skill that reads how a programme airs across the week, first runs and repeats, in a scheduling web app, and recreates it as a pattern step by step for a person to check.
The problem. Translating shows for subtitles and dubbing meant sending content to cloud services and paying by the minute.
What we built. Video in, a translated script and subtitles out: speech recognition with exact timestamps, speaker detection, then translation by a local language model that keeps real names. It runs fully offline on one 6 GB graphics card.
The problem. A product team wanted to know what people actually ask for, without reading thousands of reviews.
What we built. A collector that gathers low-star reviews and feature requests from app stores, Product Hunt, Reddit archives, Stack Exchange and GitHub issues, and sorts them by votes into a sheet the team can act on.
The problem. Backtests looked good and failed live, because models had seen the future.
What we built. A pipeline that collects and cleans exchange market data, then tests models strictly walk-forward: trained only on the past, judged only on what came after, so results are not flattered by hindsight.
Checks that each programme block’s time-code in and out add up, and flags blocks that run long or short.
Automates repetitive list selection in a catalog web app, so a long job is one click.
A button inside a booking web app that pulls the campaign data from an API and saves it to PostgreSQL.
We start from the screen your team works in, not from the vendor’s roadmap. If there is an API, we use it. If there is not, we work with the app the way a person does, only faster and the same way every time.
Our deepest work is in TV: playlist QC before playout, ad traffic that places itself, airing patterns rebuilt by an agent, and translation for subtitles on your own hardware. If your channel runs on a scheduling, traffic or playout system, we already speak its language.
See the broadcast Playlist CheckerFixed scope, fixed price, and something working early.
30 minutes on the job you want gone: what the team does, in which software, and how often.
A written plan with scope, price and delivery date. No hourly billing.
Short cycles, each ending in a working demo on your real screens and data.
Tested on real cases, with validators where a mistake is expensive.
Source code, a short guide and a video. You own what you paid for.
An optional monthly plan for changes when your software changes.
Which software, what people do in it, and how often. We reply with questions or a time for a call, then send a plan and a fixed price.
Your message could not be sent. Please write to [email protected] or on WhatsApp at +1 971 480 9697.
We reply to your e-mail address with questions or a time for a call.
Finding the manual work worth automating, building the automation (a Chrome extension, a script, an integration, a validator or an AI agent), testing it on your real data, and handing over the code with a guide. Each project is fixed in scope and price before we start.
Yes. If the software has an API we use it; if not, we automate the screen itself with a custom Chrome extension or browser automation: clicking, filling forms, selecting and exporting the way a person does, only faster and the same way every time. Data entry from Excel or Google Sheets into a web form is a common first project.
Yes. Manifest V3 extensions for your team’s own use: a button inside the web app you already work in, a check before an export is saved, or a form filled from a spreadsheet. They can be installed privately, without the Chrome Web Store.
MCP (Model Context Protocol) is an open standard that lets AI assistants such as Claude or ChatGPT use your systems as tools: read a record, run a search, create an order. An MCP server is the small program that offers those tools. You need one when you want an AI agent to work with your own data and software, with access limited to what you allow.
Yes, where they help: agents that do one job, with a person approving the result, built on Claude, ChatGPT or a model on your own hardware. Where plain rules do the job better, we use plain rules. 9eye, our broadcast platform, is built the same way.
Every project has a fixed price, agreed before we start and based on the software, the steps and the checks involved. The first call is free, and the written quote states the scope, the price and the delivery date. An optional monthly plan covers changes after hand-over.
Only what the job needs, ideally a test account. We can start from screen recordings and sample files, and we sign an NDA before we see your data.
You do, once the project is paid. You get the source code, a short guide and a hand-over video.
Yes. We work remotely with teams anywhere in the world, in English, with written updates and demos at times that suit your time zone.