The State Changers meeting focused primarily on a workflow issue faced by financial advisors who need to send marketing campaigns to compliance officers for approval. The current process is manual, involving sending a PDF or an email, and receiving approval through an email thread. The proposed solution was creating a dashboard for the compliance officers, but a key obstacle identified was the need for training and lead time for the dashboard's implementation.
In an attempt to bypass these issues, an alternative approach discussed was to develop a system where automatic emails get sent to compliance officers with a link to review the campaign. The link would contain a time-limited token linked to a different user category (the compliance user), allowing the officers to view and approve campaigns through the web browser itself, without requiring any software or login. The security of this process was thoroughly discussed. The participants highlighted the need for effective communication with all key parties in the workflow, i.e. both financial advisors and compliance officers. Insights proposed include focusing on the need of the clients (financial advisors) first and avoiding any introduction of a process that interferes with the relationship between the advisor and compliance officer. The session was effective as most of the participants found the discussion insightful, particularly in solving their problem. However, it was suggested that additional conversations with compliance officers would help to further understand their needs and pain points. The meeting did not include any direct mentions of Xano, WeWeb, FlutterFlow, Zapier, Make, Integromat, Outseta, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, or AI21.
(Source: Office Hours 2/17 )
