Use casesCustomers and sales

CRM-style sales pipeline

Configure leads, accounts and deals around how your team actually sells.

  1. Qualified
  2. Discovery
  3. Proposal
  4. Negotiation
  5. WonDone
  6. LostSide exit
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Off-the-shelf CRMs make you sell their way, and the fields that matter to your business end up in notes. Discount approvals happen in chat, and nobody can see the real pipeline without asking each rep. This is a CRM-style pipeline you configure for your process, not a complete CRM product with every CRM integration.
Who feels it: Sales teams and sales managers

How It Works

How this use case runs, step by step

Amber steps wait for a person's decision; everything else moves on its own.

  1. Existing contacts come inA commercial cleaning company imports its accounts and contacts from an Excel export. The dry run finds two rows with a missing region before anything is saved.
  2. A lead arrivesA facilities manager asks for a quote. The lead is assigned to the rep for that region, who is notified straight away.
  3. The deal moves forwardThe rep drags the opportunity to Proposal on the kanban and generates the proposal document from the record.
  4. A discount needs sign-off Approve or rejectThe customer asks for 15 percent off. That is above the rep’s limit, so the sales manager approves it from her inbox.
  5. WonThe rep marks the deal Won. The onboarding record is created for the operations team with the account details filled in.
The organisation and people are invented.

Product Capabilities

What you configure in this app

Mostly configuration. Rules that configuration cannot express are written in C#.

Records 4

  • Opportunity5 fields + history, files, comments
  • Lead5 fields + history, files, comments
  • Account4 fields + history, files, comments
  • Contact5 fields + history, files, comments

Stages 6

  1. Qualified
  2. Discovery
  3. Proposal
  4. Negotiation
  5. Won
  6. Lost

Automatic 3

  • NotifyA new lead is assigned to its owner and they are notified in-app
  • WorkflowMoving an opportunity to Won creates the customer’s onboarding record
  • ScheduleA weekly email digest lists each rep’s deals with a close date this month

Screens and reports 6

  • Kanban of opportunities by stage
  • Data grid of leads with saved filters, such as my open leads
  • Account view with contacts, deals, comments and history
  • Charts of pipeline value by stage and month
  • Weekly pipeline report in Excel for the sales meeting, on a schedule
  • Proposal document generated as Word or PDF from the opportunity
Who approves, in detail

A discount above a set percentage goes to the sales manager (role). Deals above a larger value also need the head of sales. A reminder goes out after one working day, so deals do not stall at the end of the quarter.

When the rules change

See TechAppForce on your own use case

Bring your own version of “CRM-style sales pipeline” and we will model its records, stages and approvals with you. A change a few months in is a reviewed release, not a rebuild.

Release: Lifecycle: opportunity

Stages
Unchanged: Discovery · Proposal
Added: + Site survey
Approvals
Removed: - Discount above 10%
Added: + Discount above 12%
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release