Portfolio / Kronos / Enterprise Sales Platform

Before Salesforce,
We Built Our Own.

Three mission-critical sales applications. One developer. An enterprise platform built from the ground up.

I independently designed, developed, and maintained a suite of web applications supporting sales operations at Kronos—from lead management and territory administration to opportunity tracking and forecasting.

  • Full-Stack Engineering
  • Product Ownership
  • Enterprise UX
  • SQL Server
Original Kronos Pipeline Manager v2.0 in Internet Explorer, with application navigation, a New Opportunity form, guided steps, account and selling information, and product fields.
Pipeline Manager · Original Internet Explorer screenshotView full size

The Challenge

One sales organization.
One source of truth.

Sales operations depend on connected information: who owns an account, where a lead belongs, which opportunities are progressing, and what belongs in the forecast.

Kronos needed web applications that could support those workflows and bring sales information into a consistent, usable process.

  • Sales workflows

    Leads, accounts, territories, and opportunities.

  • Centralized information

    A consistent place to manage sales information.

  • Reporting & forecasts

    Visibility into the sales pipeline and its forecasts.

  • Consistent processes

    Repeatable workflows for complex sales operations.

The Platform

Three applications.
One connected workflow.

I designed and built three distinct web applications around the sales organization's work: managing teleservices leads, administering territory assignments, and tracking the pipeline.

Each application had its own responsibility within the wider sales process.

  1. KLM

    Lead Manager

    Manage teleservices leads at the start of the sales process.

  2. KTM

    Territory Manager

    Reassign accounts between sales territories.

  3. KPM

    Pipeline Manager

    Track opportunities, manage forecasts, and generate reports.

SQL Server / Data Integration

Database and integration engineering across the suite.

The data layer represents engineering work, rather than a single shared-database topology.

The Experience

Bringing desktop
workflows to the web.

A desktop-like interface used browser frames, a persistent navigation bar, and guided forms. Opportunity and product information stayed within a familiar application shell, with reporting and contextual help close at hand.

Original Pipeline Manager opportunity screen with General Info, Contact Data, and Activities steps, sales-stage and forecast controls, account fields, and a contextual Help button.
Opportunity workflow · Original screenshotView full size

Opportunity management

Guided steps and detailed forms organize account, selling, and forecast information.

Original Pipeline Manager product-information form with employee and manager counts, product selections, software and maintenance totals, a calculation work area, and contextual Help.
Product information · Original screenshotView full size

Product configuration

A rich, interactive product license calculator simplified pricing.

  • Desktop-style browser interface
  • Guided opportunity forms
  • Reporting and forecasts
  • Contextual help

The Engineering

From the interface
to the database.

As the solo developer, I owned requirements, UX, implementation, SQL queries, deployment, and ongoing maintenance. The work extended from the browser interface to application logic and database access.

Classic ASP 3 and VBScript, IIS, ODBC/SQL Server, and Java-plugin charts reflect the tools of that period. They describe the historical implementation, not a recommended stack for a new application.

  • Classic ASP 3

    VBScript

  • SQL Server

    ODBC and SQL queries

  • IIS

    Web application hosting

  • Browser UI

    Frames, HTML, and forms

  • Java charting

    Browser-plugin charts

  • User guidance

    Help and documentation

The Impact

Building software was
only part of the job.

The suite became mission-critical production software for Kronos sales operations. I maintained the applications and supported the people who relied on them, including writing a 77-page training guide in 2005.

The applications were eventually replaced through a transition to Salesforce—a multimillion-dollar project, as I recall. That early responsibility for software, users, documentation, and support continues to inform how I lead engineering today.

Let's Build Something Exceptional

Whether you're looking for leadership, architectural guidance, or a creative partner, I'm always open to discussing new opportunities.