
Live Web Traffic
Visit siteA real-time website visitor intelligence platform that shows businesses who is on their website right now — built as an embeddable widget the client could turn into a standalone, sellable product.
Built a real-time website visitor intelligence platform — delivered as an embeddable widget — and turned the underlying technology into a subscription product the client could sell to other website owners.
Business Challenge
The client wanted website owners to see their live website traffic directly, rather than waiting on a traditional analytics report — a widget that shows who's on the site right now and where they're visiting from. But the brief went further than an internal dashboard: the client wanted to turn the technology itself into a product other website owners could install on their own sites and pay for. That meant BAMS had to design LiveWebTraffic as a real, embeddable, multi-site widget from the start — not a one-off reporting page built for a single website.
Project Objective
BAMS was tasked with building a platform that could capture live visitor activity on any website it was embedded on, broadcast that activity in real time, present it through a simple, glanceable widget, and do all of this per-site — so the same technology could be installed on many different customers' websites independently. The objective extended to commercialization: the platform needed a real path to being sold and billed as a subscription product, not just a working prototype.
What BAMS Built
BAMS built LiveWebTraffic as a real-time visitor-intelligence platform centered on a lightweight, embeddable JavaScript widget: a website owner drops a small script tag onto their site, and the widget opens a live WebSocket connection back to LiveWebTraffic's server, registering itself under that site's own tracking code. Each connected widget receives a live feed of visitor activity — recent hits, referrers, and pages visited — pushed to it in real time rather than refreshed on a timer, plus each visitor's approximate location (city and country) shown alongside their activity. Tracking codes are issued and persisted per website, so the same platform serves many independent sites without one site's traffic being visible to another's widget. On top of the working product, BAMS built the commercialization layer the client actually wanted: a real Stripe-backed subscription plan, so LiveWebTraffic could be offered and billed as a standalone product rather than staying an internal tool.
BAMS's Role
BAMS was responsible for the end-to-end product: the Next.js/React frontend, the Node.js/Express backend and WebSocket server, the embeddable widget script (built and bundled separately from the main app), the per-site tracking-code system, and the Stripe subscription integration that turned the technology into a billable product.
Implementation Approach
The platform follows a simple, real-time pipeline: Website Visitor → Embedded Widget → WebSocket Connection → Tracking-Code-Scoped Broadcast → Live Widget Feed. Rather than polling for updates, the widget holds an open WebSocket connection and receives each new hit as it happens, which is what makes the feed feel live rather than like a refreshed report. The tracking-code system is what makes the platform a real multi-site product instead of a single-purpose script: each website gets its own code, its own history, and its own isolated feed, so the same backend can serve many customers independently. The Stripe subscription sits on top of that same architecture — a real commercialization layer, not a separate demo.
Business Impact
LiveWebTraffic gave the client a way to show website owners their live traffic as it happens, in a simple, visual widget, instead of a static analytics report reviewed after the fact — and gave them a real, working path to sell that technology as its own subscription product rather than keeping it as an internal tool.
Key Features
Technology Stack
Related Resources
How to Build a SaaS Product: A Practical Starting Point
Multi-tenancy, billing, and a real MVP scope — the three decisions that determine whether your SaaS idea survives its first year.
Read moreCustom Software vs. Off-the-Shelf: How to Actually Decide
Off-the-shelf software isn't wrong, and custom software isn't always right. Here's the actual decision framework.
Read moreEMR vs. EHR: What's the Difference, and Does It Matter?
The two terms get used interchangeably, but the distinction explains a lot about why healthcare software is built the way it is.
Read moreMore Case Studies
Jobofy.com
Took Jobofy from concept to a fully AI-matched job portal in weeks, not months — the founder described the team as feeling like a true extension of their own.
Read case studyMealsHUB
Built and launched a unified multi-vendor food marketplace connecting restaurants, home chefs, food trucks, and caterers with customers through one platform.
Read case studyNebular Cross
Engineered a cross-platform framework from the ground up, with documentation clean enough to make onboarding new engineers effortless.
Read case study