Powered by the BUILD Method™
A focused 90-day engagement to understand how THT works, strengthen the steps that move each project forward, and lay the foundation for smarter systems.
Built from the knowledge, experience, and processes THT already has.
Louis, thank you again for the trust you've placed in me.
This Executive Brief captures how I see the work ahead and the approach I'll bring during our first ninety days together.
Rather than beginning with technology, we'll begin by understanding how THT already works, protecting what's working well, and building stronger operating systems from the inside out.
This workspace will become a living reference throughout the engagement as we document progress, decisions, and what we build together.
I'm looking forward to getting started.
— Tony
You described a development project as “10,000 steps to completion.”
That stayed with me.
Those steps already exist — across conversations, decisions, files, habits, and the experience your team has built over time.
The opportunity isn't to create a 10,000-page manual. It's to make the most important steps visible, easier to follow, and easier to improve.
Before we build anything new, we need to understand how THT already works — and protect what is working well.
You talked about building smart systems that can help THT document what it knows, improve how work moves, and create a stronger foundation for growth.
Over time, those systems could be supported by focused AI agents that help the team find information, follow processes, capture decisions, and reduce repetitive work.
That future doesn't begin with AI. It begins by understanding how THT works today and turning that knowledge into something clear, organized, and useful.
Before a home is framed, the blueprint is drawn. Before technology is chosen, the operating system is designed. BUILD is the way we'll move through the ninety days — five movements, one shared rhythm.
Understand before you build.
Find what matters most.
Turn ideas into things that work.
Refine through honest reflection.
Grow through stronger systems, not harder effort.
You described a project as “10,000 steps to completion.” Those steps already live across your team's conversations, experience, files, decisions, and daily habits. Our work is to make the important steps visible, strengthen the areas that need attention, and gradually turn that knowledge into smart systems.
Understand how THT works today and protect what is already working well.
Organize important processes, clarify handoffs, and improve the areas creating the most friction.
Introduce practical tools, automations, and smart systems where they can genuinely help the team.
“A smart system brings people, processes, company knowledge, and technology together so work becomes easier to understand, repeat, and improve.”
It may include documented processes, templates, communication rhythms, automations, internal tools, or AI agents — but the technology always follows the need. AI comes later — after the process is clear and the company knowledge is ready.
Smart systems should support the people doing the work — not get in their way.
We'll begin by listening, observing, and studying how work happens today. Then we'll choose the improvements that will help THT most. This is discovery-led — the plan sharpens as we learn.
Learn from Louis and the people closest to the work.
Look at the tools, conversations, files, decisions, and habits THT already relies on. With your permission, this may include reviewing relevant Slack channels, shared files, recurring questions, decisions, and handoffs. Access will be limited to the areas you approve.
We won't introduce change simply for the sake of change. We'll build from what is already serving THT well.
Focus on the few improvements that can create the greatest practical value.
Create useful improvements during the engagement and teach the people who will use them through working sessions, short guides, and walkthroughs.
THT should own the knowledge and confidently use what is built. The goal isn't to create a new dependency on Tony.
You know the business. I'll help make the system visible — and build the next version with you.
We won't pretend to know every answer before we step inside the work. But the engagement won't be vague.
These are the practical outcomes we'll aim toward together. We'll confirm the final priorities after the first stage of discovery.
EACH OF THESE IS TRACKED AND DELIVERED INSIDE THE BUILD WORKSPACE
A clear picture of how a project moves through THT, including the important decisions, handoffs, tools, and people involved.
A practical starting point for organizing THT's processes: what happens, who owns it, what information is needed, and what comes next.
Three to five important workflows chosen to document, test, and improve first — for example trade coordination, pricing, approvals, change orders, or office-to-field communication. These are examples; the final list will be selected with Louis after discovery.
Identify where information is repeated, delayed, misunderstood, or lost, then test practical ways to make selected handoffs clearer.
Build and test at least one useful improvement during the engagement — a process, template, tracker, communication rhythm, automation, or small internal tool.
A prioritized view of where stronger processes, automation, internal tools, or future AI could create the most practical value.
A clear structure for the knowledge, documentation, and assets we create, including recommendations for where THT's long-term assets should live.
The five BUILD movements are the methodology. This is the practical rhythm.
By day 30, we'll pause to review what we've learned, confirm the areas that matter most, and shape the priorities for the remaining sixty days. The purpose isn't to restart the engagement. It's to make sure everything we build next is grounded in what we now understand about THT.
By day 60, important parts of THT's operation should be easier to see, explain, and repeat.
By day 90, THT should have more than a report. It should have practical improvements, useful documentation, and a clear foundation for what comes next.
Once THT's processes and knowledge are clear, focused AI agents may be able to support specific parts of the operation — with clear jobs, reliable information, and defined boundaries.
We won't introduce AI simply because it's available. It has to solve a real problem and earn its place.
During the first ninety days, we'll identify the strongest opportunities. If the foundation and priorities allow, we may prototype one focused use case together.
We've agreed to begin a ninety-day engagement focused on understanding how THT operates and building the systems that support it.
The work is structured as a monthly consulting retainer, giving us a steady rhythm of discovery, documentation, and implementation across the full ninety days.
As discussed, we also explored the opportunity for part of the engagement to participate in future project partnerships. The details of any Limited Partnership participation will be documented separately once the applicable legal documents and project pro forma are available.
Clear terms. Clear scope. Now we build.
The engagement includes the agreed 90-day scope and full access to the BUILD Workspace. Any additional software, hosting, AI usage, or larger custom development will be discussed and approved separately.
This brief tells the story. The BUILD Workspace is where the story becomes reality — the shared environment where our engagement actually runs, week by week.
It is the single source of truth for the ninety days. Nothing lives in an inbox, a slide deck, or someone's memory. Everything we learn and build is held in one place, open to both of us at any time:
You will never have to wonder where the work happens. It happens here, in the open, one click away from this page. By day ninety, THT owns a clear record of how the company works and what we built together — not a report, but a system the team can keep using.
Louis, thank you for the trust to work alongside you and your team.
Over the next ninety days we'll make the way THT works visible, protect what's already strong, and build the operating system that supports the next chapter of the company.
Every great build starts with a blueprint. Ours is drawn. Now we build.