Anatomy of a
Custom Assembly.
This plate is organized around the work itself: finding a project, understanding it, planning it, doing it, and remembering it afterward. A developer moves through all five, across several projects at once.
The software, the website, the calendar, the automations, sit inside the work as materials. Read the drawing slowly. The longer you look, the more of the week you can see.
At the center is a person. Everything here is arranged so the business leans on that person a little less each week.
Five parts of the work, twelve materials, one week. Most of it happens without anyone opening a folder.
Notice what points back toward the core, and what quietly points from one part of the work into another.
The work, and the materials each part is built from.
Read the plate and the legend together. Each entry names a part of the work and what happens there; the materials are how it gets done. On another business these would carry different materials. This is one developer’s.
Finding Work
Where a job first arrives, and how it is won.
Understanding Work
Where the developer learns exactly what a project asks for.
Planning Work
Where the project is put into time and onto paper.
Doing Work
Where the project actually happens, day to day.
Remembering Work
Where the business keeps what it has done.
A few materials belong to more than one part of the work. Photography sits in Remembering Work, yet reaches back into Doing Work: the same photo that records progress attaches to the approval written against it.1
The AI assistant lives in Understanding Work, yet the answers it gives are drawn from the Knowledge Library and returned into Client conversations. One material, working in three.2
Where a signed approval crosses from Doing Work into Remembering Work. The seam most owners still work by hand.
The proposal system pulling prior jobs, pricing, and known language into one new document.
The developer at the center, with fewer leader lines running directly to them than there were before.
Drawn from one developer’s week.
A representative week, assembled from recurring field observations. Times and details are composite.
- Tue 07:12A site photo finishes uploading to the client’s portal on its own.
- Tue 07:41A note reads “call back the Hollises.” The follow-up was already on the calendar.
- Wed 15:30A client asks a question the developer has answered before. The written answer is already there, waiting.
- Thu 16:56An approval is signed from three states away. By 17:01 the invoice knows about it.
- FridayThe filing cabinet has not been opened since March. Nobody has looked for it.
- The photograph is one material doing two jobs: it is evidence in Remembering Work and attachment in Doing Work. Assemblies are full of these small economies.
- An assistant is only as good as the library behind it. In this plate, material 5 leans entirely on material 4.
- The core is drawn dark on purpose. It is a person, and the whole plate is arranged around the hours of their week.
This is one plate. Yours would be drawn differently.
The Real Estate Developer Assembly is a single answer to a single question: what happens here? The work stays; the materials change from one business to the next. If you can already picture where your own plate would snag, that is where to start.