Shaping Roles

In the last memo, I talked about the responsibilities and privileged that make up management ‘sticks’ that we get to group into bundles.

This week’s question is, so how do these sticks map to my specific role? Here’s how I’m thinking about it:

1. When we design a role, we have a combination of the sticks in mind. In fact, a “role” is just a label for the bundle.
2. At any given time, a person probably has their own idea of what the ideal bundle for the role is, and an idea of where they are against the ideal bundle.
3. We don’t explicitly track how their inhabiting of the role confirms or changes the initial bundle, or whether their gap assessment matches others’ gap assessment.

So, I made a widget just to play with, but maybe something like this could actually be useful?

Metrics

Traction

• Unique Buildings:
• Annual Run Rate:

Financials

• Monthly net burn (accrual basis):
• Year-to-last-month net burn (cash basis):
• 2025 Transaction fees to date:
• Outstanding invoices as of today:

Development

• Bug Count (P-0 and P-1): 1 (once the tickets that went out with Release 100 are closed)

Last Week’s Highs and Lows

• Release 100 went out! We’ll turn on the improvement to how users see team buildings and do some messaging around it this week. (JB)
• Marc shared some great news about upcoming contracts and revenue–big things ahead! (JB)
• Chuck and Naina’s 360s and the surrounding discussions helped clarify roles and responsibilities in the team. (FH)
• Mathieu De Gracia is joining us as a contractor to help with Laravel architecture assessment and guidance. (FH)
• While not officially under contract…NYC HPD let us know they want to move forward on contract negotiations for a 400k 2 year subscription starting in january. And CPC Climate Capital is moving forward with us on a strategic (10k) subscription to help them figure out (MZ)
• Thanks to Daniel stepping up, our partner E3 submitted an RFP to Con Ed to leverage BKB data in order to help Con Ed better predict which of their network locations are going to need to be further built out sooner to handle new building electrification demand. (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?

Jason’s List

Carryovers:

• We need to move faster, and I hope we can grow the team and integrate more people quickly and smoothly!
• We’ve increased our feature set quite a bit lately, and it’s going to continue growing for some time. How can we scale our our testing to keep pace?
• 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.

François’ List

(repeats with tweaks)

• 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?

• 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. Update - we’re getting new measures, progress on development handling, an updated address search, and a proof-of-concept linkback to Momentum from this work so far.

Bomee’s List

• Getting Marc a product he can sell Program-Projects for KC3/ConEd pilot - important to deliver for ConEd as success now will lead to more opportunities!

• Team dynamics Pushing for more frankness, always

• Political and economic uncertainty in the US, including NYC elections.

• 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?

• NYCA, ConEd Recompete and HPD – Waiting for contracts!

• Uptake of AI tools - are we doing what we need to so folks can go faster?

• Cash. We have a net burn that we need to minimize, even as we judiciously staff up.

• Over-all architecture What’s in the application, what are back-end services? How quickly should we start pursuing the Clean Architecture path?

• Marc’s List

• Execution, execution, execution The NYCA thing is huge. Once this is in however, there will be a lot of eyes on us (which is of course what we have wanted all along…)

On Deck for This Week

• Jeff’s 360 (JB)
• Reviewing budget and hiring needs with François (JB)
• Demo for a new group of ConEd contractors (JB)
• Patch(es) to 100 (BJ)
• Investor updates (this week and next)
• HPD negotiation - ongoing
• Folks taking time off - YAY!

• Here’s what’s on the Company Radar

Upcoming Release

Rel. 100.x:

• Bugs in or uncovered by the team-scoped buildings / dynamic collections work
• Livewire / load balancing issues

Rel. 101:

• Getting the projects feature ready for use by Willdan and KC3
• Fix EPA Portfolio Manager integration

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?