How do you handle the hardware/software complexity unique to climate tech products?
Climate tech products often span both physical and digital domains — sensors, grid-connected devices, EV infrastructure, or monitoring hardware that feeds into a software platform. This creates unique PM challenges: hardware has long lead times and high change costs, while software can iterate weekly. I bridge that gap by defining clear interface contracts between hardware and software teams early, sequencing features around physical constraints, and building a product roadmap that accounts for hardware revision cycles. I work closely with engineering and operations to ensure software features are designed around what the hardware can actually deliver, not an idealised spec.
How do you measure and communicate impact in a climate tech product?
Impact measurement is a strategic product asset in climate tech — it drives investor narrative, customer procurement decisions, and regulatory reporting. I work with teams to define a credible impact metric framework: selecting the right primary metric (tonnes CO2e avoided, kWh optimised, resource units saved), ensuring the measurement methodology is defensible against scrutiny, and building the data infrastructure to surface impact in the product itself. Impact dashboards built well become a retention and expansion lever — customers who can see and report on their outcomes renew and upsell. I help teams connect impact data to commercial outcomes so the mission and the business reinforce each other.
Can you help navigate regulatory frameworks in climate tech (NGER, ERF, safeguard mechanism)?
Yes. Regulatory compliance in climate tech is a product requirement, not just a legal obligation. I map applicable frameworks (Australia's NGER, ERF, Safeguard Mechanism, and relevant state-level schemes) into the product roadmap so compliance features are designed and shipped before they become blockers. For products operating in voluntary carbon markets or seeking ACCUs, I work with your legal and technical advisors to define the product data capture requirements that support audit trails and methodology compliance. The goal is to make compliance a competitive advantage — products that make regulatory reporting effortless win enterprise and government customers that competitors cannot serve.
What does a typical engagement look like for a climate tech startup at the growth stage?
Growth-stage climate tech companies often face the same challenge: they have proven the core technology but are struggling to scale the product and customer base without losing the mission-integrity that differentiated them. A typical engagement starts with a product audit — reviewing the current product against the ICP, identifying where the product is creating friction in the sales or retention cycle, and mapping the 90-day product investments with the highest commercial and impact leverage. I then embed as a fractional PM to execute the roadmap: running discovery, writing PRDs, facilitating sprints, and keeping the team aligned across the hardware, software, and go-to-market workstreams.