Vibemaxxed.

We exercised some new muscles and felt some burn. As detailed in the look back, the Momentum team doubled our output (by PR count as proxy) while doubling our issue burn-down rate. We might not be going straight down and yelling all the way yet, but it’s a great start! The flip side was an uptick in perceived chaos – which we’ll need to learn to wrangle with tools and process. As in exercise, we need to work through the discomfort, while focusing on technique and mechanics!

Metrics

No changes to report - new numbers for March next week

Development

• Bug Count (P-0 and P-1): just 3! Two are just waiting to be tested and closed, and the third is in progress

This Week’s Highs and Lows

• Ana has been doing a great job as tech lead! (JMB)
• The Momentum team has really taken to vibe-coding and working through a ton of tickets! (JMB)
• NYCA launch confirmed for 4/14
• 1 BKB + 4 calc service prod deployments this week: address matching, improved modeling of non-MF buildings, rebates, advanced search speed up, improved debugger. Naina landed 10 PRs in the past 3 days, and Mike already pushed code to prod. (FRH)
• The NYSERDA PM who was our original contact for the Building Data Platform is back in charge of the project. Kudos to Bomee for bringing him to realize they need pilots (and a map) to drive the car we’ve built for them. (FRH)
• Signed ConEd subcontract! Kudos to Jon for getting us through it! (BJ)
• Delivered IMT’s prototype for MD. (BJ)
• Clean bill for preliminary assessment for SOC1! Kudos to Erika and Reuben! Next up is the actual audit. (BJ)

Any missing highlights? Please share in Discord comments.

Crow’s Nest

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

Jason’s List

• Improving clarity around our roadmap and prioritization process–I’ve started to meet with a PM coach to help me. But I’m back in the cycle of dealing with near-term stuff, so it may be a while before I make a lot more progress on 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? Let’s see what happens when NYCA is launched.
• 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?
• Honing our delivery process AI is helping us write new code quickly, but we haven’t unblocked the whole flow. We need to automate more of the testing to keep quality and velocity up, while keeping in mind that we are humans who need rest. This week’s experiment with vibe coding shows potential with a lot of output, but also lots of issues fixing bugs and staying on top of testing.

François’ List

Repeats:

• To get ready for NYCA launch, we need to project ourselves to a near future were a lot of variables are multiplied by 10-100x. Max number of concurrent users. Size of database backups. Occurrences of Sentry issues. Probability of a malicious actor trying to make us look bad. Let’s be creatively paranoid and prepare the ship!
• We have a lot of “almost there” large features or complex clean-ups that need to land soon: EPA Portfolio Manager v2 (almost there), new BKB supporting buildings beyond Multi-Family (shipped!), Building Attribute Guesser for NYSERDA BDP (shipped!), improved tariff support, etc.

On Deck for Next Week

• Wrapping up lots of NYCA priorities (JMB)
• Continuing the AI journey! (BJ)
• Signing the HPD subcontract! (BJ)

Upcoming Releases

• So many things!
• Create projects directly from suggested scopes
• Updated condo/coop board member registration flow
• Role-specific data sharing consent page and welcome content for programs
• Boiler remaining useful life available
• Lots of bug fixes and small UX improvements that have been lingering
• New EPA Portfolio Manager back-end (currently in test in main and staging)

Please Leave Feedback

Please note your reaction to this update in the Discord 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?