The numbers, published quarterly.
Every operator promises local benefit. NexWave delivers a Quarterly Community Impact Report instead: jobs, wages and local spend from your routed outbound work, counted with a named methodology, formatted so your community affairs team can republish it without editing a word.
A report shaped like a benefits report, pointed at community economics.
The model already exists in this industry. Iron Mountain publishes a per customer Environmental Benefits Report: a branded, defensible document a customer can hand to a stakeholder without translating anything. NexWave builds the same artifact and aims it at the question communities are actually asking, which is not about the facility. It is about the town around the facility.
Every quarter, per engagement, we publish what your outbound work did locally: how many jobs it supported, what those roles paid, which verified local providers received the work, and what the routing saved you in dock labor and transport. The methodology is attached to every copy, because a number without a method is a brochure.
- Per engagement. Your facility, your routed volume, your providers. Not an industry average with your logo on it.
- Shareable by design. Written and formatted for republication by your community affairs and public relations teams, with the source status of every factor marked.
- Cumulative. Quarter over quarter, the report becomes the local ledger nobody currently keeps.
- Headline setJobs, wages, local spend and operator savings for the quarter, on one page.
- Jobs supportedBy role and by provider category, each one attached to work that happened.
- Dollars kept localWages and recovered asset value, itemized and reported as separate subtotals.
- Operator savingsDock labor and transport legs removed, at stated rates against stated move counts.
- Provider rosterEvery local business the facility engaged, named, with its county and category.
- Methodology appendixThe model class, what is counted, what is not, and the source status of every factor.
The same six pages every quarter, so one report can be read against the last.
Every figure on this page comes from the illustrative 100MW model, and every one of them is labelled as such.
What follows is a designed sample built entirely from the reconciled model rather than from a delivered engagement, because NexWave publishes the arithmetic before it publishes a result. The derivations are printed, the factors still awaiting an operator’s written confirmation are marked, and the label travels with every number on every page. Your quarterly report replaces all of it with measured actuals from your own routed work orders.
Illustrative model: 100MW facility. Sustainability figures are deliberately absent from this headline set; the reason is stated in full in the methodology below.
Where 153 jobs come from.
The headline job count is not a multiplier applied to a payroll figure. It is a list of roles, each one attached to work that has to happen somewhere and currently happens out of state.
| Role | What the role covers | Annual roles |
|---|---|---|
| Data center direct employees | Steady state staffing for the modeled facility | 75 |
| Processing roles, secure storage and ITAD | Provider side headcount receiving routed work | 45 |
| Logistics, drivers | Transport between dock, storage and disposition | 20 |
| Ongoing maintenance | Local crews on a standing maintenance relationship | 10 |
| Skilled technicians | Specialist roles retained locally rather than flown in | 3 |
| Total | 153 |
Illustrative model: 100MW facility.
$14.1M of it is wages paid to people who live here.
The economic impact line splits cleanly in two: wages, which depend only on headcount and pay rate, and recovered asset value, which depends on how much hardware actually moves through the chain. We report them separately because they have different confidence levels, and pretending otherwise is how impact numbers lose their credibility.
Wages subtotal, $14.1M
| Wage line | Derivation | Annual value |
|---|---|---|
| Data center direct wages | 75 roles at $110K average | $8,250,000 |
| Storage and ITAD processing wages | 45 roles at $65K average | $2,925,000 |
| Skilled labor wages, maintenance and technicians | 13 roles at $125K average | $1,625,000 |
| Logistics wages | 20 drivers at $65K average | $1,300,000 |
| Wages subtotal | $14,100,000 |
Illustrative model: 100MW facility. The wages subtotal is volume independent: it holds whatever the hardware throughput turns out to be, which is why it is the figure we lead with.
Recovered asset value, $12,300,000
| Recovery line | Derivation | Annual value |
|---|---|---|
| Server value recovery | 1,250 servers at $6,000 recovered value | $7,500,000 |
| Drive value recovery | Storage media resale and reuse, at the modeled volume basis | $4,800,000 |
| Recovery subtotal | $12,300,000 | |
| Total economic impact | Wages subtotal plus recovery subtotal | $26.4M |
Illustrative model: 100MW facility. The hardware volume basis behind the recovery lines is still awaiting client confirmation, and until it is confirmed these two lines carry lower confidence than the wage lines above them. That is stated here rather than buried, and it is the same reason the sustainability headline is withheld.
$288K back to the operator, in the same report.
Community impact is not charity, and the report is not a corporate social responsibility page. Routing work locally shortens every move, which takes dock hours and transport legs off your operating budget. Those savings sit in the same document as the jobs, because they are produced by the same decision.
| Saving | Derivation | Annual value |
|---|---|---|
| Dock labor saved at the facility | $50 per hour across 480 hours | $24,000 |
| Facility to customer transport | $600 per move across 240 moves | $144,000 |
| Customer to ITAD transport | $500 per move across 240 moves | $120,000 |
| Total | $288,000 |
Illustrative model: 100MW facility.
How we count, in full.
One method, one source of numbers, applied everywhere: this website, any proposal, and the quarterly report itself. Operators are asked to prove local benefit, and the standard industry answer is a construction jobs figure that expires the day the building opens. This measures the part that does not expire.
Every figure currently published on this site is illustrative. NexWave has not yet delivered a report from a live engagement, and the label Illustrative model: 100MW facility. accompanies each figure, on every page, without exception.
The model class
An input-output model, the same class used in the economic impact studies commissioned by state and county development offices. It traces a dollar of spending through the local economy: the direct spend, the purchases that spend triggers from other local businesses, and the household spending of the workers who earn it. Naming the model class matters because it makes the numbers falsifiable.
What is counted. Three categories, and only three.
Direct wages. Compensation paid to people employed in the facility’s own market because the work stayed there: facility roles, provider side processing roles at secure storage and ITAD partners, logistics drivers, maintenance crews, technicians. Each role is counted at a stated headcount and a stated average compensation, and both halves are printed rather than collapsed into one payroll number. Wage lines are volume independent, which makes them the most defensible figures we publish, and it is why the wages subtotal of $14.1M is published in the headline set in its own right rather than disappearing into the economic impact total.
Recovered asset value. The resale and reuse value of decommissioned hardware recovered rather than destroyed or landfilled, credited at the point of recovery. Volume dependent, so its confidence is lower than the wage lines, and it is reported as its own subtotal rather than blended silently into wages.
Operator cost reduction. Operating expense the routing decision removes from the operator’s own budget: dock labor hours no longer spent staging assets for long haul pickup, and transport legs shortened or removed because the downstream facility is local. Reported at stated rates against stated move counts.
What is not counted, and why
No carbon headline. The volume basis behind it is not yet confirmed, two different bases appear in the source material, and a sustainability number that moves when you ask about it is worse than no number. It returns when the basis is settled, not before.
No construction employment, no induced property tax, no speculative multiplier beyond the model class named above, and nothing an operator has not actually routed. A figure that cannot be sourced in a public hearing is worse than no figure at all, which is the entire reason this section exists.
Source status, and correction
Every factor carries its provenance: publicly corroborated, client supplied, or NexWave provided and not yet confirmed in writing by the operator. When a factor changes, the report is reissued with the change noted rather than quietly restated, and the quarterly figures replace this model with measured actuals from your own routed work orders the moment there are any.
Get the version with your numbers in it.
An impact assessment scopes the model to your facility, your outbound volume and the providers available in your corridor. It comes back with the methodology attached and the open assumptions marked, exactly like the sample above.