Most startups in Salt Lake City are underinsured and underprepared for serious water damage, even though one burst pipe can burn through a month of runway faster than a failed ad campaign. What if I told you a single bathroom leak on a weekend can quietly rack up 5 figures in losses before Monday standup, and most founders do not notice the real cost until three months later when payroll suddenly feels tight? The short answer: if your team works in any physical space in Salt Lake City, you need a simple, written plan for water damage, a trusted local partner for water damage remediation Salt Lake City, and a basic habit of documenting your risks like you document your code.
That is the TL;DR. Treat water like a business risk, not a maintenance chore. Have one sheet of paper that says who to call, where to shut things off, what to move first, and how to keep the company running if your office is suddenly wet or unusable. That alone puts you ahead of most seed stage teams.
Let me walk through how to do this in a way that feels realistic for a small tech company, not for a giant corporate campus with a facilities department.
Why water damage matters more to startups than they think
Most founders I know worry about burn rate, hiring, and product-market fit. Physical risk feels dull by comparison. I used to think the same thing until a friend had a small flood in their coworking space and lost two custom servers, a prototype box, and a week of productivity trying to rebuild laptops from backups that were not as current as they thought.
Here is the part many people miss:
Water damage is not just about wet carpet; it is about downtime, lost data, delayed demos, and reputational damage with clients who suddenly cannot reach you.
In a city like Salt Lake, you also have a mix of older buildings, quick weather swings, and winter pipes that like to crack at the worst possible time. If you are in a basement office or in a converted older building near downtown, your risk is higher than you probably assume.
This is not just a facilities issue. It is a business continuity issue. That sounds like corporate jargon, but in plain terms it means “can we keep working and making money if something in the building goes wrong?”
The hidden math: what water really costs a startup
To make this concrete, imagine your 12 person team works out of a small office in downtown Salt Lake. A failed supply line in the bathroom on Friday night runs until Saturday afternoon before anyone notices.
Here is a simple look at what that can mean.
| Item | Rough impact |
|---|---|
| Emergency response & drying | $3,000 – $7,000 |
| Carpet, drywall, ceiling repairs | $2,000 – $10,000 |
| Hardware damage (laptops, servers, monitors) | $2,000 – $15,000 |
| 3 days of lost productivity (12 people) | $6,000 – $12,000 in salary burn with no output |
| Lost deals / delayed launch | Hard to measure, but often more painful than repairs |
You do not feel this in one line item. It creeps up across different accounts. That is why founders underestimate it. You see a $6,000 invoice from a remediation company, but you do not connect it with the delayed release that cost you a contract.
So the point is not to panic. It is to treat water like any other risk: quantify it a bit, put in guardrails, and keep the plan simple enough that people will follow it.
Risk checklist: how likely is serious water damage in your space?
Before you over-plan, it helps to get a rough sense of your own odds. I will keep this simple and practical, not a 20 page risk assessment.
Ask yourself these questions during a quick walk around your office:
- Are you in a basement or ground-level unit?
- Do you share walls or floors with other tenants who have water use, like restaurants, salons, or gyms?
- Do you have older plumbing or visible corrosion on pipes or fixtures?
- Are there water heaters, boilers, or mechanical rooms near your unit?
- Do you see water stains on ceilings or walls?
- Is your server rack, network gear, or main power strip on or near the floor?
- Do you have any storage rooms with boxes on the floor instead of on shelves or racks?
- Have you had any roof leaks or ice dam issues in past winters?
If you answer “yes” to more than a few of these, your risk is not theoretical. It is moderate to high.
I sometimes tell founders: if you would not store your own passport or personal hard drive on that floor overnight, you probably should not keep your company hardware or paper records there either.
Salt Lake City specific risks startups forget
Salt Lake has some quirks you will not see in generic online guides.
- Snow melt periods where roofs and drains get overwhelmed for a few days.
- Older office conversions downtown with plumbing upgrades that are “good enough” but not great.
- Swamp coolers or old HVAC units on roofs that can overflow and leak into top floors.
- Basements that feel dry most of the year but get seepage during heavy rain.
If your startup is using a cheap older space to save cash, you might be accepting risk without realizing it. I am not saying move out tomorrow. I am saying walk your space with your eyes open and maybe adjust where you place critical gear.
The simple emergency playbook every startup should have
You do not need a giant binder. You need one short document that any team member can follow. I like to keep it to one printed page on the wall and a copy in your shared drive.
Here is what that playbook should cover.
1. Who to call first and second
In most water situations, the order matters. Too many people call the landlord, leave a voicemail, then wait. The water keeps spreading while you wait for someone to call back.
Your one pager should say in big letters:
If you see active water, first priority is to stop the source and protect people and equipment. Landlord and insurance come after.
Practical order for a typical startup office:
- Building maintenance or manager (if they control main water shutoffs).
- Licensed plumber or emergency maintenance contact.
- Water damage remediation company.
- Founders / leadership group chat, if they are not on site.
- Insurance agent, after the water is under control and documentation starts.
You might disagree with this order, and that is fine, but pick an order and write it down. Include actual phone numbers, not “see the contact list.”
2. Where to shut off water and power safely
During a walkthrough, ask your landlord or building engineer to show you:
- Main water shutoff for your unit.
- Local shutoffs for bathrooms, kitchenettes, and any mechanical closets.
- Main electrical panel for your unit and which breakers cover which areas.
Take photos, drop them in a short doc, and label them clearly.
I know this sounds obvious, but I have seen engineers and CTOs who can rebuild an API cluster from scratch but have no idea where the water valve is. In an emergency, they are scrolling email threads trying to find the building manager number while the ceiling drips onto a conference room table with four MacBooks on it.
3. What to move first when water hits
You cannot save everything, and you do not need to. You just need to know your order of operations.
A simple mental rule that works well:
First protect people, then hardware, then irreplaceable records, then furniture and finishes last.
For a tech startup, your priority list will often be:
- People and safety: no one standing in water near live outlets or extension cords.
- Servers, NAS boxes, modems, routers, and switches.
- Laptops and desktops on or near the floor.
- Paper records that cannot be recreated, like signed originals if you keep any on site.
- Special equipment like lab gear, 3D printers, or prototypes.
Have one or two people on your team who know where all this hardware lives and who can act quickly without asking for permission.
You might think “our stuff is all in the cloud, we are safe.” But your local routers, firewalls, and power strips are still in the physical world, and water does not care about your cloud-first architecture.
Working with a water damage company without losing control of costs
In a real event, you will not have time to compare every provider in detail. That is why it helps to loosely vet at least one local company before you ever need them.
I am not going to tell you which vendor to pick. What matters more is how you manage the relationship.
Questions to ask before you sign anything
During your next quiet week, call one or two local remediation providers and ask direct questions. Write the answers in your one pager.
Some useful questions:
- Do you provide 24/7 response in Salt Lake City, and what is your typical arrival time?
- Do you work directly with commercial insurers, or do you bill us and we handle reimbursement?
- How do you estimate the scope and cost before starting work?
- Can you explain which actions are urgent and which can wait for approval from a founder?
- Do you have experience with offices that have server rooms or sensitive electronics?
This conversation does not need to be long. You just want to hear how they talk about costs, consent, and communication. If they push you to sign a long-term contract for priority service before answering questions, that is usually a red flag for a small startup.
What happens in the first 24 hours of remediation
Whatever provider you pick, the first 24 hours follow a predictable pattern. Knowing the steps helps you stay calm and avoid agreeing to things you do not fully understand.
Typical sequence:
- Assessment: They walk the site, take moisture readings, and document visible damage.
- Water removal: They pump or vacuum standing water on floors or carpets.
- Demo decisions: They decide what to remove right away, such as soaked carpet pad, baseboards, or parts of drywall.
- Drying setup: They place fans, air movers, and dehumidifiers and might leave them running for several days.
- Monitoring: They return periodically to check moisture and adjust equipment.
Your job as a founder or office lead is to ask clear questions:
- Which areas are unsafe for my team right now?
- How long before we can safely work here again?
- Can we isolate a room to use as temporary workspace?
- What is your rough cost range if everything goes as expected?
Someone needs to be on site to sign off on demo work. Removing materials might be needed to prevent mold, but it also ripples into repair costs and downtime. If the team is about to tear out a section of wall next to your network closet, you want to be very sure you understand why.
Insurance, leases, and boring documents that suddenly matter
This is the part most founders push off because it is dull. I understand the temptation, but this is where a few hours of preparation can save you weeks of frustration later.
What to check in your lease
Pull out your lease and look, slowly, for three things:
- Who is responsible for interior plumbing repairs and who covers building plumbing failures.
- Who handles insurance for the building structure versus tenant improvements.
- Any clauses about water damage, roof leaks, or acts of nature that affect your unit.
You might find language that says the landlord covers building systems, but you are responsible for your own contents and any tenant improvements like custom glass walls, extra outlets, or a server room.
If you see something you do not quite follow, ask a real estate attorney or a more experienced founder for a plain language explanation. You do not need a long memo, just clarity on “who pays for what.”
What to check in your insurance policy
Commercial policies vary a lot. Some cover water from burst pipes but not from surface flooding. Some cover lost income from business interruption, some do not.
Look for:
- Coverage for water from internal sources like plumbing or sprinkler lines.
- Coverage for water from external sources like flooding or surface water.
- Coverage for mold if not addressed quickly.
- Coverage for business interruption and how long it applies.
- Any deductibles that apply to water events.
I personally think many very early startups skimp too much here. They pay for liability because the lease forces them to, but they underinsure contents and skip interruption coverage. That can be a mistake if your whole company depends on a small set of physical tools.
Documenting damage like a founder, not like a victim
When water hits, you will want to move fast, but you also need records. Your future self, your insurer, and maybe your landlord will thank you.
Basic approach:
- Take wide shots of each affected room.
- Take close shots of damaged items and their serial numbers if visible.
- Keep a written list of each item, approximate purchase date, and replacement cost.
- Save every email, text, and invoice related to the event in one shared folder.
If you have a project manager or operations person, this is a good task for them. It suits their mindset and frees engineers to handle technical recovery.
Treat the event like an incident in your product: you collect data, keep a clear log, and avoid making big assumptions while emotions are running high.
Protecting data and hardware when the office gets wet
From a tech perspective, your real concern is less about carpet and more about data, continuity, and customer trust.
Server rooms and network closets
If you still run any on-prem gear, ask a grim question: what happens if there is 2 inches of water on the floor in that room?
Simple physical steps that help a lot:
- Put servers and network gear on wall-mounted racks or at least on raised platforms, not on the floor.
- Use power strips with surge protection mounted off the floor.
- Label all network cables and power cords so you can unplug and move fast without confusion.
- Keep a basic set of spare cables and a backup router or firewall in a separate, dry location.
Many small teams still treat the network closet like a junk cabinet. Cleaning it up and raising hardware off the floor is a one time effort that takes an afternoon and can save you from a lot of pain.
Cloud-first teams are not fully safe
Plenty of startups say “we are cloud-native, water cannot hurt us.” That is not quite true.
Water can still:
- Take down your internet if the building network hardware is affected.
- Destroy laptops that hold cached credentials, local code, or design files not yet pushed.
- Force you out of the office into a scramble of remote work before people are ready.
So at least once a quarter, ask your team:
- Can everyone work from home or another site on short notice, for a week?
- Are local files synced regularly to your cloud storage or repo?
- Do you have a plan for support lines or phone numbers that are tied to the office?
If the honest answer is “not really,” you have homework, even if your servers live in someone else’s data center.
Keeping the team calm and productive during disruption
Water damage is stressful. Fans are loud, carpet smells weird, and people worry about their gear. That anxiety can spread and harm morale, which is fragile in early stage teams.
Communication matters more than you think here.
How and what to tell your team
When an event happens, send a single clear update in your main communication channel.
Keep it short and factual:
- What happened.
- Safety status.
- Work plan for the next 24 to 72 hours.
- Where to ask questions.
Example structure:
“Quick update: A supply line in the kitchen failed overnight and affected the front half of the office. No injuries. Remediation crew is on site now. Today and tomorrow we will work fully remote while they remove wet materials and start drying. Please do not enter the office unless asked, because there are open panels and fans running. We will share photos and next steps by 6 pm today in this channel.”
This level of clarity keeps rumors from filling the gap. You do not need to over-share, but silence can cause more stress than the event itself.
Handling customer communication
If the incident affects uptime, support, or delivery dates, tell your customers before they figure it out.
You do not have to dramatize it. A simple note to key accounts might look like:
- Brief description of the issue.
- Impact on your services, if any.
- Expected duration.
- Any workarounds or alternative contacts.
Founders sometimes worry that being honest about a physical incident makes them look weak. In practice, clear communication often builds trust, as long as you show you are taking responsibility and have a plan.
Preventive steps you can actually fit into a startup schedule
Long lists of preventive tasks are nice on paper, but they often never happen in small teams. I think a better approach is to pick a few high impact habits that you can actually keep.
Here are practical things you can do without turning your office into a construction site.
Quarterly 30 minute facility check
Once per quarter, assign one person to walk the space with a simple checklist:
- Look for new stains on ceilings or walls.
- Check beneath sinks for leaks or moisture.
- Confirm nothing critical is sitting directly on the floor.
- Verify easy access to shutoff valves and the electrical panel.
- Take 3 to 5 photos of key areas for your records.
Set a recurring reminder and rotate the person who does it. You do not need a property manager; just someone attentive.
Moving critical gear off the floor
This is boring but powerful. Make a short list of hardware and records that should never touch the floor in a ground level or basement office.
Typical items:
- Backup drives.
- Network gear.
- Desktop towers.
- Boxes with contracts or financial records.
Buy cheap shelves, use pallets, or wall mount anything you can. This is a one time change with permanent value.
A short “office disaster drill” for new hires
When someone joins, you probably show them your codebase and your product roadmap. Consider adding a 5 minute “what happens if the building has an issue” briefing.
Cover:
- Where exits are and where not to stand if water appears.
- Who to ping if something looks wrong with plumbing or leaks.
- Where the one page emergency sheet lives.
It feels a little overcautious, but people appreciate knowing you have thought about their safety, not just their output.
Framing water risk for investors and the board
This might sound strange, but for some startups, showing responsible planning around physical risk is part of a broader story: “we run this company like adults.”
You do not need a special slide for “pipe failures,” but when you talk about operational maturity, you can briefly mention:
- We have a basic incident response plan that covers office disruptions.
- Our data is backed up offsite and we can run remote on short notice.
- We know who to call for building issues and how it affects our insurance.
Investors tend to respect founders who look beyond the product and think about staying alive as a business. If that sounds boring compared to chasing growth, that is kind of the point. Boring resilience often keeps the lights on when flashier things fail.
FAQ: real questions founders in Salt Lake actually ask
Question: Is this overkill for a 5 person startup in a small office?
Probably not, as long as you keep it light. You do not need a consultant or a thick manual. You need:
- One page with phone numbers, shutoff info, and priorities.
- Quarterly 30 minute check of your space.
- Cloud backups and a realistic remote work plan.
Those are low effort compared to the cost of losing a week to a burst pipe.
Question: Can we just rely on our landlord and insurance for all of this?
You can try, but I think that is risky. Landlords care about the building. Insurers care about the policy. Neither is focused on your team’s productivity or your release schedule.
They might eventually fix everything, but your runway and customer relationships cannot wait for “eventually.” That is why you need your own plan, even if they cover some of the bills.
Question: What is the single most useful step we can take this month?
If you want one simple step, I would pick this:
Create and print a one page “water incident” sheet that lists shutoff locations, key contacts, and what to move first, then walk the space with your team for 15 minutes to explain it.
It costs almost nothing, makes your team safer, and gives you a level of preparedness that many much larger companies still lack.