Sales Pipeline #170

New Issue

2025-12-05T11:03:06+01:00

vollstock commented

2025-12-05 11:03:06 +01:00

Intend

This should reflect the usual sales pipeline.
Don't shy away to do stuff differently than the business people. They only made this stuff up, too anyway.
Use what’s useful and remove, what’s not.

I do intend to make it

pretty / easy and fun to use
self-explained (for non bnusiness people)
helpful and productive

Workflow

Lead generation

get’s it’s own view (Akquise) this could be a large dump table for collecting targets and information on them. It’s the pool of potential future customers, we want to target.
This is also the place where automation / agents could work wonders. (fill, complete, suggest).

The table needs to have features to priotise / order entries, e. g. by expected revenue, by revenue, generated from similar customers, by geographic proximity, etc.

Because entries are weighted / sorted / qualified, it’s ok for this table to have lot’s of entries.

We should also keep track of leads, that we have targeted in the past.

The pipeline

should be simplified. Let’s focus on the features that will actually help us and our customers to move projects forward.

Only three columns
1. Targets (promising entries from the leads table get moved here (autmatically when empty) and thus receive attention from now on)

Naming and explaining

# Intend This should reflect the usual sales pipeline. Don't shy away to do stuff differently than the business people. They only made this stuff up, too anyway. Use what’s useful and remove, what’s not. I do intend to make it - pretty / easy and fun to use - self-explained (for non bnusiness people) - helpful and productive # Workflow **Lead generation** get’s it’s own view (Akquise) this could be a large dump table for collecting targets and information on them. It’s the pool of potential future customers, we want to target. This is also the place where automation / agents could work wonders. (fill, complete, suggest). The table needs to have features to priotise / order entries, e. g. by expected revenue, by revenue, generated from similar customers, by geographic proximity, etc. Because entries are weighted / sorted / qualified, it’s ok for this table to have lot’s of entries. We should also keep track of leads, that we have targeted in the past. **The pipeline** should be simplified. Let’s focus on the features that will actually help us and our customers to move projects forward. - Only three columns 1. Targets (promising entries from the leads table get moved here (autmatically when empty) and thus receive attention from now on) # Naming and explaining

vollstock added this to the 1.0 milestone 2025-12-05 11:03:06 +01:00

vollstock added the Design label 2025-12-05 11:03:06 +01:00

vollstock added this to the 1.0 Accounting and CRM project 2025-12-05 11:03:06 +01:00

vollstock moved this to In Progress in 1.0 Accounting and CRM on 2026-02-17 10:36:34 +01:00

vollstock closed this issue

2026-02-18 18:05:32 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Tooloop/Caramel-CRM#170