THAT PROPERTY LLC

Technology / Oxon Hill, Maryland

Practical software for small service teams

Small tools for
work in progress.

A place for the details
that keep work moving.

We design business record tools that help teams capture inquiries, keep useful context, and pass work between people.

Find a starting point
Records · Requests · HandoversMeet the company ↗

Our work / Four starting points

Where does the
thread get lost?

Start with the information problem. A focused tool can organize one part of the work without asking the team to change everything at once.

An example, with the details left in

What should a useful
record tell you?

Explore three pieces of an invented record. The questions matter more than the number of fields.

Illustrative record / Not a live system

EXAMPLE / CONTEXT

A question about a service request

What is known
The requester has described the task but has not supplied a source reference.
What needs checking
Whether this is new work or a follow-up to an existing inquiry.
The next action
Ask for the earlier reference before creating a separate item.

A useful record preserves the uncertainty. It does not turn an unanswered question into an assumed fact.

Invented content for explanation. No requests are created or sent, and no customer information is shown.

The context view is shown.

Working together

Understand the routine.
Then decide what to build.

A short workflow review establishes the recurring difficulty, the people affected, and the smallest useful change. Deliverables, acceptance tasks, access needs, and ongoing responsibilities are agreed before implementation.

01Workflow Review02Delivery & Acceptance03Keeping It Useful

Field notes / Practical reading

Small decisions.
Lasting consequences.

A record becomes useful through ordinary details: a clear field, a defined owner, a current reference, and an understandable ending.

Note 01

A field should answer a real question.

Note 02

An owner needs a defined responsibility.

Note 03

Help a reader recognize the current version.

Note 04

Define what remains after the work ends.

Two situations to consider / Hypothetical examples

When a shared inbox stops being enough.

An illustrative service team receives inquiries in one inbox, but the next action is tracked in personal notes. The question is how a small register could make responsibility and context visible.

Read the illustration ↗

When useful details live in several files.

An illustrative team keeps supplier references in a spreadsheet, supporting documents in folders, and recent decisions in messages. A structured record could connect those pieces without copying everything into one place.

Read the illustration ↗

These examples explain possible project questions. They do not represent clients, delivered products, or measured outcomes.