How NexVerde delivers
Step-by-step operating document for Match, Ready, and Deliver—inputs, artifacts, roles, and handoffs from intake through construction. NexVerde Energy Solutions LLC · Boston, MA · hello@nexverde.com
1Company 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 | No for Match and Ready | Ranked shortlist, readiness work, and a path to their own public bid | Profile data and outcomes (applied / won / lost / why) |
| Delivery partners | 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.
Demand side: Public bodies that own buildings 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 alone. NexVerde does the work in the middle.
2Service catalog
| Service | What it is | Primary artifact |
|---|---|---|
| Match | Ranked, realistic list of programs the community can win | Shortlist with award range, deadline, match, recommended first target |
| Ready | Pre-deadline work that wins or loses applications | Readiness score, punch-list, data package, competitive application |
| Deliver | After funding, the community runs its own public bid | A fair, public bid. Once public, qualified firms are invited to compete. Milestone and funder-reporting log. |
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.
3Project 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, carport/parking canopy solar PV |
| Store and harden | BESS, solar-plus-storage, microgrids / resilience hubs |
| Electrify and heat | Air-source and geothermal heat pumps, HPWH, HVAC modernization |
| Tighten and optimize | Envelope, LED/controls, BAS, retro-commissioning |
| Move | Level 2 and DCFC; municipal and school fleet electrification |
| Public works | Water/wastewater efficiency, biogas recovery, streetlight LED |
| Plan and prove | ASHRAE I–III audits, benchmarking, load/feasibility, interconnection |
4Intake (before Match)
Purpose: Confirm the public body, build a usable funding profile, and place the community in the pipeline.
Inputs
- Legal name and type (municipality, school district, authority/special district)
- Single point of contact
- Optional: energy plan, Green Community designation, prior award letters
Steps
- Confirm the public body — Town, city, district, housing authority, transit, RPA, or special district. Confirm who can authorize data sharing and applications.
- Collect the funding profile — Building stock; energy spend and utility accounts; region; income / EJ indicators; rural status; prior awards; designations (e.g., MA Green Community).
- Pull live program universe — Federal (Grants.gov, USASpending); state and utility (e.g., DOER Green Communities, MassCEC, utility incentives). Refresh from live sources.
- Log pipeline status — Early, In readiness, or Ready to bid. Update as Match and Ready progress.
| Community | NexVerde | Delivery partner |
|---|---|---|
| Names POC; shares buildings, bills, designations, prior awards | Builds profile; pulls programs; logs pipeline | Not involved yet |
Handoff: Funding profile complete enough to score programs → Match
5Match — 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 peers (where available)
Steps
- Encode eligibility rules — Written criteria and practical constraints (match cash, designations, income thresholds, rural status, building types).
- Score competitiveness — Rank by how competitive this community is on real eligibility and award fit—not only whether it qualifies, and not a historical win model.
- Map economics and calendar — Award range, cost-share, open/close dates, required studies or plans.
- Rank and recommend a first target — Short shortlist plus one recommended first pursuit with rationale.
- Brief the community — Leadership chooses before committing staff time to Ready.
Timeline: Days once Intake is complete. Handoff: Community selects target → Ready
6Ready — 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.
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 |
Steps
- Score the five pillars — Overall readiness score; update pipeline (In readiness → Ready to bid as gaps close).
- Assemble reviewer-grade numbers. Consolidated accounts; 12-month load profiles; benchmarked baseline; a savings, cost and emissions model a reviewer can check. See how we build the numbers
- Produce the punch-list — Exact missing items with owners and due dates.
- Structure to the rubric — Outline and draft point-by-point to the funder’s scoring criteria.
- Package for submission or handoff — Submission-ready application under the community’s authority, or pieces for their grant writer.
Timeline: Tied to the funder deadline. Handoff: If funded (or firm pre-award path) → Deliver. If not, capture outcome reasons → engine; optionally rematch.
7Deliver — 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.
Steps
- Understand the project need — Help the community see what the project needs so their team or their engineer can define it. NexVerde does not write the scope or specifications.
- Explain the funder's procurement steps — When the project is funded and ready to build, walk through the steps the funder requires. The community runs its own bid.
- 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.
- Track milestones and funder reporting — From award to construction.
- Capture outcomes — Applied / won / lost / why; update pipeline and the engine.
| Community | NexVerde | Delivery partner |
|---|---|---|
| Owns the bid, procurement, and contracts; site access | Explains funder steps; after the bid is public, lets qualified firms know it is open; tracks milestones and reporting | Sees the same public bid as everyone else; prices, designs, builds |
Timeline: Through construction—months to multi-year. Handoff: Construction / complete → outcome closed; optional O&M introduction.
8Data engine underneath
| Layer | Question | Primary sources |
|---|---|---|
| National | How much funding is open, and how much reaches the ground? | Grants.gov; USASpending; clean-energy CFDA/ALN filters |
| 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 DOER / Grid-Ready–style data in the Studio |
Gap logic
Measure Need (energy burden, income, population) and Captured (federal clean energy dollars per person). High need + low captured, inside communities that qualify, is the gap. Sharpest form: eligible for a program but never received it.
Flywheel
- Engagement captures outcomes (applied / won / lost / why).
- Outcomes build the win-probability record as they accumulate; today matching runs on eligibility and award data.
- Sharper matches are more useful to communities and more valuable to delivery firms.
- More of both → more outcome data. The moat is the structured record of what works—not the public program list.
9Roles 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 | 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).
10Typical timelines
| 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 |
11Programs frequently in the set
- 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 layers refresh from public APIs; municipal detail (e.g., Grid-Ready town lists) loads as local data in the Data Studio.