> For the complete documentation index, see [llms.txt](https://salesa.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salesa.gitbook.io/docs/guide/google-sheets/sales-stage.md).

# Sales Stage

Sales stages define how your deals move from start to close.\
Salesa automatically sets up these stages based on the **industry** you select when creating your organization.\
Each industry has its own sales flow, so the stages are tailored to match real-world sales patterns.

### **How Sales Stages Work**

When you create a new organization, you choose an industry such as **IT**, **Real Estate**, or **Healthcare**.\
Salesa will then load a set of predefined stages that fit that industry.\
These stages appear as a column named **Stage** in your connected Google Sheet.

As your team exchanges emails with customers, Salesa automatically detects deal intent and moves the deal to the appropriate stage.\
For example, when a customer asks for a quote or demo, the stage may change from *Contacted* to *Qualified*.

#### **Default Stages by Industry**

<table><thead><tr><th width="157.75">Industry</th><th>Sales Stages</th></tr></thead><tbody><tr><td>Agriculture</td><td>Lead in → Need Assessment → Product Demo / Sample → Quotation → Order Confirmed → Delivery </td></tr><tr><td>Manufacturing</td><td>Lead in → Technical Requirement Discussion → Quotation / BOM Submission → Negotiation → Purchase Order → Production &#x26; Delivery</td></tr><tr><td>Construction</td><td>Lead in → Site Survey / Design Proposal → Cost Estimation → Bid / Tender Submission → Contract Awarded → Project Execution</td></tr><tr><td>Retail</td><td>Lead in → Product Presentation → Price Negotiation → Purchase Order → Delivery </td></tr><tr><td>Healthcare</td><td>Lead in →  Evaluation → Product Demo or Trial → In Negotiation → Contract Signed → Implementation / Support</td></tr><tr><td>Hospitality</td><td>Lead in → Meeting / Presentation → Proposal Sent → Negotiation → Contract Signed → Service Delivery</td></tr><tr><td>Transportation</td><td>Lead in → Assessment → Quotation → Contract Negotiation → Service Activation → Closed Won</td></tr><tr><td>Information Technology</td><td>Lead in → Discovery Call → Demo / Proof of Concept → Proposal Sent → Negotiation → Closed Won / Implementation</td></tr><tr><td>Finance</td><td>Lead in → Discovery / Qualification → Proposal Presentation → In Negotiation→ Contract Signing </td></tr><tr><td>Energy</td><td>Lead in → Feasibility Study → Technical Proposal → Regulatory / Tender Review → Contract Award → Project Execution</td></tr><tr><td>Telecommunications</td><td>Lead in → Needs Assessment → Service Proposal → Technical Validation → Contract Signed → Installation / Service Go-Live</td></tr><tr><td>Mining</td><td>Lead → Exploration / Site Visit → Feasibility Analysis → Tender / Bid Submission → Contract Award →  Delivery</td></tr></tbody></table>

### **Customizing Your Stages**

You can edit your stages directly in Google Sheets by changing the **Stage** column values.\
Salesa will learn your updated terms automatically.\
Keep the number of stages between **5–7** for clarity and best performance.

{% hint style="info" %}
For this version you unable to switch industry after organization created
{% endhint %}

### **Tips**

* Keep stage names short and consistent, like “Demo Scheduled” instead of “Waiting for Demo Confirmation.”
* Avoid overlapping meanings between stages.
* Review your pipeline stages every quarter to make sure they still fit your process.

***

> **In short:**\
> Salesa adapts your sales pipeline to your industry automatically, giving your team realistic, relevant stages right from the start.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salesa.gitbook.io/docs/guide/google-sheets/sales-stage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.