Snow Route - Sell Project

Title: Snow Route: Snow Clearing Route & Storm-Day App for Small Crews, Pre-Revenue Tagline: Keeps snow clearing stops in order on storm day, so the crew always knows where to go next. Listing type: Starter project / pre-revenue app MVP Revenue: $0. No paying customers, and no sales have ever been made. Traffic: Not tracked separately for this app. No verified visitor, sign-up or user numbers are available. Asking price: $600 USD (estimate; see rationale below) Demo: https://westbridgeindustrialinc.com/apps/snow-route/ Description Who it's for: small snow removal and landscaping crews, property maintenance companies and solo plow operators. The problem: on a storm day the crew works from a paper list or a group text. Stops get missed, the order wastes driving time, and at the end nobody has a clean record of what was cleared, when, and what to bill. What works today (a working front-end MVP): Client list: name, address, phone, service type (driveway, walkway, salt), priority 1–3, seasonal or per-visit billing with a price, and notes such as gate codes. Address lookup: turns an address into map coordinates using OpenStreetMap (Nominatim), or you can type them in by hand. Storm day: one tap builds the day's route from the client list. Order by priority, or "Best route from start", which plans a short driving order from the crew's start point (nearest-neighbour plus a 2-opt clean-up, straight-line distance). Drag-and-drop or up/down reordering, a Map link for each stop (opens Google Maps directions), Done and Skip with a reason (car in driveway, gate locked, and so on). Proof photo for each finished stop (compressed and saved on the device), and a "Text customer" link that opens the phone's own SMS app with a "your driveway has been cleared" message. End-of-storm summary with done and skipped stops, times, per-visit amounts to bill, and CSV export. Mobile-first layout for use in the truck. What is NOT built yet (be clear on this): No user accounts, logins or multiple users. All data is saved only in the visitor's own browser (localStorage), on that one device. No backend or database, and no syncing between devices or team members. Route distances are straight-line estimates, not road distances. There is no turn-by-turn navigation or live traffic. No automatic texting. Messages are sent by hand from the crew's phone, and an SMS service still has to be built. No GPS tracking of crews and no invoicing. Billing is a summary and CSV only. Address lookup uses the free public OpenStreetMap service, which has usage limits. A buyer running this at scale should switch to a paid geocoder. No billing or subscriptions, and no payment integration. No customers, no reviews and no revenue history. The screenshots use made-up EXAMPLE data, and the app labels it on screen. None of those names, numbers or dollar figures are real customers or results. What the buyer gets Full source code for the Snow Route app: index.html, app.js and styles.css, about 21 KB of hand-written code. The right to use the "Snow Route" name. No trademark is registered. Screenshots and this write-up for marketing. Not included: No domain. Snow Route has no domain of its own. It currently runs as a demo inside westbridgeindustrialinc.com, and that domain and the Westbridge brand are NOT for sale. The Westbridge logo, header, footer links and site tracker script. These are removed from the code before handover. No customer list or customer data, because none exists. Tech stack (verified from source) Plain HTML, CSS and JavaScript. No framework, no build step and no dependencies. State lives in the browser's localStorage. CSV files are made in the browser with Blob downloads. Runs as static files on any host (it is currently hosted as static files on Vercel). It needs no server or paid services to run. Geocoding uses the public OpenStreetMap Nominatim API, rate-limited in code to about 1 request a second. Monetization idea for the buyer (suggestion only, not tested) Sell it as a low-cost monthly app to snow and landscaping crews, priced per truck or crew. Add accounts, a shared crew view and automatic "cleared" texts, then bundle it with invoicing. These are ideas, not projections. No pricing has been validated with customers. Asking price rationale (estimate) Replacement cost: a freelancer would likely need about 15–25 hours to design, build and test an MVP like this. At a typical USD 40–75/hr, that is roughly $600–$1,875. This is our estimate, not a quote. Discount: it is pre-revenue, front-end only, comes with no domain, and the buyer still has to build accounts, a backend and billing. Pre-revenue starter apps usually sell well below their build cost. Suggested ask: $600 USD. Reason for selling Westbridge Industrial Inc. builds many small business apps. We're selling Snow Route as a ready-to-extend starter so we can focus on our core services, rather than running it ourselves.