MAKE A PITCH / 2 MINUTES

Close the learning loop

A yes, a no, and the little reason that makes the next pitch wiser.

Your little win: Record a response or outcome and see how it informs future work.

01 / SEE HOW IT FITS

The big picture, in little steps.

STEP 1 OF 3

Record what happened

Use Viewed, Replied, Won or Lost on a submitted proposal. These are your reported observations, not live provider verification.

02 / YOUR TURN

Have a little go.

✎ fictional practice

This is your practice table. Everything stays here—no account, real AI calls, or changes to Seerist.

THE PRACTICE TABLE

The customer got back to you.

Record a fictional outcome. Both a yes and a no can teach you something.

03 / DO IT IN SEERIST

Ready for the real thing?

Pitch Queue → Submitted proposal

Before you start: A submitted proposal and a genuine customer outcome.

  1. 1

    Record what happened

    Use Viewed, Replied, Won or Lost on a submitted proposal. These are your reported observations, not live provider verification.

  2. 2

    Add the reason

    For a win or loss, choose the closest reason and optionally add a specific note. Facts about what the customer valued are more useful than a guess.

  3. 3

    Take the next step

    A won proposal exposes Prepare delivery. Analytics shows recorded outcomes and learning signals. Sparse evidence should remain sparse rather than become a confident prediction.

A little thing to rememberYou learn from losses too. Record real outcomes, even when they do not make the chart look better.

Open this area in Seerist ↗ (new tab)

Opens the real app in a new tab. Sign in and check the selected workspace before acting.

Take a little note with you.

About this lesson

Checked September 13, 2026 against app source a365066. Based on web/src/pages/PitchQueuePage.tsx; web/src/pages/AnalyticsPage.tsx. This is a source-based guide, not a claim that every provider action was live-tested.