A custom Chrome extension open beside a web page, showing a form that replaces manual data entry.
Custom Chrome Extension Development

Automate Everything. Just Stop Paying Monthly For It.

Most of what you pay monthly for is solving a problem that lives inside one browser tab. I build a Chrome extension that does that one thing, shaped to how you actually work. You own it, it runs on nothing, and there is no renewal.

The Problem

Nothing Here Is Broken. It Just Renews.

Pull up your card statement and read the software line items out loud. There is probably one you forgot you were paying for. There is one you use twice a month and renew twelve times a year because canceling is a support ticket. And there is one that would genuinely do what you need if somebody sat down for an afternoon and learned it, and nobody has, so it sits there billing.

None of that is anybody being dishonest. It is how the model works. Software is built to own a problem, because owning it is what recurs. Solving it outright would end the relationship.

There is also a quieter cost. Every one of those tools is another company holding your data, another login a departing employee still has, another vendor whose breach becomes your Tuesday.

Meanwhile the actual repetitive thing you do every week is still being done by hand.

You should not have to rent a workaround forever because nobody built the thing that fits.

Who You're Working With

I Run My Own Business Out Of One Of These.

Andy O'Neil, founder of Weblytica
Andy O'NeilFounder, Weblytica, LLC

I did not set out to sell Chrome extensions. I built one because I could not find a tool that did what I needed and I was not willing to stack three subscriptions to approximate it.

One click opens my client list, the meetings I have had with each of them pulled in automatically, my notes and due dates, and a timer I hit to track hours. Invoices pull straight from those hours and go out to my billing system in one button. Under that: my contacts, their email history, and a follow-up queue that hands me a manageable number of people each day instead of all of them at once. My automation scenarios report their status in there too, so I can see what broke without going looking for it.

It replaced Toggl Track outright, and it does four or five things Toggl never did.

The whole thing would take about thirty hours to rebuild from scratch today. The client and time tracking piece alone, the part I use every working hour, is about ten of those.

That is the same kind of thing I build for a client. Not a template, not a white label product with your logo on it. A tool shaped like your actual workflow.

I will also tell you when the answer is no. Sometimes the honest answer is that a thirty dollar a month tool already does this well and you should just buy it. I would rather say that than sell you a build.

6 to 8 hoursTypical build time
$0Monthly cost, now and later
1,100+Hours of co-building with business owners
10 yearsWith my longest-running client
The Offer

What You Get

  • A tool built for your workflow, not for a category. Six to eight hours of build time for a typical extension with a real feature set. I have done simpler ones in about two hours. You are not buying hours, you are buying the thing that stops happening.
  • It updates itself. The extension lives in a shared Dropbox folder. You add that folder to your own Dropbox and install from it. When I push a change, Dropbox syncs it to your installation. Nobody has to remember to reinstall anything or forward a zip file around the office.
  • Your data stays where you control it. Extensions store data in a Google Sheet you own, or in Firebase if the volume calls for it. With a Sheet, access is controlled the way you already control Sheets, by who it is shared with. Where it matters, I add a second sign-in on the extension itself, so seeing anything requires both.
  • Nobody else's breach becomes your breach. A SaaS product holds thousands of companies' data in one system, which is exactly what makes it worth attacking. When that vendor gets breached you are in the disclosure email whether you did anything wrong or not. An extension your team installs locally is not in anybody's pool. There is no public sign-in page for your account to be credential-stuffed, and no vendor employee with standing access to your records.
  • You own it, and there is nothing to renew. No monthly fee to me. No seat licensing. No platform underneath it that can change its pricing next year.
  • When Chrome breaks something, it is a repair, not a subscription. Chrome changes things constantly. If an update breaks your extension, I fix it and bill you for that work. I would rather do that than charge you every month for the twenty-three months when nothing goes wrong.

To be precise about the security piece: this is a smaller attack surface, not a nonexistent one. Your data still lives in a Google account, and the machines it runs on still matter. What changes is that the surface is yours instead of shared, and the list of people who can reach it is short enough to say out loud.

See One In Action

This Is One I Built For Myself.

The client and time tracker I run my own business out of. Click around. It is the real interface, not a screenshot.

Pricing

Priced Against What It Replaces, Not Against My Hours.

TierPriceReplacesPays for itself at
Small$1,600One subscription, or does something no subscription doesAbout $160 a month replaced
Medium$2,400Two subscriptionsAbout $240 a month replaced
Large$3,600Three subscriptionsAbout $360 a month replaced

Ten months. That is the math on all three tiers. If this extension retires one tool you pay $160 a month for, you are even in ten months and it is free after that. Same story if it retires three tools at $120 each.

The bottom tier also covers the case where there is nothing to cancel, because no product does this. That is often the most valuable build, since the work is currently being done by a person instead of by a tool.

If your numbers do not land near those, say so and we will do the actual arithmetic on your stack. I would rather run it honestly on the call than have you run it later and feel misled.

The Process

Three Steps.

  1. Show me the repetitive thing.

    Not a spec. Share your screen and do the task the way you normally do it. Most of the time I can tell inside ten minutes whether this is an extension, a Make scenario, or something you should just go buy.

  2. I build it.

    Six to eight hours for most builds. You are picking a tier, not paying a clock.

  3. You install it and own it.

    Add the folder, install it, done. If it is a team, everybody installs from the same shared folder and updates reach all of them.

The Agreement

What You Own When We Are Finished

  • The code. Hand it to another developer whenever you want. Nothing about it is proprietary to me.
  • The data. It is in your Sheet or your Firebase project, under your Google account.
  • No monthly fee to Weblytica. Not for the extension, not for hosting, not for seats.
  • Repairs are billed, never subscribed. If Chrome breaks it, you pay for the fix and nothing else.
  • An honest recommendation first. If you should buy something instead of building it, I will say so before you pay me.
Fit

Who This Is Not For

  • You have not run the process yet. If the workflow is three weeks old, do not automate it. Run it fifty times, find out what actually matters, then build.
  • The problem does not live in a browser. If Chrome cannot reach it, this is the wrong tool and I will point you somewhere else.
  • You want somebody else to own it. You own this. That is the deal, and for some people a monthly product with a support desk is genuinely the better fit.
Questions

The Things People Ask

How do people install it? Do I need IT?+

No. The extension lives in a Dropbox folder I share with you. You add it to your Dropbox and install it in Chrome from that folder. When I make a change it syncs to you automatically. For a larger group I can put it on the Chrome Web Store as a private listing instead, so people install it the normal way without anybody setting up folders.

Where does my data go?+

Into a Google Sheet you own, or a Firebase project you own. Access to a Sheet is controlled the way you already control Sheets, by who it is shared with. Where the data is sensitive I add a sign-in to the extension itself, so somebody needs both the extension login and access to the Sheet before they see anything.

What permissions does it ask for?+

It depends entirely on what the extension does. Some only need local storage in your browser. Some need to read one specific site. Some talk to an API. I will walk you through the exact list for your build before you install it, and Chrome will show it to you any time you want to check.

What happens when Chrome updates and breaks it?+

I fix it, and I bill you for the repair. I do not build a maintenance fee into the price, because for a tool two or three people use, you would spend more across eleven quiet months than on the one repair. If yours is going on the Chrome Web Store for hundreds of users, that is a different conversation and we would structure it differently.

Is this actually more secure than a SaaS tool?+

For a small team, in the ways that matter, yes, and I would rather be specific than wave at it. There is no public login page for your account, so there is nothing sitting on the internet to be attacked. Your records are not in a multi-tenant system that is a target for reasons that have nothing to do with you. Access is your Google Sheet sharing list, which is short and which you already know how to manage. When somebody leaves, you revoke their Google access the way you do for everything else and they are out. What it is not is a guarantee. The extension runs on your team's machines, so those machines still count.

What if I want changes later?+

Send them over. Changes are billed as work. There is no version of this where you have to keep paying in order to keep using what you already have.

Who maintains this if you disappear?+

Any developer who works in JavaScript. It is a standard Chrome extension in a folder you own, not a platform account with your data locked inside it.

Pick a Time

Show Me What You Keep Doing By Hand.

Pick a time, share your screen, and walk me through the thing you do every week. Ten minutes usually settles it. If an extension is the answer I will tell you which tier and roughly how long. If you would be better off buying something for thirty dollars a month, I will tell you that too, and it costs you nothing to find out.

Loading the calendar…
Open it in a new tab if it does not appear.

No charge for the call.