Every territory covered, every rep a step ahead.
The projects in each rep’s territory, read and ranked, so the work worth chasing reaches the right rep first.
Filtration control gallery, F. E. Weymouth Filtration Plant, La Verne, California. HAER CAL,19-LAVER,1-16.
Your best reps get in early. The rest hear about it late.
A good rep knows every engineer in the territory and brings you the work. Some territories are thinner, and nobody can say which projects went by. You see the jobs a rep tells you about, not the ones they missed.
How it runs
A person on your team approves before anything is written to a system you run.
- Map
Each rep to the territory, states and product lines they carry for you.
- Read
Every project in each territory, from the first plan to the final spec.
- Route
The ones worth chasing to the rep who covers them, with the pages behind it.
- Show
What is moving in every territory, and what is still waiting on someone.
What it produces
Every field links to where it came from.
Territory view, this week
Three states, two rep firms.
- New
- Eleven projects worth a look, each sent to its rep
- Specified
- Named on four projects, a competitor named on two
- Early
- Three projects in design with an engineer named
- Waiting
- Two projects nobody has picked up yet
The two waiting projects are in the thinnest territory.
Questions
- Do reps need their own login?
- They can have one, or the projects reach them by email or Slack. Either way each rep sees their own territory.
- Does this go around our reps?
- No. It gives them the reading, so their time goes to the engineer and the owner.
Bring the work you’re looking at.
Thirty minutes on your own projects. We go through what each one is, whether it’s yours, and what to do next.