Claude Plugin & Skill Architect: AI Document Automation for M&A Advisory

About the engagement We are a boutique M&A advisory firm. Claude is deployed across the firm and connected to our two core systems, Microsoft 365 and HubSpot. At the center sits our Master Plugin: the shared core that governs how Claude works for every Equiteq user, giving it our identity, knowledge, rules and live deal context. Beneath it sit use-case plugins that perform investment banking tasks (financial analysis and modeling, equity storytelling, creative slide generation, etc.). The Master Plugin has been developed by assembling select skills from Anthropic's Financial Services pack, plus our own internally developed skills. It now needs to be validated by an outside expert to ensure Claude behaves reliably and consistently across our userbase. What you will do ● Review and validate the architecture — confirm our design is sound and complete, or show us exactly where it isn't. ● Complete the master plugin — finish the shared core every plugin depends on, working with our team. ● Validate and future-proof our data connections — confirm the links to Microsoft 365 and HubSpot are sound, secure and properly permissioned, and that the design can accept a future custom connection (Reasonal, our proprietary deal-intelligence layer) without re-plumbing later. ● Guarantee accurate, auditable output — every number and claim must be correct and traceable back through each step to the source system. ● Enforce a single slide skill — the only slide skill should be the one in the master plugin; every slide request should route to it. ● Advise on setup and usage — recommend where the master plugin should sit and how it should be configured, and which plugins should run in Claude Cowork versus Claude Code. ● Keep it safe and by-the-rules everywhere — no made-up facts, only data the user is allowed to see, a person makes every final decision, Claude confirms before any change. In particular, Claude must never delete or overwrite files in SharePoint, prove this with a commissioning test before rollout. ● Rule on open items — some future data sources (notably the Reasonal connection) and some HubSpot write-actions are still to be decided. Tell us whether each is fine to launch with or must be closed first. ● Leave us able to extend it ourselves — deliver a documented pattern for authoring new use-case plugins, and a golden starter skill others can copy. ● Hand over cleanly — document the design and setup so our team can maintain and extend the plugin without you. As an acceptance test, an Equiteq team member should be able to add one new skill and one new HubSpot write-action following the documentation alone. Must-have experience (we screen hard on these, please do not apply without them) ● Shipped Claude plugins / skills — you have built and delivered Claude plugins, agents or skills, not just prompts or chatbots. ● A professional-services or finance track record — you have built for M&A, PE, consulting, accounting or law, where accuracy mattered. ● Reliable, on-brand document generation — you produce PowerPoint, Word and Excel that come out right and the same way every time (see the visual standard below), not generic formatting. ● Accurate, auditable output — every output can be traced to its source, not just made to look right. ● Office automation depth — hands-on with Office COM and/or python-pptx / OOXML ● Connector integration — you have wired Claude (or similar tools) into systems like Microsoft 365 / SharePoint and a CRM with proper read/write controls, and can build or extend a custom connector (MCP). Strongly preferred ● Governance / guardrail design for regulated or confidential settings. ● Comfortable explaining technical trade-offs in plain terms to a non-technical stakeholder. ● Familiarity with Claude Cowork, Claude Code and the Microsoft 365 stack. How we will work ● Structure: a short fixed-price scoping milestone first, then a fixed-price build milestone once approved. ● Access: repository access is required for the build, granted after an NDA. ● Confidentiality: a regulated M&A environment, client and deal data are strictly confidential, an NDA is required.