Manual Deals / opportunities
A deal (or opportunity) is at the heart of the sales cycle. It carries a label, a type (Customer / Prospect / Referrer), an estimated amount, moves forward through colored stages, and closes as Won or Lost (with a reason).
Overview
The Deals screen lists the company's sales opportunities. Unlike a one-off quote, a deal lives over time: it is detected, qualified, negotiated, then won or lost. It aggregates an estimated amount and gathers all traceability (quotes, meetings, notes) under a single record.
Business goal
- Detect and qualify an opportunity
- Estimate the potential revenue
- Move the deal forward stage by stage
- Close (Won / Lost) and analyze losses
Target audience
- Sales reps — create and drive their deals
- Team leaders — oversee the pipeline
- Management — tracks forecasts & win rate
Place within the module
The deal is the central entity: it brings together the cycle quotes, the meetings and notes. For the module overview, see Sales cycle.
Access and navigation
Left-hand side menu: Deals → Deals.
List of deals
Summary cards at the top (open deals, estimated amount, won / lost this month), then the detailed list. Each row shows the current stage as a colored dot (color set on the stage).
| Label⇅ | Type⇅ | Customer⇅ | Est. amount⇅ | End⇅ | Team⇅ | Stage⇅ | ||
|---|---|---|---|---|---|---|---|---|
| IT equipment fleet | Customer | SOCIÉTÉ FONDS CLAIR | 40,000.000TND | 30/06/2026 | North Tunis Team | Negotiation | ||
| Workshop ERP migration | Prospect | ECAR | 22,100.000TND | 15/05/2026 | Greater South Team | Qualification | ||
| License renewal | Referrer | EL MAZRAA | 7,900.000TND | 20/05/2026 | North Tunis Team | Detection | ||
| Annual maintenance contract | Customer | BUFFET CONCEPT | 18,600.000TND | 28/02/2026 | North Tunis Team | Won | ||
| POS terminal rollout | Prospect | STÉ NOVA RETAIL | 31,000.000TND | 10/03/2026 | Greater South Team | Lost |
List columns
| Column | Description |
|---|---|
| Label | Name of the deal / opportunity (e.g. "IT equipment fleet"). |
| Type | Customer · Prospect · Referrer — nature of the party (section 6). |
| Customer | Customer, prospect or consumer concerned. |
| Est. amount | Estimated amount of the opportunity (TND), entered at creation. |
| Start / End | Expected processing period for the deal. |
| Team | Sales team in charge (if the deal is managed by team). |
| Stage | Current stage of the cycle (EtatCycleDeVente), colored dot based on the configured color. |
Action bar
New
Opens the deal creation form (section 5).
Delete
Deletes the ticked deals (depending on privilege).
Search
Filters by label, customer, stage, team and period.
The icon at the end of the row opens the deal's detail record: stage, linked quotes, meetings and notes grouped together.
Create a deal
Click New. Enter the label, choose the type and the customer, specify the estimated amount and the team, then save. The deal starts at the first stage of the cycle.
Form fields
Identity & estimate
- Label of the deal (mandatory)
- Type: Customer / Prospect / Referrer
- Source of the deal & field
- Estimated amount (TND)
- Dates: detection, start, end
- Description (context of the need)
Linking & management
- Customer / prospect (or on-the-fly creation)
- Partners & competitors associated
- Management: by owner or by team
- Cycle stage (1st stage by default)
- Loss reason (if the stage requires it)
On-the-fly customer
The button next to the Customer field lets you create a new customer / prospect without leaving the deal form.
Deal type
The type qualifies the nature of the party behind the opportunity. It guides sales targeting and pipeline filtering.
Opportunity with an existing customer (additional sale, renewal, extension).
Opportunity with a prospect (a party not yet a customer) — new business.
Deal brought in via a referrer / business introducer (recommendation, partner).
Cycle stages
The stages (table EtatCycleDeVente) are configurable per company: each one carries a rank (order), a display color and an "allows a loss reason" flag. The deal moves from one stage to the next; the list's dot takes on the stage's color.
Example stages — the labels, order and colors are defined in Settings › Cycle stages and vary depending on your company.
| Stage property | Role |
|---|---|
| Label | Displayed name of the stage (e.g. "Qualification"). |
| Rank | Order of the stage in the pipeline; the 1st rank is the default stage at creation. |
| Color | Color of the dot shown in the deal list. |
| Allows loss reason | If enabled, selecting this stage requires a loss reason (section 8). |
Status & loss reason
Independent of the stage, the deal carries a closing status that summarizes its outcome. A deal marked Lost mandatorily requires a loss reason.
| Status | Code | Meaning |
|---|---|---|
| Not yet | 0 | Deal in progress, outcome not decided — it moves through the pipeline. |
| Won | 1 | Opportunity won; leads to an approved quote and then an order. |
| Lost | 2 | Opportunity lost; a loss reason is required (sales analysis). |
Mandatory loss reason
As soon as a stage that "allows a loss reason" is selected (or the Lost status), Swifto requires selecting a reason (configured in Loss reasons). A lost deal cannot be closed without stating the reason — this is what feeds loss analysis.
Team & management
A deal is driven either by a single owner, or by a cycle team. This choice determines meeting assignment, visibility and pipeline grouping.
By owner
A single sales rep owns the deal. Suited to individual structures or named accounts.
By team
A cycle team (e.g. "North Tunis Team") manages the deal collectively. Members and meetings are linked to the team.
Cycle teams are configured in Settings › Cycle teams before they can be assigned to a deal.
Deal workflow
flowchart LR A([Detection / Prospect]):::s --> B[Qualification]:::p B --> C[Proposal / Quote]:::p C --> D[Negotiation]:::w D -->|agreement| G([Won]):::ok D -->|refusal + reason| K([Lost]):::ko G --> H[Approved quote
-> Order / Invoice]:::ok B -.->|meetings + notes| N[(Traceability)]:::st classDef p fill:#f3f1ff,stroke:#7366fe,color:#1f1c3d; classDef s fill:#E0F2F4,stroke:#1A8EA5,color:#0E6B78; classDef w fill:#FEF3C7,stroke:#F59E0B,color:#92400E; classDef st fill:#F5F3FF,stroke:#8B5CF6,color:#5B21B6; classDef ok fill:#D1FAE5,stroke:#10B981,color:#065F46; classDef ko fill:#FEE2E2,stroke:#EF4444,color:#991B1B;
Business rules
Default stage — at creation, the deal starts at the first stage (1st rank) of the configured cycle.
Loss reason required — a deal cannot move to Lost (or to a stage that requires it) without a reason selected.
Centralization — quotes, meetings and notes for the same deal are grouped under the deal; the detail record surfaces the entire history.
Isolation per company — each deal belongs to the current company; data is never visible from one company to another.
FAQ & Tips
Deal or quote?
The deal is the opportunity that lives over time. The cycle quote is a linked priced proposal — a deal can carry several quotes (revisions).
I can't mark my deal "Lost"?
Select a loss reason from the list (configured in Loss reasons) to confirm the closing.
Tip — track continuously
Enter a meeting or a note after each exchange: it's this history that lets a colleague pick up the deal without losing information.
