BusyBeaver-50M V12 is live.
49M param strict-JSON tool-policy model for Hermes/local agent harnesses. Not a chatbot: it picks the next tool call, then the harness grounds exact paths/commands safely.
V12 resolved eval:
- correct tool: 100%
- arg semantic: 97.9% / 90.0%
- unsafe cmd: 0%
Model: https://t.co/Rls9opwyg5
Adapter: https://t.co/l5rHh3THbh
Save your credits and use open source models when you can.
The new LTX 2.3 lipdub LoRA paired with Chatterbox TTS voice cloning model is the best workflow for lip syncing, change my mind.
Tested Google's new MTP drafter for Gemma 31B on dual 3090
MTP off: 31 tok/s
MTP on: 52 tok/s (+68%), acceptance rate ~55%
Tried MTP=8 (officially recommended for 31B), got OOM
For comparison, my Qwen 3.6 27B + MTP on the same dual 3090 hits 70 tok/s. Gemma 31B is bigger so the gap makes sense
DFlash test next, going to push it further
In the gym to get eyes on UCLA’s Tyler Bilodeau
The 6’9” forward has arguably the smoothest jumper in the 2026 NBA Draft—finishing his SR campaign with 52/46/87 shooting splits. Efficient scorer at 3-levels. Going to carve out a long career spacing the floor at a high level.
You're in CRE.
You know you’re behind on AI.
But you don't know where to start.
This post is for you.
I've spent 200+ hours building CRE tools in Claude as a non-technical person. I use them every day on live deals.
Here's the Claude Starter Kit I wish I had on day 1:
Disclaimer: Claude will blow your mind, but will NOT solve your operational challenges on day 1.
Tinker, fail, have fun, learn the basics and go from there.
You know your business and will figure out where to focus, where to plug in to address your specific pain points.
But you can't get there if you don't start.
I promise the payoff will come. It has for me and just keeps compounding.
Here are five simple use cases, broken down by role, that show what Claude can do. I included pre-made prompts so you can start right away.
ACQUISITIONS
1) PDF => Excel
The simplest of all AI tricks, this is the one that got me hooked. Drop a PDF rent roll into Claude and see it turn it into Excel.
PROMPT: Turn this rent roll into one clean Excel workbook. Include unit number, tenant name, unit type, square footage, current rent, market rent, move-in date, past-due balance, and a live upside column (market minus current). Add annual totals at the bottom and flag any tenant below 20% of market.
Next steps: This doesn’t just work for rent rolls of course. Drop in an OM and ask for the Pro Forma in excel, the lease abstract, whatever. This one you’ll find uses for right away.
2. Create neighborhood amenity maps for pitch decks
This was my first Skill, created out of pure annoyance that I couldn’t get Claude to easily recreate those POI maps it takes hours to create in Powerpoint.
But Claude is so good now, the Skill I built is already obsolete.
PROMPT: Create a branded amenity map for [property address]. Show transit stations, hotels, museums, major retailers, and restaurants within a 5-block radius. Show a maximum of five amenities for each category. Produce it as a standalone HTML file with a dark-mode sidebar and light-mode map tiles so I can open it in my browser and screenshot for a pitch deck.
(want my actual Skill that creates a more OM-ready version of the map? Shoot me a DM).
Next steps: These maps are amazing. Upload your Excel pipeline into Claude and ask for a dynamic map with key stats about each Pipeline property. You’ll be amazed at what comes up.
DUE DILIGENCE
3) Turn site visit voice notes into structured DD reports
Here’s another immediate winner. Ever leave a site walk, sit down at your desk, stare at half a page of scribbled notes and some janky iPhone photos and realize you lost 80% of what you just saw? No more.
Lots of ways to work this into your process, but here’s an easy one.
After the walk, go sit in your car and verbally brain dump everything you can remember into Claude. Just hit the voice record button and it will transcribe to text.
Next, copy the text into a new chat with the following prompt:
Organize this site visit transcript into a structured DD report. Categorize findings by roof, envelope, plumbing, electrical, HVAC, elevator, life safety, structural, and interior/common areas. For each category, summarize condition, flag urgency (immediate / Year 1 / defer), include estimated costs if discussed, and note where a vendor bid is still needed. List any categories not covered.
Distribute to your partners and they immediate know what you know.
Next steps: Record vendor feedback on site, drop third party reports into a running DD chat, there are dozens of ways to use Claude for DD but this simple brain dump exercise is the way to start.
4. Read any third-party report in plain English
Our latest SRA report was 67 pages. The PCA was 113. The ESA was 387.
Claude is good enough now to pick up the most important elements of these reports and call them out, summarize and explain in plan English. By all means double check the work, but this will save you a tremendous amount of time.
PROMPT: Summarize this report in plain English for an underwriting audience. What are the key findings, what would worry a lender, what capex should I add to my model, and what DD action items should go on my follow-up list? Flag anything that could move pricing.
Next steps: Drop in any PDF, ask the same thing. Earnings reports and transcripts, SEC filings, OMs, market studies, etc.
Bonus Prompt for work order reports: Review this work order history and tell me what systemic issues the building has. Call out turnover patterns by unit, recurring maintenance categories, emergency response time red flags, and anything that points to deferred capex. Be underwriting-focused, not descriptive.
DATA/TREND ANALYSIS
5) Crunch any dataset
As a data hobbyist / nerd, this one also hooked me.
Claude runs code beneath what we all see, so as long as we ask the right questions, the math is (usually) right and Excel charts are a thing of the past.
Try this: Navigate to ApartmentList. com’s data page and download their nationwide rent estimates. Upload the CSV to Claude and ask the following:
Analyze rent trends for Austin, Houston, Dallas and San Antonio, normalizing data from 2020-2026, 2022-2026, 2024-2026 and for the past 12 months.
Pick any city you want, any time period. Immediate market insights.
I find these side by side city comparisons a super helpful way to see how certain factors (Covid, immigration, etc) impact cities differently. I can now choose any combo, for any time period with a simple text prompt.
Next steps: dump your expensive, janky CoStar data in and let Claude make sense of it.
--
If you got this far, you’re well on your way. Now, here are three tips for general Claude usage I figured out the hard way (ie trial and error).
1) Ask Claude to help
This is actually tips 1-100, it totally unlocked my Claude usage.
It turns out Claude is much better at using itself than you are, so ask it how. “I want you to help me underwrite deals without losing my personal touch, how can we work together?” “I need to collect rental comp data without breaking any laws – how can you help?”
Rather than trying to brute force Claude into following your low-brow human instructions, get Claude to write the prompts, write the instructions, create you a step-by-step guide.
Embrace the fact that this is, for our purposes, the smartest thing you’ll ever come in contact with – so use the hell out of it.
2) Use Projects for work you do more than once
A Project is a workspace where Claude can more easily do the same thing over and over again.
Projects accrue memory so it doesn't lose the script, and you can even have Claude write itself instructions to perform better and create (for example) due diligence reports in the same format every time.
I have projects for: Deal underwriting, rental comp collection, portfolio analysis, due diligence and others.
For now, don’t worry too much about whether to use Chat or CoWork – you’ll figure that out in time and you can move projects and chats back and forth between the two.
3) Promote good outputs back into your project knowledge
An early frustration of mine was that Claude’s output was inconsistent. I’d ask for a DD report and the categories would be different every time, the graphs looked different, etc. This is an easy fix.
Grind through with Claude what you want the output to look like - remember you can relentless correct and improve and Claude will just happily chug along like the good little sycophant it is and keep making the report better.
Once you have the format you like, save it and upload it back into the project main page and ask Claude to add the report to its memory so whenever you ask for “DD report” you get the same thing.
There are more advanced and cleaner ways to do this with Skills, etc but this is an easy start.