2 weeks to go to 2026

I don’t know about you, but I like to get stuff in ship shape before taking time off so I’m in clean-up mode: Going through my open tickets, doing my end-of-year admin stuff (like turn on company-wide email footer, etc.), consent proposals for 2026, etc.

On the Momentum app front, I’d love to get Programs wrapped up and shipped (flagged, of course) as well as Scope Builder refactor done!

What’s on your end-of-year list?

Metrics

Traction

• Unique Buildings: 12,482 (Real time, via Admin panel!)
• Annual Run Rate: $1.55M

Financials

This month we are spending a little more time on education on the updated list of metrics and why we are tracking them. Descriptions of each metric live in the handbook and this link will be available as a reference each week, versus in-line descriptions.

Metric	Value	Takeaway
Revenue (YTD)	$1,497,535	On track toward $1.6M 2025 goal
Transaction fees	$63,403 (4.2% of YTD revenue)	Healthy fee capture
Annual run rate	$1.55M (+4.2% MoM)	Recurring revenue stability improving
Cash	$527K	Solid liquidity
Accounts receivable	$296,564 (-11.2% WoW)	Expect $240K collected this month; majority from L+M
Runway	15 months	Above the 12+ month healthy benchmark
Net burn (monthly, accrual)	-$43,420 (-22.8% MoM)	Burn improving; aids runway
Net burn (YTD-to-last-month, cash)	-$49,681 (-7.23% MoM)	Cash outflows easing

Details

• Revenue: Goal remains $1.6M for 2025 and we are on track to hit it by year-end.
• Annual run rate: We want this to keep climbing as an indicator of recurring revenue stability.
• Cash and AR: Combined, these are near-term funds to operate the business. We expect $240K of AR this month (63% or $153K from L+M for ConEd Cost Shift).
• Runway: We have averaged 14+ months all year; 12+ months is healthy for early-stage companies.
• Net burn: Two views (accrual vs. cash) help spot timing differences between incurred expenses and cash leaving the bank. We expect the figures to converge by year-end as accrued expenses are paid and revenue is collected.

Current expenses by department

Department	Spend	Explanation of MoM Change
COGS	$31K (+234% MoM)	Increase expected (new hire and consulting)
G&A	$64K (+14% MoM)	Increase expected (legal fees)
R&D	$139K (+28% MoM)	Increase expected (consulting up 140%)
Sales	$19K (-31% MoM)	Decrease expected (timecard wages moved to R&D)

Development

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

Last Week’s Highs and Lows

• Good discussions and some progress this week on a path for tackling the mythical UoB, with cleaner data responsibility lines across Momentum and Calc Service. (FH, +1 BJ)
• Sharp contrast between calls this week with NYSERDA on BDP -where we’re back to confusion from NYSERDA on which internal users we should be targeting-, vs that with FSE -where there seemed to be excitement about getting help on data they know to be messy and complex-. (FH)
• Release 110 has a lot of stuff in it, both front- and back-end. Kudos to the team for getting so much in, and Jeff for testing it all! (JB)
• We’ve help up with mini-360s to provide timely feedback! Kudos to Lorraine for scheduling her own 360! <3 (BJ)
• Releases and sprints seem very much according to plan – even if timelines change, we’re handling it per our process. This is good! (BJ)

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?

François’ List

Repeat from last week:

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

Jason’s List

Repeats, with a tweak:

• 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. Although local is trying to push through a cooling mandate, which is good in theory, but could derail things if executed poorly.

Bomee’s List

• NYCA contract is in nearing the end of the procurement process (phew?) and we’re in good shape against the milestones. I’m cautiously optimistic that the inevitable unexpected stuff with project kickoff – given number of partners – won’t cause stress for us on on-time delivery.
• Fueling growth for BKB and Calcs. I’m pretty convinced that we should and can raise in spring 2026, but we need to do our homework so that if we raise, we know exactly where those resources go. Without it, we probably won’t be successful raising.
• Product development process for NYCA, ConEd Recompete and HPD - a lot to organize for 2026
• Cash. Looking forward to replenishing our cash with 2026 revenues. We’ve kept 2025 burn level with last year despite growth, and (hopefully) will have some flexibility next year in balancing runway.

On Deck for This Week

• Release 110! (JB)

• Chat with Willdan about our ConEd MFEEP SOW - hopefully we can make some progress this week. (JB)

• Closing out 2025 - look out for announcements in Slack. (EP)

• Here’s what’s on the Company Radar

Upcoming Releases

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?