//Parallel Works
Shop
← All work

// A national clean-energy nonprofit

Digital infrastructure for programs that fund the transition.

A national nonprofit running public incentive programs, served across multiple program builds on a shared platform.

11// Energy & public programs
Business challenge

A nonprofit running multiple public incentive programs needed each program online fast - without rebuilding the same site over and over.

Scope

Program websites, catalogs, form routing, event sites, ongoing support.

Capabilities involved

Web Design & Development, Accessibility, Integrations & Automation.

Generic incentive program catalog and eligibility experience
// Interface study — generic, unbranded representation

// 01 The problem

The problem.

Public incentive programs live and die by their websites: eligibility rules, product catalogs, application flows, dealer and purchaser paths. Each new program arrived with new rules and new data - but the same deadline pressure and the same accessibility obligations.

Building every program site from scratch would have made each one slower and more expensive than the last. The real product was never one site - it was the system that produces them.

// 02 The approach

The approach.

Build the pattern once, then carry it. A single reusable WordPress platform - theme, component library, data structures, and deployment checklist - that every program site is built on, so program two costs a fraction of program one.

// 03 Delivery

What was implemented.

  • A reusable WordPress + Elementor platform pattern: theme, component library, and page templates shared across every program site.
  • Incentive-program sites with structured product catalogs: listing pages, detail templates, filtering, and pagination.
  • Custom data structures for program listings - voucher amounts, equipment specs, program type - implemented as proper metadata fields so catalog content is searchable and filterable, not free text.
  • Multi-path form routing: purchaser, dealer, and general inquiry flows, each routed and acknowledged differently.
  • Program event sites spun up on the same system.
  • UAT cycles per phase with tracked QA spreadsheets, plus documented go-live plans for each program launch.
  • Change-order framework for net-new pages and features - scoped, estimated, and delivered without disturbing the live programs.

// 04 Working detail

Inside the build.

// catalog metadata - field group definition
{  "key": "group_program_listing",  "title": "Program Listing Details",  "fields": [    {"name": "voucher_amount", "type": "number", "required": true},    {"name": "program_type", "type": "select", "choices": ["point-of-sale", "voucher", "rebate"]},    {"name": "eligible_equipment", "type": "checkbox", "choices": ["class-a", "class-b", "class-c"]},    {"name": "spec_sheet", "type": "file"}  ]}

// 05 Results

Results.

Three program sites delivered from one reusable platform pattern.

More than 40 catalog entries moved into structured, filterable fields.

One launch checklist reused across every program release.

Client names stay off this site by design. The full story behind this work - who it's for, what it did - is shared on a call, under NDA.

// The full picture

The names come out on a call.

Every engagement above has a full case study behind it - the client, the constraints, the numbers. We share those live, under NDA.