How to Set Up a Sales Pipeline in amoCRM Without a Developer

Updated September 24, 2026 · Kai Team · 6 min read

You can build a sales pipeline in amoCRM yourself in 1–2 hours: stages are edited under Leads → Setup (Сделки → Настроить in the Russian interface), fields are added from a lead card via Setup → Add field, and the same settings make a field required at chosen stages. No developer needed: admin rights and a thought-through stage map. Or send the same map in one message to an AI assistant such as Kai, which builds it through the official API.

Step 0. Sketch the pipeline before you open amoCRM

Most "broken" CRMs have stages invented on the fly. Write down the customer's path from enquiry to money and keep only the points where a salesperson does something checkable. Example for a made-to-order kitchen studio:

New enquiry → Qualified → Site visit booked → Quote sent → Contract and deposit → In production → Installed

Next to each stage, note what the salesperson must know to move the deal on. Those notes are your fields: "Source" at the start, "Budget" before the quote, "Loss reason" at close.

Step 1. Create the pipeline and stages in the amoCRM interface

1. Open Leads (Сделки) and click Setup (Настроить) in the top-right corner.
2. Add a stage with +. Click a stage to rename or recolour it; drag to reorder.
3. To remove a stage, move its deals out and drag it to the bin in the bottom-right corner.
4. The system stages "Won" and "Lost" cannot be deleted, only renamed, say to "Paid" and "Declined".
5. For a second pipeline (repeat orders, partners), click the current pipeline's name in the top-left corner and add one. Mixing first-time and repeat sales makes stage conversion meaningless.

Step 2. Add fields to the lead card

1. Open any lead. Contacts and companies have their own fields, set up from their cards the same way.
2. Click Setup, then Add field; pick a type and a name.
3. Core types: list, multi-select, text, text area, number, date, checkbox, birthday. Use lists for "Source" and "Loss reason": free text can't be reported on.
4. Group fields into tabs with the + next to "Files".

A minimal set: "Source" (list), "Budget" (number), "Next touch date" (date), "Loss reason" (list). Don't duplicate what amoCRM has: deal amount, responsible user, contact details.

Step 3. Make key fields required at specific stages

In a field's settings, pick the stages of one or several pipelines where it is required; the deal cannot move on until it is filled. From the step 0 map:

• "Source" to leave "New enquiry";
• "Budget" before "Quote sent";
• "Loss reason" when moving to "Lost".

Stop at one or two required fields per stage; beyond that people type dashes. Available from the "Advanced" plan upwards, administrators only.

Step 4. Run three test deals through it

Create three deals — "bought", "declined", "stuck at the site visit" — and walk each through the stages. Check that required fields block the move, analytics shows stage conversion, and the stuck deal has a task. Then delete them.

The Kai route: the same map in one message

Kai is an AI assistant that configures amoCRM and Kommo from a chat message. Connect the CRM with one-click OAuth from the amoCRM marketplace widget, then write to the Telegram bot @aiicrm_bot or the web chat (one account, one history). The step 0 map as a message:

Set up a pipeline for a made-to-order kitchen studio.
Stages: New enquiry → Qualified → Site visit booked → Quote sent → Contract and deposit → In production → Installed.
Lead fields: Source (list: website, marketplace, referral, Instagram), Budget (number), Site visit date (date), Loss reason (list).
Source required to leave "New enquiry", Budget before "Quote sent", Loss reason when lost.
When a deal reaches "Site visit booked", create a task for the surveyor one day before the visit.

Kai asks a few clarifying questions (say, whether repeat orders need their own pipeline), shows a plan and, once you confirm, creates everything through the official API and sends a report. Later changes are another message, typed or spoken. Honest limits: required fields need an amoCRM plan that has them, and Kai checks your process rather than inventing it.

Common mistakes when setting up a pipeline

• States instead of actions. "In progress", "Thinking": deals sit there for months. A stage answers "what has the salesperson done".
• Too many stages. Past ten, conversion is unreadable and deals move by feel.
• One pipeline for everything. First-time, repeat and partner sales have different cycles.
• Optional fields only. An optional "Source" is empty within weeks; you never learn which ads pay.
• No "Loss reason". The lost-deals report becomes a number you can't act on.

What if you use Kommo?

Same logic, English interface. Pipeline: Pipelines → Add pipeline; stages: … → Edit Pipeline → Add stage, click to rename, drag to reorder. Only empty stages and pipelines can be deleted, never the first pipeline. "Incoming Leads" can be toggled off but not deleted; "Closed-Won" and "Closed-Lost" can be renamed. Fields: open a lead, Setup tab, + Add field, required-per-stage in the same place. Admin role only, on every Kommo plan. Kai connects the same way.

Comparison: manual, integrator or Kai

amoAI, Kommo AI agent, no-code connectors (Albato, ApiX-Drive, Make, Zapier, n8n) and chatbots such as Salebot cover adjacent jobs: customer conversations and data sync. None designs your stages and fields; step 0 stays with you.

FAQ

What next

Stage map on paper? Open Leads → Setup and build it in an evening. Prefer someone to ask the right questions and do it through the API? Describe your business to Kai in one message.

Author: Kai Team · Updated September 24, 2026 · Paths checked against the official amoCRM and Kommo help centres.