Projects

Each engagement is a project with a start, an end, and something you can hand to someone else. Scope and fee are in a written proposal. These do not require a monthly plan.

AI adoption

The situation
A company has been told to do something with AI. Nobody has named the workflow, the tool, or what a useful result would be.
The work
The project lists the workflows worth doing, chooses a tool, writes a usage policy, and takes one pilot through until people are using it.
What you keep
A working pilot, a short policy, and a record of what was tried and what was left alone.

Systems and infrastructure

The situation
The network, the cloud accounts, identity, or a line-of-business system is in the way. It needs to be put right, or replaced.
The work
The project has a start, a cutover, and a finish. Unused overlap comes out. What stays is documented, including who administers it.
What you keep
The system in its new state, and a record of what changed, what it costs, and what to watch.

Assessments

The situation
Leadership needs a clear picture before it spends more: systems and spend, how technology supports the operation, or the exposure on the network.
The work
A technology, business, or network security assessment. Findings are ranked. This is not a certification. A licensed firm still signs any formal audit.
What you keep
A written report and a readout to the people who decide. The recommendation is the last part of that readout.

Integrations

The situation
Two systems the company already pays for should share data. Staff are moving it by hand, or the last attempt stalled.
The work
The project maps the data, chooses the path, builds the connection, and checks it against a real week of work.
What you keep
The connection running, and a note on how it fails and who fixes it.
Book a project consultation