Getting to November

This November is a big deal for us – we will need to turn the lights on for NYC Accelerator at a time when a good portion of NYC will be rushing to beat the end-of-year deadline for filings. Helping those folks will be mission #1 for NYCA, and that means Momentum has to be up and running for them.

The deliverables list for NYCA is long, but the stuff that has to be working to launch is really very concentrated:

• Willdan/KC3 need to be able to onboard new Teams/Users, and
• Momentum needs to be able to talk to Salesforce

A pre-requisite for all this is getting Team/User registration working – which is what I have been chipping away at for the past month (between other things for Marc). Once folks can register in Momentum, we’ll need to work out the specific workflow for NYCA, which will involve Willdan/KC3 checking some credentials before approving them.

Next up after that needs to include:

• Figuring out how we will hook into Salesforce
• How the self-registration meshes with the Program Admin’s superpowers – so the Program Admin dashboard, among other things.

As usual, there is a fog of not-yet-decided around exactly how these features need to work – largely because no one has thought it through all the way (and we can’t do it without Willdan, who hasn’t even hired yet). So we will have to be comfortable making some decisions that we think are future-proof, and accepting that some number of them will need to be revisited when we have more information!

I feel like folks need to take a breather, me included, so that we can all get really excited about this. It’s a lot of work, but it’s also a really big win when we deliver!

Metrics

Traction

• Unique Buildings: 6,726 (June, +77 MoM)
• Annual Run Rate: $1.499M (June, +2.46% MoM)

Financials

• Monthly net burn (accrual basis): $58,488 (3-month avg, +9.89% MoM)
• Year-to-last-month net burn (cash basis): $72,170 (-4.05% MoM)
• 2025 Transaction fees to date: $22,271 (including $6,418 in new contractor transaction fees)
• Outstanding invoices as of today: $153,028 (-$76,915 WoW, -33.45% WoW)

Development

• Bug Count (P-0 and P-1): 8, but all of them will be fixed with this week’s release

Last Week’s Highs and Lows

• Unexplained service slowdowns and mayfly (ephemeral environments for rapid testing) absorbed a bunch of time and/or mental weight from the team. (FH)
• Lots of testing last week, which means we’re on track for a big release this week with a bunch of new features and fixes. (JB)
• I really appreciated the dev folks working in the open, giving regular updates of what they were working on, including short recordings of progress throughout the week. I think it really helped with baton passing 🏃 (JB)
• Even as we double down locally in NYC, had a couple of green shoots nationally: CPC Climate Capital wants to engage us through a small (10k) subscription to help them come up with a coherent strategy for targeting buildings nationally. This will help them fundraise private capital even if GGRF is frozen. And also had an interesting discussion with Lloyd Kass of Franklin Energy (a Willdan competitor) about how we might work together in other locations (MZ)
• Related is happy as a customer, for now… (MZ)

Any missing highlights? Please share in Slack comments.

Crow’s Nest

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

François’ List

• Growing the team: the NYCA news further raises the priority of onboarding the right talent to help us deliver quickly from data processing to front-end. We’re making progress identifying places where we need the most help, Reuben is starting to circulate possible interview focus and candidates - but are we ready to welcome new folks and help them be productive?

(repeats with tweaks)

• One-to-many: the L+M project is a one-off analysis under a tight deadline. If we play it well, we will have built a lot of re-usable functionality that should benefit the rest of our customers too (measures, address matching inclusive of development, reporting)… but if we don’t, we’ll have accumulated more throwaway code dedicated to a single-use case.

Jason’s List

Carryovers, with tweaks:

• AI Document Scraping How will scraping project scopes and contractor bids, which will be more difficult, go? And how quickly can we get this figured out and incorporated into the code? This is one of the areas where we can provide some real magic for users.
• Local politics There’s still a lot that could happen between now and the general election in November. NYC DOB is worried about the optics of this first year of LL97 filing and wants to make sure it goes smoothly and offers a positive takeaway.
• NYC Accelerator news is in! 🎉 We have a lot of build for this–and I realize more with each passing day–so I’m hoping our team continues to incorporate the new tools and processes, and remains vocal and open about what they are working on and what’s not working for them.
• ConEd Recompete Still waiting for news
• Portfolio/program reporting Users want the ability to look at groups of buildings in our software, whether it’s looking in their own collections for buildings that meet certain criteria or looking at trends across projects in a program. We haven’t done anything in this vein yet, but we’ll need to start. L+M, CFHF, FirstService, and more want and expect this set of features from us. And we’re starting to learn what jobs they are looking to do with the spreadsheets we’re providing so far.

Erika’s List

(some carryover, some updates)

• Growing the team This requires conversation amongst the team leads post mid-year budget review, but also want to think ahead as far as resources and needs that could support a search such as salary comps and regional employment considerations and guidelines. This would also require getting the documentation on worldwide work into the handbook, along with other policies, asap so everyone is aware of how we should proceed with hiring, onboarding and integration moving forward.

• Hiring Process Along with growing the team, thinking about how we interview and how we could screen for things that are important to a new hire being successful in the company. Also thinking about how we will manage onboarding new folks, logistically. One hire is a lot of work, what about when there are multiple hires within a short time frame?

Bomee’s List

• Planning for growth on the team We’re going to need more hands on deck soon. What will it take for them to land on their feet and start running?
• Over-all architecture What’s in the application, what are back-end services?
• Getting Marc a product he can sell Program-Projects for KC3/ConEd pilot
• Team dynamics We’re still gelling, and we’re having more of the the conversations we need to have. Really thought last week’s staff meeting and brown-bag discussions were good for us.
• Cash. We have a net burn that we need to minimize. If we win these RFPs, we can make strategic investments!
• NYCA and ConEd Recompete – Waiting for contracts!
• Political and economic uncertainty in the US, including NYC elections.

Marc’s List

• Execution! It is definitely go time!
• Work-Life Balance But we need to not get burned out!

On Deck for This Week

• Two demos this week: one of the “core” Momentum features (buidings and advanced search) for a new group of ConEd participating contractors, and showing off the project feature for our Willdan and ConEd clients on Friday. (JB)

• Release 99! (JB)

• Working on a 2H 2025 look-ahead from a FinOps perspective - including hiring plan (EP)

• Working on the rollover timeline to the new healthcare platform for the team (EP)

• Onboarding Daniel Gonzalez (MZ)

• Picking up the pace on my manual decarb report generation for customers to get to 200+ by mid August. Ultimate goal is to build a data set for automation. (MZ)

• Here’s what’s on the Company Radar

Upcoming Release

• Projects MVP - or least something that’s demo-able and mostly there
• Showing users all of the buildings and collections from their team–this will be a big chnage in their UX, but I think a really important and welcome one
• A new version of the BKB, which improves how we handle buildings in developments

Please Leave Feedback

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?