Small commercial portfolios
Property managers overseeing a handful of offices, retail locations or mixed-use buildings with separate water records.
Water-use planning for small property portfolios
Turn water bills into better questions.
Start with the data you already have. TechWater is a reporting concept for property teams that want to understand billed water use, investigate changes and prioritize practical follow-up.
Service design stage. Pilot availability and scope are still being defined.
Designed forSmall commercial portfolios
Proposed starting pointThe Water Use Review
Current stageDiscovery & service design
01 / Clarity before hardware
A high bill is a signal. Context makes it useful.
A longer billing period, a new tenant, landscape irrigation or a faulty fixture can all change a property’s water use. Looking at the bill total alone makes it difficult to know what deserves attention.
TechWater’s first proposed product is a monthly review built from client-supplied bills or meter exports. It would normalize records by billing duration, document context and flag questions for the property team. Connected sensors can wait until the reporting workflow earns its place.
02 / A focused starting audience
Built around real needs.
Hands-on facilities teams
Operators who can gather bills and investigate flagged changes with their maintenance providers.
Water-efficiency specialists
Professionals interested in a clearer data handoff before a site visit or equipment assessment.
03 / The first offer
The Water Use Review
A proposed reporting pilot for a small set of properties with readable billing history, a designated owner and a practical way to investigate changes.
Proposed scope · Not yet bookableA consistent bill register
Record period dates, units, billed consumption and gaps. Keep unit conversions and source records traceable.
An explained trend review
Compare daily average usage across periods, with notes for occupancy, seasonality and property changes.
A follow-up action log
Separate data questions, site checks and specialist assessments. Assign the next step and record the outcome.
04 / A practical path
From an open question
to an informed next step.
Organize the records
Collect permitted bill copies or exports, identify meters and units, and document which spaces or systems each account covers.
Review change in context
Compare periods on a consistent basis and add known occupancy or operating changes. Flag patterns as questions rather than diagnoses.
Investigate & learn
Have the property team or a qualified specialist check the site. Record what was found before deciding whether monitoring hardware is justified.
05 / What this could look like
ILLUSTRATIVE SCENARIO
More use, or simply more days?
Illustrative review: two bills show different total consumption. The first check is the number of days and the units in each period. The next is context: occupancy, irrigation schedules and known work. A change that remains unexplained becomes a site-check task.
- Verify units and billing periods
- Compare usage per day with relevant context
- Document a site check before assigning a cause
06 / What comes next
Prove the useful part.
Then build on it.
A focused service should earn the right to grow. These are proposed validation milestones, not completed achievements or enrollment promises.
- 01
Validate available records
Proposed discovery: work with 3 property operators to understand bill access, units and common data gaps.
- 02
Trial a monthly review
Test up to 10 properties over 3 reporting cycles, with permission to use records and a named follow-up owner.
- 03
Measure actionability
Track usable records, explained flags and completed site checks. Conservation savings and leak-detection performance are not claimed.
07 / Good questions
A little clarity
before we talk.
Is this live leak detection?
No. The initial concept reviews periodic records. It cannot provide real-time leak alerts, emergency protection or automatic shutoff.
Can it tell us whether water is safe?
No. Consumption records do not establish water quality or potability. Those questions require appropriate testing and qualified advice.
Do we need to install sensors?
No hardware is proposed for the first reporting pilot. Future integrations would depend on access, compatibility and a demonstrated need.
How will property data be handled?
An initial inquiry should include only a general portfolio description. Before a pilot, data permissions, transfer, access and retention would need to be agreed; do not send credentials or unredacted account identifiers now.
08 / Start a conversation
Start with one property and a clearer baseline.
Tell us what records you have and what you are trying to understand. We are shaping a reporting pilot with property teams and specialists.
Prefer email? josephjilovec@pm.me
Or use the studio contact page ↗