Intersession
January 24, 2025 (Review of Week
4)
First of all, I’m really happy with the horizontal practices discussion last week – I think this is the kind of muscle memory that we need to build for the long term, and I’m really glad to be in the boat with all of you, who were so open and frank in discussion issues that could be difficult to tackle. Thanks!
I was also thinking: in some colleges, there’s a thing called January intersession (at MIT, it’s called the Independent Activity Period (IAP), and it’s thanks to IAP that we have Izzy!) where you get to do something a little out of the ordinary for the month. I sort of feel like we’re having a January intersession of sorts, where the regular work hasn’t yet kicked in for the year. Probably part of it (for me) is that we don’t have our 2025 Willdan contract or the NYSERDAta contract signed yet, and Marc and I, at least, are still working on RFP responses, which feels very “pre” or “inter.”
Anyway, thinking of January as an intersession, I’m wondering what we’re taking away into the “regular” year?
Metrics
- Unique Buildings: 5,942 (December, +52 MoM)
- Annual Run Rate: $1.28M (-$12K MoM after removing AEA from the books)
- Monthly net burn (accrual basis): $100,775 (3-month avg through Dec.)
- Year-to-Last Month net burn (cash basis): $120,533
- 2025 Transaction fees to date: $0
- Outstanding invoices as of today: $128,489 (no change WoW)
Last Week’s Highlights
- A really good horizontal practices meeting–lots of contributions from all (JB) +2 (BJ, FH)
- +1 on the horizontal practices meeting - appreciate the feedback and recommendations from everyone (EP)
- At the very end of the week, Marc and I got to look at the NYCA application text. It still has a ways to go and we’re definitely heads-down on it this week, but I’m excited that it’s getting close to submission time!
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
All the same from last week:
- I’m eager to see how the advanced planned for Generic Programs will impact the end result. I know it’s too soon to tell, but I’m hopeful.
- Which RFPs will come our way?
- When we will actually receive a 2025 contract from Willdan? It was postponed again this week–hopefully next week.
- What will learn from the upcoming conversations with Service Providers? Whatever it is, this will probably have a big impact on our revenue and roadmap.
- Figuring out a sustainable sprint planning routine that allows us to reliably ship on time and to know what will be in the release.
Erika’s List
- In the midst of fulfilling our reporting requirements and thinking about how to make pulling this information together easier and less one-off. It was already a goal for this quarter but going through the process now I am feeling how time consuming this can get the more investors or programs we participate in.
- On the same note, considering finances and wanting to make sure they are truly transparent and folks understand our position and why we may make the decisions we do.
- Also looking toward the quarterly goals and everyone participating in the exercise - our work plans mean something beyond ourselves and would like to see how they all come together.
Bomee’s List
- Mapping out Q1/H1 Momentum scope - I’ve been a bit of a bottleneck on this, but I’d like to get everyone on the same page soon!
- Burn rate - we’re at that time of year when we’re holding on for our first Willdan payment, so probably I feel it more acutely than in other times of the year, but curbing burn is important!
François’ List
- Repeats from previous weeks: RFPs uncertainty, batons passing post-360s, plans for AI
- Izzy’s internship is coming to an end very soon. She’s delivered a solid v0 of the AI building guesser in record time, and I’m looking forward to her final presentation! Risk we want to avoid: dropping that baton and letting the feature rot behind a feature flag. Izzy is working on documenting her work so that picking it up is easier: thank you!
- As we’re working to rotate the “first responder” responsibilities, I’m realizing the gaps we have in our logging / integration with Sentry. Momentum-calcs doesn’t have dedicated Sentry projects (and worse: the notebooks based code doesn’t use proper logging patterns), and our javascript code base Sentry monitoring is mostly unusable. This is fixable, but in the meantime it gets in the way of making it easy for anyone in the team to investigate production / staging issues.
On Deck for This Week
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 / lowlights?
- Did we miss a highlight? Something else you want to react to?