Internet connectivity for remote workers: what your business should provide

In the office, internet was a line item someone negotiated with the ISP and then forgot about. Bandwidth was ample, the connection was reliable, and if it went down, the business called the provider and escalated until it came back. Remote work pushed that responsibility out of the office and onto every employee’s home, where none of those assumptions hold. The connections are consumer-grade, the provider will not prioritize an SLA call from a residential customer, and the bandwidth in a suburban cul-de-sac on a Friday night is whatever the neighbors have left after streaming.

Businesses responded to this in three different ways. Some just decided it was each employee’s problem. Some started subsidizing home internet as a line item. Some built out full programs with stipends, backup connections, and clear policies about what the business provides and what it does not. This guide covers what good practice looks like today, what the tradeoffs are, and the questions HR and ops teams should be thinking about when they design the program – without crossing into tax or legal advice that should come from a qualified professional.

What remote work actually requires from a home connection

Start with the baseline: what bandwidth does a typical knowledge worker need to be productive?

Video conferencing

• Zoom, Teams, Google Meet HD video: 2-4 Mbps down, 2-4 Mbps up per participant
• Group video calls with screen sharing: 4-6 Mbps down, 2-4 Mbps up
• High-definition video (presentations, demos): 6-8 Mbps both directions
• Poor video (grainy, frozen, audio-only fallback): what you get with less than 2 Mbps up

Upload speed is the bigger issue for most remote workers. Residential internet is typically asymmetric (high download, low upload), and the person on the call needs to send their video stream at decent quality. A 200/10 connection (200 Mbps down, 10 Mbps up) is common but marginal for video-heavy work.

VoIP and phone

• Business VoIP call: ~100 Kbps per direction. Not a bandwidth issue on any modern connection.
• What matters more than bandwidth: latency and jitter. High-latency connections make calls feel laggy; jitter (variable latency) causes dropouts.

Cloud apps and SaaS

Most SaaS apps are forgiving. Microsoft 365, Google Workspace, CRMs, project management tools work fine on almost any residential connection. The exception is anything that streams live data (real-time dashboards, live screen sharing for support tools), which benefits from lower latency.

File sync

OneDrive, Dropbox, Google Drive do initial syncs faster on higher-bandwidth connections but run in the background during normal work. Not usually a bottleneck unless someone is transferring large design files or video regularly.

VPN and remote access

A VPN tunnel adds overhead but is not bandwidth-intensive for most work. If the employee is routing all their traffic through the VPN (full tunnel) and accessing cloud services through it, that multiplies the bandwidth requirement because the traffic is going to the office and then back out. Split tunneling avoids this.

Practical minimum

For a typical knowledge worker doing video calls, SaaS apps, email, and general collaboration:

• Acceptable: 50/10 Mbps. Works for everything but struggles with simultaneous video calls on the same connection (e.g., two family members both on calls).
• Comfortable: 100/20 Mbps. Handles most scenarios without strain.
• Future-proof: Gigabit fiber or 200/50+ cable. Expensive, usually overkill, but eliminates bandwidth as a variable.

Roles with heavier requirements (video production, large file transfers, real-time collaboration on big assets) should be evaluated individually.

Should the business subsidize home internet?

This is the question that triggers more internal debate than almost any other remote work policy. The right answer depends on your team, your industry, and your approach to remote work overall.

The case for subsidizing

• Fairness. The employee is using their personal internet connection for business activities. Covering part or all of the cost treats the home office as a business expense rather than a personal one.
• Quality control. If the business pays for the connection, it can set minimum specifications. An employee on a subsidized plan is usually willing to upgrade to meet the requirements. An employee paying out of pocket may stick with the cheapest option.
• Retention and recruiting. A connectivity stipend signals that the business takes remote work seriously. It is a small benefit but often remembered.
• Legal considerations in some jurisdictions. Some places (including California under Labor Code 2802, and similar laws in other states and countries) require employers to reimburse necessary business expenses incurred by employees. Whether home internet qualifies depends on the specifics and should be reviewed with qualified legal counsel – this guide does not substitute for that.
• Tax implications. In some jurisdictions, connectivity stipends may be tax-advantaged for both employer and employee. Again, specifics depend on the jurisdiction and should be reviewed with a tax professional.

The case against

• Administrative overhead. Managing stipends, tracking receipts, integrating with payroll, handling exceptions. For very small teams, the overhead can exceed the benefit.
• Scope creep. Once you are subsidizing internet, what about electricity? Home office furniture? Coffee? Businesses that start down the expense-reimbursement path sometimes find it difficult to draw a clear line.
• Inequity across locations. Internet costs vary enormously by region. A flat stipend feels generous in a low-cost area and inadequate in a high-cost one.
• Complexity with mixed models. If some employees are remote and some are in the office, subsidizing only the remote employees’ internet can feel like unequal treatment.

What a reasonable program looks like

For most SMBs, a flat monthly stipend is the simplest approach:

• $25-$75/month covers a meaningful portion of typical residential internet costs
• Paid through payroll so it flows through the same system as regular compensation
• Taxable or non-taxable depending on structure and jurisdiction (consult a tax professional)
• Documented clearly in the employee handbook so it is not a point of ad-hoc negotiation
• Applied consistently across all eligible employees, not case-by-case

Some businesses offer expense reimbursement instead of a flat stipend – employees submit their internet bill, business reimburses up to a cap. This is more administrative work and it tends to produce inconsistent outcomes because employees at similar pay levels end up receiving different amounts based on what plan they happen to have.

The flat stipend is usually cleaner.

What to avoid

• Reimbursing without a policy. Ad-hoc “we will cover your internet” conversations that do not get documented become disputes later.
• Tying reimbursement to hours worked from home. The connection is there whether they use it 8 hours or 12 hours. Prorating creates paperwork for no real benefit.
• Requiring bandwidth minimums the employee cannot meet. Some employees live where fiber does not exist. Setting a “must have 100/20 or better” requirement without acknowledging that reality creates a problem.
• Assuming the stipend covers a business-grade service. It does not. It is a contribution toward the residential plan the employee already has.

Backup connectivity: mobile hotspots and alternatives

Home internet outages are common, and a remote employee without a backup is idle when they happen. For a critical role, backup connectivity is worth investing in. The same logic on the office side – where one ISP failure takes the whole company offline at once – is in how to set up redundant internet for your business.

Mobile hotspots

The most common backup option. A dedicated cellular hotspot (or tethering from a phone) gives the employee a connection when the primary internet is down.

Dedicated hotspot devices (Netgear Nighthawk, Verizon Jetpack, T-Mobile Inseego, etc.) with a separate data plan, typically $30-$60/month for the device + plan. Good coverage and reliable for video calls.

Phone tethering is the cheap-and-good-enough option for most use cases. Modern smartphones can share cellular data with a laptop via Wi-Fi, USB, or Bluetooth. If the employee already has an unlimited plan, tethering costs nothing extra. If not, most carriers charge a modest add-on for tethered data.

Signal quality matters. A hotspot in a house with no cellular signal is not useful. If the employee’s home has poor reception, a dedicated hotspot with an external antenna or a different carrier may be needed.

Multi-carrier / cellular failover routers

For employees in genuinely unreliable areas, a router that supports cellular failover (Peplink, Cradlepoint, GL.iNet, some higher-end prosumer routers) can automatically switch between wired and cellular when the wired connection drops. More expensive and more complex, but seamless from the user’s perspective.

SD-WAN for critical roles

SD-WAN (Software-Defined Wide Area Network) combines multiple connections (primary broadband, secondary broadband, cellular backup) into a single logical connection with automatic failover and traffic optimization. Traditionally an enterprise technology, SD-WAN has started showing up in SMB offerings from Meraki, Fortinet, Velocloud, and others.

For most remote workers, SD-WAN is overkill. For roles where connectivity outages have real cost – executive assistants running scheduling across the business, call center agents, customer success leads, IT staff on call – it may be justifiable. Budget: $50-$200/month per seat for SMB-appropriate offerings, plus the hardware. The full picture on when SD-WAN earns its cost at SMB scale, when a dual-WAN firewall is the better answer, and how the multi-site math works is in SD-WAN for small business: is it worth it.

Co-working space as backup

A pre-negotiated arrangement with a co-working space near each employee’s home gives them somewhere to work when the home connection goes down. WeWork, Regus, and smaller independent spaces all offer day passes and flexible memberships.

The cost is typically $20-$40 per day or $200-$400 for a monthly membership, which is usually overkill unless the employee uses it regularly. Day passes on demand are often the right fit for “internet is down, I need somewhere to work today.”

What to do when a remote worker has unreliable connectivity

Not every address has access to decent internet. Some employees are in rural areas, some are in older buildings with weak infrastructure, some are in locations where fiber has not arrived. A few operational patterns help:

Understand the actual problem

Is it bandwidth, latency, reliability, or all three? Video calls that are grainy might be a bandwidth problem. Calls that drop out constantly might be a reliability problem. Calls that work but have a half-second echo might be a latency problem. The fix depends on the diagnosis.

Audit what upgrades are available

Before assuming the employee is stuck with their current service, check whether fiber has arrived in the area, whether a different cable provider offers service there, or whether a fixed wireless option (T-Mobile Home Internet, Starlink, Verizon 5G Home) would work. Some of these have become dramatically better in the last few years.

Consider the role’s real requirements

A developer working mostly in the terminal and git can tolerate worse connectivity than a customer success manager on video calls all day. Match the expected connectivity to the role, and have a plan for roles that genuinely cannot be done on a poor connection.

Have an escalation path for chronic issues

If an employee’s connectivity is consistently blocking their work, options include:

• Upgrading them to a better provider (with the business paying the difference if it is unreasonable)
• Providing a cellular backup
• Allowing a co-working space allowance
• In extreme cases, repositioning them to a role that can tolerate the connectivity
• In the most extreme cases, helping them relocate or accepting that the role requires better connectivity than they have

This is a management conversation, not an IT one. IT can diagnose what is happening. The business has to decide what to do about it.

Starlink and fixed wireless as a real option now

Starlink has matured to the point where it is a legitimate primary connection in rural areas. Speeds are typically 50-200 Mbps down, 10-30 Mbps up, with low-to-moderate latency. The equipment runs $300-$600 one-time and service is $90-$150/month. For an employee in an area with no decent wired option, Starlink often solves the problem cleanly.

Fixed wireless services from the major cellular carriers (T-Mobile, Verizon, AT&T) work well in areas with good cellular coverage and are often cheaper than fiber where available.

Roles that warrant more connectivity investment

Not every remote worker needs the same connectivity setup. The business should think in tiers:

Tier 1 – basic knowledge work

Standard remote worker doing typical office tasks. Primary connection is whatever residential service is available; backup is phone tethering for the rare outage. The business provides a small stipend if one is offered company-wide.

Tier 2 – video-heavy or client-facing

Sales, customer success, executive assistants. Video calls multiple times daily, and outages are visible to customers. These roles benefit from:

• Required minimum bandwidth (e.g., 100/20+)
• Business-provided dedicated cellular hotspot
• Co-working space budget for emergencies

Tier 3 – critical operations

Leadership on call, on-call IT staff, anyone whose outage causes business-wide disruption. Justify:

• Dedicated backup connection (SD-WAN or cellular failover router)
• Business-grade service where available
• On-call budget for connectivity issues

Tier 4 – specialized roles

Video editors, designers working with large files, engineers transferring datasets. Requires:

• High upload bandwidth (symmetric fiber preferred)
• May warrant business-grade service, business pays the full cost

The goal is to match connectivity investment to the actual cost of outages in that role.

Policy and documentation

Whatever the business decides, write it down. A connectivity policy section in the employee handbook should cover:

• Whether the business provides a stipend, and how much
• What the employee is expected to provide themselves
• Minimum bandwidth requirements (if any)
• Whether the business provides or reimburses backup connectivity
• What happens if the employee’s connection is consistently inadequate
• Who to contact for connectivity issues (IT helpdesk, not random)
• Whether the business has opinions about specific ISPs or services

The policy should be clear, public, and applied consistently. A remote work program without a written connectivity policy produces dozens of one-off conversations and no durable standard.

How this fits into broader remote work practice

Internet connectivity is one piece of the remote work IT picture, alongside device management, security configuration, and productivity tooling. It is the layer that often gets ignored because it lives outside the traditional IT scope – the ISP is the employee’s vendor, the modem is the employee’s property, the service call is the employee’s responsibility.

But connectivity is also the layer where the biggest productivity losses happen for remote workers, and it is the layer that gets flagged last when remote work is not working for a particular employee. A remote worker who cannot do their job because their internet is bad is not a training problem or a motivation problem, but the business often treats it as one.

Get the connectivity story right – what you provide, what you expect, what happens when it fails – and a lot of the “why is remote work hard” ambiguity resolves into specific, fixable problems.

Common connectivity mistakes

• No policy at all. The default becomes “figure it out” and every employee gets a different outcome.
• One-off stipends for squeaky wheels. The employees who complain loudest get connectivity help; the ones who quietly tolerate bad connections get nothing. Inequitable and corrosive.
• Requiring business-grade service without paying for it. Residential plans cost $50-$100/month. Business-grade plans cost $150-$500/month. If you require business-grade, you pay for it.
• Ignoring the upload side. Most residential internet is asymmetric. The employee’s download speed looks great; their upload struggles with video calls. Ask what the upload speed is, not just the download.
• Not planning for outages. Treating a connectivity outage as “IT will figure it out” rather than as a predictable event with a standard response.
• Over-engineering connectivity for roles that do not need it. A software engineer doing remote backend work does not need SD-WAN. A CEO on back-to-back video calls might.
• Giving legal or tax advice in the policy document. The policy can say “stipends may be tax-advantaged depending on jurisdiction; employees should consult their own tax professional.” It should not try to be tax guidance.

How Sequentur handles connectivity considerations for clients

The connectivity layer mostly sits outside the managed IT scope – the employee’s ISP is not Sequentur’s vendor, and the modem in their living room is not our asset. What we do provide is the surrounding infrastructure that makes the home connection work well: split-tunnel VPN configuration so not all traffic routes through a bottleneck, conditional access policies that do not unnecessarily re-prompt on reconnect, Teams/Zoom QoS settings that prioritize voice and video traffic correctly, and monitoring tools that flag connectivity patterns across the fleet so we can spot when specific employees are consistently struggling.

When a client is standing up a remote program and asking “what should we tell employees about internet,” we typically help shape the policy alongside their HR and ops teams – but the final decisions about stipends, reimbursement, and legal compliance sit with the client and their legal and tax advisors.

If your remote team’s connectivity story is “every employee handles it on their own” and that is producing real productivity problems, schedule a call and we will talk through what a coherent program looks like.