Pitch Created. Processing & Auto-Redirect

​

Purpose

This page is the landing screen a customer sees immediately after submitting a new pitch from the Create Pitch flow. Its single job is to reassure the customer that their pitch report is being generated, give them a visible sense of progress, and automatically hand them off to the Pitch Workspace as soon as the report is ready. Pitch reports take several minutes to generate (Athena runs the pitch through multiple AI models, captures responses, scores sentiment, and aggregates competitor and source data). Rather than make the customer stare at a blank screen or refresh manually, this page polls the pitch’s status in the background and redirects them automatically the moment processing finishes. It sits between two pages in the customer’s workflow: they arrive here from Create Pitch after clicking submit, and they leave here for the Pitch Workspace: either automatically when the report finishes, or manually if they decide to peek early or start another pitch. This is a transient, single-purpose page. The customer is not expected to spend long on it, and there is no data to interact with beyond two navigation buttons.

​

What’s on the page

The page renders a single centered card on an otherwise empty screen. Everything below lives inside that card.

​

Pitch Created card

A narrow, centered card (roughly the width of a sign-in form) that contains the entire screen’s content. It fades and slides in gently when the page loads.

• “Pitch Created!” heading. Confirms the pitch was successfully submitted.
• Status copy. Two short lines: “Your pitch report is being processed.” and “This typically takes 5-10 minutes.” This sets the customer’s time expectation up front.

​

Processing status indicator

A small animated indigo dot with a pulsing “ping” halo, paired with the label “Processing your data…”. The animation is purely visual: it confirms to the customer that the page is live and actively waiting on the server, not stuck.

​

Progress bar

A thin indigo progress bar directly below the status indicator. The bar fills based on how much time has elapsed since the pitch was created, on a 5-minute scale:

• It starts at whatever percent of 5 minutes has already passed by the time the customer lands here (usually near 0%).
• It increases roughly once per second.
• It is capped at 95% until the server confirms the pitch has finished processing.
• When the server reports status = completed, the bar jumps to 100% and the page redirects.

The bar is a visual reassurance, not an authoritative percent: the actual completion signal comes from server polling, not the timer.

​

Action buttons

Two full-width stacked buttons:

• Create Another Pitch (primary). Sends the customer back to the Create Pitch form so they can start a second pitch while the first one finishes processing in the background.
• View Report (May Still Be Processing) (secondary). Takes the customer directly to the Pitch Workspace right now, without waiting for the auto-redirect. The label explicitly warns that the report may not be fully ready yet.

​

Redirect notice

A small line of helper text at the bottom of the card: “We’ll automatically redirect you when your report is ready.” This tells the customer they can safely leave the tab open and don’t need to do anything.

​

What you can do here

There are exactly two actions, both top-level buttons. There are no menus, no overflow actions, no keyboard shortcuts, and no destructive actions on this page.

• Create Another Pitch. Sends the customer to the Create Pitch page. The pitch currently being processed continues in the background; the customer can return to view it later from the Pitch Workspace.
• View Report (May Still Be Processing). Refreshes the cached pitch data and navigates the customer to the Pitch Workspace immediately. If processing isn’t finished, the workspace will show whatever partial state currently exists.

In addition to these two manual actions, the page redirects automatically to the Pitch Workspace as soon as the server reports the pitch is completed. There is a brief (~0.5 second) pause after completion before the redirect fires, so the customer sees the progress bar fill to 100% before navigation. If the page can’t find a pitch to track (no pitch ID in memory or local storage after loading finishes), the customer is silently redirected back to the Create Pitch page.

​

Data shown

The page is driven by two pieces of information:

• The active pitch. Identified by an ID that’s pulled either from the in-app pitch context or, as a fallback, from local storage where the Create Pitch flow stored it. This is used to know which pitch to poll for status.
• Pitch processing status. The page asks the server every 5 seconds: “Is this pitch done yet?” The server replies with a status (e.g. processing, completed) and a creation timestamp. When the status flips to completed, the page advances the progress bar to 100% and redirects.

Nothing else is loaded or displayed. There are no metrics, prompts, competitors, sources, or pitch content shown on this page: the customer sees that data on the Pitch Workspace after redirect.

​

Common workflows

​

1. Wait for the pitch to finish (the expected path)

1. The customer submits a new pitch on the Create Pitch page.
2. They land here and see the “Pitch Created!” card with progress at roughly 0%.
3. The progress bar fills gradually over ~5 minutes (capped at 95%).
4. When the server confirms the pitch is complete, the bar jumps to 100% and the page redirects to the Pitch Workspace, where the report is ready to view.

​

2. Peek at the report before it’s done

1. The customer is impatient and clicks View Report (May Still Be Processing).
2. The page refreshes its pitch data caches and navigates to the Pitch Workspace.
3. The workspace may show the report as still processing or partially complete; the customer can wait there for it to finish populating.

​

3. Start another pitch while this one cooks

1. The customer clicks Create Another Pitch.
2. They’re sent to the Create Pitch form and can submit a new pitch.
3. The first pitch continues processing in the background and will be available in the Pitch Workspace when ready.

​

Empty, loading, and error states

• Initial loading. Before the active pitch is resolved, the card shows three gray skeleton lines (heading + two body lines) instead of the live content. This is brief: usually under a second.
• No pitch found. If the page finishes loading but can’t find a pitch ID anywhere, the customer is automatically redirected to the Create Pitch page. They do not see an error message; this is treated as “there’s no pitch to wait for, so send them to start one.”
• Polling errors. If the status check fails, polling stops silently. The page does not display an error banner. In practice, the customer will simply see the progress bar stay near 95% and can use the View Report button to navigate to the workspace manually.
• Long-running pitches. Pitches that take longer than 5 minutes will show the progress bar parked at 95% indefinitely until the server confirms completion. This is intentional: the bar is a visual hint, not a literal countdown.

​

Linked from / links to

• Linked from: The Create Pitch page, after a customer submits a new pitch.
• Links to:
  • The Pitch Workspace (/pitch-workspace): both automatically on completion and manually via the View Report button.
  • The Create Pitch page (/create-pitch), via the Create Another Pitch button, or automatically if no pitch is found.

​

Common support questions

“How long does this take?” Typically 5 to 10 minutes. The on-screen copy says the same. The progress bar is calibrated to a 5-minute baseline and will cap at 95% until the server confirms the report is ready, so pitches that take longer will look stalled near the end, that’s expected. “The progress bar is stuck at 95%. Is something broken?” No. The bar intentionally pauses at 95% until the backend signals completion. As soon as the report finishes, it jumps to 100% and the page redirects automatically. If the customer has been waiting well beyond 10 minutes, they can click View Report (May Still Be Processing) to navigate to the Pitch Workspace and check status there. “Can I leave this page and come back later?” Yes. They can navigate away: the pitch keeps processing on the server. They can find it later in the Pitch Workspace pitch list. “Can I close my browser?” Yes. Processing happens server-side. When they come back and open the Pitch Workspace, the completed pitch will be there. “I clicked ‘View Report’ but the report isn’t there.” The button is labeled “View Report (May Still Be Processing)” for exactly this reason: it lets the customer through before the report is ready. Have them wait on the workspace; the report will populate when processing finishes. “It sent me back to Create Pitch: what happened?” This happens when the page can’t find a pitch to track (for example, if the customer landed on this URL directly without coming from the Create Pitch flow, or local storage was cleared). The page treats that as “there’s no pitch to wait for” and sends them to start one. If they had genuinely submitted a pitch, it should still be available in the Pitch Workspace pitch list. “Can I get to this page without first submitting a pitch?” No, and if a customer tries (e.g. by typing the URL directly), they’ll be bounced to the Create Pitch page automatically. “I don’t see this screen at all. I just see a locked screen.” The Pitch Workspace, including this success page, requires the Pitch Workspace feature on the organization’s plan. Customers without it see a feature-locked screen at the layout level. If a customer reports being locked out, check whether their organization has the Pitch Workspace feature on their subscription.