SFA Via Issue Tracker Wiki

I love having an Issue TrackerWiki.

But what if you need an SFA system? Should we build that into a separate WikiEngine?

Or, can we use the Issue Tracker features for SFA?

You have a page for the prospect (1 for company and 1 for each individual).

Then each "issue" is an interaction/event between a salesperson and a prospect. The "Owner" is the salesperson.

The issue criticality reflects the "hotness" of the prospect, maybe.

If it's scheduled, then the dueDate is the planned date/time.

If an item gets rescheduled, you change its dueDate.

When it happens, you keep that dueDate and set status=Closed.

Then your historical report by prospect is just a BackLinks view.

Your calendar for a salesperson, past or future, is a filter of Issues.

The activity report for the team or a subteam is just a filter combining multiple Owners.

In the Start Up-s I've been in, that would pretty much be sufficient.

What am I forgetting?

Or an even simpler approach (say, where the Sales Cycle is shorter)

Every lead is an issue/ticket.

• the Owner is the salesperson

• the Priority is the Hotness of the lead

• the dueDate is the nextActionDate

• you tweak your Status field so that closed/Sold is different from closed/Dead

You lose the ability to have reports structured by specific interactions (during some time period) rather than by lead (all leads changed during the period). But if your Sales Cycle is relatively short-simple, then it's the close volume that counts, not the mid-cycle status updates.