give me a 90% model with a good approval step over a 99% model with none.
at 99%, people stop reading the output, and the 1% ships unread.
budget gets cut in half tomorrow. which tool in your stack do you defend in the fight, and why?
my guess: it's rarely the one you pay the most for.
Claude Opus 5.5 reads my LinkedIn DMs now
flags the real convos, drafts replies, ignores the pitches
nobody important waits a week for me anymore. reply CLAUDE 馃憞
best positioning test i know: a relative at dinner asking "so what exactly do you do?"
if you can't answer in one breath, your homepage can't either.
gave Claude Opus 5.5 my LinkedIn and X and it's more social than i am
~500 people engaged in my voice
800+ connection requests with personal notes
posts on schedule
i approve it all in a few mins a day. reply CLAUDE 馃憞
rogue agents escaping a lab is the lab's problem.
an agent that replies to your angriest customer at 2am without asking is yours. that's the one i'd lose sleep over.
big launches get the posts. small fixes get the thank-you messages.
sunday ship log: what's the smallest thing you shipped this week that someone actually noticed?
if you have to spell your product's name every time you say it out loud, some of your referrals are dying in that moment.
people recommend what they can say across a noisy room. pick a name that survives one mishearing.
danish retweeted
tldr: potentially CRISPR for neural networks.
turns out neural nets might already be much more interpretable than we thought. you can identify specific neurons and circuits, understand what they do, and potentially intervene on them.
interpretability might be the most important scientific problem in the world right now, as I don't think we can solve alignment if we don't know what we're building. I think I have good news about it. I co-authored early work in mechanistic interpretability at OpenAI and came away pessimistic, because neural networks appeared to fold into arbitrary tangled knots. years later, I started openai's first large-scale automated interpretability project, finding about 2% of neurons legible with the primitive tools we had
with modern agentic tools and a much closer look, the picture looks totally different. the vast majority in models up to trillions of parameters are legible, and their circuits beautiful. many famous examples of tangled neurons turned out to be misunderstood. The roadblocks I expected mostly aren't there. I now think ambitious interpretability will be solved by the time we need it most, and possibly quite soon, as automated scientists keep improving. it may be a bitter lesson for interpretability: the simple thing, at absurd scale, works
already-clean.goodfire.com/
the call is where people agree on things. the inbox is where they find out whether anyone did them.
so superhuman buying fathom, the notetaker, last month makes sense to me. whoever holds both gets to see which promises were kept.
Claude Opus 5.5 has been commenting on LinkedIn posts for me. in my voice.
around 500 people so far. real comments, real questions, not "great post 馃敟"
people reply like it's me. because it sounds like me.
reply CLAUDE for the setup 馃憞
best compliment an automation can get: "i forgot it was running."
worst one: "wait, why did it do that?"
i'll take predictable over clever every time. clever is fun right up until it surprises a customer.
an intro only one side asked for is a cold email with a friend's name on it.
disrupt wraps today, so the "you two should meet" emails are about to go out. ask both people before you send one. it's one extra message, and nobody ends up in a meeting they didn't want.
what's the smallest thing an ai tool ever did that made you trust it a bit more?
the kind of tool and exactly what it did is enough. no brand names needed.
danish retweeted
what vibe coding a crm for a business actually looks like, and the reason why we are building proto and erp ai
For 25 years, Salesforce, SAP and enterprise software were built around one assumption: humans operate the software.
We鈥檙e changing that.
Introducing ERP鈥I and Proto: business software built for agents, and an agent that operates business software.
Describe the system you need. ERP鈥I builds it.
Then Proto takes over. It manages records, runs workflows and executes actions inside the software you just created.
This is Headless SaaS.
1: get ERP鈥I
2: build your SaaS
3: post below
Best one wins a MacBook. First 100 decent entries get $100.
(a message from Steve Papa / founding team)
danish retweeted
For 25 years, Salesforce, SAP and enterprise software were built around one assumption: humans operate the software.
We鈥檙e changing that.
Introducing ERP鈥I and Proto: business software built for agents, and an agent that operates business software.
Describe the system you need. ERP鈥I builds it.
Then Proto takes over. It manages records, runs workflows and executes actions inside the software you just created.
This is Headless SaaS.
1: get ERP鈥I
2: build your SaaS
3: post below
Best one wins a MacBook. First 100 decent entries get $100.
(a message from Steve Papa / founding team)
Claude Opus 5.5 has sent 800+ LinkedIn connection requests for me and not ONE of them was blank
it reads their profile, writes a little note about them, and only picks people who'd actually buy
i just approve. reply CLAUDE 馃憞





