> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cosentriq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Complete and Submit Your CoTerminal Diagnostic

> Learn what the 75-question, 16-section CoTerminal intake covers, how each section shapes your verdict, and what to expect after you submit.

Your CoTerminal diagnostic begins with the intake — a 75-question, 16-section structured submission that conditions everything that follows. The pipeline does not guess at your situation. It reasons from what you give it. That means the specificity, honesty, and completeness of your intake directly determine the quality and confidence range of your verdict. A thin or hedged intake produces a wider confidence range and a less actionable plan. A sharp, detailed intake gives the system the signal it needs to return a high-confidence verdict you can move on.

## What the Intake Covers

The intake is organized into 16 sections that span the full picture of your product and business situation. Taken together, they give the pipeline enough context to reason across all eight domains simultaneously.

<Accordion title="Product Description">
  What your AI product does, the core mechanism, and the problem it solves. Be precise — describe the actual product you have today, not the roadmap version.
</Accordion>

<Accordion title="Market Position">
  Where you sit in your market, who your direct and indirect competitors are, and how you differentiate. Include your honest read on competitive intensity, not the polished pitch version.
</Accordion>

<Accordion title="Ideal Customer Profile">
  Your actual current user — the one paying you or using the product right now. The system distinguishes between your target persona and your actual customer. Describe the latter.
</Accordion>

<Accordion title="Financials">
  Monthly revenue, burn rate, runway, and unit economics where available. The pipeline uses these figures in the Goal Alignment and Financial sections of your dashboard. Round numbers are fine; missing numbers create gaps.
</Accordion>

<Accordion title="Team Capacity">
  Your current team size, functional coverage, and realistic bandwidth. The system uses your capacity score to calibrate the action plan. If you are a solo founder, say so. If your team is stretched, say that too.
</Accordion>

<Accordion title="Goals and Time Horizon">
  Your stated goal for the next 6–18 months and the time horizon you are working within. Be specific: "reach \$1M ARR in 12 months" is more useful than "grow the business."
</Accordion>

<Accordion title="The Decision">
  The actual strategic question you need answered. This is the most important section. State your real decision — the one you have been circling, not the polished version you would present to investors.
</Accordion>

The remaining sections cover AI technical foundations, integration complexity, customer evidence, growth trajectory, risk posture, and more. Every section feeds at least one domain reasoner in the pipeline.

## Tips for a Strong Intake

The following practices consistently produce sharper, higher-confidence diagnostic outputs:

<Tip>
  **Be specific about numbers.** Monthly revenue, burn, and runway figures matter. "We're pre-revenue with about 8 months of runway at current burn" is actionable. "Early stage, not focused on revenue yet" is not.
</Tip>

<Tip>
  **Describe your actual user, not your target persona.** Who is using your product right now? What do they do with it? What do they complain about? The system is looking for evidence of real product-market interaction — not your ICP hypothesis.
</Tip>

<Tip>
  **State your real decision.** The intake asks what decision you need help making. Be direct. "Should I rebuild the core AI system or refine the current one to close our enterprise deals?" is the kind of question the system is built for. Vague questions produce less directional verdicts.
</Tip>

<Tip>
  **Answer the capacity questions honestly.** The intake asks about operator capacity and decision drag. The system factors your real capacity into the verdict and action plan. Overstating capacity leads to an action plan you cannot execute. If you are at 70% capacity depletion, say so.
</Tip>

## What Happens After You Submit

Once you submit your intake, it enters admin review. Here is what to expect:

<Steps>
  <Step title="Pending Admin Review">
    Your intake is reviewed by the CoTerminal team. The admin checks for completeness, flags any sections that need clarification, and decides whether to trigger generation or request more information.
  </Step>

  <Step title="Clarification Request (if needed)">
    If the admin needs more detail before generating your diagnostic, you will receive an email with specific questions. Your status will show as **awaiting\_user\_clarification**. Responding completely and quickly speeds up your diagnostic.
  </Step>

  <Step title="Queued for Generation">
    Once the admin approves your intake, it enters the generation queue. Status: **queued**.
  </Step>

  <Step title="Pipeline Processing">
    The eight-domain pipeline runs against your intake. This is the parallel reasoning phase. Status: **in\_progress**.
  </Step>

  <Step title="Admin Quality Review">
    The output passes through two human quality review gates run by the CoTerminal team. Your status remains **in\_progress** until both gates are cleared and the dashboard is approved for release.
  </Step>

  <Step title="Dashboard Released">
    Your dashboard is released and you receive an email notification. Status: **released**. You can now access your founder dashboard and begin the acceptance flow.
  </Step>
</Steps>

<Note>
  If the admin requests more information, you will receive an email with specific questions. Providing complete, detailed answers to those questions speeds up your diagnostic and improves output quality. Partial answers result in the intake returning to the clarification queue.
</Note>

## Status Reference

| Status                        | What It Means                                                 |
| ----------------------------- | ------------------------------------------------------------- |
| `pending_admin_review`        | Intake submitted, awaiting the CoTerminal team's first review |
| `awaiting_user_clarification` | The team has requested more information — check your email    |
| `queued`                      | Intake approved, diagnostic queued for generation             |
| `in_progress`                 | Pipeline is running — your dashboard is being built           |
| `released`                    | Dashboard is live — check your email to access it             |
