A CRM for the [delivery] business cycle

  • Collaborative territory research

    Leveraging the power of organizational knowledge gives account managers the industry sight-lines, needed for imparting confidence in the market opportunities they present to clients. Aligning the data model supporting the CRM architecture, with the natural business relationships found within a sales-force, drives lucid consultation.

  • Content-funnel utilities

    Keeping up with information-currents, account managers maintain situational awareness within their minds. Facilitating the information juggle with tools that double as information-capture mechanisms, saves on mental energy, data entry toil, and improves content quality and richness.

  • Absorbing data for broad understanding

    The typical dedicated pages of a Salesforce account (of which many hierarchic and nested levels exist) includes walls of text entered free-form into vertically listed data fields. Presenting information visually according to its role and identity within a business cycle-enabled UI workflow, alleviates knowledge retrieval and absorption woes.

Information per Need (Site Map)

Layers and categories group and interconnect content parts, by their forms of consumption within the research and sales cycle. I derived this background from pre-existing systems and briefings with stakeholders and analysts.

These time and organizationally-based profile bits (right-side), link up with an alternate ingestion process within 'Client Communities' interactions.

Research and Knowledge Management Structures (IA)

-- Drafting of the information structure --

Market research and communications form the basis of business development– the first stage of the recruiter business cycle. Information transacted during such industry interactions requires data models that allow mapping of information to actual usage patterns; this empowerment enables collaboration and 'organizational' knowledge management

Detailing metrics interests

-- Comprehensive architecture --

The data models mentioned just prior, reveal the 'value' and organizational intelligence mapped behind this interface, revealing the purposes of knowledge management for the sales-force. The data model from 'Communities' demonstrates.


3D in [Area] Graphs

‚Äč With 3D one may browse for and perceive specific data, within a rich [if rough] and abundant, holistic notion of its context. Overlaid grids per track, and such orienting utilities for comparing data values, may dramatically mitigate the downside of unexacting measurement in the depth field.


'Client Communities' support for sales pipeline

Recruiter-Employer Overlap (Product Outline)

product map
sales pipeline story

The world of recruitment consulting and HR involves an expansive range of disparate and unintegrated products, used in the attempt to satisfy a potent, expensive, and difficult problem in society: how to deliver people to an appropriate career path.

The recruiter-client interactions suffer from memory-loss and from communication so rife with 'seams' and repetitive cycles* that even basic operating information becomes a central challenge to acquire [and then maintain]. Immersed in the routines of the industry, it becomes easy to forget the absurdities of the broad industry paradigm, visible to outsiders and professions happily lacking such basic problems.

*The vast proportion of recruiters won't last two [let alone one] year(s) on the job

'client internal dialogue' may mingle with 'position info', at a third(second) click; and then push 'up' to publish @ 'Client Project-team Info'

Structured Content (IA)

Client Project-team Info: a portable home-base for recruiter and project team to meet.

Portability draws employers into the HR ecosystem of software services; as they may invest in the system without risk of lost effort.

Lateral (same-level) content connections between 'timeline', 'position info', and 'internal dialogue'

hashtag summary and dialogue 'rooms'