Home · Community report
Catch a costly water leak
Catch a costly water leak. Review your water usage history for a pattern worth a physical check before it adds up.
What you can get
Reaches your accounts Creates or changes things in accounts you connect, with your approval.
-
It does
- Flags a usage pattern from the data you provide
- Does not contact the water utility or a plumber on your behalf
-
It stops and asks
- Before it starts: confirm what usage history or billing data is actually available.
- On a flag: check for a non-leak explanation (pool fill, irrigation, guests) before assuming a leak.
- If a leak seems likely: get a physical check or a plumber, since data alone doesn't confirm it.
Derived from this task's own brief and steps, not from the source.
- Gather usage history
At least a year of water bills or usage data, if available.
- Compare against a baseline
Flags a sustained increase against your own normal pattern.
- Check for ordinary causesStops for your approval
You rule out pool fills, guests, irrigation and similar explanations.
- Investigate physicallyStops for your approval
A meter check or plumber confirms or rules out an actual leak.
Editorial, not from the source
Works when
- Your water utility provides usage history, not just a total bill.
- You want a flag worth investigating physically, not a diagnosis.
- You can compare the flagged period against a plausible explanation (pool, guests, irrigation) yourself.
Does not work when
- You only have a single bill with no usage history to compare against.
- You need a plumber's physical inspection, which this doesn't replace.
- You want certainty about the cause rather than a flagged pattern.
Catch a costly water leak: review template
| Period | Usage vs. baseline | Your check |
|---|---|---|
| [Flagged period] | [Increase shown] | [Ordinary cause ruled out?] |
| [Baseline period] | [Normal usage] | [Comparable season] |
| [Next step] | [Meter check/plumber] | [Confirmed or not] |
The source case
On X, @austin_hurwitz says Instinct found a water leak that had cost them $5,000 that year, in a short post with an attached image, and takes it as a sign personal agents are here to stay. The post does not say how the leak was found, what it monitored, or how the figure was calculated, and nothing here has been run by this directory.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
Instinct just found a water leak that cost me $5K this year
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Water bill or usage history, Comparison period. Acts Flags a usage pattern from the data you provide. Does not contact the water utility or a plumber on your behalf. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Water bill or usage history
- Comparison period
Connected
- Your water utility account, if usage history is pulled from there
How to try it
Editorial, not from the source
- Give it access to your water bill or usage history, and say how far back to compare, since a leak shows up as a change over time, not a single reading.
- Ask for the actual numbers behind any flag: which period's usage or cost looks unusual compared to which baseline.
- Use the flag to go physically check for a leak (meter, fixtures, outdoor lines) or call a plumber, rather than treating the flag itself as a diagnosis.
- If a leak is confirmed, keep the bill or usage record that showed it, since it may be useful for a plumber or an insurance claim.
Compare usage over time, not a single bill
A single water bill tells you what you were charged, not whether something changed. A leak, especially a slow one, shows up as a pattern: usage that climbs and stays climbed across several billing periods compared to a stable baseline from before. Give it enough history, ideally a year or more, to establish what normal actually looks like for your household, including any seasonal patterns like irrigation in summer or guests over a holiday. Without that baseline, an unusual-looking number might just be unusual for the one month you happened to look at, not evidence of anything ongoing, which is why a single bill on its own is rarely enough to act on with any confidence.
Rule out the ordinary explanations first
A spike in water usage has several common, harmless explanations: filling a pool, a visiting relative staying for a while, new irrigation, a garden hose left dripping, or simply a billing or meter-reading error. Before treating a flagged pattern as a likely leak, go through what actually happened during that period, month by month, and see if an ordinary explanation accounts for some or all of it. This isn't about dismissing the flag, it's about making the eventual physical check more targeted: if nothing ordinary explains a sustained increase, that's a stronger signal worth walking the property or checking fixtures for than a number that already has an obvious, harmless cause behind it.
Use the flag to go find the leak, not as the finding itself
A data pattern can tell you that something changed; it can't tell you where the water is going. Treat a flagged increase as the reason to check physically, listening at the water meter when everything is off, checking for damp spots near pipes and fixtures, running a dye test in a toilet tank, or bringing in a plumber if nothing obvious turns up. If a leak is eventually confirmed, keep the usage history or bill that first showed the pattern; it can help a plumber understand how long it's been running, and it may be useful documentation if you pursue a reduced bill through your utility's own leak adjustment program, where one exists.
Open Instinct to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
- The source gives no detail on how the leak was found, what data was reviewed, or how the $5,000 figure was calculated.
- An unusual usage pattern can point to several things besides a leak: a filled pool, extra guests, irrigation changes, or a billing error.
- This reviews data you provide; it does not physically inspect pipes, fixtures, or a meter, and cannot replace that inspection.
- A cost figure attributed to a leak after the fact is an estimate based on billing, not a verified measurement of water lost.
Editorial, not from the source
- Before it starts: confirm what usage history or billing data is actually available.
- On a flag: check for a non-leak explanation (pool fill, irrigation, guests) before assuming a leak.
- If a leak seems likely: get a physical check or a plumber, since data alone doesn't confirm it.
Editorial, not from the source
- A usage spike has an obvious non-leak explanation
- Rule it out explicitly, a pool fill, a visiting relative, new irrigation, before treating the pattern as a leak signal.
- No usage history is available, only a total bill
- Request usage history from your water utility first; a single total figure usually isn't enough to spot a pattern.
- A leak is flagged but can't be found physically
- Check less obvious spots, irrigation lines, a water heater, a toilet that runs quietly, or call a plumber with the flagged pattern in hand.
Common questions
Can this tell me where a leak is?
No. It can flag that usage looks unusual compared to your own history. Finding the actual leak still takes a physical check or a plumber.
How much usage history do I need?
A year or more is best, since it captures seasonal patterns like irrigation. A single month or bill usually isn't enough to tell a leak from normal variation.
What else could cause a usage spike besides a leak?
A filled pool, extra guests, new irrigation, a dripping hose left on, or a meter-reading error. Rule these out before assuming a leak.
Can my water utility reduce my bill if a leak caused it?
Many utilities have a leak adjustment program for exactly this. Keep the usage history that showed the pattern; it's useful if you apply.
Is the dollar figure in a leak report reliable?
Treat it as an estimate based on billing, not a measured amount of water lost. The actual cost depends on your rate and how long the leak ran.
Next in Home
Get recurring task recommendations — ask your own agent to check for relevant updates.