Skip to content

What Freemium means...

November 7, 2025

So, I’ve been pushing for a freemium version for a while, but we had some concerns abut letting folks have scope builder for free, when that is the feature that they can best get their heads around. If they get that for nothing, what will they upgrade for? Will people use it more if they’re paying for it, or if they’re not? Who’s going to provide customer support to non-paying users, who may be less technically savvy one-building owners and/or co-ops?

Well, we girded ourselves and crossed the line last week, if ever so quietly! Here’s what I think we will get out of it:

  1. We’ll be able to get Scope Builder to a self-serve point for UX. Because we will have to. We all know it’s not there yet, and we now have a good reason to make this happen.
  2. We’ll learn what actual users value, especially once we get user observability tools like Posthog up and running. This is critical to getting our GTM right.
  3. Opportunity to be the default, even for buildings not subject to LL97. Accelerator is only a piece of the NYC market. Small multifamily is too small for consultants and too big for single-family tools. We’ll see if there’s any organic opportunity there.

So to hit again on the them of knowing our users – Freemium should be a huge help in that!

  • Unique Buildings:
  • Annual Run Rate: $1.51M
  • Monthly net burn (3-month avg, accrual basis): -$56,482 (-16.53% MoM)
  • Year-to-last-month net burn (cash basis): -$61,814 (+4% MoM)
  • 2025 Transaction fees to date: $63,403 (down $1,302 WoW after voiding a BES project that was not completed)
  • Outstanding invoices as of today: $303,391 (+40,772 WoW or +15.53% WoW)
  • Jon joined the team! (JB)
  • Zohran will be the next NYC mayor! (JB)
  • Getting freemium out so quickly thanks to some great teamwork! (JB) (+1 FH)
  • New expertise joining the team is triggering great conversations and ideas about where to take our platform. (FH)
  • Got some interresting insights from NYC government folks on how we could go deeper on citywide analysis to better support our NYC accelerator work next year (MZ)

Any missing highlights? Please share in Slack comments.

Looking out for icebergs: What are the risks on the horizon that we’re watching for and navigating around?

  • Improving clarity around our roadmap and prioritization process–I really want/need to put more time into this.
  • We may have won some minds, and we’re winning some wallets, but will we win their fingers? Which users will actually use our software instead of just looking for the outputs and expecting consultant-style service?
  • What is our moat in a world and industry where data wants to be free, especially when some of our largest customers are city and state agencies?
  • Politics Local is looking great! But national is really scary.
  • Budget and cash management - Going into year end and 2026, spend across categories will be analyzed more closely so we can budget efficiently. Overall, our spending is consistent YoY, just distributed differently. But, we also want to automate what we can so we can focus on other things. A little up front work and feedback from the teams will facilitate this moving forward.
  • Onboarding - also okay but there are still a couple of kinks to work out to make sure all hires (contractors and permanent employees)are aware of what is expected of them during the onboarding and their time with the company. Extending 15 minute onboarding calls to all should help along with the checklist for everyone and not just FTE and PTE. I will also need to be clear on what the expectations and timelines are for new hires sooner.
  • Baton passing: we are purposefully unscrewing the three legs of our platform stool (the BKB, Calc Service, Momentum), turning them into as many batons with which we can move faster as separate pieces, and possibly into separate products. Whether between people or between systems, baton passing is hard. We need to build the structure to make it work.
  • Getting ready for more traffic/scrutiny/requirements: NYCA is triggering a list of new infrastructure requirements: higher traffic, system resiliency, additional scrutiny on the security of our systems.

Carry-over:

  • Execution We are the dog that caught the car with NYCA and other stuff brewing. Stakes of everything we do will be increasingly high. So many eyes will be on us. How do we best expand the team?
  • Continuing to stay ahead of the curve that is turning into a hockey stick* How much of scope builder will be able to be recreated by an AI native start up in the mid term? What are we doing to build the flywheel so that our customers experience every project making the next one easier and we deepen our moat?
  • Process orchestration What tasks should be done by AI, what tasks should be done by AI + humans and what tasks should be done by humans? I don’t have as much of a handle on this for our development work… but this framework has gotten me thinking about how Momentum fits into the wider industry. Where and how can we disrupt things? And where and how can we be disrupted?
  • Mamdani!!! Wants to do something biggish and boldish with building decarb… NYC bulk buying window heat pumps has been floated. With a new wave of people in city government… how do we stay relevant and also exert our influence to set up any city scale program for success?
  • Product development process for NYCA, ConEd Recompete and HPD Don’t want to count the chicks before they’re hatched, but they are SOOOO close to hatching
  • Getting Marc a product he can sell We need Marc to be confident that we can make things he can sell, and I think a big contributor to that is taming our sprint / release practices. I think we’re making progress there. What do the rest of y’all think?
  • Team dynamics Maybe it’s because we’ve been doing a lot of 360s recently, but I feel like there is a lot of communication going on – another positive trend! Let’s no one disappear into any caves!
  • Planning for growth on the team We’re welcoming 4!! new folks shortly – data engineer, devops, and two Laravel devs. Whoot!
  • Uptake of AI tools - I love AI. I’d like to see more of how folks are using them.
  • Cash. We have deployed about half our cash in hand and have 16 months of runway.
  • Meeting with Willdan to discuss the 2026 SOW 🤞 (JB)
  • Meeting with Related to discuss bidding out PTHP projects (JB)
  • Informal meetings with our contacts at HPD (400k/yr subscription starting in Jan) and KC3 (partner we are trying to grow into more of a power user) to better understand their 2026 priorities (MZ)
  • I will be systematically running Momentum scopes on representative building types in multiple cities outside of NYS in order to help our customer (CPC Climate Capital) better understand costs/benefits of decarb in different markets (MZ)
  • SSO
  • Team and program admin
  • More detail related to parameterizable measures: terminal units and separate utility rates for owners and tenants

Please note your reaction to this update in the Slack channel. It helps us to know what is resonating, what is unclear, etc. Thanks!

  • What are your highlights / low-lights?
  • Did we miss a highlight? Something else you want to react to?