Afterword

A closing thought, about timing. Field Assembly could have been described a decade ago. It could not have been built this way.

For years, most businesses had two choices. Neither was ideal. One choice was to commission proprietary software built around the business itself, at a cost that only large organizations could usually justify. The other was to buy off-the-shelf software and gradually adapt the business to its broad assumptions. Almost everyone chose the second, because it was the only realistic option, and the cost of that choice stayed hidden inside a thousand small workarounds.

What has changed is the economics of customization. AI is part of that change, but it isn’t the whole story. Much of what once had to be written from scratch can now be assembled from proven parts: automation, cloud services, AI, and a relatively small amount of custom work where it genuinely earns its place. What was once practical only for large organizations has become accessible to many smaller ones.

That is the real reason Field Assembly exists now rather than a decade ago. The old assumption, that a system shaped around your particular way of working is a luxury reserved for the well-funded, is simply out of date.

If some of this feels familiar, that’s usually where an Assembly Reading begins. It starts with seeing the problem plainly. Once the work that catches becomes visible, it becomes possible to build an environment around it instead of continuing to work around the environment.

What’s driving you crazy?