Invest Like The Best · Published 2026-09-28

Inside the Personal AI Assistant Growing 10% a Day | Instinct Founder

Open on YouTube ↗

Summary

Overview

  • Speaker: Noah Shinn and Patrick O'Shaughnessy
  • Channel: Invest Like The Best
  • Main topic: Building Instinct, a personal AI assistant growing rapidly through unique interface design and trust networks.
  • Purpose: To explore the product architecture, user psychology, growth dynamics, and strategic vision behind Instinct, a next-generation personal AI assistant. Noah Shinn, founder of Instinct, discusses building a personal AI assistant that operates through simple interfaces like text and voice, scaling rapidly at 10% day-over-day growth. The conversation covers the product's philosophy of acting as a proactive proxy for users, trust networks, economic models, and the future of human-computer interaction in an AI-native world.

Topic Map

Introduction to Instinct and Growth Dynamics

  • Explanation: Introduction of Noah Shinn and Instinct, detailing its 10% day-over-day growth and positioning as a personal assistant.
  • Key claims:
    • Instinct is growing at roughly 10% day-over-day.
    • The company focuses on building a personal assistant without a traditional app interface.
    • Growth is driven entirely by word-of-mouth through an invite-only model.
  • Examples:
    • Users receive five invites to share with trusted contacts, leading to viral compounding loops.
  • Terminology:
    • Instinct
    • personal assistant
    • invite-only
  • Why it matters: Demonstrates rapid viral adoption of an AI consumer product without paid marketing spend.

Interface Philosophy and Everyday Intelligence

  • Explanation: Discussion on why Instinct avoids a heavy app interface in favor of text, voice, and proactive agentic behavior.
  • Key claims:
    • Instinct is not a new app or tool, but a new experience combining a phone and computer interface.
    • The AI acts proactively rather than just responding to prompts.
    • Simplifying the user experience reduces friction to zero.
  • Examples:
    • Instinct calling a user to remind them of a pressing document deadline before 3 PM.
    • Scanning entire wardrobes and calendars to plan outfits and schedules autonomously.
  • Terminology:
    • everyday intelligence
    • proactive behavior
    • zero friction
  • Why it matters: Shifts software interaction from reactive tool usage to proactive, agent-driven assistance.

Trusted Person Networks and Social Dynamics

  • Explanation: How Instinct coordinates between users through trusted social graphs while preserving privacy and safety.
  • Key claims:
    • Users only connect with trusted people to share calendars, emails, and preferences.
    • Trust networks enable seamless multi-user scheduling and coordination.
    • Violating trust within the network has direct relationship implications.
  • Examples:
    • Instinct coordinating a dinner party or ride-sharing across six friends by negotiating optimal schedules and routes.
  • Terminology:
    • trusted person network
    • social dynamics
    • access control
  • Why it matters: Extends AI utility from single-player productivity to multi-player social and professional coordination.

Business Models and Monetization

  • Explanation: Examining the capital-intensive nature of personal AI assistants and potential monetization strategies.
  • Key claims:
    • Traditional consumer internet businesses rely on ads, which incentivize capturing user attention.
    • Instinct aligns with user intent rather than maximizing screen time.
    • Capital intensity requires careful consideration of compute costs and unit economics.
  • Examples:
    • Comparing take-rates in travel and restaurant booking against traditional aggregators like Expedia or OpenTable.
  • Terminology:
    • take-rate
    • unit economics
    • compute inference cost
  • Why it matters: Highlights the economic challenges and alignment differences between AI agents and ad-supported platforms.

Security, Trust, and the Future of Software

  • Explanation: Addressing the challenges of data privacy, safety, and the eventual collapse of traditional software interfaces.
  • Key claims:
    • Building trust takes weeks, but retention remains high (80% retention when sensitive info is shared).
    • AI agents will eventually replace legacy software applications as the primary interface.
    • Proactivity requires rigorous safety firewalls and oversight.
  • Examples:
    • 40% of users share personal credit card information with Instinct within three weeks.
  • Terminology:
    • retention rate
    • firewall
    • inference cost
  • Why it matters: Establishes trust as the core moat and technical bottleneck for autonomous personal agents.

Key Points

Proactive vs. Reactive AI

  • Explanation: True personal assistants must anticipate needs and act proactively without requiring constant prompting from the user.
  • Evidence: Instinct calling users with urgent deadlines or booking travel itineraries automatically based on inferred preferences.
  • Practical implication: Product design must shift from chatbot prompt interfaces to ambient, autonomous background execution.

Trust as a Compounding Moat

  • Explanation: Sharing sensitive data like credit cards and calendars builds high retention and trust over a multi-week period.
  • Evidence: 80% retention rate for users who share at least one sensitive piece of information with Instinct.
  • Practical implication: Early product onboarding must prioritize security, data control, and gradual trust-building.

Multi-Player AI Coordination

  • Explanation: AI agents communicating with other users' AI agents eliminates friction in scheduling, planning, and commerce.
  • Evidence: Coordinating rideshares, dinner bookings, and meetings across groups of friends automatically.
  • Practical implication: Network effects emerge when AI agents transact and coordinate on behalf of multiple users.

Frameworks, Models & Processes

Trust-Based Scaling Framework

  • How it works: Gradually expanding AI autonomy as the user shares sensitive data and establishes trust over time.
  • Components:
    • Frictionless onboarding
    • Granular access controls
    • Proactive background execution
    • High retention through personal context
  • When to use: Building personal AI agents that handle sensitive financial, scheduling, and personal data.

Examples & Case Studies

An Instinct user needed to coordinate a ride for six friends after a dinner party.

  • Illustrates: Multi-player AI coordination and route optimization.
  • Lesson: AI agents interacting with each other reduce social coordination friction to near zero.

Instinct users scanning their entire wardrobes and bodies to plan weekly outfits.

  • Illustrates: High-intent consumer use cases for proactive AI agents.
  • Lesson: Consumers willingly share sensitive data when the utility and time savings are extreme.

Actionable Takeaways

  • Immediate:
    • Focus on understandability and predictability rather than raw capability in AI agent design.
    • Design invite-only distribution loops to manage compute scaling and viral growth.
  • Strategic:
    • The future of software is agent-native, where traditional apps disappear behind conversational and proactive interfaces.
    • Alignment with user intent creates a superior business model compared to ad-driven attention economies.
  • Questions to investigate:
    • How will compute inference costs scale relative to user growth for autonomous agents?
    • What new security paradigms are required as AI agents gain full access to personal financial accounts?

Claims Worth Verifying

  • Instinct is growing at 10% day-over-day. (metric)
  • 40% of users share personal credit card information within three weeks. (metric)
  • There is an 80% retention rate for users who share sensitive information. (metric)

Notable Quotes

"This is probably the most exciting software race ever." (at 0:31) "We're not focused on capability, we're only focused on understandability." (at 82:15)

Compressed Summary

  • Instinct is a personal AI assistant growing at 10% day-over-day via invite-only loops.
  • The product emphasizes proactivity and zero-friction interfaces over traditional app menus.
  • Trust and data security are the primary moats, driving an 80% retention rate among active users.
  • Multi-player AI coordination allows agents to interact with other agents to solve complex scheduling tasks.
  • Keywords: artificial intelligence, personal assistant, agentic workflow, trust network, software interface
  • Core insight: The future of software is shifting from reactive applications to proactive, trusted personal AI agents that coordinate seamlessly across human networks.

Core insights

7
Architecturehigh noveltymoderate evidence

Autonomy in a personal agent should be a graduated permission tier that expands as the user shares sensitive data and trust accrues over weeks, not a static capability flag set at onboarding.

Why it matters

It reframes the agent's capability surface as a per-user, evolving state that the runtime must track, gate, expose, and potentially revoke — a first-class system concern rather than a config value.

Generalization

Any agent operating on a user's behalf with real-world side effects needs an observable, monotonic-by-default trust/autonomy state machine coupled to permission grants, with explicit revoke paths.

Gradually expanding AI autonomy as the user shares sensitive data and establishes trust over time.
Open source video
Frictionless onboarding
Open source video
Granular access controls
Open source video
Building trust takes weeks, but retention remains high
Open source video
Architecturemedium noveltymoderate evidence

Proactivity inverts the agent's control flow from request-response to ambient background execution, and the summary couples it directly to a separate safety-firewall layer as a prerequisite rather than an add-on.

Why it matters

Background-triggered actions (e.g., placing a call about a deadline) execute without a synchronous human approval step, so the safety/oversight layer must be a pre-execution gate on a different code path than a chat turn.

Generalization

Designing a proactive agent requires a distinct execution loop (triggers, scheduling, idempotency, rate limits) plus a policy firewall that evaluates intended actions before any side effect, since there is no user prompt to intercept.

The AI acts proactively rather than just responding to prompts.
Open source video
Proactivity requires rigorous safety firewalls and oversight.
Open source video
Product design must shift from chatbot prompt interfaces to ambient, autonomous background execution.
Open source video
Architecturehigh noveltyweak evidence

Agent-to-agent coordination across different users' trust graphs (negotiating schedules, routes, bookings among a friend group) is framed as the source of network effects, meaning the agent must communicate with agents it does not own.

Why it matters

It forces a cross-tenant negotiation interface with identity, consent, and shared-state semantics that no single-user agent harness provides today.

Generalization

Multi-player agent value emerges only when agents can transact with other principals' agents under mutually verifiable trust and consent, which requires a negotiation protocol rather than a shared tool registry.

AI agents interacting with each other reduce social coordination friction to near zero.
Open source video
Coordinating rideshares, dinner bookings, and meetings across groups of friends automatically.
Open source video
Practicemedium noveltymoderate evidence

The stated design priority is understandability and predictability of agent behavior over raw capability.

Why it matters

Directly contradicts the default benchmark-maximization instinct: a proactive agent that does the unexpected is a liability, so predictability is a product and safety requirement, not a UX nicety.

Generalization

For agents with side-effect authority, optimize for behavioral predictability and specification adherence before capability; capability gains that reduce predictability have negative marginal value.

Focus on understandability and predictability rather than raw capability in AI agent design.
Open source video
Mechanismmedium noveltymoderate evidence

Invite-only distribution (five invites per user) is used as a deliberate mechanism to couples viral growth to compute-cost control, per the actionable takeaway framing it as managing 'compute scaling and viral growth' together.

Why it matters

Turns a growth tactic into an inference-cost throttling primitive, since a capital-intensive proactive agent cannot absorb unconstrained signup-driven compute.

Generalization

For compute-bound agent products, growth loops should be quota-coupled (invites, seats, rate limits) so demand expansion is bounded by unit-economics headroom.

Users receive five invites to share with trusted contacts, leading to viral compounding loops.
Open source video
Design invite-only distribution loops to manage compute scaling and viral growth.
Open source video
Instinct is growing at roughly 10% day-over-day.
Open source video
Empirical Resultmedium noveltymoderate evidence

Sharing a single sensitive artifact (calendar, credit card) correlates with very high retention, and 40% of users hand over credit card data within three weeks; the summary presents this as the trust moat and the reason retention is high.

Why it matters

Suggests the decisive onboarding milestone is the first sensitive-data grant, which is also the biggest risk event — onboarding should be engineered around that transition.

Generalization

If retention is driven by data/context depth rather than feature usage, instrumentation should treat the first high-trust permission grant as the primary activation metric.

80% retention rate for users who share at least one sensitive piece of information with Instinct.
Open source video
40% of users share personal credit card information with Instinct within three weeks.
Open source video
Mental Modelmedium noveltymoderate evidence

A personal agent aligned with user intent cannot monetize via attention, so the summary points to take-rate monetization on transactions (travel, restaurant booking) as the alternative to ad-supported aggregator models.

Why it matters

Monetization mechanism constrains agent design: take-rate requires the agent to actually complete transactions (execution authority), whereas ads only require engagement.

Generalization

An agent's incentive model determines how much execution autonomy it needs — aligning incentives with user intent pushes the architecture toward real transaction execution and richer unit-economics modeling.

Traditional consumer internet businesses rely on ads, which incentivize capturing user attention.
Open source video
Instinct aligns with user intent rather than maximizing screen time.
Open source video
Comparing take-rates in travel and restaurant booking against traditional aggregators like Expedia or OpenTable.
Open source video

Deep dives

4

Pre-execution safety firewall for proactive agents

Research question

What architecture and policy language for a pre-execution safety firewall minimizes harmful proactive actions while limiting utility loss from false-positive blocks?

Why

Proactive agents execute side effects without a synchronous user prompt, so the safety layer must be a distinct pre-execution gate on the background path; getting it wrong risks real-world harm and relationship damage in trust networks.

Proactivity requires rigorous safety firewalls and oversight.
Open source video
The AI acts proactively rather than just responding to prompts.
Open source video
Source video

Trust-state machine for graduated agent autonomy

Research question

What observable signals should gate each escalation of agent autonomy, and how should escalation be reversed or throttled?

Why

Autonomy is per-user, evolving state that must be tracked, gated, and revocable; without a formal trust-state machine, permissioning becomes ad-hoc config and cannot support safe escalation or audit.

Gradually expanding AI autonomy as the user shares sensitive data and establishes trust over time.
Open source video
Building trust takes weeks, but retention remains high
Open source video
Source video

Inter-agent negotiation protocol for cross-tenant coordination

Research question

How can agents from different users authenticate each other and propagate scoped consent during cross-graph coordination, and what dispute-handling mechanisms are required?

Why

Multi-player agent value emerges only when agents can transact across trust graphs under mutual consent; this requires identity, consent, and negotiation semantics that no single-user harness provides, and is the source of network effects.

AI agents interacting with each other reduce social coordination friction to near zero.
Open source video
Coordinating rideshares, dinner bookings, and meetings across groups of friends automatically.
Open source video
Source video

Unit economics of always-on proactive agents

Research question

What is the cost per proactive action versus the realized value, and what is the sustainable autonomy ceiling under take-rate monetization?

Why

Capital-intensive inference makes unbounded proactivity dangerous; without instrumentation of inference spend per active user and modeling against take-rate revenue, product decisions on autonomy and growth are ungrounded.

Capital intensity requires careful consideration of compute costs and unit economics.
Open source video
Design invite-only distribution loops to manage compute scaling and viral growth.
Open source video
Source video

Article ideas

4

Why Predictability Beats Capability in Proactive AI Agents

For agents with real-world side effects, optimizing for behavioral predictability is a safety and product requirement, not a nice-to-have; capability gains that reduce predictability have negative marginal value.

Angle

Contrarian: challenges the benchmark-maximization instinct in agent development by arguing that understandability and specification adherence should be prioritized over raw capability when agents have execution authority.

Source video

Invite-Only Is a Compute Throttle, Not Just a Growth Hack

In capital-intensive AI agent products, invite gating couples viral growth to inference cost control, and should be designed as a quota-coupled demand throttle rather than a pure growth tactic.

Angle

Systems-level: reframes a common growth tactic as an infrastructure cost-management primitive, with implications for quota design and unit-economics-aware growth loops.

Source video

The First Sensitive-Data Grant Is Your Real Activation Metric

If retention is driven by data/context depth, onboarding should be engineered around the first high-trust permission grant, and instrumentation should treat it as the primary activation event.

Angle

Data-driven: shifts the activation metric from feature usage to a single trust milestone, with implications for onboarding UX, instrumentation, and risk management.

Source video

Agents That Talk to Agents: The Missing Multi-Player Protocol

Multi-player agent value emerges only when agents can transact under mutually verifiable trust and consent, requiring a cross-tenant negotiation protocol that no single-user harness provides.

Angle

Protocol design: argues that the next wave of agent utility is cross-principal coordination, and outlines the missing identity, consent, and dispute-handling components.

Source video

Project ideas

4

Trust-State Machine for Agent Autonomy

gatehouse

A per-user trust-state machine that escalates autonomy based on observable signals (data grants, correction rate, action success) and supports revocation will increase user trust and retention compared to static permission models.

Proof of concept

Implement a runtime that tracks a trust level per user and gates agent actions accordingly; simulate user interactions with escalating data sharing and measure the machine's ability to escalate and revoke.

Measurement

Compare retention and user-reported trust in an A/B test against a static permission model; track escalation/revocation events and their correlation with retention.

Source video

Pre-Execution Policy Firewall for Proactive Agents

gatehouse

A pre-execution policy layer with action classification reduces harmful proactive actions by >50% with <10% utility loss on benchmark tasks.

Proof of concept

Build a policy engine that evaluates intended actions before execution, using a classifier and rules for action categorization; test on a set of proactive tasks with known harmful/benign labels.

Measurement

Precision/recall of block/allow decisions and utility loss (task success rate) on the proactive task suite.

Source video

Inter-Agent Negotiation Protocol for Cross-User Coordination

new

A negotiation protocol with verifiable identity and scoped consent tokens enables agents to coordinate group scheduling without central authority, reducing coordination time by >80% vs a human baseline.

Proof of concept

Implement a minimal protocol for two agents to negotiate a meeting time under consent constraints; extend to three agents for a group event.

Measurement

Time to consensus, number of messages exchanged, and user satisfaction compared to human-mediated coordination in a controlled experiment.

Source video

Compute-Aware Invite Gating System

new

Coupling invite quotas to real-time inference cost per user bounds monthly compute spend within a target budget while maintaining viral growth rate.

Proof of concept

Simulate an invite-only system with dynamic quota based on a cost threshold; model growth and compute spend under different quota policies.

Measurement

Monthly compute cost per user and growth rate compared to fixed quotas; sensitivity analysis to cost variability.

Source video

Architectural implications

4

Autonomy is described as something that grows with trust rather than being set once.

Before

Permissions/capabilities configured statically at install or signup.

After

Per-user autonomy level tracked as runtime state, escalating as sensitive-data grants and trust accrue, with per-action gating.

Consequence

Requires persistent trust-state, per-action policy evaluation, revocation, and auditability — the permission layer becomes a core subsystem, not config.

Source video

Proactive actions occur with no user prompt in the loop.

Before

Chat turn: user prompt → model → response, with human review implicit in the interaction.

After

Ambient trigger → planned action → policy firewall → side effect, with the human possibly absent entirely.

Consequence

Safety checks must move to pre-execution on the background path; failure modes shift from bad answers to bad real-world actions, raising the bar for idempotency, rate limiting, and rollback.

Source video

Agents coordinate across multiple users' trust graphs.

Before

Single-principal agent with its own tool registry and memory.

After

Inter-agent (cross-tenant) negotiation over shared scheduling/booking state under mutual consent.

Consequence

Introduces cross-principal identity, consent propagation, and dispute-handling concerns that single-user harnesses do not address; also creates the network-effect moat.

Source video

Legacy app surfaces are expected to disappear behind conversational/proactive agents.

Before

Human picks an app to accomplish a task; UI is the integration point.

After

Agent is the primary interface and selects/invokes backend services on the user's behalf.

Consequence

Integration and permission boundaries move from UI apps to agent capabilities, shifting where access control, rate limiting, and observability must live.

Source video

Tradeoffs and failure modes

5

Proactivity vs. trust and safety

Benefit

Zero-friction, anticipatory assistance (e.g., calling before a deadline, autonomous travel booking).

Cost or risk

Autonomous side effects without a prompt can be wrong or harmful, which is precisely why the summary requires safety firewalls; a single bad proactive action in a trust network has relationship-level consequences.

Proactivity requires rigorous safety firewalls and oversight.
Open source video
Source video

Rapid growth vs. compute cost

Benefit

~10% day-over-day viral growth from word-of-mouth with no paid marketing.

Cost or risk

Capital-intensive inference costs make unbounded demand dangerous; the summary ties invite-only design explicitly to compute scaling.

Capital intensity requires careful consideration of compute costs and unit economics.
Open source video
Source video

Sensitive-data collection vs. privacy risk

Benefit

High retention (80%) among users who share sensitive info; deep context enables better assistance.

Cost or risk

Sharing credit cards, emails, and calendars concentrates high-value data, making the agent a high-severity target and the trust relationship fragile; the summary notes violation carries direct relational consequences.

40% of users share personal credit card information with Instinct within three weeks.
Open source video
Source video

Intent alignment vs. monetization

Benefit

Avoids attention-capture incentives and aligns with user intent.

Cost or risk

Removes the ad revenue model, forcing reliance on take-rates whose economics are unproven against incumbents like Expedia and OpenTable.

Instinct aligns with user intent rather than maximizing screen time.
Open source video
Source video

Invite-only gating vs. growth ceiling

Benefit

Controls compute load and preserves a curated, high-trust network.

Cost or risk

Deliberately caps distribution and slows addressable-market expansion; requires the invite loop to actually compound to justify the constraint.

Users receive five invites to share with trusted contacts, leading to viral compounding loops.
Open source video
Source video

Open questions

5

What signals actually gate each escalation of agent autonomy, and how is escalation reversed or throttled?

Why unresolved

The summary describes a 'trust-based scaling framework' with components (onboarding, access controls, proactive execution) but no mechanism for measuring trust or revoking autonomy.

Research direction

Prototype a trust-state machine with observable triggers (data grants, correction rate, action success) and test revocation/recovery behavior.

Source video

How do agents from different users authenticate each other and propagate consent during cross-graph coordination?

Why unresolved

The summary asserts multi-player coordination and network effects but does not describe identity, consent, or conflict-resolution semantics between principals.

Research direction

Design and evaluate an inter-agent negotiation protocol with verifiable identity, scoped consent tokens, and dispute handling across user boundaries.

Source video

What does a safety firewall for proactive, side-effecting agent actions look like in practice, and how does it trade off utility against false-positive blocks?

Why unresolved

The summary states firewalls are required but gives no architecture, policy language, or empirical data on their precision.

Research direction

Build a pre-execution policy layer with action classification and measure block/allow accuracy and utility loss on proactive tasks.

Source video

What is the cost per proactive action versus the realized value, i.e., the true unit economics of an always-on agent?

Why unresolved

The summary names capital intensity and inference cost as concerns and mentions take-rates, but provides no numbers on inference cost or margin.

Research direction

Instrument proactive inference spend per active user and model take-rate revenue against it to find the sustainable autonomy ceiling.

Source video

Is the 80% retention driven causally by sensitive-data sharing (trust deepening), or is it selection bias from already-committed users?

Why unresolved

The summary reports a correlation between sensitive-data sharing and retention without a causal design or control group.

Research direction

Run a cohort/ablation study isolating onboarding steps that prompt sensitive grants and measure retention deltas.

Source video

Key claims

8
factualVerification needed

Instinct is growing roughly 10% day-over-day, driven by word-of-mouth in an invite-only model.

Evidence

Instinct is growing at roughly 10% day-over-day.

Question

Is the 10% day-over-day figure sustained over a meaningful period or a short spike, and what is the denominator (users, revenue, sessions)?

Source video
causalVerification needed

Proactivity in personal agents requires rigorous safety firewalls and oversight.

Evidence

Proactivity requires rigorous safety firewalls and oversight.

Question

Does adding a pre-execution safety layer measurably reduce harmful proactive actions without unacceptable utility loss?

Source video
factualVerification needed

Users who share at least one sensitive piece of information with Instinct retain at 80%.

Evidence

80% retention rate for users who share at least one sensitive piece of information with Instinct.

Question

Is sensitive-data sharing causally responsible for retention, or does it merely correlate with pre-existing commitment?

Source video
factualVerification needed

40% of Instinct users share personal credit card information within three weeks.

Evidence

40% of users share personal credit card information with Instinct within three weeks.

Question

How is the three-week window defined and what fraction of users is the denominator?

Source video
opinionVerification not requested

Agent design should prioritize understandability and predictability over raw capability.

Evidence

Focus on understandability and predictability rather than raw capability in AI agent design.

Source video
causalVerification needed

AI agents communicating with each other reduce social coordination friction to near zero.

Evidence

AI agents interacting with each other reduce social coordination friction to near zero.

Question

What measurable coordination cost remains in agent-mediated group scheduling versus human-mediated, and where does it break down?

Source video
predictionVerification needed

AI agents will eventually replace legacy software applications as the primary interface.

Evidence

AI agents will eventually replace legacy software applications as the primary interface.

Question

What evidence distinguishes interface displacement from agents simply adding another surface over existing apps?

Source video
causalVerification needed

Invite-only distribution loops can be used to manage compute scaling alongside viral growth.

Evidence

Design invite-only distribution loops to manage compute scaling and viral growth.

Question

Does invite gating meaningfully bound inference spend per period, or is it primarily a growth/positioning tactic?

Source video

Connections

5