AI is upon us

June 20, 2025

Oh, boy.

Hey claude we’ve spent a lot of time together this week. What do you suppose I have been thinking about?

Looking at our conversation history and the work we’ve done together, I can sense a few things that might be on your mind:

Process & Automation - You seem focused on streamlining workflows and reducing manual tasks. The GitHub Actions we just built automate ticket status updates that your team was probably doing manually. This suggests you’re thinking about efficiency and how to free up time for more valuable work.
Testing & Quality - Your emphasis on testing the workflows before deployment, plus the test commands in CLAUDE.md, indicates you care deeply about reliability and catching issues early.
Team Scale - Building these automations suggests your team is growing or the project velocity is increasing. Manual ticket management works fine for small teams but becomes a bottleneck as you scale.
Developer Experience - The way you wanted to simplify the setup (removing the PAT requirement) shows you’re thinking about making things easier for your team, reducing friction in the development process.
Maybe you’re also thinking about the bigger picture - how to build sustainable systems that help your team ship quality software faster while maintaining sanity? The fact that you’re investing time in tooling and automation on a Friday suggests this is important to you beyond just the immediate task.

What Claude said. Scary and exciting at the same time.

Metrics

Traction

Unique Buildings: 6,648 (May, +300 MoM)
Annual Run Rate: $1.49M

Financials

Monthly net burn (accrual basis): $54,857 (3-month avg, -28.59% MoM)
Year-to-last-month net burn (cash basis): $75,214 (-8.87% MoM)
2025 Transaction fees to date: $12,095
Outstanding invoices as of today: $213,733 (-$88,229 WoW or -29.22% WoW)

Development

Bug Count (P-0 and P-1): 6, one of which is being addressed with this week’s release!

Last Week’s Highs and Lows

HPD RFP response was sent in! Fingers crossed! -bj
Lots of code in PR, thanks to Claude (high and low) -bj
We sent out the first L+M deliverable early! (JB)
Erika’s and François’ 360s! (JB, +1 FH)
Marc received some non-public data about completed retrofit projects–may this be the beginning of more to come! (JB)
Recent chats with ex-coworkers across the industry make me think that we are not doing so bad in integrating AI tools in our workflow, as clumsy as they may feel right now. Let’s keep at it! (FH)
Walked the floor for a few hours at a large NYC trade show for energy efficiency – there are a lot of vendors peddling lots of solutions – (MZ)
Somewhat promising (but still early) convo with the “city scale” sustainability team at WSP, a 70,000 person global professional service firm about potential ways for us to “make money together” (MZ)
Less promosing (but still informative) late conversation with Leviticus, a Northeast Community Based lender who isn’t going to move forward with a Momentum subscription due to GGRF being in limbo and the development / refinement of scopes not ultimatley being in their wheel house – but they are still interested if we or others could identify projects that need their capital using Momentum (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?

Bomee’s list

Getting Marc a product he can sell Are we getting faster?
Team dynamics Just as we’re converging, AI has happened to us. We’ll see what difference that makes.
Cash. We still have a net burn that we need to minimize.
NYCA and ConEd Recompete – We’re waiting for (hopefully) two big yes’es.
Political and economic uncertainty in NYC and beyond.
Will AI move our cheese?.

Jason’s List

Carryovers with some tweaks:

Using AI tools to help us move faster We’ve been having more human about how to incorporate AI tools in our workflow. I hope these can help us move faster soon. We have a ton of stuff to build, and I feel like we end up spending a lot of time working on table stakes features that really aren’t even what we think will distinguish us in the market.
Local politics The federal picture certainly isn’t good, but we also have some local political risk on the horizon. There’s a big NYC election coming up this fall. Primary day is this Tuesday 6/24, and a lot of folks have already voted early. It’ll still be another 1-2 until we learn the outcome, but the city is holding its collective breath. There’s a lot of belief that if Cuomo becomes the mayor, Local Law 97 would face some serious setbacks—maybe even go away.
NYC Accelerator and ConEd Recompete These are both big contracts with outsized impacts on revenue and product roadmap. Both interviews are done now, and eager to hear back.
Balancing new feature development with cleaning up debt We have a lot of new features to build, but also a lot of legacy code debt that can make adding those features take longer than it otherwise should. How much time do we spend pushing new features out to the door to keep current and potential clients happy vs. time spent getting our codebase cleaned up so we can move faster in the future. Hopefully AI tools will enable to do both these more quickly, which would make the tradeoff less.
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.

François’ List

AI tooling and fun: We are feverishly integrating new AI tools and processes to help us move faster, and it should be a lot of fun, yet it sometimes feels to me like the opposite: the joy of creating is being replaced by the drudgery of assessing massive amounts of AI-generated code and documents. Finding ways to pass the baton human-AI-human more effectively is going to be a challenge.
Shipping small, often, well, and safe: I’m happy to see parallel progress on dusk, playwright, and ephemeral environments. Can we close in on at least 2 of these 3 quickly?

(repeats below)

Growing the team: the “$2.5M demo” is not only motivating on its own, it also re-opens the door to hiring. Let’s prep for it, so that we can identify the right skills, attract the right candidates, and welcome them efficiently. Ahead of permanent hires, and to flex our onboarding muscles, could it make sense to get help from consultants for Laravel expertise, or interns for testing help?
Automated Testing: I’m convinced that reliable tests that run quickly and reflect our users’ experience are table stakes to move faster and with more confidence. Are we going to find the bandwidth to get this party going?

Marc’s List (repeats)

Momentum Need to make sure we are making progress with market engagement even as we wait for dust to settle on big rfp’s.
Looking over our shoulders What would an AI native start up do to this space in 2026 or 2027 and how can we build a moat?

Erika’s List

Budget for 2H 2025 Carryover from last week but will be finished by the end of the month - seeking some outside support to ensure we are able to look at our scenarios with a high level of confidence. Completing the scenarioes will support strategic decision-making around hiring and other resources over the second half of the year and beyond.
Growing the team This requires conversation amongst the team leads post mid-year budget review, but also want to think ahead as far as resources and needs that could support a search such as salary comps and regional employment considerations and guidelines. This would also require getting the documentation on worldwide work into the handbook, along with other policies, asap so everyone is aware of how we should proceed with hiring, onboarding and integration moving forward.
Hiring Process Along with growing the team, also thinking about how we interview and how we could screen for things that are important to a new hire being successful in the company. How we hire is directly related to how we onboard and it’s important to have an idea of how we evaluate not only the ability to do the job/background but capacity to work in our horizontal environment.

On Deck for This Week

(Postponed from last week) Marc and I will be meeting with Dextall, a manufacturer of panelized envelope systems on Wednesday. I showed them Momentum at The Clean Fight summit a few weeks ago, and they really liked advanced search. (JB)
I’ll be talking with The Clean Fight about using Momentum for their cohort, which will mean some additional revenue coming our way! (JB)
Randy will onboard to help Jeff get up and running on Playwright. Yay! -bj
Trying out Github Projects and our new automated ticket status updates -bj
Marc’s 360 (MZ)
Re-engagement with two desired owner’s rep users: KC3 and Aurora Energy Advisors (MZ)
Causal review (EP)
Here’s what’s on the Company Radar

Upcoming Release

This Wednesday’s release will probably have:

New Search Export Feature - Ability to export search results to spreadsheets, with options to export all results or just selected buildings (feature flag)
Extended LL97 Compliance - Building fine calculations and compliance tracking show projections all the way to 2050
Search Interface Improvements - Should feel more responsive
Collections Table Fix - Fixed display issues in the building collections management interface
UI Bug Fixes - Fixed pagination dropdown being hidden by container overflow and special character handling in search

And

Additions to bid review in our new project UI: totals and per-measure view
Behind the scenes: prep work for L+M reports (new measures, etc.)

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?