Contact

Use cases · /05

Sales. The team’s time, given back to selling.

Inbound requests qualified, meetings prepared, proposals drafted, CRM kept up to date.

/01 · Solutions

Possible solutions.

  • /01

    Lead qualification

    Every inbound request enriched, scored against the defined criteria and sent to the right salesperson.

  • /02

    Prepared meetings

    The account, its history, contacts and company news on one page, before every meeting.

  • /03

    An up-to-date CRM

    After every call, the notes, next steps and deal stage are proposed in the CRM.

  • /04

    Tenders and RFPs

    Requirements extracted, answers found in past bids; the team completes the rest.

  • /05

    Proposals and quotes

    Proposals drafted from the templates and pricing rules, to review before sending.

/02 · Execution

Execution example.

Example: an agent reads a 64-page specification, extracts 112 requirements, finds 89 answers in past bids and leaves 23 points for the presales team to write.

/03 · Measurement

Indicators tracked.

Measured before, then every month. No figure promised.

  1. 01Lead response time
  2. 02Time to prepare a proposal
  3. 03CRM data quality
  4. 04Conversion rate

/04 · Guardrails

Guardrails.

In the code, from day one.

  1. No email goes to a prospect without the salesperson’s approval, except what is already authorized.
  2. Prices follow the grid; a discount outside it waits for approval.
  3. Prospect data stays in the company’s systems.

/05 · Systems

Connected systems.

And any tool with an API or files.

  • Salesforce
  • HubSpot
  • Microsoft Dynamics 365
  • Pipedrive
  • Outlook
  • Gmail
  • SharePoint

/06 · See also

  • /01

    Customer service

    Request triage, drafted answers with their sources, first line on chat and phone.

  • /06

    Internal knowledge

    An assistant that answers the teams from internal documents, sources cited, permissions respected.