Dave Bettner
Email Dave

Building Homebase around a promise

Why I’m connecting the customer commitment, the work, and the delivery record in one operating workspace.

Homebase

Homebase needs to support several kinds of business at once. Agency services have client briefs and review cycles. A digital product has to reach a buyer in a form they can use. Apparel adds suppliers, samples, and physical delivery. Each one has a different definition of finished.

I’m organizing the product around what someone has been promised and the evidence that the promise was met. That gives the work a finish condition beyond a task being marked done.

Keep the commitment attached

Consider a recurring content package. This is an example, not a description of a client delivery. Preparing the files, approving the current version, sending it, and confirming that the recipient can use it are separate events.

The work needs enough context to connect those events:

  • What was agreed, including the source of that agreement.
  • Who owns the next action and when it is due.
  • Which version was reviewed and what the decision covered.
  • What was delivered and what remains unresolved.

If a file changes after review, the earlier approval should still describe the earlier version. A useful system makes that distinction available to the person making the next decision.

Give agent work the same context

An agent assignment belongs with the business record it affects. The owner needs to understand what the agent was asked to do, which inputs it used, and what result came back. A separate report can help, but the relevant decision and next action also need to remain with the work.

That is the direction I’m building toward in Homebase. The application already has work, client, content, and review records. Connecting them to dependable execution and verified external delivery is still in progress.

Test the whole delivery

The useful test is a complete service cycle. Can the operator start with the commitment, follow the work through review, see what reached its destination, and identify the next obligation? That is the standard I want the product to meet as the integrations develop.

The Homebase case study shows the current workspace with fictional sandbox projects. My Now page keeps the current focus separate from these dated notes.