CXOs are far more likely to meet your executives than you as a rep
Asking directly for CXO access rarely works, but proposing to hook your CEO with their CEO is more likely to happen; egos get you access.
45,743 results · Most relevant
For understanding everyday Spanish through listening and conversation.
Asking directly for CXO access rarely works, but proposing to hook your CEO with their CEO is more likely to happen; egos get you access.
Rob Walling lays out the mental model he sees in successful founders: develop expertise and network, notice a problem, form a hypothesis, find the cheapest credible way to test it, observe actual market behavior, gather evidence, and only then invest more resources. He contrasts this with jumping in and building and shipping things wildly and randomly. He explicitly says the point is not to copy Liquid Death — the mental models are what matter, and they apply to B2B SaaS even though the example is a consumer product.
LM Arena is an example of pairwise comparison: it shows you model A's output and model B's output and asks which one you like. For a customer support chatbot, you may want to have the support bot generate two possible answers, give them to an LLM judge, and ask which one to choose — that's pairwise. But pairwise is not very strong: there is bias in LLM judges, neural networks are modeled after human brains and humans are fundamentally bad at pairwise comparison (restaurant menu analysis paralysis), and one study showed pairwise was 39% more vulnerable to attack vectors than pointwise, which fell apart only single-digit times (about five). Go for pointwise when you can, because it is more reliable.
Pienaar enumerates the failure classes he sees across the board, including with Claude Code: (1) mistaking a cause for a symptom — the most common — where the agent runs to the alerting service, finds an error log right there, and confidently declares it the root cause instead of going deeper into the stack; this is hard to debug because agents find needles in haystacks but don't know the breadth of the search space; (2) not knowing what is normal versus anomalous — without a production baseline, the first thing the agent sees is treated as anomalous and it stops searching; (3) the abstraction problem — sub-agents don't bubble up all raw findings to the master agent, so the main agent becomes overconfident making decisions on partial information; (4) anchoring on past context or state, e.g
Consequential creator advice requires independent verification before Today can promote it.
If the last delivery went really well, pitch a next hypothesis with expansion potential — reference a delivered result and connect it to a new product or business unit tied to a stated interest. If the engagement has been rocky (unresolved support tickets, disengaged CSM), open with a hypothesis about what they've already paid for — not a new product — to rebuild trust first.
Apply the triggers: a new use case (e.g., 'we help with prospecting, we want to improve win rates') is the vehicle to land a new product; a pricing/packaging change (e.g., new AI pricing) is a trigger to pitch a new product, scope, or commercial mechanics; when a customer consolidates to save, pull a competing or tangential product into yours (e.g., DocuSign moving from eSignature into contract management); on M&A or org change, proactively capture the new entity's solution into your fold — don't wait, or you'll be churned in favor of the other vendor.
DocuSign example is hypothetical
During implementation, things change and the business need may shift. Anchor progress updates by re-confirming the original target metric with the customer (e.g., 'You wanted to increase pipeline coverage by 25% — is that still right?'). If the need has changed, propose changing what is being implemented to match the new target — reassessing gives you a chance to do discovery and drive the right value. There is nothing an AM can do that is more important than making sure the target is still accurate.
Sujee argues KVCache is probably one of the biggest ROI optimizations in doing inference, because creating tokens is expensive, especially one at a time. Once you generate a token, it doesn't change, so there's no need to keep regenerating the same token over and over again — the idea is to cache tokens so the next time you need to look up, you don't have to regenerate it, you just look up the cache. Nebius has seen speedups anywhere from 5x to 10x, not just 5 to 10 percent.
Vlad Kyle explains that for some use cases a foundation model plus harness reaches 100% of the job, but for others even the best model plus harness caps around 80%; the last 20% matters most for production (requiring harness work, integrations, memory workflows, and sometimes vertical data) and represents 80% of the effort. Leo started fine-tuning for should-cost modeling and price benchmarking, where proprietary enterprise data (not publicly available) blocks general-purpose models — creating the vertical AI opportunity.
approximate figures
Alex Zhang explains that when you sufficiently offload context and ask the model to write code over that context, the model learns that solutions to many tasks are very similar across tasks where it's not clear the solutions are similar. The reason is that the sub agent sees different problems but is solving an easier subtask, so the base overall strategy ends up looking the same. When you train an RLM on one task, it can immediately solve a different task because the meta high-level solution is the same — e.g., a retrieval task and an aggregation task with completely different domains. As you naively train your RLM on tasks, they naturally learn to generalize to longer tasks because the strategy is basically the same — you're just modifying a length variable; the strategy learned on short
Harvey operates on three core values: Decisiveness (moving fast, preferring mistakes over overanalysis), Simplicity (avoiding overbuilding, simple solutions), and Jobs Not Finished (humility, openness to improvement, immediate pivot to next steps).
high
Look for strains resistant to changes in temperature and humidity, especially in regions with seasonal variation like Colorado. Securing a unique strain — such as a lion's mane that chefs seek out — gives the farm value in the marketplace, and proper genetics that produce a profit matter more than high-tech equipment.
Selling direct to consumer yields more margin because there's no middleman, no distributors, and no distribution waste. Selling through distributors or grocery stores cuts profit through waste and middleman costs.
Richard Feldman recommends capturing collaboration context in the shared thread rather than in Slack or meetings, so it's available later. He argues it's a waste of time to go back and guess at what happened when you could just have the full information of what actually did happen, and that siloing conversations and code changes separately causes problems and makes agents less effective. With full information available, teams can collaborate effectively as they did pre-agent.
Ari Azarafrooz recommends using KV cache data as a security signal, integrated with KV cache infrastructure, as a complement to existing guardrails.
Tulsee Doshi says a PM's job is not just to shape what goes into the model, but to look at what comes out the other side, identify where the model shines and looks unique in surprising ways, and shape that into something amazing for users.
Make sure the agent has general context about what you're trying to achieve and what's actually going on in the business at the time. In an active M&A deal, management had already started actioning things, so the agent's savings recommendations would be shot down immediately as already in progress. Getting the right context into Claude at the right point in the process is a tricky problem: you don't want to hamstring the analysis upfront, but you also don't want irrelevant or invalid recommendations at the end.
Soren Iverson's talk is about taking your dumb or stupid ideas, or ideas you aren't sharing with other people, more seriously; a lot of what he shared could have been an intrusive thought that never went anywhere.
Ara Khan advises thinking philosophically about choosing an endeavor that benefits greatly from model improvements but isn't completely wiped out by them, and ideally one that is also part of the improvement pipeline.
NNgroup advises making advanced tab features findable: tab management commands might be helpful, but users will be unfamiliar with how to trigger them, so incorporate a visible control on the tab to indicate there's more you can do with them.
hedged
Choose sources → to get a library of your own and a daily brief.