Strategy question

How would you grow Lindy from solo users to small teams?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests growth strategy for expanding a single player product into a multiplayer, team based one.

Identify what changes moving from solo to teams: shared agents, shared visibility into what agents are doing, and permissioning across multiple people.
Find the natural expansion moment: a solo user's agent starts handling work that affects teammates, for example a sales agent whose leads need to be seen by the whole team.
Design a low friction invite path triggered at that moment, rather than a generic invite button buried in settings.
Add team specific value: shared agent libraries, visibility into agent activity across the team, and role based permissions so not everyone can edit every agent.
Adjust pricing and packaging to reward expansion, for example team tiers that get cheaper per seat as more teammates join.
Confirm with the interviewer whether the target is teams inside existing solo accounts, or a separate go to market for teams from the start.

Times the invite prompt to a moment of real team relevance, like when an agent's output starts affecting shared work, rather than a generic ask.
Proposes shared visibility and permissions as the core team value, not just multi seat billing, correctly identifying what teams actually need beyond individual usage.
Ties pricing to team growth incentives, making it cheaper per seat to add teammates, which rewards the exact expansion behavior being targeted.
Recognizes this is a product change, not just a sales motion change, since solo built agents need a path to become shared, governed team assets.

Treating this as purely a sales or pricing problem without addressing the product gap in shared visibility and permissions.
Prompting invites at an arbitrary point rather than a moment tied to real team value.
Ignoring governance, since teams need permission controls that solo users never needed.

How would you handle conflicting edits when two teammates modify the same shared agent?
What would trigger the first invite prompt for a solo user?
How would you measure whether the team expansion motion is working?