The outcome you need
What operating result are you working toward, and who depends on it?
Contact
Start with the work that needs clarity.
Contact Josh Watson by email about any of the areas below. Start with the workflow that is hardest to operate, verify, change, or hand off. I can help determine whether the right next step is process design, a governed workbook, automation, an internal app, or a broader systems architecture.
- Property & hospitality operations
- Infrastructure & field coordination
- Fragile spreadsheet or workflow systems
- Internal application design
- Automation & integration
- Release, QA & rollback problems
- Knowledge continuity & AI adoption
Include a short description of the project, the current challenge, and the best way to follow up. You do not need a finished specification.
Helpful context
What to include in your note.
The people and roles
Who does the work, who reviews it, and who owns the decisions involved?
What’s already in place
The tools, documents, and sources currently carrying the work.
Where work is lost
Where effort is being duplicated, delayed, or dropped between people and tools.
The next decision
The decision or handoff that most needs clarity right now.
The kind of help
Whether the need is process design, a workflow system, an internal app, release controls, or applied AI.
How I work with people
You will hear it from me first.
You will hear from me before you have to ask. If something has slipped, you get it that week, along with what I am doing about it, rather than at the review.
If I think the thing you asked for is the wrong thing, I will say so once, plainly, with my reasoning. Then it is your call, and I build what you decided rather than relitigating it.
I do not hand over work you cannot run without me. The written workflows, the playbooks and the documentation exist because a system only its author can operate is a system you are renting.
What the work is for
Work to live, not live to work.
I intend to be excellent at this, and I intend to be present for the people in my life. In my experience those support each other rather than compete.
That is not the same as working gently. A pipeline built in three days against a sixty-day deadline, and a notarised build four hours and twenty-four minutes after the first commit, both came out of nights I decided to spend that way. Some of those deadlines were internal, not a client's. I go hard when something has to land. The point of going hard is that it lands, and that what lands is durable enough to hand to somebody else.
And this is the part I love. A permitted site handed to construction, and a system a five-person team runs without me, are the same act: whoever inherits it gets their week back instead of spending it rediscovering what somebody else already knew. Room to develop and scale the business, or more time with the people they love. Time is the one resource nobody can make more of, and this company was formed out of that necessity. Handing others the tools to get that time back is the best part of this work.