Built to Cut Delivery Costs, Eliminate Heavy Lifting, and Increase Consumption.
- 1Home & Office Delivery (HOD) water — ~$20B worldwide, ~$8B in the U.S. — runs on fixed schedules and guesswork: no one knows how much is left at the endpoint. The customer lifts, orders and runs out; the water company pays for empty stops, emergency runs and churn.
- 2IntelliJug puts an autonomous, IoT- and AI-based endpoint beside the existing dispenser. Every water point becomes data; every Site becomes one planned stop.
- 3Sold B2B to water companies: one contract, recurring revenue, no hardware on the balance sheet. LOI signed before prototype; a 20–30-Site pilot validates the unit economics.
An established recurring market — not a new category.
U.S. water company as Design Partner for a pilot. Signed before prototype.
A standard 5-gallon jug (~42 lb). The friction that can drive churn.
Current stage. Active fundraising process.
Market estimates vary by definition. References: HTF Market Intelligence — global home & office water delivery, $19.5B (2024) · Research and Markets / 360iResearch — global water delivery services, $23.0B (2026) · IBWA / Beverage Marketing Corporation — HOD at 9.9% of U.S. bottled-water volume (2024).
Two Problems. One Root Cause.
No one sees consumption at the endpoint — so the customer does the work, and the water company guesses.
Customer friction
- Heavy jugs — ~20 kg (42 lb), lifted and replaced by hand.
- Manual ordering — reactive and error-prone.
- A bulky Rack — buffer jugs held because delivery timing is unreliable.
- Running out — service disruption, and churn.
Water-company inefficiency
- No visibility — no precise data on what is left at the endpoint.
- Fixed routes — empty stops, low Jugs Per Stop.
- Zero-Outs — emergency deliveries, and consumption lost in the gap.
- Demand swings — summer and day to day; a fixed schedule sees none of it.
The optimization opportunity — in numbers
per stop — every non-optimal stop costs
a day, per route
a day, per route — emergency deliveries; one of the major problems at scale
per emergency delivery
scattered at every endpoint — for fear of running out
of churn — poor service, and price
Operating data mostly from our Design Partner, the rest from industry estimates. U.S. figures shown as the example; the underlying economics are broadly similar across HOD markets worldwide, with local variation. The results of this inefficiency can be seen in the documented customer complaints on the home page.
Operational pressure is rising — just as endpoint intelligence becomes deployable at scale.
Operational pressure is rising
- Last-mile costs — drivers, fuel, service — keep rising. Profitability is decided by cost-to-serve per stop, not by the price of a jug.
- Customer complaints repeat three things: run-outs, the weight of the jug, unreliable service.
- Water companies need a lever that is not price: service reliability and cost-to-serve.
The solution became possible
- Sensors, connectivity and Cloud infrastructure are cheap enough to sit at every endpoint.
- IoT and AI now run predictive operations at scale.
- The industry already manages by KPIs — Route Density, retention, cost-to-serve. Only the data that feeds them is missing.
HOD is a price-driven market, not a value-driven one: no product differentiation, competition on price and service alone.
The water company knows what it delivered. It can only guess how much is left.
Multi-point Sites first: 3–20 water points, one Hub, one planned stop.
Why this segment — the Pareto
A minority of accounts carries the majority of volume: roughly 15–25% of commercial accounts hold 35–50% or more of commercial volume. Few customers, high volume, many points per sale — and a buyer (commercial leadership with operations and finance) who decides on volume, forecast demand and cost-to-serve.
Not the target — yet
Pallet-scale Sites consuming hundreds of jugs a week, forklift-unloaded at a loading dock: pallet logistics, not dispenser logistics — a later configuration. Homes follow on the same platform, after cost-down.
Schematic only. Axes are unscaled and no values are implied.
Today — and with IntelliJug.
The platform itself is described on the home page and on How It Works. Here — only what changes.
| Today | With IntelliJug |
|---|---|
| For the customer | |
| Lifts and replaces ~20 kg jugs by hand. | No lifting — the unit stores and switches the jugs. |
| Often orders manually, or waits for a fixed route; keeps buffer jugs in a Rack. | No ordering, no tracking — no Rack. |
| Can run out — and then wait for an emergency delivery. | Supply planned on real consumption, before it runs out. |
| Service friction is the main reason customers leave. | A customer who no longer thinks about water tends to stay. |
| For the water company | |
| Fixed routes — and, at scale, mostly guesswork. | Just-in-Time (JIT) delivery on real consumption. |
| Some stops find nothing to replace; Jugs Per Stop stays low. | Fewer empty stops; higher Jugs Per Stop and Route Density. |
| Zero-Outs mean emergency runs and lost consumption. | Zero-Outs predicted days ahead; a full endpoint consumes more. |
| No precise data for every point. | One planned stop per Site — and operational data across the network. |
One Contract. One Invoice. Cost per endpoint falls as the Site grows.
SaaS per endpoint
Dashboard, operational analytics and AI-driven optimization. Recurring revenue (ARR).
Consumption fee
A small per-gallon fee, aligned with value: IntelliJug earns when consumption grows — and so does the water company.
Water-Company-Owned hardware
Designed by IntelliJug, built by a contract manufacturer, transferred at cost. No hardware margin, no HaaS.
The value engines — what the water company pays for
Route economics
Fewer stops, higher Jugs Per Stop, higher Route Density — Just-in-Time delivery on real consumption.
Supply continuity
Zero-Outs predicted days ahead: fewer emergency deliveries, no consumption lost in the gap.
Retention
No lifting, no gaps, no service friction — the churn engine switched off.
Consumption
An endpoint that is always full consumes more — and the water company sells more.
Unit economics — for the water company
Hardware is a one-time CapEx at cost, on an asset it owns; the platform fee is OpEx — a low-double-digit share of endpoint revenue. The Hub carries the expensive components once per Site: cost per endpoint falls with Site size while the value engines multiply with every point.
Unit economics — for IntelliJug
Recurring revenue from every connected endpoint. No hardware on the balance sheet (asset-light) — a structurally high gross margin. Growth from Site depth first, then from the number of customers.
Pricing is staged: each tier opens on value measured in the field, starting with the pilot. All figures are preliminary.
What is validated today — early de-risking.
- A signed LOI with a U.S. water company for a 20–30-Site pilot.
- Operator data in the model — stop cost, jugs per stop, Zero-Outs, seasonality, buffer stock, churn drivers.
- Strategy reviewed point by point with a senior advisor from a national HOD network — and confirmed in all aspects.
- Consultations with several former senior executives of leading global water companies.
- A live Hub & Spoke Site dashboard — what the water company sees — on the home page.
- Engineering — detailed system architecture, advancing to an integrated prototype with a systems-engineering partner.
Validated · modeled · measured in the pilot
Validated today
Signed LOI · operator data · market size · Hub & Spoke architecture · volume concentration in the segment.
From the model — preliminary
Unit economics · Site economics · value engines · staged pricing · break-even.
Measured in the pilot
Operator value vs. fee · Zero-Out reduction · consumption uplift · placement time and cost · hardware cost at scale · Site-type mix.
To validate in the U.S., then scale through water companies worldwide.
Validate
A 20–30-Site pilot with the U.S. Design Partner: real deployment, live operating data, a model that is measured — not assumed.
Commercial activity from a working prototype
Not waiting for the end of the pilot: mid-size U.S. operators, mainly through connections; in parallel, operators in additional target markets — the Gulf states, India, several European markets and more.
Land-and-Expand
From pilot Sites to all of the operator’s multi-point Sites, then to its full customer base. National operators and global water groups after quantified proof — upside, not the base case.
Pilot and Pre-Seed milestones — 15 months
Integrated prototype
From detailed system architecture to an integrated hardware-software prototype; software in parallel from month 0.
Pilot-ready MVP
Hardware-software MVP; manufacturing and supply-chain evaluation; suppliers for the first series.
20–30-Site pilot
U.S. deployment with the Design Partner: unit economics and pricing measured on live data; first series ordered inside the pilot.
Field validation and first deployments
Unit economics and pricing validated in the field; production readiness; first deployments.
Capital deployment
In tranches against milestones. The round proves four things: prototype, MVP, pilot, field-validated unit economics.
Where we are today
Pre-prototype: the system architecture is in detailed design, and the integrated prototype is the first milestone of the round. Preparing the MVP and the pilot; not yet at the revenue stage.
Team and current capabilities.
Additional information
Detailed investor materials — commercial validation, Site economics, the pilot pathway and the team — are available on request.
Request Investor MaterialsImportant Notice. This page is for information only and does not constitute an offer to sell, or a solicitation of an offer to buy, any securities. IntelliJug is a development-stage company; its products are under development and are not yet commercially available. Statements about plans, timelines, economics and expected outcomes are forward-looking, preliminary, and subject to validation in the pilot. Market and operating figures are drawn from third-party sources, operator data and industry knowledge and have not been independently verified. Links to third-party sources are provided for reference only; IntelliJug is not affiliated with, and does not claim endorsement by, those sources.
Confidentiality. The Design Partner is not named under a non-disclosure agreement. All content on this page is the property of IntelliJug.
