Connect Lemhi to ScalePad Lifecycle Manager, and each client's AI use cases land on their ScalePad roadmap as initiatives. Your vCIO walks into every QBR with the AI plan and the last 90 days of progress already in place.
See Lemhi in ActionA ScalePad Administrator creates an API key in ScalePad Hub. Paste it into Lemhi under Settings › Integrations, test the connection and save.
Auto-map matches each Lemhi client to its ScalePad client through ConnectWise, then by name, then by email domain. You map the rest by hand.
Approved AI use cases sync to the client's roadmap, and a 90-day AI progress note attaches to the next QBR meeting. Every item links back to Lemhi.
An admin in your MSP's Lemhi account connects ScalePad and maps clients.
Every Lemhi account can connect ScalePad. The 90-day progress note comes from Compass; clients without it get an AI Intel note instead.
ScalePad Lifecycle Manager and an API key from a ScalePad Administrator. QBR notes and report attachments need Lifecycle Manager X; on other licenses, initiatives still sync.
ScalePad Lifecycle Manager. Initiatives sync on every Lifecycle Manager license. QBR notes and meeting attachments need Lifecycle Manager X.
The client's next upcoming meeting whose type name includes "QBR" or "business review". Once that meeting passes, the note stays as the record of the review, and Lemhi starts the next one.
No. Priority and schedule belong to ScalePad from the start, and once your vCIO edits an initiative's name or description in ScalePad, Lemhi stops updating it. Lemhi never deletes your ScalePad data or changes items your team created.
The person who created the API key. Use a dedicated ScalePad user for the key, so your team can spot Lemhi's entries at a glance.
No. Lemhi runs your AI practice on its own. The integration puts that work into the QBRs you already build in ScalePad.
Walk through Lemhi with our team, including how it connects to ScalePad.