Caliber (@trycaliber) header
Caliber (@trycaliber) profile picture

The operating system for AI native organizations - helping teams measure, manage, and improve how they use AI.

Tel Aviv, Israel
Joined September 2026
Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)Photo by Caliber (@trycaliber)
caliber is the intelligence layer for how your org runs on AI. plug in your HRIS and see: - AI spend by team and by owner - $ per shipped item, per team - every seat, key and agent, plus unused ones already live with paying customers. trycaliber.ai
2
3
13
34,595
the line i'd underline in the revolut story: gains reportedly showed up once engineers stopped saving ai for the hard tickets and used it on everything. cheap tokens gave them permission. i'd want to know which teams changed habits first, and what the rest waited for. teapaw.org/guilleflorvs/status/21…
BREAKING: Revolut moved ~2,000 engineers onto self-hosted GLM for coding and pushed Claude Code and Codex to the exception list. Per David Abitbol, who leads AI ops there: 56 Nvidia B200s, a blended 30 cents per million tokens, roughly a tenth of what they paid Anthropic and OpenAI. Engineering lead time improved 70%. Here's the part that matters: the gains showed up when tokens stopped being rationed. Engineers quit saving AI for the hard tickets and pointed it at everything. Frontier models become the exception, open weights become the default. That's a pricing problem for every lab heading to IPO. h/t @OliverMolander Would you move your team off frontier APIs if the bill dropped 90%?
3
i'd read the sessions where someone gave up and finished the task by hand before looking at any ai usage chart. they show where your work and the tools don't fit yet, and those spots are often fixable for a whole team at once.
8
the tip at the end is the one i'd keep: have the bot restate what you asked in its own words. it's an old trick for briefing a person too. i suspect people who already did that with teammates are getting good with agents fastest. teapaw.org/poteto/status/21165762…
here’s a short grok bot guide on how i create high quality bots and manage my team. ask @bot to read this post and help you improve your team! • add dr eggbot to your team! he’s my bot designer that i use to create bots • you don’t need a lot of bots. a few good bots can be more useful and easier to manage than a large team • tell your bots to create skills for itself as you give it instructions on how to do tasks. this lets them do them more consistently even over long conversations. you can even ask it to create a private github repo for you to store all your skills if you want them preserved independently • add connectors, use the vault, and give access to all the tools you use to do your work. you can also ask your bot to setup its own email and it can sign up for its own accounts for better separation • thinking about all the work you do by hand, or steps in your workflows where you have to copy and paste information back to your bot. ask your bot how it can do that for you instead! • imagine you hired an intern, how would you onboard them and help them do the work correctly and efficiently? introduce yourself to your bot and describe the work you do, then ask it how it can help you automate it and my favorite tip: use voice mode or the transcription option! it’s a good way to just brain dump a lot of information. then, at the end, tell your bot to “restate this in your own words” so you can confirm it understood you x.ai/bot/_jOdbfkB16zxu7MRcmR…
2
20
boardy cut ci from 40 minutes to 2 because agents push all day. good call. i suspect the ci wait was also when a lot of engineers reread their own diff, so i'd want that reread to move somewhere on purpose. teapaw.org/owengretzinger/status/…
1
3
35
cursor's new agent sdk keeps an agent's prompt in markdown and its tools in typescript, so a good agent is now just files in a repo. i'd watch whether the one someone builds this week is running on the next team over a month from now, or only on theirs.
17
adoption % is the easiest ai number to move. a reminder email will do it. i'd rather see what each team stopped doing by hand this quarter. that one is harder to fake.
2
27
Happy to partner with @nvidia, details soon :)
2
48
Start letting Cal unpack your AI bill, down to production value and individual ownership.
3
63
putting a cap on tokens is easy. knowing which team burned through it, what shipped, and what broke after launch is the hard part. a cheaper model won't fix a workflow nobody owns.
1
2
82
careful..
1
1,351
ai adoption is a terrible north star. a team can double its prompts, tokens and active seats without shipping one extra thing. show me accepted work per team, what it cost, and who owns the bill.
61
connect HiBob, Jira and Anthropic. get this view in 3 minutes, with queryable insights and actions. AI spend and tokens for every team and manager, rolled up the org chart, plus a year of spend, PRs and cycle time next to it. this is caliber v2. @HiBob_HR @Jira @AnthropicAI
3
75
the free part of caliber. ai-setup writes CLAUDE.md, cursor rules and AGENTS.md from your repo, keeps them current on every commit, syncs skills across agents and compacts long sessions with Jev. 1,280+ stars, 2.4K npm installs last month. github.com/caliber-ai-org/ai…
1
197
your HRIS already knows the org. caliber adds the AI layer. connect HiBob, tag teams with their tools, and get spend, usage and output per team, with the actions to fix what's off.
2
1,433