Evaluating Startups: Artifacts Over Narratives

How does your team decide whether to work with a startup?

Most evaluation happens through narratives. The pitch deck tells a story. The founder describes the market. Someone takes notes. Another person sends a summary. By the time the team discusses it, everyone has a different version of what they saw. The TAM slide said one thing to the designer and another to the investor. The traction claim got lost in translation. Change that. Own it.

Startup evaluation has a structure problem. Pitch decks follow a standard pattern: problem, solution, market, traction, team, financials, ask. Investors score them on three dimensions: captivate, validate, motivate. Fifteen or more slides. But the inputs are narratives. Stories. Claims. Each retelling adds drift. "They have strong traction" means something different to everyone. "The team looks solid" invites interpretation. The very format that makes pitches compelling makes evaluation slippery.

The challenges are real. Early-stage startups lack financial records and operational history. Evaluation shifts from business metrics to founder assessment. VCs face data scarcity, cognitive bias, incentive misalignments. Red flags: unrealistic market assumptions, weak go-to-market strategy, no product-market fit evidence, poor team dynamics, uncoachable founders. These are narrative problems. Claims without artifacts. Stories without shared reference.

Structured artifacts fix this. A screenshot of the traction slide. An observation pinned to the TAM calculation. A comment on the team slide asking for the source. Concrete. Verifiable. Everyone sees the same thing. When the artifact is the message, there's no translation layer. No "what did they mean?" No "I thought the deck said." The discussion happens around the thing itself, not a retelling of it.

This is how Tribe fits. From the first idea or first contact, Tribe gives the team a shared place to work through the evaluation. Drop a screenshot of the pitch deck. Pin an observation to the market slide. Ask "what's the source for this number?" in a comment. Assign follow-ups. Track what gets verified and what doesn't. The designer, the product lead, the investor: they all see the same artifact. They all contribute in one thread.

The flow maps to the evaluation process. First contact: the deck or product demo becomes the artifact. Team review: observations get pinned to specific slides or elements. Due diligence: instead of "they said 25% MoM growth," you have the screenshot with a comment "verify against actual data." Collaboration: everyone adds questions, assigns owners, closes loops. Decision: the observations, the status, the unresolved questions, all visible. No summary memo that sanitizes the nuance. No meeting where half the room missed the context.

Same principle that makes design-dev handoffs work. The observation is the starting point, not a blame assignment. The artifact becomes the shared reference. When feedback lives in the open and the format assumes good intent, you get clear, collaborative evaluation. Focus on what to verify, what to challenge, what to decide. Not who said what in which meeting.

Epipelagic's model makes the fit explicit. Thalassocracy sets direction. Epipelagic launches ventures. Tribe does the work. Evaluation sits at the boundary: Epipelagic decides which ventures to launch, and Tribe is where the team works through that decision. Plans get refined. Assumptions get challenged. Projects move from rough ideas to executable work. The evaluation is part of that refinement. Is this venture worth launching? How do we work with this startup? The answers emerge from the artifacts, not the narratives.

You don't need a formal scorecard. Tribe doesn't implement one. The value is in the process. Artifacts over narratives. Shared context over scattered notes. Collaborative evaluation over one person's summary. Traceable feedback over lost threads. From first contact through diligence through decision, the team sees the same thing. They work from the same reference. They close the loops.

Next time a pitch deck lands in your inbox, don't summarize it. Capture it. Drop the slides as artifacts. Pin your questions to the specific claims. Invite the team. Let the discussion happen around the thing itself. Watch the evaluation sharpen. Do it now.