Sales operations automation

Every opportunity with context, an owner and a next step.

Connect the path from first enquiry to proposal: lead intake, qualification, follow-up and human review built around your sales operation.

Sales operations · opportunitiesIllustrativethis week
  • Incoming42
  • Qualified19
  • Proposal8
  • In review3
  • Closed5
  1. 08:40AIProposal request from the website: 12 units, delivery in November.
  2. 08:41AIGathered the customer's history and suggested an owner: Bruno.
  3. 11:05BRBruno reviewed the proposal and cleared it to send.Approved · Bruno

Remote projects for businesses in Brazil and internationally. We agree languages, working hours and visits as part of the scope.

The journey of an opportunity

From first contact to acceptance, without losing the thread.

Illustrative · fictional people

Every opportunity shows its source, owner and next step. Price and terms always pass through a person.

  1. Mon · 08:40

    A contact arrives

    “I need a proposal for 12 units, delivered in November.”

  2. Mon · 08:41

    Context gathered

    The AI pulls the company, past purchases and the last contact, and suggests an owner.

  3. Mon · 08:45

    Owner and next step

    Bruno takes it, with a follow-up set for 2 pm.

  4. Mon · 11:05

    Proposal reviewedApproved · Bruno

    The AI drafts it. Bruno checks price and timing and clears it to send.

  5. Wed · 10:00

    Agreed follow-up

    “Hi Lúcia. Did you get a chance to look at the proposal for the 12 units?”

  6. Thu · 15:20

    Accepted

    Status updated in the CRM, with the date and the reason it closed.

Rules of the workflow.

Each rule goes into the plan in writing.

  • One owner per opportunity
  • Next step with a date
  • Proposal reviewed by a person
  • History attached
  • Status in the CRM
  • Dashboard and log

Is this a fit for your business?

For teams receiving enquiries through different channels and losing context between the first conversation, the quote and the follow-up.

  • An enquiry arrives, but nobody knows who should respond.
  • A proposal has to be rewritten because important information is scattered.
  • Conversations continue without recording a reason for loss or a next step.

What the implementation covers

Intake with provenance

We map forms, channels and records. Identity and duplicate handling rules are agreed to preserve useful context for each opportunity.

Follow-up with ownership

Stages and qualification criteria become explicit. Reminders and drafts can support the seller while respecting consent and channel permissions.

A proposal under review

We organize information and context to prepare a proposal. Pricing, timing, messages and commercial commitments go through the designated owner.

Process demonstration

From enquiry to a reviewed proposal.

An illustrative example of connecting context and approval. Explore each step.

Intake

Someone asks for help organizing their business quotes. The record keeps the source channel and request, and receives an owner.

A local demonstration using fictional content. No customer, message delivery or external system is connected. A real workflow depends on agreed scope and confirmed integrations.

What we agree together

One initial workflow, with clear acceptance criteria

We start with one channel and an identifiable sales journey. Tools, messages, contact rules and indicators are defined with the team. Campaign activation and media spend are separate decisions.

What we need to understand

  • Enquiry channels and the CRM or tracker you use today.
  • Your definition of a qualified opportunity.
  • Who responds, who approves proposals and the working hours.
  • Contact rules, permissions and the indicators already recorded.

Before you commit

Does this include a customer service inbox?

It can, when that is part of the problem. Our customer service and CRM page covers channels, queues and history. This service focuses on continuity from opportunity to commercial decision.

Does AI close sales by itself?

The illustrated workflow prepares context and drafts. Negotiation, terms and commitments remain with authorized people. The degree of autonomy is defined per action and in the contract.

How do we assess the outcome?

We use available indicators such as response time, opportunities with a next step, meetings, proposals and contracts. Data must come from the real process with a clear definition of each stage.

Already running

Systems the house built and runs, live today.

Nellia runs its own house on the kind of system it sells. GudiSystem shows the reputation module at a fictional hotel, with illustrative data. Gestio shows the dashboard with fictional data. NelliaOS appears in its new version, with illustrative data.

NelliaOS · approval queueReviewby a person

Moving NelliaOS demonstration with fictional data. A request arrives on WhatsApp and Anjo prepares the reply. The review deck shows what goes to the customer, what changes after it is sent and what weighs on the decision. A person decides, the steps run through to the record and the desk clears. The same sequence repeats for three example companies, each with its own media kit.

Example with fictional data
GudiSystem · hospitality7modules in productionIllustrative scenario, fictional data
The GudiSystem reputation module at Hotel Estrela Imaginária. Illustrative scenario, fictional data.
Gestio · clubs and gymsPlaypublished appsIllustrative scenario, fictional data
The Gestio dashboard for Clube Horizonte Imaginário. Illustrative scenario, fictional data.
  • 2013building software since
  • +100clients with active systems
  • US$ 50Mthrough client operations
  • +25%average revenue increase for active clients

Figures from the group, reported by the group. The amount moved is what passes through the systems inside each client's own operation. Nellia's own revenue sits outside this count.

Start with one channel and one path.

Tell us how enquiries arrive today and where context gets lost before the proposal. The conversation starts there.

Sales operations automation | Nellia