Establish the context
Bring together the knowledge, current commitments, decisions, and standards that your assistant needs. Structure them so you can inspect, correct, and reuse them as circumstances change.
Operate by Design.
A 90-day engagement to design, build, and embed an AI operating system around your context, tools, and recurring responsibilities. Weekly one-to-one sessions, with support between them.
A proposal draws on what you know about a client. Delivery creates new knowledge about their needs. Planning should use what delivery has taught you.
When each activity has its own isolated context, you become the person carrying everything between them.
The Build connects those activities through a shared operating foundation. Together, we define the context your AI needs, the processes it can help execute, and the decisions that remain yours. Then we apply that architecture to the recurring responsibilities that matter in your business.
You develop a system you understand and can continue shaping.
An AI operating system is a system for systems. It gives your knowledge, instructions, processes, and specialist capabilities somewhere coherent to live and a way to operate together.
ContextOS provides a starting foundation. What we build on it depends on your situation: client delivery, planning, research, marketing, or another area where a more deliberate process would return capacity to you.
Each system needs a clear outcome, relevant context, defined responsibilities, and a way to judge whether it is helping. Those decisions guide the build.
Bring together the knowledge, current commitments, decisions, and standards that your assistant needs. Structure them so you can inspect, correct, and reuse them as circumstances change.
Choose a valuable recurring activity and make its inputs, steps, outputs, and review criteria explicit. Decide what can be delegated and where your judgement belongs.
Develop reusable instructions and specialist roles, and connect relevant tools where they serve the agreed outcome. Introduce scheduled execution when the process, permissions, and recovery path are ready for it.
Review actual results. Retain useful knowledge, correct faulty instructions, and refine the process. Use the next cycle to test whether the change helped.
Each session reviews what has been built and used, addresses the next constraint, and sets the next useful step. The sequence follows your context and capacity.
Between sessions, you apply and develop the system. You bring the business judgement and lived context; Peter brings architectural guidance, implementation support, and a disciplined way to connect the pieces.
The engagement includes:
Clients can begin throughout the year. At the end of each 90-day period, we review what has changed and whether a further 90-day period would serve your next priorities.
Implementation is collaborative. You remain involved in building and operating the system.
The Build suits an owner or independent professional whose business depends on their thinking, planning, analysis, and communication, and who wants guided implementation around that specific reality.
You need room to participate, apply what we build, and review its effects. The first conversation establishes the result you want, the current constraints, and whether this form of support fits.
If you want a shorter guided experience first, explore the Sprint or the AI Operating System Intensive. The self-paced AI Operating System course provides the foundational setup and understanding.
Not included: