Recommendation · MoneyMove from a skill-based prompt approach to a separate tool when the use case becomes critical enough that the trade-offs of the non-deterministic approach are not acceptable.
endorsed advice
AI Engineer · Stop Chatting With Spreadsheets — Francesco Galletta & Felippe Felisola Caso, Monzo
Method · MoneyTo kickstart your process internally within your organization, you can either talk to the speaker or his team, or you have six questions to start asking. These are like guideline questions for you to start asking to refine your tokenomics. The questions: (1) Who, team, spend what? (2) What must you test to use a cheaper model? (3) What's your base load? (4) What's the default model for each team? (5) Which workload has a person waiting that you need something faster? (6) How much of what we generate is useful?
Method, not a verified protocol.
AI Engineer · The AI Bill Is Too Damn High: Tokenomics 101 — Eugene Cheah, Featherless AI
Recommendation · MoneyBootstrap a fine-tuned model by starting with an expensive model that can already do the task: deploy it at small scale to generate your training dataset, then distill its outputs down to a 7B-scale model and fine-tune the collected data at different model sizes to see what fits best. Fine-tune models to specialize use cases once you reach scale.
AI Engineer · The AI Bill Is Too Damn High: Tokenomics 101 — Eugene Cheah, Featherless AI
Recommendation · MoneyNacho Martinez proposes creating vector embeddings out of the tools and skills; when the agent loop needs to retrieve useful skills or tools, do a vector similarity search against the vector store, pull the most relevant skill or tool, solve the problem, then offload it again — one of the ways to keep the context window relevant.
AI Engineer · Memory-Aware Agent Harnesses for Anti-Money Laundering — Nacho Martinez, Oracle
Recommendation · MoneyNacho Martinez describes context summarization as tackling context bloat: you ask the model to generate a short summary of everything said in the context window, then start the next conversation from that summary.
Contested by Jake on Figma
AI Engineer · Memory-Aware Agent Harnesses for Anti-Money Laundering — Nacho Martinez, Oracle
Recommendation · MoneyNacho Martinez recommends skill distillation — taking previous conversations and runs with an AI agent and creating something meaningful out of them, such as a skill MD file placed into the skill box — describing it as a technique to improve a frozen model's learning over time by controlling the data layer rather than the weights.
AI Engineer · Memory-Aware Agent Harnesses for Anti-Money Laundering — Nacho Martinez, Oracle
Recommendation · MoneyNacho Martinez proposes creating vector embeddings of tools and skills, using vector similarity search against the vector store to pull the most relevant skill or tool when the agent loop needs one, and offloading it again after solving to keep the context window relevant.
AI Engineer · Memory-Aware Agent Harnesses for Anti-Money Laundering — Nacho Martinez, Oracle
Recommendation · MoneyNacho Martinez recommends context engineering techniques that automatically summarize, compact, and shrink the working context window: asking the model to generate a short summary to start the next conversation from, and compaction — storing conversation chunks in a database or file with an ID that the agent can pull from with an offset when needed.
AI Engineer · Memory-Aware Agent Harnesses for Anti-Money Laundering — Nacho Martinez, Oracle
Recommendation · MoneyNacho Martinez describes compaction as tackling context bloat: you put chunks of the conversation into a database or file with an ID, and the agent later pulls from that ID with an offset, like reading from a file.
AI Engineer · Memory-Aware Agent Harnesses for Anti-Money Laundering — Nacho Martinez, Oracle
Recommendation · MoneyAssign someone on your marketing team to monitor weekly which vendor AI agents recommend in your space, and work to stay number one. AI agent recommendations change over time, so vendor rankings in agent answers must be tracked continuously, not checked once. Don't rely on B2B apps that charge for weekly ChatGPT-ranking updates — they won't tell you what agents will pick. Ensure your product gets recommended by as many AI agents as possible, not just by chatbots like ChatGPT — agents running in tools like Replit, Lovable, and Claude Code increasingly make vendor recommendations for end users. When a human asks ChatGPT or Claude which CRM to buy, you want your product named in the top three of the answer, because that generates massive leads.
None; direct advice.
The Official SaaStr Podcast: SaaS | Founders | Investors · SaaStr 882: Claudeforce vs. Replit vs. Lovable. Who wins? (The Agents #016)
Recommendation · MoneyThe founders describe running a private Facebook group of 15,000 dads, being loyal back to the community by engaging daily, jumping into members' lives to help them through things, and staying in the group talking to people and sharing their stories themselves even 4.5 years later rather than delegating to a community manager.
described
Foundr · We Started Dad Gang with $750 and One Hat - and did $40M in 4 Years
Method · MoneyHari offers a three-question playbook for leaders who don't build: ask 'who has already done this?' — this question forces the search and tames the build-first reflex powered by AI; ask 'what do we have that the next team, our competitors, or another person in the team don't have?' — this forces novelty as a first-class citizen into the team's minds; and ask 'where will this application live?' — forcing outcome-based thinking when everyone is high on building shows the demo is the expensive way to find out. Run the four moves as your roadmap for next quarter's features — they are not side project rules.
endorsed
Method, not a verified protocol.
AI Engineer · I Spent Two Years Building the Median — Hariprasad Sudharshan
Recommendation · MoneyHarish Gaggar recommends building a centralized authentication and routing hub (MCP gateway) that securely connects any coding assistant tool or agents to endpoints via the MCP gateway and MCP server, and avoiding direct access to any endpoints: all access must go through the MCP gateway with proper authentication before reaching the MCP server and endpoints. All agent calls should flow: agent → MCP gateway for authentication → the right MCP server → API call to the endpoint → response returned.
AI Engineer · Paving the Road to Production: Governed Enterprise AI Agents — Harish Gaggar, Credit Karma
Recommendation · MoneyHarish Gaggar recommends ensuring MCP servers have the right tools to execute queries, building customized MCP servers with the right tools in place, and leveraging the FastMCP server package or wrapper to build them with different sets of tools inside the wrapper. Every tool defined in an MCP server must be fully reviewed by the internal security team so only authorized tools go to production, and filters, limits, and block fields should be enforced in MCP tools so fields not required by the LLM are blocked. In air-gapped environments, he says it is highly recommended to build your own MCP servers rather than using externally available ones.
AI Engineer · Paving the Road to Production: Governed Enterprise AI Agents — Harish Gaggar, Credit Karma
Recommendation · MoneyHarish Gaggar recommends implementing agent PII treatment because queries can accidentally ingest secrets — e.g., uploading a doc with sensitive information or typing API keys. Put protections in place so secrets do not go into the LLM, tracking, tracing, or any memory DB. Define a framework with different data types and their severity levels for PII/secret detection; if severity is above 90 percent, block and redact the secrets immediately so they never reach LLM models, and blocked secrets must not go to the memory DB, tracking and eval tables, or tracing systems either. Block sensitive data at the moment of ingestion — the moment it is typed.
AI Engineer · Paving the Road to Production: Governed Enterprise AI Agents — Harish Gaggar, Credit Karma
Recommendation · MoneyHard environmental separation could have stopped the Lemkin incident: if the agent had been executing in an isolated remote workspace without a route to production, it doesn't matter what the prompt said — the agent would have had no path to do damage. Short-lived scoped credentials could also have stopped it: the agent got access to production because it found a credential in a forgotten file that had standing write access and was long-lived. A credential that can expire on its own or only carries the scope of the task itself makes it impossible to make a delete with the equivalent of an ID badge that lets you do everything. The last important piece is having audit logging that you own, not the agent: in this case the agent was the one writing its own record of its actions, which is how
AI Engineer · Your AI Isn’t the Problem. Your Infrastructure Is. — Jiachen Jiang, Coder
Recommendation · MoneyPaden Gayle recommends starting with the least authority that solves the problem, then asking what tasks can be proven with evidence to grant the system more; granting more authority than the problem requires creates uncontrolled operational risk.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends asking 'Who owns the source?', 'Who can grant access?', and 'Who can approve using this in the workflow?' when confirming data ownership, and warns that building AI infrastructure without understanding which datasets can be used and who can approve that use leads to deployment failure.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle warns that building an AI system without a credible path of approval means it will not ship regardless of technical quality; the MVP should be built with that approval path in mind.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyUse policies and criteria to decide when it is appropriate to approve changes: auto-approve dependency bumps, documentation changes, non-breaking security patches, and lower-risk internal tooling changes; add custom approval-gating rules written in plain English; but require a human approver on top for changes touching sensitive areas like payments or auth.
AI Engineer · Rebuilding CI for AI-Scale Commit Volume — Gautam Korlam, Sonar