For Anthropic · 4:23
0:00 Who I am · 0:26 The question twice · 1:06 The Context Vault · 2:11 The live build · 3:14 What ships
Who I am, why Anthropic, and how I teach and how I build. My own systems, my own voice, no slides. The written answers in my application were written by me first. This page is the same person on camera.
What I do
- I build AI systems that run businesses.
- I train the people who run on them.
- Every build ships with documentation and hands-on training.
The stack is Claude, MCP and Notion.
The systems. The productized systems, each with its write-up, are at dimagornovskyi.com/projects.
The record. Sixteen years running my own companies, nine of them a marketing and automation agency, five years teaching a certification curriculum, six languages. LinkedIn
Why Anthropic
Of every company I can think of, Anthropic is the one that represents my highest values: the purpose, the spirit, and the why and way we do what we do. I use Claude every day, my whole life and business run on it, I built 48 systems on it and I teach myself on it, so I know the product the way you know something that is your second nature. After sixteen years running my own companies I want to be in service of a purpose bigger than my own business, and what I read in Anthropic's decisions, in the policies and the terms and in the limits the product sets for itself, is an ethic I trust.
The walkthrough, chapter by chapter
Time | What you will see |
0:00 | Who I am, and why Anthropic. |
0:26 | The same question asked twice: in a fresh chat, and in a project that has read the business. One answer is generic, the other is real. |
0:47 | Why every new chat is a brilliant new hire on their first morning. |
1:06 | Five pages and a map. The Context Vault in Notion that Claude reads through MCP before it answers. |
2:11 | The live build on Northline Studio, a sample company: the connection, the project, the follow-up email and the discount question. |
3:14 | What ships with it: the guide, the job aid and the champion. The part most rollouts skip. |
3:44 | The measure: did the team use it again the next week without anyone asking? |
3:55 | One limit, and the hours it gives back. |
4:13 | The offer. |
What ships with every system
The build is the easy part. These three are why the teams still run the systems after I leave, and every system I ship comes with them.
A guide. One page that says who owns the system, what it may touch, and who to call when something breaks.
A job aid. One page the person keeps next to them, with the three things they actually do.
A champion. Someone on the team who learned it from me and can teach the next person. A tool a colleague learned from a colleague keeps getting used. A tool learned from a mandate does not.
The measure
Did they use it again the next week without being told? That is the only number I ask to be judged on, and I look at it again after 90 days.
The offer
Name a workflow your team runs on Claude today and I will build the context, the guide and the job aid for it before we talk. No cost and no obligation. Building against your actual work shows where I am now better than any catalog does.