ExpertsFM

Instinct AI: The AI Assistant for normal people

The Startup Ideas Podcast · September 15, 2026

5 Selected Lessons:

heuristic · 3 case · 1 framework · 1
Agent-to-agent trusted networks as agentic-era network effects
framework based on: reasoning Remy and Greg

Source

The Startup Ideas Podcast — Instinct AI: The AI Assistant for normal people (September 15, 2026) · at 5:37 ▸

When this applies

when designing a platform where autonomous actors (agents, bots, representatives) need to coordinate with other users' autonomous actors to accomplish tasks

The takeaway

In products built around autonomous agents acting on users' behalf, enabling agent-to-agent coordination (rather than just agent-to-tool) can create defensible network effects.

Why it works

Allowing a user's agent to communicate with other trusted users' agents on an allow-list creates value that increases with the number of connected agents, replicating classic network effects but at the agent-coordination layer rather than the human-user layer.

One level up

As product paradigms shift (e.g., from human-to-human apps to agent-mediated apps), network effects must be re-invented at the new coordination layer, not assumed to transfer automatically.

Where it stops holding

This stops working when the agent network stays closed and fails to reach critical mass, or if competitors create interoperable open standards that bypass the closed network advantage.

Detail

procedure:
  • Let users add other trusted users' agents to an allow-list
  • Enable direct agent-to-agent communication for coordination
  • Capture market share early while the coordination layer is new, before competitors replicate it
  • Decide whether to keep the network closed (proprietary moat) or open it to interoperate with rival agents
benchmarks: {}
rationale: Agent-to-agent coordination mirrors historical network effects (more users = more value) but applied to a new agentic layer, which the hosts flag as a potential moat question for venture-backed AI startups generally.

In their words

When you read the tweet, it makes so much sense.
Segment your agent stack by task type (personal vs. professional)
heuristic based on: lived experience Remy

Source

The Startup Ideas Podcast — Instinct AI: The AI Assistant for normal people (September 15, 2026) · at 8:57 ▸

When this applies

when selecting among multiple specialized tools rather than forcing one tool to do everything

The takeaway

When several specialized tools exist, route tasks to the tool purpose-built for that category rather than forcing a single generalist tool to cover all needs.

Why it works

Tools optimized for a narrow use case (e.g., mass-market personal tasks) outperform general-purpose power tools on that narrow use case, so routing tasks to the best-fit tool beats using one tool for everything.

One level up

Specialization within a toolkit (best tool per job) often beats consolidation onto one generalist tool, especially as tools mature.

Where it stops holding

This stops working when switching between multiple tools creates enough friction/context-loss to outweigh each tool's specialization benefit, or when one tool becomes genuinely general-purpose-excellent.

Detail

rule: Use specialized agent tools for their best-fit domain: business/coding agents for work, personal-assistant agents for errands/bookings.
threshold: n/a
rationale: Remy reports using Codex, Claude Code, GrokBot for work and Instinct strictly for personal-assistant tasks, finding this split works well.

In their words

I pretty much keep a lot of my work stuff within, split between like Codex, Cloud, Code, GrokBot. And then this is just fills the hole perfectly for a personal assistant AI.
Onboarding simplicity is make-or-break for mass-market AI adoption
heuristic based on: lived experience Remy

Source

The Startup Ideas Podcast — Instinct AI: The AI Assistant for normal people (September 15, 2026) · at 11:19 ▸

When this applies

when onboarding non-expert users into any product whose underlying mechanism (AI/agents/technical workflows) they don't understand

The takeaway

For mass-market adoption of a technically complex category, onboarding must use only primitives the user already understands, with zero exposure to the underlying technical model.

Why it works

Non-technical users don't understand underlying concepts (MCPs, CLIs, markdown files); removing any requirement to understand these and replacing with familiar primitives (phone number login, iMessage) collapses the adoption barrier.

One level up

The biggest barrier to mass adoption of a new technology category is usually the onboarding/mental-model gap, not the underlying capability itself.

Where it stops holding

This stops working when the target users are already technical/early-adopters who want visibility and control over the underlying mechanism.

Detail

rule: Mass-market AI onboarding should hide all technical concepts and use familiar sign-in/communication primitives.
threshold: zero exposure to MCPs/CLIs/markdown for the average user
rationale: Remy notes his technically-capable mother would still struggle with 'basic AI stuff' that he and Greg take for granted, underscoring that onboarding must be built for the least technical user, not the builder's own bubble.

In their words

There's no concept of MCPs, CLIs, Markdown files. It was just logging with a phone number, bang, you're in.
Containing agent financial risk with a limited-scope virtual card
heuristic based on: lived experience Remy

Source

The Startup Ideas Podcast — Instinct AI: The AI Assistant for normal people (September 15, 2026) · at 20:25 ▸

When this applies

when granting any autonomous system or third party spending authority on your behalf

The takeaway

When delegating financial authority to an unproven or autonomous actor, use a bounded-exposure payment instrument rather than your primary account, so worst-case loss is capped and acceptable.

Why it works

Issuing a separate card instrument with a hard daily spending cap limits the maximum possible loss from any single failure mode (agent error, fraud, runaway spending) to a predefined, acceptable 'blast radius.'

One level up

Delegation of risk-bearing authority to new/untested systems should always be paired with an explicit, pre-set ceiling on possible damage.

Where it stops holding

This stops working when the capped limit is set too high to meaningfully protect you, or when the task genuinely requires spending beyond the cap, causing failed transactions.

Detail

rule: Create a separate virtual card with a conservative daily spending cap before giving an AI agent payment authority.
threshold: $500 daily limit, per Remy's own setup
rationale: If the agent goes nuts and spends the max, losing up to $500 is not the end of the world, so the blast radius is contained.

In their words

because, you know, if like the agent goes nuts and if the max it spends is $500, it's not the end of the world for me.
Invite-only scarcity as growth/marketing mechanism (Instinct AI vs Clubhouse)
case based on: observed outcome Greg

Source

The Startup Ideas Podcast — Instinct AI: The AI Assistant for normal people (September 15, 2026) · at 5:37 ▸

When this applies

when launching any new product into a crowded, noisy market where everyone claims to have the same category of offering

The takeaway

Artificial scarcity in access can function as a marketing differentiator in saturated markets, separate from its stated operational justification.

Why it works

Restricting access creates perceived scarcity and status signaling ('I got a code') that differentiates the product from endless undifferentiated competitor announcements, while also serving a stated compute-constraint rationale.

One level up

When your category is flooded with lookalike announcements, controlling access (rather than features or price) can be the differentiator that creates desire.

Where it stops holding

This stops working when the exclusivity feels arbitrary or the underlying product fails to deliver once early hype fades — as the hosts note Clubhouse hit a high valuation but 'never lived up to' it.

Detail

situation: Instinct AI rolled out invite-only amid a flood of 'introducing X agent' posts on social media, officially citing compute constraints.
decision: Keep access gated/invite-only rather than open signup.
outcome: Created hype and desirability (the hosts note they likely wouldn't have signed up if access were instant) while raising an open question of whether it is a 'Clubhouse moment' — hype without lasting value — given the rumored $10B valuation.
lesson: Gating access can be a deliberate growth lever as much as an operational necessity, but hype-driven high valuations don't guarantee the company lives up to them, as Clubhouse's $4B valuation didn't hold.

In their words

Is this a club host moment or is instinct going to live up? It's rumored that it's raising money at a $10 billion valuation right now.