🚀 AI Initiatives in flight
Where AI is actively developing at Qvantum right now. Curious, or want to join one? Reach out to the owner.
| Initiative | What it is | Where it's developing | Owner |
|---|---|---|---|
| RevOps engine (HubSpot) | AI-assisted GTM workflows across the sales funnel | Live in production, expanding to more functions | Dominic |
| NPI / CPI dashboard | Unified product-introduction status dashboard for PMs | Live & demoable; MAB + PAB data side-by-side | Stefano / PM team |
| NPI process agents | Step-by-step AI support through the NPI process | Workshop mapped; candidate agents defined | Federico |
| Aircall voice pilot | First AI telephony pilot (wedge toward voice assistant + chatbot) | Scoping call-flow + pilot owner, target before summer | David L |
| Marketing home-page build | Claude Code building web / home pages | Live — summer worker shipping pages | Lina (Marketing) |
| AI Qvantum community hub | This site — tutorials, use cases, prompts, ambassadors | Live & growing | Dominic |
| Load-shifting simulation feedback | AI feedback loop on heat-pump load-shifting sims | Feedback delivered; linking the simulation | Thomas N |
A living list — a row is dropped when an initiative lands or stalls. Closed and personal-coaching tracks are deliberately left off. Want yours here? Spin one up, then message the page owner.
🆕 How to spin up a new AI project
~15 minutes to a working project. Works the same whether you drive it with Claude, Copilot, or another assistant. Need a licence?
First — what is a "project", really?
There's nothing magic about it. A "project" is just a folder (or a Claude / Copilot "Project" space) that holds everything for one piece of work — the documents and data it should know about, plus a short note telling the assistant what the work is and how to help. That's it.
The point of keeping it in one place is context: the assistant can be useful every time you come back, instead of starting from zero. In Claude Code that note is a CLAUDE.md file in the folder; in the Claude or Copilot apps it's the Project's instructions and uploaded files. Same idea, different button. The steps below are tool-neutral — Claude is just the example.
- Decide the project's home. Pick a folder — a repo, a shared-drive folder, or a new local folder — that will hold the work. One folder = one project.
- Open it with Claude. In Claude Code (terminal / VS Code): open the folder and run
claudeinside it (see the Claude Code setup tutorial). In the Claude desktop / web app: create a new Project, name it, and add any starting documents. - Give it a
CLAUDE.md— the single most important step. In Claude Code, type/initand it drafts one for you. This file is the project's memory: what it is, who it's for, conventions, do's and don'ts. A goodCLAUDE.mdis the difference between a helpful assistant and a guessing one. Edit it as the project grows. - Add your sources. Drop the documents, data, or links the project should know about into the folder (or attach them in the app). Tell Claude what each one is.
- Start working in small, clear asks. "Summarise these three docs", "build a status page from this table", "draft the email." Approve its changes as you go until you trust the workflow.
- Keep it tidy. Use
/clearbetween unrelated tasks. UpdateCLAUDE.mdwhen conventions change. Share the folder so a colleague can pick it up.
Want it visible here? Once your project is doing real work, add it to the list above — message the page owner. Need help starting? Ask an AI Ambassador in your department.
Maintained on the AI at Qvantum site · the "in flight" list is meant to be living — one row edit when an initiative changes state.