About
Built by a project manager who got tired of bad project documentation.
PM Agent Chain was founded by Guy Kushnir, a senior project manager with 15+ years of experience leading complex programs in FinTech, InsurTech, and Cybersecurity. PMP-certified, has led 22-person teams on $185M-class capital programs, and has seen the same pattern across every engagement: roughly 80% of senior PM time gets consumed producing documentation that nobody reads, while the actual work that moves the project forward gets the remaining 20%.
PM Agent Chain is the response. Built solo, using Claude Code as the primary development engine. Dogfooded on the platform’s own development from day one — every PMAC deliverable for PMAC’s own roadmap is generated by PMAC. Based in Even Yehuda, Israel.
The PMAC Method
PMBOK 7th Edition is the floor, not the ceiling.
PM Agent Chain is not a chatbot. It is a sequential 7-agent framework engineered for institutional rigor. Each agent corresponds to a PMBOK process group, and each agent reads the prior phase’s complete output before generating its own.
- 0Agent 0 — Assess
Brief intake, project pattern detection, scoping output.
- 1Agent 1 — Initiation
9 documents including Project Charter, Vision Statement, Stakeholder Register, Business Case.
- 2Agent 2 — Planning
Risk Register, Schedule, Resource Plan, Procurement Plan, Communications Plan, Quality Plan.
- 3Agent 3 — Execution
Status reports, change logs, deliverable tracking, action item registers.
- 4Agent 4 — Monitoring & Controlling
Performance reports, governance reviews, audit trails.
- 5Agent 5 — Validation
Quality gates, acceptance criteria validation, deliverable QA.
- 6Agent 6 — Closing
Final reports, lessons learned, archival packages.
This dependency chain is not a coincidence — it is the institutional logic of project management. A Charter establishes authorizing context; a Risk Register depends on the Charter’s scope; a Schedule depends on the Risk Register’s mitigations; a Status Report references the Schedule. Sequential agents preserve that logic. Parallel chats and one-prompt chatbots cannot.
The mission
Project documentation should be a competitive advantage, not a cost center.
Every PMO leader knows the cost of bad project docs: rework, missed risks, compliance findings, audits that turn into investigations. Every PMO leader also knows the cost of good docs: hundreds of senior PM hours per project, before the work even starts.
Our mission is to compress that cost without compressing the rigor — and to do it in partnership with the channel partners and PMO consultancies who have spent decades raising the bar.
If your firm helps Fortune 1000 enterprises deliver complex programs, we want to talk. The PMAC Method is yours to extend, customize, and brand. The infrastructure is ours.