What I build | Joe Cook

Knowledge architecture & custom AI systems

This is the most distinctive part of my work. I build the reference material, standing instructions, and repeatable procedures that let an AI assistant work the way a particular person or organization works. The goal is to stop repeating the same instructions in every conversation and to get more consistent results from one week to the next.

Personal AI operating systems: A consistent set of instructions and reference files that shapes how an assistant approaches every task for one person.
Writing and communication systems: Written descriptions of a person's voice, tone, vocabulary, formatting standards, and editorial rules.
Thinking and decision frameworks: Structured methods for evaluating information, defining problems, weighing alternatives, and forming recommendations.
Organizational knowledge bases: Procedures, standards, documentation, and institutional knowledge organized for use in AI-supported work.
Custom AI skills: Reusable instructions for recurring tasks, such as a weekly report, a proposal format, or a research method.

These systems need an owner. Reference files go out of date, instructions need revision as you learn what the assistant gets wrong, and sensitive information needs clear rules about what goes in and who can see it. I build that maintenance into the plan from the start.

See the Personal AI Operating System

Business process development

This is where my background in sales engineering, business development, strategy, and operations does most of the work. I help organizations write down how recurring work gets done, then build AI-supported workflows around it for market research, sales planning, account management, proposals, and internal communication.

Most of these projects start with a question an owner or manager already has.

How do we keep what our experienced people know when they retire or move on?
Why does our documentation look different depending on who wrote it?
Why does it take so long to find anything?
Which of our administrative tasks could stop eating everyone's afternoon?
Will this process still make sense when we're twice the size?

Read why a good prompt isn't enough

Technical documentation & instructional design

Service manuals, installation procedures, technical illustrations, training presentations, equipment diagrams, troubleshooting guides, and competency assessments. I've done this work for water treatment equipment, and the method carries over to most technical products.

AI speeds up the organizing, drafting, editing, and illustrating. It doesn't make the content correct. Technical accuracy depends on reliable source information and review by someone qualified, and I hold to that firmly when the subject involves electrical, plumbing, mechanical, or chemical systems.

See Technical Documentation & Training

Product design & brand development

Component layout studies, technical diagrams, interface concepts, brand identity systems, marketing collateral, and presentation design. This is where the technical and creative sides of my work meet.

I keep one line very clear. Product visuals I produce with AI are concepts for discussion. They show how an idea could work and help a team decide what to build. They are not validated engineering drawings, and I label them that way.

See Product Design & Visualization

Training, workshops & advisory work

I teach what I've learned to executives, teams, and professional groups. That can be an orientation for a leadership team, hands-on workshops built around your actual work, planning for a knowledge system, or advice on a specific project.

I don't sell fixed packages. Tell me what your people are trying to get done and we'll shape the session around it.

Start a conversation

Have a project in mind?

Whether you're exploring AI for your organization, building a knowledge system, creating training resources, or looking for a speaker, I'd welcome a conversation.

Let's talk