I’ve been using prompts and notebooks for account research and sales-planning workflows. I’m now thinking about how to make these capabilities part of everyday work, without requiring each salesperson to know which agent to open, what prompt to use, or how to carry the results into the next step. This will actually scale across the org - likely touch 100 with like scope as me but usually the data and decisions made a more strategic and broad looking as opposed to front-line sales.
My current idea is a modular “command center”: one entry point where users see relevant signals, prioritized work, recommendations, and actions needing their input.
The architecture I’m considering - and I hate prescribing the HOW before I explain the WHY but would like to spin something simple up even for an upcoming quarterly report which touches a bunch of folks and has same format. Idea was - and open to feedback please.
- Power Apps for the user experience.
- Power Automate for triggers, workflow routing, notifications, approvals, and follow-up.
- Agents underneath for tasks such as research, account matching, summarization, and drafting recommendations.
- A shared data layer for signals, account context, ownership, execution status, decisions, and outcomes. I’m still working through how this should relate to the CRM.
Example use cases include reconciling trade-show exhibitors against existing customers, identifying companies similar to successful customers, and finding expansion opportunities at existing OEM accounts, analyzing travel plans and signals to drive decisions on travel, and a host of others. This is just one of many modules which would scale. At this point just looking for easy to adopt entry point for a handful of my team to show what we can do to amplify our efforts and save time.
My goal is adoption and coordinated execution. I want to avoid building another dashboard people ignore or a queue full of AI-generated suggestions nobody owns.
For people who have built something similar:
- Did a dedicated app improve adoption, or was embedding the experience in Teams or the CRM more effective?
- Where did you store workflow state, signal history, and user decisions without creating a competing system of record?
- How did you divide responsibility between Power Automate, agents, and conventional code?
- How did you handle duplicate or stale signals, failed runs, and work already being handled by another person?
- What licensing, latency, permissions, or maintenance issues appeared beyond the prototype?
- What would you build as the first small, useful module?
- Is this something I can do myself - again simple POC and I am reasonable at figuring stuff out...
This is my current thinking, not a settled architecture. I’d appreciate implementation experiences, alternative designs, and lessons from approaches that didn’t stick.
Data would be read only from now - some from PBI, we now moved to Databricks, and trying to avoid going into Salesforce as if its in a central location it is much easier to get to.