Momentum’s back half (providers, financing, tracking) is critical to build out, but the front half is still founder-powered. Today, trust, clarity, and decision framing are being supplied live by Marc. Until Discovery → Retrofit Planning pre-answers board questions, encodes uncertainty honestly, and constrains decisions in a repeatable way, the rest of the workflow won’t activate at scale. The near-term product opportunity is trust infrastructure upstream, not more downstream features.
Why public data is fine for planning, not bidding
Gap: UI shows outputs, not how to reason about them.
B. Killing bad ideas without killing momentum
Electric boilers, solar, “just switch to gas,” waivers
Gap: No in-product guardrails explaining why not.
C. Sequencing logic
“Are we kicking the can?”
“Why invest in an old boiler?”
“What comes first vs later?”
Gap: No default phase plan.
D. Policy confidence
No waivers, caps tighten, credits ≠ guarantees
Gap: UI avoids saying “no.”
Elaboration on this: Boards look for escape hatches (waivers, grandfathering, incentives-as-shields). You consistently apply a clear rule: there are no waivers, caps only tighten, and credits reduce cost—not legal obligation. Today, you deliver that truth; the UI avoids saying “no,” which creates false confidence and pulls founders into every conversation.
Product implication: Momentum must explicitly encode “no” as a constraint, not a warning. Separate expected outcomes from compliance certainty, add standardized policy reality checks, and replace waiver fantasies with viable substitutes. Tech builds trust by being immovable—clear refusals reduce human escalation and unlock scale.
Let tech be the bad cop; humans say “here’s how to proceed”
**Anchor sentence:
** Humans earn trust through judgment; Momentum must make judgment legible, constrained, and repeatable.
Daylight with NYCA
Based on me stumbling through… how do you get paid line of question from one Powers Street
TL;DR for Owners (final, precise version)
For buildings that don’t already have a design engineer on retainer, Momentum offers an optional way to structure a contractor design-bid process.
What’s free (covered by NYC / Retrofit Accelerator)#
Paid for by the City of New York:
Access to the Momentum platform
Preliminary Local Law 97 planning and scenario analysis
Bid tracking and comparison — including bring-your-own engineer / bring-your-own RFP
👉 You can use Momentum purely as a neutral planning and coordination tool, with no fees, even through bidding.
What’s optional and paid
If you choose to use Momentum’s Auto-RFP and Design Assist features:
Momentum will:
Translate planning outputs into a standardized, performance-based RFP
Define constraints and assumptions so contractors design to the same problem
Reduce ambiguity and scope drift during bidding
Make bids meaningfully comparable without hiring an engineer upfront
Fee structure (fully disclosed upfront):
A 2–5% transaction fee on construction work that is procured using Momentum’s Auto-RFP / Design Assist workflow
The fee applies only if you select a contractor through that workflow
No fee if you:
Bring your own engineer and RFP
Use Momentum only for planning, connection, or tracking
You can use Momentum for planning, contractor connections, and bid tracking at no cost. If you want us to generate and manage the RFP itself, that’s optional and comes with a disclosed 2–5% transaction fee.
RFPs and Liability
Based on me stumbling through… how do you get paid line of question from one Powers Street
Momentum Pathways → Competitive Procurement
Momentum is designed to help building owners make defensible, low-regret decisions under Local Law 97 and then translate those decisions into procurement structuring for competitive bidding, without Cadence OneFive assuming professional design, construction, or performance liability.
Momentum operates in two distinct modes. Pathway Selection provides decision support to help owners choose which compliance direction is worth investigating next, based on tradeoffs, risk, and uncertainty. Selecting a pathway authorizes investigation—not construction or design approval. Procurement Structuring for Competitive Bidding then translates the owner-selected pathway into structured RFPs that define performance targets, constraints, and comparison frameworks, enabling licensed professionals to propose and deliver solutions while retaining responsibility for final design, means and methods, and code compliance. Momentum structures decisions and markets; it does not act as engineer, architect, or contractor of record.
To mitigate construction liability, all Momentum-generated RFPs explicitly position Cadence OneFive as a procurement and decision-support platform, not a professional services provider, and place responsibility for system design, sizing, and compliance with bidders and owners. To mitigate performance and emissions-expectation risk, Momentum presents projected savings and emissions impacts as ranges under stated assumptions, not single-point predictions or guarantees. Realized carbon outcomes depend on factors outside the platform’s control, including system selection, commissioning quality, weather, resident behavior, controls, and ongoing operations. By surfacing uncertainty, sensitivity, and downside risk directly in the scope builder, Momentum ensures owners make pathway decisions with variability visible rather than implied certainty.
**How Marc should talk about Momentum externally
** Externally, Momentum should be described as decision and procurement infrastructure, not as a source of answers or guarantees. The goal is to help boards understand tradeoffs and choose which uncertainty to resolve next, while making clear that final outcomes depend on execution and operations. Marc should consistently frame Momentum as reducing decision risk up front and structuring the market responsibly downstream.
Use phrases like:
“Momentum helps boards compare compliance pathways and understand tradeoffs.”
“This shows a range of possible outcomes under stated assumptions.”
“Selecting a pathway authorizes further investigation, not construction.”
“Momentum structures a competitive bidding process; licensed professionals and operations determine results.”
“The value is seeing downside risk before committing capital.” Avoid phrases like:
“This will make you compliant.”
“This is the right scope or solution.”
“This upgrade will reduce emissions by X%.”
“Design assist” or “pre-design.”
“Guaranteed savings” or “proven outcome.”
**External litmus test:
** If a board member could reasonably repeat Marc’s words as a promise of compliance, cost savings, or emissions reduction, the phrasing is wrong.
**Internal mantra:
** Momentum models possibilities and structures procurement; the market builds, and operations determine results.
Strategy Notebook
Running List of Pipeline Observations
Created: February 9, 2026
Executive takeaway #
Momentum’s back half (providers, financing, tracking) is critical to build out, but the front half is still founder-powered. Today, trust, clarity, and decision framing are being supplied live by Marc. Until Discovery → Retrofit Planning pre-answers board questions, encodes uncertainty honestly, and constrains decisions in a repeatable way, the rest of the workflow won’t activate at scale. The near-term product opportunity is trust infrastructure upstream, not more downstream features.
1. What is still founder-only #
Across all transcripts, the same gaps recur:
A. Interpreting the numbers
Why ranges > point estimates
Why steam savings can’t be modeled precisely
Why public data is fine for planning, not bidding Gap: UI shows outputs, not how to reason about them. B. Killing bad ideas without killing momentum
Electric boilers, solar, “just switch to gas,” waivers Gap: No in-product guardrails explaining why not. C. Sequencing logic
“Are we kicking the can?”
“Why invest in an old boiler?”
“What comes first vs later?” Gap: No default phase plan. D. Policy confidence
No waivers, caps tighten, credits ≠ guarantees Gap: UI avoids saying “no.” Elaboration on this: Boards look for escape hatches (waivers, grandfathering, incentives-as-shields). You consistently apply a clear rule: there are no waivers, caps only tighten, and credits reduce cost—not legal obligation. Today, you deliver that truth; the UI avoids saying “no,” which creates false confidence and pulls founders into every conversation.
Product implication: Momentum must explicitly encode “no” as a constraint, not a warning. Separate expected outcomes from compliance certainty, add standardized policy reality checks, and replace waiver fantasies with viable substitutes. Tech builds trust by being immovable—clear refusals reduce human escalation and unlock scale.
2. How the UI must change (near-term) #
The UI should stop trying to impress and start trying to constrain.
**A. Trust primitives (front and center) ** Every building shows:
💬 1 comment
**C. Force tradeoffs ** Explicitly surface:
3. What a non-technical ambassador can run now #
Not the full vision — a safe subset.
They should be able to:
Answer FAQs using invariant, prewritten explanations
End with a clear next step (data request, bids, or deeper review) They should not be asked to:
Defend modeling nuance
Speculate on policy or tech futures Escalation should happen only when flagged Low Confidence or Fuel switch / Electrify, not because the UI failed.
4. Questions Momentum must answer before a human #
If these aren’t answered, humans get pulled in early:
5. Reframing Momentum’s rollout #
The full-cycle vision is right long-term. Market reality: you cannot “connect to solution providers” until the decision feels safe.
Today:
The rule engine you already run (condensed) #
Marc’s “judgment” is actually a consistent rule set:
What this means for Product #
Marc isn’t a charismatic explainer — he’s a rules engine with humane defaults.
To scale that:
Daylight with NYCA
Based on me stumbling through… how do you get paid line of question from one Powers Street
TL;DR for Owners (final, precise version)
For buildings that don’t already have a design engineer on retainer, Momentum offers an optional way to structure a contractor design-bid process.
What’s free (covered by NYC / Retrofit Accelerator) #
Paid for by the City of New York:
What’s optional and paid
If you choose to use Momentum’s Auto-RFP and Design Assist features:
Momentum will:
Translate planning outputs into a standardized, performance-based RFP
Define constraints and assumptions so contractors design to the same problem
Reduce ambiguity and scope drift during bidding
Make bids meaningfully comparable without hiring an engineer upfront Fee structure (fully disclosed upfront):
A 2–5% transaction fee on construction work that is procured using Momentum’s Auto-RFP / Design Assist workflow
The fee applies only if you select a contractor through that workflow
No fee if you:
How to think about the choice #
Bottom line #
Planning, connections, and tracking are city-funded. Auto-RFP and Design Assist are optional value-add services, paid only if used.
We help you decide for free. If you want us to help structure and run procurement, we’re transparent about how we’re paid.
Ultra-short version (for live calls) #
You can use Momentum for planning, contractor connections, and bid tracking at no cost. If you want us to generate and manage the RFP itself, that’s optional and comes with a disclosed 2–5% transaction fee.
RFPs and Liability
Based on me stumbling through… how do you get paid line of question from one Powers Street
Momentum Pathways → Competitive Procurement
Momentum is designed to help building owners make defensible, low-regret decisions under Local Law 97 and then translate those decisions into procurement structuring for competitive bidding, without Cadence OneFive assuming professional design, construction, or performance liability.
Momentum operates in two distinct modes. Pathway Selection provides decision support to help owners choose which compliance direction is worth investigating next, based on tradeoffs, risk, and uncertainty. Selecting a pathway authorizes investigation—not construction or design approval. Procurement Structuring for Competitive Bidding then translates the owner-selected pathway into structured RFPs that define performance targets, constraints, and comparison frameworks, enabling licensed professionals to propose and deliver solutions while retaining responsibility for final design, means and methods, and code compliance. Momentum structures decisions and markets; it does not act as engineer, architect, or contractor of record.
To mitigate construction liability, all Momentum-generated RFPs explicitly position Cadence OneFive as a procurement and decision-support platform, not a professional services provider, and place responsibility for system design, sizing, and compliance with bidders and owners. To mitigate performance and emissions-expectation risk, Momentum presents projected savings and emissions impacts as ranges under stated assumptions, not single-point predictions or guarantees. Realized carbon outcomes depend on factors outside the platform’s control, including system selection, commissioning quality, weather, resident behavior, controls, and ongoing operations. By surfacing uncertainty, sensitivity, and downside risk directly in the scope builder, Momentum ensures owners make pathway decisions with variability visible rather than implied certainty.
**How Marc should talk about Momentum externally ** Externally, Momentum should be described as decision and procurement infrastructure, not as a source of answers or guarantees. The goal is to help boards understand tradeoffs and choose which uncertainty to resolve next, while making clear that final outcomes depend on execution and operations. Marc should consistently frame Momentum as reducing decision risk up front and structuring the market responsibly downstream.
Use phrases like:
“Momentum helps boards compare compliance pathways and understand tradeoffs.”
“This shows a range of possible outcomes under stated assumptions.”
“Selecting a pathway authorizes further investigation, not construction.”
“Momentum structures a competitive bidding process; licensed professionals and operations determine results.”
“The value is seeing downside risk before committing capital.”
Avoid phrases like:
“This will make you compliant.”
“This is the right scope or solution.”
“This upgrade will reduce emissions by X%.”
“Design assist” or “pre-design.”
“Guaranteed savings” or “proven outcome.” **External litmus test: ** If a board member could reasonably repeat Marc’s words as a promise of compliance, cost savings, or emissions reduction, the phrasing is wrong.
**Internal mantra: ** Momentum models possibilities and structures procurement; the market builds, and operations determine results.