The Tech Trek

What if the best people on your investing team are still in college? Peter Harris, Partner at University Growth Fund, breaks down how they run a roughly 100 million dollar venture fund with 50 to 60 students doing real diligence, real founder calls, and real deal work.You will hear how their student led model stays disciplined with checks and balances, why repeat games matter in venture and in business, and how this approach creates a flywheel that helps founders, investors, and the next generation of operators win together.Key Takeaways• Student led does not mean unstructured, the process is built around clear stages, data room access, investment memos, student votes, and an advisory style investment committee, with final fiduciary responsibility held by the partners• Real autonomy is the unlock, when interns are trusted with meaningful work, the best ones level up fast and start leading teams, not just supporting them• The goal is win win win outcomes, founders get capital plus a high effort support network, investors get disciplined underwriting, students get experience that compounds into career leverage• Repeat games beat short term incentives, the alumni network becomes a long term advantage, bringing the fund into high quality opportunities years later• Mistakes are inevitable, the difference is containment and systems, avoiding errors big enough to break trust, then building process improvements so they do not repeatTimestamped Highlights00:32 A 100 million dollar fund powered by 50 to 60 students, and what empowered really means01:43 The decision path, from founder screen to student memo to student vote to the advisory investment committee06:44 Why most venture internships underdeliver, and how longer tenures change outcomes10:37 Repeat games and the trust flywheel, how former students now pull the fund into top tier deals13:55 What happens when something goes wrong, damage control, learning loops, and confidentiality as a core discipline24:39 The bigger vision, expanding beyond venture into additional asset classes to create more student opportunitiesA line worth stealingIf you give people real autonomy, they’ll surprise you with what they do.Pro Tips• If you are building an internship program, start by deciding what real ownership means, then build guardrails around it, not the other way around• Treat trust like an asset, design your process so every stakeholder wants to work with you againCall to ActionIf you enjoyed this one, follow The Tech Trek and share it with a founder, operator, or student who cares about building real advantage through talent and process.

Yulun Wang, executive chairman and co founder at Sovato Health, joins Amir Bormand to unpack the next wave after telemedicine, procedural care at a distance. If you have ever wondered what it would take for a top surgeon to operate without being in the same room, this conversation gets practical fast, from the real bottlenecks inside operating rooms to the health system changes required to make remote robotics mainstream.Key takeaways• Better care can actually cost less when the right expertise reaches the right patient at the right time• Telemedicine is already normalized, which sets the stage for faster adoption of remote procedures once infrastructure and workflows catch up• Surgical robots already have two sides, the surgeon console and the patient side, today connected by a short cable, the leap is making that connection work reliably across hundreds or thousands of miles• Volume drives proficiency, the outcomes gap between high volume specialists and low volume settings is one of the biggest reasons access matters• Operating rooms spend more than half their time on steps around surgery, which creates room to dramatically increase surgeon throughput when workflows are redesignedTimestamped highlights• 00:42 What Sovato Health is building, bringing procedural expertise to patients without requiring travel• 02:10 The early days of surgical robotics and the transatlantic gallbladder surgery on September 7, 2001• 05:30 The counterintuitive idea, higher quality care can reduce total cost in healthcare• 10:27 What actually changes for patients, local hospitals stay the destination, expertise becomes the thing that travels• 14:57 Why repetition matters, the first question patients ask is still the right one• 17:53 Inside the operating room schedule, where time is really spent and why productivity can jumpA line that sticks“Healthcare is different, higher quality, if done right, costs less.”Practical angles you can steal• If you are building in regulated industries, adoption is rarely about the tech alone, it is about trust, workflows, and incentives• If you sell into health systems, position the value around system level outcomes, access, quality, and margin improvement, not just novelty• If you are designing new workflows, look for the hidden capacity, the biggest gains often sit outside the core taskCall to actionIf you want more conversations like this at the intersection of tech, systems, and real world impact, follow The Tech Trek on Apple Podcasts and Spotify.

Moiz Kohari, VP of Enterprise AI and Data Intelligence at DDN, breaks down what it actually takes to get AI into production and keep it there. If your org is stuck in pilot mode, this conversation will help you spot the real blockers, from trust and hallucinations to data architecture and GPU bottlenecks.Key takeaways• GenAI success in the enterprise is less about the demo and more about trust, accuracy, and knowing when the system should say “I don’t know.”• “Operationalizing” usually fails at the handoff, when humans stay permanently in the loop and the business never captures the full benefit.• Data architecture is the multiplier. If your data is siloed, slow, or hard to access safely, your AI roadmap stalls, no matter how good your models are.• GPU spend is only worth it if your pipelines can feed the GPUs fast enough. A lot of teams are IO bound, so utilization stays low and budgets get burned.• The real win is better decisions, faster. Moving from end of day batch thinking to intraday intelligence can change risk, margin, and response time in major ways.Timestamped highlights00:35 What DDN does, and why data velocity matters when GPUs are the pricey line item02:12 AI vs GenAI in the enterprise, and why “taking the human out” is where value shows up08:43 Hallucinations, trust, and why “always answering” creates real production risk12:00 What teams do with the speed gains, and why faster delivery shifts you toward harder problems12:58 From hours to minutes, how GPU acceleration changes intraday risk and decision making in finance20:16 Data architecture choices, POSIX vs object storage, and why your IO layer can make or break AI readinessA line worth stealing“Speed is great, but trust is the frontier. If your system can’t admit what it doesn’t know, production is where the project stops.”Pro tips you can apply this week• Pick one workflow where the output can be checked quickly, then design the path from pilot to production up front, including who approves what and how exceptions get handled.• Audit your bottleneck before you buy more compute. If your GPUs are waiting on data, fix storage, networking, and pipeline throughput first.• Build “confidence behavior” into the system. Decide when it should answer, when it should cite, and when it should escalate to a human.Call to actionIf you got value from this one, follow the show and turn on notifications so you do not miss the next episode.

New leaders face a choice fast. Do you adapt to the organization you inherit, or reshape it around the way you lead?In this conversation, Amir sits down with Gian Perrone, engineering leader at Nav, to unpack how org design really works in the first 30 to 120 days, and how to drive change without spiking anxiety or losing trust.You will hear how Gian treats leadership as triage, why “listen and learn” is rarely passive, and what separates a thoughtful reorg from one that feels chaotic.Key takeawaysLeaders almost always arrive with hypotheses, the real work is testing them without rushing to force a playbookA reorg is not automatically bad, perception turns negative when the why is unclear and people feel unsafeOver communicating helps, but thinking out loud too often can create noise, a structured comms plan keeps change steadyA simple way to spot a collaborative culture is to disagree in the interview and see how they respondManagers are the front line in change, set clear expectations so teams hear a consistent story about what is changing and whyTimestamped highlights00:01 What Nav does, and the real question behind org design for new leaders01:59 Why “first 90 days” is usually triage, not passive observation04:14 The reorg stopwatch, and why structure reflects your worldview08:36 How to communicate change without destabilizing teams12:54 A practical interview move to test whether a company truly collaborates17:03 The manager layer, how Gian sets expectations so change lands wellA line worth repeating“If you arrive and something is on fire, you are going to fix it.”A few practical moves worth stealingWhen you are new, write down your hypotheses early, then use real signals to confirm or kill themFloat a change as a real idea first, gather feedback, then come back with details before you finalizeCreate a simple comms map of who hears what, when, and from whom, then follow itBe matter of fact about changes, teams often mirror the tone you setCall to actionIf this episode helped you think more clearly about leadership and org design, follow the show and share it with one operator who is navigating change right now.

Nir Soudry, Head of R&D at 7AI, breaks down how teams can move from early experimentation to real production work fast, without shipping chaos. If you are building AI features or agent workflows, this conversation is a practical look at speed, safety, and what it actually takes to earn customer trust.Nir shares how 7AI ships in tight loops with a real customer in mind, why pushing decisions closer to the engineers removes bottlenecks, and how guardrails and evaluation keep fast releases from turning into security risks. You will also hear a grounded take on human plus AI collaboration, and why “just hook up an LLM” falls apart at scale.Key takeaways• Speed starts with focus, pick one customer and ship something usable in two or three weeks, then iterate every couple of weeks based on real feedback• If you want velocity, remove the meeting chain, get engineers in the room with customers and push decisions downstream• Agent workflows are not automatically testable, you need scoped blast radius, strong input and output guardrails, and an evaluation plan that matches real production complexity• “LLM as a judge” helps, but it is not magic, you still need humans reviewing, labeling, and tuning, especially once you have multi step workflows• In security, trust is earned through side by side proof, run a real pilot against human outcomes, measure accuracy and thoroughness, then improve with tight feedback loopsTimestamped highlights00:28 What 7AI is building, security alert fatigue, and why minutes matter02:03 A fast shipping cadence, one customer, quick prototypes, rapid iterations03:51 The velocity playbook, engineers plus sales in the same meetings, fewer bottlenecks08:08 Shipping agents safely, blast radius, guardrails, and why testing is still hard14:37 Human plus AI in practice, how ideas become working agents with review and monitoring18:04 Why early AI adoption works for some customers, and how pilots build confidence24:12 The startup reality, faster execution, traction, and why hiring still mattersA line worth sharing“When it’s wrong, click a button, and next time it will be better.”Pro tips you can steal• Run a two to four week pilot with one real customer and ship weekly, the goal is learning speed, not perfect coverage• Put engineers directly in customer conversations, keep leadership focused on unblocking, not gatekeeping• Treat every agent like a product surface, define strict inputs and outputs, sanitize both, and limit what it can affect• Build evaluation around real workflows, not single prompts, and combine automated checks with human review• Add feedback buttons everywhere, route feedback to both model improvement and the team that tunes production behaviorCall to actionIf you want more conversations like this on building real tech that ships, follow and subscribe to The Tech Trek.