Weekly Update
January 31, 2025 (Review of Week
5)
This week, we’re just sharing the facts!
Metrics
- Unique Buildings: 5,998 (January, +56 MoM)
- Annual Run Rate: $1.28M
- Monthly net burn (accrual basis): $111,027 (3-month avg through January)
- Year-to-Last Month net burn (cash basis): $178,403 (January only, net burn increase due to IRA contributions)
- 2025 Transaction fees to date: $0
- Outstanding invoices as of today: $186,822 (+$58,333 and 45.4% WoW, $168,688 of outstanding invoices belong to Willdan)
Last Week’s Highlights
- Release 89 🚢 on time! (JB)
- Isamar’s blitz internship showed that we can have folks join and contribute meaningfully over a short period of time, and gets us closer to having the AI box checked. (FH)
- We have realistic, fresh, anonymized production data in staging, so that we can better put ourselves in the shoes of our users. (FH)
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:
- Which RFPs will come our way? When will CPC GGRF call us? And I’m not loving NYC delaying the Accelerator RFP deadline again 😠
- When we will actually receive a 2025 contract from Willdan? It was postponed again this week–hopefully next 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.
- 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–and move faster.
François’ List
- The
team_building duplicate saga got us to take a cold hard look at what we have in our data attic… The bad news is that we just found a number of time-bombs, the good news is that we found them before they exploded on us too painfully. Let’s merge those rows and columns before we forget how they work, and harden our DB constraints to detect these issues faster!
- User Pain Points - Similarly, now that we have realistic anonymized data from our users, we’re detecting issues that would have been hard to spot in the old staging DB. This is good, but again there are some bad surprises. I knew the home page was slow for users with large collections, but now that I can see it, it stings.
- AI Desk Audit - I’m very happy with Isamar’s progress over the one month she spent with us, but I’m concerned about the inevitable code rot that will occur if we don’t finalize it to be ready for our users. Can we spare some time on this even though it’s not mission critical for the RFPs we’re focusing on?
- Test Automation Progress We can’t move fast (or onboard new folks efficiently) without safety nets that will help us rebound quickly when we fail. With all the other work on our plate, I’m worried the testing automation will be pushed back indefinitely. Can we kick-start it to give Jeff the foundation to build on when he’s in between release testing surges?
Erika’s List
Similar to last week:
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?
Jeremy (Coder) Feb 4th at 10:24 AM
Unique Buildings: 5,998
Let’s see if this number is about to go down…
Maybe we can add a ticket for next sprint to build the initial framework for automated end-to-end testing (browser testing). The framework that Chuck posted looks like it’ll do the job!
Jeff (QA) Feb 4th at 10:32 AM
To
@Jason (Product)
- ” upcoming conversations with Service Providers?”
Service providers? like ConEd? and lessons on what they need from us as a product?
To
@François (HOE)
- just point me at what to learn, whatever it is the team decides to use. I’ll double down on studying it. I’ve already said my piece about playwright+python, (actually TS or JS, but I don’t want to add anymore languages that no one in the team is an ninja in.) this is driven by my internal desire in using something modern, used and well documented across the industry- so when we are asked “how do you do test automation?”, it’s something that big players are using.
To
@Erika (Growth Lead)
- I’ve always wondered what outstanding invoices mean haha - We invoiced them of what we’re owed, and they haven’t paid? (edited)
Jason (Product) Feb 4th at 10:38 AM
Service providers like energy auditors and similar folks who are acting as owner’s representatives to help move projects forward. Not ConEd or CPC, but some of the network of approved participants in those programs.
:+1::skin-tone-4:
1
Erika (Growth Lead) Feb 4th at 11:20 AM
@Jeff (QA)
on the outstanding invoices, you are correct. One thing to keep in mind though is that outstanding invoices includes both invoices that are overdue and those that are “current”, meaning they have not reached their due date yet.