The pull framework is upstream of the product idea
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.
39,935 results · Most relevant
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.
Dr. Scott Forbes states creatine supplementation improves cognitive performance after sleep deprivation, and even a single dose of creatine helped preserve some cognitive function when people were sleep deprived. In rugby players who got less than three hours of sleep, passing accuracy declined — but creatine maintained passing accuracy despite poor sleep. He recommends considering creatine supplementation when you have a bad night's sleep before an important performance (e.g., athlete before competition, surgeon after a night operation), and taking creatine when traveling across time zones to offset time-delay effects on the brain. Cognitive tests used in creatine research include the MoCA test, mini mental state examination, reaction-time computerized tests for processing speed, and
Consequential creator advice requires independent verification before Today can promote it.
Hari Kumar identifies one of the biggest problems in hedge funds: an analyst works on an idea for a couple of days, it loses PM interest or something else takes precedence, and it doesn't come back for months — so the analyst misses a key price window. He recommends building agents that track all the notes an analyst has taken, even from a single day, against the market, and flash the idea as interesting again to the analyst, PM, and trader when it becomes interesting.
The hosts state that communicating a product is on-device is the most important trust message for local AI products. A founder who applied to YC with an open-source text message analyzer that read iMessages entirely locally used a hero saying 'open source, completely on device' and communicated that the internet doesn't touch the data — which they learned is what users really cared about. An 'on-device LLM' label is also a trust signal displayed on AI sites, though the host questions whether the wording is necessary.
Vague, generalized copy (e.g., 'institutional intelligence and decision infrastructure') leaves visitors unsure whether they need the product. Copy should use specific language about who should use the product and why, and give specific examples of what the product does and the problems it solves. Copy that lists claims without explaining what the product actually does fails the visitor — even after reading 'years of history, alive from day one, nothing installed, no interviews,' the reviewer still didn't know what the product does.
Isabelle Williams argues that agents should operate using an agent token with scoped access issued from your application's backend, instead of taking the user's token or an API key, so agent actions can be audited, revoked, and permission-limited. Handing an agent the user's own token breaks auditing and attribution, prevents independent revocation of the agent without impacting the user's session and access, and prevents limiting the scopes of what the agent can do.
Commercial context: The creator describes this as their own product.
Giving an agent a user's API key instead of a scoped agent token means you cannot audit, revoke, or limit the agent's permissions.
Gary Vaynerchuk advises that every episode of a live show should be post-produced into as much derivative content as possible, because failing to do so wastes content that was already created.
To test whether a model can predict a company action, run the search at a specific historical point in time (e.g., one day, seven days, and one month before an acquisition announcement) rather than live, because a live search will find the announcement and trivially predict the outcome with 100% accuracy, making the test meaningless.
To adjust how you set up a model or agent, backtest whether it could have found a known discrepancy in a generalizable way, for example by creating a set of 50 sample sets and checking performance against them, using version-controlled search to see what information existed at a prior point in time.
Rob Walling advises that if you're bootstrapping, you shouldn't compete head-on when replicating an existing idea. Instead, bring at least one differentiator: a unique focus or position (best X for Y while others chase the broad market), a unique traffic source such as ranking high in Google, or a lower price.
GaryVee advises focusing on winning over the 10% of people who can detect your intentions. When they smell that you are not actually trying to sell them anything — that you are just listening to where they're at — you completely dominate the 90% and win over the 10% who are rarely won over, making you an unstoppable salesman.
Al Chen points out that most scanning tools (Sysdig, Wiz, Prisma) only check whether a package has been bumped to a specific version and say nothing about whether the exploit is still in the application code. One solution is creating a Harbor task — like a harness or world for an agent to try things out — containing instructions for the agent, an environment with the actual Docker images, and tests to run against the agent.
endorsed
When evaluating models for RAG, Pamela Fox says to check how likely the model is to make stuff up (hallucinate) and whether it is willing to admit what it doesn't know. She also forces the model to prove every piece of information in its answer came from the provided sources, to reduce hallucination in RAG.
When evaluating a predictive system, set the snapshot date to just before the outcome was announced. Live search leaks future knowledge into an evaluation of the past, so constraining the snapshot prevents the system from being informed by the confirmation of the outcome.
Nick Nisi recommends leaning away from relying on skills alone for verification because it's up to the model whether it follows that path; instead prefer CI enforcement of the commands. Verification checks can run regularly as part of CI. Hooks are another option — though a git hook is probably the last one he'd reach for — and hooks are relevant for local development across a whole team because they can be shared. He also suggests putting an agents.md (not a claudemd) in the app with wording like 'on change, verify things by running this' or 'before you open a PR, do this'; with that in place, agents have to go out of their way to ignore or avoid the verification instructions. One could even build a full pi extension to keep verification running in the background and feed in information.
Nick Nisi recommends that if you have a web app and don't already have a custom verifier CLI, building one is one of the highest-leverage things you can start with for your codebase. He stresses that you must build tools that fit your specific application — without them the model has no way to prove correctness for your particular app — and that the tooling should produce detailed output about what happened and the state of the system so it can be audited by the application and the model.
The speakers warn that a successful screenshot is not proof: make sure it actually shows the state you expect and that the commands to reach that state actually ran, otherwise it might just be another lie. A screenshot might have taken a different path that's not actually possible within the UI or caused side effects — verify it ran start to finish.
Choose sources → to get a library of your own and a daily brief.