Sales

Lead qualification, scoring and pipeline

What you capture, the stages you move through and the rules that gate them are configuration — which is why two businesses that sell completely differently run on the same system.

In short

Linkubit asks the qualifying questions you define, writes the answers onto the contact, scores the lead rule by rule, and moves it through a pipeline whose stages refuse a move that skips a requirement. A deal is priced from your catalogue, never from a number typed in a chat.

Configuration, not code

Qualification fields you define

Lane and volume for a freight forwarder; budget and location for a property consultancy. The same engine drives extraction, the order the agent asks in, the admin forms and the filters.

One schema definition, four surfaces generated from it
Two completely different businesses, zero bespoke code

Freight forwarder

LaneNhava Sheva → Jebel AliModeFCLVolume24 TEU/moIncoterm

Property consultancy

RequirementOfficeMicro-marketWhitefieldCarpet area12,000 sq ftBudget

One schema definition drives extraction, the agent's questions, the admin forms and the filters.

A pipeline with rules

A lifecycle that refuses illegal moves

Stages carry entry requirements. Dragging a card somewhere it cannot go is refused with the requirement named, rather than snapping back without explanation.

Entry requirements are part of the stage, not tribal knowledge
The refusal tells you what to capture next

Qualifying

Sundaram Textiles

24 TEU/mo · FOB pending

Quoted

Drop refused

Won

Move to Quoted refused — Incoterm is required to enter this stage

The requirement is named, rather than the card snapping back without an explanation.

The rest of sales

Scoring you can read

Every contribution is recorded per rule, including the ones that did not fire. An opaque score gets ignored, and an ignored score is worse than none because it still takes up space.

Schema versions travel with the row

Edit your qualification schema and existing records keep the version they were captured under, migrating lazily on read. Nothing is orphaned.

Pipeline, tasks and meetings

Configurable stages with forecast weighting, follow-ups the agent can create, and meetings with outcomes.

Next best action

Ask a missing question, answer an objection, schedule, escalate. Surfaced for a person, not executed silently.

Payment in the chat

A customer who is ready pays inside WhatsApp with UPI or a card, or through a link by email. The amount is always your catalogue price, the money lands in your own gateway account, and a paid card closes the deal and writes the revenue on its own — the assistant asks a colleague before sending one.

Ready to put your sales on autopilot?

Start free

No coding required. No credit card required.