It's December!

Happy December, everyone! We’re in the home stretch for this year, so while this one is short, we’ll do a nice look-back pretty soon! Go team!

Metrics

Traction

• Unique Buildings: 12,998
• Annual Run Rate: $1.49M

Financials

• Monthly net burn (3-month avg, accrual basis): -$58,447 (-16.21% MoM)
• Year-to-last-month net burn (cash basis): -$53,553 (-9.1% MoM)
• 2025 Transaction fees to date: $64,163
• Outstanding invoices as of today: $333.939 (+61% WoW)

Annual run rate and net burn calculations will be updated for November after those books are closed. Outstanding invoices WoW increase due to new invoices for Willdan ($83K) and NYSERDA ($50K)

Development

• Bug Count (P-0 and P-1): 2

Last Week’s Highs and Lows

• A short week, with some folks mostly off.

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

• Improving clarity around our roadmap and prioritization process–I really want/need to put more time into 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?
• 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?
• Politics Local is looking great! But national is really scary.

Erika’s List

No crow’s list items this week.

François’ List

• AI Strategy in service of product: using AI for coding/development or for notemaking has been transformative. Can we deliver to our users similar transformative value by embedding AI into our product in a way that’s really useful as opposed to gimmicky? Getting this right will require a lot of exploration and a deep understanding of user needs.
• Getting ready for more traffic/scrutiny/requirements: NYCA is triggering a list of new infrastructure requirements: higher traffic, system resiliency, additional scrutiny on the security of our systems. There’s a laundry list to go through and that we need to balance with the rest of our product work.

Bomee’s List

• Focused on knocking out as much as we can in the next few weeks for NYCA
• Are we paying enough attention to LLMs?
• Getting a good start to NYCA as far as working with our partners goes
• Are we set up to deliver for FSE and Aurora?

On Deck for This Week

• Jon’s 360 (JB)
• A first version of Developments (the feature) is on development (the server)! (JB)

• Here’s what’s on the Company Radar

Upcoming Release

Release 110 will be Monday. Our releases are getting bigger (?) as we have more people contributing! We’ll need to invest more in automating testing, which we’re starting to work on.

• Self-service team joining - Users can now request to join teams, view pending requests, and team admins can approve/decline membership requests (#8027, #8200)
• Login/registration improvements - Enhanced form validation, Turnstile CAPTCHA integration, fixed layout/margins, and 2-column styling (#9933, #10120, #9665)
• Program admin dashboard & feature flag cleanup - New program admin dashboard (#9831), removed several legacy feature flags (team_scoped_buildings, dynamic_default_collections, use_eloquent_collections, team_switching, SSO) (#8426, #9589, #9996, #9545, #9539)

Release 111 So far:

• Development grouping feature - Buildings can now be grouped into developments with automatic sync from BKB, sibling building discovery, manual add/remove capabilities, and a development summary page with building metrics (#9776, #5152, #7982, #10077, #10076, #10090)
• Property name field - Added user-editable property name field to buildings, displayed in header and Property Information tab, with tracking of who added it (#8481)
• Code quality & permissions - Strict Rector configuration, DDD-style domain exceptions, new ALLOW_COLLECTIONS team permission, and customize measure permission migration to legacy teams (#9986, #9788, #9860, #10064)

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?