Product Design - Content Management - 2007-2011
Retired

Imagine

The CMS I carried from job to job, and the three products built around it.

Imagine

Most agencies sell hours. Thumbprint Strategic Media sold hours too, but it also shipped four of its own products, and the oldest one had been running for years before the company existed.

Imagine was mine, and I took it with me. I built the first version so that people who were not developers could publish their own pages. Every job after that, I brought it along and rebuilt it for the new problem. It was the most valuable thing I owned.

4products shipped
939files in Imagine alone
67staff pages it published
2007earliest surviving build

Imagine

The giveaway is in the header. Top right of every screen it reads MANAGED WEBSITE: PaylessCarRental.com. The install announces which site it is currently running. It was never built for one client. That is the whole reason it could travel.

Imagine admin screen showing the managed-website header
The administration shell. Blog, RSS and Contest tools down the left; every success and error state designed rather than left to the browser.
Imagine module dashboard
The dashboard. Locations, Hot Destinations, RSS Feed, Specials, and META Content for files, editor settings and administrator tools.

The module list is a rental company’s vocabulary: locations, hot destinations, specials. Swap those modules and the same shell runs a school district or a supplement shop. The contest engine lived here too, which is why the Payless promotions ran without a developer: marketing added a contest, picked a winner and exported the entries themselves.

Hot destinations editor
Fetch layout screen

Where it went

The archive shows the trail. The earliest structure is a school district running 67 staff pages and three schools, each maintained by the person whose name is on it. Then Payless, where Imagine sits in the administration directory of both the live site and its production database backups. Then a client, Holistic Alternatives, with its own manage/imagine.asp. Then Thumbprint, where it became the product the agency sold.

Same idea every time: the people who own the content should be able to change it without calling me.

What got built around it

Three more products came out of the same workshop, each one a thing a client had asked for often enough that it was worth building properly.

Imagine
Live content management
Imagine logo
The CMS. Locations, hot destinations, RSS, specials, contests, files and users, each as its own module.
ClientWire
Customer communication management
ClientWire logo
Its own strapline, and accurate. Ticketing for a franchise network, where a complaint has three parties and any of them can be the one holding it up.
iChatter
Social chat
iChatter logo
A hosted conversation widget with its own signup, moderation and a row of share targets for every network that mattered in 2010.
refPrint
Referral tracking
refPrint logo
Link analytics, and the one that travelled as far as Imagine did. Where a click was going, what carried it there, how many followed.

The tracker had three names

Imagine was not the only thing I kept rebuilding. A link tracker starts in 2006 as Fetch, built under my own shingle. In 2007 it is inside Payless as iFetch, a tab in the Imagine nav beside Blog Tool and Specials Manager. By 2009 it is refPrint, a Thumbprint product with its own identity. Same three columns the whole way.

The 2006 Fetch tracker table
Fetch, 2006. Tracker Name, Vendor ID, Clicks.
The refPrint tracking bar
refPrint, 2009. Going To, Via, Clicks. Three years and two rebrands later, the same question asked the same way.

Its middle-period mark, goFetch, is still sitting in the Imagine source folder where I left it.

ClientWire, and the three-party problem

A rental complaint is not between two people. There is the customer, the franchisee who ran the counter, and corporate who owns the brand. Any of the three can be the one who has not replied yet.

Eight ticket states across customer, franchisee and corporate
Eight states, not two. Franchisee to customer, franchisee to corporate, corporate to customer, corporate to franchisee, each with its answered and unanswered form. Corporate could see, at a glance, which franchisee was sitting on a complaint.
ClientWire navigation with Administrator and Franchisee roles
The same screen, two roles. Administrator and Franchisee see different tabs.

iChatter

iChatter conversation page
iChatter. A hosted conversation with its own identity, threaded replies, and a strip of share targets for every 2010 network worth a button.
iChatter signup and login dialogs
Its dialog set. Signup, login and FAQ, each styled rather than borrowed.

Provenance: recovered in 2026 from a disk image of the drive these projects were built on, the only surviving copy. Imagine 939 files (2007–2011), ClientWire 256 (2009–2010), iChatter 94 (2010), refPrint 21 (2009–2010). Screens are the original Fireworks design sources, flattened onto white and otherwise unretouched.

Need something like this for your business?

That’s what I build at Evolve Engineering.

evolve.engineering →

Or email hello@iamjust.in and tell me what’s slowing you down.

← More case studies

send a transmission

this goes straight to my inbox.