Rob Walling advises that doing things that scare you over and over is how you grow and get better, both personally and professionally. He shares his own experiences of being terrified for his first blog post, podcast episode, stage talk, emcee event, and YouTube video, and how it got easier with repetition.
Derrick Reimer advises founders to map out a complex feature request concretely in code (e.g., using an AI agent) to assess the true expansion of surface area and maintenance burden before committing. Consider whether the feature will move the needle for the business or just add bloat.
confident
Clay Parker Jones recommends establishing a 'rule of law' in organizations: a set of rules that apply equally to everyone and that everyone has consented to, with a mechanism for changing those rules. These rules should focus on what matters to the work and purpose, not trivial policies like expense reporting. The rules should be written down and treated as a temporary creed, held until new data emerges.
Clay Parker Jones recommends that every team should define a 'true purpose'—an enduring why that acts as a beacon. This purpose should be encoded in a document or phrase, referenced frequently without fear of feeling cringe, and must feel true to the end outcome, not just a feel-good statement. The purpose can range from small for an individual team to gigantic for saving the world.
Identify where you are trying to force a deal (e.g., a flaky dating app match, a dragging investor). Make a concrete agreement with opt-in/out, then hold the line without discussing reasons or intent. Some people will fall through, but others will meet you because that calm is attractive.
To avoid vague expectations that lead to boundary issues, make agreements explicit with three parts: what will happen, by when, and the option for the other person to opt in or renegotiate.
Alex Hormozi recommends a set of diagnostic questions to clarify thinking and avoid unproductive actions. The primary question is 'What problem are you trying to solve?' to ensure any proposed action addresses a real issue. A second key question is 'What do you want to have happen?' to cut through emotional noise and get to the desired outcome. A third set of questions—'What does that mean?', 'How do you know that?', and 'So what?'—are used to probe the depth of someone's thinking and connect actions to business outcomes. Finally, asking 'What else could we do with this time and energy that would yield a higher return to the business?' forces a comparison against the best alternative use of resources.
Hormozi advocates for the question 'What would it take?' as one of the most powerful in entrepreneurship. He explains that this question assumes success, which shifts the conversation from 'if' to 'how'. He contrasts this with asking 'Can we?' or 'Could we?', which he says leads people to say 'no' because they make a decision based on incomplete context. He provides numerous examples of how to use this question in different scenarios, such as asking for a faster timeline, buying a company, or getting someone to start a project today.
Consequential creator advice requires independent verification before Today can promote it.
The auto-research layer should only edit a controlled policy surface — memory writing policy, retrieval policy, communication prompts, belief trust rules, source attribution, and replanning triggers — rather than rewriting the whole application. This gives the search process room to improve behavior while preventing it from gaming the evaluation.
When an AI model applies a percentage increase, check it was applied to the correct sub-population rather than the whole population, and compare any stated percentage against the real number disclosed in filings before accepting the forecast.
When auditing an AI-generated financial model, check that every assumption is backed up with a real number from a citation, not just a citation without a number. AI can fail to identify the correct number even when the citation is real, and can draw assumption boundaries (e.g., 5-30%) that exclude the actual disclosed number (45%).
Extra agents pay off the most in planning on ProgramBench, where discovery is the bottleneck. Allocating more agents to planning achieves almost the same performance as the heavy-prompt (PIV) setup at half the cost. Each planning dollar buys almost 1.6x more reward than any other stage (implementation or verification). Planning delegation yields 2.4x more reward per call than delegating throughout implementation.
Replacing Sol workers with cheap Luna workers while keeping Sol as lead achieves almost the same performance at 60% less cost. A strong lead (Sol) with cheap workers (Luna) achieves the same performance as Sol plus Sol but at much lower cost. A 16-planner team (Sol lead, Luna planners) is 38% cheaper than an all-Sol planning team and 70% cheaper than workers at every stage (PIV).
Jesse Hall advises keeping the gap between the caller's last syllable and the agent's first audible sentence roughly inside 1.5 seconds so the call still holds, and notes that getting down to 500-600 milliseconds between turns is when the conversation really starts to feel human-like.
Prospects without pull can be enthusiastic — 'that's the future of our industry' — but aren't saying 'I need this right now'; leaned-out enthusiasm like 'let me think about it' or 'send more info' is not pull, and neither is 'we could use this in Q4.'
Rob Snyder recommends using the pull framework to stake out a claim — state which specific person is stuck — and then go test whether they try to buy before a product exists. If prospects try to buy, you might have something; then see if it repeats. If a prospect doesn't try to buy after the Hail Mary question, treat it as a learning signal that you might not have pull: 'cool, we've learned something.' He notes the Hail Mary question has led startups to completely pivot and take off.
Rob Snyder advises selling to the specific individual at a company who has a project on their to-do list they can't do themselves — 'You're not selling to SpaceX. You're selling to the head of legal at SpaceX who has a project on her to-do list.' This operationalizes the person-level view of pull into a targeting rule for sales.
The framework lets you stake out a testable claim — 'I believe this specific person is stuck' — before any product exists, then verify by seeing if they try to buy.
The thing that really matters is that the potential customer tries to buy — 'okay, cool, how do we get started?' — even before a product exists.
Every stakeholder should evaluate the agent — it is not just one role's job. Get everybody in the room who has a stake in the agent and have them define what success looks like according to their outcome. Stakeholders to include: product, engineering, support, experts, and security.
Define a rubric for what a correct extraction looks like for your documents, then use an LLM as a judge against that rubric to evaluate extraction outputs.
Set up Sales Navigator reports to surface the people most likely to help you, then build a referral prospecting list from former colleagues, your boss and boss's boss, cross-functional leaders, veteran reps in your space, and your company's current customers, working with your CSM to get connected to those customers.
The creators behind most of what cleared in Money.
11494 cleared insights match
2032 cleared insights match
1148 cleared insights match
Choose sources → to get a library of your own and a daily brief.
