Method · MoneyThe verifier first generates a rubric with N criteria of what success looks like, ranks the most relevant screenshots in the trajectory for each criterion, uses the top-K evidence group to determine whether each criterion was met, and outputs a scored rubric with partial credit (process score) plus an outcome Boolean with an explanation.
Method, not a verified protocol.
AI Engineer · Your LLM Judge Is a Confident Liar: Building Better Verifiers — Browserbase
Method · MoneyShip an AI application (e.g., a docs page with an AI chatbot), let customers use it, and real production logs start coming in. Sample a subset of production logs — maybe 10 to 20 rows — to create a dataset. From that sampled dataset, write your task, write your scoring system, and run evals; tweak your dataset, prompt, or score and run multiple different evals. After running a couple of evals and seeing which does best, you learn something about your system, make the code change, deploy it back into your application, and the whole flow repeats because those changes show up in your production logs.
Method, not a verified protocol.
AI Engineer · Agentic Search vs Vector Search for Coding Agents: We Ran the Eval — Braintrust
Method · MoneyOpen with the 'heard the name tossed around' opener — 'Hey [name], we work with a few other [portfolio company type] companies. It's [name] from [company]. Have you heard our name tossed around?' — mentioning mutual connections or shared context before pitching. Then lead with the problem before the solution (a 'problem proposition' or 'reverse pitch'). For objections, use the 'Mr. Miyagi method': agree with the objection and sell a test drive before fully addressing it.
endorsed
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Method · MoneyStart with a 15-minute recruiter screen to filter out candidates who cannot compose a sentence or show basic professionalism, protecting the team's time. In the hiring manager interview, assess whether the candidate is 'smart' and 'cares' by asking why they want to get into sales and what they did to prepare. Then run a mock cold call twice: the first call will suck and that doesn't matter — evaluate whether the candidate listened to prep material and tried to apply it, and whether the gears are turning. Give no more than two points of feedback, coach them to lead with a problem statement instead of a pitch, then run a second call to see if they adapt. If they don't change anything on the second call, that's a massive red flag. After the mock calls you should know if you have a 'triple A'
endorsed
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Method · MoneyRun an SDR team on five weekly meetings: Monday morning meeting (energy + activity focus), Tuesday teardown (cold call/email/account review), Wednesday one-on-ones (individual coaching), Thursday teardown, and Friday team dials (energy + activity). Bookend the week with energy-focused meetings on Monday and Friday to keep the team dialing.
anecdotal
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Method · MoneyA concrete multi-step method: (1) go to the company's leadership page and manually add CEO, CFO, SVPs; (2) use LinkedIn and Sales Navigator to find additional CXO/SVP/VP-level people; (3) guess reporting lines (e.g., Scott reports into Jordan, COO Valentina reports into Jordan); (4) add people like Fatima and Nadia based on best guess; (5) make up an excuse for a one-on-one with the champion and walk them through the guessed chart so they correct it. Laura prefers doing this in a tool called 'Mirror' and has built charts down to six layers in some organizations.
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #608 - How Mapping the "Shadow" Org Chart Got Me to 305% of Quota
Method · MoneyA multi-step method for building multi-threaded executive relationships before a deal closes: map the customer's org chart and power base in a Miro board, seek to be corrected to learn the real org chart, get introductions from the champion to key people by framing why access is in the champion's interest, then play matchmaker by pairing peer levels (CEO to CEO, engineers to engineers, C-suite to C-suite) using the EA, a ghost-written message, and a prep doc.
The hosts present this as an endorsed playbook for enterprise deals; no outcome data is cited.
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #608 - How Mapping the "Shadow" Org Chart Got Me to 305% of Quota
Method · MoneyRun AM discovery in three steps: (1) recap results already achieved from the last project — start with the trust factor ('this is what you asked us to do and this is the result we got') rather than a hypothesis, unlike AE-style discovery; (2) run discovery for the next outcome; (3) come back with a next step to solve it. At the end, tell the customer you'll return in a week with a plan built with the CSM and product expert showing how they can reach the outcome using the product.
Commercial context: The creator presents this as their own offering and directs viewers to get it.
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #604 - Upsell & Expansion Masterclass: 7 Lever to Grow Any Account
Method · MoneyA coherent, ordered method from the talk: (1) Give the agent Markdown files — docs checked out locally, plus major website pages (changelog, pricing, features) converted to Markdown — so it understands everything about the business and stays perfectly in sync with shipped features; (2) provide all context as a large Claude MD instructions file (~30,000 lines) containing guardrails and operating advice, and ship an update to it whenever the agent gives a wrong answer or has a bad experience, so every future conversation improves; (3) show the agent the URL of its sources so it can cite them to customers for verification; (4) use a dedicated embeddings partner (Voyage) so the agent gets the most relevant documents up front and answers faster; (5) containerize the agent as a Docker file and (
Method, not a verified protocol.
AI Engineer · We Built an AI Support Agent That Resolves 80% of Tickets — AssemblyAI
Recommendation · MoneyLincoln Murr recommends giving an agent a wallet or financial account so it can pay for different APIs on a one-off basis, instead of pre-funding accounts and managing API keys.
AI Engineer · Most of Your Docs Readers Are Now AI Agents - Hahnbee Lee, Mintlify & Lincoln Murr, Coinbase
Recommendation · MoneyJohn Stecher says that if models will be good enough and compute sufficient in six months, delay building the application today and address it with the new model — it will cost less, provided the need for the application isn't pressing. He also cautions that you don't want to wait too long to build something, because you can always be waiting for the new model or new technology.
AI Engineer · Why Waiting for the Next AI Model Can Pay Off - John Stecher, Blackstone & Scott Worland, Norm AI
Recommendation · MoneyJohn Stecher recommends using agents to help understand existing human workflows, then writing code to optimize for straight-through processing and injecting agent intelligence only where humans previously made decisions. He also advises stepping back to identify work agents can do better, to offload intellectual cycles from investment, finance, and engineering professionals so they can do higher-value work.
AI Engineer · Why Waiting for the Next AI Model Can Pay Off - John Stecher, Blackstone & Scott Worland, Norm AI
Recommendation · MoneyContinuously test the workflow at every part of the workflow, designing the test to that specific part and measuring success in that element. For a 100-step workflow, each step must be evaluated for what goes into it, what comes out of it, and the expected outcome. Testing only the final output misses intermediate failures, like an image edit that changed the background but added unwanted handles. Assuming input and output to be the outcome of anything in the workflow leads to untested failure points.
AI Engineer · If Your AI Scores 100%, Your Eval Is Wrong - Ramakrishnan Lokanathan, eslams.com
Recommendation · MoneyCharlie Holtz advises creating 'slot-free zones' — parts of the code base or app that require really strict human review. He warns that if you're not careful about slot-free zones, your code base can get in a really tricky spot, and notes Conductor has had to rewrite their whole app a couple of times because of this. As a concrete example, any change to the migrations file in Conductor's CI requires a human to review it. He also notes this careful-in-places approach is unusual: most people assume top builders are pure token maxers ripping through 30,000-line PRs.
AI Engineer · Orchestras, Not Factories: How the Fastest Builders Work — Charlie Holtz, Conductor
Recommendation · MoneyDaksh Gupta recommends optimizing the prompt as the lowest-hanging fruit for improving a review agent. Start with a very simple prompt like 'review this PR and output the comments in GitHub's API schema format', then orient the prompt around two themes: look for specific bug types, and skip the nitpicks. Do internal data science on existing outages and incidents to figure out what types of bugs your codebase has the highest propensity to produce, create a catalog of those bug types, and have your prompt look for them. Also expressly tell the review agent what a nitpick is and not to look for them. He cautions that changing a small thing in the prompt has a weirdly big impact on the number of comments the agent writes, which is quite scary.
AI Engineer · How to Build an AI Code Review Agent - Daksh Gupta, Greptile
Recommendation · MoneyDaksh Gupta recommends model inversion: use a different model to review code than the one that wrote it — if Claude Code wrote the code, use a GPT model to review it, and vice versa. The types of bugs produced by Claude models and Codex models are quite different from each other (Claude models are something like three times more likely to produce one-off errors than GPT models, while GPT models are significantly more likely to produce auth bypasses than Claude models), and these differences are artifacts of post-training, as far as he understands. Using the same model to review code that the same model wrote results in relatively fewer bugs caught, because the model fails in the same ways during review as during generation. Greptile found a 10% higher catch rate if you flip models, and a 1
AI Engineer · How to Build an AI Code Review Agent - Daksh Gupta, Greptile
Recommendation · MoneyDaksh Gupta recommends building a dataset of historical PRs that caused outages and incidents to evaluate your review agent: catalog pull requests that have caused outages and incidents in the past if your company nicely catalogs when things go wrong, run every version of your review agent through that dataset and measure with what frequency it catches those bugs, and keep the dataset updating in real time because the topology and ontology of bugs changes over time in a changing world. This allows you to tune the prompt more confidently. He notes you can get decently far evaluating with your internal data, especially for your particular company.
AI Engineer · How to Build an AI Code Review Agent - Daksh Gupta, Greptile
Recommendation · MoneyIdo Salomon recommends the software-factory pattern: give an agent a general sense of what you want, and it spawns an orchestrator, breaks the work down, and runs it all in a local container. Because everything runs in isolation, he says you don't need to babysit the work.
AI Engineer · We're the bottleneck, but we don't have to be — Ido Salomon, MCP Apps
Recommendation · MoneyKevin Hou endorses using sidecar processes to let the model listen to the outside world and set up its own triggers, hooking them to SMS messages, webhooks, cronjobs, or GitHub PRs. He also endorses using scheduled task crons in Antigravity for time-based automation.
AI Engineer · Get Out of the Model's Way — Kevin Hou, Google Antigravity
Recommendation · MoneyNoyan recommends scoping agents to a task they're good at rather than having one agent do 10 different things: narrow scoping makes agents easy to measure and easy to lifecycle-manage, and keeping things measurable is really important when designing agents. Every agent is versioned, so you can push a new version to add capabilities in small increments. Making a new agent that is a union of existing agents' functionality often ends up with a lot of tech debt and works poorly, and if you bloat an agent some functionality gets better while some gets worse and you can't easily tweak it. Going forward, the firm encourages people to leverage their agent gateway rather than building one agent with many functions.
hedged
AI Engineer · How a Trading Firm Ships New AI Models the Same Day - Noyan Tokgozoglu, Optiver