# NexVerde Delivery Playbook

**How Match, Ready, and Deliver are executed**

NexVerde Energy Solutions LLC · Boston, Massachusetts  
Contact: hello@nexverde.com

This playbook is the operating document behind the capability statement. It describes who we serve, what we sell, and the numbered steps from intake through construction—with inputs, artifacts, roles, and handoffs at each stage.

---

## 1. Company and commercial model

### Who we are

NexVerde turns public clean energy funding into finished local projects. America committed historic money to clean energy; the money is not the problem—execution is. Small and mid-sized communities often lack the staff to find winnable programs, get application-ready, and run their own bid. NexVerde is that missing capacity.

### Who pays / who does not

| Party | Pays? | What they receive | What they give back |
|-------|-------|-------------------|---------------------|
| **Communities** (towns, school districts, public agencies) | **No** for Match and Ready | Ranked funding shortlist, readiness work, and a path to their own public bid | Profile data and project outcomes (applied / won / lost / why) |
| **Delivery partners** (EPC, solar, ESCO, contractors, engineers) | **Yes**, annual subscription | Early notice of public bids. Same public information, same time as everyone. No inside information and no advantage. | Build capacity by region; execution feedback |

Our incentive aligns with construction: some firms pay a subscription for early notice of public bids. They get no inside information and no advantage. We are not paid a percentage of the grant.

### Two sides of the same project

- **Demand side:** Public bodies that own buildings, carry energy bills, and qualify for funding but rarely have staff to claim it.
- **Build side:** Firms that engineer and construct—expensive for them to find funded, ready public work on their own.

NexVerde does the work in the middle that makes the project real.

---

## 2. Service catalog

| Service | What it is | Primary artifact |
|---------|------------|------------------|
| **Match** | Ranked, realistic list of programs the community can win—not a directory dump | Shortlist with award range, deadline, match requirement, recommended first target |
| **Ready** | Pre-deadline work that wins or loses applications | Readiness score, gap punch-list, data/baselines package, competitive application (or grant-writer inputs) |
| **Deliver** | After funding, the community runs its own public bid. NexVerde explains funder procurement steps and tracks milestones. | A fair, public bid. Once public, qualified firms are invited to compete. Milestone and funder-reporting log from award to construction. |

Every step runs on one **analytics engine**: utility data, load profiles, benchmarked baselines, and a savings, cost and emissions model a reviewer can check, before technology talk. That foundation makes the match sharper, readiness real, and delivery scope credible.

---

## 3. Project types the community's engineer defines

NexVerde does **not** self-perform construction, and does not write the scope or specifications. Naming the project type keeps the funding match and readiness path accurate so the community can define the work and run a fair bid.

| Category | Typical scopes |
|----------|----------------|
| **Generate** | Rooftop, ground-mount, and carport/parking canopy solar PV |
| **Store and harden** | Battery energy storage (BESS), solar-plus-storage, microgrids / resilience hubs |
| **Electrify and heat** | Air-source and ground-source/geothermal heat pumps, heat pump water heaters, HVAC modernization / RTU replacement |
| **Tighten and optimize** | Envelope/weatherization, LED with occupancy/daylighting controls, BAS / energy management, retro-commissioning |
| **Move** | Level 2 and DCFC EV charging; municipal and school fleet electrification (including bus depots) |
| **Public works** | Water/wastewater efficiency (pumps, aeration, VFDs), biogas/energy recovery, streetlight LED conversion |
| **Plan and prove** | ASHRAE Level I–III audits, benchmarking, load/feasibility studies, engineering design, utility interconnection studies |

---

## 4. Intake (before Match)

**Purpose:** Confirm the public body, build a usable funding profile, and place the community in the pipeline.

### Inputs

- Legal name of the public body and type (municipality, school district, authority/special district)
- Single point of contact (name, title, email, phone)
- Optional: existing energy plan, Green Community (or similar) designation, prior award letters

### Steps

1. **Confirm the public body** — Town, city, district, housing authority, transit agency, RPA, or other special district. Confirm who can authorize data sharing and applications.
2. **Collect the funding profile** — Building stock and use types; energy spend and utility accounts; region; income / environmental justice indicators; rural status; prior awards; designations (e.g., Massachusetts Green Community).
3. **Pull live program universe** — Federal (Grants.gov opportunities; USASpending awards by geography and CFDA/ALN for clean energy programs); state and utility (e.g., MA DOER Green Communities, MassCEC, utility incentive programs). Refresh from live sources—do not rely on a stale printed directory.
4. **Log pipeline status** — Assign **Early**, **In readiness**, or **Ready to bid** based on readiness and winnability signals. Update as Match and Ready progress.

### Artifacts out

- Intake record and confirmed POC
- Funding profile worksheet
- Pipeline entry (status + date)

### Roles

| Community | NexVerde | Delivery partner |
|-----------|----------|------------------|
| Names POC; shares buildings, bills, designations, prior awards | Builds profile; pulls programs; logs pipeline | Not involved yet |

### Handoff

When the funding profile is complete enough to score programs → **Match**.

---

## 5. Match — find the funding you can actually win

**Logic:** Eligibility is not competitiveness. Thousands may qualify; few are positioned to win. Matching well means reading written rules and practical ones.

### Inputs

- Completed funding profile from Intake
- Live program rules (eligibility, scoring preferences, set-asides, match, deadlines)
- Prior award history for the community and peer communities (where available)

### Steps

1. **Encode eligibility rules** — Map written criteria and practical constraints (match cash, designations, income thresholds, rural status, building types, school vs. municipal eligibility).
2. **Score competitiveness** — Rank programs by how competitive *this* community is on real eligibility and award fit—not only whether it qualifies, and not a historical win model. Factors include readiness signals, prior awards, designation status, and fit to funder priorities.
3. **Map economics and calendar** — For each viable program: award range, cost-share / match, open and close dates, and any required studies or plans before submission.
4. **Rank and recommend a first target** — Produce a short shortlist. Name one recommended first pursuit with rationale.
5. **Brief the community** — Walk through the shortlist so leadership can choose before committing staff time to Ready.

### Artifacts out

- Ranked program shortlist (typically a small set, not dozens)
- Per program: award range, deadline, match requirement, competitiveness rationale
- Recommended first target

### Roles

| Community | NexVerde | Delivery partner |
|-----------|----------|------------------|
| Confirms profile facts; chooses first target | Encodes rules, scores, ranks, recommends | No notice until the community's bid is public |

### Typical timeline

**Days**, once Intake is complete—driven by data refresh and scoring, not by a funder deadline yet.

### Handoff

Community selects a target program (or ordered set) → **Ready**.

---

## 6. Ready — get application-ready and competitive

**Logic:** Applications are won or lost before the deadline. The difference between funded and unfunded is often measured vs. unmeasured. Readiness makes that gap visible and closable.

### Five pillars (scored)

| Pillar | What “good” looks like |
|--------|------------------------|
| **Data** | Consolidated utility accounts; benchmarked buildings; current baseline |
| **Planning** | Adopted energy plan with prioritized, costed projects |
| **Capacity** | Staff or partner who can run the application and post-award work |
| **Governance** | Procurement and approvals that move on a funder’s timeline |
| **Engagement** | Real structure for community input where the funder requires it |

### Inputs

- Selected program(s) from Match
- Utility bills / interval or monthly data; building list; existing plans and policies
- Funder NOFO / scoring rubric

### Steps

1. **Score the five pillars** — Rate each pillar; compute an overall readiness score; classify pipeline status (**In readiness** until gaps close toward **Ready to bid**).
2. **Assemble [reviewer-grade numbers](index.html#numbers).** Consolidated utility accounts; twelve-month load profiles; benchmarked baseline; a savings, cost and emissions model a reviewer can check (energy, cost, emissions where required). See [how we build the numbers](index.html#numbers).
3. **Produce the punch-list** — Exact missing items (e.g., missing accounts, no adopted plan, procurement lag, no engagement record) with owners and due dates.
4. **Structure to the rubric** — Outline and draft the application point-by-point to the funder’s scoring criteria so it competes instead of stalling.
5. **Package for submission or handoff** — Either a submission-ready application under the community’s authority, or organized pieces for the community’s own grant writer.

### Artifacts out

- Readiness score and pillar breakdown
- Gap punch-list with owners/dates
- Data and baselines package
- Competitive application (or grant-writer package)

### Roles

| Community | NexVerde | Delivery partner |
|-----------|----------|------------------|
| Supplies data and authorizations; closes governance/engagement gaps; signs and submits | Assesses, models, drafts to rubric, tracks punch-list | May contribute technical narratives or cost opinions when invited; still not the commercial lead sale |

### Typical timeline

**Tied to the funder deadline.** Start as early as Match allows; punch-list work often dominates the calendar.

### Handoff

Award decision path: if funded (or clearly shovel-ready under a firm timeline) → **Deliver**. If not funded, capture outcome reasons → feed the data engine; optionally rematch.

---

## 7. Deliver — get it built

**Logic:** When a project is funded and ready to build, the community runs its own bid. NexVerde does not write the bid, scope, or specifications, does not score bids, and does not pick the contractor.

### Inputs

- Award (or firm pre-award path) and matched program record
- Readiness package and baselines
- Preferred engineering category (from scopes table)

### Steps

1. **Understand the project need** — Help the community see what the project needs (for example rooftop solar on three schools, heat pumps in the elementary, storage on the fire station) so their team or their engineer can define it. NexVerde does not write the scope or specifications.
2. **Explain the funder's procurement steps** — When the project is funded and ready to build, walk through the procurement steps the funder requires. The community runs its own bid.
3. **Invite firms after the bid is public** — Once the bid is public, let qualified firms know it is open. Same public information, same time as everyone. No inside information and no advantage.
4. **Track milestones and funder reporting** — Track milestones and funder reporting from award to construction.
5. **Capture outcomes** — Record who applied, who won, who lost, and why; update the community’s pipeline status and the engine’s outcome store.

### Artifacts out

- Notes on what the project needs, for the community's engineer to define
- Funder procurement-step checklist the community uses to run its own bid
- Notice that a public bid is open, sent only after it is public
- Milestone and funder-reporting log from award to construction
- Outcome record for the flywheel

### Roles

| Community | NexVerde | Delivery partner |
|-----------|----------|------------------|
| Owns the bid, procurement decisions, and contracts; site access | Explains funder procurement steps; after the bid is public, lets qualified firms know it is open; tracks milestones and funder reporting; captures outcomes | Sees the same public bid as everyone else; prices, designs, builds, commissions; reports execution feedback |

### Typical timeline

**Through construction**—months to multi-year depending on scope, interconnection, and procurement path.

### Handoff

Project in construction / complete → outcome closed in engine; optional O&M partner introduction if in scope.

---

## 8. Data engine underneath

Every match and gap comes from one engine at three scales.

| Layer | Question it answers | Primary sources |
|-------|---------------------|-----------------|
| **National** | How much federal funding is open, and how much is reaching the ground? | Grants.gov (opportunities); USASpending (awards); clean-energy program filters (e.g., energy CFDAs / ALNs) |
| **State** | Where to work first? | Awards per state vs. need; per-capita and gap rank |
| **Local** | What is the actual work? | Community–program matches, readiness, lead status; MA municipal layer from DOER / Grid-Ready–style data loaded in the Data Studio |

### Gap logic

For a place, measure:

- **Need** — energy burden, income, population (pressure under the community)
- **Captured** — federal clean energy dollars received per person

**High need + low captured**, inside the set of communities that qualify, is the gap. Sharpest form: **eligible for a program but never received it**. That list is where work should go—and it is evidence the problem is national, using public data.

### Flywheel (why it compounds)

1. Engagement captures outcomes (applied / won / lost / why).  
2. Outcomes build the win-probability record as they accumulate; today matching runs on eligibility and award data.  
3. Sharper matches are more useful to communities and more valuable to delivery firms.  
4. More of both → more outcome data.  

The moat is the structured record of what works—not the public list of programs.

---

## 9. Roles and handoffs (summary)

| Stage | Community | NexVerde | Delivery partner |
|-------|-----------|----------|------------------|
| Intake | POC, data, authorizations | Profile, program pull, pipeline | — |
| Match | Choose first target | Score, rank, shortlist | No notice until the bid is public |
| Ready | Close gaps; submit | Score pillars; data package; application | No project details before the bid is public |
| Deliver | Run the public bid and contract | Explain funder steps; invite firms only after the bid is public; track; outcomes | See the same public bid as everyone else; design and build |
| Post | Share results | Update engine | O&M / feedback |

**Pipeline statuses:** Early → In readiness → Ready to bid (then tracked through award and construction).

---

## 10. Typical timelines (at a glance)

| Stage | Typical duration | Clock owner |
|-------|------------------|-------------|
| Intake | 1–5 business days after first response | Community data speed |
| Match | Days after Intake | NexVerde scoring + live data |
| Ready | Weeks to months | **Funder deadline** |
| Deliver | Months to years | Procurement + construction + interconnection |

---

## 11. Programs frequently in the Massachusetts / federal set

Used in matching and in the Data Studio (illustrative, not exhaustive):

- **GCD / GCC** — Massachusetts Green Communities Designation / Competitive  
- **EECBG** — DOE Energy Efficiency and Conservation Block Grant  
- **RAS** — Renew America’s Schools  
- **ELECT** — IRA Elective Pay  
- **REAP** — USDA Rural Energy for America  
- **SFA** — EPA Solar for All  
- **CEC** — MassCEC (and related state/utility programs)

Federal opportunity and award layers refresh from public APIs; municipal detail (e.g., Grid-Ready town lists) is loaded as local data in the Studio.

---

## 12. Related documents

- [Capability Statement](capability-statement.md) — 1–2 page government-style overview  
- Site pages: `capability-statement.html`, `delivery-playbook.html` (print / Save as PDF)

---

*NexVerde Energy Solutions LLC · Boston, MA · © 2026 · Clean energy funding, delivered.*