I have spent the better part of the last six months building data infrastructure for a side project. Pollers that pull market data from a dozen sources every thirty minutes. A database that has accumulated tens of millions of rows. Pages that surface that data live, with no caching layer in front of them, no spinning load indicators, no excuses. The side project has nothing to do with the agency. It does, however, have everything to do with what I now believe a website should be.
The version of the agency website most small businesses get, from the studios down the road and from the template platforms everyone uses, is a brochure. A photograph of the storefront. A list of services. A button labeled “Contact Us” that opens an email window that nobody checks. The version of the website most of those businesses need is a sales document. A page that makes the case, brings the qualified prospect to a decision, and books the next appointment without a human intervening at any step.
The difference between those two things is not aesthetic. The brochure can look beautiful. The sales document can look plain. The difference is operational. A brochure does not change after it ships. A sales document is a piece of infrastructure that gets measured, edited, instrumented, and improved every month for as long as the business is open.
Most websites in this region are brochures. The owner pays a few thousand dollars for one and never touches it again. Three years later the photos are dated, the services list is wrong, the phone number on the footer is the old one, and the business has been silently leaking prospects for the entire intervening period. Nobody notices because there is no instrumentation. Nobody measures because there is nothing to measure. The brochure either looks fine or it does not, and in either case it has nothing to do with whether the business gets a phone call this week.
Building data dashboards for the last six months has changed how I see this problem. A dashboard is the opposite of a brochure. Every number on the page exists because somebody, somewhere, needs to make a decision based on it. The page is judged not on how it looks but on whether the decision improves. If the dashboard ships and the decisions get worse, the dashboard has failed, even if the visualization is gorgeous. If the dashboard ships and the decisions get better, the dashboard has worked, even if the visualization is plain.
Apply that framework to a website. Every page exists to advance a prospect along a specific decision path. The homepage exists to qualify the visitor and direct them to the right service page. The service page exists to make the case for the service and reduce the prospect’s remaining objections. The booking page exists to remove friction from scheduling. The contact page exists for the small subset of prospects who need to talk to a human first.
A site that does these jobs well, that you measure and improve over time, is a piece of business infrastructure. A site that does not, a brochure, is a sunk cost that a competitor’s better site will defeat.
The work I do at sebVERSIVE has always been built on this premise. Custom code, not templates. Mobile-first, because most local searches in Milwaukee happen on a phone. Page speed scored against Google’s actual benchmarks, because page speed is a ranking factor and a conversion factor at the same time. Real analytics, configured properly, telling you which pages convert and which silently fail. The work has always been the work, and the engineering rigor under it was always there.
What has changed, over the last six months, is the scope of what I can now build. The side project I mentioned at the top runs live data pipelines, persistent user accounts, subscription billing, alerts, and editorial publishing, all from the same Astro and Supabase stack the agency uses for its marketing sites. The difference between a small business marketing site and a full-featured custom application, on this stack, is configuration and content. The underlying engineering is the same.
The practical implication for clients is that the sebVERSIVE offering has quietly expanded. The starting tier is what it always was: a custom site that loads in under a second, ranks well, and converts qualified prospects. The next tier up is now: that site plus a custom dashboard. A medspa that wants to see which services drove bookings last month, which referral sources sent qualified leads, which marketing channel is currently underwater. A contractor who wants a real-time read on job pipeline, average ticket size, conversion rate from quote to signed contract. The data already exists in the booking system, the CRM, the spreadsheets the office manager maintains. What does not exist is a single page that pulls it together in a way the owner can actually act on.
Most owners do not know they can have this. The agencies that built their websites never offered it. The big BI platforms, Looker, Power BI, Tableau, are aimed at enterprise budgets and require a data engineer to set up. Nothing in between has existed for the small business owner who just wants to see the picture once a week.
The version of sebVERSIVE that exists in a year offers exactly that piece. A custom site, a custom dashboard, both on the same stack, both built to last. The cost will be higher than a template-platform brochure and lower than what a BI platform consultant charges, because the engineering compounds across both deliverables and one studio is doing both pieces.
The side project is not the point. The skills I have built on it are. The work has always been about engineering websites that do business work. The expansion is just letting that engineering go further.
If you are a Milwaukee business owner with a brochure for a website and a hunch that your competitors are quietly beating you on every page that matters, this is the conversation. The sebVERSIVE offering for 2026 is built for it.