Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
A software company supplying post-sale systems to car resellers. Its pipeline comes substantially from trade events and field visits, where the artefacts are business cards and conversations.
Its data-handling position ruled out hosted lead-management tooling.
The problem
- Leads captured at events arrived as a stack of cards and a set of memories.
- Contact details were transcribed manually, days later, with the conversation context already fading.
- There was no consistent way to distinguish a lead worth calling on Monday from one worth calling next quarter.
- Follow-up campaigns were assembled by hand, so they happened late or not at all.
- Hosted tools were not an option, which removed most of the market.
What we built
An on-premise lead-management system
Running entirely on the company's own infrastructure.
Business-card digitisation
Using optical character recognition, so a card becomes a contact record without transcription.
Interaction capture with transcription and automatic field population
So the context of the conversation lands on the record while it is still accurate.
Priority tagging
So the follow-up list is ordered rather than chronological.
Bulk follow-up email campaigns
Driven from that ordering.
How we delivered it
- 1
Establish the infrastructure boundary
And size the on-premise deployment.
- 2
Build the contact and interaction model first
The thing everything else writes into.
- 3
Add card digitisation
Tuned against real cards in the languages and layouts the company actually encounters.
- 4
Add interaction capture and auto-fill
With a review step before the record is committed.
- 5
Add prioritisation and campaigns
Tested on a real event's leads.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The system and its source
- The on-premise deployment configuration
- Extraction and tagging rules
- Campaign templates