Public demo report

LedgerLeaf

This is a fixed public report with completed SWOT, evidence, and mentor annotations so evaluators can inspect the full workflow without sign-in.

Download sample deck Open sample cohort Open demo exports

Early signal snapshot

Founder interviews identified clear compliance pain but limited repeatable urgency.

Early signal snapshot

Two pilot conversations are underway, but no retained usage evidence is shown yet.

Early signal snapshot

Category positioning is still broader than the buyer proof available.

Overview

Transparent investor-style review

LedgerLeaf reads like an idea with plausible customer pain but insufficient proof. The deck is coherent enough to understand the intended workflow, yet too much of the investment case depends on narrative instead of sourced market evidence, retained adoption, and a credible moat story. This is the kind of submission that benefits most from evidence-density improvements before another screening pass.

Confidence warnings

Sparse evidence in the market and traction sections reduced scoring confidence.

Fallback note

Primary structured-output validation failed on low-evidence sections, so the deterministic fallback path completed the review.

Top signals

Problem & Solution

3/5

The workflow pain point is understandable, but the deck still reads as a concept rather than a proven solution.

Confidence 68/100

Team

3/5

The founders seem thoughtful, but the deck does not yet establish domain unfairness or GTM leverage.

Confidence 68/100

Deck Quality

3/5

The deck is readable, but the evidence density is too low for a high-confidence screening decision.

Confidence 68/100

All dimensions

Problem & Solution3/568/100 confidence

Market2/549/100 confidence

Business Model2/549/100 confidence

Traction & Validation2/549/100 confidence

Team3/568/100 confidence

Defensibility2/549/100 confidence

Deck Quality3/568/100 confidence

Coverage

Slides analyzed

Annotations

Layout checks

No explicit ask slide is visible

medium

The sample deck communicates the concept, but it does not close with a concrete capital ask or milestone framing.

The deck relies too heavily on narrative text

medium

Only a small fraction of the deck contains hard metrics, which keeps reviewer confidence lower than it could be.

Scorecard

Dimension-by-dimension evidence

Scores stay anchored to evidence and flagged gaps.

Problem & Solution

3/5medium68/100 confidence

The workflow pain point is understandable, but the deck still reads as a concept rather than a proven solution.

Weight 13%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 1

The pain definition remains broad and only lightly supported.

Slide type: problem

Gaps and improvements

Use sharper before-and-after workflow evidence from real customers.

Market

2/5low49/100 confidence

The market story is mostly qualitative and does not establish a strong, segmentable opportunity.

Weight 17%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 3

Category sizing is mostly narrative and unsupported.

Slide type: market

Gaps and improvements

Add sourced market sizing and buyer-level segmentation.

Business Model

2/5low49/100 confidence

The product concept exists, but pricing power, willingness to pay, and implementation scope are not yet clear.

Weight 15%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 2

The current product does not yet show why it meaningfully reduces compliance friction.

Slide type: solution

Gaps and improvements

Add pricing assumptions, implementation effort, and customer ROI evidence.

Traction & Validation

2/5low49/100 confidence

The validation story is the weakest part of the deck because it lacks retained users, revenue, or clear adoption milestones.

Weight 22%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 4

The startup references pilot conversations but not durable activation or revenue.

Slide type: traction

Gaps and improvements

Show active users, conversion rates, or customer renewal signals.

Team

3/5medium68/100 confidence

The founders seem thoughtful, but the deck does not yet establish domain unfairness or GTM leverage.

Weight 15%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 1

The team understands the workflow pain, but the execution proof is light.

Slide type: problem

Gaps and improvements

Clarify founder-domain credibility and customer access advantage.

Defensibility

2/5low49/100 confidence

No durable moat is visible yet beyond a generic category thesis.

Weight 10%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 2

The deck does not show why switching costs or data advantages will compound.

Slide type: solution

Gaps and improvements

Explain what becomes harder to copy after 12 to 18 months of usage.

Deck Quality

3/5medium68/100 confidence

The deck is readable, but the evidence density is too low for a high-confidence screening decision.

Weight 8%

Evidence and gap detail1 evidence / 1 gaps

Evidence

Slide 3

Important claims are not paired with evidence or citations.

Slide type: market

Gaps and improvements

Increase quantitative density and reduce unsupported narrative claims.

SWOT

Evidence-backed strategic readout

Strengths

1 items

mediumSlide 1

The team has identified a workflow that likely causes real pain, which gives the concept a reasonable starting point.

Weaknesses

1 items

lowSlide 3

The deck does not yet show enough quantitative proof or category clarity to support a strong readiness score.

Add sourced market sizing, customer proof, and retained usage evidence.

Opportunities

1 items

mediumSlide 2

If the company can narrow into one buyer workflow and prove savings or compliance speed, the story could tighten quickly.

Focus the deck on one target customer profile and one measurable customer outcome.

Threats

1 items

mediumSlide 4

Without stronger proof, investors may view the company as a broad thesis deck rather than a venture with verified demand.

Prioritize customer evidence before expanding the market narrative.

Slide map

What the model actually reviewed

Each slide record below reflects the extracted text, inferred slide type, clarity score, and any detected metric signals that fed the report.

Slide 1

problemmedium

LedgerLeaf wants to simplify sustainability bookkeeping for small businesses, but the pain definition remains broad and only lightly supported by user evidence.

Clarity 3/5

0 metric hits

Slide 2

solutionmedium

The workflow concept is understandable, yet the deck does not clearly show why the current product meaningfully reduces compliance friction or switching costs.

Clarity 3/5

0 metric hits

Slide 3

marketlow

Category sizing is mostly narrative and unsupported, with no convincing segmentation or budget-owner evidence.

Clarity 2/5

0 metric hits

Slide 4

tractionlow

The startup references pilot conversations but does not show durable activation, revenue, or retention metrics.

Clarity 2/5

0 metric hits

Decision layer

Human reviewer outcome

Decisions are stored separately from AI scores so teams can calibrate judgment, preserve rationale, and build the evidence graph over time.

Latest decision

Mentor

64/100 confidence

Decision history

MentorApr 10, 2026

64/100

Recommend mentor support before diligence because the deck needs customer proof, sharper category framing, and stronger moat evidence.

Reviewer-only decision capture is hidden for this viewer, but recorded outcomes remain visible with the report evidence.

Recommendations

Prioritized next actions

These recommendations remain visible even when this view is read-only.

Impact 1Quick Fix

Replace narrative market claims with sourced evidence

Use real segment sizing and a clear buyer map instead of broad sustainability software language.

1 linked slide references

Impact 2Moderate

Prove adoption with retained usage or revenue

Investors need durable validation signals, not only pilot conversations or qualitative enthusiasm.

1 linked slide references

Impact 3Moderate

Clarify what becomes defensible

Show what compounds with customer usage and why the workflow cannot be replicated easily by generic tools.

1 linked slide references