Ryan (ryan@themedialab.agency)
2024-01-05 10:46:28

Focus Litigation Solutions Facebook Page Management History

Screen Shot 2024-01-04 at 5.24.47 PM.png
Ryan (ryan@themedialab.agency)
2024-01-05 10:47:16

Focus Litigation Solutions Facebook Business Manager & Facebook Page IDs

Screen Shot 2024-01-04 at 5.14.28 PM.png
Ryan (ryan@themedialab.agency)
2024-02-10 12:08:49

On the call, here is the latest cheat sheet on SL financials, I just updated it.

Shield Financials Calculations ```Gross Spend = dailyspend + cccost + agency_fee

Gross Revenue = daily_revenue

Gross Spend = dailyspend + cccost + agency_fee

COGS = dailyspend
+ cccost
+ agencyfee
+ mbcommission
+ sales_commission

Total Expense = dailyspend -- COGS & gross spend + cccost -- COGS & gross spend + agencyfee -- COGS + mbcommission -- COGS + salescommission -- COGS + operationexpense

Gross Profit = dailyrevenue - dailyspend - cccost - agencyfee

Gross Profit COGS = dailyrevenue - dailyspend
- cccost
- agencyfee
- mbcommission
- salescommission

Flatirons Overhead ** = VSS fees + CSP + MRT = Total Flatirons Post Retainer Services / by mediarawv2 row count where customer LIKE '%Flatirons%' per month. Update Looker shield_legal model file.

** Is added to External Total Expense, Combined Total Expense and subtracted from External Net Profit, Combined Net Profit, Combined Cash Flow

Net Profit = dailyrevenue - dailyspend
- cccost
- agencyfee
- mbcommission
- salescommission - op_expense

Cash Flow = enetprofit (Shield) - itotalexpense (TC)```

Ryan (ryan@themedialab.agency)
2024-03-13 13:19:11

added an integration to this channel: Fireflies.ai

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-13 17:44:56

Title: DBT Codev Date: Wed Mar 13 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, mike.taluc@bytecode.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 100.00 mins

Overview • The meeting commenced with a discussion among *Mike Taluc, Ryan Vaspra, and Brian Hirst. They touched on their locations before transitioning to the company's remote work policy and an upcoming event in Nashville. Mike* detailed organizing models in DBT using folders for source, intermediate, and analytics tables within the Conex folder, clarifying the distinctions between the folders to aid in better organization.

• *Ryan* inquired about the purpose of DBT jobs, which *Mike* explained are used to build models within specific environments with job dependencies. The workflow for deploying code from development to staging and production was also addressed, emphasizing the need for testing in staging before production. They discussed the Git process for merging changes from staging to the main branch.

• The discussion further explored additional branches for developers' work zones and organizing SQL files based on data sources and transformations. *Mike and Ryan agreed on the benefits of this approach in identifying individual developers' work. Mike* clarified the purpose of intermediate folders in DBT projects, noting that the "intermediate" folder encompasses computed fields or transformations beyond raw source data, progressing towards analytics.

• Overall, the meeting centered on deploying DBT models across various environments, including job scheduling, Git branching strategies, SQL file organization, and the role of folders in a DBT project structure. The dialogue shed light on understanding how models are developed, tested, and deployed, emphasizing collaboration and organization within the DBT framework to ensure smooth transitions between development stages.

Action Items • *Mike Taluc*

• Create a job in the production environment (1:19:48)

• Run the staging test job (1:19:59)

• *Ryan Vaspra*

• Have Luke set up his IDE environment to his own branch (1:28:29)

• Validate staging datasets and push changes to main for production deployment (1:21:05, 1:21:20)

• Create a merge request from staging to main in GitLab for production deployment (1:22:17)

Outline Chapter 1: Organizing Data Structure and Models (04:43 - 15:25)

• 04:43: *Mike Taluc* explains the organization of data structure and the purpose of the meeting.

• 06:10: *Mike Taluc* mentions the Conex data as the starting point for the demonstration.

• 07:16: *Mike Taluc* points out the organization of the data and shows how he has commented it out for demo purposes.

• 09:32: *Mike Taluc* discusses the sources for the user schema, interaction schema, and voice schema.

• 11:01: *Mike Taluc* explains the process of generating a model by copying and pasting.

• 14:57: *Mike Taluc* demonstrates the folder structure for organizing the data.

Chapter 2: Understanding the Purpose of Intermediate and Analytics Data (16:13 - 29:22)

• 16:13: *Ryan Vaspra* comments on the analytics and intermediate folders within the data structure.

• 17:41: *Ryan Vaspra* states the goal of building transforms for an agent call performance report.

• 19:00: *Nick* explains the concept of source being raw, intermediate being staging, and analytics being final.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-13 17:44:56

• 21:53: *Nick asks for confirmation from Mike Taluc* about his understanding of the concept.

• 23:43: *Mike Taluc agrees with Nick's* explanation.

• 26:35: *Ryan Vaspra* summarizes the folder structure and the purpose of each level.

• 27:30: *Ryan Vaspra* emphasizes the importance of understanding the purpose of each level.

• 29:22: *Ryan Vaspra seeks to discuss further with Mike Taluc* to clarify any remaining questions.

Chapter 3: Incremental and Batch Processing (43:42 - 51:05)

• 43:42: *Mike Taluc* introduces the concept of incremental materialization for a specific model.

• 44:22: *Mike Taluc* includes comments to guide the process of incremental materialization.

• 46:26: *Mike Taluc* mentions that the example is referring to the conference calls log.

• 47:10: *Ryan Vaspra* discusses the scenario of updating data every minute during a call.

• 49:56: *Ryan Vaspra* mentions the batch running at a specific time.

• 51:05: *Ryan Vaspra* considers the business case for the incremental and batch processing.

Chapter 4: Production Data and Scheduling (1:08:33 - 1:19:53)

• 1:08:33: *Nick* raises the topic of scheduling and its impact on running processes.

• 1:09:13: *Mike Taluc* mentions the availability of integrated scheduling.

• 1:10:20: *Mike Taluc* states that there are only 20 minutes left for the discussion.

• 1:18:21: *Mike Taluc* clarifies that the data will be written to the production dataset.

• 1:19:29: *Ryan Vaspra* acknowledges the production job example and asks for further clarification.

Chapter 5: Dashboard Models and Data Flow (1:15:57 - 1:27:28)

• 1:15:57: *Ryan Vaspra* mentions the existence of staging, dashboard model files, and production dashboard model files.

• 1:18:44: *Ryan Vaspra describes the data as production data and confirms with Mike Taluc*.

• 1:22:05: *Ryan Vaspra* seeks confirmation about the data flow and the process from source to analytics.

• 1:23:45: *Ryan Vaspra* asks about the relationship between staging and five tran.

• 1:25:22: *Mike Taluc* explains that staging allows for examining the results of changes.

• 1:31:40: *Mike Taluc* mentions the use of brackets in the configuration block.

Chapter 6: Summary and Continuing Learning (1:29:28 - 1:40:08)

• 1:29:28: *Mike Taluc* agrees that the discussion has been helpful.

• 1:29:34: *Ryan Vaspra expresses the intention to follow up with Mike Taluc* for further learning.

• 1:29:47: *Ryan Vaspra suggests Nick* to organize and show the setup for better understanding.

• 1:30:48: *Mike Taluc* confirms the name "tip analytics" for staging.

• 1:34:31: *Mike Taluc* emphasizes the importance of understanding the concepts contextually.

• 1:36:43: *Mike Taluc* explains that analytics is more than just raw data.

• 1:39:33: *Ryan Vaspra* mentions the plan to experiment with Connects One and reach out with questions.

• 1:40:08: *Mike Taluc* ends the conversation with a confirmation.

• Note: This outline is a summary of the transcript and may not cover all the details and nuances of the conversation.

Shorthand Bullet • ✏️ *Demo of Data Organization*

• - Mike Taluc did some organization for the demo purposes.

• - He commented out the data to show the organization.

• - He also pulled in the conference calls log.

• - Intermediate models should be organized in a specific folder structure.

• - Final models should be in a separate folder for analysts to access.

• - Formatting and additional analytics can be done in the "more analytics" stage.

• ✏️ *Adding Columns*

• - Ryan Vaspra mentioned the need for a "billable" boolean column and a "terminal" column.

• - He created new columns called "billable rate" during the screen share.

• ✏️ *Lead ID and Billable Status*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-13 17:44:56

• - Nick suggested using a Google Sheet with the Lead ID and billable status.

• - Mike Taluc agreed with this suggestion.

• ✏️ *Business Case Alignment*

• - Ryan Vaspra emphasized the importance of aligning with the business case.

• - He mentioned the challenge of filling out 500 questions.

• - The talk time in the log table was discussed.

• ✏️ *Incremental Model*

• - Mike Taluc explained that the conference calls log is an incremental model.

• - Multiple models can be created, such as model one and model two.

• ✏️ *Production Job Example*

• - Ryan Vaspra mentioned a production job example.

• - Mike Taluc confirmed the existence of such a job.

• ✏️ *Understanding Concepts*

• - Ryan Vaspra expressed the need to understand all the concepts.

• - He mentioned struggling to listen and learn at the same time.

• ✏️ *Information Schema*

• - Mike Taluc mentioned using the information schema frequently.

• ✏️ *Organizing SQL Code*

• - Mike Taluc discussed organizing SQL code with brackets and config blocks.

• ✏️ *Useful SQL*

• - Useful SQL was mentioned as a topic of interest.

• ✏️ *Learning and Experimenting*

• - Ryan Vaspra expressed the intention to fiddle around with the code and learn more.

• - He mentioned reaching out with more questions.

• ✏️ *Next Steps*

• - Mike Taluc confirmed the need for further questions.

• - Ryan Vaspra mentioned another meeting he needed to attend.

• - He expressed the intention to write and learn Connects One.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-14 13:56:12

Title: Looker Dev user experience testing Date: Thu Mar 14 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, luke@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 112.00 mins

Overview • The meeting commenced with *Ryan Vaspra discussing his experience with DBT and the challenges faced in understanding deep models and folder organization. Brian expressed difficulty in grasping certain concepts following Michael's training. Ryan* then delved deeper into DBT, addressing issues with column spacing in YAML files and distinguishing between application tables and business analytics models.

• Subsequently, *Ryan* proposed using Fivetran to import historical data into BigQuery, considering connecting Postgres databases for better integration. Shifting focus to Looker Enterprise dashboards, permission issues were resolved by assigning proper roles. The discussion emphasized leveraging DBT effectively for data modeling and migrating data to platforms like BigQuery, ensuring seamless visualization access through Looker Enterprise.

• The meeting also involved *Luke Fontaine and Brian Hirst*, discussing tasks such as accessing folders, permissions, and embedding URLs for dashboards. They explored utilizing Data Studio for creating dashboards, addressing limitations and scheduled email deliveries for client views. Future plans included building an AI commercial app using Looker API data, considering an enterprise API over buying licenses for cost efficiency.

• *Ryan* proposed a collaboration with *Luke* to enhance dashboard aesthetics using Data Studio and BigQuery connectors, along with creating new system tables under an analytics branch folder. They touched on issues related to mobile app item resizing, database pipelines, rebuilding dashboards, maintaining user access rights while switching platforms, and scheduling automatic daily emails for views. Discussion also ensued on naming conventions for client-facing dashboards, ensuring synchronization across systems by matching advertiser IDs.

Action Items • *Ryan Vaspra*

• Refresh screen (01:05)

• Log in (01:10)

• Open daily summary (01:10)

• Click on the three dots where it refreshes (01:10)

• Click on get embed URL for dashboard embedding (01:10)

• *Brian Hirst*

• Log in to the app (01:20)

• Try downloading a file and check how it looks like (01:21)

• *Luke Fontaine*

• Test out scheduled delivery of views via email (1:13)

Outline Chapter 1: Understanding the Daily Grind Routine (02:00 - 04:20)

• 02:00: *Ryan Vaspra* mentions that he has been focusing on the daily grind routine in preparation for the transformations call.

• 02:49: *Ryan Vaspra* expresses confusion about organizing folders and relates it to branches.

Chapter 2: Schema Meetings and Work Sessions (04:20 - 08:18)

• 04:26: *Brian Hirst* expresses difficulty in following along with the previous discussion.

• 05:17: *Ryan Vaspra* offers to show what he has learned.

• 06:16: *Ryan Vaspra* explains that restarting the interactive development environment is a lesson learned from the previous day.

• 08:18: *Ryan Vaspra* discusses the structure of the schema YAML and the importance of proper formatting.

Chapter 3: User Testing and Data Visualization (08:23 - 21:41)

• 10:28: *Ryan Vaspra* encounters an issue with highlighting the commentary component.

• 11:45: *Ryan Vaspra* suggests a YAML format for the schema.

• 21:27: *Ryan Vaspra* mentions the use of split tabs and running code to visualize data.

Chapter 4: Dashboard and Analytics Views (23:22 - 26:12)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-14 13:56:12

• 23:22: *Ryan Vaspra* refers to useful examples in PG admin and Shield for creating dashboard views.

• 25:57: *Ryan Vaspra* mentions the staging environment.

• 26:43: *Luke Fontaine* asks about other topics covered besides database accessibility.

Chapter 5: Model Development and Data Transformation (31:27 - 37:00)

• 31:38: *Ryan Vaspra* discusses the final piece of model development and the number of columns needed.

• 33:08: *Ryan Vaspra* mentions a specific time zone (Pacific Time) in relation to a step in the development process.

• 35:26: *Ryan Vaspra* emphasizes the importance of a specific step in model development.

• 37:00: *Ryan Vaspra* discusses the alignment of staging and production environments initially.

Chapter 6: Data Migration and Dashboard Rollout (37:12 - 43:12)

• 37:25: *Ryan Vaspra* asks about the best way to migrate data from the old system to the new system.

• 39:11: *Ryan Vaspra* mentions the need to start building the dashboard for Shield once enough data is available.

• 43:12: *Brian Hirst* mentions two things to address before starting.

Chapter 7: Dashboard Configuration and User Roles (43:31 - 48:52)

• 43:31: *Brian Hirst* mentions two tips regarding analytics and email communication.

• 48:52: *Luke Fontaine* acknowledges the information shared.

Chapter 8: Financial Details and Summary (52:18 - 57:56)

• 52:53: *Ryan Vaspra* suggests looking at financial files for further information.

• 54:37: *Ryan Vaspra* proposes sending emails to specific user groups.

• 57:56: *Ryan Vaspra* refers to a specific board and suggests action.

Chapter 9: User Permissions and Group Management (1:00:04 - 1:02:42)

• 1:00:39: *Ryan Vaspra* suggests creating a new group with no roles assigned.

• 1:01:09: *Ryan Vaspra* confirms the suggestion.

• 1:02:42: *Ryan Vaspra* refers to a specific financial group.

Chapter 10: Data Analysis and Reporting (1:02:58 - 1:08:37)

• 1:05:12: *Ryan Vaspra* suggests a specific action related to data analysis.

• 1:06:01: *Ryan Vaspra* addresses a specific person (Luke) regarding data analysis.

• 1:08:37: *Ryan Vaspra* concludes the chapter with agreement.

Chapter 11: External Dashboards and Naming Conventions (1:09:19 - 1:19:48)

• 1:14:42: *Ryan Vaspra* discusses the need for consistent naming conventions.

• 1:18:08: *Ryan Vaspra* suggests how to present summary and details in the dashboard.

• 1:19:48: *Ryan Vaspra* mentions the timing for implementing client-facing dashboards.

Chapter 12: Integration and Platform Configuration (1:23:25 - 1:28:36)

• 1:26:54: *Ryan Vaspra* mentions the need to create drill-down functionality.

• 1:28:19: *Ryan Vaspra* mentions browsing Conx one and its configuration.

• 1:28:36: *Ryan Vaspra* suggests writing report dashboards for a specific project.

Chapter 13: Vertical Integration and Data Configuration (1:29:22 - 1:40:47)

• 1:30:01: *Ryan Vaspra* mentions setting up new verticals and tables.

• 1:35:00: *Ryan Vaspra* discusses the importance of field configuration and data mapping.

• 1:38:47: *Ryan Vaspra* suggests using an intermediary folder for pre-transformation needs.

• 1:40:03: *Ryan Vaspra* discusses the process of retrieving rates and transforming data.

• 1:40:47: *Brian Hirst* asks about the estimated time for a specific task.

Shorthand Bullet • 📂 *Folder organization*

• - Ryan Vaspra struggled to understand the organization of folders in relation to branches.

• - Mentioned the need to catch Luke up during schema meetings for serious work sessions.

• - Talked about the importance of understanding the interactive development environment and playing around in different environments and branches.

• 🔍 *User testing*

• - Ryan Vaspra mentioned starting user testing.

• - Indicated the use of GitHub from the command line for basic checks.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-14 13:56:12

• - Mentioned using the yellow tip browser to access the tip project.

• - Highlighted the need to restart the interactive development environment.

• - Discussed the importance of properly formatting the schema YAML for it to become clickable.

• 🔀 *Branches and merges*

• - Mentioned the process of creating a pull request.

• - Stressed the importance of being careful when merging.

• - Confirmed the need to confirm the merge.

• 📝 *Schema and tables*

• - Discussed the importance of properly aligning columns in the schema YAML for it to become markup language.

• - Talked about creating a YAML format with a hyphen, space, name, and colon.

• - Emphasized the importance of the most important step in model development.

• 📊 *Data organization*

• - Discussed the need for a unified raw SQL table, financial rows, and analytics map view details.

• - Mentioned staging as another aspect of data organization.

• - Luke Fontaine asked about other additional aspects of data organization.

• 📧 *Email notifications and user access*

• - Mentioned the possibility of scheduling and making notifications dependent on others.

• - Discussed the process of creating drill-down capabilities.

• - Brian Hirst asked about the appearance of the email notifications.

• - Discussed the possibility of sending hourly emails in the interim.

• 📉 *Dashboard and order information*

• - Discussed using Copper for order information on the summary tab of an external dashboard.

• - Mentioned the use of media raw v2 and financial view details tables to create order summary and order details.

• 💻 *Client-facing dashboards*

• - Talked about the need to configure Conx one and understand its usage in metadata, CRM business settings, user, and dialers.

• - Mentioned the possibility of creating call report dashboards for TIP.

• 📝 *Naming conventions*

• - Discussed the naming conventions for ruler and leadspedia.

• - Asked about the reason for not having the exact same format for both.

• 🔐 *User access and security*

• - Discussed the process of granting access to viewers.

• - Mentioned the need to edit groups.

• 💡 *Ideas and future plans*

• - Mentioned the goal of showing a lady during the Copper meeting what has been done.

• - Discussed the process of combining custom fields with hyphens.

• - Talked about the media buyer table and the need to mimic tables in spreadsheets.

• - Discussed the use of SQL and the process of building up to more complex SQL.

• ✅ *Wrap-up*

• - Mentioned the need to create look files and understand how to create drill-downs.

• - Discussed the possibility of Brian Hirst showing a layman's browsing of Conx one.

• - Luke Fontaine mentioned a conversation with Mark Menawara about naming conventions.

• - Ryan Vaspra mentioned the goal of showing the lady what has been done during the Copper meeting.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-19 11:29:28

Title: Crump Local Services Review Date: Tue Mar 19 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@themedialab.agency, lee@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 15.00 mins

Overview • The meeting started by focusing on finalizing the setup for *Dallas* and Houston local service accounts. Ryan Vaspra** mentioned that both locations are fully approved and pending a switch in categories to auto accidents and personal injury. The team ensured smooth operations by discussing tracking numbers testing for service accounts.

• *Cameron Rentch* stressed the importance of limiting raw calls to 40 per day during business hours for inbound calls, planning incremental weekly increases by 10%. Geotargeting strategies were discussed to target areas like Dallas DMA, Houston DMA, Texas state, San Antonio, and Austin specifically to optimize local auctions gradually based on performance metrics.

• The team outlined a timeline aiming for live activation by April 1st, leveraging overflow from national branding to supplement local campaigns effectively. Plans included aligning schedules with inbound reps' availability to maximize response efficiency during operational hours. Aligning bidding strategies with performance goals was crucial.

• In conclusion, tasks were assigned for further coordination with Tony regarding inbound representatives' scheduling details for successful campaign launches. The importance of aligning all aspects of implementation was highlighted to ensure the campaigns' success. Monitoring budgets and bidding strategies would be done carefully as call volumes increase incrementally.

Action Items • *Ryan Vaspra*

• Confirm receiving number (09:10)

• Test numbers and confirm auto accidents only (09:14)

• Verify tracking and auto categories, 40 calls per day on weekdays (12:40)

• *Lee Zafra*

• Get with Tony to understand inbound reps' work schedule (13:01)

• Ensure correct hours for weekday operations from Tony (12:31)

Outline Chapter 1: Account Setup and Functionality (02:18 - 05:22)

• 02:18: Discussion on local service accounts setup for turning on ads.

• 03:30: Overview of the setup readiness for Dallas and Houston locations.

• 05:15: Emphasis on activating accounts for Dallas and Houston on the same day.

Chapter 2: Call Handling and Budget Management (05:22 - 07:30)

• 05:22: Limit set for handling raw calls per day without failure.

• 06:33: Importance of aligning call handling with business hours and scheduling.

• 07:27: Strategy for budget management and gradual call volume increase.

Chapter 3: Geo-Targeting and Ad Campaign Setup (09:39 - 11:47)

• 09:39: Discussion on targeting Dallas DMA, Houston DMA, and Texas for ads.

• 10:58: Importance of layering geo-targeting for effective ad placement.

• 11:33: Confirmation of categories setup and readiness for ad campaigns.

Chapter 4: Call Volume Management and Expansion (12:56 - 15:39)

• 12:56: Commitment to wrap up setup by the end of the day.

• 15:09: Readiness for handling overflow of branding and call volumes.

• 15:09: Affirmation of preparedness for upcoming actions and campaigns.

Shorthand Bullet • 🔑 *Summary of Key Meeting Points*

• - *Local Service Accounts Setup*

• - Ryan* Vaspra* and Lee Zafra** discussed the setup of local service accounts for turning on ads.

• - Emphasized the need for verification and readiness.

• - *Tracking Numbers and Testing*

• - Ensured tracking numbers were in place and tested for functionality.

• - *Inbound Calls Management*

• - Maximum of 40 raw calls per day without failure.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-19 11:29:28

• - Calls only accepted during business hours and managed by the BCL inbound team.

• - Incremental increase of call volume by 10% weekly.

• - *Geotargeting Strategy*

• - Targeting Houston City, Houston DMA, and the state of Texas.

• - Advised on the importance of specific geo-targeting.

• - *Budget and Call Volume Management*

• - Initially set a budget and call limit of 40 calls per day, increasing by 10% weekly.

• - Adjusted bids and budgets based on performance.

• - *Live Launch Timeline*

• - Aimed to be live with the campaign by 1st April, with potential for an earlier launch.

• - *Post-Call Actions*

• - Confirmation of tracking and auto categories, and coordination with Tony for inbound call reps' schedules.

Ryan (ryan@themedialab.agency)
2024-03-20 22:31:26

Got it, thanks for the authority to keep on all these projects.

the new hire for Integrations needs to be 100% helping retainer clients for SL orders requiring integrations period no matter what Mike tells her , you can let Shellie know if you want or I will.

Mike has to focus on TT and FB and stop worrying about process management crap. I’ll hold his damn proverbial hand and manage him to be proactive on TT final testing with TT team, then push him on FB.

His apps need to be easy enough for Mark Hines or Mark Maniora to setup.

Lastly Nick , who needs to focus more on our TIP pipelines and SL pipelines, then we can solve a lot of this in scale with Google Cloud products.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 11:14:52

Title: JA - mid month commission review Date: Fri Mar 22 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: jack@themedialab.agency, cameron@themedialab.agency, debora@shield-legal.com, altonese@accountingdept.net, ryan@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 10.00 mins

Overview • *Ryan Vaspra* discussed *commissions and revenue* with *Jack Altunyan, clarifying Jack's commission amount at $49,155.54 based on February commissions and daily revenue reaching 2 million. Ryan stressed the importance of proper setup for rejection events and requested help to ensure correct esign and rejection event setups in live systems, involving Mike if adjustments are necessary. This focus shift prioritizes tasks related to Facebook and TikTok integrations over client interactions, aligning with directives from Cameron*.

• The meeting concluded with both parties acknowledging a positive outlook for the year ahead despite upcoming tasks. They affirmed dedication to continued progress and collaboration, aiming to achieve shared objectives while adapting to evolving team priorities. The mutual understanding reached ensures a focused approach to navigating challenges and opportunities as they arise within the dynamic of the team.

• *Ryan's* commitment to prioritizing key projects signifies a strategic shift towards maximizing impact. Involving *Mike for potential adjustments in live systems demonstrates a proactive approach to optimizing operations. By aligning with Cameron's* directives, the team aims to streamline efforts efficiently and effectively, leveraging resources for enhanced project outcomes.

• The collaborative focus on achieving shared objectives reflects the team's dedication to success amidst evolving priorities. Maintaining a positive outlook and commitment to progress ensures a cohesive approach to managing responsibilities and opportunities. This collective agreement underscores a united effort towards driving growth and achieving milestones in line with the team's dynamic environment.

Action Items • *Ryan Vaspra*

• Make sure both esign and rejection events are set up for currently live IDs (06:09)

• Provide the IDs of events that aren't set up (06:21)

Outline Chapter 1: Financial Performance Review (03:37 - 05:26)

• 03:37: Ryan provides Jack with the February commissions and total revenue figures.

• 05:15: Jack's commission amount is calculated and confirmed to be $49,155.54.

Chapter 2: Operational Updates and Task Assignments (05:42 - 06:47)

• 05:42: Ryan discusses the need to ensure rejection events are properly set up for certain IDs.

• 06:24: Jack agrees to review and share the necessary IDs for adjustments.

Chapter 3: Project Prioritization and Team Support (06:27 - 07:09)

• 06:27: Ryan emphasizes the importance of focusing on Facebook tasks for Cameron's priority.

• 06:59: Ryan and Jack conclude the discussion on a positive note, looking forward to the upcoming period.

Shorthand Bullet • 📊 *February Commissions*

• - Ryan Vaspra reported February commissions as $39,155.54.

• - *Total commission for *Jack is $49,155.54.**

• - Clarified breakdown of commission for hitting daily revenue milestones.

• 🔧 *Setting Up Rejection Events*

• - Ryan requested IDs from Jack and team to ensure rejection events are properly set up.

• - Emphasized the importance of having both esign and rejection events configured for live or intended events.

• 📱 *Prioritizing Facebook* and TikTok**

• - Ryan highlighted the need to focus on Facebook and TikTok tasks for Cameron.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 11:14:52

• - Mentioned redirecting efforts towards these tasks over client integrations to meet priorities.

• 🚀 *Year Outlook*

• - Ryan expressed optimism about the upcoming year's outlook.

• - Encouraged everyone to keep up the good work and maintain momentum.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 11:29:49

Title: JV - mid month commission review Date: Fri Mar 22 2024 12:15:00 GMT-0400 (Eastern Daylight Time) Participants: cameron@themedialab.agency, ryan@shield-legal.com, john@themedialab.agency, altonese@shield-legal.com, debora@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 10.00 mins

Overview • *Ryan Vaspra* discusses *Camden's typical revenue cycle, with slow January starts building up to peak performance in March-May, followed by a dip in August. He foresees increased activity ahead with visits and conventions. Ryan aims for a significant increase in contracts signed per day at Camden, which intensifies the team's workload. The growth impacts the team directly as Camden pursues expansion efforts. The conversation shifts to John's first commission of $2,512.86 for the year. Despite not being a top performer, John's role in managing remote users and business managers within media buying networks is crucial. Concerns are raised about John's commitment level due to potential side ventures like affiliate marketing. Doubts exist regarding his long-term dedication to Camden among other ventures. Plans are made for a discussion regarding Maximus, emphasizing punctuality expectations among attendees like Brian Thiessen* within their professional circle at Camden.

Action Items • *Ryan Vaspra*

• Set up workstation in the office (05:45)

• *John*

• Check if there are any commissions (05:35)

Outline Chapter 1: Budgeting and Performance Trends (03:44 - 05:35)

• 03:44: Discussion on budgeting process and the impact on business performance throughout the year.

• 04:31: Performance trends highlighted, with slow January and peak performance in March, April, May.

• 05:07: Mention of upcoming hectic times, visits, and conventions for next month.

Chapter 2: Business Growth and Commission Updates (05:50 - 07:06)

• 05:50: Mention of business growth initiatives and increase in daily contract signings.

• 06:10: John's commission amount of $2,512.86 announced, reflecting business activity.

• 06:53: John's value to the company beyond performance discussed by Ryan.

Chapter 3: Employee Dynamics and Commitment (07:27 - 07:58)

• 07:27: Discussion on John's commitment level and involvement in other ventures.

• 07:37: Reference to Caleb's fluctuating commitment and John's similar behavior.

• 07:58: Meeting reminder for Maximus, emphasizing punctuality and professionalism.

Shorthand Bullet • 📊 *Budget Planning*

• - *Ryan Vaspra* mentioned that budgets for the next year in big companies, like Camden, are typically not finalized until January.

• - January tends to be slow, but performance peaks in March, April, and May.

• 📈 *Business Growth*

• - Camden is aiming to increase the number of contracts signed per day from 200 to 300 or 400.

• - This growth strategy impacts employees like *John and Debbie*.

• 💰 *Commissions*

• - *John* received his first commission of the year, totaling $2,512.86.

• - Despite not being a top performer, *John* is valued for his other contributions.

• 👥 *Employee Insights*

• - *Ryan Vaspra* shared background information about *John* and his role in managing remote users and media buyers.

• - *John* is also an affiliate marketer with other side hustles.

• 📅 *Meeting Schedule*

• - *Ryan Vaspra* planned to reconvene with *Brian Thiessen* for a meeting in seven minutes to discuss Maximus.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 11:51:27

Title: ML - mid month commission review Date: Fri Mar 22 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: maximus@themedialab.agency, cameron@themedialab.agency, ryan@shield-legal.com, debora@shield-legal.com, altonese@accountingdept.net, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 17.00 mins

Overview • The meeting began with *Brian Thiessen commending Maximus Lynn for his punctuality. Maximus raised concerns about technical issues when connecting laptops. Ryan Vaspra* presented revenue figures and discussed plans with TikTok and Facebook, stressing accurate event tracking.

• *Cameron Rentch* addressed lead status issues and system synchronization challenges, focusing on updating leads' statuses accurately. Ryan highlighted difficulties faced with TikTok bugs and the importance of proper event setup. Maximus shared struggles with technical issues on Facebook and TikTok, aligning with Ryan's experiences.

• Concerns raised by Maximus and Ryan regarding technical challenges on Facebook and TikTok were echoed. Cameron discussed improvements in the form creation process to enhance lead quality filtering. The ongoing discussions centered on operational challenges in lead management systems, platform performance, and enhancing data accuracy for marketing campaigns across social media platforms like TikTok and Facebook.

Action Items • *Maximus Lynn*

• Follow up on St. Pierre and the forms for Mike and Mel (14:03)

• Add a new question regarding last ten years diagnosis to Facebook form (14:40)

Outline Chapter 1: Initial Project Discussion and Challenges (01:22 - 05:08)

• 01:22: Brian Thiessen mentions Maximus's punctuality.

• 03:08: Discussion about challenges faced with turning off something.

• 05:08: Reference to starting work early in the morning.

Chapter 2: Transition to E-sign Events (05:13 - 07:29)

• 05:13: Transition to discussing events related to E-sign and Facebook.

• 06:03: Plans to pivot to E-sign events.

• 07:29: Explanation about the complexities of tracking leads and statuses.

Chapter 3: Lead Management and Process Optimization (08:00 - 09:10)

• 08:00: Discussion on daily lead handling processes.

• 09:10: Clarification on lead status updates and final endpoints.

Chapter 4: Technical Challenges and Feedback (11:58 - 13:34)

• 11:58: Challenges related to system functionality.

• 13:34: Mention of varying success rates between TikTok and Facebook campaigns.

Chapter 5: Form Creation and Lead Filtering (14:03 - 16:37)

• 14:03: Maximus suggests creating additional forms for lead filtering.

• 15:43: Maximus emphasizes the importance of adding a specific question for lead quality improvement.

• 16:37: Conclusion and agreement on implementing the new question for filtering.

Shorthand Bullet • 📊 *Maximus Lynn's Campaign Updates*

• - **Restarted TikTok campaign with new content

• - Planning to create additional forms for Mike and Mel**

• 📈 *Discussion on CRM Events and System Issues*

• - **Challenges with CRM events not opening properly

• - Trying to resolve issues with Jake**

• 🔧 *Form Creation for Filtering Leads*

• - Maximus Lynn requests new two-form question for better lead filtering

• - Process involves Mike creating, Brian adding, and Mike connecting the question

• 🚀 *Overall Positive Feedback and Encouragement*

• - Good month acknowledged by Cameron Rentch and Ryan Vaspra

• - Encouragement for Maximus Lynn's performance in February

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 11:58:24

Title: Caleb (mid month commission call) Date: Fri Mar 22 2024 12:45:00 GMT-0400 (Eastern Daylight Time) Participants: debora@shield-legal.com, ryan@shield-legal.com, altonese@accountingdept.net, cameron@themedialab.agency, caleb@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 10.00 mins

Overview • *Ryan Vaspra* reviewed the February revenue, noting a decline in profits, potentially the worst month of the year. *Caleb Peters* noted improvements compared to last year but mentioned ongoing challenges. They discussed collaborating with Mike on marketing strategies for TikTok and Facebook, focusing on setting up ad accounts correctly for effective campaigns.

• *Cameron Rentch* discussed upcoming calls and platform performance assessment for future advertising decisions. *Caleb Peters* sought advice on scheduling ads efficiently based on weekend results for Lejune's campaign. The team planned to optimize marketing strategies, ensuring event tracking and collaboration with Mike on social media platforms.

• The meeting concluded with tasks assigned, ongoing project clarifications, and a shared understanding of next steps among *Cameron Rentch, Ryan Vaspra, and Caleb Peters*. They aimed to work collaboratively towards enhancing marketing strategies for the company, reflecting an aligned approach to business optimization and efficient ad campaign management.

Action Items • *Ryan Vaspra*

• Coordinate with Mike to apply the business benefit of TikTok (03:48)

• Assist in setting up esign events on Facebook (03:58)

• Check ad accounts for initials and provide an inventory to Ryan (04:23)

• *Caleb Peters*

• Review all ad accounts and share them with Ryan (04:25)

• *Cameron Rentch*

• Attend a call at 2:30 pm today (05:15)

• Provide updates on any changes throughout the day (05:25)

• Analyze platform performance over the last few months to make decisions on advertising strategy (07:13)

Outline Chapter 1: Financial Performance Review (02:11 - 04:56)

• 02:41: Revenue for February is discussed, indicating a drop in commissionable profit compared to previous months.

• 03:48: Plans to work with Mike on leveraging TikTok and Facebook for business benefits are highlighted.

• 04:13: Emphasis on ensuring all ad accounts are set up correctly to track events and spending.

Chapter 2: Advertising Strategy Analysis (05:10 - 07:16)

• 05:15: Updates and changes in advertising strategies are discussed, focusing on platform performance analysis.

• 06:02: Strategies to optimize spending on platforms like Lejune are considered for better results.

• 07:13: Reviewing platform performance data to determine where to focus advertising efforts.

Chapter 3: Action Plan and Follow-Up (07:25 - 08:10)

• 07:42: Plans to analyze platform performance data to make informed decisions on advertising strategies.

• 08:01: Confirming readiness and alignment on tasks to improve advertising performance.

• 08:06: Wrap-up and acknowledgment of tasks to be handled, indicating further communication.

Shorthand Bullet • 📊 *February Revenue Report*

• - *Revenue for February*: $2,566,000

• - *Commissionable profit*: $50,976.7

• - Mention of a bonus commission of $10,000

• 📱 *Social Media* Strategy**

• - *Focus on TikTok and *Facebook:** Plans to leverage TikTok and switch to Facebook for eSign events

• - *Collaboration with *Mike: Ryan** working with Mike to optimize business benefits on TikTok

• 📈 *Ad Account Management*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 11:58:24

• - *Review of ad accounts*: Caleb to provide an inventory of all ad accounts

• - *Action items*: Set up events where needed, ensure proper tracking

• 🔄 *Platform Performance Analysis*

• - *Evaluation of platform performance*: Cameron analyzing platform performance to make decisions on ad spending

• - *Considerations for adjustments*: Determining where to increase or decrease ad spending based on platform performance

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 13:58:39

Title: Shield Orders fix Date: Fri Mar 22 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 26.00 mins

Overview • *Andy* discusses Firefly, a new AI tool, with *Ryan, impressed by its features for automating meeting summaries and follow-up emails. They plan to explore its capabilities further, with Ryan* showcasing its efficiency for managing tasks like updating APIs.

• *Ryan* shares business updates, mentioning funding received by *Cam*, leading to his busy schedule. He discusses bonding with investor David Diamond over their AI project, foreseeing potential investments due to positive relationships with stakeholders.

• In meeting discussions, *Ryan guides Andy* through data organization processes for active orders and payments using tools like Copper. They focus on accurate tracking of budgets and account manager assignments for projects while planning system enhancements.

• Together, they collaborate on data management related to active orders and payments within their system, ensuring meticulous tracking while planning future meetings and system improvements.

Action Items • *Andy Rogers*

• Check out the Firefly tool (09:59)

• Review the AI tool for sales meetings (11:56)

• *Ryan Vaspra*

• Invite members to join a meeting (11:31)

• Add budget details to an existing contract (22:20)

Outline Chapter 1: System Demonstration and Benefits (06:13 - 15:29)

• 06:13: *Ryan* demonstrates a system for automatic meeting summaries and API access.

• 10:46: The system automatically handles notes and updates for follow-up emails.

• 12:46: *Ryan* walks through database features for order status and management.

Chapter 2: Operational Processes and Training (17:07 - 22:56)

• 17:12: Discussion on improving operational processes for efficiency.

• 21:46: Collaboration on marking contracts for proper handling and training.

Chapter 3: Data Management and Quality Control (23:06 - 25:18)

• 23:06: Steps taken to ensure data integrity and reduce duplicates.

• 25:18: Instructions provided for using a specific sheet for order submissions.

Chapter 4: Future Plans and Company Scaling (25:27 - 26:14)

• 25:27: Acknowledgment of operational improvements for company scalability.

• 26:01: Plans for upcoming meetings and focus on company growth and development.

Shorthand Bullet • 📊 *AI Tool Features*

• - *Ryan Vaspra* showcased an AI tool used for meeting summaries and updates.

• - Automatically generates notes regarding discussed topics like API access and dashboard updates.

• - Allows for editing follow-up emails before sending, including profanity checks.

• 🔍 *Database Walkthrough*

• - *Ryan Vaspra* walked through a database, focusing on active orders and statuses.

• - Mentioned a total order budget of 400K.

• 📋 *Data Management*

• - Discussed organizing data for clarity, including removing duplicates and sorting for easy access.

• - Emphasized the importance of accurate data in the database for operational efficiency.

• 📅 *Upcoming Plans*

• - Planned a meeting involving training for *Debbie and Altense*.

• - Scheduled a follow-up meeting to invite *Kristen* and manage input effectively.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 14:15:56

Title: TT CRM Events Date: Fri Mar 22 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: mike@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 10.00 mins

Overview • *Ryan Vaspra* and *Mike Everhart discussed lead status synchronization issues between dialers and event setup for Maximus, and troubleshooting negative and positive events for Mike McKinney's campaign. They planned to reconvene next Tuesday to review progress despite Mike's tooth injury affecting availability. Ryan* mentioned investigating discrepancies in event tracking for leads generated through TikTok campaigns.

• *Ryan* detailed his efforts in ensuring proper setup for positive and negative outcomes related to leads from TikTok advertising. His data validation processes involved addressing complex issues in different accounts due to varying activity volumes. Towards the end, *Ryan expressed commitment to supporting Mike* by involving other team members from TikTok and Lark channels in tackling debugging tasks collaboratively across digital marketing operations.

• The collaborative approach aimed to collectively resolve technical hurdles, highlighting their teamwork ethos in problem-solving scenarios. *Ryan* shared insights into the validation processes undertaken, acknowledging the complexity of some accounts. Both parties concluded with gratitude for each other's contributions and a forward-looking plan of action for their follow-up session next week. The ongoing collaboration focused on addressing technical challenges in lead status synchronization and event setup, emphasizing the importance of teamwork in resolving issues within digital marketing operations.

Action Items • *Ryan Vaspra*

• Set up events for Maximus (00:59)

• Validate the issue with Mike McKinney's hair relaxer events (02:09)

• Investigate why there are zero total events for 316 to 322 on Mike McKinney's account (03:44)

• Check and test the positive event setup on TikTok for Mike McKinney's account (07:18)

• *Mike Everhart*

• Debug negative events and validate esign stuff for Mike McKinney's account (08:43)

Outline Chapter 1: Data Analysis Challenges (00:03 - 02:49)

• 00:03: Discussion on challenges with reconciling data from different sources.

• 00:20: Issue highlighted regarding syncing statuses between systems, impacting lead processing.

• 01:36: Focus on validating events related to specific campaigns like hair relaxer.

• 02:21: Efforts to investigate discrepancies in event tracking for specific campaigns.

Chapter 2: Troubleshooting Event Tracking (03:13 - 06:14)

• 03:13: Data analysis for a specific campaign, hair relaxer, between certain dates.

• 04:00: Identification of issues with event tracking and code setup.

• 06:14: Discussion on resolving issues with event tracking for the hair relaxer campaign.

Chapter 3: Debugging Negative Events (06:41 - 08:55)

• 06:41: Investigation into negative events related to disqualification for a campaign.

• 07:29: Confirmation of no signed e-signs for the campaign.

• 08:43: Plan to inform stakeholders about ongoing debugging of negative events.

Chapter 4: Future Actions and Follow-Up (08:59 - 10:11)

• 08:59: Plan to reconnect on Monday to review progress and findings.

• 09:25: Agreement to meet on Tuesday for a detailed update on event tracking.

• 10:11: Conclusion of the discussion and well wishes exchanged.

Shorthand Bullet • 📊 *Issues with Event Tracking*

• - *Ryan Vaspra* discussed difficulties in reconciling data between dialers, specifically related to CPAP leads.

• - Mentioned challenges with syncing statuses between Beachy dialer and Law Ruler.

• - Noted the delay in processing 100 sold leads for CPAP.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-22 14:15:56

• - *Ryan* worked on this from 06:00 a.m. to 08:00 a.m., trying to resolve the issues.

• 🔍 *Event Setup for Maximus*

• - *Ryan* requested setting up events for Maximus, emphasizing the need for proper configuration.

• - *Mike Everhart* was asked to check and set up the events.

• 🛠️ *Investigating Mike McKinney's Hair* Relaxer Campaign**

• - *Ryan* and *Mike* discussed issues with tracking events for Mike McKinney's hair relaxer campaign.

• - Discovered discrepancies in the event tracking for rejected and signed events.

• - *Mike* planned to debug the negative events and validate the e-signs for Mike McKinney's campaign.

• - Scheduled a follow-up meeting to review progress next Tuesday at 3 PM Pacific time.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-26 13:29:14

Title: TV Test Campaigns - (Maryland/LA County Juv Hall) Date: Tue Mar 26 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: tony@tortintakeprofessionals.com, craigs@acutabovemedia.com, mark@shield-legal.com, cameron@shield-legal.com, cschwarz@sonobi.com, kristopher@shield-legal.com, chris@shield-legal.com, swilcox@sonobi.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 25.00 mins

Overview • The meeting commenced with *Ryan Vaspra sharing extensive advertising experience from Madison Avenue, focusing on linear and connected TV buying strategies for lead generation optimization. Craig Schwarz stressed effective channel mix, attribution tracking, and audience targeting, discussing tiered pricing models and dayparting strategies to maximize impact within specific timeframes. Data analytics integration for lead tracking across CTV and online video display ads was highlighted, emphasizing meticulous steps towards campaign launch within tight timelines set by Cameron. The collaboration involved past digital results analysis and demographic insights shared by Kristopher Standley*, refining targeting methods strategically aligned with budget constraints for iterative optimization based on real-time metrics.

Action Items • *Ryan*

• Create a Google sheet with matrix for two markets and three numbers each (16:00)

• Send over top line stats data from early November last year (21:23)

• *Craig Schwarz*

• Compile a media plan presentation by Thursday for review (22:12)

• Confirm restricted hours needed for the campaign (24:54)

Outline Chapter 1: Initial Strategy Discussion (00:01 - 04:38)

• 00:01: Craig introduces the topic of linear buying and acknowledges Chris.

• 01:17: Craig addresses Chris regarding linear buying strategies.

• 03:18: Steve's role in account management buying planning and strategy is discussed.

Chapter 2: Proposal for Advanced Connected TV Network (04:38 - 11:02)

• 04:57: Ryan explains the proposal for an advanced connected TV network targeting specific audiences.

• 06:21: Discussion on the number of tracking numbers needed for the proposal.

• 08:27: Decision to simplify tracking numbers for ease of use.

• 09:18: Emphasis on developing a new marketing channel and discussing attribution.

Chapter 3: Campaign Execution and Tracking (11:15 - 17:23)

• 11:15: Explanation of creating a dashboard to track leads and their status.

• 13:09: Discussion on tracking and analytics data integration.

• 16:00: Planning to create a matrix for tracking markets and phone numbers.

Chapter 4: Channel Mix and Campaign Focus (17:43 - 21:37)

• 17:43: Decision on channel mix and focusing on CTV.

• 18:56: Clarification on linear TV inclusion in the campaign.

• 21:36: Urgency to be on air in ten days and planning media strategy.

Chapter 5: Finalizing Plans and Next Steps (21:44 - 25:34)

• 21:44: Discussion on finalizing media plan presentation and launch timeline.

• 22:32: Planning to review demo data and campaign progress.

• 24:39: Confirmation of campaign restrictions and working within set hours.

• 25:32: Agreement to collaborate and move forward with the plan.

Shorthand Bullet • 📊 *Campaign Strategy*

• - *Discussing the structure and targeting of the upcoming buy.*

• - *Planning on reviewing the KPIs and demographics spreadsheets with *Ryan and Chris.**

• 📱 *Lead Tracking and Attribution*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-26 13:29:14

• - *Planning to allocate budget and track leads for a four-week campaign.*

• - *Creating a dashboard to monitor leads through various stages.*

• 💡 *Optimizing Tracking Numbers*

• - *Considering using 800 numbers for different publications.*

• - *Discussing the use of prefixes for easy recall.*

• 📈 *Data Analysis and Reporting*

• - *Planning to analyze reach, traffic, and attribution for a comprehensive understanding of the campaign's performance.*

• 🚀 *Implementation Timeline*

• - *Aiming to finalize media plan by Thursday, sign off by Friday, handle pixels by Monday, and launch campaign by Tuesday or Wednesday.*

• 🔍 *Review and Follow-Up*

• - *Setting up a review of demo data to assess progress and plan future steps.*

• - *Confirming restricted campaign hours for planning purposes.*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-27 14:32:39

Title: TT CRM Events Funnel Training Date: Wed Mar 27 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: michaelmckinney@shield-legal.com, maximus@themedialab.agency, jack@themedialab.agency, parsa@shield-legal.com, mike@shield-legal.com, caleb@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 31.00 mins

Overview • The meeting began with *Ryan Vaspra explaining a configuration correction received from the TikTok team to enable custom event tracking within accounts. Mike Everhart* offered insights on updated UI challenges, while Ryan detailed steps for setting up funnels with an emphasis on event selection and optimization. The goal was to achieve 250 cumulative events across various types to enhance campaign effectiveness.

• Participants discussed addressing technical glitches and optimizing account setups as advised by TikTok, focusing on lead generation costs and event preparations for conversion goals. Ryan guided *Jack Altunyan* on creating and utilizing funnels effectively, stressing accurate event categorization for successful campaigns. Homework tasks included reviewing ad account status, creating appropriate funnels with guidance, and reporting readiness levels for scaling campaigns.

• Instructions highlighted the need for complete setup alignment with TikTok's KPI criteria before transitioning to active spending mode. Plans were made for video tutorial distribution and internal reporting procedures once funnel setups were validated by media buyers. Participants were encouraged to engage in preparing accounts for scaling readiness under Cameron's supervision before substantial advertising investment for TikTok campaigns.

• Overall, the meeting concluded with a focus on ensuring all necessary setups are complete for successful campaign launches. Active engagement in account preparation was highlighted as a crucial prelude before substantial advertising investment could commence. The importance of aligning setups with TikTok's KPI criteria and guidance from Ryan and Mike for effective funnel utilization were emphasized throughout the meeting.

Action Items • *Ryan Vaspra*

• Set up funnel events, ping me at any time (26:57)

• Create the conversion campaigns and select the optimization event (19:09)

• Check your ad accounts to see if they are ready for events or need setup (26:50)

Outline Chapter 1: Initial Setup and Event Overview (07:24 - 10:49)

• 07:24: Ryan Vaspra mentions the time needed for a task.

• 08:27: Discussion about adding more content.

• 08:46: Emphasis on making the video more interactive.

• 10:49: Introduction to the lesson starting.

Chapter 2: Data Sets and Event Management (10:02 - 14:28)

• 10:02: Mike Everhart provides a note on updated UI accounts.

• 10:16: Ryan Vaspra starts discussing data sets and overview.

• 12:55: Testing and perfecting a setup.

• 14:28: Clearing data and setting up the process.

Chapter 3: Funnel Setup and Optimization (15:11 - 19:20)

• 15:11: Ryan Vaspra talks about setting up events for the funnel.

• 16:01: Mike Everhart raises a question about selecting events.

• 18:01: Ryan Vaspra explains selecting suitable events for optimization.

• 19:20: Discussion on the optimization event for bidding.

Chapter 4: Campaign Creation and Recommendation (22:07 - 26:28)

• 22:07: Process of setting up a funnel for campaigns.

• 24:25: Discussing the importance of warming up for conversion.

• 26:28: Recommendation from TikTok on campaign creation.

Chapter 5: Action Steps and Homework (26:47 - 29:38)

• 26:47: Instructions for next steps in ad account analysis.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-27 14:32:39

• 28:38: Setting up a sample for validation.

• 29:36: Conclusion and remarks on the session.

Shorthand Bullet • 📊 *Setting up Funnel Events*

• - *Ryan Vaspra* explained the process of setting up funnel events in TikTok.

• - Events like contact attempts, appointments scheduled, and e-signs were discussed.

• - *250 events* in total are needed for the funnel to work effectively.

• 📈 *Creating Conversion Funnel*

• - After setting up events, users need to create a conversion funnel for lead generation.

• - *Events passed back from Law Ruler* are crucial for this process.

• - Conversion goals need to be aligned with the funnel created.

• 🚀 *Optimizing Ad Accounts*

• - Users were instructed to check their ad accounts for readiness to scale with the conversion funnel.

• - *Identifying accounts* that are ready for scaling was highlighted.

• 🔍 *Monitoring and Reporting*

• - *Cameron* is involved in the process of monitoring and approving the setup for scaling.

• - *Reporting back* on the readiness of accounts for conversion lead campaigns is essential.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-27 15:14:26

Title: Dev Team Admin Date: Wed Mar 27 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, nickmcfadden@shield-legal.com, jamesscott@shield-legal.com, luke@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 13.00 mins

Overview • *Brian* discusses increased workload due to campaign expansion, limiting contract assignments. *Luke empathizes but brings challenges faced by Mark. Despite setbacks, Brian shares recent event experiences. The focus shifts to surfing and golfing plans affected by weather. Brian mentions playing golf with an eccentric friend linked to advertising and Hollywood figures. Luke* shares friendships transcending age gaps based on shared interests, acknowledging generational camaraderie in activities like golfing. The conversation humorously touches on age perceptions among friends, emphasizing shared interests over age distinctions in evolving friendships without hindrances.

Action Items • *Brian Hirst*

• Train Mark Miniora for campaign work (01:12)

• Go golfing with John (06:37)

Outline Chapter 1: Unforeseen Busyness and Workload Increase (00:01 - 02:00)

• 00:10: Unexpected increase in workload due to multiple campaigns.

• 01:23: Challenges in training Mark to handle the workload.

Chapter 2: Personal Updates and Activities (02:04 - 06:37)

• 02:04: Luke's trip to New York and reconnecting with family.

• 04:43: Attending a soccer game with family.

• 06:37: Plans for golfing and spending time with friends.

Chapter 3: Unique Friendship and Recollections (08:19 - 12:23)

• 08:19: Brian's interesting friendship with John and their shared activities.

• 09:11: Brian's encounter with John and the job opportunity that followed.

• 12:00: Humorous exchange about age and friendship dynamics.

Chapter 4: Reflections on Age and Friendship (12:31 - 12:51)

• 12:31: Discussion on age differences and evolving friendships.

Shorthand Bullet • 📊 *Campaign Workload*

• - *Brian Hirst* experienced increased workload due to unexpected busyness.

• - One campaign expanded into six, resulting in six times the work.

• - Verticals posted by *Mark* needed to be assigned to contracts without double dipping.

• 🌟 *Personal Update*

• - *Luke Fontaine* shared positive experiences from a recent trip to New York and reconnecting with family.

• ⚽ *Soccer Game*

• - *Brian Hirst* attended a soccer game with a significant turnout.

• - Mentioned player *Alex Morgan* as a prominent figure in women's soccer.

• 🏌️‍♂️ *Golfing Plans*

• - *Brian Hirst* anticipated a golfing outing despite potential rain.

• - Mentioned a friend, *John*, known for entertaining stories and connections in the industry.

• :manandwomanholdinghands: *Friendship*

• - *Brian Hirst* highlighted common interests with friend *John*, emphasizing shared activities like golfing and socializing.

• 📚 *Memory of an Elephant*

• - *Brian Hirst* referenced a book titled "The Memory of an Elephant" written by an acquaintance.

• 🎓 *Career Transition*

• - *Brian Hirst* discussed transitioning to a media buying role after a chance encounter with a recruiter.

• - Shared details of meeting a recruiter and swiftly securing a new job opportunity.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-27 17:23:21

Title: Full Testing Date: Wed Mar 27 2024 18:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, ryan@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 19.00 mins

Overview • The meeting began with *Ryan Vaspra and Brian Hirst* discussing delivery methods in Law Ruler, focusing on testing web hooks and the necessity of testing with various phone numbers for caller identification compliance. They confirmed successful setup of delivery methods and conducted tests across different verticals, also emphasizing the importance of transmitting specific information like lead ID for call center use.

• Their conversation extended to the integration of Leadspedia and Law Ruler for handling leads from TV campaigns. *Ryan* aimed to streamline lead tracking within Law Ruler, proposing a dashboard tailored for enhanced visibility and control over lead progress. Plans were made to inform agents of changes stemming from TV campaign leads and the importance of collaboration to ensure successful integration.

• Further discussions revolved around sending campaign data to Law Ruler and the creation of new Slack channels for sharing updates. The meticulous planning included extensive testing with multiple phone numbers before finalizing the Leadspedia integration within Law Ruler. Overall, the collaboration emphasized improving workflow efficiency through automated procedures within their systems, illustrating a strategic approach to enhancing operational effectiveness.

Action Items • *Brian Hirst*

• Test the 800 numbers and post them in (18:19)

Outline Chapter 1: Testing and Form Completion (00:16 - 02:20)

• 00:16: Discussion on completing delivery methods and testing forms within WordPress.

• 00:35: Focus on testing tier one phone numbers on each form.

• 01:08: Emphasis on testing specific numbers and leads in the form testing process.

Chapter 2: Communication with Call Center (04:25 - 06:21)

• 04:25: Clarification on handling live calls and new leads in progress.

• 05:46: Instructions to inform call center about the incoming calls.

• 06:05: Confirming communication plan for call center channel.

Chapter 3: Setup and Automation (12:19 - 14:03)

• 12:23: Planning for setting up web hooks to control call routing.

• 13:07: Discussion on building web hooks for call tracking.

• 14:01: Clarification on the delivery method sending data to law ruler.

Chapter 4: Dashboard Development (16:05 - 17:23)

• 16:08: Proposal to create a dashboard for monitoring lead status changes.

• 17:03: Details on the dashboard structure and functionality.

• 17:30: Importance of having a detailed lead journey view for monitoring.

Chapter 5: Final Instructions and Testing (17:44 - 18:56)

• 17:44: Confirmation on the progress made and upcoming tasks.

• 18:06: Discussion on creating a new vertical and related processes.

• 18:19: Instructions to test specific phone numbers and inform stakeholders.

• These chapters summarize the key points and decisions made during the conversation, focusing on essential information for further actions and planning.

Shorthand Bullet • 🔧 *Web Hooks Functionality*

• - *Web hooks work for completing delivery methods in WordPress panel*

• - *Cameron provides specific notifications*

• - *Testing forms and calls for tier one phone numbers*

• 📊 *Testing and Setup*

• - *Testing all web hooks successfully*

• - *Discussion on testing methods for numbers*

• - *Creating standard method for setting up web hooks*

• 📞 *Call Progress and Communication*

• - *Clarifying status of live calls and handling call in progress*

• - *Noting the importance of specific information for call center*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-03-27 17:23:21

• 📋 *Data Transfer Details*

• - *Sharing campaign details to include call receipt information*

• - *Data transferred includes first name, last name, and cell phone*

• - *Discussion on data importance and transfer methods*

• 📉 *Dashboard Development*

• - *Planning to build a dashboard for tracking lead statuses*

• - *Dashboard to show status changes and progress*

• - *Emphasis on data visualization and reporting for monitoring*

Ryan (ryan@themedialab.agency)
2024-03-28 16:57:45

For saving JIC:

SELECT             c.ldp_contract_name AS "Name",
                    c.order_info AS "Details",
                    c.ldp_advertiser AS "Company",
                    'Won' AS "Status",
                    c.account_executive AS "Owner",
                    c.order_start_date AS "Close Date",
                    c.order_amount AS "Value",
                    'USD' AS "Currency",
                    '1' AS "Win Probability",
                    'Order Pipeline' AS "Pipeline",
                    'Funded Live' AS "Stage",
                    'Existing Relationship' AS "Source",
                    'AWS Import' AS "Tag",
                    c.ldp_vertical_name || ' - ' || v.vertical_id AS "Case Type / Campaign",
                    c.call_center AS "Call Center (Contract sales only)",
                    c.sale_type AS "Sale Type",
                    'Yes' AS "Integration Required",
                    c.order_start_date AS "Campaign Start Date",
                    c.order_end_date AS "Campaign End Date",
                    --Needs "- Sale Type redacated before upload"
                    SUBSTRING(c.ldp_contract_name, POSITION(' - ' IN ldp_contract_name) + 2) AS "Partner Firm",
                    ldp_contract_id AS "Leadspedia Contract IDs (e.g. 1201,1203,1203)",
                    units_sold AS "Approx. Contracts / Leads",
                    unit_price AS "Low Approx. Price Per Contract / Lead",
                    order_amt_paid AS "Amount Paid To Date",
                    id AS "AWS Order ID"
FROM ldp_contracts c
FULL JOIN ldp_verticals v ON c.ldp_vertical_name = v.vertical_name
WHERE c.status = 'Active'
AND order_info NOT LIKE '%Split%'
ORDER BY c.id ASC
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-01 12:35:32

Title: Copper Preview Date: Mon Apr 01 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, altonese@accountingdept.net, markmaniora@shield-legal.com, brian@accountingdept.net, luke@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting, led by *Ryan Vaspra, focused on implementing a new process using Copper CRM. Ryan Vaspra* discussed streamlining order management and reducing reliance on outdated methods. Key points included irregular order reception from Cameron, assigning updating responsibilities, emphasizing accurate data entry, and preparing for the transition to Copper.

• Specific tasks were outlined, including managing payments, creating shell verticals, and coordinating with Greg Owen for data input. Implementation would start after confirming all PBS entries were up-to-date before fully migrating to Copper. The discussion emphasized entering payment activities accurately and maintaining clean data records in line with leads generated in Leadspedia to improve efficiency.

• Participants agreed on timelines for gradual migration to Copper while addressing potential challenges by close collaboration. Future steps involve ongoing monitoring of data accuracy within CRM systems and continuous improvement efforts towards smarter automation practices aligned with business needs. The aim is to facilitate smoother communication among team members and automate processes previously done manually.

• The overall objective was to improve efficiency by automating processes through Copper CRM. Participants aimed to improve accuracy through clean data records and streamline communication by using updated CRM tools. Collaborating closely, they agreed on timelines for migration and planned to monitor data accuracy continuously, aligning automation practices with business needs.

Action Items • *Ryan Vaspra*

• Ensure all orders are updated in the Shield Legal Orders dashboard table by Friday (27:24)

• Start using copper from Monday onwards (27:48)

• Begin adding Cameron's deals into copper as they go out to avoid backlog next week (30:33)

• Aim for Friday implementation and full transition to copper on Monday (31:00)

Outline Chapter 1: Introduction and Process Overview (01:52 - 05:58)

• 01:52: Meeting introduction by Ryan to discuss the new process.

• 02:35: Mark explains receiving orders through PBS chat.

• 03:47: Ryan outlines the two key tasks needed from Mark for the new process.

Chapter 2: Dashboard and Data Management (05:58 - 13:11)

• 05:58: Ryan explains the process of transferring legal orders to a new table.

• 07:32: Introduction to analytics and domain setup.

• 12:07: Instructions on updating invoices and sales pipeline tasks.

Chapter 3: Sales Pipeline and Order Information (13:11 - 19:26)

• 13:11: Details on moving orders through the sales pipeline.

• 16:05: Automation of processes in the dashboard.

• 17:15: Discussion on creating leads PDF and contract names.

Chapter 4: Implementation and Task Assignment (19:26 - 24:54)

• 19:26: Instructions on updating orders and completing tasks.

• 22:44: Mark's role in the process implementation.

• 24:09: Uploading contract IDs and form submissions.

Chapter 5: Execution and Monitoring (25:00 - 31:28)

• 25:00: Instructions for contract naming and data matching.

• 26:41: Confirmation of the new process implementation.

• 28:11: Uploading files and ensuring data accuracy.

• 31:16: Planning for future steps and addressing questions.

Shorthand Bullet

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-01 12:35:32

• 📊 *New Process Introduction*

• - *Ryan Vaspra* invited only individuals involved in a new process.

• - Discussions focused on the process and steps involved in working with *Cameron*.

• ⚙️ *Task Assignments*

• - *Mark Maniora* was assigned specific tasks related to the new process, including handling orders and activities within the system.

• - The new process required input from *Mark* in terms of required fields and activities.

• 📝 *CRM System Overview*

• - *Ryan Vaspra* provided insights into using the CRM system, emphasizing the simplicity and custom fields available.

• - Details were discussed regarding campaigns, leads, contracts, and sales pipeline management.

• 📅 *Campaign Management*

• - *Brian Thiessen* inquired about campaign start and end dates within the CRM system.

• - Explanations were given on where to locate and input campaign-related information.

• 📄 *Contract Handling*

• - Instructions were given to *Mark* on creating shell contracts and verticals as needed for new orders.

• - Emphasis was placed on descriptive and clear contract names for tracking purposes.

• 🔄 *Routine Tasks*

• - *Ryan Vaspra* outlined routine tasks related to sales pipeline management, including updating statuses and ensuring completeness.

• - The importance of accurate data input for seamless integration was highlighted.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-01 14:20:03

Title: Tech Project Status Weekly Date: Mon Apr 01 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • *Ryan Vaspra* discussed consolidating weekly meetings and scheduling more work sessions with *James Scott. They emphasized streamlining data management tasks between systems like Vici and Conex one. Concurrently, James Scott* updated on an AI application engineer hire project involving analyzing demographic data related to drug cases using AI techniques.

• Going forward, the team aims to finalize the application engineer recruitment, complete data extraction from Unicort, optimize visual representations using BI dashboards and machine learning models. *James* focuses on predicting future drugs based on data analysis and integrating Unicor.com technology for court case information. Additionally, the process of data extraction from court documentation through API calls and PDF extraction tools is outlined.

• The team discussed plans for building BI dashboards after data extraction to visualize insights on adverse events by region for specific drugs over time using predictive AI models. They aim to leverage technology effectively within the team's projects and improve efficiency in data handling processes. In summary, they intend to target adverse events accurately using AI and machine learning while incorporating Unicor.com technology and advancing data extraction and dashboard development processes.

Action Items • *Ryan Vaspra*

• Follow up with Mike and Dwight on the status of BCl MVA with Torticity integration (48:13)

• Set up a meeting for Conex one expense report discussion on Thursday at 3:00 PM (45:39)

• Check on commitment with Unicorn sooner than later (1:01:31)

• Prepare model files for Looker training tomorrow (1:03:24)

• *James Scott*

• Provide updates on extracting case documents from Unicourt API, working on creating data tables for cases and people profiles, integrating adverse events data (53:01)

• Follow up with Unicor for guidance (1:14:28)

• Create bi dashboards after two weeks of free trial (1:14:37)

Outline Chapter 1: Project Overview and Scheduling (02:31 - 06:20)

• 02:31: Ryan discusses the need for more work sessions with James.

• 04:03: Introduction of a new project overview board for top-level projects or tasks.

• 05:24: Discussion on integrating case data for AI predictions.

Chapter 2: Task Management and CRM Development (06:38 - 15:59)

• 06:38: Overview of TikTok CRM funnel events and app development tasks.

• 09:12: Instructions on configuring CRM events and qualification processes.

• 14:24: Importance of lead generation and qualifying leads before call center interaction.

Chapter 3: Dashboard Updates and Data Transformation (19:22 - 37:49)

• 19:22: Adding Ks dashboard update and planning TV campaign details.

• 21:27: Plans for updating data studio dashboard and SQL work.

• 35:27: Discussion on major expense categories and financial data transformation.

Chapter 4: Legal Document Analysis and AI Integration (54:32 - 1:07:56)

• 54:32: James explains data sets creation for legal document analysis.

• 1:00:26: Plans for PF fact sheets and dashboard development.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-01 14:20:03

• 1:07:56: Discussion on extracting information from court documents for database creation.

Shorthand Bullet • 📊 *Weekly Meeting Structure*

• - *Ryan Vaspra* suggests transitioning to a single weekly meeting for efficiency.

• - Plans to have more work sessions with *James* and other team members.

• - Will adjust schedules for optimal meeting times.

• 📈 *Project Management*

• - Introduction of a new overview board for top-level projects or tasks.

• - Different boards for major projects like business intelligence, data warehousing, or AI products.

• - Emphasis on task management and status updates for each team member.

• 📋 *CRM and Task Management*

• - Detailed discussion on setting up the TikTok CRM funnel events.

• - Process involves building an app, configuring CRM events, and managing various stages of qualification and conversion.

• 🔍 *Lead Generation and Tracking*

• - Focus on qualifying leads before forwarding to call center.

• - Plans to create new dashboards for tracking leads and eSigns.

• - Updates to existing pages for improved visual consistency.

• 🚀 *Upcoming Goals and Tasks*

• - Prioritization of tasks like profile and budget management.

• - Discussion on case types, intakes, user statuses, and call metrics.

• - Planned meetings for project updates and progress tracking.

• 💡 *AI Application Development*

• - Discussion on AI application engineer hire and collaboration with *James*.

• - Consideration of AI machine learning for data extraction and visualization.

• 📧 *Email Integration*

• - Mention of using email integration for improved communication.

• - Potential meetings scheduled for further discussions on expenses and project reports.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-02 12:28:05

Title: Media Buyer performance Date: Tue Apr 02 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* was focused during the meeting, validating information on TikTok and discussing work matters with *Lee* Zafra* such as project updates, budgeting, and campaign strategies. He emphasized optimizing *Google Ads for better visibility and competitiveness in markets like Texas through strategic bidding. *Ryan* discussed lead generation accounts and highlighted the importance of prioritizing paid projects over unpaid ones to maintain profitability.

• He expressed concerns about unpaid clients affecting business relationships and underscored the need to direct resources towards profitable ventures. *Ryan* stressed the importance of maximizing budget allocation and standing out among competitors effectively. He mentioned preparing for upcoming training sessions and activities, planning to handle dashboards and tasks from Cameron upon his return from Vegas.

• The discussions during the meeting centered around operational aspects of projects, client engagements, marketing strategies, and balancing profitability with resource utilization. *Ryan Vaspra* aimed to ensure that efforts were focused on projects contributing financially. Overall, the emphasis was on strategic bidding, lead generation optimization, and prioritizing paid projects for profitability, reflecting a proactive and business-oriented approach to work tasks.

Action Items • *Ryan Vaspra*

• Implement the picture last night (05:40)

• Verify specific things (01:38)

• Lean in on a bunch of projects (06:04)

• Send a new invoice to Dishowitz for ten k for May and June 2024 (13:02)

Outline Chapter 1: Validation Process (00:03 - 05:07)

• 00:03: Ryan explains the ongoing validation process and requests a moment to complete it.

• 01:38: Ryan affirms completion of the validation process.

Chapter 2: Project Management and Workload (06:04 - 07:44)

• 06:04: Ryan mentions being involved in multiple projects and plans for development work.

• 07:44: Cameron assigns additional project responsibilities to Ryan.

Chapter 3: Campaign Optimization and Budgeting (10:05 - 13:02)

• 10:05: Ryan reviews completed tasks related to different campaigns.

• 13:02: Ryan discusses budget adjustments and invoicing for upcoming months.

Chapter 4: Lead Management and Tracking (17:10 - 18:22)

• 17:10: Ryan explains lead tracking methods in Leadspedia and related platforms.

• 18:22: Discussion on lead identification and management strategies.

Chapter 5: Marketing Campaign Strategies (21:10 - 23:57)

• 21:10: Ryan discusses Google My Business reviews and campaign planning.

• 23:57: Planning a Google Ads campaign to complement existing strategies.

Chapter 6: Meeting Preparations and Daily Agenda (24:51 - 25:09)

• 24:51: Ryan mentions upcoming meeting preparations and training sessions.

• 25:09: Ryan signs off to attend a meeting and training session.

Shorthand Bullet • 📊 *Project Management*

• - *Ryan Vaspra* handling multiple projects simultaneously

• - Discussing deadlines and project statuses with *Lee* Zafra**

• - Managing workload and balancing development tasks

• 📝 *Campaign Strategy*

• - Planning Google Ads campaign targeting auto accident keywords

• - Analyzing cost per click averages for different locations

• - Considering oversaturation in the market for strategic opportunities

• 📈 *Lead Generation*

• - Reviewing leads and budgets for different campaigns

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-02 12:28:05

• - Discussing lead quality and paid lead strategies

• 🚀 *Future Plans*

• - Setting up campaigns for *Lee* Zafra**'s next big project

• - Considering alternatives and backup plans for campaign success

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-02 14:18:12

Title: ByteCode Looker CodeDev session placeholder Date: Tue Apr 02 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, adam.kurstin@bytecode.io, nickmcfadden@shield-legal.com, luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting began with *Adam discussing embedding in Looker through API calls, emphasizing security concerns. Ryan* then highlighted building an analytics interface for specific use cases without direct embedding and proposed external portals for different client groups. They covered derived tables, SQL queries, and user attributes for managing access permissions efficiently in Looker.

• The conversation advanced to exploring drill-down functionality in Looker dashboards for deeper insights and the importance of proper drill fields placement. *Adam* underscored the significance of linking unique identifiers for detailed information visualization. They touched on maintaining data consistency through automatic table refreshing to ensure up-to-date information in Looker reports.

• The focus shifted to creating dashboards in Looker, emphasizing the distinction between drilling down and using links for object connections. *Ryan Vaspra* elaborated on drill-down benefits for detailed data exploration and the value of links in connecting objects for better insights. They discussed implementing cross-filtering features for universal data filtering across dashboards.

• Plans for future engagements with *Adam Kurstin* were outlined, suggesting a hands-on approach through code development review sessions for technical assistance during dashboard development. The collaborative strategy aimed to acquire essential data sets gradually before delving into complex analyses, ensuring smoother navigation through implementation challenges.

Action Items • *Ryan Vaspra*

• Follow up with Luke (01:20)

• Confirm ping to someone (02:05)

• Research on the possibility of embedding a single Looker instance via API calls (02:16)

• Discuss concerns about security issues related to using features like access filters and grants via API calls (04:51)

• *Adam Kurstin*

• Review derived tables quickly in the instance (10:26)

• Share example dashboard for drilling down functionality demonstration (53:07)

• Mention the change to refresh the browser (1:02:16)

• Review individual dashboards for filter placement (1:04:11)

Outline Chapter 1: Setting the Architectural Solutions (02:05 - 10:24)

• 02:05: Introduction to the anticipated agenda based on the previous meeting.

• 06:13: Discussion on creating workarounds for complex API calls for external clients.

• 08:31: Mention of Emily's involvement in the sales process.

• 09:32: Focus on architectural solutions for using Looker effectively.

Chapter 2: Data Modeling and Integration (13:18 - 26:10)

• 13:18: Mention of adding a date field and order start date in the system.

• 14:06: Discussion on positioning and architectural considerations.

• 19:02: Connecting to the old database and building the existing real dashboard.

• 22:30: Explanation on data merging and sophisticated find and replace features.

• 26:27: Planning for future data transformations and integration with DBT.

Chapter 3: Dashboard Development and Visualization (29:51 - 37:20)

• 29:51: Planning the addition of views to the Shield Legal project and model file.

• 31:22: Discussing dimension groups and explorations of financial data.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-02 14:18:12

• 33:09: Explanation on creating clean and efficient data references for dashboard building.

• 36:50: Conversion of data into measures for complex logic.

Chapter 4: Drill-Down Functionality and Data Exploration (55:22 - 01:03:52)

• 55:22: Introduction to adding drill fields to dimensions or measures for data exploration.

• 59:57: Explanation on drill-down functionality and linking objects for detailed data exploration.

• 1:00:57: Discussion on building dashboards for agent performance using drill-down capabilities.

• 1:01:47: Planning for the integration of drill-down and link features in dashboard design.

Chapter 5: Development Review and Future Engagement (1:09:07 - 1:14:14)

• 1:09:07: Recap of covered topics and readiness for development review.

• 1:10:51: Proposal for a code development review session and developer-level engagement.

• 1:12:30: Discussion on future collaboration and documentation delivery.

• 1:14:04: Confirmation of information transfer and preparedness for next steps.

Shorthand Bullet • 🔍 *Agenda Setting*

• - *Adam*: Proposed an agenda based on the previous meeting.

• - *Flexibility*: Open to discussing any topic.

• 📊 *External Application Use Cases*

• - *Ryan*: Discussed two use cases for external applications involving an application engineer and a data scientist named James.

• 🔧 *Architectural Solutions for Looker*

• - *Ryan*: Mentioned architectural solutions for using Looker without incurring costs to Google.

• - *Collaboration*: Discussed with Emily about internal and external use cases.

• 📑 *Data Modeling and Integration*

• - *Adam*: Shared insights on architectural modeling.

• - *Merge Query*: Explained the process of merging results from multiple connections.

• 💡 *Dashboard Development*

• - *Ryan*: Shared insights on creating dashboards efficiently.

• - *Data Grouping*: Discussed grouping data for visualization purposes.

• 📈 *Data Presentation Techniques*

• - *Adam*: Explained presenting information from multiple connections on a dashboard.

• - *Table Calculations*: Discussed methods for summing dimensions in different scenarios.

• 📚 *Knowledge Sharing*

• - *Ryan*: Shared examples and best practices with team members.

• - *Documentation*: Emphasized the importance of sharing and documenting processes.

• 📧 *Email Tracking*

• - *Adam*: Discussed tracking traffic sources via email.

• - *Highlighting*: Explained the use of highlighting features in the context of email tracking.

• 🛠️ *Development Review*

• - *Ryan*: Proposed a code development review session.

• - *Action Item*: Requested documentation and notes for review.

• 📋 *Content Management*

• - *Adam*: Confirmed copying all chat content for reference.

• - *Closure*: Agreed on next steps and concluded the meeting.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-03 12:23:48

Title: Ben Crump SEO Date: Wed Apr 03 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: korbin@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Korbin* informed *Ryan about the updated SEO BCl auto layer research Google Doc, specifically focusing on car accident pages for March and April. They discussed reviewing form leads and competitive SEO strategies with larger companies like Mash and Morgan. Despite smaller resources, their team was outperforming competitors spending significantly more on marketing. Korbin* emphasized understanding Google's search signals and media influence.

• *Korbin* mentioned the transition away from UA analytics following Google's decision to sunset it completely. Concerns about a possible hack into their Slack account were raised, leading to security measures. There were instructions to add Houston keywords related to car accidents alongside Dallas ones in the dashboard. *Korbin* clarified uploading data into sharpspring as manual lists for better handling, moving away from rules lists.

• The meeting centered on SEO performance updates, competitor analysis, platform transitions like UA analytics shift, security considerations regarding potential hacks, and efficient data management practices within sharpspring for enhanced workflow.

Action Items • *Korbin Mantel*

• Get Houston keywords added in here for me, okay? (19:23)

• Add Houston, all the car accidents, right? (19:33)

• Upload it. Do your naming convention and send us the URL and then check your inbox. (20:23)

Outline Chapter 1: SEO Data Analysis and Strategy (00:46 - 09:33)

• 00:46: Access to the SEO research Google Doc is discussed.

• 01:12: Updating the research document for March and April.

• 02:33: Reviewing form leads data for February.

• 09:05: Comparison with a larger SEO team's marketing budget.

• 09:23: Positive search visibility growth in the past week.

Chapter 2: Reporting and Analytics (10:29 - 16:23)

• 10:29: Discussion on reporting to the team using search console data.

• 15:15: Notification about Google discontinuing UA analytics.

• 16:19: Expressing gratitude for assistance.

Chapter 3: Security Concerns and Task Delegation (18:38 - 20:38)

• 18:38: Mention of a possible Slack hack and adding Houston keywords.

• 19:17: Concerns about a potential security breach.

• 19:50: Delegating tasks related to data uploading and formatting.

• 20:23: Clarification on uploading data to Sharpspring.

Chapter 4: Communication and Follow-Up (10:29 - 16:23)

• 10:29: Ensuring clear communication and understanding with the team.

• 16:23: Confirming completion of tasks and future actions.

Shorthand Bullet • 📊 *SEO Research Update*

• - *Korbin Mantel* provided an update on the SEO BCl auto layer research Google Doc.

• - Added fields for March and April for car accident pages.

• - Mentioned the need to fill in April data.

• - Noted issues with functionality.

• - Referenced March numbers being mid-month data.

• - Mentioned competitor Mash and Morgan's larger SEO team and marketing budget.

• - Highlighted positive search visibility growth.

• 🔒 *Security Concern: Slack Hacking*

• - Mentioned a potential hack into the Slack account.

• - Requested to add Houston keywords to the dashboard.

• - Addressed the need for security measures.

• 📈 *Analytics Transition*

• - Discussed Google's plan to stop UA analytics.

• - Noted the need to migrate from UA analytics.

• - Emphasized the importance of transitioning to new analytics tools.

• 📋 *Data Management* Guidelines**

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-03 12:23:48

• - Clarified the process for uploading data to Sharpspring.

• - Emphasized the difference between manual and rules lists.

• - Highlighted the importance of maintaining data integrity during uploads.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-03 14:16:22

Title: Data Development Date: Wed Apr 03 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, nickmcfadden@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting started with Ryan Vaspra, Luke Fontaine, and Brian Hirst discussing technical aspects of building connectors in Five Tran. Ryan showcased his success in building AWS and Postgres connectors and guided Luke in setting up a browser view, emphasizing data sources and destinations. They also addressed troubleshooting issues with screen sharing and permissions on account roles.

• The technical discussion then shifted to creating a monthly expense table using API keys in Copper integration, based on Ryan's guidance. They delved into DBT training steps by Don Byrd, talked about improving swing techniques during golf practice, and shared insights into courses like Torrey Pines and new par three courses such as the Battlefield at Shangri La.

• As the meeting progressed, they touched on company dynamics and personnel changes, mentioning individuals like *Nick and Cameron*. Insights were shared on past business models related to lead generation companies and challenges faced by certain ventures within the group. The participants reflected on historical events influencing team structures and operational transitions post-Christmas party terminations.

• Towards the end, they discussed *golf* in Southern California, including courses like Torrey Pines and benefits of walking a course for improved performance. The group highlighted plans for future work tasks related to dashboard improvements before wrapping up the meeting. Throughout the discussions, personal anecdotes, and interactions with colleagues like *Ben Brown* were shared to provide context on individual behaviors affecting professional relationships within the organization.

Action Items • *Ryan Vaspra*

• Implement copper in the database (35:33)

• Run SQL on the table before stopping its use (35:40)

• Create a new shield legal dashboard using BigQuery in Data Studio (36:13)

• Look up this new par three (48:42)

• Work on pages 25, 26 and add (55:03)

• *Luke Fontaine*

• Work on expense side transformation tables in DBT and daily expenses calculations (27:10)

• Take up specific task assigned by Ryan for project board completion within a week, focusing on DBT training and SQL writing practice (30:09)

• *Brian Hirst*

• Attend golf course to play golf ($600-$800) with colleagues at Wynn Golf Course, Las Vegas. Note that courses are less crowded during weekdays like Wednesday at noon. Enjoying this experience can lead to building relationships with affluent individuals who share an interest in golf.

• Look up the new par three (49:07)

Outline Chapter 1: Data Integration and Analysis (03:59 - 14:52)

• 03:59: Discussion on being responsive and the role of an account analyst.

• 08:38: Instructions on grouping data and understanding project structure.

• 13:33: Setting up API keys and integrations for data processing.

• 14:52: Saving and testing data integration.

Chapter 2: Database Management and Transformation (20:06 - 29:47)

• 20:06: Planning to create a monthly expense table and set up a data set in BigQuery.

• 25:05: Explaining the process of transforming tables and using DBT for data analysis.

• 29:47: Assigning tasks and outlining the steps to work with reference data in DBT.

Chapter 3: Project Coordination and Task Delegation (30:40 - 36:24)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-03 14:16:22

• 30:40: Assigning specific tasks related to selecting raw statements and SQL writing.

• 33:32: Planning for advanced SQL practice and data transformation tasks.

• 36:24: Finalizing task assignments and addressing any questions.

Chapter 4: Strategic Data Analysis and Business Insights (35:24 - 48:57)

• 35:24: Aligning expense and revenue data for analysis and transformation.

• 42:50: Discussing the importance of sequencing and data analysis methods.

• 48:57: Proposal for a new executive course and decision-making process.

Chapter 5: Communication and Team Collaboration (53:06 - 1:14:19)

• 53:06: Importance of informal discussions and team bonding for effective collaboration.

• 1:00:40: Proposal to start a call center and seeking opinions on the idea.

• 1:09:12: Initiating short topics for discussion and sharing project experiences.

Chapter 6: Conclusion and Next Steps (1:14:19)

• 1:14:19: Wrapping up the discussion and planning for future engagements.

Shorthand Bullet • 📊 *Monthly Expense Table Creation*

• - *Ryan Vaspra*: Set up the API keys under settings, integrations, API keys.

• - *Ryan Vaspra*: Create a monthly expense table for financials with Luke working on expenses and Nick on revenue.

• - *Ryan Vaspra*: Aim to have billable leads transform table by cross-referencing data sets.

• 💼 *Task Delegation and Deadline*

• - *Ryan Vaspra*: Assign Luke a task to write select raw statements for referencing data in DBT by Friday.

• - *Ryan Vaspra*: Ensure all payments and order submissions are in by Thursday end for project completion.

• 🔑 *Data Transformation and Integration*

• - *Ryan Vaspra*: Transform tables in DBT to show expenses in subordinate tables, linking daily expenses to leads.

• - *Nick McFadden*: Caution about different date formats in data transformation.

• 📈 *Meeting Structure and Collaboration*

• - *Ryan Vaspra*: Encourage idle chit-chat at the start of meetings to foster better working relationships and productivity.

• - *Ryan Vaspra*: Discuss starting a call center, seeking opinions for decision-making.

• 🔧 *Operational Workflow*

• - *Ryan Vaspra*: Establish a plan of attack for project tasks, focusing on financials and expenses.

• - *Ryan Vaspra*: Mention adding new pages for conversion rates in enterprise daily summary.

• 📞 *Meeting Conclusion*

• - *Ryan Vaspra*: End the meeting on a positive note, indicating further discussions and communication.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-04 13:12:12

Title: Data Development Date: Thu Apr 04 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, nickmcfadden@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • *Brian Hirst* and *Nick McFadden* are unsure if an upcoming meeting will happen. Nick informs Brian about a colleague's location. They discuss a high number of case types in the system. Challenges they face include naming conventions, creating new campaigns, and managing custom fields shared among projects. Nick mentions a tense encounter with Jordan from Law Ruler due to unprofessional conduct and communication breakdowns regarding API calls. They express frustration with uncooperative attitudes hindering system improvements. As plans for the meeting become uncertain, Brian considers canceling due to workload pressures and decides to forego the meeting. They both reflect on workload pressures before ending the conversation.

Action Items • *Brian Hirst*

• Confirm if the meeting is still happening today (06:52)

• Consider canceling the meeting if needed (06:55)

• *Nick McFadden*

• Verify with others about dropping from the call (07:28)

Outline Chapter 1: Preparing for the Meeting (00:00 - 02:10)

• 00:00: Discussion about uncertainty regarding the meeting.

• 00:21: Confirmation that the meeting will proceed shortly.

Chapter 2: Data Analysis and Insights (02:11 - 05:49)

• 02:21: Conversation about the number of case types in the system.

• 04:00: Challenges faced during mapping and managing custom fields.

Chapter 3: Vendor Relations and Challenges (05:54 - 07:09)

• 05:54: Frustrations expressed regarding interactions with a vendor.

• 06:46: An account manager's response causing dissatisfaction.

Chapter 4: Meeting Cancellation and Workload (07:52 - 07:43)

• 06:52: Uncertainty about the meeting's status.

• 07:32: Decision to skip the meeting due to workload demands.

Shorthand Bullet • 📊 *Case Types*

• - Over 570 case types in the system.

• - Includes various iterations and templates.

• ⚙️ *Custom Fields*

• - Nearly 20,000 individual custom fields, with around 70,000 in total when shared.

• 📞 *Interactions with Law Ruler*

• - Lengthy meeting with Law Ruler, addressing issues with API calls and performance concerns.

• 🔒 *Meeting Schedule*

• - Uncertainty regarding the meeting schedule, with conflicting information on whether it will proceed.

• 🚫 *Canceled Meeting*

• - Initial indication that a meeting may be canceled by Brian, but later updates suggest it might proceed.

• 📝 *Agenda Creation*

• - Mention of a new practice of creating agendas for data development calls, providing structure and clarity.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-04 15:06:22

Title: BCL Next Steps Date: Thu Apr 04 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: jon@bencrump.com, uzoma@bencrump.com, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@shield-legal.com, andy@brandlytics.io, adrienne@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting between *Desiree* A*, *Ryan Vaspra,* and Uzoma Obasi* primarily focused on work-related topics. Ryan expressed concerns about tasks involving Uzi, such as the delivery of insulin and PFAS materials. Desiree highlighted that these tasks were outside her scope and emphasized the need for further communication with Uzi. They discussed marketing strategies, focusing on Google Local Service Ads, SEO optimization for legal services, long-tail keywords, search engine rankings, and social signals concerning SEO performance. The conversation delved into technology aspects, from link building practices to current SEO methodologies, and the utilization of Google products to enhance search engine rankings based on user engagement patterns across platforms.

• They explored optimizing online presence through strategic initiatives aligned with contemporary search engine algorithms and user behavior patterns within the legal services domain. Ryan underscored the importance of debunking outdated SEO practices while implementing effective digital marketing approaches for enhancing online visibility. The participants engaged in detailed discussions on marketing strategies, particularly the importance of long-tail keywords, improving search engine rankings, and attracting quality leads. Technology aspects, such as link building practices and current SEO methodologies, were a key focus, emphasizing the use of various Google products to potentially enhance search engine rankings and improve user engagement patterns across platforms. Collaborations with universities to enhance backlinking strategies were also considered.

Action Items • *Desiree A*

• Test the round robin setup and see how it works out (17:14)

• Check if social traffic can be increased for better SEO results, especially on platforms like Twitter (25:38)

• *Uzoma Obasi*

• Discuss creating instructions for university bio links to improve backlinks strategy (28:48)

• Review the ranking domains of Morgan and Morgan versus Ben Crump for insights into backlink strategies (32:12)

Outline Chapter 1: Marketing Campaign Progress and Review Strategy (02:57 - 11:19)

• - Progress update on the torticity campaign and review strategy implementation.

• - Instructions given to agents regarding reviews and leveraging personal connections for reviews.

• - Discussion on aligning address and business names across platforms for consistency.

Chapter 2: Call Management Optimization and Round Robin Strategy (15:17 - 16:39)

• - Implementation of round robin system for call management and agent assignment.

• - Clarification on the round robin process and its application within the team.

Chapter 3: SEO Strategy and Content Creation (23:23 - 25:54)

• - Explanation of SEO improvements and long-tail keyword optimization.

• - Discussion on backlink domains and anchor text strategy for improving ranking.

Chapter 4: University Engagements and Content Creation (26:42 - 28:01)

• - Strategy for including links in bios for university engagements.

• - Proposal to create instructions for university interactions to ensure clarity.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-04 15:06:23

Chapter 5: Competitive Analysis and SEO Tracking (29:45 - 32:23)

• - Proposal to produce PDFs comparing backlink domains of different firms.

• - Discussion on using SEMrush for tracking SEO performance and monitoring competitors.

Shorthand Bullet • 📊 *Marketing Strategy*

• - *Ryan Vaspra's marketing team to deliver for *Desiree A's marketing team.

• - Utilizing personal Gmail accounts for reviews to improve Google rankings.

• - Encouraging staff, friends, and family to provide reviews for Dallas and Houston listings.

• 💬 *Content Strategy*

• - **Developing original content consistently for better engagement.

• - Including links when sending bios for speaking engagements to boost online presence.

• 🔍 *SEO Optimization*

• - Focusing on long-tail keywords for better search results.

• - Leveraging social traffic and engagement on platforms like Twitter and Google feeds.

• 📈 *Website Optimization*

• - Reviewing top-level URLs and keywords for practice areas on the website to enhance visibility.

• - Understanding the importance of anchor text in content for SEO benefits.

• 🔄 *Action Items*

• - *Follow up on ranking domains of *Morgan and Morgan versus Ben Crump.

• - Testing round-robin approach and reporting back on results.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-09 14:02:40

Title: TIP Invoices - Vici + Connex One manual DB update Date: Tue Apr 09 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • *Ryan Vaspra* encountered connection issues at the start of the meeting before delving into technical discussions around device priority settings and Wi-Fi app problems. *James Scott was linked to an API contract invoice of $27,000 and overage charges for API calls. Brianna Miller* later joined to streamline Connex reports by consolidating campaign data, focusing on optimizing reporting structures for improved efficiency and accuracy. They analyzed report columns for data significance to streamline the reporting processes.

• The participants navigated system configurations and tables, identifying discrepancies in outcomes like e-signatures and transfer statuses. Despite encountering confusion in their data exploration, they were committed to enhancing efficiency and accuracy in tracking billable activities. Plans were made to integrate Brianna's report into tip dashboards after addressing any inconsistencies or missing elements. A follow-up discussion was scheduled between *Ryan Vaspra* and Luke to refine data management strategies collaboratively based on the updated reports.

Action Items • *Ryan Vaspra*

• - Fix connection stability issue (00:02)

• - Make device the priority device (00:09)

• - Get 27K API contract invoice over and sign it for payment (01:59)

• - Update expense report with received data from Brianna (52:30)

Outline Chapter 1: Data Analysis Project Overview (00:28 - 04:38)

• 00:28: Ryan presents the project scope involving data analysis tasks.

• 03:18: Introduction of dashboards created by Luke and Brian for the AI project.

Chapter 2: Report Consolidation and Analysis (15:37 - 21:06)

• 15:47: Discussion with Brianna about consolidating Connex reports into a single sheet.

• 19:47: Plan to create a pivot table for data analysis purposes.

Chapter 3: Data Processing and Outcomes (31:33 - 38:30)

• 31:35: Processing department tasks related to inbound and outbound interactions.

• 37:48: Explanation of how campaign outcomes are derived from templates.

Chapter 4: Finalizing Data Manipulation (43:27 - 50:34)

• 43:32: Utilizing Connex outcomes for billable outcomes.

• 47:26: Confirmation of completion and emphasis on cross-referencing data.

Chapter 5: Request for Additional Information (54:08 - 56:57)

• 54:08: Request for a screenshot of a report and its title.

• 56:45: Confirmation of pending tasks and readiness for further instructions.

Shorthand Bullet • 📊 *Data Consolidation*

• - *Ryan Vaspra* and *Brianna Miller* discussed merging multiple reports into one spreadsheet.

• - The aim is to create a single report with all campaign names in one column for easy analysis.

• 🔄 *Pivot Table Creation*

• - The focus was on creating a pivot table for data analysis.

• - The pivot table will help in merging data with BT expenses efficiently.

• 📋 *Reporting Simplification*

• - Instead of separate reports, the plan is to have one comprehensive report.

• - This report will consolidate talk times and cases for easier analysis.

• 🤝 *Collaboration and Follow-up*

• - *Ryan Vaspra* and *Luke* will collaborate on data analysis post-receipt of the consolidated report.

• - Plans were made for further discussions and actions after the data consolidation process.

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-09 14:02:40

• Technical discussions, data optimization, and system configurations to enhance efficiency and accuracy in tracking activities.

Bullet Gist • ⚙️ Technical Discussions: Focused on device priority settings and Wi-Fi app problems.

• 💼 Data Optimization: Streamlined Connex reports for improved efficiency and accuracy.

• ⚖️ System Configurations: Identified discrepancies in e-signatures and transfer statuses.

• 📊 Integration Plans: Planned to integrate Brianna's report into tip dashboards.

• 🗓️ Follow-up Discussion: Scheduled between Ryan Vaspra and Luke for refining data strategies.

Short Summary • The meeting involved Ryan Vaspra facing connection issues initially, followed by technical discussions on device priority settings and Wi-Fi app problems. James Scott was linked to a $27,000 API contract invoice and overage charges for API calls. Brianna Miller joined to streamline Connex reports by consolidating campaign data for optimized reporting structures. Participants analyzed report columns for data significance and identified discrepancies in e-signatures and transfer statuses. Plans were made to integrate Brianna's report into tip dashboards after refining it for consistency. A follow-up discussion was scheduled between Ryan Vaspra and Luke to collaborate on data management strategies based on the updated reports.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-09 15:57:31

Title: BigQuery for TIP & SL Date: Tue Apr 09 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 90

Overview • The meeting between *Ryan Vaspra and Luke Fontaine* initially focused on health-related discussions, including well-being and the benefits of a specific supplement. They transitioned to work topics like building reports, data processing with SQL queries, and pivot tables for financial analysis in Google Sheets. Emphasizing structuring databases effectively, they discussed SQL joins to connect tables and the importance of accurate data representation through dashboards.

• Continuing their discussion on data analysis and system development, *Ryan* stressed the importance of learning SQL and DBT for future tasks related to revenue tracking. They planned to review case types tables, transform data, and create tables for monthly expenses to streamline processes. Ryan outlined plans for Luke's progression, encouraging him to dive into SQL work for accurate financial comparisons across databases.

• Touching on practical applications, they discussed creating sequel tables for financial metrics and accurate naming conventions for database components. Future activities included updating dashboards with revenue details from Conex one costs to understand business impact further under Cameron's direction. They aimed to validate revenue figures by understanding lead metrics thoroughly for detailed financial analysis.

• Towards the end, Ryan proposed a potential side project involving Google Cloud data warehouse projects managed by Luke, supported by Bytecode coding services. This venture aimed to offer ongoing support, potentially leading to additional revenue streams. The meeting highlighted collaborative efforts towards enhancing data management skills and exploring opportunities beyond current roles through strategic partnerships in various business intelligence projects.

Action Items • *Ryan Vaspra*

• Finish the sequel, get the dashboard updated, and send a post (59:49)

• Update dashboard with Connex one talk time revenue and talk time from Connex in the invoicing channel (58:06)

• Review tip LR case type pipe (1:13:35)

• Discuss app table transform DBT next steps for BH (1:13:35)

• Create table for monthly operating expenses and tip with two months' seed data with Luke Fontaine (1:13:35)

• *Luke Fontaine*

• Spend some time playing around with the new reporting system to get more familiar with it (45:32)

Outline Chapter 1: Data Analysis and Reporting (02:43 - 34:54)

• 02:43: Discovery of the horizontal outcome call time report for data analysis.

• 04:30: Transition of data to a Google sheet for further analysis.

• 15:17: Discussion on handling secondary interviews and case reviews data.

• 24:24: Converting time data to minutes for analysis.

• 32:24: Exploring formulas to convert time format to minutes.

Chapter 2: Revenue Maximization Strategies (36:03 - 48:40)

• 36:03: Focus on capturing revenue thoughtfully from different sources.

• 41:00: Detailed discussion on the importance of tracking talk time minutes for revenue.

• 48:40: Emphasis on tracking minutes for talk time and other metrics.

Chapter 3: Operational Efficiency and Task Management (54:55 - 1:07:18)

• 54:55: Implementation of office manual procedures for task management.

• 57:57: Planning to fill out past weeks' data and integrating new expenses.

• 1:07:18: Setting up a meeting to discuss app table transformation and next steps.

Chapter 4: Database Integration and Reporting Enhancements (1:09:52 - 1:15:40)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-09 15:57:31

• 1:09:52: Importance of understanding and utilizing Conex one data for reporting.

• 1:11:18: Scheduling a meeting to learn how to extract lead metrics from the database.

• 1:14:28: Future plans to connect call lead data for improved reporting efficiency.

Chapter 5: Skill Development and Collaboration (1:16:13 - 1:19:37)

• 1:16:13: Planning for meetings with SQL experts for skill development.

• 1:17:45: Reviewing SQL to enhance knowledge and collaboration.

• 1:19:37: Conclusion of a productive session focusing on learning and development.

Shorthand Bullet • 📊 *Horizontal Outcome Call Time Report*

• - *Ryan Vaspra* found and discussed the horizontal outcome call time report.

• - It is already pivoted into stat and outcomes columns by campaigns.

• - A query will be written later to manage this data.

• 🔍 *Summary Page Creation*

• - *Ryan Vaspra* created a summary page that will be converted into a Google sheet.

• - This sheet will include values related to secondary interviews and billable buckets.

• 📈 *Financial Metrics and Dashboard Development*

• - *Ryan Vaspra* emphasized the importance of populating fields with internal expense financial metrics.

• - They plan to create a unified raw dashboard for financial data visualization.

• 📅 *Meeting Schedule and Tasks*

• - A meeting with Conexone is scheduled for Thursday at 11:00 a.m. Eastern Time.

• - Future discussions will involve app table transformation and monthly operating expenses.

• 🔧 *Future Steps with Conexone*

• - *Ryan Vaspra* highlighted the need to learn how to extract lead metrics from Conexone data for future reporting.

• - They plan to request assistance from Conexone in understanding and implementing necessary SQL queries.

• 🚀 *Progress and Validation*

• - *Ryan Vaspra* mentioned validation of SQL queries with different experts and tech support, resulting in the creation of tables for billable leads data.

• 🙌 *Positive Conclusion*

• - The session was considered useful and productive by *Luke Fontaine and Ryan Vaspra*.

Gist • The meeting between Ryan Vaspra and Luke Fontaine covered health-related discussions, work topics like data processing and financial analysis, the importance of accurate data representation, SQL and DBT for revenue tracking, and potential side projects involving Google Cloud data warehouse projects.

Bullet Gist • 💼 Work Topics: Covered data processing, financial analysis, and database management.

• 🔍 Importance of Data Accuracy: Emphasized accurate data representation and SQL for revenue tracking.

• 📈 SQL and DBT: Discussed the importance of SQL and DBT for revenue tracking.

• 🌐 Google Cloud Projects: Explored potential side projects involving Google Cloud data warehouse projects.

Short Summary • The meeting between Ryan Vaspra and Luke Fontaine covered a wide range of topics from health discussions to work-related discussions on data processing, financial analysis, and database management. They emphasized the importance of accurate data representation, the use of SQL and DBT for revenue tracking, and discussed potential side projects involving Google Cloud data warehouse projects managed by Luke.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-10 14:39:35

Title: BigQuery for TIP & SL Date: Wed Apr 10 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting between *Ryan Vaspra and Brian Hirst* centered on optimizing data pipelines and application tables in a database system. They reviewed Internet speed, navigated Google Cloud BigQuery, and discussed SQL queries for selecting specific data. Reports on call time revenue calculations were examined, along with potential data issues in Conex one.

• Ryan emphasized understanding core lead tables for accurate reporting and planning future strategies. He stressed the need to explore BigQuery SQL queries for learning and developing a systematic approach to workflow. Staging tables were discussed using DBT for effective data processing tasks and creating structured databases for insightful reports aligned with business objectives. Collaboration for data accuracy and advanced analytics tools like Looker explorers was highlighted.

• Ryan guided Brian in inserting, updating, and manipulating data within tables for workflow efficiency. Real-time data updates' importance for accurate analytics was underscored, ensuring effective transformation of raw data into usable formats with precise naming conventions. Technical details on SQL queries, table creation, and schema design considerations were delved into deeply.

• Concerns about *Nick's* timely contributions to pipeline development tasks were raised, addressing accountability issues and project delays. Solutions were strategized on how to best handle these challenges while maintaining workflow productivity. Plans were made to refine existing pipelines, ensure comprehensive field inclusion, and discuss mastering complex software engineering concepts. Ryan acknowledged Brian's capacity limits but encouraged further learning efforts towards their roles' mastery.

Action Items • *Nick*

• Investigate why the data is not looking recent (49:03)

• Get information on the core lead tables and how to build a report from them (50:41, 51:08)

• *Luke*

• Fix any mistakes in updating counts and formulas in Google Sheets (35:27)

• Ensure data accuracy for the law ruler billable lead SQL table (42:38)

• *Ryan Vaspra*

• Figure out how to create application tables (1:34:18)

• Discuss the best way to add input, output fields in LR case types final data schema (1:29:24)

Outline Chapter 1: Data Analysis and Reporting Tools (10:39 - 15:51)

• 10:39: Discussion on the project and data analysis tools initiation.

• 12:34: Importance of CXM and contact data in the project.

• 15:51: Emphasizing the need to review lead activity logs.

Chapter 2: Report Generation and Data Formatting (19:01 - 25:27)

• 19:01: Instructing on the order by ID and created at columns for SQL queries.

• 24:25: Designing a report for financial updates and data accuracy.

Chapter 3: Data Transformation and SQL Queries (33:23 - 35:29)

• 33:23: Updating the financial log with talk time revenue calculations.

• 35:29: Highlighting revenue per e-sign and talk time analysis.

Chapter 4: Database Table Development and Management (42:11 - 47:10)

• 42:11: Discussion on creating a law ruler billable lead SQL table in DBT.

• 47:02: Planning for future database table enhancements and data accuracy checks.

Chapter 5: Dashboard Integration and SQL Reporting (49:24 - 51:39)

• 49:24: Importance of understanding data for effective reporting.

• 51:08: Describing the need for a detailed horizontal report in SQL.

Chapter 6: Application Table Creation and Business Facts (1:29:24 - 1:35:13)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-10 14:39:35

• 1:29:24: Exploring solutions for updating case types and billable rates.

• 1:34:04: Planning for application table creation and dashboard integration.

Shorthand Bullet • 📊 *Table Creation in Database*

• - *Create a table called contact data* in the project.

• - *Ensure SQL is commented and legible* for better understanding.

• - Use *'order by' in all caps* followed by the primary key for organization.

• - Discuss adding *specific columns for talk time and outcomes* for billable calls.

• 💼 *Financial Data Management*

• - *Develop a report for financial analysis* integrating talk time data accurately.

• - *Update financial logs with talk time minutes* for revenue calculations.

• - Ensure *correct counts for statuses* in the financial reports.

• 🔍 *Data Analysis and Reporting*

• - *Build a report with key columns* like campaign name, client name, and talk time by statuses.

• - Emphasize the need for *granular data for client, campaign, and leads* for detailed reporting.

• 📈 *Database Management* and Querying**

• - *Discuss database tables with multiple fields* for project management.

• - *Ensure data accuracy and completeness* for commissionable deals.

• 📆 *Meeting Management* and Action Items**

• - *Assign tasks for column additions* for data completeness.

• - *Schedule follow-up meetings* for detailed discussions on data management.

• 🔑 *Key Decision Making*

• - *Plan the data structure for better application tables* and business facts understanding.

• - *Prepare for future application needs* with raw data and business facts alignment.

Gist • Discussion on optimizing data pipelines and application tables, reviewing Internet speed, navigating BigQuery, and discussing SQL queries. Emphasis on accurate reporting, data processing efficiency, and collaboration for data accuracy and advanced analytics tools.

Bullet Gist • ⚙️ Data Optimization: Focus on optimizing data pipelines and application tables.

• 🔍 SQL and BigQuery: Reviewed Internet speed, navigated BigQuery, and discussed SQL queries.

• 📊 Accurate Reporting: Emphasized the need for accurate reporting and planning future strategies.

• ⚒️ Efficient Data Processing: Discussed using DBT for staging tables and creating structured databases.

• ⚠️ Accountability Concerns: Addressed concerns about Nick's contributions to pipeline development and proposed solutions.

Short Summary • The meeting focused on optimizing data pipelines and application tables in a database system, with Ryan Vaspra and Brian Hirst discussing Internet speed, BigQuery navigation, and SQL queries. They highlighted the importance of accurate reporting, efficient data processing, and collaboration for data accuracy. Ryan emphasized understanding core lead tables, exploring BigQuery SQL queries, and using DBT for staging tables to create structured databases aligned with business objectives. Concerns about Nick's contributions to pipeline development were addressed, with solutions proposed to handle accountability issues and project delays, refining existing pipelines, and encouraging further learning efforts towards mastering roles.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-11 13:39:52

Title: TIP BI Pipeline - LR Case Types for Billables solution Date: Thu Apr 11 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, nickmcfadden@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The discussion, led by *Ryan Vaspra, started with sequel execution in BigQuery. The team covered table creation, updates for communication, managing data freshness, and strategies for maintaining data integrity. They focused on building tables incrementally with updated information*. Options like temporary views were explored for merging data efficiently without duplication. Architectural decisions regarding merging case types and billable fields were made while ensuring historical tracking capability.

• *Nick McFadden* then raised points about *DBT transformation layers* for managing snapshots of changes over time. Suggestions included creating a view to combine current case type information with input data dynamically. The team planned future steps around DBT analytics folders to streamline dashboard creation based on combined datasets.

• The meeting, involving *Brian Hirst,* Luke Fontaine, Ryan Vaspra, and Nick McFadden,* delved into work-related matters. The team discussed various topics, including sequel execution in BigQuery* and *DBT transformation layers* for managing snapshots of changes over time. They concluded by planning future steps around *DBT analytics* folders to streamline dashboard creation based on combined datasets.

Action Items • *Ryan Vaspra*

• Update the sequel name to CNX horizontal campaign (02:51)

• Rename the sequel file to match the updated name (03:05)

• Update and widen the query as instructed (03:13)

• Delete the old connector that is not needed (03:51)

• Ensure proper incrementation with given query (04:01)

• *Nick McFadden*

• Confirm if start time matches 5 trans start time for data freshness interactions table (04:46)

• Check if CID values are identical across tables for validation during syncing process (07:43)

• Assist in resolving issues with running queries due to aggregate functions in where clauses, suggest alternative approaches like max date on timestamp SQL queries, and provide guidance on querying specific fields for better filtering results

Outline Chapter 1: Renaming the Campaign (00:19 - 05:56)

• 00:19: Discussion about renaming the CNX call time to CNX horizontal campaign.

• 02:51: Decision to update the name to CNX horizontal outcome call time.

Chapter 2: Data Validation and Start Time Analysis (06:33 - 10:29)

• 06:33: Analyzing date conversion and start time calculations.

• 10:29: Focus on validating data freshness and ensuring proper data cycling.

Chapter 3: Table Preview and Data Processing (10:55 - 14:01)

• 10:55: Request to preview the table values for further analysis.

• 13:20: Reviewing the process of merging and updating tables for data consistency.

Chapter 4: Building Customer Campaign Log Report (14:01 - 17:37)

• 14:01: Discussion on constructing a customer campaign call log report flat file.

• 17:37: Exploring the process of writing to a custom table for data recording.

Chapter 5: Architectural Setup and Data Transformation (19:19 - 24:37)

• 19:19: Planning the foundational architecture for data transformation.

• 24:37: Creating a view for extracting specific data fields efficiently.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-11 13:39:52

Chapter 6: Dashboard Development and Historical Tracking (26:25 - 31:33)

• 26:25: Implementation of code in DBT for dashboard development.

• 31:33: Incorporating historical tracking of billable values for analysis purposes.

Shorthand Bullet • 🔍 *Data Querying*

• - *Ryan Vaspra* shared a query to update and widen a table.

• - Discussion on validating data freshness and interactions in the database.

• - Clarification on the start time data in the interactions table.

• 🔄 *Data Integration*

• - Mention of connecting, appending new rows, and cycling data properly in the pipeline table.

• - Emphasized the importance of matching and grouping data for effective relationships.

• 🛠️ *Data Table Management*

• - Creation of a new table called 'tip prod application iolr case types revenue'.

• - Strategies for updating and merging tables effectively discussed by *Nick McFadden and Ryan Vaspra*.

• 📊 *Data Visualization*

• - Plans to utilize the final combined view table for creating a dashboard.

• - Mention of using the data for financial analysis and tracking changes in prices over time.

Gist • Discussion on sequel execution in BigQuery and DBT transformation layers for managing data snapshots and analytics folders.

Bullet Gist • ⚙️ Sequel Execution in BigQuery: Focused on incremental table updates and efficient data merging.

• 📊 DBT Transformation Layers: Managed snapshots of changes over time and combined datasets dynamically.

• 🗂️ Future Steps Planning: Discussed using DBT analytics folders to streamline dashboard creation.

Short Summary • The meeting, led by Ryan Vaspra, covered sequel execution in BigQuery, focusing on incremental table updates and efficient data merging. Nick McFadden highlighted DBT transformation layers for managing snapshots of changes over time, suggesting combining current case type information dynamically. The team planned future steps around DBT analytics folders to streamline dashboard creation based on combined datasets.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-15 11:44:15

Title: BLX Media Buying Date: Mon Apr 15 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, korbin@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting primarily focused on *Ryan Vaspra and Lee* Zafra* discussing work-related matters. *Ryan provided updates on civil rights reviews, case counts, employment discrimination, and legal issues in locations like Atlanta and camp Lejeune. They analyzed metrics to track performance effectively and emphasized the importance of detailed tracking for better decision-making on lead conversions and marketing strategies.

• Ryan emphasized improving communication efficiency and directed Lee to collaborate closely in generating reports accurately with specific filters. Consistent monitoring of SEO efforts related to auto accident rankings and birth injury keywords was stressed. The discussion also highlighted the need for further investigations into phone number matches between LSA calls and case reviews to assess conversion rates effectively.

• The meeting concluded with Ryan calling for teamwork in streamlining data analysis processes for improved insights in the future. They set clear directives for investigating phone number matches between LSA calls and case reviews to boost conversion rates efficiently. The focus was on enhancing communication efficiency within the team and emphasizing detailed tracking for better decision-making on marketing strategies and lead conversions.

Action Items • *Ryan Vaspra*

• Review the case reviews from April 8th to today (34:20)

• Work on Texas auto accident rankings and focus on birth injury soon (35:47)

• Provide insights about auto rankings and use tools to be more visible (36:41)

• Export Texas auto stuff and help with reporting efforts (37:28)

• Collaborate with Lee Zafra to match phone numbers for paid charged ads in law ruler (39:14)

• *Lee Zafra*

• Team up with Ryan Vaspra to match phone numbers for paid charged ads in law ruler (40:59)

Outline Chapter 1: Setting Objectives and Metrics (00:02 - 03:14)

• - Introduction to the day's tasks and discussions on maintaining accuracy in data.

• - Emphasis on focusing on specific details during data entry and tracking for metrics.

Chapter 2: Review of Case Reports and Analysis (13:37 - 26:47)

• - Importance of accurately documenting case reviews for further analysis.

• - Crafting a narrative for Cameron based on the gathered data and insights.

Chapter 3: Data Export and Analysis Procedures (28:14 - 38:56)

• - Instructions on exporting data for detailed analysis and matching phone numbers for review.

• - Explanation of the process to track and match phone numbers for lead analysis.

Chapter 4: Collaboration and Follow-Up Tasks (39:27 - 41:36)

• - Assigning tasks to ensure data accuracy and matching for lead generation analysis.

• - Closing remarks and encouragement for ongoing progress and productivity.

Shorthand Bullet • 📊 *Case Review Data*

• - *980 qualified case reviews with 985 total*

• - Discussing the accuracy and importance of case review data

• - Emphasized the need to keep accurate records

• 📞 *Phone Number Matching*

• - *Instructions on matching phone numbers*

• - Using filters to save time and ensure accuracy

• - Matching phone numbers from leads with those in law ruler for specific case reviews

• 📅 *Task Assignment*

• - Assigning tasks to Corbin for data organization and matching

• - Emphasized the importance of completing tasks accurately and efficiently

• 📉 *Weekly Insights and Rankings*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-15 11:44:15

• - Discussing tracking keywords, competitor analysis, and auto rankings

• - Encouraging continuous improvement and staying informed on industry trends

• 📝 *Communication and Reporting*

• - Emphasized the need for clear and timely communication

• - Delegating responsibilities for reporting and updates to team members

• 📅 *Meeting Preparation*

• - Setting expectations for tasks completion before meetings

• - Encouraging proactive updates and preparedness for discussions

• 📈 *Performance Metrics*

• - Setting performance goals, such as 40 calls per day

• - Analyzing data for insights and improvement opportunities

Gist • Focus on work-related matters, metrics analysis, communication efficiency, and teamwork for data analysis improvement. 📊🔍🤝

Bullet Gist • 📊 Metrics Analysis: Focused on tracking performance metrics for better decision-making.

• 🔍 Communication Efficiency: Emphasized improving communication and accurate report generation.

• 🤝 Teamwork Emphasis: Stressed the importance of teamwork for data analysis improvement.

Short Summary • The discussion centered around work-related issues with Ryan Vaspra and Lee Zafra providing updates on civil rights reviews, case counts, employment discrimination, and legal matters in various locations. They emphasized the importance of detailed tracking for effective decision-making on lead conversions and marketing strategies. Ryan highlighted the need for improved communication efficiency, directed collaboration for accurate report generation, and stressed consistent monitoring of SEO efforts. The meeting concluded with a call for teamwork to streamline data analysis processes and investigate phone number matches for enhanced conversion rates.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-15 14:11:57

Title: Tech Project Status Weekly Date: Mon Apr 15 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting began with *Ryan Vaspra discussing his plan to relocate to Tulsa, touching on the airport customs center and historical aspects of the city. He shared personal anecdotes related to aviation education and family connections. Ryan later talked about work-related tasks, focusing on data processing and financial details within the company. He discussed collaborating with Brian Hirst* following a staffing change affecting accounting processes.

• Subsequently, *James Scott* showcased updates in data processing methods using Google Cloud's Vertex AI Workbench and Python scripts for creating machine learning models. He highlighted integrating these models into database systems for enhanced analytics. Both team members exchanged insights on refining SQL queries and managing data frames effectively. They focused on overcoming technical challenges for predictive modeling and ranking algorithms in pharmaceutical data analysis.

• *James Scott* shifted the discussion to a project integrating unit, courts, and cases, emphasizing the efficiency of *Python* in simplifying architecture tasks. The team discussed architecting a business intelligence system for streamlined data ingestion. They planned to enhance matching mechanisms and data ranking based on severity, using *GitHub* to track progress. Discussions also involved aligning adverse event data with medical billing codes (*ICD ten*) and linking cases to build a real-time population affected by drugs, creating a comprehensive overview of drug effects on individuals.

• The meeting concluded with *James Scott* expressing gratitude for the team's efforts and excitement towards completing an ongoing AI project with potential revenue growth impact. Future plans included dashboard enhancements and follow-up meetings for pending tasks by absent team members. The team aimed for continuous collaboration and technical advancement within the project.

Action Items • *Ryan Vaspra*

• Set up a session for Dev Ide kickoff on Thursday (40:04)

• Review the SQL join statement for bigquery, focusing on custom field value joining with custom field definition option id (41:08)

• *James Scott*

• Figure out how to use a web link instead of CSV to create an adverse event database (46:43)

• Update the pipeline in Vertex AI workbench AI platform for seamless model deployment and data processing (48:27)

• Add in a large language model instead of fuzzy match (59:30)

• Add weight constraints to the drug algorithm based on severity (1:00:54)

• Make small changes to the code before finishing up the pipeline (1:01:10)

Outline Chapter 1: Project Initiation and Task Assignment (00:11 - 07:57)

• 00:11: *Ryan Vaspra* initiates the meeting to discuss the upcoming tasks and goals.

• 05:16: Emphasis on focused work sessions with minimal interruptions.

• 07:20: Task assignments and projects outlined for the team members.

Chapter 2: Database and Analytics Development (07:57 - 16:40)

• 07:57: Detailed goals for DBT raw and staging sequel creation discussed.

• 09:58: Task confirmation and emphasis on achievability.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-15 14:11:57

• 16:40: Instructions for the Dev tip Connex campaign project explained.

Chapter 3: Sales CRM and Financial Reporting (19:23 - 30:37)

• 19:23: Task assignment related to sales CRM project.

• 20:18: Copper data integration and financial details highlighted.

• 30:37: Overview of creating expense data dashboard from Copper orders.

Chapter 4: Production Code and Revenue Calculations (31:03 - 33:37)

• 31:03: Task assignment for creating DBT analytics production code.

• 32:13: Instructions for inputting revenue values in the production code.

• 33:37: Meeting planning to discuss progress and future steps.

Chapter 5: Data Transformation and SQL Development (34:19 - 39:55)

• 34:19: Discussion on revenue rates table development.

• 35:18: Explanation on building DBT transform Ellicott.

• 39:55: Importance of testing SQL queries and development considerations.

Chapter 6: Progress Review and Next Steps (43:28 - 58:06)

• 43:28: *James Scott* shares insights on data processing and model creation.

• 46:18: Steps towards creating a ranking model.

• 58:06: Future tasks include adding a language model and enhancing fuzzy matching.

Chapter 7: Team Development and Technical Growth (1:06:55 - 1:08:20)

• 1:06:55: Focus on technical growth and team development.

• 1:08:06: Plans for broadening interactions and collaboration within the team.

• 1:08:20: Concluding remarks and plans for future communication.

Shorthand Bullet • 📊 *Project Goals for Conex One Ads Tip Talk Time Report*

• - *Goal 1:* Build DBT raw and staging sequel for weekly call time report.

• - *Goal 2:* Join call time into Finlog table with new columns for CNX talk time revenue and minutes.

• - *Action:* Email Luke, Nick, and Brian regarding Conex One SQL for campaign and call stats.

• 🛠️ *Development Tasks*

• - *Task:* Dev tip Connex campaign horizontal outcome call time.

• - *Action:* Implement CNX onetipcCXM.campaignsname as campaign name.

• - *Reminder:* Learn DBT behaviors for successful project execution.

• 📈 *Sales CRM Copper Project*

• - *Task:* Join into financial details for the project.

• - *Action:* Continue conversation with Chat GPT for project development.

• 🔗 *Database Table Updates and Interface Planning*

• - *Plan:* Meet with Tony to update database tables and interface for data maintenance.

• - *Importance:* Financial log table critical for revenue control and validation with Tony.

• 📝 *Task Assignment*

• - *Assigned *Task: Brian** to create a sub-task for the project.

• - *Follow-Up:* Set up a Dev Ide kickoff session for project alignment.

• 📈 *Ranking Model Development*

• - *Step:* Create a ranking model for metrics table based on specified criteria.

• - *Improvement:* Consider using a large language model for enhanced accuracy.

• 🔍 *ICD Ten Code Chapters*

• - *Action:* Implement mathematical scale on ICD ten code chapters or topics for analysis.

• 📅 *Schedule*

• - *Plan:* Plan a Thursday session for project updates and Looker integration.

• - *Reminder:* Use Google Docs for Chat GPT prompts for better results.

Gist • Meeting covered relocation to Tulsa, data processing, machine learning updates, and business intelligence system planning. Team focused on technical challenges and future AI project goals.

Bullet Gist • ⚙️ Technical Discussions: Focused on data processing, machine learning updates, and overcoming technical challenges.

• 📊 Business Intelligence Planning: Discussed architecting a system for streamlined data ingestion and enhancing data ranking mechanisms.

• 🔍 Data Analysis: Aligned adverse event data with medical billing codes and built a real-time population affected by drugs.

• 🚀 Future Plans: Emphasized completion of ongoing AI project, dashboard enhancements, and continuous collaboration.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-15 14:11:57

Short Summary • The meeting encompassed discussions on various topics including Ryan Vaspra's relocation plans to Tulsa, data processing tasks, machine learning updates with Google Cloud's Vertex AI Workbench, and the planning of a business intelligence system. Team members shared insights on refining SQL queries, overcoming technical challenges in predictive modeling, and enhancing data ranking mechanisms. They also discussed aligning adverse event data with medical billing codes and creating a real-time population affected by drugs. The meeting concluded with James Scott expressing gratitude for the team's efforts and excitement towards completing an ongoing AI project with potential revenue growth impact, emphasizing continuous collaboration and technical advancement within the project.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 11:22:31

Title: JV - mid month commission review Date: Tue Apr 16 2024 12:15:00 GMT-0400 (Eastern Daylight Time) Participants: cameron@themedialab.agency, john@themedialab.agency, brian@accountingdept.net, ryan@shield-legal.com, ryan@themedialab.agency, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting focused on coordinating *financial transactions* and future meetings between *Brian Thiessen and Ryan Vaspra*. Brian stressed the accuracy of money transfer numbers, particularly referenced in an email from Cameron. They discussed schedules with Maximus attending at 9:30 and Caleb at 9:45. Ryan confirmed receiving a payment of $2,112.36, expressing readiness for upcoming commitments.

• Both participants addressed logistical matters efficiently without issues. They verified critical details like meeting times, participant attendance, financial figures, and communication details around transactions. The interaction showcased effective collaboration between Brian and Ryan, ensuring a seamless coordination of shared responsibilities linked to their commitments. Ryan acknowledged completing transactions smoothly, thanked Brian, and concluded the discussion positively.

Action Items • *Ryan Vaspra*

• Send out the commission payment (08:44)

• See you in the next meeting (08:47)

Outline Chapter 1: Confirmation of Payment Details (08:35 - 08:47)

• 08:35: Ryan confirms the commission amount as $2,112.36.

• 08:44: Ryan confirms sending the payment.

Chapter 2: Meeting Scheduling and Attendees (07:00 - 07:28)

• 07:00: Brian confirms details about the next two meetings.

• 07:15: Discussion on the attendees for the meetings at 9:30.

Chapter 3: Clarification on Meeting Participants (07:30 - 07:53)

• 07:30: Brian seeks clarification on the participants for the upcoming meetings.

• 07:41: Identification of Maximus and Caleb as participants at 9:30.

Chapter 4: Finalizing Meeting Logistics (07:53 - 08:50)

• 08:47: Ryan concludes the conversation and plans to meet for the next discussion.

• 08:50: Brian acknowledges and ends the conversation.

Shorthand Bullet • 📊 *Meeting Schedule*

• - *Maximus* scheduled for 9:30 AM

• - *Caleb* scheduled for 9:45 AM

• 💰 *Financial Transaction*

• - Commission of $2,112.36 processed by *Ryan Vaspra*

• - Money sent out promptly

• 📧 *Communication*

• - *Brian Thiessen* awaiting an email with necessary numbers for the transaction

• 📅 *Future Meetings*

• - Clarification needed on start times for upcoming meetings

• - Ensuring attendance and timing for *Maximus* and *Caleb*

Gist • Meeting focused on financial coordination between Brian and Ryan, ensuring accuracy of transactions. Participants discussed schedules and confirmed payments.

Bullet Gist • ⚙️ Financial Coordination: Focus on accuracy of money transfer numbers.

• 🗓️ Schedules Discussion: Maximus attended at 9:30 and Caleb at 9:45.

• 💸 Payment Confirmation: Ryan received $2,112.36, ready for upcoming commitments.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 11:22:31

• The meeting centered on coordinating financial transactions and future meetings between Brian Thiessen and Ryan Vaspra. Brian emphasized the importance of accurate money transfer numbers, specifically mentioned in an email from Cameron. They efficiently addressed logistical matters like schedules, participant attendance, financial figures, and communication details. Ryan confirmed receiving a payment of $2,112.36, expressing readiness for upcoming commitments. The interaction showcased effective collaboration, ensuring a seamless coordination of shared responsibilities. Ryan acknowledged completing transactions smoothly, thanked Brian, and concluded the discussion positively.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 11:46:11

Title: ML - mid month commission review Date: Tue Apr 16 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: maximus@themedialab.agency, cameron@themedialab.agency, brian@accountingdept.net, ryan@shield-legal.com, ryan@themedialab.agency, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting commenced with *Ryan mistakenly joining the wrong call but quickly rectifying the error. The discussion then transitioned to AI-generated voices and videos, highlighting concerns about their realism and implications for privacy and security. Maximus* later encountered trouble accessing CRM events on Tick Tock, leading to a troubleshooting session where *Ryan* recommended clearing cookies as a temporary solution. The technical issue was resolved by following specific steps provided during the call.

• Conversations revolved around sales funnel optimization, media buying strategies, and campaign performance metrics such as cost per contract, along with future campaign plans. Despite challenges around CRM access, collaborative efforts efficiently addressed and resolved the issues. Positive feedback was exchanged regarding progress in previous months' work, looking optimistically towards future achievements. The meeting concluded with thanks and confirmed arrangements for follow-up meetings to continue productive discussions.

Action Items • *Maximus Lynn*

• Clear the cookies to resolve access issue with CRM event area (07:33)

• Screen record the issues for TikTok team (08:39)

• Review sales funnels and ensure correct events are in place (13:53)

• *Ryan Vaspra*

• Report the access issue in the account with TikTok CRM to Jake Cameron or the team (08:08)

• Share a video update on MLS and review sales funnel setup (14:55)

Outline Chapter 1: Technical Issue with CRM Event (06:28 - 12:57)

• 06:28: Maximus reports an issue with the CRM event where it keeps redirecting to the same page.

• 08:28: Discussion on the ongoing glitch and the need to screen record the problem for the tech team.

• 12:00: The team troubleshoots the issue, and it seems to be resolved.

Chapter 2: Action Plan for Resolving Technical Glitches (12:10 - 16:59)

• 12:10: Maximus confirms the issue is resolved after troubleshooting steps.

• 13:02: Ryan discusses the ongoing development process and the steps to address similar issues.

• 16:59: Cameron praises the team's work in March and encourages them to continue making progress.

Chapter 3: Review and Future Planning (17:02 - 17:19)

• 17:02: Cameron acknowledges the team's achievements and schedules the next meeting.

• 17:14: Maximus and Ryan express gratitude and say goodbye as the meeting concludes.

Shorthand Bullet • 🔍 *Issue with CRM Event in Account*

• - *Maximus *Lynn reported an ongoing issue where the **CRM event area keeps disappearing.

• - *Ryan Vaspra* advised on potential troubleshooting steps and to contact the TikTok team for resolution.

• - *Cameron Rentch* suggested screen recording the issue for better communication with the tech team.

• 🔄 *Refreshing and Fixing CRM Event Error*

• - *Ryan Vaspra* shared a trick to refresh the page to resolve the CRM event issue.

• - *Maximus *Lynn** successfully implemented the refresh method to fix the problem.

• 📹 *Video Update for MB Team*

• - *Ryan Vaspra* emphasized the importance of reviewing sales funnels and ensuring correct events are included.

• - The team was instructed to ensure bad events are unchecked and misspelled events are left out of the funnel.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 11:46:11

• - *Cameron Rentch* mentioned an update to MLS and the need for team collaboration on the video.

• 📈 *Performance Evaluation and Next Steps*

• - *Cameron Rentch* checked in on campaign progress and encouraged continued momentum.

• - *Maximus *Lynn** expressed satisfaction with progress and plans for future improvements.

• - *Cameron Rentch* rescheduled a follow-up meeting to discuss further actions.

Gist • Meeting covered AI concerns, CRM issues, and positive feedback. Discussions on sales optimization and future plans. Resolved technical problems with collaborative efforts.

Bullet Gist • ⚙️ Technical Issues Resolved: Maximus's CRM access problem fixed through collaborative troubleshooting.

• 💬 Discussion Topics: AI-generated content realism, privacy concerns, sales optimization, and future campaign plans.

• 👍 Positive Feedback: Mutual appreciation shared for past achievements and optimistic outlook on future work.

Short Summary • The meeting encompassed a range of topics starting with Ryan's initial call mix-up, leading to talks on AI-generated content's realism and privacy concerns. Maximus faced CRM access troubles on Tick Tock, resolved with Ryan's cookie-clearing suggestion. Conversations delved into sales funnel optimization, media buying strategies, and performance metrics like cost per contract. Despite CRM challenges, teamwork efficiently tackled issues, sparking positive feedback on past progress and future prospects. The session ended with gratitude and plans for follow-up meetings to sustain productive discussions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 11:57:02

Title: CP mid monthly commission review Date: Tue Apr 16 2024 12:45:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@themedialab.agency, caleb@shield-legal.com, ryan@brandlytics.io, brian@accountingdept.net, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting involved *Cameron Rentch,* Caleb Peters*, and *Ryan Vaspra discussing work-related topics. **Cameron focused on pushing forward the Lejeune project for increased productivity, highlighting the importance of consistent effort to achieve targets. The team discussed strategies to improve conversion rates for upcoming projects, success in past campaigns, and challenges with specific targeted campaigns. Caleb expressed readiness to address challenges and received guidance from Cameron on optimizing campaign performance, including using TikTok for effective conversions. They also addressed technical issues like glitches in CRM events and data upload concerns that could impact campaign success.

• Plans were made to enhance existing campaigns like Firefoam at Lejeune and Roundup promotions by refining targeting strategies and fixing technical aspects for better results. Cameron emphasized continuous improvement in campaign performance and addressing issues within their control for successful outcomes. The team set follow-up actions, including a scheduled call at twelve and commitments from Caleb to boost efforts on TikTok marketing. The focus was on aligning strategies, promptly resolving technical issues, and maximizing campaign effectiveness through targeted approaches across different platforms.

Action Items • *Caleb Peters*

• Prepare more campaigns for TikTok (09:34)

• Get Afff campaign back up (07:20)

• *Cameron Rentch*

• Keep Caleb posted on Lejeune progress (04:28)

• Follow up on getting roundup moving by the end of the week (08:13)

Outline Chapter 1: Discussion on Campaign Performance and Strategies (04:10 - 09:35)

• 04:10: Cameron acknowledges good progress and focus on Lejeune campaign. Plans to increase output.

• 05:02: Planning to boost Paraquat campaign and aim for higher daily results on Lejeune.

• 09:30: Caleb confirms readiness to launch campaign on TikTok.

Chapter 2: CRM Event Management and Campaign Launch (06:08 - 09:15)

• 06:08: Review of CRM event issues with Maximus and Ryan.

• 06:16: Caleb faces occasional glitches in CRM event access but has a workaround.

• 07:02: Caleb has only launched one campaign on CRM event platform so far.

Chapter 3: Optimization and Expansion Plans (08:02 - 11:26)

• 08:02: Updates on setting up new rate for residential and commercial campaigns.

• 09:15: Discussion on leveraging TikTok success for new campaigns and CRM events.

• 11:02: Planning to incorporate lookalike audiences data for campaign improvements.

Shorthand Bullet • 📊 *Discussion on Marketing Strategies*

• - **Cameron Rentch suggests focusing on Lejeune to increase daily output to 100k.

• - Caleb Peters mentions difficulties in converting newer, more targeted campaigns.

• - Plans to launch campaigns using CRM event and TikTok platforms.

• 🔧 *Technical Issues and Solutions*

• - *Glitch in CRM event system discussed, with *Ryan providing a workaround solution.

• - Caleb confirms occasional issues with accessing CRM events but acknowledges improvements.

• - Cameron inquires about specific campaigns utilizing CRM events.

• 💼 *Operational Updates and Plans*

• - Cameron emphasizes the need to increase spend and ensure conversions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 11:57:02

• - Mention of pending CRM events setup and data upload for lookalike audiences.

• - Expectation that lookalike audiences data could significantly impact campaigns.

Gist • Team meeting focused on enhancing campaign performance through consistent effort and targeting strategies. Technical issues addressed for better results. TikTok marketing discussed for improved conversions.

Bullet Gist • ⚙️ Enhancing Campaign Performance: Focused on consistent effort and targeting strategies.

• 🔧 Technical Issues Addressed: Discussed CRM glitches and data upload concerns.

• 💡 Optimizing Campaigns: Guidance given on using TikTok for improved conversions.

• 🚀 Improving Conversion Rates: Strategies discussed for upcoming projects.

• 🎯 Refining Targeting Strategies: Plans made to enhance existing campaigns like Firefoam and Roundup promotions.

Short Summary • The team meeting involved Cameron Rentch, Caleb Peters, and Ryan Vaspra discussing strategies to enhance campaign performance. Cameron emphasized the importance of consistent effort in pushing forward projects like Lejeune for increased productivity. They discussed improving conversion rates and addressing challenges in targeted campaigns. Caleb received guidance on optimizing campaign performance, including the use of TikTok for conversions. Technical issues such as CRM glitches and data upload concerns were addressed to ensure campaign success. Plans were made to refine targeting strategies for existing campaigns like Firefoam and Roundup promotions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 13:22:41

Title: Financials catch up Date: Tue Apr 16 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: andy@shield-legal.com, ryan@brandlytics.io, brian@accountingdept.net Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting involved *Ryan Vaspra and Brian Thiessen* discussing outstanding invoices and payment follow-ups. They reviewed invoices together, focusing on sorting by client names and identifying overdue payments, particularly from companies like Focus Litigation Solutions. Ryan emphasized prompt payment collection and strategies for engaging with slow-paying clients. Insights were shared on managing digital services and financial transactions within the advertising realm, including norms in media buying budgets and interactions with Google for billing disputes.

• Ryan provided insights into relationships within companies, highlighting effective communication strategies for individuals like Elena and Steven Giacovino. He shared experiences dealing with challenging payers like Jeff Dubin to emphasize assertive yet tactful approaches. The discussion also touched upon hiring a strong bill collector to streamline future collections efficiently. Both participants acknowledged pending payment action steps and agreed on invoicing procedures tailored to specific clients' requirements for efficient debt recovery.

• Ryan's emphasis on timely payment collection and strategic engagement with slow-paying clients led to discussions on assertive yet tactful approaches for debt recovery and hiring a strong bill collector. Additionally, insights were shared on industry norms related to media buying budgets, pay-per-lead programs, and interactions with Google for billing disputes. The meeting concluded with acknowledgments from *Brian Thiessen* regarding next steps involving customized invoicing procedures and committed efforts towards efficient debt recovery processes. Both participants emphasized the importance of tailored strategies for specific clients and efficient collections moving forward.

Action Items • *Ryan Vaspra*

• Follow up and confirm payment with John (03:33)

• Loop in Altonise to provide a list of outstanding payments (04:07)

• Lean in on finance leadership, involve Andy if needed, contact Jack for payment collection for Brandlytics (05:25)

• Text Steve about getting paid for services rendered (08:49)

• *Brian Thiessen*

• Record payment for Ben Crump invoice in Harvest (10:40)

• Send emails out regarding outstanding payments (11:30)

Outline Chapter 1: Review of Outstanding Invoices (00:06 - 03:59)

• - Discussion on outstanding invoices and focus on receivables from January.

• - Plan to follow up on outstanding payments with specific contacts.

Chapter 2: Organizing Payment Collection (04:03 - 08:57)

• - Assigning responsibilities for contacting different parties for payment collection.

• - Strategy to engage with specific individuals for effective follow-ups.

Chapter 3: Finance Leadership Transition (09:32 - 13:20)

• - Transitioning roles to focus on finance leadership responsibilities.

• - Mention of new hire and potential shifts in responsibilities.

Chapter 4: Payment Collection Strategies (15:13 - 17:54)

• - Strategies for collecting payments and engaging with specific contacts.

• - Discussion on industry standards and effective payment collection approaches.

Chapter 5: Financial Transactions and Disputes (18:07 - 20:37)

• - Handling financial transactions and disputes related to credit card accounts.

• - Request for creating a logo for a t-shirt design.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-16 13:22:41

• This outline focuses on key decisions and actions related to invoicing, finance leadership, payment collection, and financial transactions without including small talk or redundant information.

Shorthand Bullet • 📊 *Sorting of Messages*

• - Messages should be sorted by client name, not date.

• 📞 *Follow-up on Outstanding Invoices*

• - Ryan to send contact information for outstanding invoices to Brian.

• - Brian to involve all attorneys and relevant parties for better attention.

• 💰 *Payment Follow-up Strategy*

• - Ryan suggests a strategy for following up on payments with John and others.

• - Brian to handle follow-ups and involve Ryan for support.

• 📧 *Email Communication Strategy*

• - Coordination on email communication to ensure timely responses and follow-ups.

• - Specific email addresses and communication methods discussed for effective responses.

• 💻 *Invoice Management*

• - Instructions on marking actions in Harvest for invoice management.

• - Brian to record payments and add notes as necessary.

• 📈 *Client Payment Collection*

• - Ryan offers assistance in collecting payments, particularly from Focus Litigation Solutions.

• - Strategy discussed for authoritatively requesting payments and managing outstanding accounts.

• 📝 *Task Delegation*

• - Brian to handle recording payments for specific tasks, including Ben Crump.

• - Clarification on process and responsibilities for charging and notifying clients.

• 🔍 *Google* Request Handling**

• - Discussion on managing Google requests and ensuring accurate lead information.

• - Importance of clarifying the source of funds and managing accounts like Focus Litigation Solutions.

Gist • Discussion on outstanding invoices, payment follow-ups, and strategies for debt recovery. Emphasis on timely collections, industry norms, and tailored client approaches. Brian Thiessen and Ryan Vaspra collaborated on efficient debt recovery processes and customized invoicing procedures.

Bullet Gist • ⚖️ Debt Recovery Strategies: Discussed timely collections and assertive client engagement.

• 💼 Industry Insights: Shared norms in media buying budgets and billing disputes with Google.

• 🤝 Effective Communication: Highlighted communication strategies for individuals like Elena and Steven Giacovino.

• 💰 Efficient Collections: Agreed on hiring a strong bill collector for streamlined collections.

• 📝 Tailored Approaches: Acknowledged the importance of tailored strategies for specific clients.

Short Summary • The discussion between Ryan Vaspra and Brian Thiessen centered on reviewing outstanding invoices, prioritizing payment follow-ups, and devising strategies for effective debt recovery. They focused on sorting invoices by client names, identifying overdue payments, and engaging assertively yet tactfully with slow-paying clients. Insights were shared on managing digital services, financial transactions in advertising, media buying budgets, and interactions with Google for billing disputes. Emphasis was placed on tailored client approaches, hiring a strong bill collector, and efficient collections moving forward, with a commitment to prompt payment collection and customized invoicing procedures.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-18 11:17:49

Title: Media Buyer performance Date: Thu Apr 18 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* discussed tracking sports data and adjusting budgets for lead generation success. Emphasizing the need for higher daily budgets compared to lead costs in Facebook ads, he highlighted pacing budgets for effective campaign management. *Lee* Zafra** briefly contributed to the conversation, where they reviewed charts, analyzed averages, adjusted formulas, and finalized summaries.

• The discussion continued with planning future sessions, rescheduling activities, and updating charts with new data points while keeping an eye on budget allocation until May 4th. They then talked about ensuring marketing campaigns are adequately funded to generate leads efficiently and discussed litigation solutions. The meeting involved detailed discussions on managing data analytics tools effectively and optimizing ad spending based on cost per lead metrics.

• *Ryan Vaspra* underlined the importance of pacing budgets and effective campaign management. The dialogue emphasized the need for higher daily budgets in Facebook ads than lead costs, focusing on adjusting budgets for lead generation success. Conversations delved into strategizing upcoming tasks within specified timelines and efficient resource allocation.

• In summary, the meeting involved strategizing tasks, maintaining a focus on efficient resource allocation, and managing data analytics tools effectively. The discussions further revolved around optimizing ad spending based on cost per lead metrics and ensuring campaigns are adequately funded for efficient lead generation. Throughout, *Ryan Vaspra* emphasized pacing budgets for effective campaign management and higher daily budgets in Facebook ads.

Action Items • *Ryan Vaspra*

• Check if the dashboard is showing live results (05:57)

• Update the budget to be at least two to three times higher than cost per lead for Facebook ads (15:35)

• Send a specific item to someone (16:44)

Outline Chapter 1: Initial Data Analysis and Dashboard Evaluation (03:04 - 06:24)

• - 03:09: Discussion on analyzing data from the dashboard for decision-making.

• - 05:06: Emphasis on continuous data accumulation for a comprehensive overview.

Chapter 2: Budget Adjustments and Campaign Optimization (13:36 - 15:44)

• - 14:30: Budget considerations for effective campaign management.

• - 15:28: Importance of adjusting daily budget to optimize lead generation.

Chapter 3: Performance Metrics and Lead Generation Strategy (15:44 - 17:07)

• - 16:06: Reviewing lead generation metrics for campaign effectiveness.

• - 17:05: Concluding remarks on campaign progress and next steps.

Shorthand Bullet • 📊 *Reviewing Performance Metrics*

• - *Average raw leads per day discussed*

• - Ryan Vaspra suggested adjusting daily budget for better lead generation

• - Emphasis on maintaining a budget higher than cost per lead

• 📅 *Scheduling and Budgeting*

• - Adjustments made for future dates in the budget

• - Discussion on rescheduled sessions and budget allocation

• - Specific focus on budget pacing for effective campaign management

• 📈 *Analyzing Campaign Effectiveness*

• - Importance of pacing campaign to align with monthly goals

• - Consideration of lead cost in Facebook ads for budget planning

• - Highlighted the significance of a sufficient daily budget for lead generation

• 📍 *Action Items*

• - Ryan Vaspra to send information to a specific individual

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-18 11:17:49

• - Follow-up needed on updating certain metrics or information

• 🤝 *Appreciation*

• - Positive interaction and appreciation shown between participants

Gist • Strategizing tasks, efficient resource allocation, optimizing ad spending, and funding for lead generation were key points. Importance of pacing budgets and higher daily budgets in Facebook ads emphasized.

Bullet Gist • ⚙️ Strategizing Tasks: Planning future sessions and rescheduling activities within specified timelines.

• 💰 Resource Allocation: Ensuring marketing campaigns are adequately funded for efficient lead generation.

• 📊 Optimizing Ad Spending: Adjusting budgets based on cost per lead metrics for effective campaign management.

• ⏳ Pacing Budgets: Emphasizing the need for higher daily budgets in Facebook ads compared to lead costs.

Short Summary • The meeting focused on strategizing tasks within timelines, efficient resource allocation, optimizing ad spending, and ensuring adequate funding for lead generation. Ryan Vaspra highlighted the importance of pacing budgets and higher daily budgets in Facebook ads compared to lead costs. Lee Zafra also contributed to discussions on analyzing data and adjusting formulas. The dialogue revolved around managing data analytics tools effectively and optimizing ad spending based on cost per lead metrics. The participants emphasized the need for effective campaign management and discussed litigation solutions, emphasizing the importance of higher daily budgets in Facebook ads for successful lead generation.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-18 14:41:11

Title: BCL Next Steps Date: Thu Apr 18 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting began with *Adrienne Hester, Desiree A, Jonathan Wright, and Uzoma Obasi* discussing updates and plans. *Jonathan spoke about a forthcoming visit to implement new software for smart advocate with Nick and an attorney. He also mentioned setting up a campaign during the visit to the Vegas office with Precious* for the Glosser case. *Adrienne* shared updates from Ryan about the Conex system numbers push, NVA LSA campaign, SEO focus on auto accident pages, and inquired about backlink strategies.

• *Desiree* sought clarification on backlink strategies from *Uzoma* for SEO purposes. *Uzoma* expressed readiness to collaborate with Brooke and Cliff on implementation ideas but needed more details. *Adrienne emphasized pending case categories and the retainer contract crucial before moving forward with tasks related to Ben's booking processes. Jonathan* noted careful planning for the Vegas trip around May 7th due to high costs.

• *Adrienne* relayed information about moving forward with existing contracts while awaiting specific departmental actions. The meeting concluded with *Jonathan having to attend another call after a challenging discussion with lenders, offering assistance if needed. The overall discussion revolved around project updates, digital marketing strategies like backlinks for SEO optimization, and operational plans for upcoming visits involving key team members such as attorneys Precious* and Brian.

Action Items • *Adrienne Hester*

• Reach out to Ryan for clarification on SEO strategies (06:58)

• Have an internal meeting on implementation (07:58)

• *Jonathan Wright*

• Update everyone about the upcoming visit with Precious and the glosser case (09:12)

Outline Chapter 1: Team Updates and Software Implementation (04:59 - 08:04)

• - Updates on Conex system numbers and NVA LSA campaign progress.

• - Plans for software implementation to aid in case referrals and reporting.

• - Discussion on backlink domain strategies for SEO.

Chapter 2: Legal Case Progress and Campaign Preparation (08:11 - 09:55)

• - Delays in receiving case categories and retainer contract.

• - Preparation for glosser case campaign and attorney involvement.

Chapter 3: Project Coordination and Departmental Responsibilities (10:16 - 10:47)

• - Coordination of upcoming events and research into related activities.

• - Departure of a team member necessitating communication protocols.

Chapter 4: Final Updates and Task Assignments (11:02 - End)

• - Request for specific tasks or needs from team members.

• - Conclusion of the meeting with action items and follow-up tasks.

Shorthand Bullet • 📊 *Updates on Marketing Campaigns*

• - *Jonathan Wright* is implementing new software for Smart Advocate to assist *Desiree* A** with case referrals.

• - NVA LSA campaign is active, with an average of 40 calls per day to the tip team.

• - SEO focus remains on optimizing Texas and national auto accident pages.

• 🔗 *SEO Strategy Discussion*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-18 14:41:11

• - *Adrienne Hester* inquires about backlink domain social engagement strategies for SEO.

• - *Uzoma Obasi* has ideas but requires clarification on process for Ben's bookings to implement them effectively.

• 📅 *Implementation Progress and Internal Meetings*

• - *Adrienne Hester* notes the need for an internal meeting on implementation.

• - Waiting for case categories and retainer contract updates.

• - *Jonathan Wright* plans to bring an attorney, *Precious*, to set up a campaign during a visit.

• 🔍 *Contractual Progress*

• - Contract is ready for the next department's review and action, not an immediate concern.

• - *Jonathan Wright* to involve *Precious* in understanding the campaign for efficient progress.

• 📞 *Wrap-up and Next Steps*

• - *Jonathan Wright* has to leave for another call, requests updates if needed.

• - *Uzoma Obasi* has no immediate requests, mentions needing to contact *Jonathan Wright* later.

Gist • Discussion on project updates, digital marketing strategies, and operational plans involving key team members like attorneys. Key points: software implementation, campaign planning, backlink strategies, and contract considerations.

Bullet Gist • ⚙️ Software Implementation: Jonathan discussed new software implementation for Smart Advocate.

• 📈 Campaign Planning: Plans were made for a campaign in the Vegas office for the Glosser case.

• 🔗 SEO Strategies: Adrienne inquired about backlink strategies for SEO optimization.

• 💼 Contract Considerations: Adrienne stressed the importance of pending case categories and retainer contracts.

• 🗓️ Operational Planning: Jonathan highlighted careful planning for an upcoming Vegas trip.

Short Summary • The meeting involved Adrienne, Desiree, Jonathan, and Uzoma discussing project updates, digital marketing strategies, and operational plans. Jonathan mentioned upcoming software implementation for Smart Advocate with Nick and an attorney, as well as planning a campaign for the Glosser case with Precious. Adrienne shared updates on the Conex system, NVA LSA campaign, SEO focus, and inquired about backlink strategies. Desiree and Uzoma discussed SEO backlink strategies, collaboration with colleagues, and pending case categories. Adrienne emphasized the importance of retainer contracts before proceeding with tasks, and Jonathan highlighted careful planning for an upcoming Vegas trip. The meeting concluded with Jonathan offering assistance after a challenging discussion with lenders, with a focus on project updates, digital marketing strategies, and operational plans for future visits involving key team members.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-22 12:13:53

Title: TV Campaign Name updates Date: Mon Apr 22 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting began with *Ryan Vaspra and Brian Hirst discussing the need for changes in databases like leads, PDA, law ruler, and copper, emphasizing consistency in naming conventions. Ryan* assigned tasks and expressed frustration over unauthorized changes made by Anthony. They addressed challenges with colleagues not following instructions, discussing the impact on live campaigns due to naming convention issues. The importance of aligning with established naming patterns for consistency was stressed.

• The conversation then delved into technical details on manipulating data strings in databases and ensuring accurate information flow between systems. Concerns about efficiency improvements through process streamlining and module integrations were shared by *Brian*. They explored future developments like a potential delivery module for improved information processing. The focus shifted to finalizing changes in channel names based on vertical abbreviations to enhance clarity across services.

• The meticulous attention to detail in database updates was evident as they aimed for seamless integration across platforms while emphasizing adherence to standardized procedures. Throughout the discussion, the consequences of changing names without proper coordination were highlighted, risking campaign integrity. The meeting concluded with a strong emphasis on maintaining consistency in naming conventions to enhance workflow reliability. The collaborative effort between *Ryan and Brian* underscored the importance of carefully planned database modifications and adherence to established procedures for successful integration across systems.

Action Items • *Ryan Vaspra*

• Update copper in the database (01:07)

• Rename tv campaigns across all software to match from lp to tip dash (05:55)

• Simplify customer string by creating a field called customer firms in copper (07:22)

• Take care of LA, Maryland, and SS names for contracts in law ruler and leads PDF (25:45)

• *Brian Hirst*

• Take care of law ruler, lead PDF changes for BG, DL, and XSS verticals (40:28)

Outline Chapter 1: Database Management Plan (00:34 - 05:55)

• 00:34: Plan division of tasks - copper database, law ruler, and leaf PDF.

• 05:55: Renaming TV campaigns across all software for consistency.

Chapter 2: Data Management Implementation (08:17 - 13:45)

• 08:17: Clarification on changing deal names in copper to match leaf PDF.

• 13:45: Updating delivery methods for seamless integration between systems.

Chapter 3: Project Integration and Timeline (15:51 - 17:32)

• 15:51: Discussion on potential delays and impact on data warehouse implementation.

• 17:32: Agreement on the efficiency of direct integration between systems.

Chapter 4: System Optimization and Efficiency (18:02 - 27:06)

• 18:02: Planning for streamlined processes to save time and enhance efficiency.

• 27:06: Adjusting contract names and delivery methods for optimal system performance.

Chapter 5: Channel Creation and Customer Data Segmentation (39:04 - 40:39)

• 39:04: Importance of client names and verticals isolation for effective routing.

• 40:39: Decision to use abbreviated versions for channel names to protect customer information.

Shorthand Bullet • 📊 *Renaming Campaigns*

• - *Ryan and *Brian are renaming TV campaigns across all software to ensure matching from LP to Tip Dash.

• - Renaming to match verticals and campaign IDs.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-22 12:13:53

• - Using vertical key and campaign ID in CTM and Leads PDF.

• - *FYI: Changes will be shared with *Cameron directly.

• 🔧 *System Configuration*

• - Updating deal names in Copper from salesperson to match Leads PDF.

• - Discussing LR to CNX transition with Brian.

• - Finalizing project setup details.

• - Ensuring data accuracy in Law Ruler module for post-outs.

• ⏰ *Timeline and Commitment*

• - Waiting on Cameron meeting for project timeline.

• - Discussing Law Ruler's commitment to webhook module for efficient data handling.

• - Confirming $45,000 includes necessary changes for user statuses.

• 🛠️ *Efficiency and Decision Making*

• - Eliminating Law Ruler to Zapier process for time savings.

• - Decision on continuing with Law Ruler based on commitments and timelines.

• - **Stabilizing Law Ruler usage for future efficiency.

• 📝 *Case Type Management*

• - Updating case type names in Law Ruler.

• - Simplifying client names and verticals for proper routing.

• - Using abbreviated versions for customer privacy.

Gist • Database meeting focused on naming conventions, data integrity, and system integration for consistency. Task assignments, frustration over unauthorized changes, and emphasis on adherence to established procedures highlighted.

Bullet Gist • ⚙️ Naming Conventions: Emphasis on consistency in database naming conventions.

• 📊 Data Integrity: Focus on accurate information flow and data manipulation.

• 🤝 Collaborative Effort: Ryan and Brian work together for system integration success.

• 🔍 Attention to Detail: Meticulous approach to database updates for seamless integration.

• ⚠️ Risk Management: Highlighting consequences of unauthorized changes on campaign integrity.

Short Summary • The meeting revolved around the importance of consistent naming conventions in databases like leads, PDA, law ruler, and copper to ensure data integrity and system integration. Ryan Vaspra and Brian Hirst assigned tasks, expressed frustration over unauthorized changes, and emphasized the need for adherence to established procedures. They discussed challenges with colleagues not following instructions, the impact on live campaigns due to naming convention issues, and the importance of aligning with established naming patterns for consistency. Technical details on data manipulation, ensuring accurate information flow, efficiency improvements, future developments like a potential delivery module, and finalizing changes in channel names were explored. The meticulous attention to detail in database updates, the risk of changing names without coordination, and the collaborative effort between Ryan and Brian for successful integration across systems were key points of discussion.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-22 13:47:38

Title: Tech Project Status Weekly Date: Mon Apr 22 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting primarily discussed *software solutions* such as the *integration project Dialer* and a potential shift from *law ruler to Salesforce. Mike Everhart,* Ryan Vaspra, James Scott,** and others shared insights on data engineering, lead integration projects, and CRM events setup in platforms like Facebook. Considerations focused on software changes, API implementations, and challenges with platform transitions, maintaining stability amid operational needs being a concern.

• Ongoing tasks involved setting up a *drug master prediction model*, working on funnel events for Facebook ads, and managing CRM event testing in ad accounts. Team dynamics, particularly regarding hiring decisions for roles like an integration developer, were addressed. Emphasized was the need for effective orchestration among team members for smooth operations during potential software shifts.

• Maintaining stability amidst software changes and balancing technical requirements with operational needs were key concerns. Complexity in transitioning major platforms, ensuring seamless operations during adjustments or integrations across different software tools, was discussed. Collaboration efforts among team members aimed at aligning technical solutions with business goals, navigating potential software transitions were highlighted.

• Key takeaways included the importance of effective orchestration within the team, aligning technical solutions with business goals. Collaborative efforts among team members were aimed at navigating potential software transitions. Challenges involving platform transitions, maintaining stability during software changes, and balancing technical requirements were emphasized, along with the need for seamless operations across different software tools.

Action Items • *Mike Everhart*

• Set up CRM event steps in Facebook Ads Manager (29:12)

• Access and set up ESIGN CRM conversion event testing in the USA Consumer Network account (36:33)

• Confirm accounts to work on with Maximus through Telegram app (39:14)

Outline Chapter 1: Project Integration and Decision Making (04:27 - 06:03)

• 04:27: Discussion on the Dialer and lead integration project, focusing on the Law Ruler API.

• 05:23: Decision-making process regarding the Salesforce implementation and its impact on the project timeline.

Chapter 2: Data Mapping and SQL Queries (08:18 - 10:59)

• 08:18: Work on SQL statements for weekly reporting and mapping questions.

• 09:20: Plans to create intermediate tables and conduct data transformations.

Chapter 3: Automation and Benchmark Reports (14:21 - 16:09)

• 14:21: Plans to automate the Flatiron's benchmark report and discuss API testing.

• 15:22: Focus on automating processes and discussing proof of concept for API functionality.

Chapter 4: Data Transformation and Integration (20:33 - 22:15)

• 20:33: Discussion on data transformation and managing business settings.

• 22:15: Further planning on data integration and setting up CRM conversion event testing.

Chapter 5: Orchestration and Career Development (43:02 - 44:52)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-22 13:47:38

• 43:02: Importance of orchestration and career development guidance from Cameron.

• 44:40: Noting due dates for future checkpoints and expressing gratitude for the discussion.

Shorthand Bullet • 📊 *Dialer and Lead Integration Project*

• - Ryan Vaspra scheduled a meeting with Nick and Mike to discuss the Law Ruler API.

• - They will have a meeting to review the dialer and lead integration project.

• 📋 *SQL Statements and Mapping Questions*

• - Mike Everhart is working on SQL statements for weekly reporting.

• - He has mapping questions regarding finding specific information for weekly expenses.

• 🔗 *DBT Meeting Setup*

• - Mike suggested labeling the upcoming meeting as a DBT meeting.

• - Ryan will include Mike in the YAML meeting with Brian to address his mapping questions.

• 📱 *API Testing and Proof of Concept*

• - Nick McFadden mentioned doing a test proof of concept for the API with JP from Cello.

• - They discussed passing and sharing data through the API and Google's role in serving it.

• 🌐 *Webhook Implementation Strategy*

• - Ryan discussed utilizing webhooks to invoke APIs in Google Cloud for their solution.

• - They aim to develop an app to simplify webhook insertion and schema mapping for basic users.

• 📅 *Upcoming Checkpoints and Due Dates*

• - Ryan noted due dates for the next week's checkpoint.

• - Mike Everhart mentioned discussing Salesforce in the next ten minutes and upcoming tasks related to it.

Gist • The meeting discussed software solutions like the integration project Dialer and a potential shift to Salesforce, focusing on data engineering, CRM events setup, and team dynamics. Challenges included software changes, API implementations, and maintaining stability amid operational needs.

Bullet Gist • ⚙️ Software Solutions: Integration project Dialer and potential shift to Salesforce.

• 📊 Data Engineering Insights: Lead integration projects and CRM events setup.

• 💼 Team Dynamics: Hiring decisions for roles like integration developers.

• 🛠️ Operational Challenges: Maintaining stability amid software changes and transitions.

• 🔄 Platform Transitions: Challenges with software transitions and seamless operations.

Short Summary • The meeting delved into software solutions such as the integration project Dialer and a potential move to Salesforce. Discussions encompassed data engineering insights, CRM events setup in platforms like Facebook, ongoing tasks like the drug master prediction model, and team dynamics including hiring decisions for roles like integration developers. Emphasis was placed on maintaining stability during software changes, balancing technical requirements with operational needs, and navigating potential platform transitions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-22 16:30:44

Title: Shield <> Sonobi Weekly Date: Mon Apr 22 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@shield-legal.com, cschwarz@sonobi.com, swilcox@sonobi.com, kristopher@shield-legal.com, tony@tortintakeprofessionals.com, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Craig Schwarz* led a meeting with *Kristopher Standley, Cameron Rentch, and Ryan Vaspra* to discuss Ace TV's TV campaigns. They reviewed Facebook CPL metrics, analyzed campaign performance by tier and channel, and aimed to optimize spending towards specific demographics. The team emphasized narrowing down channels for better targeting results, focusing on effective platforms rather than spreading resources too thin.

• The discussion covered analyzing ad performance based on frequency capping and publisher selection. Strategies included tightening spending parameters, optimizing impressions on key networks like BET, leveraging data cuts for audience segmentation, and using log-level data insights for smarter decision-making. They agreed to concentrate efforts on high-performing channels and refine targeting strategies based on demographic preferences from successful campaigns.

• The team explored tracking conversion paths through their ad server logs to improve understanding of user interactions. They suggested enhancing efficiency by streamlining spend allocation towards more productive advertising avenues. By continuously refining targeting strategies based on demographic insights, they aimed to improve campaign effectiveness and reach a more tailored audience.

• In their efforts to enhance efficiency, the team focused on streamlining spend allocation towards productive advertising avenues. By concentrating on high-performing channels and refining targeting strategies, they aimed to improve campaign effectiveness and reach a more tailored audience.

Action Items • *Craig Schwarz*

• Review linear options (04:11)

• Confirm the meaning of CPL (05:00)

• Analyze lead id status changes (06:11)

• Check on the spending from 18th and investigate if there was an issue (07:28)

• Ensure clarity on Facebook CPL's and cost per call metrics (14:21)

• *Cameron Rentch*

• Address building air conditioning issue as a hard stop in 20 minutes (10:08)

• *Kristopher Standley*

• Provide Craig with the link for spin submission form (28:16)

Outline Chapter 1: Campaign Review and Optimization (03:35 - 13:51)

• 03:35: Discussion about setting up a weekly call to review TV campaigns.

• 03:59: Proposal to have daily spend updates shared for better tracking.

• 11:29: Automation suggestions for tracking daily spend efficiently.

• 13:05: Implementing a system to report leads to media buyers for optimal spending.

Chapter 2: Data Analysis and Optimization Strategies (15:24 - 26:42)

• 15:24: Importance of analyzing lead data and CPM buckets.

• 17:26: Focus on frequency capping and optimizing channel impressions.

• 25:28: Layering audience cuts for targeting demographics effectively.

• 26:23: Aligning spend with audience consumption habits for strategic targeting.

Chapter 3: Strategic Decision-Making and Evaluation (27:53 - 28:37)

• 27:53: Emphasizing the importance of strategic decisions in the campaign.

• 28:12: Final remarks on strategy and next steps for optimization.

• 28:26: Wrapping up the discussion and planning for the next meeting.

Shorthand Bullet • 📊 *Weekly TV* Campaign Review**

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-22 16:30:44

• - *Craig, *Cam suggests a weekly call to discuss TV campaigns**

• - *Craig to provide notes, drive leads*

• - *Kristopher explains lead ID tracking*

• 🔍 *Lead Tracking and Optimization*

• - *Discussion on lead sources and tracking methods*

• - *Craig seeks clarity on tracking and dashboard integration*

• - *Ryan suggests frequency-based targeting strategy*

• 📈 *Channel and Budget Optimization*

• - *Ryan advises optimizing spend based on channel frequencies*

• - *Cameron highlights challenges of channel budget allocation*

• - *Craig emphasizes aligning strategy with audience behavior*

Gist • Team meeting focused on optimizing TV campaigns by narrowing channels, refining targeting, and using data insights for better ad performance. Emphasis on efficient spend allocation and demographic-based strategies.

Bullet Gist • ⚙️ Optimizing TV Campaigns: Focused on narrowing channels and refining targeting for better performance.

• 📊 Data-Driven Decisions: Emphasized leveraging data insights for ad optimization.

• 💡 Efficient Spending: Discussed streamlining spend allocation towards productive avenues.

• 🔍 Targeting Strategies: Agreed to refine targeting based on demographic preferences.

• 📈 Improving Effectiveness: Aimed to enhance campaign effectiveness through focused efforts.

Short Summary • The team, led by Craig Schwarz, delved into optimizing Ace TV's campaigns by narrowing down channels, refining targeting strategies, and leveraging data insights for improved ad performance. They discussed analyzing Facebook CPL metrics, campaign performance by tier and channel, and optimizing spending towards specific demographics. Strategies included tightening spending parameters, focusing on high-performing channels like BET, and refining targeting based on successful campaigns. They explored tracking conversion paths through ad server logs, streamlining spend allocation, and continuously refining targeting strategies to reach a more tailored audience and enhance campaign effectiveness.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-23 11:26:54

Title: BLX Media Buying Date: Tue Apr 23 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, lee@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting commenced with *Ryan Vaspra highlighting the team's productivity and demonstrated a SQL script for generating pipeline reports efficiently using Gemini and chat GDP tools. They discussed tracking charge leads and verifying lead sources, focusing on marketing campaigns to generate leads from regions like Texas through platforms including Smart Advocate. Lee* Zafra* and *Ryan Vaspra** meticulously reviewed lead counts, strategizing to streamline reporting processes for better insights into campaign performance. They stressed the importance of updating reports regularly to track costs per lead accurately.

• The conversation shifted towards examining the effectiveness of various marketing campaigns, particularly focusing on generating leads from specific regions like Texas through platforms such as Smart Advocate. *Lee* Zafra* and *Ryan Vaspra reviewed lead counts meticulously, discussing strategies to streamline reporting processes for better insights into campaign performance. The meeting briefly touched upon incoming leads from Navy Camp Lejeune in **Maryland, highlighting efforts to monitor different lead sources effectively. They emphasized updating reports regularly to track costs per lead accurately and ensure alignment with ongoing initiatives while exploring avenues for improved data organization.

• Towards the end of the meeting, they delved into tracking charge leads and verifying lead sources like LSA for potential contracts. The conversation encompassed examining the effectiveness of various marketing campaigns, particularly focusing on generating leads from specific regions like Texas through platforms such as Smart Advocate. They touched upon incoming leads from Navy Camp Lejeune in Maryland, highlighting ongoing efforts to monitor different lead sources effectively. The meeting concluded with a summary of active leads and a mutual acknowledgment of their progress before wrapping up cordially.

Action Items • *Ryan Vaspra*

• Update the report with the date 'April 23rd' (18:39)

• Make sure to update the column with the data and spin (10:02)

• Add a case review summary to match from the dashboard for Cameron (20:05)

• *Lee Zafra*

• Count how many charge leads there are from beginning to end (09:03)

Outline Chapter 1: Project Overview and Progress (00:03 - 04:08)

• 00:03: Initial discussion on the project status and challenges faced.

• 02:03: Introduction to a new SQL report to streamline processes.

• 04:00: Mention of utilizing Shield's dashboard for media buying insights.

Chapter 2: Lead Management and Reports (05:37 - 09:44)

• 05:38: Decision to use phone numbers for charge leads for efficiency.

• 09:03: Request to update lead count and report regularly.

Chapter 3: Data Analysis and Reporting (11:15 - 14:21)

• 11:15: Review of leads and case types for analysis.

• 14:01: Discussion on case reviews and updates for Cameron.

Chapter 4: Progress Tracking and Metrics (16:04 - 19:35)

• 16:04: Tracking of leads and updates on case reviews.

• 19:35: Formula creation for analyzing data and providing insights.

Chapter 5: Future Planning and Reporting (20:50 - 22:31)

• 20:50: Planning for future case review summaries.

• 21:29: Discussion on generating reports for specific case types.

Chapter 6: Project Review and Closing (23:47 - 25:12)

• 23:50: Review of previous week's progress and updates.

• 25:10: Appreciation for efforts and conclusion of the meeting.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-23 11:26:54

Shorthand Bullet • 📊 *Weather Discussion*

• - Spring weather discussed by *Ryan Vaspra and Lee* Zafra**.

• - *Ryan* mentioned it's not rocket science due to the consistent weather across the country.

• 🛠️ *Database Update*

• - *Ryan* presented a SQL view to convert field orders into a pipeline report.

• - They discussed past productivity and lack of unnecessary activities.

• 📞 *Lead Management*

• - Emphasis on obtaining phone numbers for charge leads from Texas.

• - *Lee* to update lead counts and data columns regularly.

• 📈 *Lead Tracking*

• - Tracking of charge leads discussed, current count stands at 335.

• - *Ryan* emphasized the importance of keeping track of daily lead updates.

• 📅 *Report Updates*

• - Request to update the report with correct dates and lead counts daily.

• - Importance of accurate data presentation for reporting purposes discussed.

• 📑 *Case Review Summary*

• - Plan to create a summary for case reviews in the report.

• - Future request for an export of all Texas cases from Smart Advocate for analysis.

• 📊 *Data Analysis*

• - Discussion on organizing data for analysis and reporting.

• - *Ryan* emphasized the need for accurate tracking and reporting of Texas leads.

Gist • Team discussed lead tracking, campaign effectiveness, and data organization. Emphasis on generating leads from specific regions and updating reports for accurate insights. Productivity and efficiency highlighted using Gemini and chat GDP tools.

Bullet Gist • ⚡ Productivity Highlight: Ryan showcased SQL script for efficient pipeline reports using Gemini and chat GDP tools.

• 📊 Lead Tracking Focus: Emphasis on tracking charge leads, verifying lead sources, and updating reports for accurate insights.

• 🎯 Campaign Effectiveness: Strategizing to streamline reporting processes for better campaign performance analysis.

• 🗺️ Regional Lead Generation: Discussion on generating leads from specific regions like Texas through platforms such as Smart Advocate.

• 💼 Data Organization: Efforts to monitor different lead sources effectively and ensure accurate cost tracking per lead.

Short Summary • The team meeting focused on lead tracking, campaign effectiveness, and data organization. Ryan Vaspra showcased a SQL script for pipeline reports using Gemini and chat GDP tools. Lee Zafra and Ryan Vaspra strategized on streamlining reporting processes for insightful campaign performance analysis. They emphasized the importance of updating reports regularly to track costs per lead accurately. The discussion covered generating leads from regions like Texas through platforms such as Smart Advocate and monitoring lead sources effectively, including from Navy Camp Lejeune in Maryland. The meeting concluded with a summary of active leads and progress acknowledgment.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-23 14:04:10

Title: Dashboard Creation Working Session Date: Tue Apr 23 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • *James Scott* and *Luke Fontaine set up connections and joins in Looker for Unicorn and adverse event databases from BigQuery. They managed data sources, created joins, and filtered data effectively using table infrastructure. They added multiple tables, set up joins, and resolved blending issues. James mentioned needing a fuzzy match for drug names, while Luke focused on calculated fields and James* on Python scripts for automation.

• Discussing hosting machine learning models in AWS services, they aimed to integrate metrics like deaths and hospitalizations for visualization in Looker Studio. Despite technical challenges, they laid a foundation for development and analysis within their roles effectively.

Action Items • *James Scott*

• Create a new field name in here to relate the drug ranking model results to the unicort data (02:21)

• Develop some summary metrics on high-level information like number of deaths, hospitalizations, serious outcomes, and percent change in rank over a year-to-year basis (20:45)

• Write a calculated field for percent change in rank based on year (21:40)

• *Luke Fontaine*

• Focus on the Looker aspect of it and work on creating calculated fields (46:32)

Outline Chapter 1: Setting Up Table Infrastructure (00:06 - 03:13)

• 00:06: James Scott initiates discussion on table infrastructure and joins.

• 01:44: Luke Fontaine confirms the number of total tables.

• 03:01: Luke Fontaine lists specific tables like case analytics and case documents.

Chapter 2: Data Joins and Relationship Building (05:26 - 14:03)

• 05:29: Luke Fontaine offers to assist in defining joins and columns.

• 11:16: James Scott explains the joins between tables like case analytics and case search.

• 13:13: Discussion on developing relationships between different data points.

Chapter 3: Data Visualization and Model Integration (16:32 - 26:25)

• 16:32: James Scott explains the process of integrating aggregate data and predictive models.

• 21:45: Importance of capturing metrics like percent change in rank for visualization.

• 25:50: James Scott updates on creating columns for model results and case IDs.

Chapter 4: Workflow Automation and Data Refresh (33:13 - 38:07)

• 34:47: James Scott discusses setting up data refresh schedules for automation.

• 37:12: Luke Fontaine works on scripting and data management processes.

Chapter 5: Future Enhancements and Project Wrap-Up (52:56 - 59:28)

• 52:56: Discussion on future queries, scripting requirements, and business needs.

• 58:37: Planning for next steps and finalizing project goals for implementation.

Shorthand Bullet • 📊 *Starting Data* Analysis**

• - *James Scott* suggests starting the analysis process.

• - *Luke Fontaine* agrees and mentions working on tables and joins.

• 🔄 *Joining Tables*

• - Discussion on managing blends and joins between tables.

• - *James Scott* explains the need for specific joins between tables.

• 📊 *Developing Data* Metrics**

• - *James Scott* emphasizes the need to gather metrics for a summary page.

• - Metrics discussed include number of deaths, hospitalizations, serious outcomes, and percent change in rank.

• 🔍 *Adding Aggregate Data*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-23 14:04:10

• - The goal is to add aggregate data from Python predictive models to the data table.

• - Focus on connecting data for better visualization, like heat maps.

• 📈 *Creating New Fields*

• - *James Scott* talks about creating new fields to relate data for analysis.

• - Mention of creating a new column for specific data relationships.

• 📉 *Ranking Models Integration*

• - Integrating ranking model results with existing data for analysis.

• - Discussion on matching fields for data coherence.

• 🧮 *Data Refresh and Validation*

• - *Luke Fontaine* suggests data refresh strategies.

• - Validation and verification of data integrity discussed.

• 🚀 *Moving Forward*

• - Agreement to work on revisions and further development.

• - *James Scott* expresses readiness to progress with the project.

Gist • James and Luke set up connections and joins in Looker for data sources, focusing on data filtering, joins, and resolving blending issues. They discussed integrating machine learning models in AWS for visualization in Looker Studio.

Bullet Gist • ⚙️ Data Management in Looker: Set up connections, created joins, and filtered data effectively.

• ⚖️ Data Blending: Resolved blending issues by adding multiple tables and setting up joins.

• 🔍 Data Enhancement: James mentioned the need for fuzzy match for drug names.

• ⚡ Automation Focus: James worked on Python scripts for automation, while Luke focused on calculated fields.

• 🌐 AWS Integration: Discussed hosting machine learning models in AWS for data visualization in Looker Studio.

Short Summary • James and Luke worked on setting up connections and joins in Looker for Unicorn and adverse event databases from BigQuery. They managed data sources, created joins, and filtered data effectively. James highlighted the need for fuzzy match for drug names, while Luke focused on calculated fields, and James on Python scripts for automation. They also discussed hosting machine learning models in AWS services to integrate metrics like deaths and hospitalizations for visualization in Looker Studio, overcoming technical challenges to lay a solid foundation for development and analysis within their roles.

Ryan (ryan@themedialab.agency)
2024-04-23 15:03:05

LawRuler Meeting Strategy

Meeting Plan:

Goal: Get discount on $46K for 3 API features or package more features into scope of $46K and ensure we have control of payment over schedule of delivery.

One of those Billable Statuses Feature so leads in a series-of-statuses cannot be changed once flagged billable unless new status is marked billable.

Strategy: Back them into a mutually aligned position with commonality of goals, while stressing our knowledge of the situation and features to get rate, hours decreased or scope of features increased

Sequential Talk Tracks:

  1. First, we are all on the same team, but our side of the locker room just wants to ensure that any solution ensures all of our LawRuler stakeholders walk away happy, right Dean?
  2. So if we can get LR some value better features and custom dev revenue, build a deeper relationship with a large and growing key account, but ensure that all stakeholders at our companies are happy with the deliverables of the $46K, I think we can have a team win here, you agree Dean?
  3. Also, noting that Cameron and our teams key project consideration be timeline, what is the schedule for delivery on the SOW as it stands now?
  4. Can we have it faster?
  5. Please send us a schedule and please put major milestones into the schedule, as we will require to pay out on milestones to ensure we do not find ourselves in a situation of non-delivery. I hope you understand.
  6. In my experience as custom development engineer and professional services and using todays market rates at $200 per hour custom dev, $46K is 230 hours. Is that how the $46K total cost was calculated? What is the rate on that?
  7. Now with this agreement in place (on this call), if we said right now, "we are good" we would spend X on the API features and that would make only us developers happy, so of these many, many features, lets talk about the one that is truly important: a. Billable Statuses - One of those Billable Statuses Feature so leads in a series-of-statuses cannot be changed once flagged billable unless new status is marked billable or something that achieves the same result.

------

  1. Other Features: a. As discussed, there are certain aspects requiring custom development work as they are not native functions of the system, such as: i. Implementing user permissions to prevent field editing once they become cases. ii. Creating specific dialer features. iii. Unlocking certain fields and organizing them in the user interface.
  2. Furthermore, we suggested three different workflow options to mitigate internal user issues: a. Restricting intake user permissions to view only leads assigned to them, ensuring that only the current assignee can edit lead information. Milestones and statuses would be used to manage tasks within this workflow. i. The feedback on this was due to wanting multiple users to have visibility to a lead if a lead is unassigned since there is not official admin in charge of lead disbursement. b. Creating a dedicated portal for cases, where qualified leads are sent for further processing, allowing for seamless data transfer and management. i. The feedback we received on this was that you did not want to have 2 separate systems to manage and were worried about the additional lead ID's c. Implementing separate cases to maintain departmental separation, utilizing user permissions to control visibility of specific case types for each user. i. The feed back we received on this was you were concerned about being unable to pull reports in a designated case type.
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-24 12:55:05

Title: Ben Crump SEO Date: Wed Apr 24 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting involved *Korbin Mantel* and *Ryan Vaspra* discussing* SEO strategies. They analyzed keyword data, backlinks, on-page grades, and used Moz tools for SEO efforts, aiming to improve search rankings. *Ryan highlighted areas for improving organic search visibility, emphasizing high-intent keywords for better conversion rates rather than broad content.

• They delved into user behavior patterns during purchase cycles to optimize content strategy, focusing on website traffic and click-through rates. Discussing *Ben Crump's legal topics, they identified potential keyword opportunities to capitalize on relevant search queries. They planned to leverage Moz tools for strategic content creation, monitoring website performance closely. The meeting revolved around targeted SEO tactics, competitive analysis, and data-driven content optimizations to enhance online visibility for Ben Crump*'s legal services.

Action Items • *Ryan Vaspra*

• Implement SEO efforts for Corbin (06:03)

• Look for competitors' social profiles and note if they post about wrongful death, have Julie help with this (08:26)

• List competitors and add them to Moz to track with Morgan (09:22)

• Analyze keyword opportunities and consider adding articles around those with great click-through rates and low difficulty (19:18)

• *Korbin Mantel*

• Review the article page that can potentially get more traffic (16:36)

Outline Chapter 1: SEO Analysis Findings (04:16 - 10:03)

• 04:26: Ryan discusses a decrease in brand name visitors and click-through rate for Trump's Q1 performance.

• 05:26: Further details on SEO efforts, including improving backlink profile and internal link optimization.

• 07:07: Suggestions for backlink strategies and internal link profiles to enhance website performance.

Chapter 2: Competitor Analysis and Strategy (10:16 - 13:15)

• 10:16: Discussion on dropping keyword impressions and the need to compete with other firms.

• 11:56: Emphasis on attracting higher-intent traffic and the importance of conversions.

• 12:45: Qualifying website traffic for better conversion rates and focusing on converting keywords.

Chapter 3: Keyword Opportunities and Content Strategy (17:53 - 20:46)

• 17:53: Identifying potential keyword opportunities for content creation and SEO benefits.

• 19:13: Highlighting ranking highlights and keyword opportunities for content creation.

• 20:03: Emphasizing the importance of optimizing content and ensuring no 404 errors on the website.

Shorthand Bullet • 📊 *SEO Analysis and Recommendations*

• - *Ryan Vaspra* discussed a drop in visitor numbers and click-through rates for a specific brand.

• - Utilize Moz and other tools for SEO efforts.

• - Focus on on-page grade, backlink profile, internal link profile, and image optimization.

• - Consider competitor analysis for social profiles and backlinks.

• 🔍 *Keyword Opportunities and Strategy*

• - Identified two keyword opportunities for potential benefits.

• - Emphasized targeting keywords with high click-through rates and low difficulty.

• - Highlighted the importance of featured snippets and ranking on page one for specific keywords.

• 🚕 *Rideshare SEO Strategy*

• - *Korbin Mantel* mentioned optimizing for terms like 'Lyft' within the rideshare category.

• - Considered targeting both Uber and Lyft keywords effectively.

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-24 12:55:05

• SEO strategy meeting discussing keyword analysis, backlinks, and content optimization for Ben Crump's legal services. Emphasis on high-intent keywords and user behavior patterns. Leveraging Moz tools for SEO efforts.

Bullet Gist • ⚙️ SEO Strategy Analysis: Focused on keyword data, backlinks, and content optimization.

• 🔍 Targeted Keywords: Emphasized high-intent keywords for better conversion rates.

• 📊 User Behavior Patterns: Analyzed purchase cycle behaviors for content optimization.

• 🌐 Website Performance: Monitored website traffic and click-through rates closely.

Short Summary • In a strategic SEO meeting, Korbin Mantel and Ryan Vaspra focused on analyzing keyword data, backlinks, and on-page grades using Moz tools to enhance search rankings for Ben Crump's legal services. They aimed to improve organic search visibility by targeting high-intent keywords for better conversion rates. The discussion delved into user behavior patterns during purchase cycles to optimize content strategy, with a focus on website traffic and click-through rates. The meeting emphasized the importance of data-driven content optimizations, competitive analysis, and strategic SEO tactics to boost online visibility and capitalize on keyword opportunities for Ben Crump.

Ryan (ryan@themedialab.agency)
2024-04-24 12:55:29

.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-24 13:32:50

Title: Law Ruler prep Date: Wed Apr 24 2024 14:15:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • *Ryan Vaspra* and *Mike Everhart* discussed the book "Life Scripts," emphasizing handling communication situations across personal and professional aspects. They noted the book's editions and the importance of content like flowcharts for effective strategies. Ryan shared a negotiation tactic to ensure all parties are satisfied, emphasizing playing specific roles when needed. He outlined key points regarding pricing and features for an upcoming call with Nick.

• The conversation shifted to Nick's background as a data scientist and developer within their team dynamics. Ryan praised Nick's skills while acknowledging areas for growth towards higher leadership roles. Mike expressed readiness to leverage his development experience if needed during negotiations. Both strategized on approaching discussions around API features pricing with mutual respect between business needs.

• The meeting focused on preparing for an important negotiation call involving strategic communication styles and technical expertise to achieve favorable outcomes professionally. Ryan emphasized effective role-playing and addressing key points during negotiations. Nick's background as a data scientist and developer was discussed, with acknowledgment of his skills and potential for higher leadership roles. Mike's willingness to contribute his development experience during negotiations was highlighted, emphasizing respect for business needs in discussions.

• Overall, Ryan and Mike strategized on negotiation tactics for the upcoming call, focusing on professionalism and respect throughout interactions. They aimed to achieve favorable outcomes by leveraging their communication styles and technical expertise. The discussions included key points on pricing, features, and the importance of mutual respect in business negotiations, highlighting the value of effective strategies and leveraging team dynamics.

Action Items • *Ryan Vaspra*

• Post notes for the call (04:27)

• Add one bullet point at the bottom, which is webhook portal release/beta (07:01)

• *Mike Everhart*

• Play good cop during the call (09:15)

• Prepare to lean on 20 plus years of development experience if needed during the call (14:03)

Outline Chapter 1: Book Recommendation - "Life Scripts" (01:59 - 03:36)

• 01:59: Ryan recommends the book "Life Scripts" by Steven Pollan and Mark Levine.

• 02:18: The book is described to have useful flowcharts for handling communication in various situations.

• 03:15: Discussion on the book's edition and pricing for the Kindle version.

Chapter 2: Preparing for a Business Call (04:21 - 07:52)

• 04:21: Ryan shares notes and preparations for an upcoming call with Nick.

• 05:11: Detailed discussion of strategies and bullet points for the call's agenda.

• 07:18: Mention of the good cop-bad cop strategy for the call dynamics.

Chapter 3: Call Strategy and Negotiation (09:12 - 12:18)

• 09:12: Discussion on the approach of negotiation during the call with Nick.

• 10:12: Emphasis on the importance of features and API integration in the negotiation process.

• 12:18: Planning to address concerns about pricing and integration difficulties during the call.

Chapter 4: Role of Nick in the Negotiation (12:26 - 14:03)

• 12:26: Ryan provides insights on Nick's background and role in the negotiation.

• 13:44: Nick's expertise in data science and development is highlighted for the call's context.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-24 13:32:50

• 14:03: Discussion on the collaborative relationship with Nick and his role in the team.

Chapter 5: Leveraging Experience in the Call (14:18 - 16:17)

• 14:18: Mike mentions his extensive development experience for potential input during the call.

• 15:22: Importance of respectfully requesting adjustments in the project scope and cost.

• 16:17: Acknowledgment of the need for effective communication to avoid misunderstandings post-call.

Shorthand Bullet • 📚 *Discussing the Book "Life Scripts"*

• - *Ryan Vaspra* recommends the book "Life Scripts" for handling various communication situations.

• - The book contains flowcharts and strategies for personal and professional interactions.

• 📑 *Preparation for Call with Nick*

• - *Ryan Vaspra* provides notes for the upcoming call with *Nick*.

• - Discussion on approaching the call with a good cop/bad cop strategy.

• 💰 *Negotiating Pricing and Features*

• - *Ryan Vaspra* emphasizes the need to negotiate prices and features effectively.

• - Mention of potential discounts and scope of work adjustments for client satisfaction.

• :male_technologist: *Understanding Nick's Role*

• - *Nick* is described as a data scientist with development skills.

• - *Mike Everhart* considers leveraging his 20+ years of development experience during the call.

• 🤝 *Maintaining Respectful Communication*

• - The team aims to negotiate respectfully with the client.

• - Emphasis on clear timelines, milestones, and mutual understanding in the project scope.

Gist • Discussion on negotiation tactics and communication strategies for an upcoming call, emphasizing professionalism and leveraging team dynamics. 🤝

Bullet Gist • ⚙️ Negotiation Strategies: Emphasized professionalism and leveraging team dynamics.

• 📚 Book 'Life Scripts': Highlighted importance of flowcharts for effective strategies.

• 💼 Role-playing Tactics: Discussed negotiation tactics for ensuring satisfaction among all parties.

• :male_technologist: Nick's Potential: Acknowledged Nick's skills and growth potential for leadership roles.

• 🤝 Mutual Respect: Focused on respect for business needs and effective strategies.

Short Summary • Ryan Vaspra and Mike Everhart discussed strategies for handling communication situations in personal and professional contexts, focusing on the book 'Life Scripts' and the importance of flowcharts for effective strategies. They highlighted negotiation tactics, including role-playing, to ensure satisfaction among all parties during discussions with Nick, a data scientist and developer. The meeting centered on preparing for a negotiation call, emphasizing professionalism, respect, and leveraging their communication styles and technical expertise to achieve favorable outcomes. Key points included pricing, features, mutual respect in negotiations, and Nick's potential for higher leadership roles.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-26 15:49:52

Title: Meeting with TIP - Ryan Date: Fri Apr 26 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: branden.brooks@lawruler.com, jordon.espinoza@lawruler.com, ryan@brandlytics.io, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Meeting Summary:*

• *Ryan Vaspra* and *Branden Brooks* had a challenging meeting due to technical issues, focusing on user restrictions for changing statuses in their system. Ryan highlighted the importance of restricting specific agents from altering billable statuses without proper authorization. They discussed detailed business cases related to lead statuses and revenue processes, considering implementing lockable statuses accessible only by admins or managers.

• The conversation expanded to user permissions for post-retainer services and case reviews. Discussions touched on advanced API features, potential solutions to prioritize key functionalities, and aligning Salesforce configurations with future enhancements. Branden emphasized tracking abilities within Law Ruler's activity log. They aimed to streamline workflows through automation, focusing on critical fields like contact IDs for better coordination across departments.

• The meeting centered on system enhancements, including a suggestion by *Cameron* about the acquisition of Law Ruler. Topics covered Salesforce consultant meetings, user permissions, and process reviews. Technical discussions involved setting up user permissions based on roles, improving interface layouts, and resolving bugs related to status management and lead handling. Branden expressed intentions to propose sub-roles with individualized permissions for enhanced functionality, planning both short-term solutions and long-term enhancements.

• Both parties agreed on follow-ups regarding proposed changes and upcoming deliverables. They aimed to optimize the system's capabilities by enhancing user visibility and focusing on structured improvements in team structures and processes. The plan includes discussions on further customizations to empower users with enhanced functionalities tailored to their specific roles and responsibilities.

Action Items • *Branden Brooks*

• Implement the internal workflow automation for changing statuses using buttons (46:02)

• Investigate adding contact id as a field in the interface inbox to help solve interdepartmental challenges (54:15)

• Take information back to the team and appreciate the insight (1:00:36)

• Make a suggestion to development team to clean up page layout in Copper CRM (1;05;03)

• Pitch idea of creating individual permissions set by role and sub roles internally, focus on short-term solutions first while aiming for system expansion in long term (1:06:01)

• *Ryan Vaspra*

• Reach out to Tony first to ensure clear understanding of how the automated steps through process will work (49:00)

• Discuss with Brittany setting up Salesforce for post-retainer services and its potential impact on law ruler operations (57:20)

• Look for the statement of work update next week (1:07:37)

• Demo automating statuses and creating a second instance for training purposes (1:08:04)

• Share the steps for intake status (1:09:47)

• Resolve bug with Dnu status not deleting by using filters in inbox settings (1:12:45)

Outline Chapter 1: Understanding User Restrictions (00:00 - 05:31)

• 00:00: Purpose of the call clarified regarding user restrictions for status changes.

• 04:30: Discussion on user-specific needs for changing status.

Chapter 2: Workflow Process and Data Management (09:06 - 20:10)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-26 15:49:52

• 09:06: Mention of structuring light user stories for different users.

• 11:28: Describing workflow stages from deal processing to QA checks.

• 14:01: Reference to Brittany Barnett for process insights.

• 20:01: Utilizing a spreadsheet as a guide for data warehouse processes.

Chapter 3: System Automation and Flow Chart Overview (20:59 - 29:20)

• 20:59: Importance of case review questions in the process.

• 23:32: Explaining flagged statuses on spreadsheets.

• 28:41: Email automation and Slack alerts integration highlighted.

• 29:20: Monitoring financials through automated processes.

Chapter 4: User Roles and Process Teams (30:30 - 39:19)

• 30:30: Clarification on status selection for different user roles.

• 32:07: Structuring the workflow from left to right.

• 35:17: Discussion on commission and flat transactions.

• 39:08: Finalization process through processing and review teams.

Chapter 5: Advanced API Integration (53:16 - 55:23)

• 53:16: Focus on accessing key fields through advanced API.

• 55:10: Internal report usage for specific data visualization.

Chapter 6: Team Collaboration and Training (58:18 - 1:08:28)

• 58:18: Inquiring about group sizes for task assignment.

• 1:00:47: Discussing the scope of work with the CEO.

• 1:06:12: Training suggestions for team members' role definitions.

• 1:08:28: Considerations for creating a training instance for process automation.

Chapter 7: Process Optimization and Milestones (1:08:59 - 1:15:59)

• 1:08:59: Focus on optimizing available resources for immediate goals.

• 1:11:01: Streamlining statuses and removing redundant ones.

• 1:12:45: Organizing views for efficient workflow management.

• 1:15:50: Milestones planning for project deliverables.

Shorthand Bullet • 📊 *User Restrictions for Status Changes*

• - *Clarify specific user needs for status change restrictions*

• - Discuss the role of different users like *lead assignee and intake staff manager*

• - Ensure understanding of the *workflow for status changes*

• 🔧 *Automation for Status Changes*

• - Explore using a dedicated section for *internal workflow automation*

• - Consider a *button-based system* for status changes instead of traditional methods

• - Highlight the importance of *automation in the process*

• 🛠️ *Visibility and Access Control*

• - Focus on determining *visibility permissions for different users*

• - Discuss exposing key fields in *report templates* for better user experience

• - Emphasize the need to make clients and team members *happy with the system*

• 📈 *API Integration and Contact ID*

• - Discuss *exposing contact ID* through the API

• - Highlight the importance of understanding *API capabilities* for the team

• - Consider creating a *training instance* for the team to practice automation

• 🔍 *Workflow Optimization*

• - Request steps for setting up *intake statuses*

• - Organize views in the kanban structure for better *workflow management*

• - Implement *milestones for deliverables* to track progress efficiently

Gist • Meeting highlighted user restrictions, system enhancements, and workflow automation. Emphasis on permissions, Salesforce alignment, and future enhancements. 🔒💼🔧

Bullet Gist • 🔒 User Restrictions: Highlighted the importance of restricting specific agents from altering billable statuses without proper authorization.

• 💼 System Enhancements: Discussed implementing lockable statuses, advanced API features, and aligning Salesforce configurations with future enhancements.

• 🔧 Workflow Automation: Focused on streamlining workflows through automation, improving critical fields like contact IDs for better coordination.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-26 15:49:52

• The meeting delved into the importance of user restrictions for changing statuses, focusing on billable statuses and lead statuses. Discussions revolved around implementing lockable statuses, advanced API features, and aligning Salesforce with future enhancements. Attention was given to user permissions, tracking abilities, and workflow automation, aiming to streamline processes and enhance functionality through system enhancements and proposed changes, focusing on structured improvements in team structures and processes.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 11:16:15

Title: BLX Media Buying Date: Mon Apr 29 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, lee@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* and *Lee* Zafra* discussed attending a festival spontaneously after *Ryan overlooked ticket purchase. They spoke about post-festival plans, such as watching NBA games. Their conversation shifted to work matters, focusing on lead generation strategies and client feedback. Lee detailed budget adjustments to enhance lead acquisition, with Ryan emphasizing the need for consistent spending to yield effective outcomes.

• Ryan raised concerns about leads from LSA not meeting criteria like auto accident cases. He intended to consult with Cameron about modifying strategies to improve lead quality and campaign performance. The discussion turned to upcoming tasks concerning client projects, emphasizing the timely update of crucial data for future talks on progress and outcomes. The meeting concluded with a focus on ensuring data readiness for future project discussions.

Action Items • *Lee Zafra*

• Make sure to get the lead counts all in there today, Corbin (10:08)

• Ensure to pace out for next week's wrap-up of focus litigation solutions (10:24)

• *Ryan Vaspra*

• Ping Cameron about running LSA for auto only and potentially building a Ben Crump Google Maps Google Ads campaign (09:13)

Outline Chapter 1: Weekend Recaps and Lead Generation Strategy (00:04 - 05:09)

• - Weekend activities discussed, including attending a festival and concert.

• - Review of lead generation strategy and budget adjustments for increased leads.

Chapter 2: Evaluation of Campaign Performance (05:22 - 07:36)

• - Analysis of lead generation campaigns and adjustments made to optimize results.

• - Discussion on the importance of pacing and cost per lead metrics.

Chapter 3: Client Feedback and Future Campaign Plans (08:00 - 09:56)

• - Concerns raised about lead quality and campaign performance for specific types of cases.

• - Proposal to focus on auto-related leads and potential Google Ads campaign strategies.

Chapter 4: Project Management and Timeline Review (10:02 - 10:31)

• - Review of upcoming projects and deadlines.

• - Reminder to update lead counts and prepare for future meetings.

Shorthand Bullet • 📊 *Lead Generation Performance*

• - *Lee* adjusted the budget resulting in an increase in leads to around 10 per day.

• - *Ryan* emphasized the importance of pacing at the new budget level.

• - Focus on generating leads for auto-related cases discussed.

• 🔄 *Client Follow-Up*

• - *Adrian* emailed the client to assess the impact of 20 new leads generated.

• - *Ryan* awaiting feedback from the client on lead quality and qualification criteria.

• 🔎 *Campaign Strategy Review*

• - Consideration of running LSA for auto cases only.

• - Proposal to create a Google Ads campaign for Ben Crump.

• - Discussion on feedback and KPIs with *Cameron* pending.

• 🗓️ *Project Timeline*

• - Wrapping up of Focus Litigation Solutions and preparation for the next project.

• - Lead counts to be finalized for discussion in the upcoming meeting with *Corbin*.

Gist • Discussion on spontaneous festival attendance, lead generation strategies, and client feedback with a focus on data readiness for future projects.

Bullet Gist • ⚡ Spontaneous Festival Attendance: Ryan and Lee discussed attending a festival on the spur of the moment.

• 💼 Lead Generation Strategies: Lee detailed budget adjustments to enhance lead acquisition.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 11:16:15

• 📊 Client Feedback: Ryan emphasized consistent spending for effective outcomes.

• ⚠️ Lead Quality Concerns: Ryan raised concerns about leads not meeting criteria.

• 🔍 Consulting on Strategies: Ryan planned to consult with Cameron for strategy modifications.

Short Summary • Ryan Vaspra and Lee Zafra discussed attending a festival spontaneously, post-festival plans, lead generation strategies, and client feedback. Lee detailed budget adjustments for lead acquisition while Ryan emphasized the need for consistent spending. Ryan raised concerns about lead quality and intended to consult on modifying strategies for better outcomes. The meeting concluded with a focus on data readiness for upcoming project discussions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 14:06:53

Title: Tech Project Status Weekly Date: Mon Apr 29 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting commenced with *James Scott, Ryan Vaspra, Mike Everhart, and Brian Hirst discussing schedule adjustments and project progress. Mike* presented advancements in a CRM app for Facebook ads, focusing on functionalities similar to TikTok.

• *James* delved into analyzing legal documents on drug names in PDF files, while *Ryan* proposed exploring competitor technologies for potential system enhancements. They planned espionage tactics to understand competitors' features for application development.

• *Brian* and *Ryan* addressed challenges in integrating intake criteria into law firm orders, particularly regarding firefighting foam contracts. The team emphasized improving data analytics tools to align with market trends and customer demands.

• Lastly, *Ryan* stressed the importance of effective questioning in legal processes and highlighted the significance of data management with machine learning tools. They discussed leveraging first-party data sources for predictive modeling and exploring e-discovery algorithms based on historical case data analysis for enhanced legal intelligence services.

Action Items • *James Scott*

• Continue searching for specific text within PDF documents (45:09)

• Determine the most efficient way to extract information from 15,000 documents (41:58)

• *Ryan Vaspra*

• Set up a session with the legal team to review extreme cases of PDF files and understand them better (42:28)

• Have all partner law firms send updates to a specific email for data collection (53:45)

• Research on tech companies starting tomorrow and share findings via emails (1:02:01)

Outline Chapter 1: Database Construct and Cross Reference Table (04:04 - 09:12)

• - Ryan discusses building a DBT construct to extract data and create a cross reference table.

• - James acknowledges the work in progress.

Chapter 2: Data Management and Status Tracking (21:26 - 26:53)

• - Ryan explains the process of using automations to manage status lifecycles.

• - Discussion on implementing billable status edit access and real-time lead dashboard reporting.

Chapter 3: Text Extraction from PDF Documents (35:09 - 46:39)

• - James describes searching for specific text within multiple PDF documents.

• - Challenges in efficiently extracting information and understanding the process.

Chapter 4: AI Implementation and Data Extraction (33:50 - 57:01)

• - Ryan mentions a new AI prompt for medical cases and positive client feedback.

• - James works on searching for drug names in PDF documents for predictive modeling.

• - Discussion on the importance of avoiding manual input of medical terms and building integration MVP for an app.

Chapter 5: Competitive Research and Roadmap Building (48:28 - 1:02:06)

• - Ryan emphasizes the importance of researching competition and building software roadmaps.

• - Discussion on evolving roadmaps, building a vision, and exploring software capabilities.

• - Focus on e-discovery algorithms, marketing predictions, and case status analysis for software development.

Shorthand Bullet • 📊 *Client Integration and Support*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 14:06:53

• - *Ryan Vaspra* to build DBT construct for cross-reference table

• - *James Scott* sharing screen for demonstration

• - DBT integration progress discussed

• 🚒 *Firefighting Phone*

• - *Ryan Vaspra* working on firefighting phone project

• - Plans to create a report builder with law ruler API integration

• 🔍 *Document Analysis*

• - *James Scott* analyzing documents for specific words

• - Fuzzy matching used for word search

• - Counting occurrences of words in documents

• 📈 *Product Research*

• - *Ryan Vaspra* conducting research on legal tech players

• - Aim to explore new technologies for potential adoption

• 📑 *Data Extraction*

• - *Ryan Vaspra* discussing efficient data extraction methods

• - Mention of machine learning and AI for data analysis

• 📧 *Email Data* Analysis**

• - *Ryan Vaspra* exploring email and PDF analysis for communication patterns

• - Looking for inconsistencies in linear communications

• 🔍 *Search Functionality*

• - *James Scott* developing search functionality for word translation

• - Targeting easy translation of searched words

• 📅 *Future Plans*

• - *Ryan Vaspra* to continue research and share updates with the team

• - Encouraging team members to reach out with any issues or challenges

Gist • Team discusses project progress, CRM app features, legal document analysis, competitor technologies, data analytics tools, and machine learning for legal processes.

Bullet Gist • ⏰ Project Progress: Discussion on schedule adjustments and project advancements.

• 📱 CRM App Features: Mike presented a CRM app with TikTok-like functionalities.

• 🔍 Competitor Technologies: Ryan proposed exploring competitor technologies for system enhancements.

• 📊 Data Analytics Tools: Emphasis on improving data analytics tools to align with market trends.

• 💡 Machine Learning in Legal Processes: Discussion on leveraging machine learning and first-party data for legal intelligence services.

Short Summary • The team, consisting of James Scott, Ryan Vaspra, Mike Everhart, and Brian Hirst, engaged in a productive meeting covering a range of topics. Mike presented updates on a CRM app with TikTok-like functionalities, James focused on analyzing legal documents, Ryan proposed exploring competitor technologies, and espionage tactics to understand competitors better. Brian and Ryan addressed challenges with integrating intake criteria in law firm orders, emphasizing data analytics tool improvements. Ryan emphasized effective questioning in legal processes, data management with machine learning, leveraging first-party data for predictive modeling, and exploring e-discovery algorithms for enhanced legal intelligence services.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 16:35:35

Title: Shield <> Sonobi Weekly Date: Mon Apr 29 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@themedialab.agency, cameron@shield-legal.com, cschwarz@sonobi.com, swilcox@sonobi.com, kristopher@shield-legal.com, tony@tortintakeprofessionals.com, ryan@brandlytics.io, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Craig Schwarz* held a meeting with *Kristopher Standley, Cameron Rentch, and Ryan Vaspra* to discuss lead generation metrics, reviewing campaign performance in LA County and Maryland. The team analyzed daily spend, lead quality, and conversions, emphasizing the need for improved targeting strategies. Challenges with lead quality versus spend efficiency were noted, with a focus on driving calls over digital efforts.

• Efforts went into streamlining reporting and enhancing access to call center data for better monitoring and analysis. *Ryan Vaspra set up a Slack channel for efficient communication among team members involved in lead tracking. Craig* expressed interest in accessing raw call recordings directly for deeper insights. The meeting aimed to refine lead generation strategies through data-driven decision-making, optimize campaign performance by balancing budget distribution, enhance visibility into conversion metrics, and streamline access to vital data sources within the organization's systems.

• The discussion touched upon adjusting budget allocation across the week based on historical data, aiming for higher volume during peak days while ensuring cost-effectiveness. The team highlighted the importance of driving calls for improved results and identified the necessity for better targeting strategies. Overall, the meeting focused on refining lead generation strategies through data-driven decision-making, optimizing campaign performance by balancing budget distribution throughout the week, enhancing visibility into conversion metrics, and streamlining access to essential data sources.*Craig's interest* in raw call recordings for deeper insights was also noted.

• In summary, *Craig Schwarz led a meeting with Kristopher Standley, Cameron Rentch, and Ryan Vaspra* to analyze lead generation metrics, focusing on campaign performance in different regions. They identified challenges with lead quality and spending efficiency, discussed the prioritization of driving calls over digital methods, and endeavored to streamline reporting processes and enhance access to call center data. The meeting emphasized data-driven decision-making to refine lead generation strategies and optimize campaign performance through balanced budget distribution, improved visibility into conversion metrics, and streamlined access to essential data sources.

Action Items • *Cameron Rentch*

• Clean up reporting (20:25)

• Focus on driving calls rather than digital efforts (11:42)

• Help set up a user in the sub-account for Craig to access call recordings (20:54)

• *Ryan Vaspra*

• Set up a loop with Craig to have access to Tony and someone in intake for call recordings (20:30)

• Add Steve Wilcox and Carl to the slack channel for communication (21:16)

• *Craig Schwarz*

• Cut Friday spend a bit and focus more on Monday through Wednesday spending initially, then taper off towards Thursday and Friday (18:38)

• Analyze tier two performance in Maryland and increase volume there if needed (19:44)

Outline Chapter 1: Reporting and Performance Analysis (01:19 - 05:01)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 16:35:35

• 01:19: *Craig discusses sending daily campaign numbers to Chris* for accuracy in budget allocation.

• 03:19: *Ryan* mentions the need for more detailed reporting on lead performance.

• 05:01: *Craig* highlights the importance of audience targeting adjustments made after the previous week's call.

Chapter 2: Campaign Optimization and Budgeting (05:51 - 08:15)

• 05:51: *Cameron* emphasizes the need for a breakdown of spending and lead acquisition by campaign.

• 08:15: *Kristopher* suggests front-loading the budget earlier in the week for optimal results.

• 08:35: *Cameron and Craig* plan to adjust spending patterns to maximize campaign efficiency.

Chapter 3: Lead Conversion and Follow-Up (13:40 - 16:39)

• 13:40: *Craig* addresses the need for a bigger week and plans to enhance lead conversion rates.

• 14:56: *Kristopher and Craig* discuss strategies to increase campaign performance based on past successes.

• 15:58: *Kristopher* emphasizes the importance of tracking lead sources for better targeting.

Chapter 4: Data Analysis and Call Center Integration (20:26 - 25:44)

• 20:26: *Cameron* proposes streamlining reporting processes for improved data analysis.

• 22:56: *Ryan* suggests creating a dedicated channel for call center communication and data sharing.

• 25:10: *Craig* acknowledges the value of detailed spreadsheets showing raw leads and call recordings for quality control.

Chapter 5: Action Plans and Implementation (26:20 - 27:42)

• 26:20: *Craig* seeks clarification on how to utilize the data provided in spreadsheets for decision-making.

• 27:04: *Craig and Ryan* discuss accessing call recordings for further insights into lead interactions.

• 27:22: *Ryan prompts Chris* to review campaign strategies and implement necessary adjustments.

Shorthand Bullet • 📊 *Weekly/Daily Numbers Reporting*

• - *Craig Schwarz* mentioned sending weekly or daily numbers by campaign to *Chris* to prevent errors in fund allocation.

• - *Detailed dashboard* displays lead IDs and campaign performance.

• 💰 *Budget and Lead Monitoring*

• - *Craig Schwarz* emphasized the importance of monitoring spending and tracking total leads per campaign.

• - *Need for driving calls* and understanding campaign performance.

• 📞 *Call Center* Operations**

• - *Ryan Vaspra* discussed call center operations, including recording calls and providing assistance.

• - *Accessing spreadsheets* to review raw leads and audio recordings linked within.

• 📈 *Optimizing Campaign Strategy*

• - *Focus on earlier week spending* and granular analysis of campaigns to drive results.

• - *Monitoring unique leads* and optimizing ad spend throughout the week.

• 📧 *Communication and Collaboration*

• - *Setting up external organization* for collaboration and sharing information.

• - *Direct access to call recordings* discussed for better monitoring and quality control.

Gist • Team meeting led by Craig Schwarz discussed lead generation metrics, campaign performance, and targeting strategies with a focus on driving calls. Efforts were made to streamline reporting and enhance access to call center data.

Bullet Gist • ⚙️ Lead Generation Analysis: Discussion on campaign performance and targeting strategies.

• 📊 Data-Driven Decisions: Emphasis on driving calls and optimizing campaign performance.

• 📞 Efficient Communication: Setup of a Slack channel for better team communication.

• 🔍 Insightful Monitoring: Interest in accessing raw call recordings for deeper insights.

• 💡 Streamlined Processes: Efforts to enhance reporting and call center data access.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-29 16:35:35

• Craig Schwarz convened a meeting with Kristopher Standley, Cameron Rentch, and Ryan Vaspra to delve into lead generation metrics, campaign performance in LA County and Maryland, and targeting strategies. They highlighted challenges with lead quality and spending efficiency, emphasized driving calls, and focused on data-driven decision-making. The team aimed to optimize campaign performance through balanced budget distribution, improve visibility into conversion metrics, and streamline access to essential data sources. Craig expressed interest in raw call recordings for deeper insights, while efforts were made to enhance communication and monitoring through a Slack channel and improved data access.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-30 14:23:30

Title: SL Database Maintenance Date: Tue Apr 30 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, luke@brandlytics.io, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In a detailed technical meeting between *Luke Fontaine and Ryan Vaspra, troubleshooting DBT models in BigQuery was the focal point. Ryan* faced challenges with partition fields leading to errors during compilation, spurring extensive debugging efforts. They discussed employing unique partition keys for incremental updates, emphasizing selecting specific columns for data filtering during incremental runs. Ryan emphasized meticulous testing to ensure quality output and highlighted the need for thorough verification before committing changes.

• During the meeting, a focus on optimizing queries emerged. *Ryan* demonstrated testing practices for quality assurance. They delved into adjusting configuration parameters such as materialization options and partitioning strategies based on date fields. The discussion revolved around efficiently reverting changes when needed to identify root causes of unexpected errors. Collaborative problem-solving and code revisions were employed to address discrepancies in SQL queries affecting DBT model execution in BigQuery.

• Despite encountering setbacks like unexpected errors, *Ryan*'s methodical approach involved precise testing and iterative improvements. The meeting showcased a deep dive into data modeling intricacies within technical complexities of streamlined processes for database management tasks. Emphasis was placed on dedication to delivering high-quality solutions through precision testing, collaborative problem-solving, and iterative enhancements. The commitment to resolving discrepancies and optimizing queries underscored their dedication to achieving efficient and effective outcomes in data management.

Action Items • *Ryan Vaspra*

• Fix the issue with partitioning field for date (1:05:46)

• Test DBT build command on the model to check for errors and fix them (1:08:00)

• Investigate the error "Expected a close but got aware" during compilation and resolve it (1:10:25)

• Let me know if you need any more assistance or details!

Outline Chapter 1: Data Management Strategy (00:18 - 14:56)

• 00:40: Discussion on managing real-time data processes efficiently.

• 07:02: Decision to implement a 24-hour delay for billable leads table processing.

• 08:45: Importance of differentiating between real-time and delayed data for financial reporting.

Chapter 2: Financial Data Integration (16:08 - 26:14)

• 16:10: Plan to set up a GCP BigQuery Python notebook for updating financial details.

• 25:06: Scheduling the notebook to run every five minutes for data updates.

Chapter 3: Reporting and Dashboard Development (27:18 - 35:56)

• 27:40: Creating pivot tables for outcome reports and data analysis.

• 31:08: Discussion on building financial dashboards for reporting and analysis.

Chapter 4: Database Management and Query Optimization (41:30 - 52:17)

• 41:37: Reviewing table structures for effective data management.

• 47:10: Explanation of incremental data updates in BigQuery.

• 50:54: Importance of compiling SQL queries for accurate data processing.

Shorthand Bullet • 📊 *Managing Real-time Data*

• - *Ryan Vaspra* discussed managing real-time data for various purposes, including financials.

• - Mentioned updating financial details in a GCP BigQuery Python notebook.

• - Emphasized the importance of differentiating between shield legal billables and real-time billboards.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-04-30 14:23:30

• 📉 *Financial Dashboard Development*

• - *Ryan Vaspra* and *Luke Fontaine* planned to work on a financial dashboard.

• - Discussed creating a view for running SQL to update revenue.

• - Addressed the need to break out end-of-month expenses for specific business allocations.

• 🔍 *Data Analysis and Reporting*

• - Talked about setting up reports for analyzing outcomes and call duration.

• - Discussed the process of grouping data by date created and company ID.

• - Mentioned the importance of validating work lead campaigns and cost per intakes.

• 🔧 *Technical Implementation*

• - *Ryan Vaspra* provided technical guidance on schema details and data formatting.

• - Discussed syncing databases, committing changes, and fixing SQL for BigQuery tables.

• - Addressed the need for incremental table testing and maintaining data integrity.

Gist • Troubleshooting DBT models in BigQuery with a focus on optimizing queries and meticulous testing for quality assurance. Collaborative problem-solving and iterative improvements highlighted.

Bullet Gist • ⚙️ Troubleshooting DBT Models: Challenges with partition fields and unique keys for incremental updates.

• ⭐ Optimizing Queries: Adjusting parameters and reverting changes for efficiency.

• ⚖️ Quality Assurance: Meticulous testing practices and collaborative problem-solving.

• 🔍 Iterative Improvements: Continuous enhancements and code revisions to address discrepancies.

Short Summary • The discussion between Luke Fontaine and Ryan Vaspra centered on troubleshooting DBT models in BigQuery, emphasizing challenges with partition fields and the need for unique partition keys for incremental updates. They also focused on optimizing queries by adjusting configuration parameters and reverting changes when necessary. Testing practices, collaborative problem-solving, and iterative enhancements were key themes, showcasing a commitment to delivering high-quality solutions in data management.

Ryan (ryan@themedialab.agency)
2024-04-30 19:58:07

Update BLX Platforms:

Google Ads Google LSA Ads 4197460051477330 05/28 777 Brandlytics Media Card

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-02 13:03:19

Title: Ben Crump SEO Date: Thu May 02 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting began with a focus on mapping case types to web pages and organizing data tables. *Ryan Vaspra* discussed cloning auto accident pages for slip and fall injuries. Emphasizing clear communication, concerns were raised about potential system glitches and workflow changes. Discussions expanded to implementing a tier-one dialer like Conex One for lead management efficiency, touching on webhook synchronization and lead routing strategies.

• Moving forward, attention was given to creating article-style pages about hurricanes and storm damages, targeting disaster-prone regions like Florida. The strategic planning involved aligning website content with emerging case types to enhance organic search results. Additionally, insurance coverage details related to perils like wind damage were discussed. Collaboration between *Ryan Vaspra, Korbin* Mantel**, and the team focused on optimizing the website structure for legal services delivery while addressing technical challenges associated with lead management systems integration.

Action Items • *Ryan Vaspra*

• - Request new one cloning auto accident page (05:05)

• - Confirm with Adrian and Desiree John to clone auto torticity (08:05)

• - Seek Latoya and tip team confirmation for piping personal injury into trunk accidents (10:00)

• - Request more article FAQ style pages for hurricanes and storms focusing on Florida, Dallas, Orlando, Texas areas (25:24)

Outline Chapter 1: Mapping Case Types and Data Normalization (00:03 - 05:04)

• 00:03: Discussion on mapping case types to vertical law ruler and the need for data normalization.

• 01:55: Decision to include a questionnaire for specific cases requiring a questionnaire.

• 04:05: Consideration of separating intake questionnaire and template.

Chapter 2: Tracking and Reporting Implementation (08:48 - 14:11)

• 09:12: Emphasis on the need for tracking numbers and sources for data completeness.

• 10:23: Introduction of CTM receiving number and discussion on tracking accidents.

• 12:00: Final steps of tracking implementation and importance of checkbox completion.

Chapter 3: Communication and System Integration (16:16 - 18:21)

• 16:16: Plans to discuss system workings with relevant team members for clarity.

• 17:36: Consideration for improved tracking of campaigns and billable statuses.

Chapter 4: Content Strategy and Focus Areas (23:40 - 26:48)

• 24:19: Focus on generating more article-style pages for specific case types.

• 25:48: Request to increase organic content for hurricane and storm-related cases.

Chapter 5: Task Delegation and Progress Updates (27:26 - 28:35)

• 27:44: Delegation of tasks for page updates and publishing readiness.

• 28:00: Overview of lead delivery process and the importance of tracking measures.

Shorthand Bullet • 📊 *Mapping Case Types to Verticals*

• - Ryan highlighted the mapping process of case types to verticals for auto accident pages.

• - Mentioned the importance of normalizing data into a table format.

• - Emphasized the need for mapping case types to verticals for consistency.

• 📑 *Intake Questionnaire*

• - Discussed the need for a specific questionnaire for personal injury cases.

• - Addressed the importance of having a questionnaire tailored to specific case requirements.

• 🚀 *Tracking and Lead Generation*

• - Mentioned the completion of French gear tracking.

• - Highlighted the process of tracking and lead generation for efficient workflow.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-02 13:03:19

• 📞 *Communication and Collaboration*

• - Ryan planned to confirm details with Adrian, Desiree, John, Tony, Brett, and Adam.

• - Mentioned the need to strategize with the team for effective implementation and communication.

• 📈 *Content Development*

• - Emphasized the need for more article and FAQ-style pages for hurricane and storm cases.

• - Assigned Korbin the task of increasing the volume of content for specific case types.

• 🔍 *Monitoring and Updates*

• - Discussed the role of Corbin in updating yellow cells and informing about page updates and publishing readiness.

• - Highlighted the importance of monitoring and updating content for lead delivery and Dialer efficiency.

Gist • Discussion on website optimization for legal services, lead management efficiency, and content creation for disaster-prone regions. Emphasis on case types mapping and communication.

Bullet Gist • ⚙️ Website Optimization: Focus on mapping case types to web pages and enhancing website structure.

• ⚠️ Lead Management Efficiency: Discussions on implementing a tier-one dialer for efficient lead management.

• 🔗 Content Creation: Creation of article-style pages for disaster-prone regions like Florida.

• 🌪️ Strategic Planning: Aligning website content with emerging case types for improved search results.

• 🤝 Collaboration: Team effort to address technical challenges and optimize website structure.

Short Summary • The meeting revolved around optimizing the website structure for legal services delivery, focusing on mapping case types to web pages, lead management efficiency, and content creation for disaster-prone regions like Florida. Ryan Vaspra discussed cloning auto accident pages for slip and fall injuries, while concerns were raised about potential system glitches and workflow changes. Strategies for lead management efficiency with a tier-one dialer like Conex One were explored, including discussions on webhook synchronization and lead routing. Collaboration between Ryan Vaspra, Korbin Mantel, and the team aimed at addressing technical challenges associated with integrating lead management systems and aligning website content with emerging case types to improve organic search results.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-02 14:20:46

Title: Meeting with Branden Brooks Date: Thu May 02 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: branden.brooks@lawruler.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Meeting Summary:*

• *Branden Brooks* and *Ryan Vaspra* discussed enhancing the lead workflow by segmenting tasks based on specific statuses for accuracy and accountability. They considered a feature request to lock leads at certain statuses for data security. Plans were made for post-implementation training and budget allocations for additional features.

• The meeting involved *Branden Brooks, Ryan Vaspra, and Jordon Espinoza* discussing API parts for their MVP project. They confirmed new items in scope and updated milestones. Branden demonstrated milestone updates and discussed post-retainer processes. The team finalized bundling API parts into the project scope, ensuring a timeline for implementation.

• Throughout their dialogue, emphasis was placed on aligning technology solutions with business needs in system integration. Discussions highlighted operational workflow optimization focusing on API integration tasks. The team collaboratively clarified timelines and progress updates for the project scope, expressing mutual appreciation for contributions towards achieving goals effectively.

• The discussion touched on reversible locks and access permissions, aligning with team preferences. Considerations for gradual rollout strategies and budgetary allocations were emphasized. The team showcased a strategic approach towards user adoption challenges and scalability concerns, aligning tasks related to API integration and making progress updates between *Branden and Ryan*.

Action Items • *Branden Brooks*

• - Update scope for the contact id (45:02)

• - Forward Fireflies to Branden (45:44)

• - Show how to update milestones (45:54)

Outline Chapter 1: Lead Workflow Enhancement Discussion (00:25 - 07:58)

• 00:31: Objectives for the call: Lead workflow enhancements and finalizing the advanced API scope of work.

• 02:10: Discussion on adding elements to the lead workflow, focusing on form completion and status grouping by department.

Chapter 2: Form Structure and Team Alignment (08:05 - 14:15)

• 09:13: Clarification on building multiple forms for different case types and the importance of aligning with team structures.

• 12:00: Aligning on the concept of second interviews and review processes within the workflow.

Chapter 3: Milestones and Task Triggers (26:22 - 33:01)

• 26:36: Defining milestones for the lead creation process and specific actions/tasks required at each step.

• 32:13: Task triggers based on lead status changes, ensuring completion confirmation and visibility in the workflow.

Chapter 4: Scope of Work and Deliverables (36:22 - 42:15)

• 37:44: Overview of critical path MVP items, including advanced API permissions and contact ID exposure.

• 39:23: Addition of lead customization training and new feature requests within the project scope.

• 42:15: Discussion on budget allocation and prioritization of essential project features.

Chapter 5: Feedback and Milestone Updates (45:54)

• 45:54: Conclusion with feedback incorporation and demonstration of milestone updates during the meeting.

Shorthand Bullet • 🚀 *Lead Workflow*

• - Branden outlined three main objectives for the call: lead workflow, finalizing details for the advanced API scope, and seeking additional input.

• - Discussion on structuring the lead workflow, focusing on form completion and grouping statuses by department.

• - *Emphasis on creating clear milestones and tasks within the workflow*.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-02 14:20:47

• 🔒 *Locking Leads*

• - The importance of locking leads at specific statuses was discussed, aiming to achieve clarity and control over the process.

• - *Implementation of roles and groups for specific users to manage lead progression* effectively.

• 📊 *Milestones and Tasks*

• - Detailed discussion on milestones and tasks required at each step of the workflow.

• - *Ryan suggested adding a milestone column for clearer tracking* of tasks and progress.

• 📧 *Communication and Updates*

• - Method discussed for internal communication and updating milestones during the workflow.

• - *Clarification on the necessity of triggering tasks based on lead status changes*.

• 📝 *Scope of Work and Deliverables*

• - Discussion on the scope of work, including API permissions, contact ID exposure, and custom report functions.

• - Mention of a business meeting to strategize the rollout plan with the team.

• 🔧 *Feature Requests*

• - Incorporation of new feature requests within the existing scope of work.

• - *Focus on simplicity and maximizing benefits for all users* of the law ruler system.

• 🔄 *Update Process*

• - Branden demonstrated updating milestones in real-time during the call.

• - *Efficient handling of lead cloning and updates discussed* for streamlined workflow management.

Gist • Discussion on enhancing lead workflow, API parts for MVP project, and aligning technology with business needs. Focus on task segmentation, data security, API integration, and user adoption strategies.

Bullet Gist • ⚙️ Enhancing Lead Workflow: Segmenting tasks for accuracy and accountability.

• 🔒 Data Security Consideration: Feature request to lock leads at certain statuses.

• 🔄 API Integration Focus: Discussion on API parts for MVP project.

• 📈 Business Alignment: Emphasizing technology solutions aligned with business needs.

• 💼 Budget Allocations: Plans for budget allocations for additional features.

Short Summary • The meeting involved Branden Brooks, Ryan Vaspra, and Jordon Espinoza discussing enhancing lead workflow by segmenting tasks based on specific statuses for accuracy and accountability. They also discussed API parts for their MVP project, confirmed new items in scope, and emphasized aligning technology solutions with business needs. The team focused on post-implementation training, budget allocations for additional features, API integration tasks, user adoption challenges, and scalability concerns.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-02 14:46:02

Title: BCL Next Steps Date: Thu May 02 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Adrienne Hester* expressed gratitude for *Uzoma Obasi's* assistance during a challenging day, focusing on scheduling conflicts and personnel availability, mentioning John's presence during the week of the 13th. Plans were made regarding website updates to emphasize appointments and improve online visibility through SEO strategies. The discussion then shifted to ongoing projects related to Drax air pollution, retainer agreements, press releases, and social media efforts. *Ryan Vaspra* outlined an SEO strategy involving various case types like hurricane damages and slip-and-fall accidents, planning to optimize web forms for better lead management.

• They addressed technical concerns about call tracking metrics post-implementation changes, with Ryan clarifying how marketing tools functioned within their workflow and highlighting the potential for SMS marketing integration using Connex one platform. Personal matters concerning weather conditions in different locations and future travel plans were briefly discussed between *Uzoma Obasi* and *Adrienne Hester*. They concluded the meeting with a focus on maintaining communication channels open via Slack for any additional questions or updates required moving forward.

Action Items • *Uzoma Obasi*

• Put appointment only on the website (07:31)

• Coordinate with Desiree about Connex one trial access (13:25)

• Consider SMS blast for missed calls (14:18)

• Decide on potential visit to Vegas and discuss moving plans with Amir (16:03)

• *Ryan Vaspra*

• Ensure appointment only is added to location pages, office pages, attorney pages, and offices footer (08:48)

• Work on SEO campaigns related to hurricane damages, truck accidents, slip and falls (09:30)

• Implement new forms on the website for specific case types intake by the tip team (10:19)

Outline Chapter 1: Meeting Overview and Scheduling (02:33 - 07:20)

• - 02:33: Discussion about upcoming meetings and schedules for the week.

• - 04:43: Planning for meetings to be held during the week of the 13th.

• - 05:40: Coordination for John and team's visit during the week of the 13th.

• - 07:20: Mention of issues with unscheduled office visits by individuals seeking immediate attorney meetings.

Chapter 2: Marketing and SEO Strategies (07:58 - 10:56)

• - 07:58: Discussion on implementing "by appointment only" notices for office visits.

• - 08:13: Recommendations on incorporating appointment details on various pages for visibility.

• - 10:02: Plan to streamline website forms for better lead management and tracking.

Chapter 3: Call Tracking and Marketing Analytics (11:38 - 14:53)

• - 11:38: Exploring call tracking metrics for monitoring incoming calls and form submissions.

• - 12:06: Explanation of the role of call tracking metrics in marketing analytics.

• - 14:09: Potential use of call tracking metrics for SMS communication and customer engagement.

Chapter 4: Project Updates and Future Plans (15:44 - 17:33)

• - 15:44: Brief discussion on current project status and upcoming tasks.

• - 16:06: Playful suggestion to create content or updates for future engagements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-02 14:46:02

• - 17:26: Closing remarks and encouragement to reach out for further discussions.

Shorthand Bullet • 📅 *Meeting Schedule*

• - *Week of the 13th:*

• - *Attendees:* John, Precious, and others

• - *Discussion of upcoming meetings*

• 📰 *Press Release*

• - *Scheduled for the week of the 13th*

• 🔒 *Appointment System*

• - Implement "by appointment only" policy

• - Locations, office pages, and attorney pages to be updated

• - Use Google My Business for appointment setting

• 📊 *SEO Strategy*

• - Focus on specific case types like slip and falls

• - Create FAQ pages tailored to local areas in Florida

• 📞 *Call Tracking Metrics*

• - Utilize for lead capture and form submissions

• - Consider SMS blast capability for customer engagement

• - Enhance communication with missed call notifications

• 📝 *Action Items*

• - Update forms on the website for better lead filtering

• - Communicate any updates or issues via Slack

• 👋 *Conclusion*

• - Meeting adjourned with thanks and goodbyes

Gist • Gratitude expressed for assistance during challenges, website updates planned, ongoing projects discussed, SEO strategy outlined, technical concerns addressed, and future travel plans briefly mentioned.

Bullet Gist • 🙏 Gratitude Expressed: For assistance during challenges.

• 🌐 Website Updates Planned: To emphasize appointments and improve online visibility.

• ⚙️ Ongoing Projects Discussed: Related to Drax air pollution, retainer agreements, press releases, and social media efforts.

• 💻 SEO Strategy Outlined: Involving various case types like hurricane damages and slip-and-fall accidents.

• ⚠️ Technical Concerns Addressed: Regarding call tracking metrics and SMS marketing integration.

Short Summary • The meeting involved expressions of gratitude for assistance during challenges, plans for website updates to emphasize appointments and improve online visibility through SEO strategies. Discussions encompassed ongoing projects related to Drax air pollution, retainer agreements, press releases, and social media efforts. An SEO strategy was outlined involving various case types like hurricane damages and slip-and-fall accidents. Technical concerns about call tracking metrics post-implementation changes were addressed, with a focus on SMS marketing integration. Personal matters regarding weather conditions and future travel plans were briefly discussed. The meeting concluded with an emphasis on maintaining communication channels open via Slack for any additional questions or updates required moving forward.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 12:04:35

Title: Sonobi | Shield log level data ingestion Date: Fri May 03 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, swilcox@sonobi.com, kristopher@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Steve Wilcox* and *Ryan Vaspra* discussed optimizing campaign strategies using log-level data, emphasizing the need for efficient insights extraction. They explored integrating data into a campaign optimization layer, focusing on metrics like leads and publisher performance for refining campaigns. The idea of centralizing data in Looker for comprehensive analysis and team transparency was proposed. Ryan shared experience from Goldman Sachs on the effectiveness of log-level data analysis in attribution reports.

• Technical aspects were delved into, such as connecting Google Sheets or Amazon Redshift to streamline data processing. Practical steps like creating path-to-conversion reports and using IP addresses for deeper analysis were discussed. Starting with a spreadsheet format to gradually kickstart the process before complex integrations was suggested. They agreed to value simple yet impactful initiatives based on detailed log-level analyses. The focus was on practical solutions for enhancing campaign performance without unnecessary complexity.

Action Items • *Steve Wilcox*

• Format log level data columns in the path to conversion format (25:11)

• Send a spreadsheet of log level data for analysis (25:52)

• Check into cloud storage as an option for data sharing (30:02)

Outline Chapter 1: Overview of Campaign Optimization Strategy (00:21 - 06:54)

• 00:21: Introduction to the concept of campaign optimization using log level data.

• 02:14: Explanation of leveraging log level data for optimization and refinement.

• 04:27: Proposal to create a comprehensive report for insights and transparency.

Chapter 2: Integration of Call Tracking Metrics (05:56 - 07:11)

• 05:56: Discussion on utilizing call tracking metrics for lead management.

• 06:30: Challenge in integrating call tracking metrics with log level data.

Chapter 3: Campaign Manager's Attribution Report (08:00 - 10:07)

• 08:00: Highlighting the significance of the campaign manager's attribution report.

• 09:47: Proposal to analyze log level data for channel interactions and conversions.

Chapter 4: Generating Path to Conversion Report (10:33 - 14:05)

• 10:33: Explanation of generating a path to conversion report.

• 12:19: Suggestion to format the path to conversion report in a Google sheet.

Chapter 5: Data Analysis and Custom Queries (17:18 - 19:25)

• 17:18: Discussion on custom queries for data analysis.

• 19:25: Implementation of data parsing for effective analysis and insights.

Chapter 6: Collaboration and Data Sharing (25:15 - 27:56)

• 25:15: Proposal to share log level data for collaborative analysis.

• 27:56: Utilizing channels for data sharing and collaborative analysis.

Shorthand Bullet • 📊 *Analyzing Log Level Data*

• - *Steve Wilcox* discussed leveraging log level data to analyze leads and conversions by day and time.

• - Emphasized the importance of optimizing, testing, and refining based on insights from log level data.

• - *Ryan Vaspra* highlighted the significance of call tracking metrics and data enhancement features for lead management.

• 📈 *Generating Detailed Reports*

• - Mentioned the value of a comprehensive report, like the Looker report, displaying leads, conversions, and channel interactions.

• - Suggested creating a path to conversion report format for deeper analysis.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 12:04:35

• - Discussed the need for a Google sheet to organize log level data for report generation.

• 🔍 *Data Formatting and Collaboration*

• - Shared insights on formatting log level data columns in a Google sheet for collaborative analysis.

• - Discussed sharing data through channels like Slack for further collaboration and analysis.

• - Discussed the importance of clear nomenclature and data organization for effective analysis.

Gist • Discussion on optimizing campaign strategies using log-level data for efficient insights extraction and practical solutions for enhancing campaign performance without unnecessary complexity. 📊🔍

Bullet Gist • ⚙️ Optimizing Campaign Strategies: Using log-level data for efficient insights extraction.

• 📈 Integration of Data: Into campaign optimization layer with focus on leads and publisher performance.

• 🔍 Centralizing Data: In Looker for comprehensive analysis and team transparency.

• 💡 Technical Aspects Explored: Connecting Google Sheets or Amazon Redshift for streamlined data processing.

• 📊 Practical Steps: Creating path-to-conversion reports and using IP addresses for deeper analysis.

Short Summary • Steve Wilcox and Ryan Vaspra discussed the optimization of campaign strategies using log-level data, emphasizing the need for efficient insights extraction. They explored integrating data into a campaign optimization layer, focusing on metrics like leads and publisher performance for refining campaigns. The idea of centralizing data in Looker for comprehensive analysis and team transparency was proposed. Ryan shared his experience from Goldman Sachs on the effectiveness of log-level data analysis in attribution reports. Technical aspects were discussed, such as connecting Google Sheets or Amazon Redshift to streamline data processing. Practical steps like creating path-to-conversion reports and using IP addresses for deeper analysis were also explored. They suggested starting with a spreadsheet format before complex integrations and agreed to value simple yet impactful initiatives based on detailed log-level analyses, focusing on practical solutions for enhancing campaign performance without unnecessary complexity.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 12:22:43

Title: BLX EOM Media Spend & Budget Tracking Billing Meeting Date: Fri May 03 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, lee@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* discussed budget overages in various campaigns, stressing the importance of cost control and avoiding unnecessary expenditures by adhering to clear directives. He highlighted instances where budgets were exceeded, leading to negative margins, emphasizing campaign performance metrics like form leads, CPL, and market costs.

• Addressing concerns about campaign pausing due to overspending, *Ryan Vaspra* emphasized accurate invoicing based on lead generation activities. He detailed backfilling leads for investor transparency and correct cost allocation at month-end while resolving discrepancies in call center costs and clarifying date entries for financial accuracy.

• Providing updates on LSA ads expenditure in April, *Ryan Vaspra* sought guidance from colleagues like Cameron for strategic spending decisions. Mentioning missing contact information, follow-up actions were needed for verification processes. The meeting concluded with reminders to monitor expenses closely to avoid overages and maintain financial stability.

• The meeting underscored prudent budget management practices within marketing campaigns for optimal outcomes and mitigating financial risks from exceeding allocated funds. By focusing on budget control, performance metrics tracking, and communication among team members like Adrian and Cameron, *Ryan Vaspra* aimed at streamlining operations for improved efficiency.

Action Items • *Ryan Vaspra*

• Pause the campaign and say Dayton at Adrian (04:41)

• Check if Elena wants to add any further budget (07:01)

Outline Chapter 1: Campaign Budget Management (00:04 - 05:19)

• - Discussion on overspending and the importance of not exceeding the budget.

• - Decision to pause the campaign due to overspending in the Sue City, Iowa group campaign.

• - Analysis of budget spent, overages, and form leads data.

Chapter 2: Investor Communication and Call Center Costs (11:56 - 13:55)

• - Explanation of the process of selling leads to an investor and the need for accurate cost reporting.

• - Clarification on call center costs and addressing discrepancies with the investor.

• - Update on fixing date issues related to lead reporting for accuracy.

Chapter 3: LSA Ads and Budget Allocation (15:00 - 16:57)

• - Recap of the significant budget spent on BCL Texas LSA ads in April.

• - Plan to seek guidance on the $70,000 spent for LSA ads from Cameron.

• - Reminder to monitor spending and avoid going over budget in future campaigns.

Shorthand Bullet • 📊 *Litigation Solutions*

• - *Paused campaign due to overspending in *Sue City, Iowa group campaign.

• - Budget overspend of $519, resulting in negative margin.

• - Campaign originally had a budget of $1500.

• - Requested additional budget from Elena to cover overspend.

• - Campaign had a high CPL of $44 due to the expensive rural market.**

• 💸 *Financial Updates*

• - **Investor call regarding high call center costs due to lead volume miscalculation.

• - Adjusting records to reflect accurate costs.

• - Explained cost discrepancies to investor.**

• 🔒 *Campaign Management*

• - **Emphasized the importance of not overspending without prior approval.

• - Mentioned the need for strict adherence to budget constraints.

• - Monitored spending closely to avoid further overages.**

• 📧 *Communication and Coordination*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 12:22:43

• - *Requested specific email address from *Adrian (possibly for LSA verification).

• - Sought guidance from Cameron on $70,000 spent on BCL Texas LSA ads in April.**

• 🔍 *Data Analysis*

• - *Reviewed campaign spending for *April, focusing on LSA ads.

• - Missing DeWitt's email address for LSA verification.

• - Seeking clarification on specific spends for further analysis.**

Gist • Meeting notes highlight budget management, performance metrics, and team communication for marketing campaigns.

• 📊💰🔍

Bullet Gist • 📊 Budget Management: Focus on avoiding overages and adhering to clear directives.

• 💰 Cost Control: Emphasize accurate invoicing and backfilling leads for transparency.

• 🔍 Performance Metrics: Track form leads, CPL, and market costs for campaign performance.

Short Summary • The meeting notes focus on *Ryan Vaspra discussing budget overages, emphasizing cost control and clear directives to avoid unnecessary expenditures. He highlighted instances of exceeding budgets, impacting margins, and emphasized performance metrics like form leads, CPL, and market costs. Ryan Vaspra* addressed concerns about pausing campaigns due to overspending by emphasizing accurate invoicing, backfilling leads for transparency, and resolving discrepancies in call center costs. Updates on LSA ads expenditure in April were provided, seeking guidance from colleagues for strategic spending decisions. The meeting concluded with reminders to monitor expenses closely to maintain financial stability, emphasizing prudent budget management practices and efficient team communication.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 13:22:45

Title: Connex One update Date: Fri May 03 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: tony@tortintakeprofessionals.com, brettmichael@tortintakeprofessionals.com, ryan@brandlytics.io, cameron@shield-legal.com, nicholas@tortintakeprofessionals.com, nickmcfadden@shield-legal.com, darrell@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting involved *Nicholas Ward and Ryan Vaspra discussing dialer solutions, focusing on integrating ringcentral five nine with other systems. Ryan expressed concerns about the current setup's efficiency and proposed changes to optimize workflows. Nicholas* shared frustrations regarding Conex one's implementation impact on operations and reporting capabilities, suggesting exploring Dialpad or Matterbox for Salesforce integration for a more suitable solution.

• They discussed advanced API development in Law Ruler for improved case management functionality, including features like status groups, automation controls, and permission sets. The conversation also touched on leveraging Snowflake postgres access provided by Conex one for enhanced reporting capabilities. *Ryan* emphasized the importance of complete access to database tables for generating comprehensive reports efficiently, considering future software integrations' compatibility requirements.

• Plans were made to engage further with Law Ruler for API implementation guidance and training sessions, focusing on smooth adoption of new features. The goal is to align vendor choices with long-term business goals to maintain data pipelines and operational continuity without disruptions. The meeting aims to address challenges faced due to system integrations not being optimal and enhance workflow efficiency within processes.

• The discussion is geared towards improving operations through potential changes and exploring optimized solutions. They are considering various options to address ongoing issues with the current setup, aiming for a long-term and sustainable solution. Efforts are focused on ensuring efficient data management, workflow optimization, and improved reporting capabilities while preparing for future software integrations and aligning choices with business objectives.

Action Items • *Nicholas Ward*

• Set up a little time with Brandon early next week (16:10)

• Wrap up with RingCentral today to ensure CSP gets set up to replace Becker's or Bailey Blaster system (08:17)

• Chat with Dialpad today to see if their cloud solution is better (08:32)

• *Ryan Vaspra*

• Call Nicholas, Nick, Tony, and Brett together once the API is ready for law ruler discussion (16:23)

• Track milestones with law ruler team over five weeks for API development cycle (16:33)

Outline Chapter 1: Technical Requirements and Dialer Timing (00:00 - 05:52)

• - Discussion on technical requirements for lead management systems such as Leadspedia and law ruler.

• - Focus on the timing of dialer operations and ensuring quick lead response.

Chapter 2: Law Ruler Integration and API Development (08:08 - 14:55)

• - Issues with current reporting tools and consideration of alternative solutions like Dialpad.

• - Planning for Law Ruler integration and development of an advanced API for contact ID exposure.

Chapter 3: Case Management and Workflow Improvements (10:20 - 16:08)

• - Progress on case management and e-signature integration within Law Ruler.

• - Enhancements in workflow efficiency and milestone tracking for agents.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 13:22:45

Chapter 4: Training and System Configuration (15:36 - 17:26)

• - Preparation for demos and training sessions with Law Ruler team.

• - Coordination for system configuration and timeline for implementation.

Chapter 5: Reporting and Revenue Analysis (17:26 - 18:42)

• - Consideration of building custom reports for detailed outcome analysis.

• - Importance of revenue reporting and cost integration for effective decision-making.

Shorthand Bullet • 📊 *Technical Integration*

• - *Nicholas Ward* to handle technical requirements as the point person.

• - Integration process discussed involving daisy chain, shield, and form leads.

• - Process flow outlined from form submission to lead distribution.

• 🚀 *Automation and Workflow Enhancement*

• - *Law Ruler* automation for new lead notifications.

• - Integration of *Zapier* for seamless lead transfer.

• - Emphasis on real-time data processing and automation for efficiency.

• 📞 *Dialer System Evaluation*

• - Considering a switch to a potentially better cloud solution like *Dialpad*.

• - Requirement for a database for unified reporting and metrics.

• - Future planning for a possible dialer transition.

• 📝 *Law Ruler System Development*

• - Advanced API development for contact ID exposure.

• - Custom permission set creation for non-admin management.

• - Training plan for staff on the new system configuration.

• 🔒 *Status Management* and Workflow Control**

• - Introduction of status groups and terminal status locking.

• - Implementation of milestone tracking for workflow visualization.

• - Focus on admin-exclusive access to critical status changes.

• 🔄 *Development Cycle and Milestone Tracking*

• - Five-week development cycle planned for law ruler enhancements.

• - Milestone tracking to ensure timely delivery.

• - Consideration for potential future software transitions.

Gist • Meeting involved discussions on optimizing dialer solutions, API development for improved case management, and enhancing reporting capabilities. Efforts focused on aligning vendor choices with long-term business goals for efficient operations.

Bullet Gist • ⚙️ Optimizing Dialer Solutions: Discussions on improving efficiency and exploring integrations with RingCentral Five Nine.

• ⚖️ API Development for Law Ruler: Focused on advanced features like status groups, automation controls, and permission sets.

• 📊 Enhancing Reporting Capabilities: Utilizing Snowflake postgres access for comprehensive reporting and database table access for future software integrations.

• 🔄 Aligning Vendor Choices with Business Goals: Planning to ensure vendor selections align with long-term business objectives for operational continuity.

Short Summary • The meeting centered around Nicholas Ward and Ryan Vaspra discussing the optimization of dialer solutions, proposed changes to enhance workflows, frustrations with current system implementations, and exploring solutions like Dialpad and Matterbox for Salesforce integration. They also delved into advanced API development for Law Ruler, leveraging Snowflake postgres access for better reporting, and planning API implementation guidance with Law Ruler for improved operations and software integrations alignment with business goals.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 13:42:36

Title: BCL LSA Date: Fri May 03 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io, cameron@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting *involved *Ryan Vaspra discussing* tasks and deadlines, emphasizing prompt action. *He organized* tasks related to spreadsheets, phone numbers, and case reviews for *Cameron by 1:30 PM. Ryan** instructed on managing data in a detailed spreadsheet, resolving issues efficiently, ensuring accurate data collection, and handling lead disputes diligently within specific systems like LSA dashboard. The importance of maintaining data integrity for effective decision-making was highlighted throughout.

• *Ryan focused* on maximizing lead generation outcomes through meticulous handling of case reviews and email transfers, consistent follow-up on retained leads, and optimizing results from ongoing efforts amidst operational constraints. The meeting *revolved around aligning actions* with efficient task completion and outcome evaluation during *Cameron's* review at 1:30 PM. Commitment to thorough data management, dispute resolution strategies, and lead retention tactics were emphasized as key elements in driving successful outcomes within specified parameters.

Action Items • *Ryan Vaspra*

• Download, open the spreadsheet and check for phone numbers in the raw data tab (03:32)

• Dispute any leads without matching phone numbers in LSA dashboard (04:31)

• Start disputing leads to resolve by 130, aim for 50 to 100 disputes done by then (04:39)

Outline Chapter 1: Urgency and Scheduling Concerns (00:00 - 01:51)

• 00:00: Ryan expresses frustration over changing timelines.

• 00:31: Discussion about rescheduling and prioritizing tasks for the afternoon.

Chapter 2: Data Management and Review Process (01:51 - 04:46)

• 01:51: Reviewing and sending spreadsheets, ensuring data accuracy.

• 02:46: Instructions for data review process and dispute resolution.

Chapter 3: Case Reviews and Lead Management (04:46 - 05:17)

• 04:46: Importance of case reviews for future outcomes.

• 05:17: Decision to hold off on certain actions pending further review.

Chapter 4: Lead Generation Strategies and Outcome Evaluation (05:17 - 06:17)

• 05:17: Discussion on lead generation success rates.

• 06:17: Sending leads for further processing and evaluation.

Chapter 5: Communication and Reporting (06:17 - 07:58)

• 06:17: Sending leads for external intake and review.

• 07:21: Request for updating and highlighting retained leads.

Chapter 6: Task Management and Technical Issues (07:58 - 08:55)

• 07:58: Ensuring accurate data transfer and avoiding errors.

• 08:43: Technical issues with cut and paste functionality.

Chapter 7: Meeting Coordination and Final Remarks (08:55 - End)

• 08:55: Confirmation of next steps and meeting schedule.

Shorthand Bullet • 📊 *Meeting Rescheduling*

• - Ryan Vaspra rescheduled the meeting to 1:30 PM.

• 📑 *Data Management*

• - Ryan instructed Cameron to review and dispute leads missing phone numbers in the raw data spreadsheet.

• - *Urged prompt action on disputing leads to resolve the issue by 1:30 PM.*

• 📅 *Case Reviews Importance*

• - Emphasized the critical need for cases resulting from the 84 reviews sent to Cameron.

• - Decision to wait for Cameron's input before proceeding further.

• 📧 *Lead Transfer*

• - Ryan sent leads to BCL external intake for further processing.

• - Requested updates on retained leads from April 2024 Texas sales.

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 13:42:36

• Ryan Vaspra led a meeting focusing on data management, lead generation, and task alignment for effective outcomes. Emphasis on data integrity, lead retention, and efficient task completion.

Bullet Gist • ⚙️ Task Organization: Tasks related to spreadsheets, phone numbers, and case reviews were organized for Cameron.

• ⏰ Deadline Emphasis: Emphasis on prompt action and efficient task completion by 1:30 PM.

• 📊 Data Management: Detailed spreadsheet management, accurate data collection, and efficient issue resolution highlighted.

• 🔍 Lead Generation: Focus on maximizing outcomes through case reviews, email transfers, and lead retention strategies.

• ⚖️ Decision-Making: Importance of data integrity for effective decision-making reiterated throughout.

Short Summary • Ryan Vaspra organized a meeting to discuss tasks and deadlines, instructing on managing data in detailed spreadsheets, resolving issues efficiently, and handling lead disputes within specific systems. The meeting emphasized data integrity for decision-making, maximizing lead generation outcomes through meticulous handling of case reviews and email transfers, and aligning actions for efficient task completion. Commitment to data management, dispute resolution strategies, and lead retention tactics were highlighted as key elements for success within specified parameters.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 15:37:33

Title: BCL LSA Date: Fri May 03 2024 16:30:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io, cameron@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Lee Zafra* menciona tener un total de 15 clientes potenciales para el autobús y destaca ocho que no se incluyeron en la revisión de incentivos del caso de torticidad uno. Durante la reunión, *Ryan Vaspra señala que todos están presentes, excepto Lee* Zafra*, quien llega más tarde después de ver a *Cameron. La discusión se centra en revisar números e identificar discrepancias en los procesos de gestión de clientes potenciales, especialmente en relación con los del autobús. *Lee* Zafra** toma la iniciativa de acceder a herramientas de abogado inteligentes mientras espera más información sobre los clientes potenciales perdidos. A pesar de no ser un experto, está familiarizado con cómo navegar por ellas y avanzar hacia la resolución de problemas identificados durante la reunión.

• La conversación concluye con un compromiso de ambas partes, donde *Lee* Zafra* acepta hablar a *las 2:15 PM, según lo mencionado por *Ryan Vaspra*, lo que indica una colaboración continua y comunicación entre los miembros del equipo con respecto a las estrategias de gestión de clientes potenciales.

Action Items • *Lee Zafra*

• Find out what's up (05:35)

• Go see if I can get into their smart advocate (06:16)

• *Ryan Vaspra*

• Talk then (08:57)

Outline Chapter 1: Initial Lead Analysis (02:08 - 05:39)

• 02:08: Lee Zafra highlights the need to review the leads and mentions potential missed entries.

• 04:47: Lee Zafra identifies 15 auto leads not included in the previous review.

• 05:39: Ryan Vaspra agrees to investigate further.

Chapter 2: Reviewing Unprocessed Leads (05:39 - 06:27)

• 05:39: Lee Zafra plans to investigate the eight auto leads that were not processed.

• 06:21: Lee Zafra attempts to access the smart advocate system for more information.

Chapter 3: Progress Update and Action Plan (06:27 - 09:00)

• 06:27: Lee Zafra discusses accessing the smart advocate and potential next steps.

• 08:59: Ryan Vaspra agrees to further discussion at 2:15 PM.

• Please note that the timestamps are approximate and provide a general overview of the main points discussed in the transcript.

Shorthand Bullet • 📊 *Lead Review*

• - Lee identified a total of 15 leads that were auto-generated.

• - *Eight of these leads were not put into the Torticity incentives case review.*

• - Lee is tasked with finding out the status of these eight leads.

• 🔍 *Smart Advocate Access*

• - Lee plans to access Smart Advocate with his login to investigate further.

• 🕑 *Follow-up Call*

• - Ryan and Lee plan to talk at 2:15 regarding the leads.

Gist • Meeting discusses client management issues, Lee Zafra has 15 potential clients, 8 not included in incentives review. Focus on discrepancies in client management processes, Zafra explores smart lawyer tools. Commitment to ongoing collaboration highlighted by Vaspra and Zafra's meeting schedule.

Bullet Gist • ⚖️ Client Management Challenges: Lee Zafra has 15 potential clients, 8 not in incentives review.

• 🔍 Discrepancies in Processes: Focus on identifying disparities in client management, specifically with bus clients.

• ⏰ Utilizing Smart Tools: Zafra accesses smart lawyer tools to address issues during the meeting.

• 🤝 Commitment to Collaboration: Vaspra and Zafra schedule a meeting, emphasizing ongoing teamwork.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 15:37:34

• The meeting delves into client management challenges, revealing that Lee Zafra has 15 potential clients, with 8 distinct from the incentives review. Emphasis is placed on identifying disparities in client management procedures, particularly related to the bus clients. Zafra takes the lead in utilizing smart lawyer tools to address issues. The commitment to continued teamwork is evident as Ryan Vaspra and Lee Zafra agree on a 2:15 PM discussion, showcasing ongoing communication and collaboration regarding client management strategies.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 16:43:36

Title: BCL LSA Date: Fri May 03 2024 17:15:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io, cameron@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting involved *Lee Zafra, Ryan Vaspra, and Cameron Rentch* discussing the LSA campaign's performance, focusing on auto accident leads in Texas. Ryan shared insights on lead generation strategies and specific campaign adjustments. Cameron expressed concern over budget allocation and emphasized targeting auto accidents. Ryan updated on case reviews, emphasizing evaluations of campaign effectiveness.

• They deliberated on enhancing lead quality in a specific legal niche and acknowledged challenges with Google Ads. Decisions were made to pause current activities, reassess strategies, and potentially explore other platforms. The aim is to optimize lead acquisition efficiently through a targeted strategy mainly on auto accident cases in Texas, ensuring cost-effective resource utilization. Plans were set to regroup for further strategic discussions based on revised approaches.

Action Items • *Ryan Vaspra*

• Turn on only auto accidents on Monday (10:33)

• Regroup and look at different strategies for MVA spending (14:29)

• Consider Google Maps mobile click-to-call ads as the main strategy (13:38)

• *Cameron Rentch*

• Untangle the current situation and regroup with a new plan (17:06)

• Determine how to make LSA work effectively (20:35)

Outline Chapter 1: Initial Campaign Launch and Performance Evaluation (04:01 - 11:09)

• 04:12: Discussion on the initial campaign launch and evaluation of performance metrics.

• 06:26: First signed design final came in on Monday, the 8th.

• 09:00: Reviewing the number of leads and outcomes from Texas deals.

• 10:03: Monitoring cost per metrics in the dashboard for billable items.

Chapter 2: Reviewing Lead Generation Strategies (11:23 - 17:27)

• 11:41: Specific budget allocation discussion for the Texas project.

• 15:18: Evaluating the handling of leads by Christine Hodges.

• 17:27: Concerns about the discrepancy in the number of leads received versus Texas leads.

Chapter 3: Media Strategy Assessment and Adjustments (19:24 - 22:50)

• 19:24: Considering adjustments to the media strategy for better outcomes.

• 20:07: Reevaluation of the current media strategy effectiveness.

• 22:10: Reflecting on past experiences with media strategies to inform decision-making.

Chapter 4: Action Plan and Next Steps (23:01 - 24:38)

• 23:06: Decision to regroup on Monday for further discussion and planning.

• 23:28: Analysis of previous campaigns and planning for future adjustments.

• 24:31: Temporary pause in current actions with plans to regroup later.

• This outline highlights the key points and decisions made during the conversation, focusing on the strategic aspects of the campaign, lead generation strategies, media strategy assessment, and the action plan for moving forward.

Shorthand Bullet • 📊 *Review of Leads and Campaign Performance*

• - *Ryan Vaspra* provided an overview of the leads generated and campaign performance.

• - Mentioned launching on the fifth with zero calls initially in certain areas.

• - Noted success with auto accident leads after specific actions were taken.

• 📞 *Discussion on Billable Calls*

• - *Cameron Rentch* inquired about the billable calls and whether they were all auto accident-related.

• - Clarification provided regarding the nature of the billable calls and the strategy employed.

• 🛠️ *Media Strategy Evaluation*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-03 16:43:36

• - *Ryan Vaspra* emphasized the need to rethink the media strategy, indicating Google may not be effective.

• - Mentioned exploring alternative strategies to improve campaign performance.

• 📅 *Action Plan for Future Meetings*

• - Decision made to regroup on Monday to reassess the situation and make further plans.

• - *Cameron Rentch* and *Ryan Vaspra* agreed to pause and revisit the strategy in the next meeting.

Gist • Discussion on optimizing lead acquisition through targeted strategies for auto accident cases in Texas with a focus on cost-effective resource utilization. Decisions made to pause current activities and explore other platforms.

Bullet Gist • ⚙️ Lead Acquisition Optimization: Focused on targeted strategies for auto accident cases in Texas.

• 💰 Budget Allocation: Cameron expressed concern over efficient resource utilization.

• 🔍 Strategic Decisions: Decided to pause activities, reassess strategies, and explore other platforms.

• 🌟 Lead Quality Enhancement: Acknowledged challenges and aimed to improve lead quality in a specific legal niche.

Short Summary • The meeting involved Lee Zafra, Ryan Vaspra, and Cameron Rentch discussing strategies to enhance lead quality in auto accident cases in Texas. Ryan shared insights on lead generation strategies and campaign adjustments, while Cameron emphasized budget allocation and targeting auto accidents. They decided to pause current activities, reassess strategies, and consider other platforms to optimize lead acquisition efficiently. Plans were made to regroup for further strategic discussions based on revised approaches.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-06 13:38:46

Title: Tech Project Status Weekly Date: Mon May 06 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting, led by *Ryan Vaspra, focused on work-related discussions involving Luke Fontaine, Ryan Vaspra, James Scott, and Nick McFadden*. Topics included project updates, team assignments, and future plans like updating performance calculations and integrating smart advocate with tip reports. They also discussed handling new hires such as Shane Latimer and technical issues like API integrations for dialer systems like Ringcentral and Five9. Nick updated demo schedules and potential implementations while addressing challenges with Connex integration issues.

• Further discussions revolved around training Shane on DBT processes by reviewing recorded sessions to facilitate a smooth transition into working on automation scripts. The team also strategized regarding client projects, focusing on Ben Crump's analytics requirements in conjunction with Smart Advocate data reporting. They highlighted the need for efficient data handling practices to enhance productivity within workflow tools like Looker Enterprise. Overall, the meeting showcased a collaborative effort to tackle current tasks effectively and prepare for upcoming developments across various projects, emphasizing operational efficiency and improved productivity.

Action Items • *Ryan Vaspra*

• Get the adjustments dashboard Luke with type form form from Cameron into Looker (05:07)

• Discuss slowing down the pace of tip business intelligence development and reverting back to a couple things like finishing shield AWS database looker pages (05:13)

• Have the new Python AWS guy rewrite calculate performance for tip stuff automagically and potentially help in other tasks like writing a lambda for call center cost calculation (06:31)

• Review the Looker dashboard of drug ranking model and impact analysis with James Scott, Brian, and Luke during two sessions per week (16:58)

• *Mike Everhart*

• Research trusted form integration related to Facebook native ads for media buyers this week (15:11)

• *Nick McFadden*

• Start Shane Latimer on handing over python automation scripts for Brittany's team after he is done training today (32:47)

• Update on Connex progress regarding issues faced with fixes planned this week; inquire about statement of work status with Law Ruler integration kick-off plans discussed in next Ben Crump team meeting later this month

Outline Chapter 1: Business Intelligence Development Plan (04:24 - 07:47)

• 04:24: Discussion on prioritizing tasks related to shield AWS database and looker pages.

• 05:22: Plans to embed forms into looker and automate tip business intelligence development.

• 06:47: Proposed tasks to enhance call center cost calculations and data processing efficiency.

Chapter 2: Data Visualization Strategy (16:17 - 18:01)

• 16:17: Mention of client integration support and transitioning to enterprise-level data visualization tools.

• 17:26: Importance of research analytics, insights, and visualizations in product marketing.

• 18:01: Future plans to add more insights to the data visualization strategy.

Chapter 3: Integration and Reporting Requirements (19:38 - 21:36)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-06 13:38:46

• 19:38: Updates on Facebook CRM event codes and data collection progress.

• 20:00: Discussion on integrating shield legal and brandlytics data into smart advocate.

• 21:25: Plans to address reporting requirements and integration needs with Ben Crump team.

Chapter 4: Operational Reports and System Integration (27:31 - 30:50)

• 27:31: Mention of operational reports for paralegal and intake teams.

• 28:31: Efforts to wrap up legacy system integration and data pipelines.

• 29:42: Collaboration on system integration tasks and project prioritization discussions.

Chapter 5: Project Management and Collaboration (32:05 - 38:19)

• 32:05: Initial project planning discussions and considerations for future tasks.

• 33:37: Importance of coordinating with the development team and leveraging best practices.

• 35:18: Scheduling upcoming meetings for operational reports and training sessions.

• 38:19: Closing remarks and anticipation for future collaborations.

Shorthand Bullet • 📊 *Reorganized Sprint View*

• - *Ryan Vaspra* reorganized the sprint view to prioritize ongoing tasks.

• - *Assigned tasks*: Mike for Facebook update, Luke for tip business intelligence development.

• 🔄 *Workflow Discussions*

• - Discussion about slowing down the pace of business intelligence development.

• - Mention of reverting back to previous strategies by *Ryan Vaspra*.

• 📈 *Project Scope*

• - *James Scott* highlighted the need to quantify and present project information effectively.

• - Focus on finalizing the Looker dashboard for project insights.

• 🔍 *Data Analysis and Insights*

• - Emphasis on researching analytics, insights, and visualizations by the team.

• - *Ryan Vaspra* mentioned the importance of understanding data requirements.

• 💡 *Client Integration Strategy*

• - Discussion on integrating data from TIP to BCL sample by *Ryan Vaspra and Luke Fontaine*.

• - Mention of a potential conversation with Cameron and Andy for strategic alignment.

• 📉 *Operational Reporting*

• - Mention of operational reports and paralegal team insights by *Nick and Ryan Vaspra*.

• - Potential collaboration to create operational reports for Smart Advocate.

• 📅 *Upcoming Tasks*

• - *Nick* planning to focus on pipeline tasks after current priorities.

• - Discussion about training sessions and best practices for model development.

Gist • Meeting led by Ryan Vaspra with Luke Fontaine, James Scott, and Nick McFadden. Discussed project updates, team assignments, future plans, new hires, technical issues, training, client projects, and data handling for improved productivity.

Bullet Gist • ⚙️ Work Discussions: Focused on project updates, team assignments, and future plans.

• 👥 Team Members: Included Luke Fontaine, James Scott, and Nick McFadden.

• 📈 Future Plans: Involving updating performance calculations and integrating Smart Advocate with tip reports.

• 🔧 Technical Issues: Addressed API integrations for dialer systems like Ringcentral and Five9.

• 📚 Training and Projects: Reviewed recorded sessions to train Shane on DBT processes and strategized on client projects.

Short Summary • The meeting, led by Ryan Vaspra, focused on project updates, team assignments, future plans like updating performance calculations and integrating Smart Advocate with tip reports. Discussions included handling new hires, technical issues with API integrations, training Shane on DBT processes, strategizing on client projects like Ben Crump's analytics requirements, and emphasizing efficient data handling practices for enhanced productivity within workflow tools like Looker Enterprise. The collaborative effort aimed at tackling current tasks effectively and preparing for upcoming developments across various projects.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-06 16:33:02

Title: Shield <> Sonobi Weekly Date: Mon May 06 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@themedialab.agency, cameron@shield-legal.com, cschwarz@sonobi.com, swilcox@sonobi.com, kristopher@shield-legal.com, tony@tortintakeprofessionals.com, ryan@brandlytics.io, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting began with an analysis of the marketing campaign led by *Craig Schwarz and Cameron Rentch, supported by insights from team members Steve Wilcox and Ryan Vaspra*. Discussions revolved around spending, conversion rates, lead generation, and media strategies. Specific leads that converted, demographics, and tier categorization for targeting efficiency were examined.

• The team highlighted the importance of refining audience targeting based on age range and ethnic demographics to align with the nature of cases handled by Maryland Juvenile Hall and Los Angeles centers. Balancing reach with frequency to avoid overserving certain audiences was emphasized. Data transparency was deemed essential for informed decision-making regarding network selection optimization.

• Efforts focused on enhancing data reporting processes to gain better visibility into lead outcomes post-conversion. The goal was to streamline daily reports compiled by Jackson to reflect closed deals for accurate assessments. Suggestions were made to adjust meeting schedules to improve coordination among team members moving forward.

Action Items • *Ryan*

• Update the DQ and open lead reports for Maryland Juvenile Hall TV and LA juvenile abuse TV each morning (15:18)

• Provide details on path to conversion report (15:29)

• *Cameron Rentch*

• Run disposition reports from intake system starting tomorrow to track closed, DQ'd, and open leads daily (28:00)

Outline Chapter 1: Lead Generation Analysis (00:00 - 04:37)

• 00:44: Discussion on the slowdown of leads and the need to analyze conversion data.

• 01:29: Request for firm spend numbers to optimize lead generation strategies.

• 02:08: Reviewing media situation and adjusting frequency for better results.

Chapter 2: Data Analysis and Optimization Strategies (05:03 - 09:30)

• 05:33: Analyzing full-week adjustments based on daily performance.

• 07:55: Working on path conversion reports and improving transparency in data analysis.

• 09:25: Reviewing estimated numbers and planning for optimizing media spend.

Chapter 3: Performance Evaluation and Strategy Refinement (10:00 - 14:53)

• 10:27: Emphasizing the importance of matching impressions with timestamps for deeper insights.

• 12:39: Discussing the analysis of web, phone, and leads data to optimize strategies.

• 14:53: Implementing daily reports for tracking progress and performance evaluation.

Chapter 4: Media Channel Optimization and Targeting (15:16 - 19:41)

• 15:29: Planning to cut underperforming networks and focus on high-converting channels.

• 18:50: Prioritizing funnel optimization and targeting strategies for better results.

• 19:53: Emphasizing the need for accurate targeting based on insights and data.

Chapter 5: Team Collaboration and Action Plan (22:00 - 29:14)

• 22:17: Setting goals to cut networks, optimize tiers, and improve overall performance.

• 24:34: Urging team efforts to focus on lead generation and strategic optimization.

• 27:47: Committing to actionable takeaways and immediate implementation for better results.

Shorthand Bullet • 📊 *Sign-ups Total*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-06 16:33:03

• - *Craig Schwarz*: Mentioned about optos happening this week and still trying to call the high number.

• - *Ryan Vaspra*: Shared lead creation and closure times.

• - *Craig Schwarz*: Agreed and discussed the lead creation and closure times.

• 📈 *Path Conversion Report*

• - *Craig Schwarz*: Mentioned efforts to import data into the Looker report for more transparency and visual insights on retargeting.

• - *Craig Schwarz*: Working towards providing path conversion report as requested by Ryan.

• 📋 *Data Analysis and Optimization*

• - *Craig Schwarz*: Emphasized the need to optimize networks, cut non-performing tiers, and focus efforts on effective channels.

• - *Craig Schwarz*: Discussed the goal of optimizing strategies with a budget of $35k and the importance of pacing against efforts.

• 📅 *Daily Reporting*

• - *Cameron Rentch*: Described the process of receiving daily reports via Google Sheets for closed leads and follow-ups.

• - *Craig Schwarz*: Acknowledged the process of daily reporting and ensuring timely updates on dispositions and progress.

• 🔍 *Insights and Feedback*

• - *Craig Schwarz*: Requested feedback on publishers driving responses to enhance targeting strategies.

• - *Craig Schwarz*: Encouraged the team to gather insights on effective networks and channels for improved performance.

• 🚀 *Action Items*

• - *Craig Schwarz*: Mentioned plans to start cutting non-performing networks and optimizing tiers during the week.

• - *Craig Schwarz*: Discussed the importance of balancing efforts with pacing and focusing on effective strategies.

• 📑 *Documentation and Follow-up*

• - *Cameron Rentch*: Shared details on receiving updates and reports for tracking progress and outcomes.

• - *Craig Schwarz*: Agreed to implement the process of receiving daily updates and reports for better tracking and decision-making.

Gist • Meeting discussed marketing campaign analysis, audience targeting refinement, data reporting enhancement, and team coordination improvement.

Bullet Gist • ⚙️ Marketing Campaign Analysis: Led by Craig Schwarz and Cameron Rentch, with insights from Steve Wilcox and Ryan Vaspra.

• 📊 Audience Targeting Refinement: Emphasized based on age range and ethnic demographics to align with center cases.

• 📈 Data Reporting Enhancement: Focused on gaining better visibility into lead outcomes post-conversion.

• 🤝 Team Coordination Improvement: Suggestions made to adjust meeting schedules for better coordination.

Short Summary • The meeting delved into the analysis of the marketing campaign led by Craig Schwarz and Cameron Rentch, focusing on spending, conversion rates, lead generation, and media strategies, with insights from Steve Wilcox and Ryan Vaspra. Audience targeting refinement based on age range and ethnic demographics was emphasized to align with Maryland Juvenile Hall and Los Angeles centers' cases. Data transparency for network selection optimization, data reporting enhancement for better lead outcome visibility, and coordination improvement among team members were key priorities discussed.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-06 18:06:59

Title: Ryan / Nick Date: Mon May 06 2024 18:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nicholas@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting primarily focused on *Ryan Vaspra guiding Nicholas Ward* through various project boards and data management tasks. Ryan explained project boards intricacies, highlighting the importance of proper delegation and task management. They discussed new software tools for efficient data handling and Nicholas's critical role in managing financials.

• Insights were shared into their roles, emphasizing Nicholas's role in financial management. Streamlining processes with automation was discussed, aiming to enhance productivity and handle daily financial reports effectively. Technical aspects like altering database tables and troubleshooting errors were explored. Ryan stressed clear communication and transparency within the team for effective issue resolution and collaborative problem-solving.

• Discussions emphasized leveraging technology tools to manage projects efficiently, streamline workflows, and improve data accuracy. The hands-on approach showcased teamwork dynamics, problem-solving strategies, and a commitment to continuous improvement in project management practices. The meeting highlighted Ryan Vaspra's leadership alongside Nicholas Ward's valuable contributions, underlining a collaborative approach and a focus on enhancing productivity.

Action Items • *Nicholas Ward*

• Start your own board (03:30)

• Get added to the tech project board (03:34)

• Review and update the db table schema in bigquery (17:44)

• Insert seed data for pricing model columns (23:55)

Outline Chapter 1: Initial Office Exploration and Project Overview (00:26 - 05:34)

• 00:26: Nicholas Ward starts familiarizing himself with the office environment and gathering information.

• 02:39: Nicholas Ward expresses his approach of learning through listening and asking questions.

• 04:19: Ryan Vaspra introduces the tech project board and discusses ongoing projects.

Chapter 2: Project Management and Task Assignments (05:05 - 09:26)

• 05:05: Nicholas Ward confirms recording details with Ryan.

• 07:42: Ryan Vaspra explains the setup of subtasks for specific project components.

• 09:07: Nicholas Ward acknowledges his assignment on the project board.

Chapter 3: Technical Project Details and Data Handling (10:39 - 17:13)

• 10:39: Ryan Vaspra elaborates on using voice technology for call experiences.

• 13:35: Nicholas Ward seeks guidance on showcasing a feature using BigQuery.

• 16:03: Ryan Vaspra explains the columns and input-output process in data handling.

Chapter 4: Database Creation and Management (17:59 - 21:43)

• 17:59: Ryan Vaspra discusses creating a table and data management.

• 19:26: Nicholas Ward encounters an issue with a query statement.

• 21:15: Nicholas Ward and Ryan Vaspra collaborate on schema details for the database.

Chapter 5: Financial Analytics and Workflow Implementation (26:13 - 28:34)

• 26:13: Ryan Vaspra discusses his role in financial analytics and data tracking.

• 27:29: Ryan Vaspra mentions implementing a table for tracking law firm details.

• 28:03: Nicholas Ward acknowledges the upcoming implementation and planning for the analyst's involvement.

Chapter 6: Productivity Optimization and Process Improvement (30:53 - 32:30)

• 30:53: Ryan Vaspra emphasizes the importance of dashboard utilization for productivity.

• 31:45: Ryan Vaspra discusses optimizing workflow processes for efficiency.

• 32:30: Ryan Vaspra reflects on time spent addressing stakeholder requests and improvements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-06 18:06:59

Shorthand Bullet • 📊 *Project Management Board* Setup**

• - *Ryan Vaspra* shared the tech project board for adding *Nicholas Ward*.

• - Discussion on creating individual boards for better project organization.

• 🛠️ *Task Management* and Prioritization**

• - Emphasis on assigning tasks to aid project progress.

• - Importance of utilizing tools like Natterbox for efficient communication.

• 🔍 *Data Management* and Analysis**

• - Overview of using BigQuery for data analysis.

• - Explanation of table structures and data handling processes.

• 📈 *Process Improvement and Automation*

• - Highlighted automation opportunities to enhance productivity.

• - Mentioned the potential for workflow enhancements and process changes.

• 💬 *Communication and Collaboration*

• - Discussion on involving team members in project planning.

• - Importance of clear communication for effective project management.

Gist • Meeting focused on project boards, data management, financials, and technology tools for efficiency. Emphasized teamwork, continuous improvement, and leadership.

Bullet Gist • ⚙️ Project Boards and Data Management: Focused on project boards intricacies and efficient data handling.

• 💰 Financial Management: Emphasized Nicholas's critical role in managing financials.

• 🔧 Automation and Technology Tools: Discussed streamlining processes, enhancing productivity, and improving data accuracy.

• 🤝 Teamwork and Collaboration: Highlighted clear communication, transparency, and collaborative problem-solving.

• 🚀 Continuous Improvement: Emphasized a commitment to enhance productivity and project management practices.

Short Summary • The meeting revolved around Ryan Vaspra guiding Nicholas Ward through project boards and data management tasks, stressing proper delegation and task management. Discussions highlighted the importance of Nicholas's role in financial management, automation for streamlining processes, and leveraging technology tools for efficient project management. They aimed to enhance productivity, handle financial reports, and improve data accuracy through collaborative problem-solving and clear communication within the team, showcasing a commitment to continuous improvement and a focus on enhancing productivity.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-07 11:53:07

Title: Catch up call (DL/Flatirons) Date: Tue May 07 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: myjahnee@tortintakeprofessionals.com, tony@tortintakeprofessionals.com, ryan@shield-legal.com, michaelbrunet@tortintakeprofessionals.com, mabramowitz@dicellolevitt.com, vernon@tortintakeprofessionals.com, cameron@themedialab.agency, alan@tortintakeprofessionals.com, brittany@tortintakeprofessionals.com, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • *Alan Gill* expressed concerns about financial reports' inaccuracies due to data interpretation differences among team members like *Ryan Vaspra. Mark Abramowitz* emphasized the urgency of resolving work process bottlenecks, maintaining accurate data records, and promptly obtaining necessary documentation. They discussed addressing challenges through increased monitoring, clear benchmarks, and potential incentives for staff. Efforts were made to identify productivity issues among team members handling various tasks and strategize solutions like adjusting work schedules and implementing tracking systems.

• *Mark* highlighted the need for automation instead of manual adjustments and the importance of updating lead ID numbers for information integration. He stressed urgency due to impending deadlines, advocating for coordinated efforts in resolving cases. *Alan* mentioned ongoing issues with Law Ruler integration and uncertainties about progress but hinted at potential solutions being explored. Concerns were raised regarding missed data updates impacting benchmark reports and the need for improved communication between teams to prevent crucial information gaps.

• *Efforts focused on discussing financial reports, data analysis discrepancies, and productivity improvement.* *Alan raised concerns about inaccurate financial reports due to data interpretation differences among team members. Mark emphasized resolving work process bottlenecks and maintaining accurate data records. They discussed addressing challenges through increased monitoring, clear benchmarks, and potential incentives for staff. Strategies were suggested for improving efficiency, such as adjusting work schedules and enhancing tracking systems.*

• *Further discussions addressed outstanding case management responsibilities and the importance of swift resolutions using targeted approaches.* *Mark highlighted the need for automation and updating lead ID numbers. He emphasized urgency and accountability in resolving cases. Alan* mentioned challenges with Law Ruler integration and hinted at potential solutions being explored. Concerns were raised about missed data updates impacting benchmark reports and the necessity of improved communication between teams.

Action Items • *Alan Gill*

• Review all differences and highlight them for the financial report (08:59)

• Remove declined QA ones and update the report (11:14)

• Get together with Brittany to discuss and possibly implement a solution (45:51)

• Update lead id number with relevant information (44:37)

• Report back on the shield side regarding medical records tracker for CSP's (48:35)

• *Cameron Rentch*

• Resolve discrepancies with Nick regarding flatiron data immediately, separate from the call (07:30)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-07 11:53:07

• Ensure Ryan Vaspra works with Brittany Barnett to align data formats for Lejeune cases (13:25)

• *Mark Abramowitz*

• Coordinate with Henry on monitoring productivity of CSPs and provide benchmarks document if needed (39:56)

• Discuss idea with Alan Gill and speed up actions due to upcoming deadlines (46:04)

• Ensure teams are split up effectively to handle multiple tasks simultaneously (47:26)

• Investigate missing data in benchmark reports and address responsibilities within teams (49:32)

Outline Chapter 1: Financial Report Analysis (01:19 - 09:07)

• 01:19: Alan Gill raises questions about discrepancies in Nick's financial report compared to Dave's statements.

• 03:18: Alan Gill questions if the audit has been completed.

• 08:45: Alan Gill plans to identify and list all differences in the financial report.

Chapter 2: Data Integration Challenges (12:09 - 16:57)

• 12:09: Brittany Barnett assigns Edward to work on a script to compare EO data with form 95 data.

• 16:34: Cameron Rentch highlights challenges in aligning data fields and headings for comprehensive analysis.

Chapter 3: Data Cleaning and Analysis (23:29 - 25:02)

• 23:29: Mark Abramowitz emphasizes the importance of cleaning up data for accuracy.

• 24:31: Alan Gill acknowledges the need for data cleaning and analysis.

Chapter 4: Process Optimization and Monitoring (32:10 - 34:23)

• 32:10: Cameron Rentch stresses the importance of obtaining answers and setting reasonable timeframes.

• 33:23: Cameron Rentch discusses the need for clear guidelines, benchmarks, and monitoring for improved efficiency.

• 34:10: Cameron Rentch plans to address staffing issues and incentivize performance once operations are back on track.

Chapter 5: Communication and Task Delegation (36:01 - 42:48)

• 36:01: Mark Abramowitz emphasizes the need for clear roles and responsibilities within the team.

• 38:28: Cameron Rentch emphasizes maximizing productivity during work hours.

• 42:48: Mark Abramowitz suggests sending important documents via FedEx for prompt delivery.

Chapter 6: Action Plan and Follow-Up (43:30 - 50:26)

• 44:23: Mark Abramowitz suggests aligning data with Ryan for more precise answers.

• 46:04: Alan Gill plans to discuss implementing strategies with Brittany and Mark.

• 47:02: Mark Abramowitz prepares for an upcoming hearing and schedules further discussions.

Shorthand Bullet • 📊 *Data Alignment and Reporting*

• - *Alan Gill and *Cameron Rentch discussed aligning data and reports for clarity and accuracy.**

• - *Cameron emphasized the importance of clear guidelines and benchmarks for monitoring.*

• 📋 *Form 95 Data Integration*

• - *Brittany Barnett and *Ryan Vaspra talked about integrating up-to-date Form 95 data for accuracy.**

• - *Mark Abramowitz highlighted the need for reliable data sources for reporting.*

• ⏰ *Work Productivity and Monitoring*

• - *Cameron Rentch emphasized maximizing work hours and productivity for effective results.*

• - *Clear goals and monitoring mechanisms were discussed to keep the workflow on track.*

• 🤝 *Team Collaboration and Accountability*

• - *Alan Gill mentioned discussing team metrics with *Henry for accountability.**

• - *Mark Abramowitz stressed the importance of delegating work effectively within the teams.*

Gist • Financial data accuracy concerns, process bottlenecks, and productivity issues discussed with strategies for improvement. Emphasis on automation, lead ID updates, and Law Ruler integration challenges.

Bullet Gist • ⚠️ Financial Data Concerns: Inaccuracies due to interpretation differences highlighted.

• ⏳ Process Bottlenecks: Urgency in resolving work obstacles emphasized.

• 📈 Productivity Strategies: Efforts to improve efficiency through adjustments and tracking systems.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-07 11:53:07

• 🤖 Automation Focus: Importance of automation over manual adjustments stressed.

• 🔢 Lead ID Updates: Emphasis on updating lead ID numbers for integration.

Short Summary • The discussion revolved around concerns raised by Alan Gill and Mark Abramowitz regarding financial data inaccuracies, work process bottlenecks, and productivity challenges within the team. They highlighted the need for increased monitoring, clear benchmarks, and potential incentives to address these issues. Strategies included adjusting work schedules, implementing tracking systems, and emphasizing automation and lead ID updates. Challenges with Law Ruler integration and missed data updates were also addressed, stressing the importance of improved communication between teams to prevent information gaps.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-07 13:38:50

Title: Catch up Date: Tue May 07 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* solicited *Andy Rogers for a conversation regarding commissions. Andy Rogers agreed and proceeded to discuss the matter with Ryan Vaspra*.

Action Items • *Ryan Vaspra*

• Go over commissions with Andy Rogers (03:48)

• Follow up on available time to discuss commissions (05:08)

Outline Chapter 1: Discussion on Commissions (03:44 - 05:08)

• 03:44: *Ryan Vaspra initiates discussion on going over commissions with Andy Rogers*.

• 03:51: *Ryan Vaspra asks if Andy Rogers* is available to review commissions.

Chapter 2: Clarifying Details (00:00 - 02:33)

• 00:00: *Ryan Vaspra* mentions "It it it's".

• 02:33: *Ryan Vaspra* repeats "It".

• 04:42: *Ryan Vaspra* mentions "It's".

• 05:08: *Ryan Vaspra* repeats "It it".

Shorthand Bullet • 🔍 *Commissions Review*

• - Andy Rogers: Are you available to go over commissions?

• - Ryan Vaspra: Sending you available to go over commissions.

Gist • A discussion about commissions between Ryan Vaspra and Andy Rogers took place.

Bullet Gist • 💬 Discussion Initiated: Ryan Vaspra reached out to Andy Rogers to discuss commissions.

• ✅ Agreement Reached: Andy Rogers agreed to engage in the conversation with Ryan Vaspra.

• 💼 Business Context: The meeting likely pertained to financial or sales-related matters.

Short Summary • Ryan Vaspra engaged Andy Rogers in a conversation regarding commissions. Andy Rogers accepted the discussion and proceeded to address the commission matter with Ryan Vaspra. The meeting centered on commission-related topics, indicating a business or sales context. The interaction likely involved negotiating or clarifying commission structures and agreements between the two parties. The exchange was professional and focused on financial arrangements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-08 12:36:59

Title: Meeting with TIP Date: Wed May 08 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: branden.brooks@lawruler.com, ryan@themedialab.agency, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* and *Branden Brooks discuss API features and milestones* and emphasize supporting *Nick Ward with Tony* and Brett effectively. They review advanced API additions, planning a five-week timeline from the signed statement of work. **Ryan aims to help Nick establish rapport and avoid being underutilized. Branden offers assistance, suggesting sending information to both Nicks for review.

• Ryan highlights concerns about Nick potentially underutilization, stressing the importance of supporting him. The agreed next steps focus on project delivery and collaboration strategies for Nick's success within the team. The meeting concludes with mutual appreciation, indicating readiness for further communication and action points discussion.

Action Items • *Nick Ward*

• Meet with Nick McFadden, Nick Ward first for review (02:50)

• Assist Nick Ward in building rapport with Tony and Brett (03:05)

Outline Chapter 1: Project Review and Planning (00:01 - 03:02)

• 00:01: The meeting starts with a review of the project status.

• 01:51: *Branden* outlines the advanced API features and lead lock feature to be implemented.

• 02:30: Milestones are added to the timeline, with production expected to start five weeks from the signed statement of work.

Chapter 2: Team Collaboration and Support (03:05 - 03:46)

• 03:05: *Ryan* discusses the plan to review the information with Nick McFadden and Nick Ward.

• 03:18: Providing support to Nick Ward to build rapport with the team.

• 03:46: Emphasizing the importance of helping Nick Ward succeed in his role.

Chapter 3: Document Sharing and Communication (03:55 - 04:15)

• 03:55: Branden confirms sending the document to Ryan, Nick Ward, and Nick McFadden.

• 04:12: Document delivery is acknowledged, and farewell exchanged.

Shorthand Bullet • 📋 *Final Review and Milestones*

• - Branden Brooks reviews the advanced API features and lead lock feature with Ryan Vaspra.

• - Milestones added to the timeline for production, taking around five weeks from signed statement of work.

• - Ryan Vaspra to meet with Nick McFadden and Nick Ward for review and question sessions.

• 🤝 *Support for Nick Ward*

• - Ryan Vaspra aims to support Nick Ward in building rapport with Tony and Brett.

• - Branden Brooks offers assistance to facilitate Nick Ward's success.

• 📧 *Document Sharing*

• - Branden Brooks to send the reviewed details to Ryan Vaspra, Nick Ward, and Nick McFadden.

• - Document to be sent shortly for further review and discussion.

Gist • Discussion on API features and milestones, focusing on supporting Nick Ward for success. Advanced API additions planned with a five-week timeline from signed statement of work. Concerns about Nick's potential underutilization addressed with collaboration strategies and readiness for further communication.

Bullet Gist • ⚙️ API Features and Milestones: Discussion on advanced API additions and milestones.

• 🤝 Supporting *Nick Ward: Emphasis* on supporting Nick for success within the team.

• ⏳ Timeline Planning: Five-week timeline set from signed statement of work.

• ⚠️ Concerns Addressed: Concerns about Nick's potential underutilization raised.

• 🤝 Collaboration Strategies: Agreed next steps focus on project delivery and supporting Nick.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-08 12:36:59

• The discussion centered around API features and milestones, with Ryan Vaspra and Branden Brooks emphasizing the importance of supporting Nick Ward for success within the team. They reviewed advanced API additions and planned a five-week timeline from the signed statement of work. Concerns were raised about Nick potentially being underutilized, leading to a focus on collaboration strategies to ensure his success. The meeting concluded with mutual appreciation and readiness for further communication and action points discussion.

Ryan (ryan@themedialab.agency)
2024-05-09 11:30:36

Ben Crump Retained Case Statuses:

• Presign - Case Signed - File Not In Office [2:55 PM] Desirée Austin-Holliday

• LV – Case Retained by Pintas [2:55 PM] Desirée Austin-Holliday

• LV-retained case [2:55 PM] Desirée Austin-Holliday

• Pre-Lit - Case Retained In House [2:55 PM] Desirée Austin-Holliday

• Pre-Lit - Retained Sent to Handling Firm

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-09 14:23:05

Title: TIP Reporting Sync Date: Thu May 09 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nicholas@tortintakeprofessionals.com, anthony@tortintakeprofessionals.com, nickmcfadden@tortintakeprofessionals.com, luke@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Meeting Summary:*

• In this meeting, *Ryan Vaspra and Nicholas Ward discussed lead conversion metrics, reviewing a report by Anthony* and planning a specification tab for detailed definitions. They aimed to integrate reporting into a Data Studio dashboard. Addressing discrepancies in e-sign dates, they identified issues with status changes affecting finalization dates, emphasizing accurate tracking for financial reconciliation. They explored solutions to align system records with actual sign dates and forthcoming projects using Looker for data analysis tasks related to Conex data integration.

• *Ryan Vaspra* talked about updating financial tables with *Shane for training purposes and immediate needs. Plans were made to compare telephony systems and collect data regularly. A meeting with Nicholas Ward* was scheduled to address pending issues. Nicholas suggested going through problems together, leading Ryan to reschedule prior commitments. They set a time slot for the session tomorrow, focusing on optimizing workflow processes within the team structure.

• Ryan expressed readiness to work with Nicholas on resolving issues and streamlining ongoing tasks with Shane's assistance. An upcoming meeting was planned to address specific work requirements efficiently. The interaction between *Ryan Vaspra and Nicholas Ward* highlighted collaboration efforts in resolving operational challenges promptly, setting clear objectives for future engagements. Their coordination reflected a proactive approach towards workflow optimization.

Action Items • *Ryan Vaspra*

• Investigate and address the discrepancy in the sign dates (20:04)

• Set up a meeting with Luke, Brian, and Nick to get Anthony into Looker Enterprise for training (19:32)

• Work on building a data studio interface for the team's deliverables (19:32)

• Update the financial table to run every hour or every half hour (41:58)

• Have Shane update the financial table (41:58)

• Solve immediate needs now versus future planning (42:20)

• Gather data on other telephony systems for comparison (42:25)

• Create daily roll-ups of data looking forward (42:40)

• *Nicholas Ward*

• Review lead IDs for discrepancies and make necessary changes to prevent future issues (37:27)

• Schedule a meeting with Ryan to go over issues (43:00)

Outline Chapter 1: Data Analysis Tool Overview (00:00 - 04:59)

• 00:21: Ryan introduces the data analysis tool and initiates a discussion on its functionality.

• 03:35: Nicholas demonstrates the tool's features for tracking leads and conversions.

Chapter 2: Spec Creation and Reporting (05:23 - 13:27)

• 05:23: Ryan instructs on creating a spec tab for detailed reporting requirements.

• 12:25: Ryan emphasizes the importance of documenting the data structure for future automation.

Chapter 3: Data Visualization and Dashboard Creation (14:09 - 19:59)

• 14:59: Ryan discusses the process of creating visualizations like line charts and scorecards.

• 19:45: Nicholas mentions clickable links and enhanced reporting capabilities.

Chapter 4: Data Accuracy and Reporting Challenges (21:13 - 30:04)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-09 14:23:05

• 21:33: Nicholas raises concerns about data accuracy and matching dates in reports.

• 27:48: Ryan assures alignment between law ruler reports and financial logs for accuracy.

Chapter 5: Future Data Integration and Training (32:14 - 43:43)

• 32:56: Ryan suggests methods for refining data integration processes.

• 41:23: Ryan plans a training session for advanced reporting using Looker Enterprise.

• 43:43: Ryan schedules a meeting to review the law ruler statement of work.

Shorthand Bullet • 📊 *Total Leads and Conversions*

• - *Nicholas Ward* shared a report showing total leads, total finals, conversion finals, and decline numbers.

• - The report breaks down leads and conversions by day for comparison.

• 📝 *Spec Sheet Request*

• - *Ryan Vaspra* asked for a specification sheet to be added to the report, detailing grouping by day, case type, or hour.

• - The sheet should include total leads, total finals, conversion percentages, and definitions for each metric.

• 📈 *Accuracy Improvement*

• - *Ryan Vaspra* noted that the current data tracking is more accurate due to the inclusion of new lead forms.

• - This improvement enhances the reliability of the reported numbers.

• 📅 *Day-by-Day Reporting*

• - The report includes components for daily summaries, case type breakdowns, and hourly analyses.

• - *Ryan Vaspra* emphasized the importance of clear day-over-day and weekly reports for quick reference.

• 📧 *Automated Reporting*

• - Discussion on automating data extraction for easy dashboard creation and sharing via email or other platforms.

• - *Ryan Vaspra* highlighted the efficiency of using a data explorer for generating reports.

• 🔍 *Data Analysis and Reporting Tools*

• - Mention of using Looker Enterprise for in-depth data analysis and visualization.

• - Plans to introduce team members to Looker for exploring and utilizing data effectively.

• 📅 *Upcoming Meetings*

• - Scheduling a session to review the Law Ruler statement of work with *Nicholas Ward and Ryan Vaspra*.

• - *Ryan Vaspra* proposed a time slot for the meeting to discuss the statement of work in detail.

Gist • Discussion on lead conversion metrics, data integration, and workflow optimization. Collaboration between Ryan Vaspra and Nicholas Ward for resolving operational challenges and setting clear objectives for future engagements.

Bullet Gist • 💬 Lead Conversion Metrics Review: Discussion on lead conversion metrics and data integration.

• 📊 Data Integration Planning: Plans to integrate reporting into a Data Studio dashboard for detailed definitions.

• 🔄 Workflow Optimization: Focus on aligning system records with actual sign dates and optimizing workflow processes.

• 🔍 Data Analysis with Looker: Exploring solutions using Looker for data analysis tasks related to Conex data integration.

• 🤝 Collaborative Efforts: Collaboration between Ryan Vaspra and Nicholas Ward to resolve operational challenges.

Short Summary • The meeting between Ryan Vaspra and Nicholas Ward centered on lead conversion metrics, data integration, and workflow optimization. They reviewed a report by Anthony, planned a specification tab for detailed definitions, and aimed to integrate reporting into a Data Studio dashboard. Addressing discrepancies in e-sign dates, they identified issues with status changes affecting finalization dates, emphasizing accurate tracking for financial reconciliation. Ryan discussed updating financial tables with Shane, comparing telephony systems, and scheduling a meeting with Nicholas to address pending issues. They emphasized collaboration in resolving operational challenges and setting clear objectives for future engagements, reflecting a proactive approach towards workflow optimization.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-09 15:09:24

Title: ZOOM: DiCello Levitt <> BP Date: Thu May 09 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, austin@broughtonpartners.com, mabramowitz@dicellolevitt.com, gary@broughtonpartners.com, cameron@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • *Mark Abramowitz*, also known as Abe, and Austin discussed obtaining specific raw data for case analyses. Mark highlighted the importance of clean data for accurate evaluations and confirmed the required dataset related to Rosen's case. They agreed on sharing this crucial raw data promptly. Austin assured seamless collaboration by mimicking the requested file format and offering additional formats if necessary.

• The conversation concluded positively with a plan in motion to share the requested data. Both parties expressed satisfaction with the straightforward discussion and emphasized open communication channels for future requirements. Ryan Vaspra briefly joined but didn't significantly impact the main dialogue between *Mark* and Austin. The focus remained on the urgency of obtaining and sharing clean data for case analyses. Open communication channels were prioritized for effective collaboration moving forward.

Action Items • *Mark Abramowitz*

• Provide raw data from the intake (02:12)

• Send over the specific data requested (02:48)

• Email the manipulated file for their cases (03:18)

• Confirm if there are other formats available and send additional columns if possible (03:44)

Outline Chapter 1: Data Request and Clarification (02:00 - 03:30)

• 02:00: Mark requests raw data from the intake to understand the injuries in cases.

• 02:58: Confirmation of the specific data needed regarding the Rosen case.

• 03:30: Agreement to provide the requested data.

Chapter 2: Data Format and Additional Information (03:38 - 04:35)

• 03:38: Mark inquires about other formats or additional column data that can be provided.

• 04:05: Clarification on the type of additional data requested.

• 04:35: Assurance to double-check for any missing information and inclusion in the data export.

Chapter 3: Data Delivery Timeline (04:36 - 05:07)

• 04:36: Confirmation of data delivery later the same day.

• 05:01: Assurance of prompt delivery by the end of the day.

• 05:07: Conclusion of the conversation with expectations of receiving the data soon.

Shorthand Bullet • 📊 *Request for Raw Data*

• - *Mark Abramowitz* requests raw data from the intake showing different injuries on all cases.

• - The data was requested due to issues with previous data received.

• 📁 *Data Transfer*

• - *Austin* agrees to provide the specific raw data requested by *Mark Abramowitz*.

• - Austin will have the BI team mimic the exact file and send it over.

• 🔍 *Additional Data* Formats**

• - *Mark Abramowitz* asks about other file formats or column data that can be provided.

• - Austin will double-check for any additional data that was not included in the initial export.

Gist • Discussion on obtaining and sharing clean data for case analyses, emphasizing open communication channels.

• 📊🔄📞

Bullet Gist • ⚙️ Obtaining Raw Data: Discussion on obtaining specific raw data for accurate evaluations.

• 🔄 Sharing Data: Agreement on promptly sharing crucial raw data.

• 📞 Open Communication: Emphasis on open communication channels for future collaboration.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-09 15:09:24

• Mark Abramowitz (Abe) and Austin discussed the importance of obtaining specific raw data for case analyses, focusing on the significance of clean data for accurate evaluations. Mark confirmed the required dataset related to Rosen's case, and both parties agreed on promptly sharing the crucial raw data. Austin assured seamless collaboration by mimicking the requested file format and offering additional formats if necessary. The conversation concluded positively with a plan in motion to share the requested data, highlighting the satisfaction with the straightforward discussion and the emphasis on open communication channels for future requirements. Ryan Vaspra briefly joined but didn't significantly impact the main dialogue between Mark and Austin, as the focus remained on the urgency of obtaining and sharing clean data for case analyses, prioritizing open communication channels for effective collaboration moving forward.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 13:03:15

Title: Shield Legal // Bytecode - Project Planning Date: Fri May 10 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: deb.chatterjee@bytecode.io, ryan@brandlytics.io, javier.ramos@bytecode.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Deb Chatterjee, Ryan Vaspra, and Javier Cardenas-Ramos* held a meeting to discuss work-related topics. Ryan gave an overview of their data analytics workflow, with team members such as Brian Hurst and Luke Fontaine. Roles within his team were outlined, emphasizing data engineering and analysis tasks.

• Ongoing projects involve building pipelines using Python for prediction models, working with AWS databases, and using CRM systems like Copper. Challenges include API integrations, legacy system migrations, and data visualization tools like DBT. Priority was given to engaging external resources for data engineering support and using tools like Retool for user-friendly portals.

• Additional assistance is needed from experts like Michael Talik, particularly in areas beyond the team's expertise. Future steps include coordinating with resourcing teams to allocate support hours based on project needs. Communication channels through Slack or Google Workspace will facilitate collaboration once external support is onboarded.

Action Items • *Ryan Vaspra*

• Reach out to Javier early next week with progress on data engineering milestone (33:11)

Outline Chapter 1: Data Engineering Efforts Overview (03:19 - 08:56)

• - Ryan discusses pushing organic cases and case types for revenue growth.

• - Legacy system integration into Bigquery for call center data conversion.

• - Implementation of CRM with sales team requests and SQL code development.

Chapter 2: Utilizing Chat GDP and DBT (09:24 - 16:51)

• - Ryan explains using Chat GDP for SQL queries and data formatting in DBT.

• - Challenges faced in formatting queries in DBT efficiently.

• - Importance of understanding business metrics and financial flows.

Chapter 3: Engaging Data Engineering Support (17:01 - 18:28)

• - Javier outlines the process of allocating support hours for data engineering efforts.

• - Need for ad hoc support on data engineering and looker side.

Chapter 4: Prioritizing Data Engineering and Modeling (19:16 - 31:41)

• - Priority on data engineering, DBT, and modeling for upcoming tasks.

• - Planning to engage a resource for retool support post-data engineering.

• - Discussion on next steps and connecting with resourcing team for project staffing.

Chapter 5: Operations and Communication Planning (32:04 - 33:25)

• - Setting up effective communication channels and operational structure.

• - Recap of insights shared on data analytics workflow and project requirements.

• - Commitment to follow up on data engineering milestones in the upcoming week.

Shorthand Bullet • 📊 *Data Engineering Priority*

• - *Ryan Vaspra* emphasized the importance of data engineering, DBT, and modeling as the top priority.

• - Plan to connect with resourcing team on Monday to allocate support from *Mike Tallock*.

• 📁 *Engagement Model Clarification*

• - *Javier Cardenas-Ramos* outlined the process for requesting ad hoc support, specifically in data engineering.

• - Discussion on submitting requests to allocate resources like *Mike* and setting up engagement scenarios.

• 🔧 *Operational Support*

• - Clarification on operational support and scoping to be provided by the team.

• - Suggestions for setting up communication channels like Slack or Google Workspace for coordination.

• 📅 *Next Steps and Follow-Up*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 13:03:15

• - *Ryan Vaspra* to update on data engineering milestone progress early next week.

• - Acknowledgment of the need for ongoing communication and planning for future use cases.

Gist • Team meeting discussed data analytics workflow, projects, challenges, and future steps with emphasis on external support and coordination.

Bullet Gist • ⚙️ Data Analytics Workflow Overview: Ryan presented the team's data analytics workflow and outlined team roles.

• ⏳ Ongoing Projects: Projects involve Python pipelines, AWS databases, and CRM systems like Copper.

• 🛠️ Challenges: Challenges include API integrations, legacy system migrations, and data visualization tools.

• 🔌 External Support Focus: Emphasis on engaging external resources for data engineering support.

• 📅 Future Steps: Future steps include coordinating support hours and enhancing collaboration through communication channels.

Short Summary • The team meeting involved Deb Chatterjee, Ryan Vaspra, and Javier Cardenas-Ramos discussing the data analytics workflow within the team, including roles of team members like Brian Hurst and Luke Fontaine. Ongoing projects focused on Python pipelines for prediction models, AWS databases, and CRM systems like Copper. Challenges included API integrations, legacy system migrations, and data visualization tools like DBT, with plans to engage external resources for support. Future steps included coordinating support hours based on project needs and leveraging communication channels for collaboration.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 13:04:18

Title: LawRuler - SOW Date: Fri May 10 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, nickmcfadden@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Meeting Summary:*

• *Ryan Vaspra* discussed TV campaigns, ad server logs, and Google Cloud services with *Nicholas Ward*. He shared efforts in data management and finance analysis, highlighting challenges faced. Insights on data engineering capabilities and collaboration with external resources like Mike were provided by Nicholas as they discussed using DBT for model building.

• Progressing, Ryan is mentoring *Brian Hurst and Luke Fontaine*, guiding them beyond their initial capabilities towards becoming data engineers. A deep dive into technical challenges faced by Ryan, particularly in advancing data engineering processes within the legal database setup, was emphasized. Plans to connect with the working team on Monday and setting up a dedicated Slack channel for communication were outlined.

• Ryan's expertise in mass torts cases involving *Ben Crump reflects his dedicated approach to nurturing talent and driving essential data engineering initiatives. The meeting showcased a strong focus on supporting Ryan's mentoring efforts and prioritizing data engineering tasks for efficient operations. The need for external support from Mike Tallock* for DBT modeling remained a priority, aligning with strategies for an internal portal and discussion on display scenarios.

• In summary, the meeting demonstrated Ryan's commitment to nurturing talent like Brian and Luke, emphasizing a hands-on approach to learning and development. The discussions highlighted the complexities involved in managing data processes, with a clear strategy outlined for collaboration with external experts for enhanced data engineering capabilities. Ryan's involvement in intricate legal processes further underlined the importance of meticulous handling of sensitive information in line with organizational goals.

Action Items • *Ryan Vaspra*

• Set up DBT for the shield system (1:09:23)

• Build a CRM opportunity order level dashboard in Copper (1:06:37)

• Continue working on modeling and automations to simplify daily routines, weekly routines, end of month routines, and closing the month routines (multiple references throughout)

• Have Brian complete the seed data (1:25:54)

• Plan a meeting next week to discuss progress and tasks (1:25:54)

• *Nicholas Ward*

• Submit a request to allocate Mike's expected hours for Ryan's engagement with data engineering support (1:14:59)

Outline Chapter 1: Data Organization and Workflow (02:26 - 15:29)

• 02:26: *Nicholas Ward* highlights the need for smoother processes.

• 03:37: *Ryan Vaspra* explains the tracking of consumer interactions across channels.

• 09:59: Discussion on analyzing the timing of consumer interactions.

• 10:24: Introducing the concept of exposed contact ID and question ID for organization.

• 13:11: Importance of the case type name format and software features.

Chapter 2: Financial Analysis and Reporting (17:07 - 25:56)

• 17:07: *Ryan Vaspra* discusses manual financial processes and routines.

• 20:07: Explanation of calculating the cost per worked lead.

• 22:11: Updating revenue and costs for financial accuracy.

• 24:06: Importance of constructing formulas and datasets for accurate reporting.

Chapter 3: CRM Implementation and Data Dashboard (40:33 - 50:17)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 13:04:18

• 40:33: *Nicholas Ward* mentions organizational skills and leadership qualities.

• 46:05: Discussion on the storyline and leadership attributes.

• 50:17: Consideration of sacrificing the storyline for productivity.

Chapter 4: Database Management and Query Development (1:00:06 - 1:19:31)

• 1:00:06: *Ryan Vaspra* discusses the volume of questions and work-related tasks.

• 1:06:26: Implementation of CRM tools and SQL code development.

• 1:09:42: Detailed discussion on lead tracking and data aggregation.

• 1:11:23: Future development plans and API integration considerations.

• 1:19:31: Importance of console refresh and project prioritization.

Chapter 5: Data Engineering Support and Planning (1:25:40 - 1:30:20)

• 1:25:40: Discussion on seed data completion and project deadlines.

• 1:27:00: *Nicholas Ward* emphasizes the need for support on the engineering side.

• 1:28:14: Planning to allocate resources for engineering support.

• 1:30:06: *Ryan Vaspra* plans to update on data engineering milestones next week.

Shorthand Bullet • 📊 *Data Engineering Support*

• - *Ryan Vaspra mentioned the need for data engineering support from *Mike Tallock to build pipelines in the CRM system.

• - Nicholas Ward confirmed the priority for data engineering and modeling support.

• - A request will be submitted to allocate Mike Tallock for expected hours of engagement.

• 🛠️ *CRM Dashboard Development*

• - Ryan Vaspra discussed the development of a CRM opportunity order level dashboard using SQL code with help from chat GDP.

• - The dashboard summarizes activity types, order details, payment information, and requires further configuration for optimal performance.

• 🔍 *Future Development* Planning**

• - Ryan Vaspra expressed a desire for full-time development involvement post API fixes in the call center CRM system.

• - Plans to involve Michael for configuration and to avoid issues with projects and Yammels.

• 📈 *Data Analytics Workflow Progress*

• - Nicholas Ward acknowledged Ryan Vaspra's progress in data engineering milestones.

• - Ryan Vaspra plans to update on data engineering achievements in the upcoming week.

Gist • Discussion on data management, finance analysis, and mentoring in data engineering. Collaboration with external resources. Emphasis on talent nurturing and data engineering tasks.

Bullet Gist • ⚙️ Data Management and Finance Analysis: Discussions on TV campaigns, ad server logs, and Google Cloud services.

• 🤝 Collaboration and External Resources: Collaboration with external resources like Mike for model building.

• 🌱 Talent Nurturing and Mentoring: Emphasis on mentoring Brian Hurst and Luke Fontaine in data engineering.

• 🔧 Technical Challenges: Deep dive into advancing data engineering processes within legal database setup.

• 💡 Strategic Planning: Setting up a dedicated Slack channel for team communication.

Short Summary • The meeting delved into various topics including data management, finance analysis, and mentoring in data engineering, with Ryan Vaspra and Nicholas Ward leading the discussions. They highlighted challenges in data processes, the use of DBT for model building, and the importance of external collaboration with experts like Mike Tallock. Ryan's mentoring efforts with Brian Hurst and Luke Fontaine were emphasized, showing a commitment to developing talent in data engineering. The session underscored the complexities of managing data processes and the strategic approach to enhancing data engineering capabilities through external support and meticulous handling of legal data.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 13:52:35

Title: CMT to Connex / Hair Relaxer Case Files Import Date: Fri May 10 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, desiree@bencrump.com, adrienne@brandlytics.io, andy@shield-legal.com, jon@bencrump.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting commenced with *Andy Rogers recounting his recent emergency eye surgery experience, followed by Jonathan Wright sharing a similar incident. Desiree* A* raised questions about CTM subscription end dates and voicemail forwarding, while *Ryan Vaspra clarified transitioning to Connex for phone management. Discussions then focused on handling hair relaxer cases in Smart Advocate, led by *Jonathan Wright*, with insights shared by Ryan, Desiree, and Andy. Participants navigated work-related discussions on UDFs and case types within Smart Advocate seamlessly.

• As the meeting progressed, a dynamic atmosphere was fostered with personal anecdotes intertwined with professional topics. Conversations delved into the technical details of managing UDFs and case types for hair relaxer cases within Smart Advocate. *Jonathan Wright, Ryan, Desiree, and Andy contributed insights, fostering a collaborative approach to problem-solving. The meeting concluded with appreciative sentiments shared among attendees, with Jonathan* expressing gratitude for everyone's input. Andy humorously shared family dynamics, reflecting on his son's resemblance to him.

• In summary, the meeting's discussions revolved around personal experiences, business matters, and technical details related to Smart Advocate. The collaborative atmosphere allowed for seamless transitions between work-related discussions and light-hearted exchanges. Insights from *Andy Rogers, Jonathan Wright*, Ryan, and Desiree enhanced understanding and problem-solving approaches. The meeting's cordial conclusion highlighted the camaraderie among attendees, underscoring the value of shared experiences and appreciation for teamwork.

Action Items • *Desiree A*

• Check CTM subscription end date (05:15)

• Forward voicemails from CTM to Conex (05:25)

• *Ryan Vaspra*

• Undo agent licenses in Connex for non-renewal (05:56)

• Keep call tracking metrics for Ben Crump law firm as marketing system (06:11)

• Update hair relaxer case type in Smart Advocate with UDFs (10:54)

• *Andy Rogers*

• Clarify travel restrictions due to eye surgery before flying to Vegas (08:48)

Outline Chapter 1: Clarifying CTM Subscription and Voicemail Forwarding (04:15 - 06:28)

• - Desiree inquires about the end date of the CTM subscription and the possibility of forwarding voicemails to Connect.

• - Ryan explains that voicemails will be managed through Connect, not CTM.

Chapter 2: Call Tracking Metrics and Operational Phone Management (06:32 - 07:02)

• - Ryan discusses how call tracking metrics are used for lead collection and analysis.

• - The team ensures operational phone management is in place for tracking leads effectively.

Chapter 3: Data Mapping in Smart Advocate (11:46 - 13:47)

• - Ryan plans to export UDFs from Smart Advocate and map them with the team's assistance.

• - Desiree expresses the need for improved documentation in Smart Advocate for better usability.

Chapter 4: Finalizing Case Information Integration (14:55 - 15:09)

• - The team confirms the process of importing case information without answering intake questions.

• - Jonathan acknowledges the clear instructions provided for the task.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 13:52:35

Chapter 5: Weekly Routine and Office Schedule (17:40 - 18:00)

• - Ryan outlines his office schedule for the upcoming week.

• - Andy and Jonathan discuss their availability and routine tasks for the week.

Chapter 6: Closure Rates and Future Plans (20:06 - 20:33)

• - Andy mentions the need for improved closure rates.

• - The team concludes the discussion with a focus on future developments and updates.

Shorthand Bullet • 📋 *CTM Voicemails Forwarding*

• - *Desiree A* inquired about forwarding voicemails from CTM to Connect.

• - *Ryan Vaspra* explained the process involving call tracking metrics.

• 📊 *Call Tracking Metrics Integration*

• - Discussion on porting 150+ tracking numbers for lead retention.

• - *Ryan Vaspra* highlighted the role of call tracking metrics in lead collection and analysis.

• 📞 *Smart Advocate Field Mapping*

• - Mapping UDF fields from Smart Advocate for data alignment.

• - *Ryan Vaspra* planned a mapping process involving Mike and Dwight.

• :knifeforkplate: *Dinner Plans*

• - *Ryan Vaspra* suggested meeting for dinner before departure.

• - *Andy Rogers* to clarify plans with the team.

Gist • Meeting covered personal experiences, business matters, and technical details in Smart Advocate. Collaboration and camaraderie were key themes.

Bullet Gist • ⚙️ Technical Details in Smart Advocate: Focus on UDFs and case types for hair relaxer cases.

• 🤝 Collaborative Atmosphere: Seamless transitions between work discussions and personal exchanges.

• 🤣 Personal Anecdotes: Andy shared family dynamics humorously.

• 👁️ Personal Experiences: Andy and Jonathan recounted emergency eye surgery incidents.

• 💬 Business Matters: Discussions on CTM subscriptions, voicemail forwarding, and transitioning to Connex.

Short Summary • The meeting encompassed discussions on personal experiences like emergency eye surgery, business matters including CTM subscriptions and phone management, and technical details in Smart Advocate regarding UDFs and case types for hair relaxer cases. The atmosphere was collaborative and dynamic, blending work-related topics with personal anecdotes, culminating in a cordial conclusion highlighting teamwork and shared experiences.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 14:51:31

Title: TIP EOM / Revenue Updates for SL & CC Costs Date: Fri May 10 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, luke@shield-legal.com, luke@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting primarily focused on *Ryan Vaspra and Luke Fontaine* discussing work-related topics, emphasizing financial analysis for Shield legal revenue. They delved into revenue, expenses, and commission calculations, discussing LLC formation for tax benefits and the importance of financial planning.

• *Ryan* and *Luke* also outlined upcoming tasks involving DBT usage, visualization dashboard creation, and the need to streamline performance calculations. Future meetings were planned to improve operational efficiency within their workflow. They shared insights on education choices for children, relocating homes for family activities, entrepreneurialism, investment strategies, and tax implications of different business structures.

• The discussions intertwined professional responsibilities with personal anecdotes on finances and life decisions. Insights aimed at striking a balance between career growth and personal well-being amidst challenging work dynamics. Personal experiences with taxes, LLC formation for tax benefits, and discussing financial planning highlighted the importance of integrating work and personal life effectively.

• Overall, the meeting revealed a blend of professional responsibilities and personal insights, emphasizing the integration of career development with personal well-being. The discussions were focused on financial matters, work tasks, and personal life decisions, highlighting the importance of holistic approaches to achieve a balance between professional growth and personal fulfillment.

Action Items • *Luke Fontaine*

• Work on geographical heat map and data set summary charts (40:49)

• Check with James for edits on the visualization dashboard (41:03)

• Ensure correct setup of auto switch in DBT for time statement (41:21)

• *Ryan Vaspra*

• Coordinate with Shane to finalize AWS patchwork for tip calculate performance (42:02)

• Review and validate data sets related to financial calculations with Shane (42:10)

• Take action items from Monday's meeting regarding AWS tasks seriously, especially related to tip calculations (43:00)

Outline Chapter 1: Financial Analysis and Decision Making (00:54 - 17:34)

• 00:54: Ryan expresses urgency in completing financial tasks.

• 03:16: Discussion on daily operational expenses.

• 09:30: Reviewing financial data and percentages for shield revenue.

• 17:34: Calculations and decision-making on financial shortfall coverage.

Chapter 2: Task Assignments and Progress Tracking (20:17 - 31:57)

• 20:17: Planning upcoming tasks and review with Luke.

• 26:55: Mention of ongoing work and coordination with team members.

• 31:57: Discussion on tax advice and incorporation.

Chapter 3: Data Visualization and Project Planning (40:03 - 46:55)

• 40:03: Recap of completed tasks and upcoming priorities.

• 41:40: Focus on reconciliation and data validation tasks.

• 45:34: Discussion on project management and task delegation.

Shorthand Bullet • 📊 *Discussion on Financial Operations*

• - *Flat irons call review with Ryan Vaspra*

• - Mention of daily operation expenses

• - Quarterly formula inclusion

• - Review before making changes to tip database and shield legal call center costs

• 💼 *Task Assignments*

• - *Luke Fontaine to work with *Shane on tip performance calculations**

• - Validation of data set with Shane

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-10 14:51:31

• - Visualization dashboard creation by Luke with James

• 📉 *Future Plans*

• - *Development pause on tip-related tasks*

• - Luke and Nick collaboration on morning financials

• - Emphasis on task recall in upcoming Monday meeting

• 📝 *Data Analysis and Collaboration*

• - *Ryan Vaspra's tax advice discussion*

• - Incorporation and tax-related talks

• 🚀 *Entrepreneurship Insights*

• - Ryan's ambition to be CEO and achieve success

• - Importance of understanding investor expectations

Gist • Discussion on financial analysis, LLC formation, and personal well-being integrating work-life balance

• 📊💼💰

Bullet Gist • 💼 Financial Analysis: Focused on Shield legal revenue and expenses.

• 📊 LLC Formation: Discussed for tax benefits.

• 💰 Personal Well-being: Highlighted importance of work-life balance.

Short Summary • The meeting between Ryan Vaspra and Luke Fontaine revolved around financial analysis for Shield legal revenue, including revenue, expenses, and commission calculations. They discussed LLC formation for tax benefits, financial planning, upcoming tasks on DBT usage, visualization dashboard creation, and streamlining performance calculations. The blend of professional responsibilities and personal insights emphasized the importance of integrating career growth with personal well-being, touching on education choices, family activities, investment strategies, and tax implications of different business structures.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-13 13:48:51

Title: Tech Project Status Weekly Date: Mon May 13 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting began with a discussion on operational and financial matters. *Brian Hirst shared personal health updates, leading into a conversation with Luke Fontaine about aging concerns. The focus then shifted to a financial discussion led by Ryan Vaspra* on data analysis and cost considerations related to commission rates and database structures. The team addressed issues with reporting accuracy and challenges in managing research project overages, emphasizing the importance of clear cost projections.

• Efforts were made to refine data extraction processes and plan future meetings for lambda upgrades under the guidance of *Shane Latimer. The meeting covered diverse topics ranging from personal well-being discussions to financial analyses, highlighting a collaborative effort towards operational efficiency. Ryan Vaspra discussed changes in the database related to document processing stages and set up an internal meeting with Shane. A plan outlined by Ryan Vaspra included tasks such as performance tip calculations, fixing Shield Legal* issues, generating log updates, and creating a test dashboard for comparison purposes.

• *Ryan Vaspra* then scheduled a post-retainer billables meeting involving key individuals like Alan, Gil, Brian, Hurst, and Luke to address billing discrepancies and ensure a proper understanding of billable items. *Nick McFadden and Ryan Vaspra* discussed revenue-related matters and coordinated efforts around resolving status issues and potential dashboard modifications. The team's focus was on improving communication around reporting requests and scoping out tasks for system enhancements to drive strategic decision-making within the team structure.

Action Items • *Ryan Vaspra*

• Finalize the pricing details with Cameron (05:17)

• Sling a meeting invite to Cameron for cost management discussion (09:44)

• Set up a review meeting with James on Unicorn costs and future strategy (32:48)

• Schedule a 45-minute meeting with Shane to set up access (41:51)

• Create calculate performance tip version (42:03)

• Fix shield legal issues (42:07)

• Generate tip thin log with status changes for Shield Legal (42:20)

• Create a test dashboard to compare updates with four times per day data (42:40)

• Organize post retainer billables meeting including certain team members and possibly have Shane update Tipgen log financial production lambda accordingly (43:26, 43.39)

Outline Chapter 1: Financial Analysis and Reporting (02:27 - 12:47)

• 02:27: Discussion on reconstructing invoices and closing the month's financial tasks.

• 04:49: Adjusting costs and formulas in the financial data.

• 07:52: Wrapping up tasks and assigning responsibilities for financial analysis.

• 11:50: Reviewing benchmark reports and ensuring accuracy for billing.

Chapter 2: Data Gathering and Analysis (15:05 - 26:41)

• 15:05: Clarification on the benchmark report contents and billing process.

• 16:25: Understanding Cameron's business logic for billing and reporting.

• 19:02: Aligning benchmark reports with billing details for accuracy.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-13 13:48:51

• 24:42: Gathering data for cost analysis and future planning.

Chapter 3: Meeting Scheduling and Task Management (29:25 - 44:49)

• 29:25: Planning meetings for cost management discussions and task scoping.

• 35:03: Scheduling meetings for refining search algorithms and data processing.

• 39:02: Coordinating tasks for Lambda upgrades and data automation.

• 44:23: Planning a meeting to clarify billable statuses and revenue discussions.

Shorthand Bullet • 🚀 *Reconstructing Invoices for Financial Changes*

• - *Ryan Vaspra* discussed reconstructing invoices to close the month.

• - Task assigned to *Brian* to fill out the sheet for this process.

• 📊 *Benchmark Report and Dashboard Updates*

• - *Ryan* emphasized the need to ensure the benchmark report reflects correct billables.

• - *Nick* to send lead IDs for adding or removing from the dashboard.

• 📝 *Strategy Alignment and Feasibility*

• - *Ryan* and *Nick* discussed aligning on strategy for data validation.

• - Feasibility of new search algorithm emphasized by *James*.

• 📅 *Upcoming Meetings and Reviews*

• - Meeting set with *Cameron* for cost management discussions.

• - Scheduled meetings for data review and updates with *James and Ryan*.

• 💡 *Internal Meetings and Data Updates*

• - Discussion on setting up internal meetings for data access.

• - Plans to update dashboard with test data for comparison.

• 📉 *Post Retainer Billables Meeting*

• - *Ryan* organizing a meeting on post-retainer billables for clarity on billing.

• - *Nick* invited to ensure understanding of billable statuses.

• 🔧 *Challenges Resolution*

• - *Ryan* attempted to address challenges by organizing multiple meetings.

• - Focus on revenue discussions to resolve outstanding issues.

Gist • Meeting covered personal health updates, financial discussions, database changes, and post-retainer billables. Emphasized clear cost projections and operational efficiency.

Bullet Gist • 💼 Operational and Financial Matters: Discussions on personal health, aging concerns, data analysis, and cost considerations.

• 📊 Database Changes: Discussion on document processing stages, internal meetings, and system enhancements.

• 💸 Financial Focus: Addressing billing discrepancies, revenue matters, and commission rates.

• 🔍 Data Refinement: Efforts to refine data extraction processes and improve reporting accuracy.

• 📈 Strategic Decision-Making: Planning future meetings for lambda upgrades and driving operational efficiency.

Short Summary • The meeting entailed a wide array of topics including personal health updates shared by Brian Hirst, financial discussions led by Ryan Vaspra, database changes, and post-retainer billables. The focus was on clear cost projections, refining data extraction processes, and enhancing operational efficiency. Efforts were made to address billing discrepancies, improve communication, and drive strategic decision-making within the team structure.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-13 15:13:29

Title: Outstanding invoices Date: Mon May 13 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: andy@shield-legal.com, ryan@brandlytics.io, steve@gaclawyer.com, jeff@gaclawyer.com, andy@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* discussed website management and SEO concerns with *Jeff*. He emphasized the need for regular meetings to align optimization efforts with business operations, suggesting involving Adrian and Andy in technical discussions. Ryan detailed tracking methods for customer leads through call tracking systems and spreadsheet reports. He proposed setting up monthly meetings to review performance metrics and payment schedules while ensuring proper routing of leads from various online platforms like Google Maps. The focus was on improving visibility into paid criminal leads versus organic ones generated through the website.

• Plans were made to include additional attorneys in future communications related to financial matters and upcoming meetings. *Ryan assured Jeff of scheduling payment plans considering cash flow constraints, confirming details of bank account changes for invoice payments. They agreed on communication protocols before making any financial transactions. In conclusion, Ryan thanked Jeff* for his cooperation in organizing the forthcoming email communication about monthly meetings and payment arrangements while expressing gratitude for their discussion during this call.

Action Items • *Ryan Vaspra*

• Set up monthly meetings to discuss website optimization and management (04:39)

• Coordinate with Adrian, Andy, and the team for technical tasks (06:02)

• Schedule a meeting with Adrian and Andy to review tracking systems (07:29)

• Reach out to Steve about adding other attorneys to the list (08:00)

• Have Adrian send an email to arrange a monthly meeting for the team (08:12)

Outline Chapter 1: Website Management Review and Strategy (03:23 - 06:02)

• - 03:24: Discussion on the lack of meetings regarding website management and optimization.

• - 04:26: Highlighting the services included in the monthly payment for website management.

• - 05:52: Emphasizing the need for regular meetings to align website optimization with business operations.

Chapter 2: Tracking and Monitoring Leads (06:51 - 07:22)

• - 06:51: Explanation of how leads are tracked using a call tracking system.

• - 07:19: Offer to provide a detailed spreadsheet of lead tracking for review.

Chapter 3: Planning Monthly Meetings and Payment Schedule (07:38 - 08:39)

• - 07:38: Agreement to set up monthly meetings to discuss website progress and strategies.

• - 08:28: Scheduling out payments to catch up on outstanding invoices.

Chapter 4: Financial Updates and Payment Confirmation (08:40 - 09:03)

• - 08:40: Reminder to use the newer bank account for payments.

• - 08:57: Assurance of confirming payments before processing.

• - 09:00: Mention of involving the finance team in payment arrangements.

Chapter 5: Follow-Up and Next Steps (09:04 - 09:09)

• - 09:04: Appreciation for coordinating the email for the upcoming monthly meeting.

• - 09:07: Gratitude expressed for the assistance provided.

• - 09:09: Closing remarks wishing a great day.

Chapter 6: Return Call and Upcoming Availability (10:42 - 11:25)

• - 10:42: Jeff's return call reminder and expected availability.

• - 11:25: Mention of stepping away briefly.

• Note: This outline focuses on key decisions and actions related to website management, lead tracking, financial updates, and upcoming meetings, excluding non-essential details.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-13 15:13:29

Shorthand Bullet • 📊 *Website Management* and Optimization**

• - *Steve's concern about lack of meetings to discuss website changes and optimization*

• - **Monthly meetings proposed to ensure alignment with business operations

• - *Tracking of website leads and call tracking system discussed*

• 📅 *Monthly Meetings*

• - *Proposal to set up monthly meetings with *Adrian, Andy, and Steve**

• - *Adrian to send an email to coordinate the monthly meetings*

• 💵 *Payment Plan*

• - *Plan to schedule payments to catch up on outstanding invoices*

• - *Confirmation required for using the newer *UBS bank account for payments**

• 📧 *Communication*

• - *Adrian to send an email to coordinate meetings and payment details*

• - *Brian, the finance guy, to be kept in the loop regarding payments*

Gist • Discussion on website management, SEO, and financial matters with a focus on optimizing leads. Regular meetings planned to align efforts and review metrics. Involvement of Adrian and Andy in technical discussions suggested.

Bullet Gist • ⚙️ Website Management and SEO: Optimization efforts and metrics review emphasized.

• 💼 Financial Matters: Payment plans and cash flow constraints considered.

• 📈 Performance Metrics: Monthly review meetings proposed.

• 👥 Involvement of Adrian and Andy: Suggested for technical discussions.

Short Summary • The discussion revolved around website management, SEO concerns, and financial matters between Ryan Vaspra and Jeff. Ryan emphasized the importance of aligning optimization efforts with business operations through regular meetings. He proposed involving Adrian and Andy in technical discussions, detailed tracking methods for customer leads, suggested monthly performance review meetings, and highlighted the importance of proper routing of leads from online platforms like Google Maps. Plans were made to include additional attorneys in financial discussions and meetings, ensuring payment plans aligned with cash flow constraints and communication protocols before financial transactions. Ryan thanked Jeff for his cooperation in organizing monthly meetings and payment arrangements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-14 12:41:07

Title: Media Buyer performance Date: Tue May 14 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* discussed LSAs that need reviews in Orlando, Sacramento, and Houston for verification. Instructions were given to the team to fill out the necessary details for these listings promptly. Confirmed budget completion and status updates on Dayton projects. A review of financial details was conducted with mentions of specific amounts allocated and spent. In a detailed conversation with *Lee* Zafra**, restructuring tasks related to lead generation, PDFs, call tracking, metrics, and law ruler responsibilities between team members for efficiency and skill development were considered. The dialogue concluded with plans to optimize team productivity by leveraging individual strengths effectively while addressing potential client issues regarding payment delays.

Action Items • *Ryan Vaspra*

• Send out the review links to our team and just say, guys, when you get it (00:27)

• Can everyone please add a review so that we can. We can get these LSA listings verified? (00:37)

• Double check if they paid me 5000 for Dayton (01:44)

• Send it to the group about Iowa budget details (02:10)

• Inform Adrian that the dashboard is up to date and Dayton is finished (02:16)

• Consider giving tasks related to leads PDF stuff, call tracking, metric stuff down to law ruler stuff from Corbin to someone else (06:32)

Outline Chapter 1: Review of LSA Listings and Team Assignments (00:00 - 01:15)

• 00:04: Discussion on the need for three LSAs to undergo reviews before going live.

• 00:25: Instructions to send out review links to the team for the Orlando, Sacramento, and Houston law firms.

• 01:00: Confirmation of completion of budget and tasks related to LSA listings.

Chapter 2: Financial Assessment and Budget Allocation (01:10 - 02:19)

• 01:45: Review of budget details and confirmation of payment for the Dayton project.

• 02:00: Confirmation of financial transactions with Energetic Solutions and Iowa.

• 02:25: Instructions to update the team on the dashboard and task completion for Dayton.

Chapter 3: Delegation of Tasks and Team Structure (02:50 - 08:39)

• 02:58: Discussion on potentially reallocating tasks from Corbin to optimize team efficiency.

• 07:24: Comparisons of different marketing roles and consideration of task delegation to align with expertise.

• 08:18: Agreement on task redistribution to enhance productivity and skill development within the team.

Shorthand Bullet • 📊 *LSA Reviews*

• - *Three LSAs need reviews for verification: *Orlando, Sacramento, Houston**

• - *Send review links to team for completion*

• - Request team to add reviews in the BCL channel

• - Specifically mention *Orlando* listings** that require attention

• ⏳ *Budget Update*

• - Budget for Dayton completed, showing $2500 spent out of $5000

• - Confirm payment received for Dayton with appropriate team members

• - Mention involvement of *Aaron Longrup* from Energetic Solutions**

• 💡 *Task Delegation*

• - Discuss potential task transfer from Corbin to another team member

• - Consider transferring tasks related to leads, PDFs, call tracking, and metric analysis

• - Emphasize the importance of understanding technical aspects for skill improvement

• 🗣️ *Communication Strategy*

• - Mention challenges faced with Shades of Mass nonprofit arm

• - Highlight potential issues with communication and leadership style

• - Consider reassigning tasks to manage workload effectively

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-14 12:41:07

• Discussion on LSAs in multiple locations, budget completion, financial review, and restructuring tasks for efficiency and skill development.

Bullet Gist • ⚙️ LSA Reviews: LSAs in Orlando, Sacramento, and Houston discussed for verification.

• 💰 Budget Completion: Confirmed completion and status updates on Dayton projects.

• 📊 Financial Review: Detailed conversation on allocated and spent amounts.

• 🔁 Restructuring Tasks: Tasks discussed for efficiency and skill development.

• ⚡ Team Optimization: Plans to optimize productivity and address payment delay issues.

Short Summary • The discussion involved Ryan Vaspra highlighting the need for reviews of LSAs in Orlando, Sacramento, and Houston, while emphasizing prompt completion of necessary details. Updates on budget completion and status of Dayton projects were confirmed. A thorough review of financial details, including specific amounts allocated and spent, took place. Lee Zafra and team members discussed restructuring tasks related to lead generation, PDFs, call tracking, metrics, and law ruler responsibilities to enhance efficiency and skill development. Plans were made to optimize team productivity by leveraging individual strengths effectively and addressing potential client issues regarding payment delays.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-15 13:56:53

Title: LawRuler - SOW Date: Wed May 15 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, nickmcfadden@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Nick McFadden* raised data discrepancies in the flatiron table and bigquery, highlighting a location mix-up affecting dashboard accuracy. *Ryan Vaspra* emphasized validating case type updates through lead IDs for precise data transfer. Plans were made to rebuild bots from a data warehouse perspective to enhance efficiency, reducing reliance on current automations. The team aimed to streamline processes with locked statuses and improved slack alerts.

• Intake templates revisions and milestone progress strategies were discussed. Steps would include an esign statement version and ongoing training to prevent errors in status sequences. Future hires like a sales operations administrator were planned for efficient project management. Areas for improvement in system logs access and automated workflows were identified.

• Discussions moved towards enhancing data integrity, automation efficiency, and optimizing project milestones with clear communication channels. The team planned regular project update meetings to refine processes continually. Future goals included improving automated workflows while ensuring data integrity. Regular meetings aimed to enhance project milestones efficiently.

Action Items • *Nick McFadden*

• Reach out to Shane for the lead id and validate in Law Ruler (01:00)

• Post the document in hashtag tip logistics (01:45)

• Share the law ruler lead ID with Ryan Vaspra (02:09)

• Provide access to system logs for secondary interview dates review (17:15)

• *Ryan Vaspra*

• Add Brandon to weekly or bi-weekly milestone progress meetings (19:24)

• Touch base with Nick Ward on visiting Las Vegas and inform Ryan (19:28)

• Send the esign version of statement of work for execution (18:45)

Outline Chapter 1: Data Transfer and Validation (00:10 - 02:19)

• 00:10: Shane has questions about the flatiron, a table, and BigQuery.

• 01:00: Need the lead ID for data transfer validation.

• 02:09: Request for the law ruler lead ID to proceed with changes.

Chapter 2: Document Sharing and Review (04:25 - 06:13)

• 04:27: Workable Google Word doc shared for review.

• 05:31: Request to read through the document and ensure understanding.

• 06:13: Review of document sections A and B.

Chapter 3: Intake Form Customization and Automation (12:07 - 14:23)

• 12:07: Discussion on building a query for custom fields in intake forms.

• 13:25: Importance of specific fields for slack alerts and automation.

• 14:02: Example of automation process with fields and alerts.

Chapter 4: Milestone Progress and Weekly Meetings (18:34 - 22:38)

• 18:34: Appreciation for the value in the statement of work.

• 19:27: Proposal for weekly or bi-weekly meetings for milestone progress.

• 21:33: Introduction of sales operation administrator candidate.

• 22:13: Plan for ongoing training and configuration to prevent status changes.

Chapter 5: Final Remarks and Conclusion (23:08 - 24:22)

• 23:08: Discussion on inbound numbers for marketing cases.

• 24:14: Conclusion of the conversation and plan to talk later.

Shorthand Bullet • 🔍 *Data Transfer Process*

• - *Ryan Vaspra* discussed building the data transfer process.

• - Lead ID needed for validation in Law Ruler.

• - Request for Law Ruler lead ID from *Nick McFadden*.

• 📊 *Dashboard Update*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-15 13:56:53

• - Plans to build and update the dashboard.

• 📝 *Document Sharing*

• - *Ryan Vaspra* to share Google Word doc in Google Docs for collaboration.

• 🔧 *Improvements Clarification*

• - Discussion on search criteria and improvements in the system.

• - Question raised about searching by contact ID.

• 📋 *Intake Form Structure*

• - Review of intake form structure and sub-forms by *Ryan Vaspra and Nick McFadden*.

• 📑 *Automation Configuration*

• - Automation setup based on form submissions discussed.

• - Fields required for automation processes highlighted.

• 🤖 *Automated Alerts*

• - Explanation on automating Slack alerts based on form submissions.

• - Integration with Zapier for automation.

• 🚀 *Weekly Progress Meetings*

• - Proposal for weekly or bi-weekly meetings for milestone progress.

• - Discussion on automating statuses via intake buttons.

• 👥 *Team Collaboration*

• - Collaboration plans with Tony, Brett, and *Nick McFadden* for milestone tracking.

• - Training for intake agents and managers on system configurations.

• 📞 *Marketing Cases*

• - Inbound numbers for marketing cases noted for tracking.

• 🏢 *New Role*

• - Mention of a new role: Sales Operation Administrator.

• - Coordination for onboarding and training discussed.

Gist • Data discrepancies addressed, automation enhancements planned for efficiency, milestones and project management strategies discussed. Focus on data integrity and process optimization.

Bullet Gist • ⚙️ Automation Enhancements: Plans to rebuild bots for efficiency.

• 📊 Data Integrity Focus: Addressing data discrepancies and system logs access.

• 📈 Process Optimization: Streamlining processes with locked statuses and improved slack alerts.

• 💼 Project Management Strategy: Inclusion of a sales operations administrator for efficient project management.

• 🔍 Continual Improvement: Regular project update meetings for refining processes.

Short Summary • The meeting covered issues like data discrepancies in the flatiron table and bigquery highlighted by Nick McFadden, and the need to validate case type updates by lead IDs as emphasized by Ryan Vaspra. Plans were made to enhance automation efficiency by rebuilding bots from a data warehouse perspective, improve milestone progress with intake template revisions, and strategize for efficient project management with the addition of a sales operations administrator. Discussions also centered on enhancing data integrity, automation efficiency, and optimizing project milestones through clear communication channels, with a focus on regular project update meetings to refine processes continually.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-15 15:58:22

Title: TortIntel.ai Unicourt cost review Date: Wed May 15 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: jamesscott@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Ryan Vaspra* and *James Scott analyzed call center statistics, focusing on API calls and document downloads. They addressed cost breakdowns, call count discrepancies, and billing clarification with Cameron*. Additionally, they discussed the Uniport API update, planning strategies to optimize data retrieval efficiently. Ryan assigned tasks for dashboard cleanup and mobile app enhancements to improve user experience and align with company standards.

• The team also looked into upcoming projects concerning shield legal AWS dashboard completion and transitioning from free studio tools. They emphasized improving graph layouts for better presentation to streamline data visualization procedures within the organization. The meeting underscored efforts to enhance data management practices through meticulous analysis and dashboard optimization. The goal was to align with organizational objectives while efficiently utilizing resources under *Cameron's* oversight.

• Throughout the meeting, the focus remained on enhancing visualizations, formatting, and usability across various dashboards to improve user experience. They highlighted a collective effort to streamline data visualization processes and align with organizational goals. The team emphasized the importance of efficient utilization of resources like APIs and document retrieval systems under *Cameron's* supervision. The meeting highlighted a dedicated approach to improving data management practices for better visualization and usability, aligning with company standards and organizational objectives.

Action Items • *Luke*

• Go through each page of the dashboard and check the titling, formatting of visualizations, table columns, rows, and tooltips (12:03)

• Update tooltip formatting to ensure it is useful and properly sized (36:48)

• *Brian*

• Review each page of the dashboard for embedded markdown titles, formatted graphs or charts/scorecards, and proper table column widths (46:01)

Outline Chapter 1: Data Analysis and Cost Breakdown (00:57 - 10:47)

• 00:57: James and Ryan discuss analyzing data from 54,000 calls for cost breakdown.

• 03:11: James mentions documents associated with cases, one containing 80,000 docs.

• 06:24: Ryan plans to explore incremental costs for downloading all data without API calls.

Chapter 2: Strategic Planning and Research (13:37 - 18:40)

• 13:37: Ryan and James discuss the potential impact of analyzing large amounts of data.

• 16:20: Ryan emphasizes the goal of acquiring data cost-effectively for future applications.

• 18:36: Ryan plans to research legal tech companies and push on corporate formation strategies.

Chapter 3: Dashboard Formatting and Data Presentation (29:40 - 47:47)

• 31:16: Ryan suggests providing summary statistics for tabular data in the mobile app.

• 35:13: Ryan explains embedding titles in dashboards using markdown for cleaner presentation.

• 39:47: Ryan emphasizes formatting tooltips and ensuring proper display of financial data.

• 46:50: Ryan stresses the importance of formatting graphs, charts, and tables for effective data visualization.

Shorthand Bullet • 📊 *Review of API Call Statistics*

• - *Ryan Vaspra* requested statistics on 54,000 calls for discussion with Cameron.

• - Mentioned an API session involving calling x endpoints.

• 🛠️ *Pricing Model Discussion*

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-15 15:58:22

• - *Ryan Vaspra* inquired about the pricing model and its impact on business goals.

• - Referenced the need to hire an app engineer and focus on data acquisition.

• 📱 *Mobile App Usability Testing*

• - *Ryan Vaspra* mentioned testing mobile app usability, highlighting the need for clear and concise data presentation.

• - Discussed the importance of formatting visualizations and tooltips for improved user experience.

• 📝 *Dashboard Formatting Instructions*

• - *Ryan Vaspra* instructed the team to check and format dashboard titles for a cleaner look.

• - Emphasized the significance of properly formatting graphs, tables, and scorecards for better understanding.

• 👥 *Action Items*

• - *Ryan Vaspra* assigned tasks related to formatting and enhancing dashboard elements to ensure consistency and user-friendliness.

• - Encouraged team members to review and refine their respective dashboard components.

Gist • A meeting was held to analyze call center statistics, address cost breakdowns, discuss API updates, and plan dashboard enhancements. The focus was on optimizing data retrieval, improving visualizations, and aligning with organizational goals.

Bullet Gist • ⚙️ Data Analysis and Optimization: Analyzed call center statistics, addressed cost breakdowns, and planned API updates.

• 📊 Dashboard Enhancements: Tasked with dashboard cleanup and mobile app enhancements for better user experience.

• 🔍 Visualizations Improvement: Emphasized improving graph layouts for streamlined data visualization.

• 💡 Efficient Resource Utilization: Focused on utilizing resources effectively under Cameron's oversight.

• 📈 Organizational Alignment: Aimed to align with company standards and objectives for improved data management.

Short Summary • A meeting was conducted to review call center statistics, analyze cost breakdowns, discuss API updates, and plan dashboard enhancements. Ryan Vaspra and James Scott led the discussion on optimizing data retrieval, improving visualizations, and aligning with organizational objectives. Tasks were assigned for dashboard cleanup and mobile app enhancements to enhance user experience. The team emphasized the importance of efficient data management practices and aligning with company standards. They also discussed upcoming projects related to dashboard completion and transitioning from free studio tools, focusing on improving graph layouts for better data presentation and visualization.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-15 18:04:01

Title: Post Retainer Billables meeting Date: Wed May 15 2024 18:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, alan@tortintakeprofessionals.com, luke@shield-legal.com, tony@tortintakeprofessionals.com, luke@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting began with *Ryan Vaspra updating Luke Fontaine and Nick McFadden* on data management, revenue strategies, and system optimization. Ryan introduced an improved SQL insert statement for invoicing specific services. Streamlining revenue capture and billing accuracy were key topics. Discussions progressed to structuring data in Bigquery for enhanced analytics and performance reporting. Integration of data pipelines for real-time financial insights was emphasized.

• The team explored transitioning legacy programs to modern frameworks while ensuring clear categorization of case types and financial tracking enhancements. Implementing user and case type level overrides for improved financial tracking was discussed. The focus remained on streamlining processes, improving data accuracy, and optimizing revenue generation. Dedication to operational efficiency through leveraging technology solutions like Bigquery was highlighted. The commitment to efficient data handling and accurate billing aligned with service offerings was underscored.

• Conclusively, the collaborative efforts showcased a commitment to optimizing operations and leveraging technology efficiently. Utilizing Bigquery for efficient data management and accurate billing mechanisms was emphasized. The dedication to improving operational efficiencies across departments was evident throughout the meeting. The team's approach aimed at enhancing data accuracy and financial tracking within their operations, signaling a commitment to driving efficiency and effectiveness.

Action Items • *Ryan Vaspra*

• Send a sheet of all perfect posture data services in one column and the price you charge or will charge the client for each secondary interview billing event (21:26)

• Ensure to send all active case types that are billable but haven't been billed to Ryan for backlogging revenue (12:06)

• Add a column called IO agent commission override as boolean in the table structure in Bigquery (11:00)

Outline Chapter 1: Data Integration and Workflow Improvements (00:30 - 05:37)

• 00:30: Introduction to the new row for shoehorning invoices directly into the system.

• 01:59: Discussion on capturing case review revenue and secondary interview processes.

Chapter 2: Data Cleanup and Integration Efforts (05:38 - 11:27)

• 05:38: Focus on cleaning up data from intake processes and ensuring accuracy.

• 11:17: Exporting data and discussing the structure of the new data warehouse.

Chapter 3: Billing and Commission Strategies (11:27 - 18:44)

• 11:27: Exploring case type billing rates and commission structures.

• 17:45: Clarification on billing and commission rates for different case types.

Chapter 4: Reporting and Performance Metrics (25:50 - 27:00)

• 25:50: Overview of call reports and data analysis tools.

• 26:47: Utilizing tools to generate performance metrics and reports for decision-making.

Shorthand Bullet • 📊 *Secondary Interview Space*

• - *Completion and sending by Ryan Vaspra*

• - Discussion on cleaning up data from intake for finalization

• - Mention of plaintiff fact sheet and questionnaire

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-15 18:04:01

• - Luke Fontaine's involvement in ASA secondary interview billing

• - Making improvements in categorizing and billing for different case types

• 🛠️ *Database Structuring*

• - Creation of table structure in Bigquery by Ryan Vaspra

• - Mention of key fields like case type, billable rate, and campaign types

• - Adding category points for future reference in billing

• 📑 *Data Analysis and Reporting*

• - Utilization of Bigquery for analytics and reporting

• - Discussion on structured and unstructured data

• - Importance of accurate data for performance metrics and reporting

• 📈 *Implementation Planning*

• - Planning to create an interface for categorizing case types based on difficulty

• - Milestoning and algorithmic locking of statuses discussed

• - Collaboration with team members like Luke Fontaine and Nick McFadden

• 👋 *Meeting Conclusion*

• - Mutual agreement on discussed points

• - Closure of the meeting by Luke Fontaine and Ryan Vaspra

Gist • Data optimization, revenue strategies, and system enhancement discussed. Focus on Bigquery analytics, real-time insights, and modernizing frameworks. Emphasis on efficiency, accuracy, and leveraging technology for billing.

Bullet Gist • 💡 Strategic Discussions: Focused on data optimization, revenue strategies, and system enhancement.

• 📊 Analytics Emphasis: Highlighted the importance of Bigquery for enhanced analytics and performance reporting.

• ⚙️ Operational Efficiency: Discussions on streamlining processes, improving data accuracy, and optimizing revenue generation.

• 💻 Technology Integration: Emphasized leveraging technology solutions like Bigquery for efficient data management.

• 🔍 Data Accuracy Focus: Commitment to enhancing data accuracy and financial tracking within operations.

Short Summary • The meeting delved into data management, revenue strategies, and system optimization, with Ryan Vaspra updating Luke Fontaine and Nick McFadden. Topics included an improved SQL insert statement for invoicing, Bigquery data structuring for analytics, and real-time financial insights. Transitioning legacy programs, implementing user overrides for financial tracking, and leveraging technology like Bigquery for efficiency were key points. The commitment to operational efficiency, accuracy in billing, and enhancing data accuracy was highlighted throughout the meeting, showcasing a dedication to driving effectiveness and efficiency within the team's operations.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-16 14:45:25

Title: BCL Next Steps Date: Thu May 16 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Adrienne Hester* led the meeting, sharing updates on projects like Drax, SEO launch, FAQ articles, and integrations progress. Key points included pollution impact assessment, hair relaxer integration, SA spec review, truck accidents campaign, slip and fall accidents campaign, and lead automation for Illinois juvenile hall. *Desiree* A* had no further input. The meeting closed promptly at 03:13 after *Adrienne Hester's** remarks.

• *Ryan* was absent due to other commitments, acknowledged by *Adrienne Hester, who efficiently continued with project updates. Discussions focused on project progress reports and related action items. A minor issue about the TV buy back feedback loop was raised but didn't lead to immediate actions. Adrienne Hester kept the session structured despite Ryan*'s absence, ensuring progress was communicated effectively.

Action Items • *Adrienne Hester*

• Reviewing SA spec without udfs required (02:12)

• Truck accidents (02:21)

• Slip and fall accidents (02:27)

• Illinois juvenile hall lead automation and tracking for team Tv buy back (02:33)

Outline Chapter 1: Project Updates and Launch Preparation (00:52 - 03:13)

• 00:52: Desiree notes the attendees and questions if Ryan is present.

• 01:55: Drax is live, SEO launched, and FAQ articles in progress for long tail searches.

• 02:12: Hair relaxer integration submitted to integrations team.

• 02:21: Organic campaigns live for truck accidents and slip and fall accidents.

• 02:33: Illinois juvenile hall lead automation and tracking update provided.

Chapter 2: Team Coordination and Feedback (03:05 - 03:13)

• 03:05: Adrienne concludes updates, prompting no further questions.

• 03:07: Positive feedback from Desiree on updates.

• 03:09: Meeting concludes appreciatively with thank yous and goodbyes.

Shorthand Bullet • 📊 *Drax Launch and SEO Update*

• - Drax is live and tested

• - Launching full SEO

• - *FAQ articles in progress for long tail searches*

• 🚛 *Truck Accidents and Organic Campaign*

• - Organic campaign live for routing to tip intake agents

• - *Focus on slip and fall accidents*

• 📝 *Integration and Reviewing SA Spec*

• - Hair relaxer integration submitted to integrations team

• - Reviewing SA spec without UDFs required

• 📺 *Illinois* Juvenile Hall Lead Automation**

• - Lead automation and tracking for team TV buyback

• - Feedback loop to Cameron and TV buyback team for Spin Crump Law

• 👋 *Meeting Wrap-Up*

• - All updates provided, no further questions

• - Quick and efficient meeting closure

Gist • Adrienne Hester led a meeting discussing various projects and updates, including pollution impact assessment, hair relaxer integration, and campaigns for truck and slip and fall accidents. Desiree A had no input, and Ryan was absent. The meeting closed efficiently at 03:13.

Bullet Gist • ⚡ Lead by Adrienne Hester: Adrienne Hester shared project updates and led the meeting efficiently.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-16 14:45:25

• 🌐 Key Points: Discussions included pollution impact assessment, hair relaxer integration, campaigns for accidents, and lead automation.

• ⏰ Meeting Closure: The meeting closed promptly at 03:13 after Adrienne Hester's updates.

• 🚫 Absences: Desiree A had no input, and Ryan was absent due to other commitments.

Short Summary • Adrienne Hester led the meeting, updating on projects such as Drax, SEO launch, FAQ articles, and integrations progress. Key points covered pollution impact assessment, hair relaxer integration, SA spec review, truck accidents campaign, slip and fall accidents campaign, and lead automation for Illinois juvenile hall. Desiree A did not contribute, while Ryan was absent. Despite Ryan's absence, discussions on project progress and action items proceeded smoothly. Adrienne Hester managed the session effectively, addressing minor issues like the TV buy-back feedback loop without immediate action.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-20 13:19:23

Title: Quick TV Contract Review Date: Mon May 20 2024 13:45:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, ryan@shield-legal.com, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • *Ryan Vaspra and *Brian Hirst discuss the **CTM contract setup, focusing on delivery methods and filters. They work on adding fields for new callers to ensure proper data population. Issues arise with calls from Maryland being attributed to Illinois, leading to troubleshooting discrepancies in lead data integration.

• *Ryan Vaspra and *Brian Hirst** test call tracking metrics using different phone numbers, encountering challenges due to false caller status preventing data transfer. They explore solutions like changing settings or using alternate phone numbers for testing, aiming to resolve issues with duplicate calls and ensure accurate lead tracking.

Action Items • *Ryan Vaspra*

• Have Mark Hines add the call lead fields to those three Illinois juvie hall TV verticals (01:39)

• Test the webhook back over here for my phone call (08:11)

• Call a tracking number and test it (08:17)

• Look at API logs to check why the call did not come over (26:09)

• *Brian Hirst*

• Build the other contracts right now while Ryan tests the webhook (08:09)

• Reset call tracking metrics password (26:59)

Outline Chapter 1: Review of Delivery Methods and Verticals (00:04 - 02:02)

• - Discussion on adding verticals and CTM delivery methods.

• - Request to add call lead fields to Illinois juvie hall TV verticals.

Chapter 2: Troubleshooting Lead Tracking (07:49 - 12:58)

• - Investigation into a lead from Gail Nauman and its tracking issues.

• - Setting up tracking sources and webhooks for lead tracking.

Chapter 3: Quality Assurance and Testing (19:11 - 25:25)

• - Testing leads into Law Ruler for quality assurance.

• - Testing call recording and lead tracking metrics.

Chapter 4: Form Testing and Implementation (30:52 - 31:37)

• - Preparation for testing forms and submission process.

• - Agreement to test forms and follow up on progress.

Shorthand Bullet • 📊 *Reviewing Schedule and Filters*

• - *Brian Hirst* discusses schedules and filters with *Ryan Vaspra*.

• - Filters in vertical fields are identified.

• 🔗 *Webhook Integration*

• - *Ryan Vaspra* mentions building nine webhooks.

• - Check for discrepancies in keys for webhooks in CTM.

• 📞 *Testing Lead Receipts*

• - *Ryan Vaspra* tests sending lead receipts to Law Ruler from Brandlytics.

• - Issues with the lead not showing correctly in Leedspedia are addressed.

• 🔑 *Webhook Configuration*

• - Discussion on configuring webhooks for activities received start.

• - *Ryan Vaspra* verifies keys and callback URLs for accurate integration.

• 📞 *Call Tracking Metrics*

• - *Brian Hirst* plans to reset call tracking metrics.

• - Strategies to handle repeat callers and avoid duplicates are considered.

• 📋 *Form Testing*

• - *Ryan Vaspra* and *Brian Hirst* plan to test and submit forms.

• - *Ryan Vaspra* to be informed when forms are ready for testing.

Gist • The meeting was about discussing CTM contract setup, delivery methods, and filters, testing call tracking metrics, and resolving issues with lead data integration.

Bullet Gist • 📊 Reviewing Schedule and Filters: Brian Hirst discusses schedules and filters with Ryan Vaspra, identifying filters in vertical fields.

• 🔗 Webhook Integration: Ryan Vaspra mentions building nine webhooks and checks for discrepancies in keys for webhooks in CTM.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-20 13:19:23

• 📞 Testing Lead Receipts: Ryan Vaspra tests sending lead receipts to Law Ruler from Brandlytics and addresses issues with the lead not showing correctly in Leedspedia.

• 🔑 Webhook Configuration: Discussion on configuring webhooks for activities received start, with Ryan Vaspra verifying keys and callback URLs for accurate integration.

• 📞 Call Tracking Metrics: Brian Hirst plans to reset call tracking metrics and considers strategies to handle repeat callers and avoid duplicates.

Short Summary • Ryan Vaspra and Brian Hirst delved into the CTM contract setup, focusing on delivery methods and filters, as well as addressing issues with calls from Maryland being inaccurately attributed to Illinois. They tested call tracking metrics using different phone numbers, encountered challenges with false caller status hindering data transfer, and explored solutions like changing settings or using alternate phone numbers for testing to ensure accurate lead tracking. Discussions also revolved around testing lead receipts, configuring webhooks, handling repeat callers, and planning form testing.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-20 16:28:10

Title: Shield <> Sonobi Weekly Date: Mon May 20 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@themedialab.agency, cameron@shield-legal.com, cschwarz@sonobi.com, swilcox@sonobi.com, kristopher@shield-legal.com, tony@tortintakeprofessionals.com, ryan@brandlytics.io, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on discussing the current campaigns and budget allocations, particularly for Illinois and other markets. Attendees like *Steve Wilcox, Craig Schwarz, and Kristopher Standley* reviewed the progress of campaigns, identified issues with data discrepancies, and planned strategies for optimization and future scaling based on market performance.

• Key points included clarifying budget allocations per law firm in different markets, addressing data discrepancies in tracking conversions, discussing optimization strategies based on campaign performance, and planning for upcoming holidays' impact on call center operations.

Action Items • *Steve Wilcox*

• Validate a few things (17:37)

• Track down the form submits tied to seeing the ad (23:36)

Outline Chapter 1: Campaign Expansion Strategy (00:00 - 02:38)

• 00:00: Initial discussion on expanding current campaigns and utilizing learnings.

• 01:32: Importance of gaining law firm approvals for current campaigns.

• 02:38: Recommendation to launch campaigns when creative and targeting are ready.

Chapter 2: Campaign Execution and Budgeting (04:12 - 08:07)

• 04:12: Discussion on starting campaigns with allocated budgets for each firm.

• 05:16: Focus on pacing and running campaigns at a set weekly budget.

• 08:07: Flexibility to shift budgets based on campaign timing.

Chapter 3: Data Analysis and Lead Generation (13:13 - 16:23)

• 13:13: Acknowledgment of helpful data insights for lead generation.

• 16:23: Emphasis on utilizing data effectively for campaign optimization.

Chapter 4: Lead Tracking and Optimization (18:01 - 23:10)

• 18:01: Updates on impressions delivered and changes made for optimization.

• 20:53: Coordination on monitoring leads and optimizing for future campaigns.

Chapter 5: Reporting and Conversions (22:09 - 25:22)

• 22:09: Reviewing leads, conversions, and the need for optimization in LA.

• 25:22: Wrapping up discussion on call center strategies and next steps.

Shorthand Bullet • 🚀 *Expansion Opportunities*

• - **Steve Wilcox suggests expanding based on learnings from current campaigns.

• - Focus on getting law firm approvals for current campaigns.

• 📊 *Data Analysis and Utilization*

• - Discussion on using data effectively from different sources.

• - Clarification on IP addresses and data sets.

• 🔄 *Campaign Launch Decision*

• - **Consider launching campaigns if creative and targeting are ready.

• - Craig Schwarz mentions the need for approval and potential edits before launching.

• 📈 *Scaling Strategies*

• - Aim to sync and dial up operations for adding more markets.

• - Plan to scale operations for market expansion.

Gist • The meeting centered on campaign progress, budget allocations, data discrepancies, and scaling strategies for different markets.

Bullet Gist • 🚀 Expansion Opportunities: Steve Wilcox suggests expanding based on current campaign insights.

• 📊 Data Analysis and Utilization: Discussion on effective data utilization from various sources.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-20 16:28:10

• 🔄 Campaign Launch Decision: Consideration for launching campaigns with prepared creative and targeting.

• 📈 Scaling Strategies: Planning to sync and scale operations for market expansion.

Short Summary • The meeting focused on reviewing campaign progress and budget allocations, addressing data discrepancies, planning optimization strategies, and discussing scaling opportunities for market expansion. Attendees like Steve Wilcox, Craig Schwarz, and Kristopher Standley discussed expanding based on current campaign learnings, clarifying budget allocations per law firm, addressing data discrepancies, and planning for scaling operations. Key points included data analysis, campaign launch decisions, and strategies for scaling operations.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-21 12:37:44

Title: BLX Media Buying Date: Tue May 21 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, lee@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • Ryan Vaspra discussed various issues and challenges related to email platforms, communication with support teams, and Salesforce integration. He emphasized the importance of problem-solving skills and effective communication within the team.

• The meeting also involved a detailed review of signed deals across different cases, such as civil rights, medical malpractice, insurance claims, and more. The discussion included updates on lead counts for various categories like employment LSA, personal injury, navy federal credit union, and other legal matters.

Action Items • *Ryan Vaspra*

• Get back with support as soon as you can and say, look, okay, I need to know (01:34)

• Get in touch with Darren McCracken and set up 15 minutes for recommendations on email platform integration (02:29)

• Talk to Salesforce developer about alternative systems and inform the client (04:06)

• Find out what platforms LSA shows up on and when it started appearing on Google Maps (17:24)

• Determine how LSA gets shown or if Google Ads with location extensions get shown (17:24)

Outline Chapter 1: Decision on Email Platform Integration (02:29 - 03:39)

• 02:29: Plan a meeting with Darren McCracken to discuss recommendations for an email platform to integrate with Lidify Salesforce.

• 03:15: Emphasize the importance of aligning politically with Adrian regarding email platform choices.

Chapter 2: Addressing Issues with Sharpspring (03:39 - 05:08)

• 03:39: Plan to address issues with Sharpspring's functionality and support.

• 04:25: Discuss strategies to resolve problems with Sharpspring and avoid negative impacts on the team's reputation.

Chapter 3: Reviewing Sales Deals and Leads (11:00 - 26:16)

• 11:00: Review the number of signed deals, starting with Ben Crump.

• 18:03: Analyze the signed deals and qualified leads data for various sources.

• 23:48: Confirm the number of qualified leads for different categories and ensure accuracy in the data.

Chapter 4: Ensuring Data Accuracy and Completeness (26:41 - 28:45)

• 26:41: Verify and confirm the number of qualified leads for a particular category.

• 28:06: Ensure data correctness and make necessary changes for accuracy.

Chapter 5: Finalizing Data Analysis and Conclusion (31:57 - 32:58)

• 31:57: Finalize the data analysis process and ensure completeness.

• 32:06: Conclude the discussion and express appreciation for everyone's time.

Shorthand Bullet • 🚀 *Action Items for Integration with Email Platform*

• - *Set up 15 minutes with *Darren McCracken to discuss recommendations for email platform integration.

• - Consider using Mailchimp for ad hoc emails if it aligns politically with Adrian and others.

• - Engage with the Salesforce developer on integration efforts.

• 📊 *Review of Qualified Leads*

• - Confirm 14 qualified leads for 'Other LSA'.

• - Verify 4 qualified leads for 'National sex'.

• - Lee Zafra to check the count for qualified leads.

• 🔍 *Clarification on *Google Maps Business Profile**

• - Discuss the Google Maps Business Profile display.

• - Lee Zafra provided insights into the profile.

• 📉 *Dashboard Update*

• - Ensure the accuracy of the signed deals count on the dashboard.

• - Check and correct the total count of qualified leads.

• 📧 *Communication Strategy*

• - Emphasize the importance of clear communication with solutions in discussions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-21 12:37:44

• - Highlight the need for actionable statements in all interactions for effective problem-solving.

Gist • The meeting aimed to discuss issues with email platforms, Salesforce integration, and review signed deals across various legal cases.

Bullet Gist • 🚀 Action Items for Integration with Email Platform: Discussions planned with Darren for email integration and consideration of Mailchimp for ad hoc emails.

• 📊 Review of Qualified Leads: Confirmation of qualified leads counts for various categories like 'Other LSA' and 'National sex'.

• 🔍 Clarification on Google Maps Business Profile: Insights shared on the Google Maps Business Profile display by Lee Zafra.

• 📉 Dashboard Update: Ensuring accuracy in signed deals count on the dashboard and correcting total qualified leads count.

• 📧 Communication Strategy: Emphasis on clear communication and actionable statements for effective problem-solving.

Short Summary • The meeting covered topics such as challenges with email platforms, communication with support teams, Salesforce integration, and a detailed review of signed deals in civil rights, medical malpractice, insurance claims, and more. Action items included setting up discussions for email platform integration and clarifying Google Maps Business Profile. Emphasis was placed on problem-solving skills and effective communication within the team.

Ryan (ryan@themedialab.agency)
2024-05-22 12:07:40

Shield Legal FEIN / EIN Tax ID

Brian Thiessen (https://themedialaboratory.slack.com/team/U069ZMLFFDM)
<p>85-3521502</p>
Slack Conversation
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-23 14:42:31

Title: Lead Gen & CRM Support Call with Dan J from Constant Contact Lead Gen & CRM Support Date: Thu May 23 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: jbankston@dicellolevitt.com, ryan@brandlytics.io, korbin@brandlytics.io, dan.jopling@constantcontact.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • *Dan Jopling* and *Korbin Mantel* guide *+1 512--17* through the process of adjusting email settings on an agency account, focusing on unchecking the email suppression box to target unengaged contacts.

• The call concludes with *Dan Jopling* explaining how the client can manage engagement levels for each email sent, ensuring control over suppressing unengaged recipients. The meeting ends cordially with thanks exchanged among participants.

Action Items • *+1 512--17*

• *Noah*

• Log in to agency account (00:36)

• Share screen for directions (00:54)

• Go to settings, manage clients, email suppression, uncheck the box and save changes (01:34)

Outline Chapter 1: Account Management Setup (00:27 - 02:27)

• 00:27: *Jennifer* logs into the agency account and prepares to make changes.

• 01:15: Account settings are adjusted under agency tools to manage clients effectively.

• 02:01: Email suppression settings are modified to allow for unengaged contacts.

• 02:08: Clarification provided on client's ability to suppress unengaged contacts during email sends.

Chapter 2: Finalizing Account Changes (02:29 - 02:34)

• 02:29: Account setup process is completed with adjustments for future client interactions.

• 02:33: Participants express gratitude for the assistance and conclude the meeting.

Chapter 3: Closing Remarks (07:43)

• 07:43: Final brief exchange and conclusion of the call.

Shorthand Bullet • 🔧 *Client Account Management*

• - *Jennifer* logged into the agency account and navigated to settings.

• - Jennifer accessed email suppression settings under agency tools.

• - *Jennifer* unchecked the email suppression box for *Shallow Levitt* and saved changes.

• 📊 *Email Engagement Settings*

• - *Clients* can now choose to suppress unengaged emails on each send.

• - New checkbox added for unengaged emails alongside low engagement and duplicate sends checkboxes.

• 👋 *Closure*

• - *Dan* and *Korbin* thanked each other and *Jennifer* for their assistance.

• - Participants bid farewell and wished each other a great weekend.

Gist • The meeting focused on adjusting email settings on an agency account to target unengaged contacts and manage engagement levels for each email sent.

Bullet Gist • 🔧 Client Account Management: Jennifer adjusted email settings on the agency account to target unengaged contacts.

• 📊 Email Engagement Settings: Clients can now choose to suppress unengaged emails on each send, with a new checkbox added for unengaged emails.

• 👋 Closure: Participants thanked each other and Jennifer for their assistance, bidding farewell and wishing a great weekend.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-23 14:42:31

• The meeting revolved around Dan Jopling and Korbin Mantel guiding +1 512-*-17 through adjusting email settings on an agency account, with a focus on unchecking the email suppression box to target unengaged contacts. *Jennifer played a key role in logging into the agency account, accessing email suppression settings, and unchecking the suppression box for Shallow Levitt. The discussion highlighted the ability for clients to suppress unengaged emails on each send, with a new checkbox added for unengaged emails. The meeting ended cordially with thanks exchanged among participants and wishes for a great weekend.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-24 10:54:30

Title: Brandlytics Monthly Meeting Date: Fri May 24 2024 11:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, steve@gaclawyer.com, jeff@gaclawyer.com, adrienne@brandlytics.io, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • Adrian and Adrienne Hester discuss website updates, including adding attorneys' bios and changing the site's structure. They plan to feature team members like Norma and focus on issues like social media addiction in content creation.

• The meeting covers details such as upcoming surgery for Steve Giacovino, scheduling a follow-up discussion, adjusting website content categories, and planning social media activities. The conversation emphasizes updating the staging site with proposed changes before going live.

Action Items • *sgacovino*

• Update the staging site with the name "Stephen Giacovino" instead of "Steve" (11:59)

• Review and put up the updated staging site for further development (17:58)

• Send a meeting recap including all past notes and action items to sgacovino (16:32)

• *Adrienne Hester*

• Start social media back up in June (22:21)

Outline Chapter 1: Initial Website Development Discussion (02:06 - 05:03)

• - 02:28: Discussion on highlighting other attorneys on the website for outreach.

• - 03:40: Recap of incorporating immigration into the website header.

• - 05:04: Plans to start by adding lawyers to the website.

Chapter 2: Bio Updates and Video Integration (08:00 - 11:26)

• - 08:00: Update on waiting for a bio from Robert.

• - 09:05: Plans for attorneys to write their own bios for the website.

• - 11:05: Decision to include videos for immigration and other category pages.

Chapter 3: Social Media and Blog Feedback (14:06 - 14:06)

• - 15:44: Discussion on social media addiction and platform algorithms.

• - 16:24: Agreement to send a meeting recap with notes on social media.

Chapter 4: Review and Next Steps (16:42 - 19:06)

• - 16:42: Intention to compile past notes and send a meeting recap.

• - 17:44: Plan to review website updates and make necessary changes.

• - 19:02: Discussion on scheduling the next follow-up meeting.

Chapter 5: Scheduling Follow-Up Meeting (19:12 - 22:27)

• - 19:12: Setting the date for the next meeting in the second week of July.

• - 21:57: Confirmation to talk on the 7th to discuss progress.

• - 22:32: Exchange of closing remarks and conclusion of the call.

Shorthand Bullet • 📊 *Immigration Header*

• - *Action:* Incorporate immigration into the header.

• - *Participants:* Adrienne Hester

• - *Details:* Already implemented in the meeting invite.

• 🛠️ *Website Call to Action*

• - *Action:* Include a call to action at the bottom of each category page.

• - *Participants:* Adrienne Hester, sgacovino

• - *Call to Action:* Email for questions related to specific categories like DUI, reckless driving.

• 💼 *Team Introduction on Website*

• - *Action:* Feature team members on the website.

• - *Participants:* Adrienne Hester, sgacovino

• - *Details:* Bios and presentation style to be provided for attorneys and staff.

• 📅 *Next Meeting*

• - *Action:* Schedule next meeting for the second week of June.

• - *Participants:* Adrienne Hester, sgacovino

• - *Details:* To follow up on the progress and further planning.

Gist • Discussion on website updates, team features, and social media focus.

Bullet Gist • 📊 Immigration Header: Incorporate immigration into the website header.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-24 10:54:31

• 🛠️ Website Call to Action: Add a call to action at the bottom of category pages.

• 💼 Team Introduction on Website: Feature team members with bios and presentation styles.

• 📅 Next Meeting: Schedule a follow-up meeting for the second week of June.

Short Summary • Adrian and Adrienne Hester strategized website enhancements, including attorney bios, restructuring, and content themes like social media addiction. They planned surgery support for Steve Giacovino, scheduled a follow-up meeting for June, and emphasized staging site updates before going live.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-28 13:10:28

Title: Tech Project Status Weekly Date: Tue May 28 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, shane@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting discussed various topics, including the challenges of integrating different systems for marketing and legal compliance. Ryan shared concerns about a costly integration involving Facebook ads and legal advertising laws, highlighting the complexity of the process and his frustration with getting approval. James provided updates on data analysis efforts to determine drug-case correlations using language models.

• Additionally, there were discussions on model training platforms like Vertex AI and GCP, along with plans for dialer system improvements. The team also strategized on training sessions for law ruler implementation and retool usage. Brian was assigned tasks related to interface development and database interactions in line with ongoing projects.

Action Items • *James Scott*

• Set up recurring meetings with Luke (06:58)

• Consider how to spin the information found in case documents (07:36)

• Further refine document analysis for drug mentions (08:33)

• *Nick McFadden*

• Look into Vertex AI and Google's AI platform permissions (21:53)

• Update on dialer integration progress (29:23)

• *Ryan Vaspra*

• Follow up on Lambda acquisition with Shane (27:01)

• Hand over modeling tasks for Shield and Tip to Luke and Brian (27:22)

• Organize training session with Bytecode for Retool application ($200/hr, 4 hours) (31:01)

Outline Chapter 1: Data Management and Analysis Strategy (02:49 - 10:38)

• 02:49: Discussion on management software built for data processing and fees involved.

• 08:01: Incorporating language models for document analysis and understanding context.

• 10:35: Importance of metadata in identifying and categorizing documents for analysis.

Chapter 2: Implementing Large Language Models (13:22 - 17:14)

• 13:22: Utilizing large language models for analyzing a high volume of documents efficiently.

• 14:20: Consideration of categorization systems to enhance document understanding.

• 17:14: Predicting market maturity based on data analysis and closing ratios.

Chapter 3: Data Integration and Proprietary Information (18:00 - 20:31)

• 18:00: Discussing the use of proprietary data and law firm details for forecasting.

• 19:24: Leveraging raw leads data and proprietary benchmarks for forecasting.

• 20:31: Incorporating AI platforms for data analysis and integration processes.

Chapter 4: Model Training and Data Warehouse Integration (26:18 - 27:49)

• 26:18: Model training strategies and data integration with the data warehouse.

• 27:33: Building model views for data analysis and connecting core data structures.

Chapter 5: Operational Planning and Training (29:19 - 32:28)

• 29:19: Planning operational strategies and training processes for effective implementation.

• 31:11: Bytecode training for tool usage and data manipulation for specific users.

• 32:28: Addressing unexpected financial aspects and guiding team members accordingly.

Shorthand Bullet • 📊 *Dashboard Update*

• - *Ryan Vaspra* requested an update from *James Scott* on dashboard progress.

• - Discussion on scheduling recurring meetings with *Luke* for dashboard sessions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-28 13:10:28

• 🔍 *Data Analysis Strategy*

• - *Nick McFadden* suggested using Olama, a large language model, to analyze data.

• - Discussion on using a large language model to categorize documents efficiently.

• 🚀 *Data Categorization*

• - Emphasis on identifying where data originates from, such as medical records or plaintiff fact sheets.

• - Importance of categorizing data to understand the context of each document.

• 💡 *Model Training and Integration*

• - Plans to use the Vertex AI platform for model training and integrating with the data warehouse.

• - Collaboration between team members for successful training and implementation.

• 🔑 *Key Responsibilities*

• - *Ryan Vaspra* outlined responsibilities for team members, including updates to specific individuals and working closely with teammates.

• - Focus on effective communication, collaboration, and training for project success.

Gist • The meeting focused on challenges in integrating marketing and legal systems, data analysis using language models, model training platforms, and team responsibilities for project success.

Bullet Gist • 📊 Dashboard Update: Ryan requested an update on dashboard progress and discussed recurring meetings for dashboard sessions.

• 🔍 Data Analysis Strategy: Nick suggested using Olama for data analysis and categorizing documents efficiently.

• 🚀 Data Categorization: Emphasis on identifying data sources and categorizing for context understanding.

• 💡 Model Training and Integration: Plans to use Vertex AI for model training and collaboration for implementation success.

• 🔑 Key Responsibilities: Ryan outlined team responsibilities focusing on effective communication and collaboration for project success.

Short Summary • The meeting delved into the challenges of integrating marketing and legal systems, with Ryan expressing concerns about costly integrations. James provided updates on data analysis using language models to find drug-case correlations. Discussions included model training platforms like Vertex AI, plans for dialer system improvements, and training sessions for law ruler implementation. Responsibilities were outlined by Ryan for effective communication and collaboration within the team.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-28 13:43:25

Title: Integrations priorities Date: Tue May 28 2024 14:15:00 GMT-0400 (Eastern Daylight Time) Participants: dwight@shield-legal.com, ryan@brandlytics.io, mike@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • Ryan Vaspra, Mike Everhart, and Dwight Thomas discussed integration priorities and upcoming tasks during the meeting. They reviewed progress on projects like Wagstaff testing and form integrations, addressing challenges and timelines for production.

• The conversation also touched on managing Cameron's communication style and expectations, highlighting the need for clear processes to handle requests efficiently. The attendees shared insights on navigating Cameron's approach to work while emphasizing teamwork and effective communication within the team.

Action Items • *Ryan Vaspra*

• Keep an eye on the production for Wagstaff today and tomorrow, then focus on acts stuff (02:57)

• Check if Lead Conduit allows passing lead form values into it to shove over to trusted forms (05:09)

• Follow up with TikTok buying representatives regarding integration possibilities (06:02)

• Communicate regularly about progress in weekly calls (20:33)

• *Mike Everhart*

• Go back to the drawing board on acts integrations, especially after last week's call (01:22)

• Clarify issues with integrating lead forms and discuss potential solutions during the Trusted Form call (07:24)

Outline Chapter 1: Project Integrations and Priorities (00:16 - 03:08)

• 00:16: Initial discussion on project priorities and separating meetings for better focus.

• 01:24: Plans to revisit integration strategies due to new requirements from stakeholders.

• 02:09: Progress update on form integrations and setting up automated connections.

Chapter 2: Client Communication and Lead Conduit (04:09 - 06:28)

• 04:09: Discussion on using Lead Conduit for delivering leads to clients efficiently.

• 05:22: Importance of Lead Conduit in passing lead form values for smoother processes.

Chapter 3: Team Coordination and Project Management (07:14 - 10:47)

• 07:14: Transition of responsibilities within the team for learning and guidance.

• 09:12: Coordination strategies to align with Cameron's communication preferences.

• 10:32: Establishing efficient communication channels and feedback loops for better project management.

Chapter 4: Timelines and Expectations (17:25 - 18:34)

• 17:25: Emphasis on explaining timelines effectively to leaders and partners.

• 18:07: Discussion on aligning project timelines with client expectations.

Chapter 5: Cultural Considerations and Workplace Dynamics (23:04 - 25:58)

• 23:09: Insights on the importance of culture in fast-growing companies.

• 24:19: Observations on team dynamics and communication challenges in different departments.

• 25:58: Conclusion and closing remarks on workplace culture and operational dynamics.

Shorthand Bullet • 📊 *Act Integrations Progress*

• - **Mike Everhart's next steps on the Act integrations after the previous call.

• - Working on form integrations and setting up automated integration.

• - Setting up the first of four different calls for integration.

• - Replication of steps for subsequent integrations with different parameters.

• 🔗 *Upcoming Meetings*

• - Scheduled 12:00 meeting with Trusted Form regarding API.

• - Discussion on Lead Conduit, their version of Zapier, for lead delivery.

• - Planning to explore market strategies related to TikTok.

• 💬 *Communication and Process Management*

• - **Emphasis on clear communication and formal requests with Cameron.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-28 13:43:25

• - Encouragement to follow specific processes and provide detailed information.

• - Delegation of tasks and ownership for effective management.

• - Regular status updates and positive communication with team members.

• 🔧 *Technical Challenges and Solutions*

• - Challenges in communication with Cameron regarding integrations and call center channels.

• - Strategies to address Cameron's communication style and work preferences.

• - Emphasis on utilizing available resources effectively for successful project management.

Gist • The meeting focused on integration priorities, upcoming tasks, challenges with communication, and managing expectations within the team.

Bullet Gist • 📊 Act Integrations Progress: Mike Everhart's next steps on Act integrations, form integrations, and setting up automated integration.

• 🔗 Upcoming Meetings: Scheduled discussions with Trusted Form, Lead Conduit, and market strategies related to TikTok.

• 💬 Communication and Process Management: Emphasis on clear communication, formal requests, delegation of tasks, and regular updates.

• 🔧 Technical Challenges and Solutions: Challenges in communication, strategies for addressing work preferences, and resource utilization.

Short Summary • The meeting centered around discussing integration priorities and upcoming tasks. Mike Everhart outlined next steps for Act integrations, including form integrations and automated setups. They scheduled meetings with Trusted Form and discussed Lead Conduit for lead delivery. Communication and process management, technical challenges, and strategies for addressing Cameron's style were key points, emphasizing clear processes and effective teamwork.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-28 16:39:53

Title: Shield <> Sonobi Weekly Date: Tue May 28 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@shield-legal.com, cschwarz@sonobi.com, swilcox@sonobi.com, kristopher@shield-legal.com, tony@tortintakeprofessionals.com, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting involved discussions between *Kristopher Standley, Steve Wilcox, and Craig Schwarz* regarding the performance of marketing campaigns in Maryland and LA. They reviewed cost per case metrics, identified issues with leads not being tracked properly, and strategized on optimizing media buys for better results.

• They discussed the need to adjust frequency caps at an IP level to target new audiences effectively. The conversation also touched on data analysis challenges, including monitoring unique IP addresses for accurate targeting and avoiding overexposure to the same audience.

• Craig Schwarz discusses the importance of *CTV* incrementality in terms of eyeballs, emphasizing non-repetitive content and conversions. Ryan Vaspra acknowledges the strategy, while Steve Wilcox expresses appreciation for the discussion.

• The meeting concludes with Kristopher Standley confirming his understanding and thanking the team, followed by Craig Schwarz and Steve Wilcox expressing gratitude as well.

Action Items • *Kristopher Standley*

• Follow up on launching Illinois with creative approval (12:52)

• Keep updated on the progress of creating copies for other law firms (12:49)

• *Craig Schwarz*

• Follow up and email updates about continuing LA and Maryland campaigns through the quarter (11:08)

• Investigate missing leads in Looker, particularly from LA calls (15:02)

• *Ryan Vaspra*

• Fix any discrepancies related to IP addresses affecting ad frequency caps (30:43)

• *Steve Wilcox*

• Confirm the implementation of FCAP at an IP level for tracking ad frequency (32:44)

Outline Chapter 1: Initial Planning and Strategy Discussion (00:40 - 11:42)

• 00:40: Meeting begins with a focus on starting the discussion.

• 03:49: Decision to break down tasks into manageable portions for efficiency.

• 06:10: Emphasis on gradual implementation for better results.

• 07:13: Importance of analyzing media mix and leads for effective decision-making.

Chapter 2: Data Analysis and Reporting Procedures (13:29 - 21:34)

• 13:29: Transition to data-related discussions and the importance of data analysis.

• 17:01: Instructions on using call tracking metrics for performance evaluation.

• 21:34: Explanation of tracking form submits and call lead receipts for insights.

Chapter 3: Optimization Strategies and Performance Monitoring (24:11 - 31:54)

• 24:11: Acknowledgment of helpful insights for optimizing strategies.

• 29:30: Discussion on the correlation between different data points for improvement.

• 31:13: Focus on publisher-level optimization and data visualization for analysis.

Shorthand Bullet • 📊 *Performance Review for Baltimore*

• - *Craig Schwarz* highlighted a successful week in Baltimore.

• - *Email to be sent for alignment* on unpacking numbers.

• 📈 *Optimizing Publishers and Frequency*

• - *Optimizing publishers and frequency* was acknowledged as beneficial.

• - *Tapering down* on Thursday and cutting off on Friday was effective.

• 📞 *Tracking Leads and Campaign Performance*

• - *Identified about seven leads* in the data.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-28 16:39:53

• - *Learning optimal frequency* during initial weeks in LA.

• - *Tracking data through Slack channels* for visibility.

• 📧 *Email Follow-Up*

• - *Email follow-up* planned for further discussion points.

• - *Spreadsheet updates in Slack channels* for daily insights.

• 📑 *Data Analysis and Reporting*

• - *Utilizing call tracking metrics* for detailed analysis.

• - *Daily lead receipts* shared in Slack channels.

• 🔍 *Data Filtering and Analysis*

• - *Filtering by first-time caller* and group by contact discussed.

• - *Reviewing call and form lead receipts* for insights.

• 🤝 *Collaborative Efforts*

• - *Collaboration* emphasized to optimize performance.

• - *Prioritizing actions* post-meeting for progress.

Gist • Meeting to discuss marketing campaign performance, issues with tracking leads, and optimizing media buys in Maryland and LA.

Bullet Gist • ⚙️ Marketing Campaign Performance Review: Reviewed cost per case metrics and identified lead tracking issues.

• 🎯 Optimizing Media Buys: Strategized on optimizing media buys for better results.

• 🔍 Audience Targeting: Discussed adjusting frequency caps at an IP level for effective targeting.

• 📺 CTV Incrementality: Emphasized CTV incrementality for non-repetitive content and conversions.

• 🤝 Gratitude: Participants expressed gratitude as the meeting concluded.

Short Summary • The meeting involved Kristopher Standley, Steve Wilcox, and Craig Schwarz discussing the performance of marketing campaigns in Maryland and LA. They reviewed cost per case metrics, identified lead tracking issues, and strategized on optimizing media buys for better results. The conversation highlighted the need to adjust frequency caps at an IP level for effective audience targeting and emphasized CTV incrementality for non-repetitive content and conversions. Participants expressed gratitude as the meeting concluded.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-29 12:47:46

Title: Media Buyer performance Date: Wed May 29 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting revolved around *Ryan Vaspra* discussing various cases and organizing data related to media buying performance. He clarified mislabeled entries, counted cases accurately, and emphasized the importance of accurate data for client reporting.

• *Lee Zafra* was guided by *Ryan on creating dashboards using Google Looker Studio for specific clients like Dishwitz. Ryan* highlighted the critical fields in dashboard creation, focusing on metrics and user-centric naming conventions.

Action Items • *Ryan Vaspra*

• - Update note for Illinois clergy sex abuse cases (05:35)

• - Check the cases listed under smart advocate for hair relaxer in tip (08:29)

• - Export and dedupe the list of cases from smart advocate for Ben Crump end of May (08:15)

• - Create a dashboard for Dishwitz starting with his data source (14:01)

Outline Chapter 1: Data Analysis and Dashboard Creation (00:58 - 15:54)

• 00:58: Initial discussion on redirecting organic pages for optimization.

• 02:05: Reviewing and updating data related to clergy and juvenile home abuse.

• 06:16: Updating notes and data entries for tracking purposes.

• 09:06: Completion of tasks and making necessary notes for reference.

• 10:33: Introduction to data dashboard creation and the significance of key metrics.

• 15:41: Importance of metric columns and data organization in dashboard creation.

Chapter 2: Dashboard Implementation and Data Visualization (16:02 - 17:54)

• 16:02: Explaining the use of a specific tool, Google Looker Studio, for dashboard creation.

• 17:36: Sharing a dashboard template for editing and customization.

• 17:54: Handing over the task of creating a dashboard and providing guidance for the process.

Shorthand Bullet • 🚀 *Redirecting Organic Pages*

• - *Ryan Vaspra* mentioned redirecting more organic pages over.

• 📊 *Data Management*

• - Mentioned updating status and handling cases.

• - Discussed deduplication and unique count for cases.

• 📅 *Task Assignment*

• - Assigned *Lee* Zafra** to create a dashboard for Dishwitz.

• - Planned to rearrange data in the sheet post-dashboard creation.

• 🛠️ *Dashboard Building Guidance*

• - Provided instructions on building Google Data Studio dashboards.

• - Emphasized the importance of filters and metric columns in dashboard creation.

• - Advised on structuring data for focus litigation solutions dashboard.

• 📝 *Data Naming and User Focus*

• - Emphasized naming data for user understanding.

• - Encouraged considering user perspective when building dashboards.

Gist • The meeting aimed to discuss media buying performance data organization, dashboard creation using Google Looker Studio, and emphasizing user-centric data naming conventions.

Bullet Gist • 🚀 Redirecting Organic Pages: Mention of redirecting more organic pages.

• 📊 Data Management: Updates on status, handling cases, deduplication, and unique case counts.

• 📅 Task Assignment: Assignment of creating a dashboard for Dishwitz and planned data rearrangement.

• 🛠️ Dashboard Building Guidance: Instructions on Google Data Studio dashboard creation, emphasizing filters, metric columns, and structuring data.

• 📝 Data Naming and User Focus: Importance of user-centric data naming and considering user perspective in dashboard creation.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-29 12:47:46

• The meeting focused on *Ryan Vaspra addressing media buying performance data accuracy, clarifying mislabeled entries, and stressing accurate data for client reporting. Lee* Zafra* was directed by *Ryan to create dashboards for specific clients like Dishwitz using **Google Looker Studio, with a focus on critical fields, metrics, and user-centric naming conventions. Discussions included redirecting organic pages, data management updates, task assignments, dashboard building guidance, and emphasizing user-focused data naming and dashboard creation.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-29 13:08:13

Title: Ben Crump SEO Date: Wed May 29 2024 13:45:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • A detailed discussion between *Ryan Vaspra and Korbin Mantel* regarding lead management strategies, contract sorting, and data flow for personal injury cases under Ben Crump SEO.

• The conversation also touched on the delegation of tasks, understanding campaign flows for brandlytics and shield, and the importance of clear communication in handling various responsibilities within the team.

Action Items • *Ryan Vaspra*

• - Go real quick into leads PDA and open (01:35)

• - Find the personal injury contract, share your screen (01:41)

• - Open the personal injury contract in the notes section (02:51)

• - Add "This contract includes URLs from the following practice areas" in internal notes (03:00)

• - Sort vertical column so that Branlytics is first, then scroll down to personal injury and open it (02:20, 03:39)

• - Click save changes in contracts section (04:38)

• - Diagram out Shield lead flow and Brandlytics lead flow (13:58)

Outline Chapter 1: Data Management and Lead Routing (00:00 - 10:28)

• 00:00: Initial discussion on managing leads and organizing data effectively.

• 02:05: Sorting the vertical column to prioritize Branlytics.

• 10:28: Explanation of the lead delivery methods and the importance of uniformity.

Chapter 2: TV Campaigns and Lead Automation (10:28 - 12:20)

• 10:28: Details about TV campaigns and lead automation processes.

• 12:20: Importance of quick access to lead information and efficient routing methods.

Chapter 3: Diagramming Lead Flows (13:02 - 15:20)

• 13:02: Request to diagram lead flows for Shield and Brandlytics.

• 15:20: Emphasis on visualizing lead flows and understanding the processes comprehensively.

Chapter 4: Delegation and Career Growth (14:37 - 16:57)

• 14:37: Encouragement for professional growth through delegation and skill development.

• 16:57: Transition towards delegating tasks and fostering a collaborative work environment.

Chapter 5: Dashboards and Data Analysis (16:50 - 18:46)

• 16:50: Progress update on financials and data analysis tools.

• 18:46: Mention of ongoing data validation and final adjustments for data accuracy.

Shorthand Bullet • 🔍 *Meeting Review with Ryan*

• - *Sorting Contracts:*

• - Sort vertical column, placing Branlytics first.

• - *Internal Notes:*

• - Include "this contract includes URL's from the following practice areas."

• - *Lead Routing:*

• - Ensure uniformity for law ruler and dialer data delivery.

• - *Lead Automation:*

• - Be Brian's second set of eyes for campaign setup.

• - *Forms Management:*

• - Ensure proper handling and organization of forms.

• - *Software Workflow:*

• - Understand the flow from gravity forms to leads PDA.

• - *Campaign Set Up:*

• - Diagram out the lead flow for brandlytics and shield.

• - *Professional Development:*

• - Emphasize career-oriented growth and teamwork.

• - *Data Management:*

• - Continue to fill in and validate data accurately.

Gist • The meeting focused on lead management strategies, contract sorting, and data flow for personal injury cases under Ben Crump SEO.

Bullet Gist • 🔍 Lead Management Strategies: Discussion on sorting contracts, lead routing, lead automation, forms management, and campaign setup.

• 📊 Data Flow and Sorting: Ensuring uniformity in data delivery and proper forms handling.

• 🚀 Professional Development: Emphasis on career growth and teamwork.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-29 13:08:13

• The discussion between Ryan Vaspra and Korbin Mantel revolved around lead management strategies, contract sorting, and data flow for personal injury cases under Ben Crump SEO. Key points included sorting contracts with Brandlytics as a priority, lead routing uniformity, lead automation support, forms management, and campaign setup visualization. Emphasis was also placed on professional development and data accuracy validation.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-30 12:21:25

• 😤 Team Frustrations: Expressions of frustrations within the team dynamics.

Short Summary • The meeting covered a range of topics including database maintenance with updates and error troubleshooting by Ryan, discussions on creating tables for media buyers, updates on Michael and Parsley's issues, expressions of team frustrations, end-of-month tasks delegation, personal updates on Ryan's new house, and plans for future tasks and pricing adjustments. Key points included resolving errors in sales records, creating tables to avoid hard coding, and addressing team issues.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-05-30 13:36:26

Title: SL Lambdas Date: Thu May 30 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, shane@shield-legal.com, luke@shield-legal.com, nicholas@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on code refactoring and improvement, transitioning from ISA to TIP functionality, updating the database for media buyer lookup, dynamically extracting ad platform information, and setting up a follow-up meeting for progress review. Action items include Shane refactoring code and extracting information dynamically, while Ryan is tasked with setting up the next meeting.

Action Items • *Shane Latimer*

• Refactor the reconcile.py file to make it more modular, testable, and readable (00:35)

• Remove ISA functionality from the code and replace it with TIP functionality (01:48)

• Use the new table in the shield legal database to look up media buyers instead of hardcoding them (11:11)

• Extract ad platform information dynamically from Typeform instead of hardcoding it (14:00)

• *Ryan Vaspra*

• Set up another meeting to review progress and provide further guidance (34:52)

Shorthand Bullet • 🔧 *Code Refactoring and Improvement* (00:35 - 01:48)

• Shane to refactor reconcile.py to be more modular, testable, and readable.

• Set up a parallel testing environment for the new code.

• 🛠️ *ISA* to TIP Transition** (01:48 - 11:00)

• Remove ISA functionality from the code and replace it with TIP functionality.

• Ensure the new TIP functionality is thoroughly tested.

• 📊 *Database and Media Buyer Lookup* (11:11 - 12:01)

• Use the new table in the shield legal database to look up media buyers instead of hardcoding them.

• Update the code to reference the new table.

• 🔍 *Dynamic Ad Platform Extraction* (12:02 - 21:17)

• Extract ad platform information dynamically from Typeform instead of hardcoding it.

• Update the Typeform to include ad platform information.

• Modify the code to dynamically extract this information.

• 📅 *Next Steps and Follow-up* (29:47 - 35:51)

• Set up another meeting to review progress and provide further guidance.

• Shane to work on the assigned tasks and reach out if any help is needed.

Gist • The meeting focused on code refactoring, transitioning to TIP functionality, updating the database for media buyer lookup, dynamically extracting ad platform info, and planning a follow-up meeting for progress review.

Bullet Gist • 🔧 Code Refactoring and Improvement: Shane to refactor code for modularity and readability, set up testing environment.

• 🛠️ ISA to TIP Transition: Replace ISA with TIP functionality, ensure thorough testing.

• 📊 Database and Media Buyer Lookup: Use new table for media buyer lookup, update code to reference it.

• 🔍 Dynamic Ad Platform Extraction: Extract ad platform info dynamically, update Typeform and code.

• 📅 Next Steps and Follow-up: Schedule follow-up meeting, Shane to work on assigned tasks.

Short Summary • The meeting primarily centered around improving code quality through refactoring, switching from ISA to TIP functionality, updating the database for media buyer lookup, dynamically extracting ad platform information, and scheduling a follow-up meeting for progress assessment. Shane was tasked with refactoring code and dynamic extraction, while Ryan was assigned to organize the next meeting.

Ryan (ryan@themedialab.agency)
2024-05-30 13:56:31

TIP Credit Card

Cameron Rentch (https://themedialaboratory.slack.com/team/UHMC40W4E)
<p>@Ryan @deleted-U04HFGHL4RW note many credit cards are expiring June 1, here is the TIP expense card updated exp date and ccv. Please make sure you swap out on any services that have auto pay set up today!</p> <p>4197460076334011 06/28 038 Tort Intake Professionals Expense Card TJ Cameron Rentch 89119</p>
Slack Conversation
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-03 13:33:46

Title: Mike catch up Date: Mon Jun 03 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, cameron@shield-legal.com, mike@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting focused on Mike's burnout and desire to focus on IT and Ops. It included discussions on a transition plan and team responsibilities, with Mike suggesting training Dwight to lead the integrations team. Next steps include finalizing the transition plan, detailing Mike's tasks, and emphasizing the importance of redundancy in the team. Action items include detailing tasks, training team members, adding Dwight to tech calls, and scheduling a call to discuss responsibilities.

Action Items • *Mike Everhart*

• Detail out the tasks Mike wants to continue doing and those he wants to transition to other team members (03:12)

• Train Dwight and the integrations team to operate autonomously (05:24)

• Train Hasan and Nick McFadden on pixel integrations (23:25)

• *Ryan Vaspra*

• Add Dwight to the weekly tech project call (17:44)

• Schedule a call with Mike, Ryan, Nick McFadden, and Nick Ward to discuss the transition plan and responsibilities (29:47)

Shorthand Bullet • 🗣️ *Meeting Kickoff and Initial Discussion* (00:09 - 06:28)

• Mike expressed his burnout and desire to focus on IT and Ops.

• Cam and Ryan acknowledged Mike's concerns and discussed the need for a transition plan.

• 🔄 *Transition Plan and Team Responsibilities* (07:50 - 23:43)

• Cam emphasized the need for a clear transition plan.

• Mike proposed training Dwight to lead the integrations team autonomously.

• Ryan suggested adding Dwight to the weekly tech project call.

• 📅 *Next Steps and Scheduling* (23:43 - 32:46)

• Ryan and Cam discussed the need for a meeting to finalize the transition plan.

• Mike agreed to detail his tasks and responsibilities.

• Cam emphasized the importance of redundancy in the team.

Gist • The meeting aimed to address Mike's burnout and transition plan towards focusing on IT and Ops.

Bullet Gist • 🗣️ Meeting Kickoff and Initial Discussion: Mike expressed burnout and interest in IT and Ops; Cam and Ryan discussed transition plan needs.

• 🔄 Transition Plan and Team Responsibilities: Cam stressed clear transition planning; Mike proposed training Dwight to lead integrations team.

• 📅 Next Steps and Scheduling: Ryan and Cam planned a meeting to finalize transition plan; importance of redundancy highlighted.

Short Summary • The meeting centered around addressing Mike's burnout and his desire to shift focus to IT and Ops. Discussions included planning a transition, assigning responsibilities, training team members, and emphasizing redundancy. Mike suggested training Dwight for a leadership role, with actions items set to finalize the transition plan, detail tasks, and discuss responsibilities.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-03 15:02:17

Title: Tech Project Status Weekly Date: Mon Jun 03 2024 14:15:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 45

Overview • The meeting focused on the Tech Project Status, covering casual conversation, technical issues, dashboard and data review, project management and integrations, and AI dashboard development. Key points included discussing weekend activities, addressing Facebook CRM event matching issues, scheduling a Looker review meeting, improving integration with Monday board, and planning the layout for an AI internal feasibility dashboard. Action items assigned to individuals included setting up a meeting to address CRM issues, scheduling review meetings, and preparing detailed layouts for the AI dashboard.

Action Items • *Mike Everhart*

• Set up a meeting with Caleb to ensure Facebook CRM events are correctly configured and forms are passing the lead ID back through Zapier (29:02)

• *Brian Hirst*

• Schedule a Looker review meeting to finalize dashboards (32:45)

• Set up a retool session for the leads PDF contracts pipeline with Google Cloud function and Vivetran (34:26)

• *Luke Fontaine*

• Add Ryan Vaspra to the AI dashboard meetings (01:09:01)

• Prepare a detailed layout for the AI internal feasibility dashboard (01:32:44)

Shorthand Bullet • 🗣️ *Casual Conversation* (01:04 - 06:46)

• Discussion about weekend activities and local spots.

• Brian and Luke shared their camping and golfing experiences.

• 🔧 *Technical Issues and Solutions* (19:37 - 29:02)

• Discussion on Facebook CRM event matching issues.

• Need to ensure forms are passing the lead ID back through Zapier.

• 📊 *Dashboard and Data Review* (32:45 - 34:28)

• Plan to schedule a Looker review meeting.

• Discussion on the leads PDF contracts pipeline with Google Cloud function and Vivetran.

• 🛠️ *Project Management* and Integrations** (51:33 - 01:00:55)

• Discussion on project management tools and processes.

• Need for better integration and use of Monday board.

• 📈 *AI *Dashboard Development** (01:08:56 - 01:36:44)

• Discussion on AI dashboard layout and structure.

• Plan to add Ryan Vaspra to AI dashboard meetings.

• Preparation of detailed layout for AI internal feasibility dashboard.

Gist • The meeting focused on Tech Project Status, discussing casual conversation, technical issues, dashboard and data review, project management, and AI dashboard development.

Bullet Gist • 🗣️ Casual Conversation: Weekend activities and local spots discussed.

• 🔧 Technical Issues and Solutions: Addressed Facebook CRM event matching problems.

• 📊 Dashboard and Data Review: Scheduled a Looker review meeting.

• 🛠️ Project Management and Integrations: Discussed project management tools and Monday board integration.

• 📈 AI Dashboard Development: Reviewed AI dashboard layout and planned for a detailed internal feasibility dashboard.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-03 15:02:17

• The meeting centered around the Tech Project Status, covering various aspects including casual conversation about weekend activities, addressing technical issues like Facebook CRM event matching, planning for a Looker review meeting for the dashboard, improving project management tools and integrations such as Monday board, and detailing the layout for an AI internal feasibility dashboard.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-04 14:38:20

Title: Caleb FBA e-Sign Config Date: Tue Jun 04 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, mike@shield-legal.com, caleb@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting was focused on configuring e-sign feature for Caleb FBA, starting with initial setup discussion where the attack plan was outlined, CRM event configuration, troubleshooting data source connection issues, and final steps and testing. Action items include checking Zapier, updating and testing setup, building campaign and creating funnel, setting up CRM event, connecting data source, and ensuring Facebook lead ID is passed through.

Action Items • *Mike Everhart*

• Check Zapier to ensure the Facebook lead ID is passed through to the leads PDF (16:36)

• Update and test the setup by the end of the day (31:18)

• *Caleb Peters*

• Build a campaign using the CRM event and create the funnel (17:17)

• Set up the CRM event in the business settings and connect the data source (18:48)

• Send account ID, pixel ID, and access token to Mike (23:56)

• Ensure the Facebook lead ID is passed through from the native ad to Zapier (28:30)

Shorthand Bullet • 🛠️ *Initial Setup Discussion* (10:15 - 17:24)

• Ryan apologizes for being late due to end-of-month financials.

• Mike and Caleb were waiting for Ryan to start.

• Ryan outlines the attack plan: check Zapier for the S5 field and ensure the Facebook lead ID is passed through.

• Caleb is to build a campaign using the CRM event and create the funnel.

• 🔧 *CRM Event Configuration* (17:32 - 19:35)

• Mike asks Caleb if the CRM event is created.

• Ryan and Mike guide Caleb through the business settings to set up the CRM event.

• Caleb is instructed to connect the data source in the events manager.

• 📊 *Data Source Connection Issues* (20:45 - 27:52)

• Caleb encounters issues with Facebook while trying to connect the data source.

• Mike and Caleb troubleshoot the problem.

• Caleb sends the account ID, pixel ID, and access token to Mike.

• ✅ *Final Steps and Testing* (27:53 - 32:22)

• Caleb confirms the Facebook lead ID is passed through from the native ad to Zapier.

• Mike and Caleb discuss the specifics of the ad account and campaign types.

• Mike plans to update and test the setup by the end of the day.

• Caleb inquires about the minimum data threshold for the process.

Gist • The meeting focused on configuring e-sign feature for Caleb FBA, including initial setup, CRM event configuration, troubleshooting data source connection issues, and final steps and testing.

Bullet Gist • 🛠️ Initial Setup Discussion: Ryan outlined the attack plan, and Caleb was tasked with building a campaign using the CRM event and creating the funnel.

• 🔧 CRM Event Configuration: Mike guided Caleb through setting up the CRM event and connecting the data source.

• 📊 Data Source Connection Issues: Caleb faced issues connecting the data source with Facebook, and troubleshooting was done.

• ✅ Final Steps and Testing: Final steps involved confirming the Facebook lead ID passing through, discussing ad account specifics, and planning setup testing.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-04 14:38:20

• The meeting centered around configuring the e-sign feature for Caleb FBA. It began with an initial setup discussion where the attack plan was outlined, followed by CRM event configuration, troubleshooting data source connection issues, and final steps and testing. Action items included checking Zapier, updating and testing setup, building a campaign, creating a funnel, setting up CRM events, connecting data sources, and ensuring the Facebook lead ID is passed through.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-04 15:25:16

Title: GCP / Looker sync Date: Tue Jun 04 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, lawrencejordan@google.com, nickmcfadden@tortintakeprofessionals.com, google.com_726f6f6d5f75735f73666f5f7370655f355f356d33@resource.calendar.google.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on synchronizing GCP and Looker, with discussions on legal concerns, documentation, and internal/external communication. Key points included the frustration with legal requirements, the need for specific legal assurances, and the involvement of senior personnel from Google. Action items include providing Google Cloud security information, addressing legal questions, and strategizing before sending information to the relevant stakeholders.

Action Items • *Lorenzo Jordan*

• Provide a one-sheeter or links on Google Cloud security and clarify that Google does not use client data for training its own algorithms (02:00)

• Check internally for resources to address legal questions regarding Google Cloud's data usage and AI components (09:17)

• *Nick McFadden*

• Send an email to Lorenzo Jordan detailing the specific information needed regarding Google Cloud, BigQuery, Vertex AI, and Looker (17:22)

• Meet with Ryan Vaspra to strategize before sending the gathered information to Michael Brunette (19:23)

Shorthand Bullet • 🛡️ *Introduction and Context* (00:09 - 03:49)

• Ryan Vaspra and Nick McFadden discuss their background and the purpose of the meeting.

• Ryan explains the relationship between Shield Legal, Tort Intake Professionals, and their staffing services for law firms.

• Nick mentions the need for Google Cloud security documentation and assurances regarding data usage.

• 📜 *Legal Concerns and Documentation* (03:49 - 07:33)

• Nick has provided some documentation but needs more specific legal assurances.

• Ryan and Nick express frustration with the legal requirements and bureaucracy.

• They discuss the need for a legal contact at Google to address their concerns.

• 📞 *Internal and External Communication* (07:35 - 09:40)

• Ryan suggests involving a senior salesperson or business development leader from Google.

• Nick mentions the need for a call with Google legal team to address their concerns.

• Lorenzo agrees to check internally for resources and provide documentation.

• 📧 *Next Steps and *Follow-ups** (17:22 - 19:53)

• Nick will send an email to Lorenzo detailing the specific information needed.

• Ryan and Nick will strategize before sending the gathered information to Michael Brunette.

• Lorenzo will look into internal resources and documentation to address their concerns.

Gist • The meeting aimed to synchronize GCP and Looker, addressing legal concerns, documentation, and communication strategies.

Bullet Gist • 🛡️ Introduction and Context: Discussion on background, Shield Legal, Tort Intake Professionals, and need for Google Cloud security documentation.

• 📜 Legal Concerns and Documentation: Frustration with legal requirements, bureaucracy, and need for specific legal assurances.

• 📞 Internal and External Communication: Suggestion to involve senior Google personnel, call with Google legal team, and internal resource check.

• 📧 Next Steps and Follow-ups: Email detailing information needed, strategizing before sharing with Michael Brunette, and internal resource search.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-04 15:25:16

Short Summary • The meeting centered on aligning GCP and Looker, with a focus on legal requirements and communication plans. Discussions highlighted the frustration with legal demands, the necessity for specific assurances, and the involvement of senior Google personnel. Action items included providing security information, addressing legal queries, and strategizing before sharing data with stakeholders.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-05 16:33:05

Title: Looker Enterprise - SL Financials AWS Date: Wed Jun 05 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • During the Looker Enterprise - SL Financials AWS meeting, the team discussed several key issues and adjustments for dashboard 37, such as centering elements and adjusting graphs, with Brian assigned to address these. They explored the potential use of Looker ML or BigQuery to solve formula and data display problems and planned further meetings for in-depth discussions with Mark and Cameron. Ryan was tasked with adding new pages to the dashboard and refining formulas alongside Luke, who focused on integrating all necessary branches and expenses into the overhead formula. Additionally, personal weekend plans were briefly touched upon. The next steps include further formula testing and setting up another meeting, which Brian will organize. Key action items were assigned to Brian, Ryan, and Luke to ensure continued progress.

Action Items • *Brian Hirst*

• Check the issues with dashboard 37, including centering some elements and adjusting the graph to show the correct conversion rates (01:17)

• Play with the dashboard filters to ensure the correct data is displayed for Illinois juvenile hall abuse (03:35)

• Set up another meeting to continue working on the Looker Enterprise formula and explore potential solutions (01:24:23)

• *Ryan Vaspra*

• Meet with Mark and Cameron to discuss potential changes to the dashboards and take notes (13:19)

• Add three new pages to the dashboard as requested by Mark, formatted like pages 22, 26, and another page (32:11)

• Save the working formula to the dashboard for further testing and adjustments (01:11:07)

• *Luke*

• Work on the formula for Looker Enterprise and determine if Looker ML or BigQuery is the right solution (32:11)

• Work on the overhead formula to ensure it includes all the necessary branches and hard-coded expenses (01:12:07)

Shorthand Bullet • 📊 *Dashboard Issues and Adjustments* (00:02 - 05:50)

• Discussion on dashboard 37 issues, including centering elements and adjusting graphs.

• Brian to check and adjust the dashboard elements and conversion rates.

• Ryan suggests playing with filters to ensure correct data display for Illinois juvenile hall abuse.

• 🔄 *Formula and Data Display* (05:55 - 13:54)

• Ryan and Brian discuss the issues with the current formula and data display.

• Consideration of Looker ML or BigQuery as potential solutions.

• Ryan to meet with Mark and Cameron to discuss dashboard changes.

• 📅 *New Pages and Formula Work* (14:13 - 24:50)

• Ryan to add three new pages to the dashboard as requested by Mark.

• Luke to work on the formula for Looker Enterprise.

• Discussion on whether Looker ML or BigQuery is the right solution.

• :knifeforkplate: *Personal Plans* (25:01 - 27:38)

• Brief discussion on personal plans for the weekend.

• Ryan and Brian talk about dinner plans and favorite foods.

• 🔧 *Formula Adjustments* (27:57 - 32:19)

• Ryan and Luke work on adjusting the formula for Looker Enterprise.

• Discussion on the challenges of using Looker ML and the need for further testing.

• 📈 *Formula Testing and Adjustments* (34:31 - 01:11:31)

• Ryan and Luke continue to test and adjust the formula.

• Discussion on the need to include all necessary branches and expenses in the overhead formula.

• Ryan to save the working formula to the dashboard for further testing.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-05 16:33:05

• 📝 *Final Adjustments and Next Steps* (01:11:31 - 01:29:34)

• Ryan and Luke discuss the final adjustments needed for the formula.

• Plan to set up another meeting to continue working on the formula.

• Brian to schedule the next meeting and prepare for further discussion.

Gist • Meeting focused on addressing issues with dashboard elements, formulas, and data display, with plans for further discussions and testing. Key actions assigned to team members for progress.

Bullet Gist • 📊 Dashboard Issues and Adjustments: Discussed issues with Dashboard 37, focusing on centering elements and adjusting graphs.

• 🔄 Formula and Data Display: Considered Looker ML or BigQuery to solve formula and data display issues.

• 📅 New Pages and Formula Work: Ryan tasked with adding new pages, Luke focused on formula integration for Looker Enterprise.

• :knifeforkplate: Personal Plans: Brief discussion on weekend plans and dinner arrangements.

• 🔧 Formula Adjustments: Worked on adjusting formulas and discussed challenges with Looker ML.

Short Summary • The meeting centered around addressing issues with Dashboard 37, including centering elements and adjusting graphs, exploring solutions with Looker ML or BigQuery for formula and data display problems. Brian, Ryan, and Luke were tasked with specific actions such as refining formulas, adding new pages to the dashboard, and integrating branches and expenses into the overhead formula. Personal weekend plans were briefly discussed, and plans for further formula testing and setting up additional meetings were made.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-06 14:55:33

Title: Integrations Date: Thu Jun 06 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, mike@shield-legal.com, cameron@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the "Integrations" meeting, participants discussed various challenges and updates, including frustrations with coding interruptions and inefficiencies in data manipulation within Looker Enterprise dashboards. Ryan committed to granting Looker Enterprise access to Soboleski and training Cameron and Mark. Mike agreed to train Nick McFadden in pixel configuration, who will then train Dwight, Asan, and Shane. Efforts to improve project management processes led Nick McFadden to set up systems in Monday.com, and Nick Ward to schedule a process improvement meeting with Ryan. A major focus was transitioning some of Mike's responsibilities to Nick Ward and Nick McFadden, with Ryan and Nick McFadden supporting the smooth handover.

Action Items • *Ryan Vaspra*

• Grant Soboleski access to Looker Enterprise after confirming his hourly metrics are running (05:00)

• Set up Looker Enterprise access for Shane (06:07)

• Add Mark to Looker Enterprise and train him along with Cameron (06:33)

• Investigate if Gravity Forms can handle conditional logic for processing qualified criteria (21:19)

• *Mike Everhart*

• Train Nick McFadden on pixel configuration setup (15:55)

• Schedule a meeting with Dwight to discuss the transition and new responsibilities (50:47)

• *Nick McFadden*

• Train Dwight, Asan, and Shane on pixel configuration setup (18:58)

• Set up a project management process in Monday.com for integration projects (35:50)

• *Nick Ward*

• Schedule a 30-minute meeting with Ryan Vaspra to discuss process improvements and new data integration (32:01)

Shorthand Bullet • 💼 *General Updates and Challenges* (00:23 - 04:22)

• Discussion on the challenges of coding and interruptions in the office.

• Ryan shared frustrations with Looker Enterprise and data manipulation issues.

• Nick and Ryan discussed the inefficiencies of doing data manipulation inside dashboards.

• 📊 *Looker Enterprise* Access** (05:00 - 07:38)

• Ryan to grant Soboleski access to Looker Enterprise after confirming hourly metrics.

• Discussion on setting up Looker Enterprise access for Shane and Mark.

• Ryan to train Cameron and Mark on Looker Enterprise.

• 🔧 *Pixel Configuration and Integrations* (15:55 - 21:19)

• Mike to train Nick McFadden on pixel configuration setup.

• Nick McFadden to train Dwight, Asan, and Shane on pixel configuration.

• Discussion on the importance of quick pixel setup for media campaigns.

• Mark Hine handles pixel fixing and landing page setup.

• 📅 *Project Management* and Process Improvements** (32:01 - 39:52)

• Nick McFadden to set up a project management process in Monday.com.

• Discussion on improving integration processes and reducing delays.

• Nick Ward to schedule a meeting with Ryan to discuss process improvements.

• Ryan to assist Nick Ward with dashboards and process improvements.

• 📞 *Team Management* and Transition** (48:14 - 53:19)

• Discussion on transitioning some of Mike's responsibilities to Nick Ward and Nick McFadden.

• Mike to have a call with Dwight to explain the transition and new responsibilities.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-06 14:55:33

• Emphasis on the importance of managing integrations efficiently.

• Ryan and Nick McFadden to support the transition and ensure smooth handover.

Gist • The meeting focused on discussing challenges, updates, and transitions within the team's workflow and responsibilities.

Bullet Gist • 💼 General Updates and Challenges: Challenges of coding interruptions and data manipulation inefficiencies discussed.

• 📊 Looker Enterprise Access: Actions to grant access, train team members, and discuss metrics.

• 🔧 Pixel Configuration and Integrations: Training sessions on pixel configuration and importance for media campaigns.

• 📅 Project Management and Process Improvements: Setting up project management processes and scheduling process improvement meetings.

• 📞 Team Management and Transition: Transitioning responsibilities and emphasizing efficient integrations.

Short Summary • Participants in the 'Integrations' meeting discussed challenges such as coding interruptions and data manipulation inefficiencies in Looker Enterprise dashboards. Actions included granting access, training team members, setting up project management processes, and transitioning responsibilities. Notable discussions involved pixel configuration, project management improvements, and team management transitions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-07 12:19:19

Title: Integrations Download Date: Fri Jun 07 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nicholas@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the "Integrations Download" meeting, Ryan Vaspra outlined the urgent need for a trusted forms service for legal compliance, driven by investor firm requirements, noting that Active Prospect holds a monopoly on the costly service at $60,000 annually. Nicholas Ward and Ryan discussed passing these costs to clients due to their high expense. Ryan detailed technical setups and ongoing issues with Mark Hines' work in Leadspedia, suggesting a switch from Google Meet due to screen sharing problems. Emphasis was placed on maintaining consistent naming conventions in Leadspedia to avoid data merging issues, with Anthony Sobleski tasked to align vertical names with the Shield system. Ryan reviewed the workflow from client engagement to CRM setup, highlighting the complexity and multiple steps involved. Key action items included Anthony aligning names across systems and Ryan switching to a more reliable screen sharing tool.

Action Items • *Anthony Sobleski*

• Ensure that the vertical names in Leadspedia are consistent with the names used in the Shield system to avoid confusion and manual merging (09:05)

• *Ryan Vaspra*

• Switch to a different screen sharing tool to avoid technical issues experienced with Google Meet (11:08)

Shorthand Bullet • 📋 *Trusted Forms and Legal Compliance* (00:01 - 01:50)

• Ryan Vaspra discussed the need for trusted forms for legal compliance, which is a product requested by one of Cameron's big investor firms.

• The trusted forms capture form data, timestamps, and metadata, storing it for five years to provide proof in case of legal disputes.

• Active Prospect has a monopoly on this service, charging $60,000 per year.

• 💼 *Cost Implications* (01:50 - 02:14)

• Nicholas Ward and Ryan Vaspra discussed the high costs associated with the trusted forms service.

• Cameron is likely to pass these costs down to the clients, potentially raising prices.

• 🔧 *Technical Setup and Issues* (03:09 - 11:08)

• Ryan Vaspra explained the technical setup involving Mark Hines, who builds websites and configures verticals, campaigns, and offers in Leadspedia.

• There were technical difficulties with screen sharing, causing frustration and interruptions.

• Ryan suggested switching to a different screen sharing tool due to ongoing issues with Google Meet.

• 📊 *Data Consistency* (09:05 - 09:54)

• Ryan emphasized the importance of consistent naming conventions in Leadspedia to avoid manual data merging.

• Anthony Sobleski was mentioned as needing to ensure the vertical names are consistent with the Shield system.

• 🔄 *Workflow Overview* (10:37 - 12:16)

• Ryan provided an overview of the workflow from client engagement to setting up in the CRM and Leadspedia.

• The process involves multiple steps, including client commitment, adding opportunities to the CRM, and configuring Leadspedia.

Gist • The meeting focused on the urgent need for a trusted forms service for legal compliance, cost implications, technical setups, and workflow overview in the context of client engagement and CRM setup.

Bullet Gist • 📋 Trusted Forms and Legal Compliance: Urgent need for trusted forms service for legal compliance driven by investor firm requirements.

• 💼 Cost Implications: Discussion on passing high costs of trusted forms service to clients.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-07 12:19:19

• 🔧 Technical Setup and Issues: Challenges with technical setups and screen sharing tool in Leadspedia.

• 📊 Data Consistency: Emphasis on consistent naming conventions in Leadspedia to prevent data merging.

• 🔄 Workflow Overview: Overview of the complex workflow from client engagement to CRM setup.

Short Summary • The meeting centered around addressing the critical requirement for a trusted forms service to ensure legal compliance, driven by investor firm demands and the monopoly held by Active Prospect with a significant annual cost of $60,000. Discussions revolved around the potential cost implications for clients, technical setups and challenges with Leadspedia, the importance of data consistency in Leadspedia to prevent merging issues, and an overview of the workflow from client engagement to CRM setup. Key actions included aligning names across systems and transitioning to a more reliable screen sharing tool.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 12:55:36

Title: Tasha(ActiveProspect)+Shield Legal meeting Date: Mon Jun 10 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nastasia.thomas@activeprospect.com, justin.myers@activeprospect.com, cameron@shield-legal.com, mike@shield-legal.com, activeprospect@assistant.gong.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the meeting between Tasha (ActiveProspect) and Shield Legal, key points included a clarification on certificate retention, where Cameron Rentch confirmed that only certificate numbers need to pass through the system without storing the actual certificates. Nastasia Thomas explained the default retention period is 72 hours, extendable to 90 days, which Cameron agreed to communicate to partner firms. Additionally, changes to the contract were discussed, with Nastasia tasked to push for an amendment to remove the certificate retention clause, and Cameron agreeing to add a retrieval period clause in agreements with law firms. Action items include Nastasia's task to amend the contract and Cameron's task to update the law firms about the 90-day certificate retrieval period.

Action Items • *Nastasia Thomas*

• Push the contract back to the sales director for an amendment to remove the certificate retention clause (06:16)

• *Cameron Rentch*

• Include a clause in agreements with law firms stating that trusted form certificates must be retrieved within 90 days (07:19)

Shorthand Bullet • 📜 *Certificate Retention Clarification* (00:01 - 04:33)

• Cameron Rentch clarified that they only need to pass certificate numbers through their system, not store the certificates.

• Nastasia Thomas explained the retention period: 72 hours by default, extendable to 90 days in some cases.

• Cameron confirmed understanding and agreed to inform partner firms about the 90-day retrieval period.

• ✍️ *Contract Amendment* (06:16 - 07:19)

• Nastasia Thomas will push the contract back to the sales director for an amendment to remove the certificate retention clause.

• Cameron Rentch agreed to include a clause in agreements with law firms about the 90-day retrieval period for certificates.

Gist • The meeting aimed to discuss certificate retention clarification and contract amendments between ActiveProspect and Shield Legal.

Bullet Gist • 📜 Certificate Retention Clarification: Only certificate numbers to pass through system, not store certificates.

• ✍️ Contract Amendment: Push for amendment to remove certificate retention clause.

Short Summary • During the meeting, Cameron Rentch clarified that only certificate numbers need to pass through the system without storing the actual certificates. Nastasia Thomas explained the default retention period of 72 hours, extendable to 90 days, which Cameron agreed to communicate to partner firms. The discussion also involved changes to the contract, with Nastasia tasked to push for an amendment to remove the certificate retention clause and Cameron agreeing to add a retrieval period clause in agreements with law firms.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 13:20:25

Title: Tech Project Status Weekly Date: Mon Jun 10 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the weekly Tech Project Status meeting, Ryan Vaspra kicked off the session by confirming attendance and discussing added agenda items, including the bytecode kickoff. Ryan and Brian require access to Retool and BigQuery to set up an internal user portal. Ryan and Luke need to resolve a custom calculation issue in Looker Enterprise through a scheduled meeting. Ryan is also working on providing Anthony Sablevsky with granular permissions in Looker Enterprise. Nick McFadden highlighted the leads PDF data setup and the necessity to use only advertiser IDs. Nick will review the data fields with Ryan for completeness. Ryan is preparing for a presentation with Cameron and Mark on Looker Enterprise, built on the old AWS database, while Luke plans to create a new model view in DBT for contract ID data. Mike Everhart sought clarification regarding the bytecode meeting, which Ryan provided. Action items were assigned to ensure progress on these tasks.

Action Items • *Ryan Vaspra*

• Get Brian access to Retool and BigQuery for setting up the internal portal (03:44)

• Schedule a meeting with Luke to resolve the Flatirons custom calculation issue in Looker Enterprise (04:29)

• Figure out how to give Anthony Sablevsky access to the Explorer tool in Looker Enterprise without exposing sensitive data (05:29)

• Prepare for the meeting with Cameron and Mark to present Looker Enterprise built on the old AWS database (15:02)

• *Nick McFadden*

• Provide a screenshot of the leads PDF data setup and post it in Slack (09:04)

• Review the leads PDF data fields with Ryan to ensure all necessary fields are included (11:25)

• *Luke Fontaine*

• Create a new model view in DBT for the contract ID data (16:44)

Shorthand Bullet • 📋 *Meeting Kickoff* (00:25 - 03:18)

• Ryan Vaspra initiates the meeting and confirms attendance.

• Discussion on bytecode kickoff and added agenda items.

• 🔧 *Retool and BigQuery Access* (03:37 - 03:44)

• Ryan and Brian need access to Retool and BigQuery.

• Purpose is to set up an internal portal for users.

• 🧮 *Flatirons Custom Calculation Issue* (04:29 - 04:43)

• Ryan and Luke are stuck on a custom calculation in Looker Enterprise.

• Need to schedule a meeting to resolve the issue.

• 🔍 *Looker Enterprise* Permissions** (05:29 - 07:40)

• Ryan is trying to give Anthony Sablevsky access to the Explorer tool.

• Issues with setting up granular permissions in Looker Enterprise.

• 📊 *Leads PDF Data Setup* (08:43 - 10:26)

• Nick McFadden discusses the leads PDF data setup.

• Questions about the difference between buyer and advertiser IDs.

• Ryan and Mike clarify that only advertiser IDs are used.

• 💼 *Leads PDF Data Fields Review* (11:25 - 14:35)

• Nick has gathered all necessary fields for leads PDF data.

• Plan to review the fields with Ryan to ensure completeness.

• 📅 *Upcoming Meeting Preparation* (15:02 - 16:44)

• Ryan is preparing for a meeting with Cameron and Mark.

• Objective is to present Looker Enterprise built on the old AWS database.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 13:20:25

• 🛠️ *DBT Model View Creation* (16:44 - 17:12)

• Plan to create a new model view in DBT for contract ID data.

• Join map view fin details with contract ID data.

• 📞 *Bytecode Meeting Clarification* (17:15 - 19:39)

• Mike Everhart seeks clarification on the upcoming bytecode meeting.

• Ryan explains the purpose and logistics of the meeting.

Gist • The meeting focused on project status updates and action items related to Tech Project tasks.

Bullet Gist • 📋 Meeting Kickoff: Ryan Vaspra confirmed attendance and discussed agenda items.

• 🔧 Retool and BigQuery Access: Ryan and Brian needed access for an internal portal setup.

• 🧮 Flatirons Custom Calculation Issue: Ryan and Luke faced challenges with a custom calculation.

• 🔍 Looker Enterprise Permissions: Ryan worked on granular permissions for Anthony Sablevsky.

• 📊 Leads PDF Data Setup: Nick McFadden discussed setting up leads PDF data.

Short Summary • The Tech Project Status meeting centered on updates and tasks assigned to team members. Ryan Vaspra initiated the session by confirming attendance and discussing agenda items like the bytecode kickoff. Issues addressed included access to Retool and BigQuery for an internal portal setup, resolving a custom calculation problem in Looker Enterprise, granular permissions in Looker Enterprise, leads PDF data setup, and upcoming presentations and model views.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 14:45:00

Title: Shield Legal // Bytecode - Intro / Kick-Off Date: Mon Jun 10 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, shane.koski@bytecode.io, brian@shield-legal.com, jamesscott@shield-legal.com, luke@shield-legal.com, mike@shield-legal.com, nickmcfadden@shield-legal.com, deb.chatterjee@bytecode.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the "Shield Legal // Bytecode - Intro / Kick-Off" meeting, Shane Koski and Brian Hirst introduced themselves and discussed their project locations. Ryan Vaspra explained the plan for setting up Retool apps for Tort Intake Professionals and Shield Legal, and Shane will collaborate with Brian on this task. They discussed user roles, data management with BigQuery and FiveTran, as well as creating a custom table for managing case types and commissions. Shane will create a mockup for the Retool app interface as no wireframes currently exist. They also tackled Looker issues, including formula calculations and user permissions, with a plan to hold a session for solving these problems. Action items include Shane working on the Retool app, setting up user roles, creating the mockup, while Ryan will provide necessary access and schedule the Looker issue session.

Action Items • *Shane Koski*

• Pair up with Brian Hirst to start working on the Retool app for Tort Intake Professionals and Shield Legal (05:09)

• Set up user roles and permissions in Retool for administrators, operations end users, and finance end users (17:27)

• Create a mockup of the Retool app interface for the next session (19:29)

• *Ryan Vaspra*

• Provide access to BigQuery and Retool for Shane Koski (30:38)

• Schedule a session to address Looker issues, including formula calculations and user permissions (32:43)

• Add Shane Koski to the Looker instance for troubleshooting (40:50)

Shorthand Bullet • 👋 *Introductions and Locations* (02:49 - 04:58)

• Shane Koski and Brian Hirst discuss their locations and backgrounds.

• Ryan Vaspra joins the call and confirms the team is ready.

• 🛠️ *Retool App Setup* (05:09 - 07:57)

• Ryan explains the task of setting up Retool apps for Tort Intake Professionals and Shield Legal.

• Shane will pair up with Brian to work on the Retool app.

• Discussion on user roles: administrators, operations end users, and finance end users.

• 📊 *BigQuery and *Data Management** (07:58 - 15:52)

• Ryan explains the data pipeline setup using BigQuery and FiveTran.

• Discussion on the custom table created in BigQuery for managing case types and commissions.

• Shane to expose the table in Retool for updates and inserts.

• 🔧 *Retool Interface and *User Management** (15:53 - 22:03)

• Shane inquires about wireframes for the Retool app interface.

• Ryan confirms no wireframes exist and Shane will create a mockup.

• Discussion on user management and permissions in Retool.

• 🔍 *Looker Issues and Scheduling* (32:43 - 40:06)

• Ryan outlines issues with Looker, including formula calculations and user permissions.

• Shane suggests a simpler method for managing user permissions in Looker.

• Plan to schedule a session to address Looker issues.

• 📅 *Next Steps and Scheduling* (40:07 - 45:14)

• Shane to prepare a mockup for the Retool app.

• Ryan to provide access to BigQuery and Retool for Shane.

• Schedule a session to address Looker issues.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 14:45:00

• Shane to be added to the Looker instance for troubleshooting.

Gist • The meeting focused on introducing the team members, discussing the setup of Retool apps, data management with BigQuery, user roles, creating a custom table, addressing Looker issues, and scheduling next steps.

Bullet Gist • 👋 Introductions and Locations: Shane and Brian introduced themselves and discussed project locations.

• 🛠️ Retool App Setup: Discussion on setting up Retool apps and user roles.

• 📊 BigQuery and Data Management: Explanation on data pipeline setup and custom table creation.

• 🔧 Retool Interface and User Management: Planning for Retool app interface and user permissions.

• 🔍 Looker Issues and Scheduling: Addressing Looker problems and planning a session.

Short Summary • The meeting started with introductions by Shane Koski and Brian Hirst, followed by discussions on setting up Retool apps for Tort Intake Professionals and Shield Legal. Ryan Vaspra explained the data pipeline using BigQuery and FiveTran, with plans for creating a custom table. Shane will work on the Retool app mockup, while addressing Looker issues and scheduling further sessions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 15:47:26

Title: Shield <> Sonobi Date: Mon Jun 10 2024 16:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@shield-legal.com, swilcox@sonobi.com, cschwarz@sonobi.com, kristopher@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting between Shield and Sonobi included a casual conversation about recent personal experiences, followed by a focused discussion on tracking calls in Illinois and overall performance metrics. They reviewed the slow week for cases but noted a positive start in Illinois, analyzing costs per call and conversion rates. Advertising performance was highlighted, especially the high impressions on Pluto TV, and issues with Plex mobile impressions were noted. They talked about a targeted approach for LA and discussed campaign performance, including a review of long calls in Maryland and LA, along with Q3 budgeting and strategies. Future campaigns, like addressing gaming addiction, were considered, emphasizing the coordination between digital and TV broadcast teams. The meeting concluded with encouragement for open communication and outlined next steps and follow-ups, assigning specific action items to Ryan, Kristopher, and Steve.

Action Items • *Ryan*

• Check call tracking metrics more frequently to monitor Illinois calls (01:22)

• *Kristopher Standley*

• Follow up on the longer Maryland call logged recently (05:51)

• Follow up with Bailey Glasser to start in Maryland (09:03)

• Discuss Q3 budgets and campaign strategies with Cameron (09:26)

• Consider new campaigns such as gaming addiction for TV broadcast (11:13)

• *Steve Wilcox*

• Add another group with targeted zips for LA to test (06:58)

Shorthand Bullet • 🎰 *Casual Conversation* (00:01 - 00:49)

• Discussion about recent casino visit and weather conditions.

• Kristopher and Craig share personal experiences.

• 📞 *Illinois* Call Tracking** (00:53 - 01:30)

• Illinois launch discussed.

• Encouraging call tracking metrics.

• Ryan advised to check call tracking metrics more frequently.

• 📉 *Performance Metrics* (01:30 - 05:12)

• Slow week for cases, but good start in Illinois.

• Maryland and LA performance reviewed.

• Cost per call and conversion rates discussed.

• 📊 *Advertising and Impressions* (05:12 - 06:34)

• High impressions on Pluto TV, especially Fox News.

• Completion rates and FCAP discussed.

• Issues with Plex mobile impressions noted.

• 📍 *Targeted Approach for LA* (06:34 - 07:21)

• Discussion on targeted zip codes for LA.

• Steve to add another group with targeted zips for testing.

• 📈 *Campaign Performance and Strategy* (07:21 - 09:26)

• Review of long calls in Maryland and LA.

• Discussion on overall campaign performance.

• Q3 budget and strategy planning.

• 🎯 *Future Campaigns* (09:26 - 12:32)

• Potential new campaigns like gaming addiction discussed.

• Coordination between digital and TV broadcast teams.

• 🤝 *Closing Remarks* (12:32 - 13:49)

• Encouragement to maintain open communication.

• Next steps and follow-ups summarized.

Gist • The meeting discussed recent personal experiences, Illinois call tracking, performance metrics, advertising, targeted LA approach, campaign performance, future campaigns, and concluded with action items.

Bullet Gist • 🎰 Casual Conversation: Recent personal experiences shared by Kristopher and Craig.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-10 15:47:26

• 📞 Illinois Call Tracking: Encouraging call tracking metrics with more frequent checks advised.

• 📉 Performance Metrics: Review of slow cases, positive start in Illinois, cost per call, and conversion rates.

• 📊 Advertising and Impressions: Focus on high impressions on Pluto TV and issues with Plex mobile impressions.

• 📍 Targeted Approach for LA: Discussion on targeted zip codes for LA and testing groups.

Short Summary • The meeting covered a range of topics including recent personal experiences shared by Kristopher and Craig, Illinois call tracking metrics emphasizing the need for more frequent checks advised by Ryan, performance metrics review on slow cases and positive start in Illinois with cost per call and conversion rates analysis, advertising focus on high impressions on Pluto TV and issues with Plex mobile impressions, targeted approach for LA with discussions on campaign performance in Maryland and LA, Q3 budgeting and strategies, potential future campaigns like gaming addiction, and the importance of coordination between digital and TV broadcast teams. The meeting wrapped up with a call for open communication and assigned action items to Ryan, Kristopher, and Steve.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-11 15:11:12

Title: Shield Legal // Bytecode - Retool Enablement Session Date: Tue Jun 11 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, shane.koski@bytecode.io, brian@shield-legal.com, deb.chatterjee@bytecode.io, jamesscott@shield-legal.com, luke@shield-legal.com, mike@shield-legal.com, nickmcfadden@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, shane@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 90

Overview • The meeting titled "Shield Legal // Bytecode - Retool Enablement Session" focused on working with Retool and addressing issues in Looker Enterprise. Participants began with introductions and discussed their weekends, followed by an overview and setup of Retool where Brian Hirst created a service account in Google Cloud for BigQuery. Shane Koski demonstrated Retool's navigation setup, and Brian configured sections for 'Tip Monthly Expenses' and 'User Admin.' The team also discussed using Retool for internal and external applications. Following this, they customized the UI to align with Shield Legal's branding. Ryan Vaspra and Mike Everhart left after confirming the changes. In the query setup segment, Brian Hirst encountered an error while pulling distinct case names from cached data, and Shane Koski offered to troubleshoot it post-meeting. Action items included tasks for Brian to complete the setup and UI adjustments and Shane to troubleshoot the query issue.

Action Items • *Brian Hirst*

• Set up a service account in Google Cloud for Retool with BigQuery Data Viewer and BigQuery User roles (29:01)

• Upload the Shield Legal logo to the Retool app and adjust the color scheme to match the Shield Legal branding (01:07:29)

• Create a query to pull distinct case names from the cached data in Retool (01:24:15)

• *Shane Koski*

• Troubleshoot the issue with the query for pulling distinct case names from the cached data in Retool (01:38:56)

Shorthand Bullet • 👋 *Introductions and Agenda* (02:01 - 09:34)

• Participants greeted each other and discussed their weekends.

• Shane Koski outlined the meeting's purpose: to work on Retool and address issues in Looker Enterprise.

• Ryan Vaspra mentioned he would be a few minutes late.

• 🛠️ *Retool Overview and Initial Setup* (09:34 - 29:44)

• Brian Hirst expressed uncertainty about the Retool setup process.

• Shane Koski explained the need for a service account in Google Cloud for BigQuery.

• Brian Hirst created the service account and assigned the necessary roles.

• The JSON key was generated and uploaded to Retool, successfully connecting BigQuery.

• 🔄 *Navigation and UI Customization* (29:52 - 55:38)

• Shane Koski demonstrated how to set up navigation in Retool using a tabbed container.

• Brian Hirst configured the navigation for 'Tip Monthly Expenses' and 'User Admin' sections.

• The team discussed the possibility of using Retool for both internal and external applications.

• 🎨 *Branding and UI Adjustments* (01:07:29 - 01:17:47)

• Brian Hirst uploaded the Shield Legal logo to the Retool app.

• The team adjusted the color scheme to match Shield Legal's branding.

• Ryan Vaspra and Mike Everhart left the meeting after confirming the changes.

• 🔍 *Query Setup and Troubleshooting* (01:17:47 - 01:40:17)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-11 15:11:12

• Shane Koski explained the importance of using cached data for performance.

• Brian Hirst attempted to create a query to pull distinct case names from the cached data.

• The query returned an error, and Shane Koski offered to troubleshoot it after the meeting.

Gist • The meeting aimed to work with Retool and address Looker Enterprise issues.

Bullet Gist • 👋 Introductions and Agenda: Participants greeted each other, discussed weekends, and outlined the meeting's purpose.

• 🛠️ Retool Overview and Initial Setup: Brian created a service account in Google Cloud for BigQuery, connecting it successfully.

• 🔄 Navigation and UI Customization: Team discussed using Retool for internal and external applications and customized UI.

• 🎨 Branding and UI Adjustments: Logo uploaded, color scheme adjusted to match Shield Legal's branding.

• 🔍 Query Setup and Troubleshooting: Importance of cached data explained; troubleshooting query error discussed.

Short Summary • The meeting focused on using Retool and resolving Looker Enterprise problems. Participants discussed Retool setup, navigation, UI customization, branding alignment, and query troubleshooting. Brian Hirst created a service account in Google Cloud for BigQuery, while Shane Koski demonstrated Retool's features and offered to troubleshoot a query error post-meeting. Action items included setup tasks for Brian and query troubleshooting for Shane.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 12:17:27

Title: BLX SEO Clients Date: Wed Jun 12 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting titled "BLX SEO Clients" focused on several key areas, including keyword research and tracking, dealing with crawl errors, client management and sales, and overall business strategy. Specific actions were assigned, such as Korbin Mantel performing Google search console keywords research and fixing URL crawl errors, adding Markowitz's website to the tracking system, and expanding keyword coverage for Steven Giacomino. Collaborative efforts with Kelly to address crawl errors and tracking fixes in a Google Sheet were also discussed, along with Ryan's efforts to engage new clients, particularly in niche areas like bankruptcy and family law. Ryan is focusing on technical SEO over content SEO, exploring estate planning for new clients, and cautiously approaching personal injury cases due to market competition and long conversion times.

Action Items • *Korbin Mantel*

• Perform Google search console keywords research, export the keywords, and add them to the track words for Crump and Steven Giacomino (02:54)

• Get rid of crawl errors and mark as fixed for URL too long errors (04:25)

• Add Markowitz's website to the keyword tracking system and perform keyword research for his practice areas (06:00)

• Track more keywords for Steven Giacomino and ensure all his practice areas are covered (07:19)

• Ping Lee and inform him to join the call with Ryan (15:03)

Shorthand Bullet • 🔍 *Keyword Research and Tracking* (02:54 - 07:27)

• Perform Google search console keywords research for Crump and Steven Giacomino.

• Add Markowitz's website to the keyword tracking system.

• Track more keywords for Steven Giacomino.

• 🛠️ *Crawl Errors and Fixes* (04:25 - 07:57)

• Get rid of crawl errors and mark as fixed for URL too long errors.

• Collaborate with Kelly to address the errors.

• Track fixes in a Google Sheet and invite Ryan to view it.

• 📊 *Client Management* and Sales** (05:46 - 13:56)

• Ryan is trying to get Markowitz on a call to talk SEO.

• Ryan is talking to a bankruptcy attorney in NYC without a website.

• Ryan is trying to sell Yext licenses and track conversions.

• Ryan is focusing on niche areas like bankruptcy and family law instead of personal injury.

• Ryan met four attorneys at NCAA tournament weekend and is hopeful for new clients.

• 💼 *Business Strategy and Focus* (08:02 - 14:58)

• Ryan prefers technical SEO over content SEO.

• Ryan aims to cover the cost of his team with enough revenue.

• Ryan is exploring estate planning as a potential area for new clients.

• Ryan is cautious about dealing with personal injury cases due to high competition and long conversion times.

Gist • The meeting focused on SEO client management, keyword research, crawl errors, sales strategies, and business direction.

Bullet Gist • 🔍 Keyword Research and Tracking: Performing Google search console keywords research and tracking for clients.

• 🛠️ Crawl Errors and Fixes: Collaborating to address crawl errors and track fixes.

• 📊 Client Management and Sales: Focusing on niche areas for new clients and tracking conversions.

• 💼 Business Strategy and Focus: Emphasizing technical SEO, exploring new client areas, and revenue strategies.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 12:17:27

• The meeting titled 'BLX SEO Clients' concentrated on various areas such as keyword research and tracking, addressing crawl errors, client management and sales, and business strategy. Specific actions were assigned to team members like performing Google search console keywords research, fixing URL crawl errors, and expanding keyword coverage. Ryan emphasized technical SEO over content SEO, explored niche areas for new clients, and strategized to cover team costs with revenue.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 12:27:54

Title: Media Buyer performance Date: Wed Jun 12 2024 13:15:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • During the meeting titled "Media Buyer Performance," Ryan and Lee reviewed updates for Markowitz's LSA accounts, including providing CIDs for DC and New York, and renaming the Google Ads accounts. Lee successfully linked the New York CID to the manager's account, while Ryan added the accounts to the Brandlytics IO Google Ads manager, resolving an initial access issue using his Gmail. Ryan was also tasked with updating billing information for these accounts. It was noted that LSA verification had been pending for four days, prompting Lee to plan a call to LSA support after lunch. Ryan discussed sales strategies for LSA services with a bankruptcy attorney named Singer. Action items included various account updates by Ryan and a follow-up call by Lee.

Action Items • *Ryan Vaspra*

• Update the Google Ads name for Markowitz's LSA accounts (00:43)

• Update the billing information for Markowitz's accounts (01:41)

• Attempt to sell LSA services to Singer, a bankruptcy attorney (05:58)

• *Lee Zafra*

• Link Markowitz's New York CID to the manager's account (00:30)

• Call LSA support to check on the verification status (05:54)

Shorthand Bullet • 🔄 *Account Updates* (00:10 - 00:43)

• Ryan and Lee discussed updating Markowitz's LSA accounts.

• Lee provided the CIDs for DC and New York accounts.

• Ryan updated the Google Ads name for the accounts.

• 🔗 *Linking Accounts* (00:30 - 04:25)

• Lee linked the New York CID to the manager's account.

• Ryan added the accounts to the Brandlytics IO Google Ads account manager.

• Ryan faced issues accepting the account link but resolved it by using his Gmail.

• 💳 *Billing Information* (01:41 - 04:25)

• Ryan was tasked with updating the billing information for Markowitz's accounts.

• Lee confirmed the accounts were visible under Brandlytics Local Services.

• 📞 *Verification and Follow-up* (01:09 - 05:58)

• Lee mentioned that LSA verification was pending for four days.

• Lee planned to call LSA support after lunch to check on the verification status.

• Ryan discussed potential sales strategies for LSA services with Singer, a bankruptcy attorney.

Gist • The meeting focused on updating Markowitz's LSA accounts, linking accounts, resolving access issues, updating billing information, and addressing pending verification for four days.

Bullet Gist • 🔄 Account Updates: Discussed updating Markowitz's LSA accounts and renaming Google Ads accounts.

• 🔗 Linking Accounts: Lee linked the New York CID and Ryan added accounts to Brandlytics IO Google Ads manager.

• 💳 Billing Information: Ryan tasked with updating billing information for Markowitz's accounts.

• 📞 Verification and Follow-up: LSA verification pending for four days, Lee planned a call to LSA support.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 12:27:54

• During the meeting titled 'Media Buyer Performance,' Ryan and Lee discussed updating Markowitz's LSA accounts, providing CIDs for DC and New York, renaming Google Ads accounts, linking accounts, resolving access issues, updating billing information, and addressing pending LSA verification. Lee successfully linked the New York CID to the manager's account, while Ryan added accounts to the Brandlytics IO Google Ads manager and resolved access issues using his Gmail. Ryan was tasked with updating billing information, and Lee planned to call LSA support to check verification status after four days of pending verification. Sales strategies for LSA services were also discussed with Singer, a bankruptcy attorney.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 14:37:47

Title: Singer Law Group Date: Wed Jun 12 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jsinger@jsingerlawgroup.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Singer Law Group meeting, Ryan Vaspra, Andy Rogers, and Jeb Singer discussed their respective companies, with Ryan providing insights into Shield Legal, Tort Intake Professionals, and Brandlytics, contrasting their services with competitors like Broughton. Andy elaborated on intake processes and quality control at Shield Legal, emphasizing their approach to handling mass tort cases. They explored potential collaborations, particularly around investment opportunities in mass tort cases, with Jeb showing an interest in equity structures. Ryan also offered marketing support to Jeff Markowitz for his divorce practice through Google Local Service Ads (LSA). Finally, Ryan and Jeb discussed their personal connections and the possibility of future partnerships, agreeing to set up a follow-up meeting to discuss financial terms and further collaboration. Ryan committed to assisting Jeff with LSA for his practice, while Andy was tasked with exploring collaboration opportunities between Shield Legal and Singer Law Group.

Action Items • *Ryan Vaspra*

• Set up a follow-up meeting with Jeb Singer's finance guy to discuss potential investment opportunities and partnership terms (38:21)

• Assist Jeff Markowitz in trialing Google Local Service Ads (LSA) for his divorce and family law practice (17:36)

• *Andy Rogers*

• Explore potential collaboration opportunities between Shield Legal and Singer Law Group for mass tort cases (12:28)

Shorthand Bullet • 👋 *Introductions and Background* (02:14 - 05:45)

• Ryan Vaspra, Andy Rogers, and Jeb Singer introduce themselves.

• Ryan provides an overview of their companies: Shield Legal, Tort Intake Professionals, and Brandlytics.

• Discussion on the differences between their services and other companies like Broughton.

• 🏢 *Company Operations and Processes* (05:17 - 08:14)

• Andy explains the intake process and quality control measures at Shield Legal.

• Discussion on the differences in lead qualification and disqualification processes.

• Ryan and Andy highlight their unique approach to handling mass tort cases.

• 💼 *Potential Collaboration* (10:10 - 12:28)

• Jeb expresses interest in understanding how he can be helpful.

• Discussion on potential collaboration opportunities between Shield Legal and Singer Law Group.

• Ryan and Jeb discuss the possibility of finding investors for mass tort cases.

• 📈 *Marketing Strategies* (13:01 - 17:36)

• Ryan discusses digital marketing strategies for Jeff Markowitz's divorce practice.

• Explanation of Google Local Service Ads (LSA) and their effectiveness.

• Ryan offers to help Jeff trial Google LSA for his practice.

• 💰 *Investment Opportunities* (20:56 - 22:24)

• Discussion on finding investors for mass tort cases.

• Ryan and Jeb discuss the structure of potential investments and equity.

• Jeb expresses interest in equity for mass tort cases.

• 🤝 *Building Relationships* (29:36 - 38:41)

• Ryan and Jeb discuss their personal connections and shared interests.

• Ryan mentions his plans to move and his busy schedule.

• Discussion on setting up a future meeting to explore partnership opportunities.

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 14:37:47

• The meeting focused on discussions between Ryan Vaspra, Andy Rogers, and Jeb Singer regarding their companies, collaborations, and potential partnerships in mass tort cases and marketing support for Jeff Markowitz.

Bullet Gist • ⚖️ Company Insights: Ryan discussed Shield Legal, Tort Intake Professionals, and Brandlytics services.

• 🔍 Quality Control Focus: Andy highlighted Shield Legal's intake processes and quality control.

• ⭐ Collaboration Opportunities: Exploration of investment opportunities in mass tort cases.

• 💼 Marketing Support Offered: Ryan offered marketing support to Jeff Markowitz through Google LSA.

• 🤝 Partnership Discussions: Discussions on personal connections and potential partnerships.

Short Summary • During the meeting, Ryan Vaspra shared insights on Shield Legal, Tort Intake Professionals, and Brandlytics, contrasting their services with competitors like Broughton. Andy Rogers elaborated on Shield Legal's intake processes and quality control, emphasizing their approach to mass tort cases. The participants explored investment opportunities in mass tort cases, with Jeb Singer showing interest in equity structures. Ryan also offered marketing support to Jeff Markowitz through Google Local Service Ads (LSA). The meeting concluded with discussions on personal connections, potential partnerships, and plans for follow-up meetings to finalize collaboration terms and financial arrangements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 16:11:39

Title: Looker Enterprise // Shield Legal // ByteCode Date: Wed Jun 12 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io, shane.koski@bytecode.io, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • During the Looker Enterprise meeting, initial technical difficulties were addressed before delving into key topics such as permissions and overhead calculations. Shane showcased the current Looker dashboard, emphasizing best practices for LookML and the importance of reusability and durability. Detailed discussions on LookML code organization, including base and refinement view files, were conducted, and custom dimensions and measures were created for overhead and net profit calculations. These calculations were validated and adjusted to resolve discrepancies in data accuracy. The meeting also covered setting up user roles and permissions in Looker, specifically for Shield Legal and TIP, to restrict access to financial data. Future plans were discussed, with Shane committing to push changes to production, while Ryan and Luke will continue to validate calculations and progress project work. Key action items were assigned to Shane and Luke to standardize projects, create necessary calculations, push updates, configure permissions, and validate data accuracy.

Action Items • *Shane Koski*

• Standardize Looker projects and adhere to best practices (05:31)

• Create a custom dimension for overhead and net profit calculations (10:53)

• Commit and push changes to Looker project for Flatirons (49:05)

• Set up user roles and permissions in Looker to restrict access to financial data (56:11)

• *Luke Fontaine*

• Validate the overhead and net profit calculations for accuracy (28:56)

Shorthand Bullet • 🛠️ *Technical Issues and Meeting Start* (00:01 - 01:54)

• Initial technical difficulties with Google Meet

• Discussion on Looker permissions and overhead calculation issues

• 📊 *Looker Dashboard and Best Practices* (01:54 - 05:30)

• Shane shares screen to show current Looker dashboard

• Discussion on best practices for LookML and custom fields

• Importance of reusability and durability in LookML

• 🔧 *LookML Code and *Project Organization** (05:31 - 11:16)

• Shane explains LookML code organization

• Introduction of base and refinement view files

• Discussion on creating custom dimensions and measures

• 📈 *Overhead Calculation and Net Profit* (11:16 - 24:30)

• Ryan provides additional data for overhead calculation

• Shane and Ryan discuss the correct approach for net profit calculation

• Creation of custom dimensions and measures for overhead and net profit

• 🔍 *Validation and Adjustments* (24:31 - 34:55)

• Validation of overhead and net profit calculations

• Ryan and Shane discuss discrepancies in data

• Adjustments made to LookML code for accuracy

• 🔒 *User Roles and Permissions* (50:01 - 01:01:00)

• Discussion on setting up user roles and permissions in Looker

• Creation of model sets for Shield Legal and TIP

• Application of roles to user groups to restrict access to financial data

• 📅 *Future Plans and Next Steps* (01:01:00 - 01:09:20)

• Ryan discusses future plans for client dashboards

• Shane commits to pushing changes to production

• Ryan and Luke to validate calculations and continue project work

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-12 16:11:39

• The meeting focused on addressing technical difficulties, discussing LookML best practices, creating custom calculations, setting up user roles, and planning future project tasks.

Bullet Gist • ⚙️ Technical Challenges Addressed: Initial technical difficulties were resolved at the beginning of the meeting.

• 📊 LookML Best Practices: Shane highlighted the importance of reusability and durability in LookML.

• ⚖️ User Roles and Permissions: Discussions included setting up user roles for Shield Legal and TIP to restrict access to financial data.

• ⏭️ Future Plans: Plans involved pushing changes to production and ongoing validation of calculations by Ryan and Luke.

Short Summary • The meeting started by resolving initial technical challenges and moved on to in-depth discussions on LookML best practices, custom calculations for overhead and net profit, and setting user roles for data access restrictions. Shane showcased the Looker dashboard, emphasizing reusability and durability in LookML. Action items were assigned to standardize projects, configure permissions, and validate data accuracy. Future plans involved pushing changes to production and ongoing validation of calculations by Ryan and Luke.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-13 16:36:04

Title: SL Lambdas Date: Thu Jun 13 2024 17:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, shane@shield-legal.com, nickmcfadden@shield-legal.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting titled "SL Lambdas" covered several key topics, starting with Ryan discussing the challenges of moving into a leadership role and sharing his screen to review new refactored code, which Shane confirmed was running correctly. There were technical difficulties with screen sharing, which Luke and Shane helped resolve, leading to the use of Zoom for recording. The team reviewed the new refactored code for handling performance tips, incomplete calculations, and log file reading from a separate database. Ryan outlined the process for handling referrals in the financial log table, and Luke described the manual assignment of referrals to media buyers, addressing issues with blank entries. Future steps discussed included Shane handling referral cases in the new code and building an external client portal for report access. Action items assigned were for Shane to handle referral cases and meet with Ryan next week, Luke to clean up referral entries, and Ryan to set up a test case for performance logic and discuss the client portal with Cameron.

Action Items • *Shane Latimer*

• Shane to look at the new code and handle the referral cases in the financial log table (25:52)

• Shane to meet with Ryan next week to review progress on the new code implementation (36:18)

• *Luke Fontaine*

• Luke to clean up the extra empty referral entries in the financial log table (14:24)

• *Ryan Vaspra*

• Ryan to set up a test case for the new calculate performance logic using type form data (25:52)

• Ryan to discuss with Cameron about building an external client portal and the necessary steps involved (28:54)

Shorthand Bullet • 💼 *Introduction and Initial Discussion* (00:42 - 02:30)

• Ryan discusses the challenges of transitioning from a developer to a leadership role.

• Ryan shares his screen to review the new refactored code.

• Shane confirms the new code is running correctly.

• 🔧 *Technical Issues and Screen Sharing* (02:30 - 05:20)

• Ryan experiences issues with screen sharing and recording.

• Luke and Shane assist in troubleshooting the screen sharing problems.

• Ryan decides to use Zoom for recording.

• 🗂️ *Review of Refactored Code and Data Handling* (05:20 - 17:59)

• Ryan reviews the new refactored code for 'do not touch tip'.

• Discussion on handling incomplete calculate performance tips.

• Ryan explains the logic for reading the log file from a separate database.

• 🛠️ *Handling Referrals and Financial Logs* (18:14 - 27:00)

• Ryan explains the process of handling referrals in the financial log table.

• Luke manually assigns referrals to media buyers each morning.

• Discussion on issues with blank entries and how to resolve them.

• 📊 *Future Steps and Client Portal Discussion* (27:19 - 36:25)

• Ryan outlines the next steps for Shane to handle referral cases in the new code.

• Discussion on building an external client portal for clients to access reports.

• Ryan emphasizes the importance of making decisions on the dialer and Salesforce implementation.

Gist • The meeting focused on code review, performance tips, and handling referrals in the financial log table.

Bullet Gist • ⚙️ Code Review: Ryan and Shane reviewed new refactored code.

• 💻 Technical Difficulties: Luke and Shane resolved screen sharing issues.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-13 16:36:04

• 🔍 Performance Tips: Discussed handling performance tips and log file reading.

• 📊 Referrals Handling: Outlined process for handling referrals in financial log table.

Short Summary • The meeting titled 'SL Lambdas' covered Ryan discussing challenges in a leadership role, code review of new refactored code, technical difficulties resolved by Luke and Shane, use of Zoom for recording, review of code for performance tips and log file reading from a separate database, process for handling referrals in the financial log table, manual assignment of referrals by Luke, future steps including Shane handling referral cases and building an external client portal, and action items assigned to Shane, Luke, and Ryan for handling referrals and setting up a test case for performance logic.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-13 17:23:23

Title: Shield Client Dashboard Portal MVP Date: Thu Jun 13 2024 17:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, cameron@shield-legal.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The meeting focused on several key areas for the Shield Client Dashboard Portal MVP. Ryan Vaspra and Nick McFadden discussed shifting from hard-coded media buyers to a media buyer lookup, with Nick set to replace the ISA call center lookup and handle contract and revenue tracking via Leadspedia. Nick also suggested migrating financial data to Google Cloud SQL, and Ryan confirmed additional new pipes for Google Cloud. Cameron Rentch outlined the need for a visually appealing client dashboard with essential metrics like campaign summary and revenue, allowing drill-down capabilities. Integration efforts include combining Leadspeedia data with Shield BigQuery and resolving permissions issues. Cameron also proposed a meeting with the TikTok team in London to focus on development and engineering integrations. Additionally, the team discussed taking over API management from Dwight’s team, with Nick to follow up on training for pixel configuration. Action items were assigned to Ryan, Nick, and Shane to ensure progress on these initiatives.

Action Items • *Ryan Vaspra*

• Meet with Nick McFadden to replace the ISA call center lookup and count the signed contracts and get the revenue from Leadspedia (00:00)

• Prepare for a meeting in London with the TikTok team focused on development, engineering integrations, and creatives (33:02)

• *Nick McFadden*

• Build the new pipes for LR inbox, LR intake templates, questions and answers, and LR statuses in Google Cloud (01:28)

• Develop a beta version of the client dashboard with a focus on visual appeal and essential metrics (04:29)

• Integrate Leadspeedia contract pipeline into the Shield BigQuery project (10:49)

• Prepare for a meeting in London with the TikTok team focused on development, engineering integrations, and creatives (33:02)

• Follow up with Mike on training for using pixel configuration and other tools (44:21)

• *Shane Koski*

• Create a template in Retool for external clients to view signups, intake templates, questions, and answers (03:03)

Shorthand Bullet • 💻 *Code and Media Buyer Lookup* (00:00 - 00:57)

• Ryan Vaspra discussed using media buyer lookup instead of hard coding media buyers.

• Nick McFadden to replace the ISA call center lookup and count signed contracts and get revenue from Leadspedia.

• Next steps include meeting with Nick next week and further cleanup components.

• ☁️ *Cloud Migration and New Pipes* (00:57 - 03:03)

• Nick McFadden suggested migrating financial stuff to Google Cloud SQL.

• Ryan Vaspra confirmed new pipes for LR inbox, intake templates, questions, and answers will be in Google Cloud.

• Luke to model linking pipes for dashboard visualization.

• 📊 *Client Dashboard Requirements* (03:03 - 07:28)

• Cameron Rentch emphasized the need for a visually appealing client dashboard.

• Key metrics include campaign summary, spend, signed contracts, and revenue.

• Dashboard should allow drill-down into demographics and financial summaries.

• 🔄 *Integration and Dependencies* (10:49 - 13:45)

• Nick McFadden and Shane Koski to integrate Leadspeedia contract pipeline into Shield BigQuery.

• Ryan and Luke to work on financial summaries and dashboards.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-13 17:23:23

• Dependencies include resolving permissions issues and integrating pipelines.

• ✈️ *TikTok Team Meeting in *London** (33:02 - 35:35)

• Cameron Rentch discussed the need for a meeting in London with the TikTok team.

• Focus on development, engineering integrations, and creatives.

• Proposed dates are July 17-18 or July 24-25.

• 📈 *API and *Integration Management** (41:22 - 47:05)

• Discussion on taking over API management from Dwight and his team.

• Nick McFadden to follow up with Mike on training for pixel configuration.

• Need for regular updates and training sessions to ensure smooth transitions.

Gist • The meeting focused on planning and strategizing key areas for the Shield Client Dashboard Portal MVP.

Bullet Gist • ⚙️ Transition to Media Buyer Lookup: Ryan and Nick discussed moving to a media buyer lookup system.

• 📊 Visual Client Dashboard: Cameron highlighted the need for a visually appealing client dashboard with key metrics.

• 🔗 Integration Efforts: Efforts included merging Leadspeedia data with Shield BigQuery.

• 📈 Revenue Tracking: Nick to handle contract and revenue tracking via Leadspedia.

• 🔄 API Management: Discussion on taking over API management and training for pixel configuration.

Short Summary • The meeting delved into crucial aspects of the Shield Client Dashboard Portal MVP. Ryan Vaspra and Nick McFadden discussed transitioning to a media buyer lookup system, with Nick managing contract and revenue tracking through Leadspedia. Integration efforts included merging Leadspeedia data with Shield BigQuery and addressing permissions issues. Cameron Rentch emphasized the importance of a visually appealing client dashboard with essential metrics like campaign summaries and revenue, proposing a meeting with the TikTok team in London for development collaborations. Action items were assigned to ensure progress on initiatives.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-14 13:53:13

Title: BLX EOM Fin Date: Fri Jun 14 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@accountingdept.net, ryan@brandlytics.io, andy@shield-legal.com, andy@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the BLX EOM Fin meeting, Ryan addressed several key financial topics including the compensation and role of Andy, proposing a possible reallocation of his responsibilities to Adrienne without altering her title. The discomfort around the current credit card approval process was discussed, leading Ryan to instruct that monthly approvals be sought via email. The team reviewed various invoices and Ryan emphasized the importance of follow-ups, particularly with Jeff Dubin regarding an outstanding payment. Financial updates highlighted the need to collect overdue payments to balance the books, with Ryan planning to personally follow up with Jack Avino. Detailed billing strategies were also discussed, with specific instructions given to create a detailed invoice for Corbin Mantell’s services, including a 15% upcharge, for presentation to Cameron. Action items assigned included confirming Andy's situation, sending and forwarding pertinent emails, double-checking accounting details, and calculating Corbin Mantell’s bill.

Action Items • *Ryan Vaspra*

• Ping Andy to confirm his attendance and discuss his compensation structure (00:06)

• *+1 602--81*

• Send an email to Ben for credit card approval for the invoice (01:42)

• Forward the email to Jeff Dubin asking for the first payment and details (04:20)

• Double-check the accounting and update the wire instructions for invoice 158 (07:10)

• Create a tab for BLX email staff and calculate Corbin Mantell's total bill with a 15% upcharge from October 2023 to July 2024 (16:56)

Shorthand Bullet • 💼 *Discussion on *Andy's Compensation and Role** (00:06 - 01:19)

• Ryan discusses Andy's compensation and role, questioning the value of his $70,000 base salary.

• Ryan suggests reallocating responsibilities to Adrienne without changing her title.

• 💳 *Credit Card Approval Process* (01:42 - 02:16)

• Discussion on the discomfort of charging a credit card without explicit approval.

• Ryan instructs to send an email for monthly approval for credit card charges.

• 📧 *Invoice and Payment *Follow-ups** (02:27 - 07:10)

• Ryan and the team discuss various invoices and their statuses.

• Ryan asks to follow up with Jeff Dubin regarding the first payment for an outstanding invoice.

• Ryan mentions the need to double-check accounting and wire instructions for invoice 158.

• 📊 *Financial Updates and Collections* (07:10 - 10:01)

• Ryan discusses the importance of collecting outstanding payments to balance the books.

• Ryan plans to take the initiative with Jack Avino for payment confirmation.

• Ryan and the team discuss the need to update invoice settings for future accuracy.

• 📝 *Billing and Invoicing Strategy* (10:25 - 20:52)

• Ryan and the team discuss billing strategies for various clients, including CSP and TIP.

• Ryan instructs to create a detailed bill for Corbin Mantell's services with a 15% upcharge.

• Ryan plans to present this bill to Cameron for approval.

Gist • The meeting focused on financial discussions, responsibilities reallocation, credit card approval process, invoice reviews, overdue payments, and billing strategies.

Bullet Gist • 💼 Financial Topics: Discussions on responsibilities, credit card approvals, invoices, overdue payments, and billing strategies.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-14 13:53:13

• 📧 Email Approvals: Shift to email approvals for monthly credit card transactions.

• 📑 Invoice Reviews: Emphasis on follow-ups and detailed billing strategies.

• 💰 Overdue Payments: Plan to collect outstanding payments to balance the books.

• 📝 Action Items: Tasks assigned like confirming situations and calculating bills.

Short Summary • The meeting centered around key financial topics such as proposing a reallocation of responsibilities from Andy to Adrienne without changing titles, addressing discomfort with the credit card approval process by shifting to email approvals, emphasizing follow-ups on invoices, planning to collect overdue payments, detailing billing strategies with a 15% upcharge for Corbin Mantell's services, and assigning action items like confirming Andy's situation and calculating Corbin Mantell's bill.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-14 14:30:54

Title: Looker Enterprise for TIP Ops Date: Fri Jun 14 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nicholas@tortintakeprofessionals.com, anthony@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the "Looker Enterprise for TIP Ops" meeting, Nick McFadden was assigned to develop pipelines for Leeds PD and an advanced API for Law Ruler. Ryan Vaspra conducted a comprehensive training session on Looker and tasked Anthony Soboleski with learning the platform to create dashboards, with Ryan providing the necessary data and tools. Due to technical issues with screen sharing on Google Meet, Ryan will organize a Slack huddle for further discussions and screen sharing. Action items include Nick starting on the pipelines and API, Anthony becoming proficient with Looker, and Ryan facilitating the access and setting up the Slack huddle.

Action Items • *Nick McFadden*

• Nick McFadden needs to start working on the pipelines for Leeds PD and the new advanced API for Law Ruler (00:24)

• *Anthony Soboleski*

• Anthony Soboleski to get familiar with Looker and start creating dashboards (06:51)

• *Ryan Vaspra*

• Ryan Vaspra to provide Anthony Soboleski with access to the necessary data and tools for creating dashboards (17:29)

• Ryan Vaspra to set up a Slack huddle for further screen sharing and discussion due to technical issues with Google Meet (24:32)

Shorthand Bullet • 🔧 *Pipeline and API Development* (00:24 - 01:26)

• Nick McFadden needs to start working on pipelines for Leeds PD and the new advanced API for Law Ruler.

• Ensure the correct project is selected for the Leeds PD pipeline.

• Complete the advanced API for Law Ruler.

• 📊 *Looker Training and Dashboard Creation* (01:30 - 21:25)

• Ryan Vaspra provided a detailed walkthrough of Looker functionalities.

• Anthony Soboleski to get familiar with Looker and start creating dashboards.

• Ryan Vaspra to provide Anthony with access to necessary data and tools.

• Anthony will help rebuild TIP operations and agent performance dashboards.

• 💻 *Technical Issues and Next Steps* (21:37 - 25:15)

• Technical issues with Google Meet screen sharing on Mac.

• Ryan Vaspra to set up a Slack huddle for further discussion and screen sharing.

Gist • The meeting focused on assigning tasks related to pipeline and API development, Looker training, and addressing technical issues with screen sharing.

Bullet Gist • 🔧 Pipeline and API Development: Nick to work on pipelines for Leeds PD and advanced API for Law Ruler.

• 📊 Looker Training and Dashboard Creation: Ryan provided Looker training, Anthony tasked with creating dashboards.

• 💻 Technical Issues and Next Steps: Ryan to set up Slack huddle for further discussions.

Short Summary • The meeting assigned Nick McFadden to develop pipelines for Leeds PD and an advanced API for Law Ruler, while Ryan Vaspra conducted a Looker training session and tasked Anthony Soboleski with creating dashboards. Technical issues with screen sharing led to the decision to organize a Slack huddle for further discussions and sharing screens.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-17 13:37:45

Title: Tech Project Status Weekly Date: Mon Jun 17 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the weekly Tech Project Status Meeting, Nick McFadden aired frustrations about client issues and inadequate processes, leading Ryan to recommend direct interventions with Nick Ward and Cameron. Ryan emphasized the importance of leadership and task delegation to Nick Ward, advising Mike to facilitate the project management transition smoothly. Shane Latimer was tasked with AWS Lambda updates to expedite financial processes and automate tasks out of the TIP dashboard. Brian Hirst, alongside Shane, is to expedite the tort intake retool portal design and swiftly pivot to dashboard design. Ryan is focusing on client dashboard layout design and collaborating with Nick McFadden and Shane on law pipeline development involving various intake and Q&A tables. Issues with Power Automate integrations were discussed, with Nick McFadden assigned to investigate and resolve them. James Scott is running a large language model through PDFs for system improvements. Lastly, Ryan is also working on the client portal dashboards mockup, emphasizing visualization and scorecards. Action items were allotted to each member, aligning their tasks with these discussions.

Action Items • *Nick McFadden*

• Resolve the issues with the client and processes that are causing frustration (00:53)

• Investigate and resolve issues with Power Automate integrations (11:14)

• *Mike*

• Assist Nick McFadden and Nick Ward in resolving client issues (01:12)

• *Shane Latimer*

• Work on AWS Lambda updates for financial crunches and automate tasks out of the TIP dashboard (04:33)

• *Brian Hirst*

• Complete the tort intake retool portal design and test (05:56)

• *Ryan Vaspra*

• Design the client dashboard layout and work on law pipeline development (07:41)

• Build the client portal dashboards mockup and clean up the dashboard (28:59)

• *James Scott*

• Run large language model through PDFs and improve the metric system (16:52)

Shorthand Bullet • 🔧 *Client Issues and Process Frustrations* (00:35 - 01:12)

• Nick McFadden expressed frustration with client issues and process failures.

• Ryan suggested Nick focus on resolving the issues directly with Nick Ward and Cameron.

• 💼 *Project Management* and Task Delegation** (01:12 - 02:38)

• Ryan emphasized the importance of leadership and delegation to Nick Ward.

• Mike was advised to act as a bridge and not take the project management transition personally.

• 📊 *AWS Lambda and TIP Dashboard Updates* (04:33 - 05:56)

• Shane Latimer is working on AWS Lambda updates for financial crunches.

• The updates will automate tasks out of the TIP dashboard, speeding up routine processes.

• 🛠️ *Tort Intake *Retool Portal Design** (05:56 - 07:41)

• Brian Hirst is tasked with completing the tort intake retool portal design.

• Brian has 2 hours with Shane to learn the platform quickly and pivot to dashboard design.

• 📈 *Client Dashboard and *Law Pipeline Development** (07:41 - 09:57)

• Ryan is designing the client dashboard layout.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-17 13:37:45

• Nick McFadden and Shane Latimer are working on law pipeline development, including LR inbox, LR intakes, and LR lead Q&A tables.

• 🔄 *Power Automate Integrations* (10:35 - 14:48)

• Nick McFadden discussed issues with Power Automate integrations.

• Ryan suggested checking the dev login spreadsheet for Power Automate logins and ensuring integrations are completed.

• 📑 *Large Language Model and PDF Processing* (16:52 - 17:31)

• James Scott is running a large language model through PDFs to improve the metric system.

• Testing involves 100 documents initially, followed by the remaining 8000 documents.

• 📊 *Client Portal Dashboards Mockup* (28:59 - 34:56)

• Ryan is working on designing the client portal dashboards mockup.

• Focus is on visualization, scorecards, and cleaning up the dashboard.

Gist • The meeting focused on project updates, client issues, process improvements, and task assignments to team members.

Bullet Gist • ⚙️ Project Updates and Client Issues: Discussions on client issues and process improvements.

• 📊 Task Assignments: Assigning tasks like AWS Lambda updates, dashboard designs, and system improvements.

• ⚠️ Emphasis on Leadership: Ryan stressed leadership and task delegation for smooth project management.

• 🔍 Investigations and Resolutions: Assigning investigations like Power Automate issues and system improvements through PDF analysis.

• 🎯 Alignment of Tasks: Action items allocated to team members to align tasks with the meeting discussions.

Short Summary • The meeting discussed project updates and client issues, with interventions recommended for process improvements. Tasks were assigned to team members, including AWS Lambda updates, dashboard designs, Power Automate investigations, and system improvements through PDF analysis. Ryan emphasized leadership and task delegation, highlighting the importance of smooth project management transition and client dashboard design collaboration. Action items were allocated to align tasks with the discussions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-18 11:40:31

Title: ML - mid month commission review Date: Tue Jun 18 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: maximus@themedialab.agency, cameron@themedialab.agency, ryan@shield-legal.com, ryan@brandlytics.io, brian@accountingdept.net, briant@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • During the "ML - mid-month commission review" meeting, Cameron and Maximus started with morning greetings and small talk about their current locations and activities, with Cameron mentioning work in Vegas. Ryan read off the commissions, reporting $36,783.17 and a $5,000 bonus, which led to a discussion about the positive sales performance. The conversation shifted to ongoing gaming projects, upcoming campaigns, and potential partnerships, with Maximus expressing excitement about social media gaming and targeting companies like Microsoft. Cameron reminded Maximus of their later meeting, and Maximus confirmed rescheduling a call with Jan and Attai to the next day. The meeting concluded with Cameron expressing appreciation for the updates. Key action items included Ryan reading commissions and Maximus rescheduling a call.

Action Items • *Ryan Vaspra*

• Read off the commissions for Cameron Rentch (03:03)

• *Maximus Lynn*

• Move the call with Jan and Attai to tomorrow and discuss with them (07:26)

Shorthand Bullet • 🌅 *Morning Greetings and Small Talk* (01:16 - 02:20)

• Cameron and Maximus greeted each other and discussed their current locations and activities.

• Cameron mentioned being busy with work in Vegas.

• 💼 *Commission Review* (03:03 - 04:05)

• Cameron asked Ryan to read off the commissions.

• Ryan reported a commission of $36,783.17 and a $5,000 bonus.

• Cameron and Maximus discussed the positive performance and recent rush in sales.

• 🎮 *Gaming and Campaign Updates* (04:12 - 06:01)

• Cameron mentioned ongoing projects in gaming and storm damage.

• Discussion on upcoming campaigns and partner firms.

• Maximus expressed excitement about social media gaming being the next big trend.

• Conversation about targeting specific gaming companies like Microsoft.

• 📅 *Meeting Scheduling and *Follow-ups** (07:19 - 08:06)

• Cameron reminded Maximus about their meeting later in the day.

• Maximus confirmed rescheduling a call with Jan and Attai to tomorrow.

• Cameron appreciated the update and concluded the meeting.

Gist • The meeting focused on mid-month commission review and discussions about ongoing gaming projects, upcoming campaigns, and partnership opportunities.

Bullet Gist • 🌅 Morning Greetings and Small Talk: Cameron and Maximus discussed their current locations and activities, with Cameron mentioning work in Vegas.

• 💼 Commission Review: Ryan reported a commission of $36,783.17 and a $5,000 bonus, leading to a discussion on positive sales performance.

• 🎮 Gaming and Campaign Updates: Discussion on ongoing gaming projects, upcoming campaigns, and targeting companies like Microsoft.

• 📅 Meeting Scheduling and Follow-ups: Maximus confirmed rescheduling a call with Jan and Attai for the next day.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-18 11:40:31

• During the meeting, Cameron and Maximus exchanged morning greetings before diving into a commission review led by Ryan, who reported a commission of $36,783.17 and a $5,000 bonus, sparking a discussion on positive sales performance. The conversation shifted to ongoing gaming projects, upcoming campaigns, and potential partnerships, with Maximus expressing excitement about social media gaming trends and targeting companies like Microsoft. Cameron reminded Maximus of their upcoming meeting and Maximus confirmed rescheduling a call with Jan and Attai for the next day, leading to the conclusion of the meeting with Cameron expressing appreciation for the updates.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-21 12:20:02

Title: SL Lambdas Date: Fri Jun 21 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, shane@shield-legal.com, nickmcfadden@shield-legal.com, luke@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The SL Lambdas meeting focused on the development progress of the project, including working with financial logs and incorporating datasets into leadspedial logic. Updates were provided on creating data views in DBT, financial details in the database, future development plans, review and reconciliation of tables, verification of data accuracy, and challenges with DBT and BigQuery syntax. Action items include finalizing tables in DBT, reconciling orders, updating tables, and building media buyer tables in the portal, with plans for the next meeting scheduled for next Friday to review progress and next steps.

Action Items • *Luke Fontaine*

• Review and finalize the table created in DBT for the modeling layer, ensuring it connects leads, PDA contracts to shield proper orders (04:24)

• Reconcile three orders with payments in Copper to ensure data accuracy (14:11)

• Update the table to include columns for target order budget remaining and paid left to spend amount (16:42)

• *Shane Latimer*

• Build the media buyer table and forms in the portal for Shield (07:50)

Shorthand Bullet • 🛠️ *Development Progress* (01:15 - 03:23)

• Shane provided an update on the development progress.

• Separated the project into two major steps: working with the financial log and incorporating the returned dataset into the leadspedial logic.

• Built early plumbing to look at two different verticals.

• 🔗 *Data View in DBT* (03:24 - 04:24)

• Luke is working on creating a data view in DBT for the modeling layer.

• Connecting leads, PDA contracts to shield proper orders.

• Recreating the materialized financial views in PostgreSQL.

• 🔄 *Financial Details and Views* (04:25 - 06:26)

• Ryan explained the financial details and views in the database.

• Discussed the creation of a new view called Matt, then view details, copper.

• Plan to migrate from PostgreSQL to BigQuery tables.

• 📊 *Future Development* Plans** (06:27 - 07:50)

• Plan to build the media buyer table and forms in the portal for Shield.

• Train media buyers to use the new portal.

• Update calc performance to look things up in BigQuery.

• 📅 *Review and Reconciliation* (07:51 - 14:11)

• Luke has finished the table in DBT and saved it.

• Plan to review the table on Monday.

• Reconcile three orders with payments in Copper.

• 🔍 *Verification and Updates* (14:12 - 16:53)

• Verify the joins in the table to ensure data accuracy.

• Update the table to include columns for target order budget remaining and paid left to spend amount.

• Ensure the table is formatted correctly.

• 🤖 *DBT and BigQuery Syntax* (16:54 - 18:14)

• Discussed challenges with DBT and BigQuery syntax.

• ChatGPT's limitations in understanding platform-specific syntax.

• Plan to continue improving the syntax over time.

• 📅 *Next Meeting* (18:15 - 18:43)

• Plan to schedule another meeting for next Friday.

• Review progress and next steps in the upcoming meeting.

Gist • The meeting focused on project development progress and plans for future tasks.

Bullet Gist • 🛠️ Development Progress: Updates on working with financial logs and incorporating datasets.

• 🔗 Data View in DBT: Creating data views in DBT for modeling layer.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-21 12:20:02

• 🔄 Financial Details and Views: Explaining financial details in the database and migration to BigQuery.

• 📊 Future Development Plans: Planning to build media buyer tables and forms in the portal.

• 📅 Review and Reconciliation: Finalizing tables, reviewing on Monday, and reconciling orders.

Short Summary • The meeting centered on discussing the development progress of the project, covering areas such as working with financial logs, creating data views in DBT, financial details in the database, future development plans, review and reconciliation of tables, verification of data accuracy, and challenges with DBT and BigQuery syntax. Action items included finalizing tables in DBT, reconciling orders, updating tables, and building media buyer tables in the portal, with a follow-up meeting planned for next Friday to review progress and next steps.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-24 13:37:04

Title: Tech Project Status Weekly Date: Mon Jun 24 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, nicholas@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Tech Project Status Weekly meeting, updates on various projects were discussed. Ryan Vaspra shared his new office setup and emphasized the importance of mental health discussions. Shane Latimer is working on automating financial log counts, while Brian Hirst is progressing with the tort intake portal design and test. Brian needs an hour with Shane for assistance, and Ryan set a due date for the portal to June 28th. James Scott discussed using different LLMs for PDF extraction, and Ryan suggested getting a demo account for further testing. Mike Everhart explained changes in Zapier integration for trusted forms, and Ryan plans to explain these changes to Cameron. Action items include scheduling a one-hour session with Shane for assistance, setting the due date for the portal, and following up on a demo account for PDF extraction tools.

Action Items • *Brian Hirst*

• Email Shane Latimer, Deb Chattery, and Ryan Vaspra to schedule a one-hour session with Shane for assistance (06:33)

• *Ryan Vaspra*

• Set the due date for the tort intake portal design and test to Friday, June 28th (07:07)

• Explain the changes required for the Facebook CRM events funnel app to Cameron (37:24)

• *James Scott*

• Follow up with Forest to get a demo account for PDF extraction and parsing tools (21:23)

Shorthand Bullet • :male_technologist: *Project Updates and Setup* (02:06 - 03:47)

• Ryan Vaspra discusses his new office setup.

• Mike Everhart shares positive updates on his sleep schedule.

• Ryan emphasizes the importance of mental health discussions.

• 📊 *AWS Legacy BI Enhancement and Tort Intake Portal* (03:47 - 07:23)

• Shane Latimer is working on automating financial log counts.

• Brian Hirst is progressing on the tort intake portal design and test.

• Brian needs an hour with Shane for further assistance.

• Ryan sets a due date for the tort intake portal to June 28th.

• 🛠️ *Iterative Development* and User Admin Tab** (07:23 - 11:03)

• Brian Hirst discusses the iterative development approach.

• Focus on getting specific users to see only relevant case types.

• Ryan clarifies the purpose of the user admin tab.

• 📄 *PDF Extraction and Parsing Tools* (11:06 - 22:44)

• James Scott discusses using different LLMs for PDF extraction.

• Ryan suggests getting a demo account for further testing.

• Mike Everhart advises on data privacy when using LLMs.

• 🔄 *Trusted Forms and Zapier Integration* (26:05 - 37:56)

• Mike Everhart explains changes in Zapier integration for trusted forms.

• Ryan and Mike discuss the necessity of these changes.

• Ryan plans to explain these changes to Cameron.

Gist • Discussion on project updates, office setup, mental health, automation of financial log counts, tort intake portal design, PDF extraction tools, and Zapier integration changes.

Bullet Gist • :male_technologist: Project Updates and Setup: Updates on office setup and mental health discussions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-24 13:37:04

• 📊 Automation and Portal Design: Shane automates financial log counts, Brian progresses with the tort intake portal design.

• 📄 PDF Extraction Tools: Discussion on using different LLMs for PDF extraction.

• 🛠️ Iterative Development: Focus on user admin tab and relevant case types.

• 🔄 Zapier Integration Changes: Explanation of changes in Zapier integration for trusted forms.

Short Summary • The meeting covered various project updates including Ryan Vaspra's office setup and focus on mental health discussions. Shane Latimer is automating financial log counts, Brian Hirst is progressing with the tort intake portal design, and James Scott discussed PDF extraction tools. Mike Everhart explained Zapier integration changes. Action items include assistance sessions, setting due dates, and testing demo accounts.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-25 12:14:22

Title: Ben Crump Yext setup Date: Tue Jun 25 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting discussed setting up Yext for Ben Crump, focusing on auditing entities, managing listings, adding new entities, optimizing SEO, and strategizing for local SEO. Action items include performing full audits, adding new entities, running listing scans, and confirming local city pages with Stephen Giacovino. The importance of timely execution and adding Yext to future SEO meeting agendas were emphasized.

Action Items • *Korbin Mantel*

• Perform a full audit of all entities in Yext to identify who is live and who hasn't paid. Create a spreadsheet from the audit (03:33)

• Add new entities to Yext for Ben Crump's six offices and Jeff Markowitz's two offices, including setting up DTM tracking numbers (12:15)

• Run Yext listing scans for Ben Crump's six offices, Jeff Markowitz's two offices, and Fullster Law Firm. Take screenshots of the results and send them to Ryan (23:57)

• Post in the Los G channel to confirm with Stephen Giacovino about creating more local city pages for his practice areas (21:05)

Shorthand Bullet • 📋 *Meeting Setup and Initial Discussion* (00:00 - 02:27)

• Ryan and Korbin discuss audio setup and personal matters.

• Ryan mentions dealing with renters insurance.

• Korbin and Ryan talk about chair adjustments and screen setup.

• 💻 *Yext Overview and Audit Request* (02:36 - 04:24)

• Ryan introduces Yext as bloatware and explains its functionalities.

• Ryan requests Korbin to perform a full audit of entities in Yext.

• Discussion on how to activate/deactivate services in Yext.

• 📊 *Entity Management* in Yext** (04:24 - 08:25)

• Ryan shows how to manage entities in Yext.

• Discussion on removing unpaid entities and keeping track of active ones.

• Ryan highlights the need to keep certain entities for potential payments.

• 🏢 *Adding New Entities and Tracking* (11:06 - 13:53)

• Ryan instructs Korbin to add new entities for Ben Crump and Jeff Markowitz.

• Details on setting up DTM tracking numbers and forwarding to main intake number.

• Ryan mentions the importance of tracking primary inbound calls.

• 🔍 *SEO and Ongoing Tasks* (16:16 - 17:40)

• Korbin updates Ryan on ongoing SEO tasks and URL issues.

• Discussion on optimizing press releases and fixing crawl errors.

• Ryan emphasizes the importance of ongoing SEO work.

• 📈 *Local SEO Strategy for Giacovino* (18:02 - 21:05)

• Ryan and Korbin discuss expanding local SEO for Stephen Giacovino.

• Recommendation to create more local city pages for better ranking.

• Plan to confirm with Stephen about his top markets.

• 📝 *Yext Listing Scans and Reporting* (23:16 - 27:10)

• Ryan instructs Korbin to run Yext listing scans for multiple entities.

• Details on taking screenshots of scan results and sending them to Ryan.

• Ryan explains the importance of these scans for client satisfaction.

• ✅ *Meeting Wrap-Up and Next Steps* (27:10 - 28:42)

• Ryan and Korbin summarize the tasks to be completed.

• Ryan emphasizes the importance of timely execution.

• Discussion on adding Yext to the SEO meeting agenda.

Gist • The meeting focused on setting up Yext for Ben Crump, auditing entities, managing listings, optimizing SEO, and local SEO strategy.

Bullet Gist • 📋 Meeting Setup and Initial Discussion: Ryan and Korbin discuss audio setup and personal matters.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-25 12:14:22

• 💻 Yext Overview and Audit Request: Ryan introduces Yext functionalities and requests a full audit of entities.

• 📊 Entity Management in Yext: Discussion on managing entities, removing unpaid ones, and tracking active entities.

• 🏢 Adding New Entities and Tracking: Instructions on adding new entities, setting up tracking numbers, and tracking inbound calls.

• 🔍 SEO and Ongoing Tasks: Updates on ongoing SEO tasks, optimizing press releases, and local SEO strategies.

Short Summary • The meeting centered around setting up Yext for Ben Crump, including auditing entities, managing listings, adding new entities, optimizing SEO, and strategizing for local SEO. Ryan and Korbin discussed various aspects such as activating/deactivating services in Yext, managing entities, adding new entities for specific individuals, tracking inbound calls, ongoing SEO tasks, and local SEO expansion for Stephen Giacovino, emphasizing the importance of timely execution and incorporating Yext into future SEO agendas.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-26 12:34:41

Title: MB Commish Date: Wed Jun 26 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io, brian@accountingdept.net Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on discussing the setup of commissions, payroll additions, BLX meeting preparation, media spend and lead generation pacing, client campaign management, new campaigns and website projects, budget adjustments, and dashboard review. Action items include adding Anthea to the payroll, including Melissa Phillips in the process, preparing for the next BLX meeting, adjusting media spend pacing, discussing the paused campaign with Jeff, and meeting with a potential new client for a website project.

Action Items • *Anthea*

• Ensure Anthea adds the necessary items to the payroll next week (04:15)

• *Melissa Phillips*

• Include Melissa Phillips in the payroll process (04:22)

• *Ryan Vaspra*

• Prepare for the BLX meeting next month, including sales commissions, media commissions, invoices, and accounts receivable (05:06)

• Review and adjust the media spend pacing to ensure it aligns with the budget and lead generation goals (08:12)

• Discuss with Jeff about the paused campaign and potential budget adjustments (09:37)

• Meet with the woman who needs a website and discuss potential collaboration (12:09)

Shorthand Bullet • 📋 *Meeting Setup and Initial Discussion* (00:01 - 03:59)

• Ryan explains his setup and apologizes for the delay in handling commissions.

• Discussion on the different payment structures for media buyers and Brainlytics.

• 💼 *Payroll and Commissions* (04:15 - 05:08)

• Ryan and Lee discuss adding Anthea to the payroll.

• Consideration of including Melissa Phillips in the payroll process.

• Ryan ensures focus on tasks requested by Cameron.

• 📅 *BLX Meeting Preparation* (05:06 - 06:09)

• Ryan confirms the agenda for the next BLX meeting, including sales commissions, media commissions, invoices, and accounts receivable.

• Lee and Ryan discuss the upcoming meeting schedule.

• 📊 *Media Spend and Lead Generation* (06:05 - 08:12)

• Ryan reviews the media spend and lead generation pacing.

• Discussion on adjusting the budget to align with lead generation goals.

• Ryan emphasizes the importance of maintaining a steady lead flow without overspending.

• 📞 *Client Campaign Management* (08:22 - 09:00)

• Discussion on Jeff's paused campaign and potential budget adjustments.

• Ryan mentions the need for a long-term budget commitment from clients for better management.

• Ryan plans to discuss the paused campaign with Jeff.

• 🌐 *New Campaigns and Website Projects* (09:31 - 12:12)

• Ryan mentions a potential new client needing a website.

• Discussion on not pushing too hard for new clients but being open to opportunities.

• Ryan is getting unique website projects, including one for an aeronautics aerospace factory.

• 🔧 *Budget Adjustment and Dashboard Review* (13:34 - 22:14)

• Ryan adjusts the budget to slow down lead generation for a client.

• Ryan prepares for an upcoming dashboard review.

• Ryan receives a new lead during the meeting.

Gist • The meeting focused on discussing various topics such as commissions, payroll, BLX meeting preparation, media spend, lead generation pacing, client campaign management, new campaigns, website projects, budget adjustments, and dashboard review.

Bullet Gist • 📋 Setup and Initial Discussion: Ryan explains commission setup and discusses payment structures for media buyers and Brainlytics.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-26 12:34:41

• 💼 Payroll and Commissions: Discussion on adding Anthea to payroll and involving Melissa Phillips in the process.

• 📅 BLX Meeting Preparation: Confirmation of agenda items for the upcoming BLX meeting and discussion on meeting schedule.

• 📊 Media Spend and Lead Generation: Review of media spend and lead generation pacing, emphasizing budget alignment.

• 📞 Client Campaign Management: Discussion on paused campaign, potential budget adjustments, and long-term client commitment.

Short Summary • The meeting covered a range of crucial topics including setting up commissions and payroll, preparing for the BLX meeting, reviewing media spend and lead generation pacing, managing client campaigns, discussing new campaigns and website projects, adjusting budgets, and reviewing dashboards. Action items included adding Anthea to payroll, involving Melissa Phillips in the process, discussing the paused campaign with Jeff, and meeting a potential new client for a website project.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-26 13:32:33

Title: Thomson Reuters meeting w/ Ryan Vaspra of Shield Legal to discuss Westlaw Precision Date: Wed Jun 26 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@themedialab.agency, braden.holton@thomsonreuters.com, brian.hall@thomsonreuters.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 25

Overview • Summary: The meeting between Thomson Reuters and Shield Legal focused on discussing Westlaw Precision. Key points included introductions, background discussions, business overviews, legal services and tools, and planning for a demo. Action items were assigned to Braden Holton to send updated numbers, follow-up email, and schedule a demo with Ryan Vaspra and his team.

Action Items • *Braden Holton*

• Send updated numbers to Molly to get the ball rolling on the demos and follow-up calls (02:17)

• Send follow-up email with hyperlinks and general information around Westlaw and Co-Counsel (30:32)

• Schedule a demo to walk through Westlaw and Co-Counsel features (30:58)

Shorthand Bullet • 👋 *Introductions and Initial Discussion* (00:00 - 03:53)

• Braden Holton and Brady Boehm discuss the absence of Ryan Vaspra and the use of Fireflies AI for meeting notes.

• Braden mentions the use of Copilot for similar functions within their team.

• Braden plans to send updated numbers to Molly.

• 📈 *Ryan Joins* and Background Discussion** (03:53 - 12:07)

• Ryan joins the call and explains his technical difficulties.

• Ryan shares details about his lake house and personal background.

• Discussion about mutual connections and locations in Oklahoma and Texas.

• 🏢 *Business Overview by *Ryan** (12:07 - 15:36)

• Ryan explains his role as Chief Analytics Officer at Shield Legal and their business model.

• Details about their sister company, Tort Intake Professionals, and their services.

• Ryan describes their marketing and staffing operations, emphasizing quality control and in-house media buying.

• 🔍 *Discussion on *Legal Services and Tools** (15:36 - 22:17)

• Ryan discusses the need for better tools and services to support their legal operations.

• Braden explains the range of services offered by Thomson Reuters, including Westlaw and Co-Counsel.

• Ryan expresses interest in AI features and workflow automation for their legal teams.

• 📅 *Next Steps and Demo Planning* (22:17 - 31:13)

• Ryan outlines the timeline for decision-making, estimating 3-6 months.

• Braden suggests setting up a demo to showcase Westlaw and Co-Counsel features.

• Ryan agrees and mentions involving James Scott, his data scientist, in the follow-up.

Gist • The meeting focused on discussing Westlaw Precision between Thomson Reuters and Shield Legal.

Bullet Gist • 👋 Introductions and Initial Discussion: Discussed AI tools and planned to send updated numbers.

• 📈 Background Discussion by Ryan: Shared personal background and details about Shield Legal.

• 🏢 Business Overview by Ryan: Explained Shield Legal's business model and services.

• 🔍 Discussion on Legal Services and Tools: Highlighted the need for better tools and interest in AI features.

• 📅 Next Steps and Demo Planning: Outlined decision-making timeline and planned a demo.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-26 13:32:33

• The meeting between Thomson Reuters and Shield Legal centered around discussions on Westlaw Precision. It started with introductions and initial discussions regarding AI tools like Copilot and Fireflies. Ryan Vaspra joined later, sharing personal background and details about Shield Legal's business model. The conversation delved into legal services and tools, highlighting the interest in AI features and workflow automation. Planning for a demo of Westlaw and Co-Counsel was also a key point, with action items assigned to Braden Holton for follow-up.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-27 14:41:45

Title: BCL Next Steps Date: Thu Jun 27 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting discussed finalizing the CTM number, naming the campaign 'Church Fan Campaign', and progress on the script with an emphasis on completing tasks early. Corbin was assigned to ensure the CTM number is obtained and finalized.

Action Items • *Corbin*

• Ensure the CTM number is obtained and finalized (02:04)

Shorthand Bullet • 📋 *CTM Number* (01:28 - 02:12)

• Adrienne asked Corbin to finalize the CTM number today.

• Uzoma confirmed there's no immediate deadline but prefers to have it done early.

• 🏷️ *Campaign Naming* (02:21 - 02:27)

• The campaign will be called 'Church Fan Campaign' as suggested by Uzoma.

• 📜 *Script Progress* (02:39 - 02:45)

• Adrienne mentioned that the team is working hard on the scripts.

• Uzoma expressed anticipation for the completed scripts.

Gist • The meeting focused on finalizing the CTM number, naming the campaign 'Church Fan Campaign', and discussing progress on the script with an emphasis on early completion.

Bullet Gist • 📋 Finalizing CTM Number: Adrienne requested Corbin to ensure the CTM number is finalized early.

• 🏷️ Campaign Naming: The campaign was named 'Church Fan Campaign' based on Uzoma's suggestion.

• 📜 Script Progress: Adrienne mentioned the team's diligence in script development, with Uzoma looking forward to the completed scripts.

Short Summary • The meeting revolved around the finalization of the CTM number, naming the campaign 'Church Fan Campaign' at Uzoma's suggestion, and the team's dedication to advancing the script early. Adrienne tasked Corbin with ensuring the timely acquisition of the CTM number. Uzoma emphasized the importance of early completion without a set deadline, showing eagerness for the completed scripts.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-28 11:29:19

Title: Lex Machina Date: Fri Jun 28 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@themedialab.agency, rscott@lexmachina.com, ryan@brandlytics.io, richard.scott@lexisnexis.com, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting revolved around rescheduling to include James Scott, sharing personal backgrounds, introducing Lex Machina and its capabilities, discussing features and use cases, and setting up preparation for a detailed demo session on Monday. Action items include rescheduling the meeting and inviting James, as well as preparing a demo of Lex Machina's features.

Action Items • *Ryan Vaspra*

• Reschedule the meeting to Monday, the 1st of the next week at 11:30 AM Pacific Time and ensure James Scott is added to the invite (04:42)

• *Richard Scott*

• Prepare a demo of Lex Machina's features and functionalities for the rescheduled meeting (22:05)

Shorthand Bullet • 📅 *Rescheduling the Meeting* (02:52 - 05:01)

• Ryan realized his data scientist, James Scott, was not invited.

• Discussion on rescheduling the meeting to include James.

• Agreed on Monday, the 1st of the next week at 11:30 AM Pacific Time.

• 🌍 *Personal Backgrounds and Experiences* (05:20 - 16:05)

• Ryan and Richard discussed their personal backgrounds and experiences in London and other places.

• Shared anecdotes about playing football and living in different neighborhoods.

• 📊 *Introduction to Lex Machina* (18:23 - 21:45)

• Ryan explained the structure and rapid growth of his companies: Shield Legal, Torque Call Intake Professionals, and Brandlytics.

• Richard introduced Lex Machina and its capabilities in legal analytics.

• Discussion on the importance of using advanced AI and avoiding outdated technologies.

• 🔍 *Lex Machina's Features and Use Cases* (22:45 - 26:44)

• Richard provided an overview of Lex Machina's features, including case aggregation, classification, and analytics.

• Ryan expressed interest in understanding how Lex Machina organizes and classifies data.

• Discussion on the potential use cases and benefits for Ryan's companies.

• 🤝 *Next Steps and Preparation for the Demo* (26:45 - 27:28)

• Agreed to have a detailed demo session on Monday.

• Richard to prepare a demo showcasing Lex Machina's features.

• Ryan and James to prepare questions and areas of interest for the demo.

Gist • The meeting aimed to reschedule to include James Scott, share personal backgrounds, introduce Lex Machina and its capabilities, discuss features and use cases, and prepare for a detailed demo session on Monday.

Bullet Gist • 📅 Rescheduling the Meeting: Discussion on rescheduling to include James Scott on Monday at 11:30 AM PT.

• 🌍 Personal Backgrounds and Experiences: Ryan and Richard shared personal anecdotes and experiences from London and beyond.

• 📊 Introduction to Lex Machina: Overview of Lex Machina's capabilities in legal analytics and the importance of AI.

• 🔍 Lex Machina's Features and Use Cases: Detailed discussion on Lex Machina's features, classification, and potential benefits.

• 🤝 Next Steps and Demo Prep: Agreement on a detailed demo session preparation for Monday with specific focus areas.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-06-28 11:29:19

• The meeting involved rescheduling to accommodate James Scott, sharing personal anecdotes and experiences, introducing Lex Machina and its legal analytics capabilities, discussing the importance of advanced AI, exploring Lex Machina's features and use cases, and setting up a demo session preparation for Monday. Ryan and Richard engaged in discussions covering personal histories, company structures, and the potential benefits of Lex Machina for Ryan's companies.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-01 12:31:38

Title: Tech Project Status Weekly Date: Mon Jul 01 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, nicholas@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting discussed the status of various tech projects, including BigQuery and Retool editing, Looker Enterprise user permissions, financial models, CRM event app training, and dialer status. Action items include making copies of BigQuery for editing, setting up user groups in Looker, working on financial models, providing training on custom apps, and reconciling financial records. Overall, progress was made on key project tasks with clear action items assigned for follow-up.

Action Items • *Brian Hirst*

• Brian Hirst to make copies of different parts of BigQuery for retool editing and ensure it overwrites the original table at the end of the day (03:33)

• *Nick McFadden*

• Nick McFadden to help create the history record in DBT correctly with Brian Hirst (08:20)

• Nick McFadden to discuss BigQuery and Looker permissions setup with Ryan Vaspra (18:34)

• *Ryan Vaspra*

• Ryan Vaspra to clean up the back end of Looker enterprise and set up user groups for TIP operations (19:40)

• *Mike Everhart*

• Mike Everhart to train Nick McFadden and Asad on Pixel Fix, CRM event app, and leads CTM to leads PDF (24:20)

• *Luke*

• Luke to reconcile copper orders with Shield legal financials and ensure they match (29:20)

Shorthand Bullet • 🛠️ *BigQuery and Retool Editing* (02:13 - 08:56)

• Ryan Vaspra discusses the need to make copies of different parts of BigQuery for retool editing.

• Brian Hirst to ensure the edited table overwrites the original at the end of the day.

• Nick McFadden suggests a DBT workflow for maintaining raw and production versions.

• 📊 *Looker Enterprise* and User Permissions** (18:34 - 20:54)

• Ryan Vaspra is working on cleaning up Looker enterprise and setting up user groups for TIP operations.

• Nick McFadden to discuss BigQuery and Looker permissions setup with Ryan.

• Anthony has access to Looker enterprise and is expected to build explorers and dashboards.

• 📈 *Financial Models and AWS Dashboard* (21:13 - 22:07)

• Ryan Vaspra mentions the need to move away from AWS to BigQuery for financial models.

• Nick McFadden and Asad to work on the LR lead using the advanced API.

• Brian and Luke to write financial models and log models for operations and financials.

• 💻 *Pixel Fix and CRM Event App Training* (24:20 - 26:40)

• Mike Everhart to train Nick McFadden and Asad on Pixel Fix, CRM event app, and leads CTM to leads PDF.

• Cameron wants cross-training to ensure coverage in case of absences.

• Mike to provide access and training materials for the custom apps he built.

• 📞 *Dialer Status and Shield Financials* (27:18 - 29:20)

• Nick McFadden confirms the contract for the new dialer is signed.

• Implementation roadmap to be discussed next week.

• Luke to reconcile copper orders with Shield legal financials and ensure they match.

Gist • The meeting focused on discussing the status of various tech projects and assigning action items for follow-up.

Bullet Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-01 12:31:38

• 🛠️ BigQuery and Retool Editing: Discussed making copies for editing and implementing a DBT workflow.

• 📊 Looker Enterprise and User Permissions: Cleaning up Looker and setting up user groups for operations.

• 📈 Financial Models and AWS Dashboard: Transitioning financial models to BigQuery and working on LR lead with advanced API.

• 💻 Pixel Fix and CRM Event App Training: Training on Pixel Fix, CRM event app, and cross-training for coverage.

• 📞 Dialer Status and Shield Financials: Confirming new dialer contract, discussing implementation roadmap, and reconciling orders with financials.

Short Summary • The meeting delved into the progress of tech projects such as BigQuery and Retool editing, Looker Enterprise user permissions, financial models, CRM event app training, and dialer status. Action items included making copies for editing, setting up user groups, transitioning financial models to BigQuery, providing training on custom apps, and ensuring financial records match. Key participants like Ryan Vaspra, Nick McFadden, and others contributed insights and were tasked with specific responsibilities.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-02 11:54:04

Title: BLX EOM Fin Date: Tue Jul 02 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@accountingdept.net, ryan@brandlytics.io, andy@shield-legal.com, malissa@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on introductions, technical issues, client discussions, invoice management, follow-ups, financial planning, and future projects. Key points included introducing Melissa Phillips, discussing customer obsession and legal work focus, updating invoices for clients, and discussing potential new projects' financial impact. Action items assigned included sharing updated staffing worksheets, introducing Melissa to clients, revising invoices, monitoring for payments, and preparing financial statements. Importance was emphasized on accurate client communication and financial tracking.

Action Items • *Unassigned*

• Share updated staffing worksheets with Ryan Vaspra and notify him when they are updated (00:28)

• Message Melissa Phillips to join the meeting (01:35)

• *Ryan Vaspra*

• Introduce Melissa Phillips to Steven Giacovino and Jeff Dubin via email and request payment for outstanding invoices (07:10)

• Forward the history of emails and invoices to Melissa Phillips (09:44)

• Revise the invoice for Cello Levitt based on accurate payroll numbers (16:17)

• *Brian*

• Post the updated invoice for Cello Levitt in the BLX invoice channel and seek approval from Cameron (14:35)

• Look up and forward the Savvy Branding Group invoice to Melissa Phillips (22:58)

• Monitor for the arrival of the Jeffrey Markowitz payment and notify Melissa Phillips upon receipt (23:53)

• Prepare a pro forma P&L statement considering all discussed invoices and allocations (44:06)

• *Melissa Phillips*

• Chime in on the Holster Boca Raton invoice email thread and follow up on payment (24:30)

Shorthand Bullet • 👥 *Introductions and Technical Issues* (00:00 - 03:36)

• Ryan Vaspra introduces Melissa Phillips to the team.

• Melissa experiences technical difficulties joining the meeting.

• Discussion about staffing worksheets and sharing updates.

• 📊 *Client and Invoice Discussions* (04:13 - 16:02)

• Ryan discusses the importance of customer obsession and legal work focus.

• Melissa shares her legal background and experience.

• Detailed discussion on clients like Steven Giacovino and Jeff Dubin, and their payment issues.

• Ryan forwards relevant emails and invoices to Melissa.

• 💼 *Invoice Management* and Updates** (16:04 - 23:54)

• Ryan and Brian discuss updating and revising invoices for clients.

• Ryan revises the invoice for Cello Levitt based on accurate payroll numbers.

• Brian to post the updated invoice in the BLX invoice channel for Cameron's approval.

• 📧 *Follow-ups and Client Communication* (23:55 - 41:03)

• Ryan forwards the Savvy Branding Group invoice to Melissa.

• Melissa to follow up on the Holster Boca Raton invoice.

• Brian to monitor for the arrival of the Jeffrey Markowitz payment and notify Melissa.

• Discussion on the importance of accurate and timely client communication.

• 📈 *Financial Planning and Future Projects* (41:33 - 51:46)

• Ryan discusses potential new projects and their financial impact.

• Brian to prepare a pro forma P&L statement considering all discussed invoices and allocations.

• Ryan shares insights on the company's focus and future direction.

• Discussion on the importance of accurate financial tracking and reporting.

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-02 11:54:04

• The meeting aimed to cover introductions, technical issues, client discussions, invoice management, follow-ups, financial planning, and future projects.

Bullet Gist • 👥 Introductions and Technical Issues: Ryan introduced Melissa Phillips, discussed staffing worksheets, and technical difficulties were experienced by Melissa during the meeting.

• 📊 Client and Invoice Discussions: Customer obsession and legal work focus were highlighted; invoices for clients like Steven Giacovino and Jeff Dubin were discussed.

• 💼 Invoice Management and Updates: Discussions included updating and revising invoices, revising payroll numbers for Cello Levitt, and posting invoices for approval.

• 📧 Follow-ups and Client Communication: Follow-ups on invoices, monitoring payments, and stressing accurate client communication were key points.

• 📈 Financial Planning and Future Projects: Discussions covered potential new projects, preparing financial statements, and emphasizing accurate financial tracking.

Short Summary • The meeting revolved around introducing Melissa Phillips to the team, discussing customer obsession and legal work focus, updating invoices for clients like Steven Giacovino and Jeff Dubin, emphasizing accurate client communication and financial tracking, and planning for potential new projects. Action items included sharing staffing worksheets, revising invoices, monitoring payments, and preparing financial statements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-02 14:17:18

Title: SL Lambdas Date: Tue Jul 02 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, ahsan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on discussing the old AWS legacy system architecture, code improvements, morning routine for financial logs, revenue adjustments, GitHub and code review, access and permissions, script and process improvements, meeting scheduling with Luke, and next steps for automating the financial log process. Action items include forwarding training materials, setting up necessary access for Ahsan, reviewing Shane's code, and updating the script for better efficiency.

Action Items • *Ryan Vaspra*

• Forward training materials to Ahsan Tebha (02:43)

• Set up Ahsan with access to AWS, Typeform, and Data Studio (01:06:35)

• Schedule meetings with Luke to review the morning routine and understand the current process (49:37)

• *Ahsan Tebha*

• Review Shane's code in GitHub to understand the current state of the project (43:15)

• Update the script to dynamically calculate the date for the 'where sign date' field (01:02:01)

Shorthand Bullet • 📊 *System Architecture Overview* (02:43 - 05:11)

• Ryan explains the old AWS legacy system architecture.

• Discussion on data workflow involving WordPress, call tracking metrics, and AWS Lambdas.

• Explanation of business logic for calculating leads per contract per day.

• 🔧 *Code Improvements and Assignments* (05:11 - 10:36)

• Shane's improvements on the old code, including better Python coding and removal of hard codes.

• Discussion on assigning media buyers to leads without S1 or LP lead IDs.

• Plan to sum up contracts by media buyer and day.

• 📝 *Morning Routine and Financial Logs* (12:30 - 18:47)

• Explanation of the morning routine for generating financial logs.

• Discussion on handling referrals and test leads.

• Importance of accurate data entry and reconciliation.

• 📈 *Adjustments and Revenue Calculation* (35:11 - 37:10)

• Cameron's role in making revenue adjustments.

• Process of applying adjustments and updating contract budgets.

• Importance of accurate financial logs for daily operations.

• 💻 *GitHub and Code Review* (43:15 - 45:34)

• Ryan discusses the GitHub repository and Shane's branch.

• Plan to review Shane's code for better understanding.

• Adding Ahsan and Nick to the GitHub repository.

• 🔄 *Access and Permissions* (45:48 - 47:15)

• Discussion on setting up Ahsan with necessary access to AWS, Typeform, and Data Studio.

• Plan to remove unnecessary users from the system.

• Importance of having the right permissions for smooth operations.

• 🛠️ *Script and Process Improvements* (51:53 - 01:02:27)

• Discussion on making the script dynamic for date calculations.

• Plan to automate the process for better efficiency.

• Importance of reducing manual interventions in daily operations.

• 📅 *Meeting Scheduling and Next Steps* (01:02:32 - 01:12:10)

• Plan to schedule meetings with Luke for process review.

• Discussion on the end goal of automating the financial log process.

• Ryan's commitment to setting up necessary tools and access for Ahsan.

Gist • The meeting aimed to discuss AWS legacy system architecture, code improvements, financial log processes, revenue adjustments, GitHub collaboration, access permissions, script enhancements, and automation plans.

Bullet Gist • 📊 System Architecture Overview: Discussion on old AWS system architecture and data workflow involving WordPress and AWS Lambdas.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-02 14:17:18

• 🔧 Code Improvements and Assignments: Shane's enhancements on old code, media buyer assignments, and contract summarization plans.

• 📝 Morning Routine and Financial Logs: Explanation of morning routine for financial logs and importance of accurate data entry.

• 📈 Adjustments and Revenue Calculation: Cameron's role in revenue adjustments and the process of applying updates.

• 💻 GitHub and Code Review: Discussion on GitHub repository, code review, and adding new members.

Short Summary • The meeting delved into various key topics including a review of the old AWS system architecture, code enhancements by Shane, morning routines for financial logs, revenue adjustments managed by Cameron, GitHub and code review, access permissions, script improvements, and plans for automating financial log processes. Action items included forwarding training materials, setting up access for Ahsan, reviewing code, and updating scripts for efficiency.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-08 13:08:51

Title: Tech Project Status Weekly Date: Mon Jul 08 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, mike@shield-legal.com, nickmcfadden@tortintakeprofessionals.com, luke@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting discussed the status of various tech projects, including setting up a shield Facebook ad CRM funnel event, validating data models, preparing AI dashboards, addressing security and access control issues, and planning for the dialer project and client dashboard. Action items include monitoring logs, clarifying contract issues, setting up meetings for progress reviews, sharing roadmaps, and conducting assessments for various projects.

Action Items • *Mike Everhart*

• Monitor the logs for the shield Facebook ad CRM funnel event setup (01:32)

• *Ryan Vaspra*

• Call Nastasia to address the contract negotiation issues and clarify the requirements and costs (02:21)

• Set up a call with Nastasia if no response is received by tomorrow (04:41)

• Schedule a meeting to review the AI MDL dashboard progress (17:26)

• Set up a meeting to discuss security and access control (29:02)

• *Nick McFadden*

• Validate the model combining copper orders with cross-referenced data for the shield portal (05:52)

• Add Ahsan to the GCP projects as admin for both tip and shield (28:39)

• Prepare a roadmap for the dialer project and share it with the team (30:53)

• *Brian Hurst*

• Set up the shield retool account and import the shield portal template (07:52)

• *James Scott*

• Prepare the AI dashboard with MDL data and analytics (10:04)

• *Luke Fontaine*

• Conduct a Google Data Studio client dashboard assessment and cleanup (31:50)

Shorthand Bullet • 🌐 *Shield Facebook* Ad CRM Funnel Event** (01:32 - 04:41)

• Ryan discusses the setup of the shield Facebook ad CRM funnel event.

• Mike to monitor the logs for the setup.

• Plan to call Nastasia if no response is received regarding contract issues.

• 📊 *Data Model and Shield Portal* (05:52 - 10:04)

• Discussion on validating the model combining copper orders with cross-referenced data.

• Brian to set up the shield retool account and import the shield portal template.

• Plan to prepare the AI dashboard with MDL data and analytics.

• 📅 *AI Dashboard and MDL Data* (10:04 - 17:26)

• James to prepare the AI dashboard with MDL data and analytics.

• Schedule a meeting to review the AI MDL dashboard progress.

• Discussion on predictive impact model and its implementation.

• 🔒 *Security and Access Control* (27:07 - 29:02)

• Nick to add Ahsan to the GCP projects as admin for both tip and shield.

• Plan to set up a meeting to discuss security and access control.

• Discussion on restructuring pipelines and moving to GCP.

• 📞 *Dialer Project and Client Dashboard* (30:09 - 34:41)

• Nick to prepare a roadmap for the dialer project and share it with the team.

• Luke to conduct a Google Data Studio client dashboard assessment and cleanup.

• Discussion on the client portal dashboard and its specifications.

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-08 13:08:51

• The meeting focused on discussing various tech projects and action items related to setting up Facebook ad CRM funnel event, validating data models, preparing AI dashboards, addressing security issues, and planning for the dialer project and client dashboard.

Bullet Gist • 🌐 Shield Facebook Ad CRM Funnel Event: Discussion and setup of the shield Facebook ad CRM funnel event with assigned tasks.

• 📊 Data Model and Shield Portal: Validation of data model, shield portal setup, and AI dashboard preparation discussed.

• 📅 AI Dashboard and MDL Data: Preparation and review of AI dashboard with MDL data, predictive impact model discussion.

• 🔒 Security and Access Control: Enhancements in security and access control, restructuring pipelines, and moving to GCP planned.

• 📞 Dialer Project and Client Dashboard: Planning roadmap for the dialer project, client dashboard assessment, and portal specifications discussed.

Short Summary • The meeting delved into multiple tech projects such as setting up a shield Facebook ad CRM funnel event, validating data models, preparing AI dashboards, addressing security and access control concerns, and planning for the dialer project and client dashboard. Specific action items were assigned, like monitoring logs, clarifying contract issues, setting up progress review meetings, sharing roadmaps, and conducting project assessments. Each project had designated team members responsible for tasks and discussions revolved around key aspects like data validation, security enhancements, and project roadmap sharing.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-08 13:22:08

Title: Integrations from TIP LR to BCL SA for Hair Relaxer URGENT Date: Mon Jul 08 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on the urgent handover of integration tasks from Mike to Ryan for the hair relaxer project with client Ben Crump. The task board was reviewed, client requirements were discussed, task assignments were made, and specifications were clarified with a focus on reporting. The meeting concluded with finalizing details for the integration task and preparing for task tracking. Action items include sharing task details, confirming specifications with Desiree, and moving the task to the appropriate board for tracking.

Action Items • *Ryan Vaspra*

• Share the integration task details with Nick McFadden (09:00)

• Move the integration task to the appropriate board for tracking (14:10)

• *Nick McFadden*

• Confirm with Desiree about the specifications for the integration, especially regarding user-defined fields (UDFs) (10:43)

Shorthand Bullet • 🔄 *Integration Handover* (05:52 - 06:54)

• Ryan Vaspra discusses the handover of integration tasks from Mike Everhart.

• The task is now more urgent due to delays and the importance of the client, Ben Crump.

• 📋 *Task Board* Review** (06:57 - 07:33)

• Ryan and Nick review the DevOps board for integration tasks.

• Nick confirms that his team is maintaining the board.

• 📝 *Client Requirements* (08:23 - 08:59)

• Nick mentions that Desiree has periodically asked about the integration status.

• Desiree is more interested in reporting rather than full integration.

• 📧 *Task Assignment* (09:00 - 10:03)

• Ryan forwards the integration task details to Nick.

• Discussion about existing cases and their statuses.

• 🔍 *Specification Clarification* (10:43 - 11:20)

• Ryan advises Nick to confirm specifications with Desiree.

• Nick mentions Desiree's focus on total leads and their current status.

• ✅ *Task Finalization* (12:13 - 13:03)

• Ryan and Nick finalize the details for the integration task.

• Ryan takes a screenshot for documentation.

• 📂 *Task Tracking* (13:56 - 14:13)

• Ryan prepares to move the task to the appropriate board.

• Nick agrees with the plan.

Gist • The meeting focused on urgent handover of integration tasks from Mike to Ryan for the hair relaxer project with client Ben Crump.

Bullet Gist • 🔄 Integration Handover: Ryan discusses urgent handover of integration tasks from Mike due to client importance.

• 📋 Task Board Review: Ryan and Nick review the DevOps board for integration tasks with Nick confirming maintenance.

• 📝 Client Requirements: Desiree focuses on reporting rather than full integration, prompting periodic status inquiries.

• 📧 Task Assignment: Ryan forwards integration task details to Nick, discussing existing case statuses.

• 🔍 Specification Clarification: Ryan advises Nick to confirm specifications with Desiree, highlighting her interest in total leads status.

Short Summary • The meeting centered on the critical handover of integration tasks from Mike to Ryan for the hair relaxer project with client Ben Crump. Discussions included task board review, client requirements emphasizing reporting, task assignments, specification clarification, finalizing task details, and preparing for task tracking.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-11 10:57:50

Title: BLX SEO Clients Date: Thu Jul 11 2024 11:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, korbin@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The meeting focused on technical setup and issues, SEO progress, new data review, Google Search Console insights, crawl errors and optimization, and an investigation into an algorithm change that benefited Ben Crump's SEO performance. Key points included resolving audio setup issues, reducing 'title too long' issues in WordPress, improving SEO for better Google ranking, reviewing SEO data, noting a 6% increase in search visibility and traffic, improving homepage ranking from position 35 to 19, and investigating the May algorithm change. Action items assigned to Korbin included summarizing the algorithm change that benefited Ben Crump's SEO performance.

Action Items • *Korbin Mantel*

• Investigate and summarize the May algorithm change that benefited Ben Crump's SEO performance (21:41)

Shorthand Bullet • 🔧 *Technical Setup and Issues* (00:20 - 02:12)

• Ryan and Korbin discuss audio setup issues and resolve them.

• Korbin is working on reducing 'title too long' issues in WordPress.

• SEO issues include missing keywords and meta descriptions.

• 📊 *SEO Progress and Challenges* (02:13 - 03:05)

• Korbin is marking SEO issues as complete, but Moz shows high numbers due to delayed crawling.

• Moz takes about eight days to crawl the site; manual crawl might be needed.

• Ryan and Korbin discuss the importance of reducing SEO issues for better Google ranking.

• 🏠 *New Place and Data Review* (04:20 - 07:10)

• Ryan mentions adjusting to a new place.

• Ryan reviews SEO data and shares insights with Korbin.

• Ryan notes a 6% increase in search visibility and traffic for Ben Crump's site.

• 📈 *Google* Search Console Insights** (07:38 - 14:29)

• Ryan reviews Google Search Console data for Ben Crump's site.

• Homepage ranking improved from position 35 to 19, a 45% improvement.

• Non-branded keywords click-through rate increased from 0.44% to 0.6%, a 50% improvement.

• 🛠️ *Crawl Errors and Optimization* (15:50 - 21:17)

• Korbin and Kelly are focusing on 'title too long' issues.

• Final 400 crawl errors from historical press releases and articles are almost complete.

• Ryan exports data from Google Search Console for further analysis.

• 🔍 *Algorithm Change Investigation* (21:41 - 23:08)

• Ryan asks Korbin to investigate the May algorithm change that benefited Ben Crump's SEO.

• Korbin mentions Neil Patel as a potential source for information.

• Ryan emphasizes the importance of understanding the algorithm change for better SEO strategy.

Gist • Meeting focused on technical setup, SEO progress, data review, Google Search Console insights, crawl errors, and investigating an algorithm change benefiting SEO performance.

Bullet Gist • 🔧 Technical Setup and Issues: Resolved audio setup issues and worked on 'title too long' problems in WordPress.

• 📊 SEO Progress and Challenges: Discussed the importance of reducing SEO issues for better Google ranking.

• 🏠 New Place and Data Review: Reviewed SEO data, noted a 6% increase in search visibility for Ben Crump's site.

• 📈 Google Search Console Insights: Homepage ranking improved, non-branded keywords click-through rate increased.

• 🛠️ Crawl Errors and Optimization: Focused on resolving 'title too long' issues and analyzing Google Search Console data.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-11 10:57:50

• The meeting delved into technical setup and issues where Ryan and Korbin resolved audio setup and worked on reducing 'title too long' issues in WordPress. They discussed SEO progress, highlighted the importance of reducing SEO issues for improved Google ranking, and noted a 6% increase in search visibility for Ben Crump's site. Google Search Console insights revealed homepage ranking improvement and increased click-through rates. The team also addressed crawl errors and optimization, focusing on resolving 'title too long' issues and analyzing Google Search Console data. An investigation into an algorithm change benefiting Ben Crump's SEO was initiated by Ryan, emphasizing the need to understand the change for a better SEO strategy.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-12 10:34:51

Title: Media Buyer performance Date: Fri Jul 12 2024 11:15:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting discussed Ryan's completion of software development tasks related to data management, communication issues with a developer, and the importance of managing financial and performance metrics for LSAs. Action items were assigned to Ryan to finish deploying jobs and create a table, and to Lee to follow up with Markowitz, report to Cameron on LSAs, and educate on profitability maintenance. The emphasis was on effective management of LSAs to prevent neglect.

Action Items • *Ryan Vaspra*

• Finish the pull request merge and deploy jobs to BigQuery (00:02)

• Create a table with 127 columns mixed by four tables of significant information for shield (03:29)

• Add LP contract ids, LP vertical ids, and LLP id string to the table (03:29)

• *Lee Zafra*

• Keep the ticket open with evident Markowitz and follow up every couple of days (15:56)

• Report to Cameron and manage the pacing and lead volume for LSAs (17:17)

• Educate Cameron on managing LSAs and maintain profitability in the 25% to 40% range (17:17)

• Ensure LSAs are managed effectively and not neglected (21:10)

Shorthand Bullet • 💻 *Software Development* and Data Management** (00:02 - 03:29)

• Ryan completed the pull request merge and deployed jobs to BigQuery.

• Created a table with 127 columns mixed by four tables of significant information for shield.

• Added LP contract ids, LP vertical ids, and LLP id string to the table.

• 📞 *Communication and *Follow-ups** (03:29 - 15:56)

• Ryan expressed frustration over a developer not naming fields accordingly, causing extra work.

• Lee and Ryan discussed the importance of following up with Tony Jones and evident Markowitz.

• Lee was tasked to keep the ticket open with evident Markowitz and follow up every couple of days.

• 📊 *Financial and Performance Metrics* (17:17 - 21:10)

• Ryan explained to Lee the importance of managing the pacing and lead volume for LSAs.

• Lee was advised to educate Cameron on managing LSAs and maintaining profitability in the 25% to 40% range.

• Ryan emphasized the need to ensure LSAs are managed effectively and not neglected.

Gist • The meeting focused on software development tasks completion, communication issues, and managing financial metrics for LSAs.

Bullet Gist • 💻 Software Development and Data Management: Ryan completed pull request merge, deployed jobs to BigQuery, and created a table with essential information.

• 📞 Communication and Follow-ups: Issues with developer's field naming caused extra work; task assigned to follow up with specific individuals.

• 📊 Financial and Performance Metrics: Importance of managing LSAs' pacing, lead volume, and profitability emphasized.

Short Summary • The meeting revolved around Ryan's completion of software development tasks related to data management, addressing communication challenges with a developer, and stressing the importance of managing financial and performance metrics for LSAs. Action items assigned included finishing job deployment, creating a comprehensive table, following up with specific individuals, and educating on profitability maintenance to prevent neglect of LSAs. Key points covered Ryan's progress in merging pull requests, creating a detailed table, communication frustrations, financial metric management, and the significance of effective LSA management.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-12 14:17:28

Title: Rob / James Date: Fri Jul 12 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: jamesscott@shield-legal.com, robl@unicourt.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the meeting between Rob and James, they discussed adjusting the query for MDL court, making technical corrections in the code, summarizing MDL cases by extracting sub-cases and their locations, and sharing pseudocode. James has action items to move the query, make corrections, and summarize MDL cases, while Rob will send the pseudocode and relevant queries via email.

Action Items • *James Scott*

• Move the query for MDL court to the correct location in the code (02:12)

• Remove the colon and adjust the spacing in the query for court system id (03:12)

• Paste the corrected line of code in the chat for Rob to review (03:43)

• Summarize MDL cases by extracting sub-cases and their locations (04:18)

• *Rob Lynch*

• Send the pseudocode and relevant queries to James via email (12:48)

Shorthand Bullet • 🔍 *Discussion on Query Adjustments* (00:09 - 02:12)

• James and Rob discussed the need to adjust the query for MDL court.

• Rob suggested moving the query to the correct location in the code.

• James acknowledged the mistake and agreed to make the changes.

• 💡 *Technical Corrections* (03:08 - 03:43)

• Rob guided James on removing the colon and adjusting the spacing in the query for court system id.

• James pasted the corrected line of code in the chat for Rob to review.

• 📊 *Summarizing MDL Cases* (04:18 - 11:59)

• James explained his goal to summarize MDL cases by extracting sub-cases and their locations.

• Rob clarified that MDL cases are made up of multiple sub-cases in different locations.

• Rob demonstrated how to get the list of sub-cases and their details using specific queries.

• 📧 *Sharing Pseudocode* (12:48 - 14:05)

• Rob agreed to send the pseudocode and relevant queries to James via email.

• James confirmed that he would test the code and follow up if needed.

Gist • The meeting focused on adjusting the query for MDL court, making technical corrections in the code, summarizing MDL cases by extracting sub-cases and locations, and sharing pseudocode.

Bullet Gist • 🔍 Query Adjustments: Discussion on adjusting the query for MDL court and moving it in the code.

• 💡 Technical Corrections: Guidance on technical corrections in the code for court system id.

• 📊 Summarizing MDL Cases: Explanation and demonstration of summarizing MDL cases by extracting sub-cases and locations.

• 📧 Sharing Pseudocode: Agreement to send pseudocode and relevant queries via email for testing.

Short Summary • During the meeting, Rob and James discussed adjusting the query for the MDL court, making technical corrections in the code, summarizing MDL cases by extracting sub-cases and their locations, and sharing pseudocode. Rob suggested moving the query in the code, guided James on technical corrections, explained the concept of MDL cases and sub-cases, and agreed to send pseudocode to James via email for further testing.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-18 11:09:16

Title: JA - mid month commission review Date: Thu Jul 18 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: jack@themedialab.agency, cameron@themedialab.agency, ryan@themedialab.agency, ryan@brandlytics.io, debora@shield-legal.com, altonese@accountingdept.net, brian@accountingdept.net, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • During the mid-month commission review meeting, Ryan and Jack discussed the commission report, with Jack receiving a total commission of $89,440 for the quarter, including a bonus. They also discussed the impact of gaming referrals and shared personal updates, with Jack mentioning his recent vacation to Cabo San Lucas. Cameron was tasked with reviewing and approving the commission report for the month.

Action Items • *Cameron*

• Review and approve the commission report for the month (06:36)

Shorthand Bullet • 📊 *Commission Review* (04:11 - 05:36)

• Ryan and Jack discussed the commission report for the month.

• Total revenue for the quarter was $3 million.

• Jack's commission amounted to $74,440 with a bonus commission of $15,000, totaling $89,440.

• Ryan suggested Jack consider purchasing a permanent condominium in Cabo.

• 🎮 *Gaming Referrals* (05:36 - 06:11)

• Ryan noted the high number of referrals coming in, particularly related to gaming.

• Discussion on the impact of gaming on children and the unexpected surge in referrals.

• ✈️ *Travel and Personal Updates* (02:00 - 03:50)

• Jack shared details about his vacation in Cabo San Lucas.

• Ryan and Jack exchanged personal updates and travel experiences.

Gist • The meeting was held to review the commission report, discuss gaming referrals, and share personal updates.

Bullet Gist • 📊 Commission Review: Ryan and Jack reviewed the commission report, with Jack earning $89,440 for the quarter including a bonus.

• 🎮 Gaming Referrals: Discussion on the impact of gaming referrals and the surge in referrals.

• ✈️ Travel and Personal Updates: Jack shared about his vacation in Cabo San Lucas.

Short Summary • During the mid-month commission review meeting, Ryan and Jack discussed the commission report, with Jack receiving a total commission of $89,440 for the quarter, including a bonus. They also talked about the impact of gaming referrals, especially on children, and shared personal updates, including Jack's recent vacation to Cabo San Lucas. Cameron was assigned to review and approve the commission report for the month.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-18 11:24:16

Title: JV - mid month commission review Date: Thu Jul 18 2024 12:15:00 GMT-0400 (Eastern Daylight Time) Participants: cameron@themedialab.agency, ryan@shield-legal.com, john@themedialab.agency, ryan@brandlytics.io, brian@accountingdept.net, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting focused on the mid-month commission review for the joint venture, with discussions centered around ad accounts and business managers. Ryan and Brian talked about the involvement of John and Cameron in managing ad accounts, including Cameron's red flag on his account due to extensive advertising activities. Ryan manages ad accounts for Cameron, who often has ad copy suspended on Facebook. Action items included Ryan sending pre-written emails regarding ad accounts and business managers.

Action Items • *Ryan Vaspra*

• Send the pre-written emails regarding the ad accounts and business managers (05:39)

Shorthand Bullet • 📊 *Discussion on Ad Accounts and Business Managers* (01:52 - 05:35)

• Ryan and Brian discussed the involvement of John and Cameron in managing ad accounts.

• John brought Cameron the remote multi-user login (RML) system.

• Ryan explained the use of Facebook profiles for managing business managers and ad accounts.

• Cameron has a red flag on his account due to extensive advertising activities.

• Ryan manages ad accounts for Cameron, including those under shieldlegalnetwork.com and usaconsumernetwork.com.

• Cameron's ad copy often gets suspended on Facebook due to its borderline nature.

• Ryan spends a significant portion of his day managing Facebook ad accounts.

• Natito is crucial for resolving ad account suspensions and ensuring scalability.

Gist • The meeting focused on mid-month commission review for the joint venture, discussing ad accounts and business managers.

Bullet Gist • 📊 Discussion on Ad Accounts and Business Managers: Ryan and Brian discussed John and Cameron's involvement in managing ad accounts.

• 📌 Cameron's Account Red Flag: Cameron has a red flag on his account due to extensive advertising activities.

• 💼 Ryan's Management: Ryan manages ad accounts for Cameron, including shieldlegalnetwork.com and usaconsumernetwork.com.

• ⚠️ Ad Copy Suspension: Cameron's ad copy often gets suspended on Facebook due to its borderline nature.

• ⏰ Time Allocation: Ryan spends a significant portion of his day managing Facebook ad accounts.

Short Summary • The meeting revolved around reviewing commissions for the joint venture, specifically focusing on ad accounts and business managers. Ryan and Brian discussed John and Cameron's roles in managing ad accounts, highlighted Cameron's account red flag due to extensive advertising, and detailed the challenges with ad copy suspension on Facebook. Action items included sending pre-written emails about ad accounts and business managers.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-18 11:37:48

Title: ML - mid month commission review Date: Thu Jul 18 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: maximus@themedialab.agency, cameron@themedialab.agency, ryan@shield-legal.com, ryan@brandlytics.io, brian@accountingdept.net, briant@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • The meeting was titled "ML - mid month commission review" where key points included a quiet and focused workday with Ryan being productive and Cameron's paid vs. spent table being praised. The commission for June was reviewed, totaling $27,737 with $1.3 million in revenue. A $5,000 bonus was confirmed, resulting in a total of $32,773.28 with agreement from Maximus. Action item for Ryan is to review and finalize the paid vs. spent table.

Action Items • *Ryan Vaspra*

• Review and finalize the paid vs. spent table built by Cameron (04:24)

Shorthand Bullet • 🔇 *Quiet and Focused Workday* (04:05 - 04:24)

• Ryan had a very focused and quiet day by muting his phone and ignoring Slack and email.

• Cameron's paid vs. spent table was built and found to be powerful.

• 💰 *Commission Review* (04:49 - 05:06)

• Reviewed commission for June: $27,737 plus $1.3 million in revenue.

• Confirmed a $5,000 bonus, totaling $32,773.28.

• Maximus agreed with the figures.

Gist • Meeting focused on ML commission review with Ryan's productivity and Cameron's table praised, confirming a $5,000 bonus and total earnings of $32,773.28.

Bullet Gist • 🔇 Quiet and Focused Workday: Ryan had a productive day by muting distractions and Cameron's table was commended.

• 💰 Commission Review: June's commission totaled $27,737 with $1.3 million revenue, confirmed a $5,000 bonus, reaching $32,773.28.

Short Summary • The meeting centered on reviewing the mid-month ML commission, highlighting Ryan's productive workday and Cameron's effective paid vs. spent table. The commission for June amounted to $27,737 along with $1.3 million in revenue, culminating in a confirmed $5,000 bonus and total earnings reaching $32,773.28. Maximus supported the figures, and Ryan was tasked with finalizing the paid vs. spent table.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-18 13:33:38

Title: Brandlytics/ Kinnari Date: Thu Jul 18 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kinnaris@google.com Transcript: See full transcript Audio: Listen to audio Duration: 20

Overview • The meeting between Brandlytics and Kinnari covered small world connections, company overview and AI implementation, data security and compliance, current projects and IT budget, as well as scheduling next steps. Key points included discussions on Google Cloud adoption, data security in Bigquery, Medpalm AI for security and compliance, and IT budget allocation. Action items include sharing IT budget details, setting up a meeting with the account executive, and exploring the use of Medpalm AI and Vertex AI.

Action Items • *Kinnari Shetty*

• Send resources on Medpalm AI to Ryan for potential use in legal and medical implementations (11:22)

• Set up a meeting with the account executive, Tyler, to discuss data security and compliance, including Medpalm and Vertex AI (26:32)

• *Ryan Vaspra*

• Prepare and share the IT budget details with Kinnari for compliance purposes (22:23)

• Discuss the potential use of Medpalm AI and Vertex AI with Nick McFadden and prepare for the upcoming meeting with Tyler (26:32)

Shorthand Bullet • 🌍 *Small World Connections* (00:01 - 01:13)

• Ryan shares a story about meeting someone from London.

• Kinnari mentions a similar experience.

• 🏢 *Company Overview and AI Implementation* (02:32 - 05:22)

• Ryan explains Brandlytics' adoption of Google Cloud and Looker Enterprise.

• Discussion on the company's different systems and their functions.

• Introduction of a new AI project for market prediction.

• 🔒 *Data Security and Compliance* (10:39 - 12:50)

• Ryan discusses the need for data security in Bigquery.

• Kinnari suggests Medpalm AI for security and compliance.

• Plan to involve Nick McFadden in the next call with the account executive.

• 📊 *Current Projects and IT Budget* (19:05 - 22:23)

• Ryan talks about ongoing projects and the integration of AWS and Google Cloud.

• Discussion on the IT budget and its allocation.

• Ryan mentions the need for security enhancements.

• 📅 *Scheduling Next Steps* (26:32 - 31:45)

• Plan to set up a meeting with the account executive, Tyler.

• Discussion on the best time for the meeting.

• Ryan and Kinnari finalize the meeting details.

Gist • The meeting focused on small world connections, company overview, AI implementation, data security, current projects, and IT budget, with actions planned for Google Cloud adoption, Medpalm AI usage, and meeting with the account executive.

Bullet Gist • 🌍 Small World Connections: Ryan and Kinnari shared experiences of meeting people from around the world.

• 🏢 Company Overview and AI Implementation: Discussion on Brandlytics' Google Cloud adoption and new AI project for market prediction.

• 🔒 Data Security and Compliance: Focus on data security in Bigquery and the suggestion of Medpalm AI for compliance.

• 📊 Current Projects and IT Budget: Updates on ongoing projects, IT budget allocation, and the need for security enhancements.

• 📅 Scheduling Next Steps: Planning to meet with the account executive, Tyler, and finalizing meeting details.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-18 13:33:38

• The meeting between Brandlytics and Kinnari covered various key topics including small world connections shared by Ryan and Kinnari, Brandlytics' adoption of Google Cloud and Looker Enterprise for AI implementation, discussions on data security in Bigquery and the recommendation of Medpalm AI, updates on current projects, IT budget allocation, and plans to schedule a meeting with the account executive, Tyler. Action items included sharing IT budget details, exploring Medpalm AI and Vertex AI, and setting up a meeting with the account executive.

Ryan (ryan@themedialab.agency)
2024-07-19 16:12:22

Remove Korbin from SharpSpring.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-24 12:28:24

Title: Organic Lead Contracts Date: Wed Jul 24 2024 13:15:00 GMT-0400 (Eastern Daylight Time) Participants: kelly@brandlytics.io, markmaniora@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Overview • During the Operational Transition Meeting for Organic Lead Contracts, key points were discussed such as Staffing Changes and Role Reassignment, Marketing Automation Tasks, Additional Responsibilities, and Next Steps and Training. Action items were assigned to Mark Maniora and Brian to ensure a smooth transition and successful management of responsibilities. Mark is to take over marketing automation tasks, learn to set up tracking numbers, get trained on creating Zapiers, manage daily lead counting, and gain access to the Yext platform. Brian will train Mark on new responsibilities next week and ensure he has access to necessary channels and systems.

Action Items • *Mark Maniora*

• Take over marketing automation responsibilities for clients (06:04)

• Learn to set up tracking numbers in Call Tracking Metrics (06:04)

• Get trained on creating Zapiers for data transfer (09:08)

• Start managing daily lead counting in spreadsheet (10:28)

• Gain access to and familiarize with Yext platform (10:28)

• *Brian*

• Train Mark on new responsibilities next week (11:49)

• Get Mark into necessary channels and systems (11:49)

Shorthand Bullet • 🔄 *Staffing Changes and Role Reassignment* (04:02 - 06:04)

• Corbin's position as email service provider terminated

• Mark to take over Corbin's responsibilities for marketing automation clients

• 📊 *Marketing Automation Tasks* (06:04 - 09:08)

• Building lead generation contracts for clients like Cello Focus, Litigation Solution

• Setting up tracking numbers in Call Tracking Metrics

• Routing calls to Conex One paralegal team or Vin Crump intake agent

• Creating Zapiers for data transfer from Survey Monkey to HubSpot

• 📈 *Additional Responsibilities* (09:08 - 11:49)

• Managing Focus Litigation Solutions' upcoming projects

• Daily lead counting in spreadsheet from Law Ruler

• Overseeing Yext platform for SEO and lead flow management

• 🗓️ *Next Steps and Training* (11:49 - 12:10)

• Brian to train Mark on new responsibilities next week

• Mark off for the next two days

Gist • The meeting focused on operational transition for lead contracts, discussing staffing changes, role reassignment, marketing automation tasks, additional responsibilities, and training plans.

Bullet Gist • 🔄 Staffing Changes and Role Reassignment: Corbin's position terminated, Mark to assume marketing automation duties.

• 📊 Marketing Automation Tasks: Building contracts, setting up tracking numbers, creating Zapiers.

• 📈 Additional Responsibilities: Managing projects, daily lead counting, overseeing Yext platform.

• 🗓️ Next Steps and Training: Brian to train Mark on new responsibilities, Mark off for two days.

Short Summary • The Operational Transition Meeting for Organic Lead Contracts delved into critical areas such as Staffing Changes and Role Reassignment, Marketing Automation Tasks, Additional Responsibilities, and Next Steps and Training. Mark Maniora is set to take over marketing automation duties and learn new tasks, while Brian will facilitate training and ensure smooth handover. Specific responsibilities like managing projects, lead counting, and platform oversight were outlined, with a clear plan for Mark's training and access to essential systems.

Ryan (ryan@themedialab.agency)
2024-07-24 12:51:19
File
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-25 14:52:06

Title: BCL Next Steps Date: Thu Jul 25 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The Status update and strategy discussion meeting focused on BCL's next steps, covering topics such as website publishing and SEO optimization, improving attorney page visibility, Google search results and locations, SEO performance and organic campaigns, Yext implementation and benefits, team growth, office space, and personal updates. Action items included adding attorney links to the website footer, contacting a partner firm for New Jersey cases, focusing on local birth injury content, and exploring a potential office move.

Action Items • *Ryan*

• Ryan to make adding attorney link to footer an action item (04:14)

• Ryan to text John about partner preference for New Jersey cases (07:16)

• *unassigned*

• SEO team to focus on local birth injury content (08:17)

• *Desiree*

• Desiree to contact Tony for information about potential office move (15:36)

Shorthand Bullet • 🌐 *Website Publishing and SEO* (00:05 - 04:19)

• Latoya and team averaging one press release per day

• Press releases optimized for SEO with 99 keyword grade

• Strategy to improve attorney page visibility in Google search results

• Suggestion to add attorney link to footer and increase internal linking

• 📊 *Google* Search Results and Locations** (04:19 - 05:37)

• Discussion about Google search results showing different office locations based on user's geography

• Explanation of how Google integrates various products in search results

• 🚀 *SEO Performance and Organic Campaigns* (05:37 - 08:48)

• Website performing well with 50,000 links

• High rankings for auto accident-related searches

• Organic pages being created for New Jersey and Pennsylvania

• Discussion about which partner firm to use for New Jersey cases

• Focus on local birth injury content

• 📡 *Yext Implementation and Benefits* (10:08 - 13:30)

• Yext software implemented for managing online directories

• Presence on 120+ directories including Google, Apple Maps, Yelp

• 58 leads generated in 4 weeks from Yext listings

• Expectation of 200-300 organic leads per month from Yext

• 👥 *Team Growth and Office Space* (13:30 - 16:23)

• Desiree's team currently has 9 people, including an intern

• Plans to hire more case managers, call managers, and paralegals

• Discussion about potential office move to a new, larger building

• 🏠 *Personal Updates and Relocation* (16:23 - 19:45)

• Ryan relocating to Tulsa, Oklahoma for family reasons

• Discussion about cost of living differences between states

• Brief chat about state friendliness rankings

Gist • The meeting focused on discussing BCL's next steps, including website publishing, SEO optimization, attorney page visibility, Google search results, Yext implementation, team growth, office space, and personal updates.

Bullet Gist • 🌐 Website Publishing and SEO: Latoya and team excelling in press releases and SEO strategies.

• 📊 Google Search Results and Locations: Discussion on Google search results showing different office locations.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-25 14:52:06

• 🚀 SEO Performance and Organic Campaigns: Successful SEO performance with high rankings for auto accident-related searches.

• 📡 Yext Implementation and Benefits: Yext generating leads and presence on 120+ directories.

• 👥 Team Growth and Office Space: Plans to hire more staff and potential office move.

Short Summary • The meeting delved into various key areas such as website publishing and SEO optimization, with Latoya and the team excelling in press releases and SEO strategies, Google search results and locations discussion, successful SEO performance and organic campaigns including local birth injury content focus, Yext implementation benefits generating leads, team growth plans, and personal updates like Ryan's relocation to Tulsa, Oklahoma for family reasons. Action items ranged from website improvements to potential office relocation.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-29 11:10:41

Title: BLX Media Buying Date: Mon Jul 29 2024 11:30:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, markmaniora@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The BLX Media Buying Operations and Reporting Review meeting focused on several critical areas, including campaign tracking, call metrics, dashboard analysis, and lead classification. Ryan shared a confidential spreadsheet for tracking both organic and paid campaigns, highlighting the need for updates to qualified leads and case reviews. The team reviewed lead counting methods using Call Tracking Metrics, specifically regarding the Chicago campaign, where 159 unique leads were identified. Discrepancies between case reviews and signed cases were discussed, emphasizing the importance of accurate lead counting. Additionally, the team outlined weekly tasks for updating lead counts and explored the potential for automating the tracking process, while addressing budget adjustments for ongoing campaigns. Action items were assigned, including updating the tracking spreadsheet, learning Call Tracking Metrics, and preparing for upcoming marketing automation discussions.

Action Items • *Mark Maniora*

• Update columns U and V in the tracking spreadsheet with qualified leads/case reviews (01:51)

• Perform Monday morning task of updating lead counts before 9 AM (32:31)

• Learn Call Tracking Metrics basics (07:23)

• *Ryan Vaspra*

• Set up time to go over New Jersey testing for marketing automation (24:28)

• Pull spreadsheet from Smart Advocate for SEO meeting next week (29:39)

• Show Mark how to get all phone calls counted in LeadsPDF (35:41)

• *Lee Zafra*

• Continue managing column J and keeping an eye on column K in the tracking spreadsheet (34:02)

Shorthand Bullet • 📊 *Campaign Tracking and Reporting* (00:00 - 09:39)

• Ryan shared a confidential spreadsheet for tracking BLX organic and paid campaigns

• Mark to update columns U and V with qualified leads/case reviews

• Discussed accessing TIP dashboard for billable leads data

• Filtering process for active campaigns and paused/canceled campaigns explained

• 📞 *Call Tracking Metrics and Lead Counting* (09:44 - 20:48)

• Ryan demonstrated using Call Tracking Metrics for lead counting

• Focused on Chicago campaign: 159 unique leads counted

• Process of updating spreadsheet and sending invoices explained

• Lee responsible for filling out specific columns in the tracking sheet

• 📄 *Dashboard Analysis and Case Reviews* (20:57 - 28:41)

• Analyzed billable leads dashboard for signed cases

• Discussed discrepancies between case reviews and signed cases

• Reviewed various campaigns: Camp Lejeune, Drax global, clergy abuse, etc.

• Importance of accurate lead counting emphasized

• 🔍 *Lead Classification and Weekly Tasks* (29:12 - 37:49)

• Explained difference between case reviews and signed cases

• Discussed Monday morning task of updating lead counts before 9 AM

• Potential for automating the tracking process in the future

• Reviewed organic and paid lead generation campaigns

• Discussed budget adjustments for ongoing campaigns

Gist • The meeting focused on improving campaign tracking and lead classification for BLX Media.

Bullet Gist • 📊 Campaign Tracking Overview: Ryan shared a confidential spreadsheet to track BLX's organic and paid campaigns.

• 📞 Lead Counting Insights: 159 unique leads were identified from the Chicago campaign using Call Tracking Metrics.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-29 11:10:41

• 📄 Dashboard Analysis: Discrepancies between case reviews and signed cases were discussed to improve accuracy.

• 🔍 Weekly Updates: The team outlined tasks for updating lead counts weekly and explored automation options.

• 💰 Budget Adjustments: The meeting addressed necessary budget adjustments for ongoing campaigns.

Short Summary • The BLX Media Buying Operations and Reporting Review meeting addressed crucial aspects of campaign tracking, call metrics, and lead classification. Ryan presented a confidential spreadsheet for monitoring both organic and paid campaigns, highlighting the necessity for updates related to qualified leads and case reviews. The team evaluated lead counting methods using Call Tracking Metrics, particularly analyzing the Chicago campaign, which identified 159 unique leads. They discussed discrepancies between case reviews and signed cases, underscoring the importance of accurate lead counting. Additionally, weekly tasks for updating lead counts were outlined, and the potential for automating tracking processes was explored, alongside budget adjustments for ongoing campaigns. Action items included updating the tracking spreadsheet, familiarizing with Call Tracking Metrics, and preparing for upcoming discussions on marketing automation.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-30 11:30:35

Title: Tech Project Status Weekly Date: Tue Jul 30 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the Tech Project Status Weekly meeting, the team discussed various project updates and priorities including Brian's progress on the tip dashboard, which is essential for pricing management, and Ryan's ongoing work on the paid vs. spent dashboard and a client-sided dashboard. The shield legal portal was identified as a critical priority. Additionally, James provided updates on the data pipeline in BigQuery, emphasizing the integration of prediction algorithm results and aiming for completion to allow for visualization. The team engaged in discussions about the iterative process for improving the prediction model and the importance of stakeholder feedback on algorithm weights. Personal updates included Ryan's move to Tulsa and James's long-term plans in Florida. Key action items were set, notably for Brian to finalize the tip dashboard for review by Friday, James to complete the data pipeline, and Ryan to arrange a review meeting and plan travel for potential meetings in Vegas early September.

Action Items • *Brian Hirst*

• Finish the milestone for the tip dashboard, making it usable for Tony and team to update prices (16:03)

• Aim to have the tip dashboard ready for review by Friday morning (16:33)

• Work on the shield portal alongside the tip dashboard (15:01)

• *James Scott*

• Complete the data pipeline and add visualization for stakeholder review (20:12)

• Continue adjusting the prediction algorithm (20:12)

• Check availability for potential Vegas meetings in early September (28:16)

• *Ryan Vaspra*

• Set up a review meeting for Friday morning to check Brian's progress on the tip dashboard (16:31)

• Work on recreating James' dashboards in Looker Enterprise (21:08)

• Confirm meeting dates and arrange travel details for Vegas meeting (28:16)

Shorthand Bullet • 🚀 *Project Updates and Priorities* (02:01 - 14:33)

• Brian working on tip dashboard, facing some challenges

• Ryan explained the importance of the tip dashboard for pricing management

• Shield legal portal identified as critical priority

• Ryan working on paid vs spent dashboard for two weeks

• Mark has fully adopted Looker Enterprise

• Ryan aims to finish client-sided dashboard

• 💻 *Dashboard Development* and Data Pipeline** (14:33 - 23:14)

• James working on data tables in BigQuery

• Prediction algorithm results being added to data tables

• James aims to complete pipeline today for visualization

• Ryan plans to recreate dashboards in Looker Enterprise

• Discussion about iterative process for prediction model improvement

• Ryan suggests getting feedback from stakeholders on algorithm weights

• 🏠 *Personal Updates and Future Plans* (23:14 - 29:36)

• Ryan moved to Tulsa full-time due to family reasons

• James expressing interest in staying in Florida long-term

• Discussion about real estate markets in different locations

• Planning for potential meetings in Vegas in early September

Gist • The meeting focused on project updates and priorities, including dashboard progress and critical action items.

Bullet Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-30 11:30:35

• 📊 Dashboard Progress: Brian and Ryan provided updates on the tip and paid vs. spent dashboards, both crucial for pricing and client insights.

• ⚖️ Critical Priorities: The shield legal portal was highlighted as a pressing priority for the team.

• 📈 Data Pipeline Updates: James updated the team on the BigQuery data pipeline, focusing on integrating prediction algorithms.

• 💬 Stakeholder Feedback: Discussion emphasized the importance of stakeholder feedback for refining prediction models.

• 🔑 Action Items Set: Key tasks were assigned, including finalizing dashboards and planning travel for upcoming meetings.

Short Summary • During the Tech Project Status Weekly meeting, the team discussed several important project updates and priorities. Brian provided an update on the tip dashboard, critical for pricing management, while Ryan shared his ongoing work on the paid vs. spent dashboard and a client-sided dashboard. The shield legal portal emerged as a key priority. James highlighted progress on the data pipeline in BigQuery, emphasizing the integration of prediction algorithm results and the goal of completion for data visualization. The team also discussed the iterative process for enhancing the prediction model and the significance of stakeholder feedback on algorithm weights. Personal updates included Ryan's recent relocation to Tulsa and James's long-term plans in Florida. Key action items were assigned, including Brian finalizing the tip dashboard by Friday, James completing the data pipeline, and Ryan organizing a review meeting and planning travel for potential meetings in Vegas in early September.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-30 13:48:10

Title: SL Database Maintenance Date: Tue Jul 30 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, luke@shield-legal.com, nickmcfadden@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The SL Database Maintenance meeting focused on resolving several technical issues and optimizing processes. Key discussions included Nick's successful fix of a divide by zero error in the Lambda code, the deletion and resubmission of certain spins, and Luke's ongoing work on financials. The team addressed challenges with Google rate limiting impacting Power Automate, identifying a temporary solution with a new Gmail account while considering potential API adjustments. Access management was discussed, emphasizing the need for a general Shield account, currently overseen by Mike. The team explored utilizing a data warehouse for email parsing, weighing event-driven architecture against batch processing. Conversations also covered the timeline for integrating Law Ruler and the impact of upcoming travel on development priorities. Lastly, a 5-minute data processing pipeline was agreed upon, allowing for the pulling of 1,000 records at a time, with Nick set to enhance the data pipeline for financial dashboards as part of the follow-up action items.

Action Items • *Nick McFadden*

• Implement 5-minute pipeline function pulling 1000 records at a time (48:59)

• Work on inbox data pipeline for financial dashboards (48:59)

• Continue efforts to fix Power Automate issues (27:37)

• *unassigned*

• Reset password for Rahat@shield.com Google Workspace account (34:57)

• Create a general Shield account accessible to all team members (34:57)

Shorthand Bullet • 🛠️ *Lambda Fix and Data Issues* (00:26 - 26:05)

• Nick fixed a divide by zero issue in Lambda code

• Deleted and resubmitted Caleb's spins without New Jersey data

• Luke is back working on Cameron's financials

• 🔌 *Power Automate and API Issues* (27:37 - 33:17)

• Discussed Google rate limiting issue affecting Power Automate

• Created new Gmail account as temporary solution

• Explored options for API credentials and connectors

• Considered rebuilding flows or transferring to new Power Automate instance

• 🔑 *Account Access and Management* (34:57 - 36:28)

• Discussed need for general Shield account accessible to all team members

• Mike currently manages Google Workspace

• Nick has full admin access to Google Cloud

• 📊 *Data Pipeline and Warehouse Discussion* (37:58 - 42:17)

• Explored using data warehouse for email parsing and trigger events

• Discussed pros and cons of event-driven architecture vs. batch processing

• Considered eliminating Gmail and Power Automate in favor of data warehouse pipelines

• 🚀 *Law Ruler Integration and Development Priorities* (43:35 - 47:45)

• Discussed timeline for Law Ruler inbox and intake pipeline development

• Acknowledged delays due to integration work

• Considered working on development during London trip

• Cameron not attending London trip

• ⏱️ *Data Processing and Pipeline Implementation* (48:59 - 51:16)

• Agreed on implementing 5-minute pipeline function pulling 1000 records at a time

• Discussed de-duping process and raw database table creation

• Nick to work on inbox data pipeline for financial dashboards

Gist • The meeting focused on resolving technical issues and optimizing processes related to the SL Database.

Bullet Gist • 🔧 Technical Fixes: Nick resolved a critical divide by zero error in the Lambda code.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-30 13:48:10

• 📊 Financials Work: Luke is actively working on financials to improve data management.

• 📧 Google Rate Limiting: A new Gmail account provides a temporary solution to Google rate limiting issues.

• 🔒 Access Management: Mike oversees the general Shield account, crucial for access management.

• 🚀 Data Processing Pipeline: A new data processing pipeline will pull 1,000 records at a time, enhancing efficiency.

Short Summary • The SL Database Maintenance meeting addressed various technical challenges and process optimizations. Nick successfully resolved a divide by zero error in the Lambda code, while the team discussed the deletion and resubmission of certain spins. Luke is continuing his work on financials, and the impact of Google rate limiting on Power Automate was identified, leading to a temporary fix using a new Gmail account. Access management was a key point, with a general Shield account managed by Mike being emphasized. The use of a data warehouse for email parsing was explored, weighing event-driven architecture against batch processing. The integration timeline for Law Ruler and how upcoming travel would affect development priorities were also discussed. Lastly, a plan was set for a 5-minute data processing pipeline capable of pulling 1,000 records at a time, with Nick tasked with enhancing the data pipeline for financial dashboards.

Ryan (ryan@themedialab.agency)
2024-07-31 12:58:24

Template For BCL Organic Lead Generation:

Pennsylvania Juvenile Hall Abuse organic lead campaign setup request @LaToya @Kelly and @Mark Maniora, FYI @Brian Hirst incoming.

  1. @Kelly, please write the three pages below (include backlinks to attorney URL in the articles Kelly): a. https://bencrump.com/pennsylvania-juvenile-hall-abuse-lawsuit/ b. https://bencrump.com/pennsylvania-juvenile-hall-abuse/ c. https://bencrump.com/pennsylvania-juvenile-hall-abuse-compensation/
  2. @LaToya, please setup form submission into CTM & LP, phone lead tracking and submission into LP (webhook). a. Leadspedia Vertical: Brandlytics - BCL - Pennsylvania Juvenile Hall Abuse for form and phone leads b. Please add to the practice areas page c. Please add to the main navigation page
  3. @Mark Maniora, once Leadspedia Vertical / Campaign / Offer are ready, please setup contract at 0 price, 100 credit, active status named Pennsylvania Juvenile Hall Abuse - Crump
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-31 13:10:18

Title: BLX SEO Clients Date: Wed Jul 31 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io, latoya@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The Strategy and Implementation Meeting for BLX SEO Clients focused on key initiatives for the New Jersey campaign, including the establishment of tracking numbers, creation of contracts, and call tracking metrics. Participants discussed the configuration of webhooks and examined their effectiveness in various campaigns, while also addressing SEO strategies to enhance attorney visibility in search results through site structure improvements. LaToya Palmer expressed interest in the creative aspects of marketing, leading to insights on branding versus lead generation. Action items were assigned, including the setup of tracking numbers and internal links, with responsibilities delegated to team members to ensure smooth execution of the campaign strategies.

Action Items • *LaToya Palmer*

• Set up tracking number for New Jersey campaign (04:37)

• Create webhook for New Jersey juvenile abuse site (26:39)

• Make the attorney list on the website into four columns (42:50)

• *Kelly*

• Add 'Attorneys' link to global website footer (42:55)

• Add internal links to attorney page on national practice area homepages (42:55)

• *Ryan Vaspra*

• Submit Pennsylvania juvenile hall abuse campaign details to team (39:44)

• Coordinate with Savvy person to wrap up pending tasks (46:42)

• Inform Cameron about small incoming projects (46:42)

• *Mark Menor*

• Create contract for New Jersey campaign (05:31)

• *Brian Hurst*

• Handle post and train for New Jersey campaign (05:31)

Shorthand Bullet • 🔧 *Setting Up *New Jersey Campaign** (00:51 - 14:33)

• Ryan testing screen sharing and Corbin's setup

• Discussion on creating tracking numbers for phone leads and forms

• Mark Menor to create contract, Brian Hurst to handle post and train

• Mike Everhart created webhook app for call tracking metrics

• Cameron's juvenile hall abuse television campaign mentioned

• :maleofficeworker: *Marketing Discussion* (14:35 - 17:42)

• LaToya expressed interest in creative side of marketing

• Ryan shared experiences with marketing teams in large corporations

• Discussed differences between branding and lead generation teams

• 📊 *Call Tracking and Webhooks* (18:14 - 21:08)

• Ryan cleaned up and simplified the system

• Examination of webhook setup for Ben Crump campaigns

• Explanation of how call tracking metrics work with Leadspedia

• 🔗 *Webhook Configuration* (22:01 - 26:39)

• Detailed walkthrough of webhook setup for different campaigns

• Explanation of campaign IDs, keys, and parameters

• Discussion on API integration attempts with Law Ruler

• 🛠️ *Testing New Webhook* (26:39 - 37:30)

• Creation and testing of new webhook for New Jersey juvenile abuse site

• Troubleshooting why test calls weren't showing up in the system

• Explanation of 'new caller' condition in webhook setup

• 📝 *Campaign Setup and Tasks* (38:01 - 40:57)

• Discussion on setting up Pennsylvania juvenile hall abuse campaign

• Ryan to submit campaign details to team members

• Addressing Uzi's question about attorney visibility in search results

• 🔍 *SEO Strategies* (40:57 - 47:32)

• Discussion on improving attorney visibility in Google search results

• Strategies for internal linking and site structure optimization

• Plans for Kelly to add internal links to practice area pages

• Ryan to coordinate with Savvy person for pending tasks

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-07-31 13:10:18

• The meeting focused on strategies for the New Jersey SEO campaign, including call tracking, webhooks, and enhancing attorney visibility online.

Bullet Gist • 🔧 New Jersey Campaign Setup: Discussion on tracking numbers and contracts to enhance lead management.

• :maleofficeworker: Creative Marketing Insights: LaToya emphasized the importance of creativity in marketing strategies.

• 📊 Call Tracking Updates: Ryan simplified the call tracking system for better performance.

• 🔗 Webhook Configuration: Detailed setup for webhooks was discussed to improve campaign metrics.

• 🔍 SEO Strategy Planning: Strategies were outlined to boost attorney visibility in search results.

Short Summary • Key initiatives were discussed for the New Jersey SEO campaign, including the creation of tracking numbers for phone leads and forms, with Mark Menor tasked to draft a contract and Brian Hurst responsible for posts and training. Mike Everhart presented a webhook app designed for call tracking metrics, while LaToya Palmer highlighted the creative aspects of marketing, sparking a conversation on branding versus lead generation. The team examined the configuration of webhooks for various campaigns, including the Ben Crump initiative, and Ryan simplified the call tracking system. They also planned the setup of a juvenile abuse site for New Jersey and discussed SEO strategies to improve attorney visibility, focusing on internal linking and site structure optimization, with action items assigned to ensure effective execution of the campaign.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-01 10:37:15

Title: Ben Crump SEO Date: Thu Aug 01 2024 11:30:00 GMT-0400 (Eastern Daylight Time) Participants: kelly@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-01 11:51:36

Title: Ben Crump SEO Date: Thu Aug 01 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: kelly@brandlytics.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Ben Crump SEO team meeting, which lasted from 00:00 to 23:00, participants engaged in fragmented discussions covering a range of topics including class schedules, border issues, healthcare, loan processes, and shopping; however, the meeting lacked a clear narrative or flow. As a follow-up, Kelly Smith has been assigned the action item to review and clarify these discussions to produce a coherent summary of the meeting.

Action Items • *Kelly Smith*

• Review and clarify the fragmented topics discussed in the meeting to create a coherent summary (00:00)

Shorthand Bullet • 📝 *Meeting Overview* (00:00 - 23:00)

• Meeting contained fragmented discussions on various topics.

• No clear narrative or flow was established during the meeting.

• Topics included class schedules, border issues, healthcare, loan processes, and shopping.

Gist • The meeting aimed to discuss various fragmented topics, including class schedules and healthcare, but lacked a coherent flow.

Bullet Gist • 📝 Meeting Overview: Discussions spanned various topics but lacked coherence.

• 🗣️ Fragmented Topics: Participants addressed class schedules, border issues, healthcare, loan processes, and shopping.

• 🔍 Action Item: Kelly Smith is assigned to clarify discussions for a coherent summary.

• 📉 Need for Structure: The meeting demonstrated a need for better organization in future discussions.

• 🤔 Future Improvements: Future meetings should aim for a clearer narrative and focused topics.

Short Summary • During the meeting, participants engaged in discussions covering a range of fragmented topics such as class schedules, border issues, healthcare, loan processes, and shopping. Despite the variety of subjects addressed, the meeting did not establish a clear narrative or flow, leading to a chaotic exchange of ideas. Kelly Smith has been tasked with reviewing and clarifying these discussions to produce a coherent summary, ensuring that key points are captured effectively. The lack of organization during the meeting highlighted the need for improved communication and structure in future discussions, allowing participants to focus on the most pertinent topics without veering off course.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-01 14:39:40

Title: Corp Dev w/ Cam Date: Thu Aug 01 2024 14:54:31 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 15

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-05 15:42:57

Title: Shield <> Sonobi Date: Mon Aug 05 2024 16:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@themedialab.agency, cameron@shield-legal.com, swilcox@sonobi.com, cschwarz@sonobi.com, kristopher@shield-legal.com, ryan@brandlytics.io, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Performance Review and Strategy Planning meeting between Shield and Sonobi, the team discussed recent campaign performances, starting with casual recaps of their weekends before delving into specifics. The Maryland campaign incurred a cost per call of $847, totaling $100K expenditure for 10 cases, while the LA campaign yielded 2 cases at $25K each, and unexpected outcomes were noted for the Illinois campaign. With a total spend of $200K across all campaigns, the overall cost per call performance was considered satisfactory. Moving forward, the team proposed continuing the current strategy with refinements, including the use of multiple tracking numbers and an exploration of a potential partnership with another law firm in Maryland, with a proposed budget of $100K-$150K. They aimed to prepare a comprehensive 4-5 page report detailing top publishers by market for delivery by Wednesday. Positive reflections on the partnership's foundation and discussions about improving the Illinois campaign targeting and expanding into the LA market rounded out the meeting, with specific action items assigned to team members for follow-up.

Action Items • *Craig*

• Prepare and send detailed campaign report by Wednesday (06:02)

• *Kristopher*

• Review report with Cam and gather feedback (06:16)

• *Craig and team*

• Develop more granular insights for phase two planning (05:38)

• Consider refining targeting for Illinois campaign (03:41)

• Explore potential for new law firm partnership in Maryland (04:48)

Shorthand Bullet • 🍻 *Weekend Recap and Small Talk* (00:00 - 01:47)

• Craig had a barbecue and soccer dinner

• Kristopher stayed local, visited happy hour spots in Old Town La Quinta

• Steve mentioned Olympic action at sports bars

• Craig plans to visit Kristopher's area in October

• 📊 *Campaign Performance Review* (01:47 - 04:47)

• Maryland campaign: $847 cost per call, $10,000 cost per case

• 10 total Maryland cases, $100K spent

• LA campaign: 2 cases, $25K each

• Illinois campaign: No results, surprising outcome

• Total spend across campaigns: $200K

• Cost per call performance was good overall

• 🚀 *Phase Two Planning* (04:47 - 06:38)

• Proposal to continue current strategy with refinements

• Suggestion to use multiple 800 numbers to track by publisher

• Potential to scale by publisher performance

• Consideration of adding another law firm in Maryland

• Possible budget of $100K-$150K for Maryland campaigns

• 📑 *Report Preparation and Delivery* (06:38 - 07:26)

• Full report to include 4-5 pages with top publishers by market and geo

• Goal to deliver report by Wednesday

• Chris to review report with Cam

• 🤝 *Partnership Reflection and Next Steps* (07:26 - 09:38)

• Positive feedback on partnership and foundation laid

• Interest in Cam's thoughts on next steps

• Consideration of revisiting Illinois campaign with improved targeting

• Potential to expand in LA market with refined approach

Gist • The meeting focused on reviewing campaign performances and strategizing enhancements for future initiatives.

Bullet Gist • 📊 Campaign Performance Review: The team analyzed the performance of recent campaigns, noting costs and outcomes.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-05 15:42:57

• 🤝 Strategic Enhancements: Plans were made to refine strategies and explore new partnerships for better results.

• 📈 Future Reporting: A detailed report on top publishers is in preparation for upcoming discussions.

• 💡 Positive Reflections: The meeting ended with a positive outlook on the partnership and strategies moving forward.

• 🔍 Targeting Improvements: There were discussions on improving targeting for campaigns, particularly for Illinois and LA.

Short Summary • During the Performance Review and Strategy Planning meeting between Shield and Sonobi, the teams analyzed recent campaign performances, starting with brief personal updates. They highlighted the Maryland campaign's $847 cost per call, totaling $100K for 10 cases, and noted that the LA campaign achieved 2 cases at $25K each. Unexpected outcomes were recorded for the Illinois campaign, contributing to a total spend of $200K across all initiatives. Despite the challenges, the overall cost per call performance was deemed satisfactory. Moving forward, the teams proposed to maintain the current strategy with refinements, such as utilizing multiple tracking numbers and exploring a partnership with another law firm in Maryland, budgeting between $100K and $150K. The meeting concluded with plans for a comprehensive report on top publishers by market, due by Wednesday, and discussions on enhancing targeting strategies for the Illinois campaign and expanding into the LA market.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-12 12:16:35

Title: BLX Media Buying Date: Mon Aug 12 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: lee@brandlytics.io, markmaniora@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The Data Review and Training Session for BLX Media Buying focused on analyzing key data pertaining to lead generation and management. During the meeting, Ryan shared his screen with Mark to review specific data columns within a spreadsheet, highlighting the performance of qualified leads in Atlanta. The team discussed the process for interpreting data from various sources, addressed challenges faced when logging into systems, especially in England, and detailed lead management strategies for Jack Avino’s campaigns. Emphasis was placed on the differentiation between disputing and returning leads, as well as the technical aspects of counting sold leads via filters in Leedspedia. The session concluded with a call to action for Mark to finalize the counts for Ben Crump’s sold leads and qualified cases, ensuring clarity on next steps.

Action Items • *Mark Maniora*

• Complete the counts for Ben Crump's sold call leads, cases, and qualified leads (14:33)

Shorthand Bullet • 🖥️ *Screen Sharing and Data Review* (01:18 - 04:11)

• Ryan shared his screen with Mark

• Discussed columns L and M in a spreadsheet

• Reviewed data for Atlanta force code: 2 qualified leads and 2 cases

• Analyzed total leads (27) and breakdown of qualified leads and cases

• 📊 *Data Analysis Process* (04:11 - 06:37)

• Explained how to interpret data from law ruler and Crump.com website

• Discussed CTM for focused litigation solutions

• Mentioned challenges with logging into systems, especially in England

• 🔍 *Lead Management* for Jack Avino** (06:37 - 09:31)

• Explained lead handling for Jack Avino's organic and paid campaigns

• Discussed the process of deduping non-sales leads

• Clarified the difference between disputing leads and returning leads

• 📈 *Lead Counting and Reporting* (09:31 - 14:33)

• Demonstrated how to count sold leads using filters in Leedspedia

• Discussed challenges in pulling historical lead data

• Reviewed criminal leads specifically

• Checked updated spending data

• 🏁 *Wrap-up and Next Steps* (14:33 - 14:47)

• Ryan asked Mark to complete the counts for Ben Crump's sold call leads, cases, and qualified leads

Gist • The meeting aimed to analyze lead generation data and improve lead management strategies for BLX Media Buying.

Bullet Gist • 🖥️ Screen Sharing and Data Review: Ryan shared his screen with Mark to discuss and analyze key data columns regarding leads.

• 📊 Data Analysis Process: The team explained how to interpret various data sources and addressed system access challenges.

• 🔍 Lead Management for Jack Avino: Strategies for managing leads in Jack Avino's campaigns were clarified, including deduplication processes.

• 📈 Lead Counting and Reporting: Demonstrations on counting sold leads using filters in Leedspedia were provided, with a focus on historical data.

• 🏁 Wrap-up and Next Steps: Ryan emphasized the importance of finalizing counts for Ben Crump's leads.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-12 12:16:35

• The Data Review and Training Session for BLX Media Buying focused on the analysis of key data related to lead generation and management. Ryan shared his screen with Mark to review specific data columns within a spreadsheet, particularly highlighting the performance of qualified leads in Atlanta. The team discussed the interpretation of data from various sources, addressing challenges faced when logging into systems, especially in England. They detailed lead management strategies for Jack Avino's campaigns, emphasizing the differentiation between disputing and returning leads. Technical aspects of counting sold leads using filters in Leedspedia were also demonstrated, alongside challenges in pulling historical lead data. The session concluded with a call to action for Mark to finalize counts for Ben Crump’s sold leads and qualified cases, ensuring clarity on next steps.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-12 13:12:32

Title: Tech Project Status Weekly Date: Mon Aug 12 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Tech Project Status Weekly meeting, key updates were discussed, focusing on project progress, financial analytics, portal development, and lead management. There are currently 19 integrations in progress and 29 completed since mid-2023, with clients requesting additional features and new complex integration demands involving multiple stakeholders. The financial dashboard is being enhanced by Ryan, Mark Barmazel, and Cameron, with plans for a tip data warehouse and updated case types in the tip portal. Brian is addressing permission groups and real-time updates for case types within the portal. Additionally, configurations for inbound flows in the dialer are underway, along with discussions on lead scoring and campaign management. Action items were assigned to team members, including scheduling meetings to discuss the tip portal and dashboard progress, prioritizing specific integrations, and refining algorithms.

Action Items • *Ryan Vaspra*

• Schedule meeting with Brian to discuss tip portal and DBT app (22:00)

• Meet with James on Thursday to review dashboard progress (28:55)

• Plan trip to Vegas with James to meet Cameron (28:00)

• Approve $2,000 for Law Ruler character limit change (40:01)

• *Brian Hirst*

• Work on updating case type names in the tip portal (15:48)

• Implement user permissions for the tip portal (23:52)

• *Nicholas Ward*

• Prioritize hair relaxer integration (06:54)

• Continue configuring inbound flows and recordings for the dialer (29:35)

• *James Scott*

• Continue refining algorithms and working on the dashboard (28:49)

Shorthand Bullet • 🔧 *Project Updates and Integrations* (01:31 - 06:33)

• 19 integrations currently in progress

• 29 integrations completed since mid-2023

• Clients requesting additional functionality for existing campaigns

• New complex integration requests involving multiple parties

• 📊 *Financial Dashboard and Data Analytics* (06:33 - 19:21)

• Ryan working on financial dashboard with Mark Barmazel and Cameron

• 47 pages of financial dashboard improved

• Plans for tip data warehouse and financial log table

• Discussion on updating case types in the tip portal

• 💻 *Tip Portal Development* (19:22 - 28:59)

• Brian working on permission groups for the tip portal

• Discussion on updating case type names in real-time

• Plans to create a new table for case types revenue rates

• Strategies for embedding dashboards and managing user permissions

• 📞 *Dialer Configuration and *Lead Management** (29:26 - 40:56)

• Inbound flows and recordings being configured for the dialer

• Campaigns to be built based on case types

• Discussion on lead scoring and prioritization

• Plans to integrate lead source data and improve campaign tracking

Gist • The meeting focused on project progress, financial analytics, and portal development, with updates on integrations and lead management strategies.

Bullet Gist • 🔧 Project Updates and Integrations: 19 integrations are currently in progress with 29 completed since mid-2023.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-12 13:12:32

• 📊 Financial Dashboard Enhancements: Ryan, Mark Barmazel, and Cameron are improving the financial dashboard and planning a tip data warehouse.

• 💻 Tip Portal Development: Brian is working on permission groups and updating case types in real-time within the tip portal.

• 📞 Dialer Configuration: Configurations for inbound flows in the dialer are being set up, focusing on lead scoring.

• ✅ Action Items: Team members have been assigned action items to prioritize integrations and refine algorithms.

Short Summary • During the Tech Project Status Weekly meeting, key updates were shared regarding various ongoing projects. There are currently 19 integrations in progress and 29 completed since mid-2023, as clients continue to request additional features and complex integrations involving multiple stakeholders. The financial dashboard is undergoing enhancements by Ryan, Mark Barmazel, and Cameron, who are also planning a tip data warehouse and updates to case types in the tip portal. Brian is addressing permission groups and real-time updates for case types within the portal. Additionally, configurations for inbound flows in the dialer are underway, with discussions on lead scoring and campaign management. Action items were assigned to team members to prioritize integrations and refine algorithms.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-12 14:07:43

Title: BLX EOM Fin Date: Mon Aug 12 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@accountingdept.net, ryan@brandlytics.io, andy@shield-legal.com, malissa@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The BLX End-of-Month Financial Review and Operations Meeting covered several key topics, starting with a financial review led by Ryan and Malissa, which focused on commissions for June and July, ongoing deals, and the need to follow up with Jeff regarding Jack and Vino payments. Staff allocations were discussed, including a $1200 payment to Savvy Branding Group and the allocation of Adrian, Luke, and Corbin to Shield and BLX, respectively. Invoice follow-ups were conducted, confirming payments for Focus Litigation Solutions and addressing outstanding invoices with Bolster. The team also examined billing strategies, particularly for Markowitz and upcoming quarterly billing for Crump, with an objective for BrandLytics to achieve a small net profit for potential disbursement. Action items were assigned to Malissa, Ryan, and Brian to ensure timely follow-up on payments and invoicing matters.

Action Items • *Malissa Phillips*

• Ping Jeff again about Jack and Vino payments, cc Ryan, Brian, and Cameron (13:55)

• Mark Focus Litigation Solutions invoices as paid (18:50)

• Email Markowitz invoice and ask when to charge the card on file (27:11)

• Update BrandLytics account number in invoice settings (29:41)

• *Ryan Vaspra*

• Mark $1200 Savvy Branding payment as paid in Harvest (15:26)

• Send email with correct account numbers for invoicing (15:26)

• Reply to Bolster's email about invoice details (32:21)

• Wait for Latoya to finish before proceeding with wire transfer (34:02)

• *Brian*

• Allocate payments for Focus Litigation Solutions (18:25)

Shorthand Bullet • 📊 *Financial Review and Invoices* (03:50 - 13:57)

• Ryan and Malissa discussed commissions for June and July

• Reviewed deals: 142,782 and 35 (not booked yet)

• Discussed pinging Jeff about Jack and Vino payments

• 💼 *Staff Allocations and Payments* (14:04 - 18:44)

• Discussed $1200 Savvy Branding Group payment deposited to Shield account

• Agreed to allocate Adrian 80% to Shield, 20% to BLX

• Luke 100% Shield, Corbin 100% BLX

• Reviewed Focus Litigation Solutions payments

• 📝 *Invoice *Follow-ups** (18:46 - 22:24)

• Marked Focus Litigation Solutions as paid

• Discussed following up with Bolster regarding invoice

• Reviewed LSA invoices

• 💰 *Billing and *Account Management** (22:26 - 35:52)

• Discussed Markowitz billing strategy

• Reviewed Shield and BrandLytics bank account information

• Discussed upcoming billing for Crump (quarterly)

• Aim for BrandLytics to have a small net profit for potential disbursement

Gist • The meeting focused on financial reviews, staff allocations, invoice follow-ups, and billing strategies to ensure timely payments and profitability.

Bullet Gist • 📊 Financial Review and Invoices: Ryan and Malissa discussed commissions and ongoing deals, emphasizing follow-ups on payments.

• 💼 Staff Allocations and Payments: A $1200 payment to Savvy Branding Group was confirmed along with staff allocations for Shield and BLX.

• 📝 Invoice Follow-ups: Focus Litigation Solutions payments were confirmed, and outstanding invoices with Bolster were discussed.

• 💰 Billing and Account Management: The team strategized on Markowitz billing and quarterly billing for Crump, aiming for a net profit.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-12 14:07:43

• The BLX End-of-Month Financial Review and Operations Meeting reviewed key financial metrics, led by Ryan and Malissa, focusing on commissions for June and July, ongoing deals, and necessary follow-ups regarding payments for Jack and Vino from Jeff. Staff allocations were addressed, including a $1200 payment to Savvy Branding Group and the distribution of Adrian to Shield (80%) and BLX (20%), while Luke and Corbin were fully allocated to Shield and BLX, respectively. Invoice follow-ups confirmed payments for Focus Litigation Solutions and highlighted the need to address outstanding invoices with Bolster. The team discussed billing strategies, particularly for Markowitz, and outlined upcoming quarterly billing for Crump, with the goal for BrandLytics to achieve a small net profit for potential disbursement. Action items were assigned to Malissa, Ryan, and Brian to ensure effective follow-up on payments and invoicing matters.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-13 14:10:56

Title: Ryan Vaspra 30 Minute Meetings (Aliyah Andersen) Date: Tue Aug 13 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: aliyah.andersen@idealimage.com, ryan@brandlytics.io, cschwarz@sonobi.com, deborah.mcginn@idealimage.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The Strategy and consultation meeting focused on addressing the significant financial and operational challenges facing Ideal Image, which saw its revenue plummet from $500 million to $220 million amidst changes in ownership and leadership. With Deborah McGinn as the new CMO, the primary goal is to stabilize the company, resolve key issues, and pursue growth within three years. The meeting highlighted critical data and analytics problems, including a complicated customer journey, inefficient call center operations, and a lack of clear KPIs. Additionally, technology and infrastructure concerns were raised, particularly regarding the limitations of the overly customized Salesforce instance and the need for a new data warehouse solution. Marketing challenges discussed included a 30% decline in organic traffic and an overreliance on paid media, necessitating a revival of SEO and content marketing efforts. The conversation also covered ways to enhance the customer journey by improving data flow and analytics. Action items were assigned to Deborah McGinn and Ryan Vaspra for follow-up, emphasizing the need for both immediate fixes and long-term strategic improvements.

Action Items • *Deborah McGinn*

• Review the 'contact to cash' PowerPoint shared by Ryan (54:52)

• Discuss data flow and warehouse rebuild with CTO (42:44)

• Have conversations with leadership team in Tampa about next steps (01:04:34)

• Prepare a skeleton version of Ideal Image's 'contact to cash' flow for next meeting (01:04:48)

• *Ryan Vaspra*

• Share the 'contact to cash' PowerPoint with Deborah (54:50)

• Prepare for next meeting to discuss Ideal Image's 'contact to cash' flow (01:05:15)

Shorthand Bullet • 🏢 *Company Background and Challenges* (02:41 - 13:49)

• Ideal Image faced significant financial challenges, dropping from $500 million to $220 million revenue

• Company underwent multiple ownership changes and leadership restructuring

• Deborah McGinn joined as CMO to help turn the company around

• Current goal: stabilize the business, fix issues, and show growth within 3 years

• 📊 *Data and Analytics Issues* (13:49 - 22:41)

• Complicated customer journey with multiple touchpoints

• Inefficient call center operations and lead routing

• Lack of clear KPIs and data visibility across the organization

• Need for improved data warehouse and analytics capabilities

• 🛠️ *Technology and Infrastructure* (22:53 - 34:49)

• Current use of multiple systems: AWS, Azure, Power BI, Salesforce

• Overly customized Salesforce instance causing limitations

• Need for a new data warehouse solution

• Discussion of potential tools like Fivetran, DBT, and Google Cloud BigQuery

• 📈 *Marketing Challenges and Strategies* (35:01 - 43:24)

• Decline in organic traffic by 30% year-over-year

• Overreliance on paid media, especially Facebook

• Need to rebuild SEO and content marketing efforts

• Issues with audience segmentation and targeting due to legal constraints

• 🔄 *Customer Journey and Data Flow* (43:24 - 57:11)

• Discussion of 'contact to cash' concept for mapping customer journey

• Need for better cohort analysis and performance tracking

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-13 14:10:56

• Challenges in connecting marketing activities to revenue

• Importance of understanding inputs vs outputs in business performance

• 🚀 *Next Steps and Potential Solutions* (57:13 - 01:05:29)

• Plan to rebuild organic traffic and diversify marketing channels

• Need to fix current spend issues before expanding efforts

• Potential collaboration on data flow and analytics improvements

• Importance of balancing short-term fixes with long-term strategic improvements

Gist • The meeting aimed to address Ideal Image's financial and operational challenges, focusing on stabilization and growth strategies.

Bullet Gist • 📉 Revenue Decline: Ideal Image's revenue fell significantly from $500 million to $220 million due to changes in ownership.

• 📊 Data Challenges: Critical issues included a complicated customer journey and inefficient call center operations.

• 💻 Tech Concerns: There is a need for a new data warehouse solution due to limitations in the customized Salesforce instance.

• 🚀 Marketing Strategy: A 30% drop in organic traffic highlighted the necessity to refocus on SEO and content marketing.

• 📝 Action Items: Deborah McGinn and Ryan Vaspra were tasked with addressing both immediate issues and long-term strategies.

Short Summary • The Strategy and consultation meeting centered on Ideal Image's urgent financial and operational issues, marked by a dramatic revenue drop from $500 million to $220 million due to ownership and leadership changes. With Deborah McGinn newly appointed as CMO, the primary objective is to stabilize the company within three years. Key discussions included problems with data and analytics, such as a convoluted customer journey and inefficient call center operations, alongside the absence of clear KPIs. Technology concerns were also prevalent, notably the limitations of an overly customized Salesforce instance and the necessity for a new data warehouse. Marketing challenges included a 30% decline in organic traffic and an overreliance on paid media, prompting a need to revive SEO and content marketing efforts. Action items were assigned to Deborah and Ryan Vaspra for both immediate fixes and long-term strategic improvements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-13 14:36:29

Title: TIP Portal - Create DBT applrcasetypesrev_rates for Retool SQL Date: Tue Aug 13 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 45

Overview • In the recent informal work discussion and troubleshooting session, the team focused on various technical issues related to the TIP Portal and DBT app development. Key highlights included Ryan's efforts to resolve a data insertion problem and issues with the master append variable in Python, leading to multiple manual data pushes due to a bug. Alongside work topics, Ryan shared personal updates about his recent road trip from Las Vegas to Tulsa, during which he visited notable spots in Colorado and discussed family dynamics. The meeting concluded with a plan to seek assistance from Quint if the technical challenges persist and a decision to reschedule the bigquery meeting for the following morning at 7:30 AM. Action items included continuing the troubleshooting efforts on the master append issue and considering creating a master pen solo if the problem remains unresolved.

Action Items • *Ryan*

• Continue troubleshooting the master append issue (22:18)

• Create master pen solo if current issue persists (22:18)

• Seek help from Quint if unable to resolve the issue (22:18)

• *Ryan and Brian*

• Reschedule bigquery meeting for tomorrow at 7:30 AM (28:13)

Shorthand Bullet • 🔧 *Technical Issues and Work Tasks* (00:01 - 05:20)

• Ryan working on running Cameron's numbers

• Turning on Tev and TPV for verticals in DBT

• Issue with master append not resetting variable in Python

• Ryan manually pushing data multiple times due to bug

• 🚗 *Travel Discussion* (05:20 - 16:29)

• Ryan's recent road trip from Vegas to Tulsa

• Stayed in Palisade, Colorado and visited South Park

• Ryan now has 100% custody of his children

• Discussion about Grand Lake of the Cherokees and Jenks, Oklahoma

• Comparison with lakes in northern California

• 💻 *Technical Troubleshooting* (16:29 - 28:13)

• Continued attempts to resolve data insertion issue

• Ryan considering asking Quint for help

• Decision to move bigquery meeting to tomorrow

Gist • The team met to troubleshoot technical issues with the TIP Portal and DBT app, while Ryan shared personal updates during the discussion.

Bullet Gist • 🔧 Technical Issues: Ryan is addressing data insertion problems and master append variable issues in Python.

• 🚗 Personal Updates: Ryan discussed his recent road trip from Vegas to Tulsa, sharing insights from his travels.

• 💻 Troubleshooting Plans: The team decided to continue troubleshooting and may seek Quint's help if problems persist.

• ⏰ Meeting Rescheduling: The bigquery meeting has been rescheduled for the next morning at 7:30 AM.

• 📝 Action Items: Action items include resolving the master append issue and considering solo solutions.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-13 14:36:30

• In a recent informal work discussion, the team focused on resolving technical challenges with the TIP Portal and DBT app development. Key highlights included Ryan's attempts to fix a data insertion problem and address issues with the master append variable in Python, which resulted in multiple manual data pushes due to a bug. Alongside the technical topics, Ryan shared personal updates about his recent road trip from Las Vegas to Tulsa, during which he visited notable locations in Colorado and discussed family dynamics, including his newfound custody of his children. The meeting concluded with a plan to seek assistance from Quint if the challenges continued and a decision to reschedule the bigquery meeting for the next morning at 7:30 AM. Action items included ongoing troubleshooting of the master append issue and consideration of creating a master pen solo if the problem persisted.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-14 12:09:35

Title: BLX SEO Clients Date: Wed Aug 14 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io, latoya@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-14 12:42:25

Title: TIP Portal - Create DBT applrcasetypesrev_rates for Retool SQL Date: Wed Aug 14 2024 12:15:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 45

Overview • The Technical Discussion and Problem-Solving meeting focused on the development of the DBT applrcasetypesrev_rates for the TIP Portal, emphasizing the setup of DBT and BigQuery and the integration of SQL functionalities such as left joins. Participants analyzed discrepancies in case type IDs, refined SQL queries to address missing data, and optimized queries to resolve issues with insertion, updates, and duplicates. Data cleanup and standardization efforts were implemented to ensure consistency in case type names and pricing information. The team established scheduled queries for automated updates while discussing user access permissions in Retool, highlighting the need for a business plan to unlock advanced features. The meeting concluded with action items, including preparations for a training session and adjustments to user permissions, all aimed at finalizing testing and enhancing future project iterations.

Action Items • *Brian*

• Test and prepare the app for training session (01:18:13)

• Remove Ryan's admin access and add him back as a regular user for testing (01:17:30)

• *Ryan*

• Set up training session with David and Anthony's team (01:18:13)

• *unassigned*

• Upgrade Retool to business plan for advanced features (01:10:47)

Shorthand Bullet • 🖥️ *DBT and BigQuery Setup* (00:01 - 08:37)

• Discussed setting up DBT and BigQuery for case types

• Explored left join functionality in SQL queries

• Addressed issues with app connectivity to multiple tables

• 📊 *Data Analysis and Query Refinement* (09:49 - 18:03)

• Analyzed discrepancies in case type IDs

• Refined SQL queries to insert missing data

• Investigated issues with data population in tables

• 🔧 *Troubleshooting and Query Optimization* (19:32 - 33:08)

• Fixed issues with data insertion and updates

• Optimized SQL queries for better performance

• Addressed problems with duplicate entries and missing data

• 📝 *Data Cleanup and Standardization* (35:45 - 43:06)

• Cleaned up and standardized case type names

• Updated pricing information for specific case types

• Ensured consistency in data across different tables

• 🔄 *Query Scheduling and Automation* (43:36 - 54:19)

• Set up scheduled queries in BigQuery

• Discussed the benefits of automated data updates

• Compared BigQuery's features to AWS and DBT

• 🧪 *Testing and Verification* (55:34 - 01:03:18)

• Created test case types in Law Ruler

• Verified data synchronization between systems

• Discussed default values for new case types

• 👥 *User Access and Permissions* (01:04:01 - 01:12:32)

• Explored user types and permissions in Retool

• Discussed upgrading to a business plan for advanced features

• Planned user setup for different team members

• 🏁 *Wrap-up and Next Steps* (01:18:13 - 01:18:15)

• Agreed to finalize testing and preparation

• Planned training session for David, Anthony, and team

• Discussed potential improvements for future iterations

Gist • The meeting focused on developing the DBT applrcasetypesrev_rates for the TIP Portal, addressing data discrepancies and enhancing SQL functionalities.

Bullet Gist • 🖥️ DBT and BigQuery Setup: The team discussed setting up DBT and BigQuery, including exploring left join functionalities.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-14 12:42:25

• 📊 Data Analysis and Query Refinement: Participants analyzed discrepancies in case type IDs and refined SQL queries to address data gaps.

• 🔧 Troubleshooting and Optimization: Issues with data insertion and updates were fixed, along with optimizing SQL queries for performance.

• 📝 Data Cleanup and Standardization: Efforts were made to standardize case type names and update pricing information for consistency.

• 🔄 Query Scheduling and Automation: Scheduled queries were set up in BigQuery to automate data updates and improve efficiency.

Short Summary • Participants discussed the development of the DBT applrcasetypesrev_rates for the TIP Portal, emphasizing the setup of DBT and BigQuery. They explored SQL functionalities, including left joins, to resolve discrepancies in case type IDs and refine queries for missing data. Troubleshooting efforts included optimizing SQL queries for performance and addressing duplicate entries. Data cleanup initiatives ensured consistency in case type names and pricing. Scheduled queries were established to automate updates, while user access permissions in Retool were reviewed, highlighting the need for a business plan to unlock features. The meeting concluded with action items on training preparations and permission adjustments for effective testing and future project improvements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-15 12:42:28

Title: BLX SEO Clients Date: Thu Aug 15 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-15 15:08:19

Title: BCL Next Steps Date: Thu Aug 15 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@shield-legal.com, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The BCL Next Steps Performance Review and Strategy Planning meeting provided a comprehensive update on recent achievements and future strategies. Notably, July emerged as the best month of the year with over 101,000 visitors and a significant increase in domain authority from 49 to 52. Key improvements in SEO and traffic were highlighted, including a 40% traffic increase and successful implementation of Yext, which generated 156 leads. The performance of civil rights and employment discrimination cases was particularly strong, alongside a notable uptick in hair relaxer cases. The discussion also emphasized effective social media tracking, resulting in 68 leads from social forms and 619 call leads, with plans to enhance tracking and generate more predictable leads. Action items were assigned, including tasks for Ryan concerning cross-referencing leads and optimizing tracking systems, and a meeting for Uzoma to align desired case types with attorneys.

Action Items • *Ryan*

• Send list of social form leads to tip team for cross-referencing with cases (23:08)

• Investigate easier way to track social leads conversion to cases (23:53)

• Work on creating a dashboard for tracking social leads to cases conversion (34:52)

• Tinker with dashboard and fix CTM connector issue (37:11)

• *Uzoma*

• Meet with attorneys to discuss desired case types (36:34)

Shorthand Bullet • 📊 *Performance Update* (02:11 - 08:17)

• July was best month of the year with 101,000+ visitors

7.1% average visitor to lead form or phone call rate

• Domain authority increased from 49 to 52

• Reduced crawl errors from 3100 to nearly 0

• 🚀 *SEO and Traffic Improvements* (08:25 - 19:31)

• Implemented Yext in May, resulting in 156 leads from directories

• Rankings up 6.53% over prior month

• Traffic up 40% over prior month

• Working on blog articles for keyword opportunities

• Focusing on internal linking and high-value keywords

• 📈 *Case Types and Dashboard* (20:23 - 29:15)

• Civil rights and employment discrimination cases performing well

• Hair relaxer cases doing well with 103 and counting

• Dashboard shows case types and numbers

• Discussed tracking social leads conversion to cases

• 🔍 *Social Media* Tracking and Improvements** (29:15 - 37:32)

• 68 leads from social form alone

• 619 call leads from social media

• 339 qualified leads (calls lasting more than 2 minutes)

• Discussing creation of a custom link tree page on website

• Planning to generate more predictable calls through social media strategy

Gist • The meeting focused on reviewing BCL's performance and strategizing future improvements in SEO, lead generation, and case management.

Bullet Gist • 📊 Performance Update: July was the best month with over 101,000 visitors and domain authority rising from 49 to 52.

• 🚀 SEO Boost: Yext implementation led to a 40% traffic increase and 156 leads, with ongoing efforts on blog articles.

• 📈 Strong Case Performance: Civil rights and employment discrimination cases are thriving, alongside a rise in hair relaxer cases.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-15 15:08:19

• 🔍 Social Media Success: Effective tracking yielded 68 leads from social forms and 619 call leads, with plans for improved strategies.

• ✅ Action Items Assigned: Ryan to optimize tracking systems; Uzoma to coordinate desired case types with attorneys.

Short Summary • The BCL Next Steps Performance Review and Strategy Planning meeting highlighted significant achievements in July, marking it as the best month of the year with over 101,000 visitors and a notable increase in domain authority from 49 to 52. Key improvements in SEO were evident with a 40% traffic increase and the successful implementation of Yext, generating 156 leads. Civil rights and employment discrimination cases performed strongly, alongside an increase in hair relaxer cases. The meeting emphasized effective social media tracking, which resulted in 68 leads from social forms and 619 call leads, with plans to enhance tracking for more predictable lead generation. Action items included optimizing tracking systems assigned to Ryan and a meeting for Uzoma to align case types with attorneys.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-16 09:33:03

Title: BLX SEO Clients Date: Fri Aug 16 2024 10:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Strategy and Planning Meeting for the BLX SEO Clients, participants focused on enhancing SEO strategies and content development. Ryan initiated discussions on collaborating with Uzi, the marketing director for Crushing, to refine blog posts and introduced a 'five pack' content concept, comprising three pages, one blog, and one press release. Key highlights included a strategic assessment of internal linking practices, specifically comparing Ben Crump's links with industry competitors and utilizing Google Search Console for insights on high-traffic pages. The team prioritized content optimization related to civil rights and personal injury cases while establishing Kelly's SEO routine, emphasizing the significance of backlinks and the need for optimized interlinking across all content. Action items assigned included revising blog content to reflect a professional tone, researching new topics, and confirming logistics with the paralegal team, with Ryan tasked to facilitate collaborations and oversee quality improvements.

Action Items • *Kelly Richardson*

• Revise the blog page to make it sound like an attorney wrote it (28:52)

• Ensure new articles are interlinked with existing valuable pages (30:35)

• Research and propose additional topics for content creation (24:05)

• Implement internal linking strategy for press releases and blog posts (13:45)

• Focus on optimizing content for civil rights, personal injuries, auto accidents, and birth injury cases (19:12)

• *Ryan Vaspra*

• Add Kelly to the Ben Crump channel for collaboration (05:11)

• Review and send the revised blog post to Uzi for feedback (31:26)

• Confirm new form, phone, and routing details with BCL paralegal team for birth injury cases (23:01)

• Work on hiring a brand consultant to manage marketing efforts (32:05)

Shorthand Bullet • 🔍 *SEO Strategy and Content Creation* (01:42 - 11:11)

• Ryan discussed meeting with Uzi, director of marketing for Crushing

• Uzi interested in reviewing blog posts

• Introduced concept of 'five pack': 3 pages, 1 blog, 1 press release

• Kelly to optimize press releases and consider SEO opportunities

• Ryan to add Kelly to Ben Crump channel for collaboration

• 📊 *Interlinking and SEO Improvement* (11:11 - 22:11)

• Focused on improving internal linking strategy

• Compared Ben Crump's internal links to competitors

• Emphasized importance of strategic interlinking in press releases and blogs

• Discussed using Google Search Console for identifying high-traffic pages

• Prioritized focus on civil rights, personal injuries, auto accidents, and birth injury cases

• 🎯 *Content Optimization and SEO Routine* (22:12 - 33:12)

• Established Kelly's SEO routine: optimize press releases, add internal links, fix errors

• Discussed importance of backlinks for improving page rankings

• Ryan encouraged Kelly to research and propose topics independently

• Reviewed competition analysis using Moz

• Emphasized distinction between case pages and blog pages

• Discussed internal linking strategy for truck accident lawyer pages

Gist • The meeting aimed to enhance SEO strategies and content development for BLX SEO clients.

Bullet Gist • 🔍 SEO Strategy Enhancement: Focused on improving SEO strategies and content development for BLX clients.

• 📝 Content Collaboration: Ryan proposed collaboration with Uzi to refine blog posts and introduced a 'five pack' content concept.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-16 09:33:03

• 📊 Internal Linking Assessment: Team assessed internal linking practices, comparing Ben Crump's links with competitors.

• 📈 Content Optimization Focus: Prioritized optimization for civil rights and personal injury content.

• ✅ Action Items Assigned: Assigned tasks for revising blog content, researching topics, and confirming logistics.

Short Summary • During the Strategy and Planning Meeting for BLX SEO Clients, the participants discussed ways to enhance SEO strategies and improve content development. Ryan initiated a collaboration with Uzi, the marketing director for Crushing, focusing on refining blog posts and introduced a 'five pack' content concept, which includes three pages, one blog, and one press release. The team conducted a strategic assessment of internal linking practices, comparing Ben Crump's links with those of industry competitors, while utilizing Google Search Console to gain insights on high-traffic pages. They prioritized content optimization related to civil rights and personal injury cases and established Kelly's SEO routine, emphasizing the significance of backlinks and optimized interlinking across all content. Action items included revising blog content for a professional tone, researching new topics, and confirming logistics with the paralegal team, with Ryan overseeing collaborations and quality improvements.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-19 13:14:30

Title: BLX Media Buying Date: Mon Aug 19 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, lee@brandlytics.io, markmaniora@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the BLX Media Buying Status Update Meeting, participants discussed recent progress on key tasks. Lee confirmed that he has updated the relevant sheets, and Mark validated the updates on his end. Ryan reported on his work with crump case counts, indicating that he will document updates directly in the sheets while utilizing smart advocate and de-duping from law ruler. He aims to complete this task by Thursday. An action item was assigned to Ryan to ensure the case counts are updated and notes are made accordingly.

Action Items • *Ryan Vaspra*

• Update crump case counts and make notes in cells as updates are made, while checking smart advocate and de-duping from law ruler, aiming to complete by Thursday (00:45)

Shorthand Bullet • 📊 *Sheet Updates* (00:06 - 00:44)

• Lee has updated sheets

• Mark confirmed sheets are updated on his end

• 🧹 *Crump Case Counts* (00:45 - 01:27)

• Ryan working on crump case counts

• Will make notes in cells as updates are made

• Checking smart advocate and de-duping from law ruler

• Aiming to complete by Thursday

Gist • Participants reviewed progress on media buying tasks, focusing on updates to case counts and sheet validations.

Bullet Gist • 📊 Sheet Updates: Lee updated the necessary sheets, and Mark confirmed these updates.

• 🧹 Crump Case Counts: Ryan is working on updating crump case counts and will document his progress in the sheets.

• 🗓️ Deadline: Ryan aims to complete his updates by Thursday.

• ✅ Action Item: Ryan was assigned to ensure case counts are updated and notes are recorded.

• 🔄 Collaboration: The team is working together to ensure accurate media buying data.

Short Summary • During the BLX Media Buying Status Update Meeting, participants discussed recent progress on key tasks related to media buying. Lee confirmed he has updated the relevant sheets, which were validated by Mark on his end. Ryan reported on his ongoing work with crump case counts, stating that he will document updates directly in the sheets while utilizing smart advocate and de-duping from law ruler. He aims to complete this task by Thursday, and an action item was assigned to him to ensure that the case counts are updated and notes are made accordingly, emphasizing the collaborative effort in maintaining accurate case tracking.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-19 14:21:41

Title: Tech Project Status Weekly Date: Mon Aug 19 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The Tech Project Status Weekly meeting covered several key updates, starting with Nicholas providing progress on the Five9 implementation, specifically on inbound queue requirements and the Crump team's phone number setup. He also shared experiences from his recent trip to Serbia and Bosnia, including an incident of food poisoning and observations of local cultural events. Ryan outlined upcoming meetings and travel plans, while discussing a solution for automating the revenue rates table for LR case types using BigQuery. Challenges regarding financial reporting were raised, particularly around splitting new contract data for Flatirons and mapping lead IDs. Development tasks were assigned, with Ryan coordinating efforts on the performance tip version and SSL maintenance. Action items were assigned among team members to ensure project continuity, including review and presentation tasks related to the TIP portal and financial reporting efforts.

Action Items • *Ryan Vaspra*

• Schedule meeting with Quint and Nick McFadden regarding calculate performance tip version (17:54)

• Provide Nicholas with information on mapping lead IDs in financial log for Flatirons (16:49)

• Review TIP portal progress with Brian (19:43)

• *Nicholas Ward*

• Continue work on splitting out new contract data for Flatirons financial reporting (13:28)

• *Brian Hirst*

• Prepare to present TIP portal progress to Ryan (19:47)

• *Nick McFadden*

• Work on finishing the calculate performance tip version (18:00)

• Ensure SSL certificates on Light Sail don't expire (18:27)

Shorthand Bullet • 🔄 *Five9 Implementation Update* (00:52 - 04:18)

• Nicholas updated on progress with inbound queue requirements

• Discussed Ben Crump team's phone number setup

• Ryan clarified phone number porting process for Crump team

• 🌍 *Nicholas' Travel Recap* (04:25 - 10:04)

• Nicholas shared experiences from his trip to Serbia and Bosnia

• Discussed food poisoning incident and weather challenges

• Observed cultural events like water polo match between Serbia and Croatia

• 📊 *Project Updates and Scheduling* (10:23 - 13:03)

• Ryan discussed upcoming meetings and travel plans

• Explained solution for LR casetypes revenue rates table using BigQuery

• Discussed scheduled SQL query to update case types automatically

• 💼 *Financial Reporting Challenges* (13:28 - 17:32)

• Nicholas raised issue with splitting out new contract data for Flatirons

• Discussed need to map lead IDs for detailed financial reporting

• Identified specific case types for Flatirons: Illinois juvenile hall and AFFF

• 🛠️ *Development Tasks and Portal Progress* (17:54 - 20:08)

• Ryan to coordinate with Quint and Nick McFadden on calculate performance tip version

• Discussed SSL certificate maintenance for Light Sail

• Brian to present TIP portal progress to Ryan for review before delivery to Tony's team

Gist • The meeting focused on project updates, including Five9 implementation, financial reporting challenges, and upcoming development tasks.

Bullet Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-19 14:21:41

• 🔄 Five9 Implementation Update: Nicholas provided updates on inbound queue requirements and the Crump team's phone number setup.

• 🌍 Nicholas' Travel Recap: Nicholas shared experiences from his recent trip to Serbia and Bosnia, including cultural observations.

• 📊 Project Updates and Scheduling: Ryan discussed upcoming meetings and travel plans along with solutions for revenue rates table automation.

• 💼 Financial Reporting Challenges: Challenges in financial reporting were raised, particularly around contract data and lead ID mapping.

• 🛠️ Development Tasks and Portal Progress: Ryan coordinated tasks related to performance tips and SSL certificate maintenance.

Short Summary • The Tech Project Status Weekly meeting covered essential updates, beginning with Nicholas discussing the progress of the Five9 implementation, highlighting inbound queue requirements and the setup of the Crump team's phone number. He also shared insights from his recent trip to Serbia and Bosnia, including a food poisoning incident and observations of local cultural events. Ryan outlined upcoming meetings and travel plans while proposing a solution for automating the revenue rates table for LR case types using BigQuery. Challenges were identified in financial reporting, particularly in splitting new contract data for Flatirons and mapping lead IDs for detailed reporting. Development tasks were assigned, with Ryan coordinating efforts on the performance tip version and SSL maintenance, while action items were designated to ensure project continuity, including presentations related to the TIP portal and financial reporting.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-20 13:09:09

Title: TIP Portal for external users Date: Tue Aug 20 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the introductory and exploratory business meeting titled "TIP Portal for External Users," participants Ryan and Brian delved into the setup and access issues of the TIP Portal, addressing user permission challenges and the process of inviting external users. Following initial technical discussions, the meeting transitioned to introductions of Sphere and TIP/Shield Legal representatives, with Cameron providing an overview of their business model related to mass tort acquisition. Sphere's capabilities, particularly in AI and data services, were highlighted alongside ongoing projects in data science, including predictive modeling. The conversation then explored potential integrations between Shield and TIP, identifying challenges with existing CRM systems and data flow to law firms. The meeting concluded by outlining next steps for collaboration, including sending a non-disclosure agreement (NDA) and planning future discussions on specific projects, while action items were assigned to relevant participants for follow-up.

Action Items • *Brian*

• Send NDA to Cameron for review (02:01:52)

• Forward Shane's response to Ryan when received (17:46)

• *Cameron*

• Review NDA and send to legal team (01:48:18)

• *Ryan*

• Follow up with Sphere team after NDA is signed (01:49:35)

Shorthand Bullet • 🔧 *TIP Portal Setup and Access* (00:20 - 05:29)

• Ryan and Brian discussing TIP Portal setup

• Brian creating a new app for cost adjustment tool

• Ryan requesting access as an external user

• Brian inviting Ryan as a new user for the TIP price adjustment tool

• 🔐 *User Permissions and Access Issues* (05:35 - 13:48)

• Ryan logging in and experiencing incorrect user permissions

• Discussion about user administration and external user setup

• Brian attempting to adjust user permissions

• Identifying issues with all users group and viewer-only access

• 📧 *Contacting Support for Assistance* (13:52 - 17:43)

• Brian composing an email to Shane for support

• Ryan suggesting to include user access setup information

• Agreement to wait for Shane's response before proceeding

• 👥 *Introduction and Company Overview* (01:01:50 - 01:11:59)

• Introductions of participants from Sphere and TIP/Shield Legal

• Cameron explaining TIP and Shield Legal's business model

• Discussion of mass tort acquisition and claimant intake process

• 🏢 *Sphere Company* Presentation** (01:13:46 - 01:22:58)

• Sphere team presenting their company capabilities

• Overview of Sphere's AI and data services

• Discussion of Sphere's experience in financial services and fintech

• 🤖 *AI and Data Science Projects* (01:23:41 - 01:33:54)

• Ryan and James discussing current AI and data science projects

• Explanation of predictive modeling and customer journey optimization

• Discussion of data security and privacy concerns

• 💼 *Business* Systems Integration** (01:35:11 - 01:46:21)

• Exploration of potential integration between Shield and TIP

• Discussion of current CRM systems and challenges

• Consideration of Salesforce implementation and licensing costs

• 🔄 *Data Flow and Integration Challenges* (01:47:05 - 01:55:39)

• Addressing data transfer issues between TIP and law firms

• Discussion of case management software incompatibilities

• Exploration of potential solutions for streamlining data flow

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-20 13:09:09

• 🤝 *Next Steps and Potential Collaboration* (01:56:55 - 02:02:28)

• Discussing potential areas for Sphere to assist TIP/Shield Legal

• Agreement to send NDA for further discussions

• Consideration of future meeting to explore specific projects

Gist • Ryan and Brian discussed the TIP Portal setup, user permissions, and potential collaborations with Sphere and TIP/Shield Legal.

Bullet Gist • 🔑 TIP Portal Access Issues: Ryan and Brian addressed user permission challenges regarding the TIP Portal.

• 🤝 Collaboration Opportunities: The meeting outlined potential collaborations between Sphere and TIP/Shield Legal.

• 📊 AI and Data Services: Sphere highlighted its capabilities in AI and ongoing data science projects.

• 📝 Next Steps Defined: Action items and plans for sending an NDA were established for future discussions.

• 💡 CRM Integration Challenges: Challenges with existing CRM systems were identified in the integration discussion.

Short Summary • In the introductory meeting titled 'TIP Portal for External Users,' participants Ryan and Brian focused on the setup and access challenges of the TIP Portal, particularly user permission issues and the invitation process for external users. Following technical discussions, representatives from Sphere and TIP/Shield Legal were introduced, with Cameron elaborating on their business model related to mass tort acquisition. The meeting highlighted Sphere's strengths in AI and data services, along with ongoing data science projects, including predictive modeling. Additionally, the conversation explored potential integrations between Shield and TIP, addressing challenges related to existing CRM systems and data flow to law firms. The meeting concluded with a plan for collaboration, including sending a non-disclosure agreement (NDA) and scheduling future discussions on specific projects, with action items assigned to participants for follow-up.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-21 15:25:33

Title: Shield Lambdas & AWS Date: Wed Aug 21 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: quint.johnson@gmail.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the Project Update and Task Assignment Meeting focused on "Shield Lambdas & AWS," key updates were discussed regarding ongoing projects and resource challenges. Ryan and Nick are collaborating on the Looker Enterprise and the integration of Law Ruler with BigQuery, but are facing bandwidth limitations due to staff shortages. The meeting highlighted the urgent need to address an SSL certificate on Light Sail by August 22, with Quint assigned to this task and required to resume work on the Calculate Performance Tip branch after the Burning Man event on September 3. Issues concerning data corruption in the Law Ruler stash report were resolved by Ryan, who recreated the corrupted reports. Action items were assigned, including Quint's responsibility to provide an estimate for the Calculate Performance Tip project's completion and to notify Ryan via Slack upon addressing the SSL certificate. Ryan will follow up with Quint on September 3 regarding the project status.

Action Items • *Quint Johnson*

• Handle SSL certificate on Light Sail before August 22 (02:27)

• Resume work on Calculate Performance Tip branch after Burning Man (02:53)

• Provide estimate for completing Calculate Performance Tip project (16:06)

• Message Ryan on Slack when SSL certificate is addressed (15:27)

• *Ryan Vaspra*

• Ping Quint on September 3 about Calculate Performance Tip project (17:18)

Shorthand Bullet • 🔧 *Project Updates and Bandwidth Issues* (00:55 - 02:27)

• Ryan and Nick working on Looker Enterprise and retool portal for client dashboard

• Nick building new pipelines from Law Ruler to BigQuery using Google Cloud Function

• Bandwidth issues due to staff limitations and ongoing integrations

• 📊 *SSL Certificate and Calculate Performance Tip* (02:27 - 08:29)

• SSL certificate on Light Sail needs to be addressed before August 22

• Quint to resume work on Calculate Performance Tip branch

• Issue with Calculate Performance Tip possibly due to inclusion of 'referral' in lead ID

• Do Not Touch Tip table in DB Master used for testing and comparison

• Financial log query explained, focusing on Shield Legal data

• 🔍 *Data Corruption and Reporting Issues* (10:35 - 13:42)

• Law Ruler stash report corrupted, causing data discrepancies

• Multiple sends of corrupted reports leading to missing deals

• Ryan discovered and fixed the issue by recreating corrupted reports

• 📅 *Next Steps and Timelines* (13:42 - 17:28)

• Quint to handle Light Sail SSL certificate before Burning Man

• Calculate Performance Tip project to resume after Burning Man (September 3)

• Estimate needed for Calculate Performance Tip completion

• Importance of completing Calculate Performance Tip to reduce daily workload

Gist • The meeting focused on project updates for Shield Lambdas & AWS, addressing resource challenges and urgent tasks.

Bullet Gist • 🔧 Project Updates and Bandwidth Issues: Ryan and Nick are collaborating on Looker Enterprise and facing staff limitations.

• 📊 SSL Certificate Deadline: Quint must resolve the SSL certificate issue by August 22 before the Burning Man event.

• 🔍 Data Corruption Resolved: Ryan fixed the corrupted Law Ruler stash report by recreating it.

• 📅 Next Steps Post-Burning Man: Quint will resume the Calculate Performance Tip project after September 3.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-21 15:25:33

• ⚙️ Action Items Assigned: Quint needs to provide an estimate for the Calculate Performance Tip's completion.

Short Summary • In the Project Update and Task Assignment Meeting for Shield Lambdas & AWS, Ryan and Nick discussed their collaborative efforts on Looker Enterprise and the integration of Law Ruler with BigQuery, while facing bandwidth limitations due to staff shortages. An urgent issue regarding an SSL certificate on Light Sail was identified, necessitating attention by August 22, with Quint assigned to resolve it. Quint is also expected to resume work on the Calculate Performance Tip branch following the Burning Man event on September 3. Ryan successfully addressed data corruption issues in the Law Ruler stash report by recreating the corrupted reports. Action items included Quint's responsibility to provide a completion estimate for the Calculate Performance Tip project and to notify Ryan via Slack once the SSL certificate issue is addressed. Ryan will follow up with Quint on the project's status after September 3.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-26 14:59:41

Title: Tech Project Status Weekly Date: Mon Aug 26 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com, dschussler@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the Tech Project Status Weekly meeting, team members discussed updates and challenges regarding the API and Retool portal, emphasizing improvements for tip case pricing and usability enhancements, particularly in field refreshing and billable rate formatting. Brian is tasked with resolving refresh issues and removing a redundant field in the portal, while Ryan will conduct a review session with him. Integration challenges were highlighted, focusing on issues with data transfers, particularly with Law Ruler and Smart Advocate, and the need for better communication was stressed. David is set to assist with morning financials and will invest some time in learning the relevant processes. Action items were assigned to team members, with deadlines established for the completion of critical tasks.

Action Items • *Brian Hirst*

• Fix refresh issues in the retool portal (10:04)

• Remove 'new billable rate' field and adjust formatting (19:22)

• Complete portal updates by next meeting (20:54)

• *Nick McFadden*

• Create benchmark report in Looker enterprise (05:43)

• *Ryan Vaspra*

• Review retool portal with Brian (02:43)

• Work on order summary component (05:43)

• Discuss David's role in morning financials with Cameron (23:26)

• *David Schussler*

• Start learning morning financials process (23:26)

Shorthand Bullet • 🔧 *API and Retool Portal Updates* (00:00 - 09:28)

• Brian working on API and retool portal for tip case pricing

• Ryan set meeting with Brian to review retool portal

• Portal needs white labeling and usability improvements

• Looker enterprise embed feature discussed as next step

• Nick to create benchmark report in Looker enterprise

• Ryan working on order summary component

• 📊 *Retool Portal Improvements* (09:28 - 14:43)

• Brian addressing refresh issues in the portal

• Ryan demonstrated issues with case type switching and field refreshing

• Discussed removal of 'new billable rate' field

• Ryan requested formatting changes for current and new billable rate fields

• 💼 *David's Role* and Morning Financials** (15:22 - 19:57)

• David to help with integrations and morning financials

• Ryan emphasized need for backup on morning financials

• Discussed potential for David to spend 20% time on learning morning financials

• 🔄 *Integration Challenges and Lambda Issues* (20:17 - 34:33)

• Discussed corrupted status reports in Law Ruler

• Ryan explained issues with lead transfers between campaigns

• Suggested adding contract ID to naming convention in Law Ruler

• Explained complexities of data warehouse and views in BigQuery

• 🚀 *Integration Engineer Challenges* (36:07 - 52:38)

• Discussed difficulties with law firm integrations, particularly Smart Advocate

• Highlighted issues with field customization and API activation

• Emphasized need for constant communication with Cameron

• Discussed policy of not transforming data during integrations

• Addressed challenges with field naming and character case sensitivity

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-26 14:59:41

• The meeting focused on updates and challenges related to the API and Retool portal, aiming to enhance usability and data integration.

Bullet Gist • 🔧 API and Retool Updates: Brian is working on API improvements, while Ryan will review the portal for better usability.

• 📊 Retool Improvements: Refresh issues were discussed, along with the removal of redundant fields and formatting changes.

• 💼 David's Financial Role: David will support morning financials and dedicate time to learn the related processes.

• 🔄 Integration Challenges: Integration issues with Law Ruler and Smart Advocate highlighted the need for improved communication.

• 🚀 Field Customization Issues: Challenges with field customization and data transformation during integrations were addressed.

Short Summary • During the Tech Project Status Weekly meeting, team members discussed various updates and challenges pertaining to the API and Retool portal, particularly focusing on improvements for tip case pricing and usability enhancements. Brian is addressing refresh issues and plans to remove a redundant field from the portal, while Ryan is set to conduct a review session with him. Integration challenges were a significant focus, especially concerning data transfers with Law Ruler and Smart Advocate, where the need for better communication was emphasized. David will assist with morning financials and invest time in learning the relevant processes. The meeting assigned action items to team members with specific deadlines to ensure critical tasks are completed promptly.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-28 14:10:25

Title: BLX SEO Clients Date: Wed Aug 28 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the BLX SEO Clients team meeting, the discussions focused on project timelines, team responsibilities, and upcoming deadlines, laying a foundation for effective collaboration. Key decisions included finalizing project milestones and assigning specific tasks to team members to ensure accountability. The meeting concluded with the scheduling of the next meeting date. An action item was assigned to Kelly Smith to review the meeting notes and extract key discussion points and action items.

Action Items • *Kelly Smith*

• Review the meeting notes and identify key discussion points and action items (00:05:00)

Shorthand Bullet • 📝 *Meeting Overview* (00:00:00 - 00:10:00)

• Discussion on project timelines

• Review of team responsibilities

• Planning for upcoming deadlines

• 🔍 *Key Decisions* (00:10:01 - 00:20:00)

• Finalized project milestones

• Assigned tasks to team members

• Set next meeting date

Gist • The meeting aimed to finalize project milestones and assign tasks, ensuring clear responsibilities and deadlines for effective collaboration.

Bullet Gist • 📝 Meeting Overview: The team discussed project timelines and responsibilities.

• 🔍 Key Decisions: Project milestones were finalized, and tasks were assigned to ensure accountability.

• 📅 Next Steps: The next meeting date was scheduled for ongoing collaboration.

• ✅ Action Items: Kelly Smith was tasked with reviewing notes for key points and action items.

Short Summary • In the BLX SEO Clients team meeting, the primary focus was on establishing project timelines and delegating responsibilities among team members. Discussions included a comprehensive review of each member's roles in relation to upcoming deadlines, which laid a solid foundation for effective collaboration. Key decisions were made, including the finalization of project milestones and the assignment of specific tasks to ensure accountability. The meeting concluded with scheduling the next meeting date and assigning Kelly Smith the action item to review the notes and extract crucial discussion points and action items for further clarity.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-29 15:24:50

Title: BCL Next Steps Date: Thu Aug 29 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@shield-legal.com, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The "BCL Next Steps" meeting focused on progress updates and strategic planning for enhancing case tracking and content strategy. Ryan and Uzoma began with a brief introduction and casual conversation before diving into data analysis, where Ryan shared improvements in tracking, reviewed case retention metrics, and highlighted significant organic case growth of 400% since 2023. The team examined the dashboard for case type distribution and discussed call tracking enhancements, including setting up a webhook for social media leads. They also deliberated on content strategies to enhance attorney visibility, suggesting article postings on bio pages. In the wrap-up, Ryan showcased a pivot table for case type analysis, while action items were assigned to improve campaign performance, including setting up webhooks for additional social media platforms, updating budget spents, and initiating monthly leadership discussions on case priorities.

Action Items • *Ryan Vaspra*

• Set up webhooks for other social media platforms (34:50)

• Update budget spent for the last quarter and next quarter in the campaign breakdown (48:49)

• Prepare s1 tracking measurement for the next meeting (49:30)

• *Uzoma Obasi*

• Start monthly meetings with leadership team to discuss case priorities and content strategy (40:02)

• *Latoya*

• Work on passing URL parameters from social posts to capture s1 data (29:34)

Shorthand Bullet • 🔄 *Meeting Introduction and Small Talk* (00:01 - 01:53)

• Ryan and Uzoma exchange greetings

• Brief discussion about football and youth football participation rates

• 📊 *Data Analysis and Reporting* (02:56 - 14:22)

• Ryan explains improvements in data tracking and reporting

• Discussion of BCO retained cases and status updates in Smart Advocate

• Ryan demonstrates export of 3167 cases for analysis

• Explanation of s1 tracking parameter for social media links

• Mention of 400% growth in organic cases from 2023 to present

• 📈 *Dashboard and Case Review Analysis* (15:06 - 34:50)

• Review of dashboard showing case retention and reviews

• Discussion of case types and their distribution

• Explanation of call tracking metrics and social media lead tracking

• Ryan sets up webhook for tracking social media phone leads

• 🔧 *Content Strategy and Tracking Improvements* (36:02 - 43:40)

• Discussion about content creation process for attorneys

• Ryan suggests posting articles on attorney bio pages

• Review of top pages on the website

• 📑 *Case Type Analysis and Meeting Wrap-up* (43:49 - 50:07)

• Uzoma requests analysis of case types from leads and closed cases

• Ryan demonstrates pivot table for case type summary

• Review of campaign performance and ROI

• Brief discussion about Labor Day plans

Gist • The meeting focused on progress updates and strategic planning for enhancing case tracking and content strategy.

Bullet Gist • 🔄 Meeting Kick-off: Ryan and Uzoma exchanged greetings and discussed youth football participation.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-08-29 15:24:50

• 📊 Data Analysis Highlights: Ryan showcased significant improvements in tracking, including a 400% growth in organic cases since 2023.

• 📈 Dashboard Review: The team analyzed case retention metrics and the distribution of case types.

• 🔧 Content Strategy Discussion: Ryan proposed article postings on attorney bio pages to enhance visibility.

• 📑 Action Items and Wrap-up: Ryan demonstrated a pivot table and assigned tasks for campaign performance improvement.

Short Summary • Ryan and Uzoma led the "BCL Next Steps" meeting, discussing significant progress in case tracking and content strategy enhancements. Ryan presented improvements in data analysis, revealing a remarkable 400% growth in organic case retention since 2023, alongside a review of case types and metrics. They explored enhancements in call tracking, including the implementation of a webhook for social media leads. The team deliberated on content strategies aimed at increasing attorney visibility, suggesting article postings on bio pages. In the concluding segment, Ryan showcased a pivot table for case type analysis, while action items were assigned to further improve campaign performance, including extending webhook setups to more social media platforms and initiating leadership discussions on case priorities.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-03 12:01:01

Title: Tech Project Status Weekly Date: Tue Sep 03 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com, dschussler@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Tech Project Status Weekly meeting, team members shared personal highlights from the Labor Day weekend before diving into project updates and challenges. Nick McFadden reported progress on critical items focused on the business data warehouse, while Cameron prioritized integrations, recently aided by new data engineer David Schussler. A debate arose regarding integration strategies between Gmail and Power Automate. Ryan provided updates on the dashboard interface and reconciling data from Flatirons, highlighting the creation of the Looker enterprise dashboard 'shield reconciliation.' In portal development, Brian showcased a new portal built using Retool and discussed white-labeling and enhancing its features, alongside seeking assistance with date input syntax. Ongoing projects included law ruler lead inbox workflows and plans for developing financial log tables, with potential contributions from James in Python development for Google Cloud Functions. Action items were assigned to Brian, Nick, James, and Ryan, focusing on white-labeling, client methodology, and continued work on ongoing projects.

Action Items • *Brian Hirst*

• White-label the Retool portal (15:24)

• Build another account for Shield with Looker enterprise embed (17:47)

• Implement user group methodology for multiple clients in Retool (22:42)

• *Nick McFadden*

• Continue working on law ruler lead inbox and intake questions pipelines (26:52)

• *James Scott*

• Be prepared to help with Google Cloud Function Python development if needed (30:06)

• *Ryan Vaspra*

• Work on dashboard interface and reconcile Flatirons data (12:42)

• Attend meeting with Chris for DBT table builds (14:11)

Shorthand Bullet • 🏖️ *Labor Day Weekend Recap* (02:29 - 05:09)

• Ryan spent time at the lake with family and friends

• Brian went to horse races and stayed out of the house due to girlfriend studying

• 🚀 *Project Updates and Challenges* (05:09 - 13:42)

• Nick McFadden working on critical items for business data warehouse

• Integrations are top priority for Cameron

• New data engineer David Schussler hired, focusing on integrations

• Debate over integration issues: Gmail vs Power Automate

• Ryan working on dashboard interface and reconciling Flatirons data

• Looker enterprise dashboard called 'shield reconciliation' created

• 💻 *Portal Development* and Retool Discussion** (14:00 - 19:31)

• Brian built a portal using Retool

• Plans to white-label the portal and add more features

• Discussion on user group methodology for multiple clients

• Brian seeking help with date input syntax in Retool

• 🔧 *Ongoing Projects and Future Plans* (19:31 - 31:13)

• Nick working on law ruler lead inbox and intake questions pipelines

• Plans to create IO staffing revenue and expense tables

• Need to develop IO tip financial log real-time and validation tables

• Potential involvement of James in Google Cloud Function Python development

• Meeting scheduled with Chris for DBT table builds

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-03 12:01:01

Gist • The meeting focused on project updates, challenges, and personal highlights from the Labor Day weekend.

Bullet Gist • 💼 Project Updates: Team members reported significant progress on various projects, including the business data warehouse and dashboard interface.

• 🤝 Integration Discussions: Debate on integration strategies for Gmail and Power Automate highlighted the team's collaborative approach.

• 🖥️ Portal Development: Brian showcased a new Retool-built portal, focusing on white-labeling and improving its features.

• 📊 Ongoing Projects: Projects like law ruler lead inbox workflows and financial log tables are in progress, with contributions from team members.

• ✅ Action Items: Action items were assigned to key members, ensuring continued progress on various tasks.

Short Summary • During the Tech Project Status Weekly meeting, team members shared their personal highlights from the Labor Day weekend before transitioning to project updates. Nick McFadden reported on progress related to the business data warehouse, while Cameron emphasized the importance of integrations, which have recently seen enhancements thanks to new data engineer David Schussler. A lively debate occurred regarding the integration strategies between Gmail and Power Automate. Ryan updated the team on the dashboard interface and the reconciliation of data from Flatirons, notably the development of the Looker enterprise dashboard for 'shield reconciliation.' In the realm of portal development, Brian presented a new portal built using Retool, discussing its white-labeling and feature enhancements, while seeking help with date input syntax. Ongoing projects included workflows for law ruler lead inboxes and plans for financial log tables, with James potentially contributing Python development for Google Cloud Functions. Action items were assigned to Brian, Nick, James, and Ryan for various ongoing tasks.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-03 12:41:21

Title: Ryan/Cam - connect Date: Tue Sep 03 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@themedialab.agency, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • During the Project Planning and Status Update meeting, Ryan and Cameron discussed the integration of the Sakaloff asbestos campaign, emphasizing the need for consistency with the current system and effective data synchronization into Slack. Ryan proposed either utilizing API access or Law Ruler for this integration and highlighted the importance of automating workflows to minimize manual errors, suggesting a webhook method. An update on ongoing projects included Nick's automation for Cello and a new dashboard for campaign rate management, alongside discussions on MDL case thresholds and FDA data consolidation. Cameron raised concerns regarding missing campaigns in the Flatirons dashboard, prompting Ryan to address client attribution issues in Copper CRM. Action items included Ryan setting up integration for Sakaloff, creating a custom campaign code, investigating dashboard discrepancies, and scheduling a follow-up with the Sakaloff team, while Cameron will contact Bill regarding the integration.

Action Items • *Ryan Vaspra*

• Work with tech teams to set up integration for Sakaloff asbestos campaign (07:56)

• Bring up Sakaloff integration at the afternoon integration meeting (22:02)

• Create a custom campaign code for Sakaloff asbestos calls (23:52)

• Investigate and fix missing Flatirons campaigns in the dashboard (35:09)

• Check new opportunity IDs sent by Melissa and update the system (34:35)

• Fix client attribution for Flatirons campaigns in Copper CRM (39:36)

• Schedule meeting with Sakaloff team for tomorrow (40:19)

• *Cameron Rentch*

• Send email to Bill regarding Sakaloff integration (21:47)

Shorthand Bullet • 🔧 *Sakaloff Asbestos Campaign Integration* (05:58 - 15:24)

• Cameron explains Sakaloff's request for an asbestos campaign

• Requirement: Everything must look the same as current system

• Need to pipe data back into Slack, matching lead IDs and S1s

• Daily decline reports required, similar to current process

• Ryan proposes solutions: API access to Slack or using Law Ruler

• 📊 *Integration Details and Workflow* (16:37 - 27:07)

• Discussion on best method for seamless integration

• Emphasis on automatic processes to avoid manual errors

• Ryan suggests using webhook method for Sakaloff

• Cameron stresses importance of media buyers not noticing difference

• Ryan outlines potential workflow using Law Ruler and automations

• 🚀 *Ongoing Projects and Dashboards* (27:07 - 35:31)

• Update on Nick's automation work for Cello

• Ryan showcases new dashboard for campaign rate management

• Discussion on MDL case thresholds and feasibility dashboards

• James working on FDA data consolidation for clearer product listings

• Potential for AI-driven settlement value estimates in the future

• 📈 *Data Reconciliation and Dashboard Issues* (36:26 - 40:20)

• Cameron raises concerns about missing campaigns in Flatirons dashboard

• Ryan to investigate and fix client attribution in Copper CRM

• Discussion on syncing historical data and resolving discrepancies

Gist • The meeting focused on integrating the Sakaloff asbestos campaign and updating ongoing projects to improve data synchronization and workflow automation.

Bullet Gist • 🔗 Integration Discussion: Ryan and Cameron discussed the integration of the Sakaloff asbestos campaign with a focus on data synchronization.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-03 12:41:21

• ⚙️ Automation Importance: Emphasizing automated workflows, Ryan proposed solutions like API access or webhooks to minimize manual errors.

• 📊 Project Updates: Updates included Nick's automation for Cello and a new dashboard for managing campaign rates.

• ❗ Dashboard Concerns: Cameron raised issues regarding missing campaigns in the Flatirons dashboard and client attribution in Copper CRM.

• ✅ Action Items: Key action items were outlined, including integration setup and follow-up with the Sakaloff team.

Short Summary • During the Project Planning and Status Update meeting, Ryan and Cameron discussed integrating the Sakaloff asbestos campaign while ensuring consistency with the current system and effective data synchronization into Slack. Ryan proposed utilizing API access or Law Ruler for this integration and emphasized automating workflows to minimize manual errors, suggesting a webhook method. They also reviewed ongoing projects, including Nick's automation efforts for Cello and a new dashboard for campaign rate management. Cameron raised concerns about missing campaigns in the Flatirons dashboard, which led to discussions about client attribution issues in Copper CRM. Action items included Ryan setting up the Sakaloff integration, creating a custom campaign code, investigating dashboard discrepancies, and scheduling a follow-up with the Sakaloff team, while Cameron would contact Bill regarding the integration.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-03 14:04:20

Title: Paid vs Spent Date: Tue Sep 03 2024 14:25:00 GMT-0400 (Eastern Daylight Time) Participants: markmaniora@shield-legal.com, ryan@brandlytics.io, gregowen@shield-legal.com, malissa@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • In the Technical Discussion and Problem-Solving meeting titled "Paid vs Spent," the team addressed several key issues related to dashboard creation and data synchronization. Ryan highlighted the importance of using consistent naming conventions between Leadspedia and Copper to facilitate accurate data retrieval, showcasing how to update contract names accordingly. The meeting also included a detailed examination of data synchronization challenges, specifically addressing errors in the dashboard and verifying the accuracy of contract counts, where discrepancies were noted between expected and actual numbers. Further, the team explored the complexities of the database structure that underpins the dashboard, discussing the performance issues that caused slow loading times and the critical need for data consistency. Action items were established, including marking customer firms in Copper to align with Leadspedia contract names and updating relevant fields for new campaigns, ensuring streamlined data management moving forward.

Action Items • *Mark Maniora*

• Ensure customer firms in Copper match Leadspedia contract names when updating with contract IDs (09:36)

• *Melissa*

• Update vertical field in Copper when Patsy creates a new campaign without a vertical (24:42)

• *unassigned*

• Inform Cameron that all 23 Flatirons orders are now in the dashboard (25:16)

Shorthand Bullet • 🔧 *Dashboard Creation and Naming Conventions* (00:00 - 08:55)

• Ryan explains the issue with using Leadspedia contract names in the dashboard

• Copper contract name is created using vertical name, customer firms, call center, and sale type

• Importance of accurate field information for Cameron to find things

• Example given: NeC baby form, DL, flat irons

• Ryan demonstrates how to update contract names in Copper to match Leadspedia

• 📊 *Data Synchronization and Filtering* (08:57 - 13:16)

• Ryan checks if changes have synced in the dashboard

• Explanation of error messages in the dashboard

• Confirmation that customer firm field must match Leadspedia contract name

• Ryan demonstrates filtering for Flatirons contracts

• Team identifies missing contracts and investigates why

• 🔍 *Troubleshooting and Verification* (13:19 - 16:35)

• Ryan and team verify that all changes have been applied correctly

• Confirmation of 23 Flatirons contracts in the dashboard

• Greg points out a discrepancy in the number of contracts (30 vs 23)

• Ryan explains the filtering process and why some contracts are excluded

• 🏗️ *Database Structure and Performance* (16:35 - 26:40)

• Ryan explains the complex database structure behind the dashboard

• Discussion of views, tables, and cross-reference tables in BigQuery

• Explanation of why the dashboard is slow to load and update

• Importance of maintaining data consistency across Copper and Leadspedia

• Ryan emphasizes the need for accurate data entry and updates

Gist • The meeting focused on addressing data synchronization issues and establishing consistent naming conventions for dashboards.

Bullet Gist • 🔍 Data Consistency: The team highlighted the importance of consistent naming conventions for accurate data retrieval.

• ⚠️ Synchronization Challenges: Errors in the dashboard and discrepancies in contract counts were major discussion points.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-03 14:04:20

• 🗄️ Database Complexity: The complexities of the database structure contributed to slow loading times.

• ✅ Action Items: Future steps include updating contract names and syncing data more effectively.

• 📊 Dashboard Performance: The meeting addressed critical performance issues affecting the dashboard.

Short Summary • In the 'Paid vs Spent' meeting, the team, led by Ryan, emphasized the necessity of consistent naming conventions between Leadspedia and Copper to enhance data retrieval accuracy. They examined the challenges in data synchronization, particularly errors in the dashboard and discrepancies in contract counts, contrasting expected versus actual numbers. The complexities of the underlying database structure were also discussed, highlighting performance issues that resulted in slow loading times and the critical need for data consistency. Action items were created to improve data management, including marking customer firms in Copper to match Leadspedia contract names and updating fields for new campaigns, ensuring a streamlined approach moving forward.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-04 14:02:57

Title: Shield Legal: Chris/Ryan sync (Brian Hirst) Date: Wed Sep 04 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, chris.goodell@bytecode.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • In the recent Technical Discussion and Planning meeting titled "Shield Legal: Chris/Ryan sync," the team focused on enhancing data processing and financial reporting through the implementation of DBT and the migration from AWS to Google Cloud Platform (GCP). Key topics included the updating of financial data in AWS, transitioning to DBT SQL for data management, and the creation of a historical table for revenue rate changes. Discussions emphasized the need for an 'upsert' table and the challenges of real-time updates within DBT. Additionally, the group strategized on migrating views to GCP and improving a complex financial dashboard's performance. Action items were assigned to individuals, with Chris tasked to build a proof of concept for the historical revenue rates table and assist in reconstructing a financial details view, while Ryan would provide DBT access and update the Looker model for compatibility with GCP. Brian was to collaborate on the implementation efforts, ensuring effective orchestration and management of data streams moving forward.

Action Items • *Chris Goodell*

• Build a proof of concept for the historical revenue rates table in DBT (36:50)

• Create a DBT snapshot for the IOLR case types revenue rates table (36:08)

• Assist in reconstructing the financial details view in DBT or BigQuery (46:00)

• *Ryan Vaspra*

• Provide access to DBT for Chris (35:17)

• Update Looker model file to use new BigQuery connection (43:59)

• *Brian Hirst*

• Collaborate with Chris and Ryan on implementing the new DBT solutions (56:00)

Shorthand Bullet • 🔧 *Data Pipeline and DBT Implementation* (00:00 - 19:20)

• Ryan updating financial data in AWS system

• Transitioning from lambda to DBT SQL for data processing

• Discussion of LR case types pipeline and revenue rates table

• Brian created an app for updating revenue rates table

• Need to create a historical table for revenue rates changes

• 📊 *Financial Data Management* (19:22 - 30:50)

• Discussion on creating an 'upsert' table in DBT

• Need for a history-based table with its own primary key

• Challenges with real-time updates in DBT

• Consideration of running jobs at different frequencies

• 🔄 *Data Migration and Dashboard Integration* (30:50 - 37:43)

• Migrating from AWS to Google Cloud Platform

• Importing views and materialized views from postgres to GCP

• Need to update Looker model file to use new GCP connection

• 📈 *Dashboard and Financial Reporting* (37:43 - 51:02)

• Complex 49-page financial dashboard based on materialized view

• Need to recreate financial details view in DBT or BigQuery

• Discussion on improving dashboard performance

• 🛠️ *DBT Orchestration and Best Practices* (52:18 - 58:23)

• Plan to catalog data sources and replication frequencies

• Discussion on defining jobs based on replication cadence

• Importance of proper DBT orchestration for efficient data management

Gist • The meeting aimed to enhance data processing and financial reporting by migrating to GCP and implementing DBT.

Bullet Gist • 🔄 Data Migration to GCP: The team is transitioning from AWS to Google Cloud Platform for better data management.

• 📊 DBT Implementation: DBT SQL will be utilized to enhance data processing and reporting efficiency.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-04 14:02:57

• 📈 Historical Revenue Table: A new historical table will be created to track changes in revenue rates.

• ⚙️ Performance Improvement: Strategies were discussed to improve the performance of a complex financial dashboard.

• 📝 Assigned Action Items: Specific tasks were allocated to team members to ensure progress and accountability.

Short Summary • In the recent Technical Discussion and Planning meeting titled "Shield Legal: Chris/Ryan sync," the team concentrated on improving data processing and financial reporting. Key initiatives included updating financial data in AWS, transitioning to DBT SQL for efficient data management, and creating a historical table to track revenue rate changes. The discussions highlighted the necessity for an 'upsert' table and addressed the challenges of achieving real-time updates within DBT. Additionally, strategies were outlined for migrating views to Google Cloud Platform (GCP) and enhancing the performance of a complex financial dashboard. Action items were assigned, with Chris responsible for developing a proof of concept for the historical revenue rates table and reconstructing a financial details view, while Ryan was tasked with providing DBT access and updating the Looker model for GCP compatibility. Brian's role involved collaborating on the implementation efforts to ensure effective data stream management.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-09 14:50:35

Title: Tech Project Status Weekly Date: Mon Sep 09 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com, dschussler@shield-legal.com, ryan@shield-legal.com, dsurwill@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • In the Tech Project Status Weekly meeting, team members addressed key updates and challenges across various project components. The session began with a light weather discussion, where Brian shared his experience of a heat wave, followed by Ryan and Nicholas discussing differing weather patterns in their locations. Moving into project updates, Ryan outlined the integration plan with Sokolov, while Nick McFadden committed to preparing documentation on the Law Ruler API interface. The team agreed on creating new case types, automations for lead transfer, and database tables for tort intake cases. Integration support included progress on Microsoft 365, although Gmail integration was deemed unnecessary. Regarding dialer and reporting updates, Nicholas conducted internal outbound dialing tests, while Joe worked on establishing ghost email addresses and testing call functionalities. New members Daniel, Dustin, Zacharias, and James were welcomed. Action items for the upcoming week were assigned to various team members, ensuring continued momentum on project tasks.

Action Items • *Ryan Vaspra*

• Create new case type and statuses in Law Ruler (09:04)

• Set up automations for lead transfer and status updates (09:04)

• Create financial details in shield database using DBT tables (14:14)

• *Nick McFadden*

• Prepare documentation on Law Ruler API interface (09:04)

• *Brian Hirst*

• Focus on portal white-labeling and setup (15:34)

• Work with Mike Everhart to set up subdomain for reporting (16:08)

• *Nicholas Ward*

• Set up skill groups for dialer (22:53)

• Review reporting for dialer (22:53)

• Prepare for live test with soft phones (22:53)

• *unassigned*

• Migrate Rohat account to shield organization in Microsoft (20:25)

Shorthand Bullet • 🌡️ *Weather Discussion* (00:17 - 06:29)

• Brian experiencing heat wave in apartment

• Ryan discusses Oklahoma weather patterns

• Nicholas shares experience moving from California to Midwest

• Discussion on extreme weather conditions in different locations

• 🏢 *Project Updates* (06:29 - 17:43)

• Ryan explains integration plan with Sokolov

• Nick McFadden to prepare documentation on Law Ruler API interface

• New case type and statuses to be created in Law Ruler

• Automations to be set up for lead transfer and status updates

• DBT tables to be created for tort intake LR case types

• Brian to focus on portal white-labeling and setup

• 💻 *Integration Support* (17:49 - 19:37)

• Microsoft 365 integration progressing

• Gmail integration no longer needed

• Issue with device tokens limiting access for new hires

• 🔄 *Dialer and Reporting Updates* (19:40 - 48:50)

• Nicholas conducted internal testing on outbound dialing

• Joe setting up ghost email addresses

• Inbound and outbound testing in progress

• Need to set up skill groups and review reporting

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-09 14:50:35

• Plans to discuss call reporting data format with team

• Welcoming new team members: Daniel, Dustin, Zacharias, and James

Gist • Team members provided updates on project integrations, documentation, and upcoming tasks, while welcoming new members.

Bullet Gist • ☀️ Weather Chat: Brian and team members discussed recent weather patterns, lightening the mood before diving into project updates.

• 🔗 Integration Plans: Ryan presented the integration plan with Sokolov, setting the stage for upcoming project phases.

• 📄 Documentation Commitment: Nick McFadden will prepare essential documentation for the Law Ruler API interface.

• 📊 Dialer Updates: Nicholas performed internal outbound dialing tests, while Joe focused on ghost email addresses.

• 👥 New Additions: The team welcomed new members Daniel, Dustin, Zacharias, and James, enhancing project collaboration.

Short Summary • In the Tech Project Status Weekly meeting, team members discussed updates and challenges across various project components. Brian initiated a light conversation about a heat wave, leading to Ryan and Nicholas sharing their weather experiences. Ryan detailed the integration plan with Sokolov, while Nick McFadden committed to preparing documentation for the Law Ruler API interface. The team agreed on creating new case types, automations for lead transfer, and setting up database tables for tort intake cases. Progress on Microsoft 365 integration was noted, though Gmail integration was deemed unnecessary. Nicholas conducted tests for internal outbound dialing, and Joe worked on establishing ghost email addresses and testing call functionalities. New members Daniel, Dustin, Zacharias, and James were welcomed, and action items were assigned to ensure continued progress on project tasks for the upcoming week.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-10 14:50:43

Title: DBT tables for Historical Data (Chris Goodell) Date: Tue Sep 10 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: chris.goodell@bytecode.io, ryan@brandlytics.io, brian@shield-legal.com, nickmcfadden@shield-legal.com, ryan@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • In the recent Technical Implementation and Project Restructuring meeting led by Chris Goodell, the team focused on several key areas regarding the DBT project. The restructuring involved renaming the 'intermediate' folder to 'workspace,' setting up specific folders for raw data ingestion and analytics, and adhering to best practices for project setup. Data modeling was emphasized, particularly the use of sources, refs, and templated references for improved DAGs, alongside discussions on materialization strategies. Schema and environment configurations were also covered, including the use of macros and addressing schema naming issues. Project cleanup measures involved disabling unused models, renaming existing ones for clarity, and planning for the organization of BigQuery datasets. Finally, strategies were discussed for transitioning Looker from staging to production, resolving issues with missing tables, and troubleshooting merge conflicts. Action items were assigned to Chris Goodell and Ryan Vaspra for debugging, project updates, and future cleanups as the team looked to implement similar solutions for the Shield aspect of the project.

Action Items • *Chris Goodell*

• Debug and fix the 'none' dataset issue in BigQuery (56:49)

• Update the Shield version of the DBT project with the new organization structure (07:45)

• Send documentation on DBT utils and other helpful DBT resources to the team (01:03:27)

• Create tipprodworkspace and tipstagingworkspace in BigQuery (01:13:52)

• *Ryan Vaspra*

• Review and validate changes in BigQuery after Chris's updates (01:34:47)

• *Ryan Vaspra and Chris Goodell*

• Reconvene to clean up the project and discuss the Shield side implementation (01:34:26)

Shorthand Bullet • 🔧 *DBT Project Restructuring* (00:00 - 15:20)

• Chris Goodell explained the restructuring of the DBT project

• Renamed 'intermediate' folder to 'workspace'

• Stage folder for raw data ingestion

• Analytics folder for pristine data for dashboards

• Subfolders created for data sources (Connex and Law Ruler)

• Implemented best practices for DBT project setup

• 📊 *Data Modeling and Transformations* (15:24 - 29:24)

• Discussed the use of sources and refs in DBT models

• Explained the importance of using templated references for the DAG

• Introduced DBT utils package and its benefits

• Discussed materialization strategies (tables vs views)

• 🔄 *Schema and Environment Configuration* (29:28 - 42:38)

• Explained the use of macros for generating schema names

• Discussed environment variables and their impact on builds

• Addressed issues with schema naming in staging environment

• Ryan and Chris worked on updating the generateschemaname macro

• 🧹 *Project Cleanup and Renaming* (42:41 - 59:19)

• Identified and disabled unused models (e.g., Xref)

• Renamed models with 'DBT' prefix for easier identification in BigQuery

• Discussed the organization of schemas and datasets in BigQuery

• Planned cleanup of old and unused datasets

• 🔀 *Production Setup and Looker Integration* (59:28 - 01:14:36)

• Discussed strategy for switching Looker from staging to production data

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-10 14:50:43

• Renamed snapshots and other models for consistency

• Planned creation of production workspace and staging workspace

• Addressed issues with missing tables in BigQuery

• 🐛 *Troubleshooting and Next Steps* (01:14:36 - 01:35:14)

• Encountered issues with merging changes to main branch

• Planned to reconvene to clean up the project and ensure everything is working

• Discussed next steps for implementing similar solutions for the Shield side of the project

Gist • The meeting aimed to restructure the DBT project, focusing on data modeling, project organization, and transitioning to production.

Bullet Gist • 📁 Folder Restructuring: Renamed 'intermediate' folder to 'workspace' and set up distinct folders for data ingestion and analytics.

• 📊 Data Modeling Focus: Emphasized the use of sources, refs, and templated references to improve DAGs.

• 🧹 Project Cleanup: Disabled unused models and renamed existing ones for better clarity and organization.

• 🔄 Transitioning Looker: Discussed strategies for moving Looker from staging to production, resolving table and merge conflict issues.

• 🔧 Action Items Assigned: Chris Goodell and Ryan Vaspra were tasked with debugging and future project updates.

Short Summary • In a recent meeting led by Chris Goodell, the team discussed restructuring the DBT project by renaming the 'intermediate' folder to 'workspace' and establishing specific folders for raw data ingestion and analytics. Emphasis was placed on data modeling techniques, including the use of sources, refs, and templated references to enhance Directed Acyclic Graphs (DAGs). Furthermore, materialization strategies and schema configurations were addressed, with a focus on using macros and resolving schema naming issues. The team also undertook project cleanup initiatives, such as disabling unused models, clarifying model names, and organizing BigQuery datasets. Additionally, strategies for transitioning Looker from staging to production were explored, tackling challenges like missing tables and merge conflicts. Action items were assigned to Chris Goodell and Ryan Vaspra for debugging and future cleanups, with plans for similar solutions in the Shield aspect of the project.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-11 13:06:20

Title: BLX SEO Clients Date: Wed Sep 11 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The BLX SEO Clients meeting focused on the review and optimization of SEO performance, highlighting a notable 23% increase in September visits with a total of 74,408 sessions, predominantly from new visitors (82%). Despite traditionally being a slow season, the site has performed well, especially with a 9% visitor to lead conversion rate, the highest of the year. The discussion included analyzing top converting keywords for August and emphasized the need to enhance website content related to 'Slip and fall' lawsuits. Action items were assigned, including Kelly Richardson's responsibility to research this topic and update the navigation bar, while Ryan Vaspra will oversee the approval of the proposed navigation changes to better reflect the site's offerings.

Action Items • *Kelly Richardson*

• Analyze top converting keywords for August using Google Analytics and Search Console data (15:14)

• Research and create content for 'Slip and fall' practice area (23:23)

• Add 'Slip and fall' to navigation bar once content is created and improved (23:56)

• *Ryan Vaspra*

• Review and approve changes to navigation bar structure (19:46)

Shorthand Bullet • 📊 *Performance Review* (10:22 - 14:36)

• September visits are up

• Sessions at 74,408, better than last year (23% increase)

• 82% of visitors were new compared to last August

• Traditionally slow season, but performing well

• 📈 *Analytics and Insights* (14:50 - 17:55)

• Suggestion to look at top converting keywords for August

• Visitor to lead conversion rate at 9%, highest of the year

• 🔍 *Website Improvement* (18:18 - 24:03)

• Focus on 'Slip and fall' lawsuit content

• Need to add 'Slip and fall' to navigation bar

• Premise liability not in navigation

• Suggestion to make navigation three columns

Gist • The meeting focused on reviewing SEO performance and strategizing improvements to enhance website content and navigation.

Bullet Gist • 📊 Performance Review: September visits increased by 23%, reaching 74,408 sessions, with 82% being new visitors.

• 📈 Analytics Insights: The visitor to lead conversion rate hit 9%, the highest of the year, highlighting effective strategies.

• 🔍 Website Improvement Focus: The team aims to enhance content on 'Slip and fall' lawsuits and improve navigation.

Short Summary • The BLX SEO Clients meeting concentrated on the review and optimization of SEO performance, highlighting a significant 23% increase in September visits, totaling 74,408 sessions, with 82% of those being new visitors. Despite September being a traditionally slow season, the site exhibited strong performance, particularly with a 9% visitor to lead conversion rate, marking the highest conversion rate of the year. The discussion included an analysis of top converting keywords for August and emphasized the necessity to enhance the website's content regarding 'Slip and fall' lawsuits. Action items were assigned, with Kelly Richardson tasked with researching this topic and updating the navigation bar, while Ryan Vaspra will oversee the approval of the proposed navigation changes to ensure they accurately reflect the site's offerings.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-11 17:33:27

Title: Shield Legal - Monthly Financial Review & True Up Date: Wed Sep 11 2024 16:45:00 GMT-0400 (Eastern Daylight Time) Participants: debora@shield-legal.com, cameron@themedialab.agency, ryan@shield-legal.com, rose@accountingdept.net, nsay@hrdepartment.net, altonese@accountingdept.net, brian@accountingdept.net, malissa@shield-legal.com, ryan@brandlytics.io, alan@tortintakeprofessionals.com, henri@tortintakeprofessionals.com, tony@tortintakeprofessionals.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 45

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-12 13:13:31

Title: Case Type Names Cont. Date: Thu Sep 12 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, ryan@brandlytics.io, markmaniora@shield-legal.com, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, anthony@tortintakeprofessionals.com, david@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 60

Overview • The Operational/Technical Update Meeting focused on the ongoing updates of case type names in the Law Ruler system and the associated database. The team initiated discussions with the Chowchilla cases, ensuring that updates were made to specific cases such as Chowchilla Acts DL Flatirons, Levinson TC, and Chowchilla Acts Shield Legal. Attention was also directed toward Illinois cases, including Larry Jones and Merowitz, addressing necessary naming convention corrections. The handling of NC (New Criteria) cases was clarified, with separate contracts identified as necessary. Additional updates included Illinois Juvenile Hall and DL Flatirons cases, with plans for upcoming updates in California Juvenile Hall cases. Key action items were assigned, including case name updates in both Law Ruler and the database, with Anthony and Ryan tasked with specific updates and exports. Future meetings will continue to ensure the timely progression of project goals.

Action Items • *Anthony Tort*

• Update case names in Law Ruler for each discussed case (throughout meeting)

• Send CSV export of field names from intake template screen for Sokolov (01:03:07)

• *Ryan Brand*

• Update case names in the database for each discussed case (throughout meeting)

• Send field names to client for approval and set up contract to push leads (01:03:07)

• *Mark Maniora*

• Schedule next meeting for case name updates (01:01:16)

• *unassigned*

• Focus on California Juvenile Hall cases in the next meeting (59:48)

Shorthand Bullet • 🔄 *Case Type Name Changes* (00:01 - 15:19)

• Team working on updating case type names in Law Ruler and database

• Started with Chowchilla cases, focusing on ones with activity in September

• Updated Chowchilla Acts DL Flatirons, Levinson TC, and Chowchilla Acts Shield Legal

• Anthony updating in Law Ruler, Ryan updating in database

• Discussed format changes, including hyphen usage instead of slashes

• 📊 *Illinois* Case Updates** (15:35 - 37:08)

• Moved on to Illinois cases, starting with Forman

• Updated Larry Jones, Merowitz and Wasserberg, and Crump Slater cases

• Discussed naming conventions and format corrections

• Addressed issues with slashes vs. hyphens in names

• 🏷️ *NC (New Criteria) Cases* (37:14 - 47:01)

• Discussed handling of NC (New Criteria) cases

• Explained the need for separate contracts for NC and non-NC cases

• Determined NC cases started on July 10th

• Updated naming conventions for NC cases

• 📝 *Additional Case Updates* (47:03 - 59:37)

• Continued updates for Illinois Juvenile Hall cases

• Updated DL Flatirons cases, including NC versions

• Completed updates for Walsh cases

• Discussed plans for future California case updates

• 🗓️ *Next Steps and Additional Tasks* (59:48 - 01:04:38)

• Planned to focus on California Juvenile Hall cases next time

• Discussed Sokolov intake fields setup

• Anthony to send CSV export of field names from intake template

• Planned to set up contract to push leads and test raw lead sending

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-12 13:13:32

• The meeting focused on updating case type names in the Law Ruler system and database, including specific cases from Chowchilla and Illinois.

Bullet Gist • 🔄 Case Type Updates: The team is updating case type names in the Law Ruler system and database, starting with Chowchilla cases.

• 📊 Illinois Cases Review: Illinois cases were reviewed, correcting naming conventions and formats to enhance clarity.

• 🏷️ NC Cases Management: The team clarified the handling of NC cases, establishing the need for separate contracts.

• 📝 Ongoing Updates: Updates continued for Illinois Juvenile Hall and DL Flatirons cases, with future California updates planned.

• 🗓️ Next Steps: Future meetings will focus on California Juvenile Hall cases and other key action items.

Short Summary • The Operational/Technical Update Meeting centered on updating case type names within the Law Ruler system and its database. The team initiated discussions by addressing the Chowchilla cases, ensuring that updates were made to key cases such as Chowchilla Acts DL Flatirons, Levinson TC, and Chowchilla Acts Shield Legal, with Anthony and Ryan assigned specific updates. Attention then shifted to Illinois cases, including Larry Jones and Merowitz, where necessary naming convention corrections were made to improve clarity. The handling of NC (New Criteria) cases was also discussed, emphasizing the need for separate contracts for these cases, which began on July 10th. Further updates were made to Illinois Juvenile Hall and DL Flatirons cases, with plans for upcoming changes in California Juvenile Hall cases. Key action items were assigned, and future meetings were scheduled to ensure timely project progression.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-12 15:01:48

Title: BCL Next Steps Date: Thu Sep 12 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@shield-legal.com, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 30

Overview • The Strategic Planning and Progress Review meeting titled "BCL Next Steps" focused on enhancing data analysis, marketing strategies, and future improvements. Ryan led a discussion on matching social leads from Smart Advocate with BigQuery tables, utilizing SQL for improved data accuracy and suggesting updates on closed case dollar amounts. Latoya outlined ongoing enhancements to the Ben.com website and the upcoming review of split testing software, while Ryan shared updates on the Vin Crump dashboard. Future strategies included exploring dedicated lead management software and automation for lead routing, alongside a proposal for a December planning meeting to discuss initiatives for 2025. Positive trends were noted in SEO, website traffic, and lead conversion rates, and several action items were assigned to team members for follow-up.

Action Items • *Uzoma*

• Confirm with Desiree about the status of closed cases (02:39)

• Ask John or Desiree about dollar amounts for closed cases (06:50)

• Talk to John about potentially joining Ryan in Vegas (11:58)

• *Ryan*

• Push the next meeting earlier in the week due to travel (09:30)

• Build an attribution page in the dashboard (14:28)

• *Ryan and Latoya*

• Review split testing software during Vegas visit (09:30)

• *Ryan and Uzoma*

• Plan a December meeting for 2025 planning (24:09)

Shorthand Bullet • 🔍 *Data Analysis and Matching* (00:33 - 07:21)

• Ryan conducted an exercise matching social leads from Smart Advocate with BigQuery tables

• SQL query used to clean and format phone numbers and names for better matching

• Phone number match returned one result, name match returned more

• Closed cases in the data likely represent actual cases, but Uzoma to confirm with Desiree

• Suggestion to update Smart Advocate with dollar amounts for closed cases

• 📊 *Marketing and Website Updates* (07:25 - 15:12)

• Latoya working on Ben.com mobile and desktop site navigation improvements

• Plan to review split testing software during Ryan's visit on the 23rd

• Multivariate testing planned for website optimization

• Updated Vin Crump dashboard now shows S1 data for call leads

• Ryan working on SQL template for easier data integration and attribution tracking

• 💡 *Future Improvements and Strategies* (16:54 - 30:04)

• Discussion on potential improvements to lead management in Smart Advocate

• Consideration of dedicated lead management software like Cake

• Idea for automated lead routing system based on case type and firm preferences

• Proposal for December planning meeting to discuss 2025 initiatives

• SEO improvements noted, including significant keyword ranking increases

• Positive year-over-year website traffic and lead conversion rate improvements

Gist • The meeting aimed to enhance data analysis, marketing strategies, and plan future improvements for BCL.

Bullet Gist • 🔍 Data Analysis and Matching: Ryan matched social leads from Smart Advocate with BigQuery, improving data accuracy with SQL.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-12 15:01:48

• 📊 Marketing and Website Updates: Latoya is enhancing Ben.com’s site navigation and reviewing split testing software for optimization.

• 💡 Future Improvements and Strategies: Discussions included dedicated lead management software and a proposal for a December planning meeting.

Short Summary • The Strategic Planning and Progress Review meeting titled 'BCL Next Steps' focused on enhancing data analysis and marketing strategies. Ryan led a discussion on matching social leads from Smart Advocate with BigQuery tables, utilizing SQL to improve data accuracy, and recommended updating closed case dollar amounts. Latoya provided updates on ongoing enhancements to the Ben.com website, including navigation improvements and a review of split testing software. Ryan also shared updates on the Vin Crump dashboard, which now includes S1 data for call leads. Future strategies discussed included exploring dedicated lead management software and automation for lead routing based on case types. The team proposed a December planning meeting to outline initiatives for 2025, and noted positive trends in SEO, website traffic, and lead conversion rates, assigning action items for follow-up.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-12 16:25:40

Title: Shield Legal - Monthly Financial Review & True Up Date: Thu Sep 12 2024 16:30:00 GMT-0400 (Eastern Daylight Time) Participants: debora@shield-legal.com, cameron@themedialab.agency, ryan@themedialab.agency, rose@accountingdept.net, nsay@hrdepartment.net, altonese@accountingdept.net, brian@accountingdept.net, malissa@shield-legal.com, ryan@brandlytics.io, alan@tortintakeprofessionals.com, henri@tortintakeprofessionals.com, tony@tortintakeprofessionals.com, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 45

Overview • The "Shield Legal Monthly Financial Review & True Up" meeting focused on enhancing financial processes and improving billing practices. Key discussions included the need for weekly reconciliations of billable actions and the standardization of case types and pricing, with Ryan requesting a comprehensive list from Alan. The team emphasized the importance of accurate status tracking in Law Ruler for billing and explored automating the billing process through a data warehouse. Financial reporting highlights included the profitability of Victim Support Services (VSS) and the establishment of target numbers for juvenile detention cases. To streamline efforts, an automated dashboard for VSS payroll and data was proposed, alongside action items for team members, such as updating historical data and improving invoice payment tracking. Overall, the meeting aimed to refine financial management and ensure accurate reporting and billing practices within the organization.

Action Items • *Alan Gill*

• Send comprehensive list of case types and prices to Ryan (16:09)

• Provide VSS team payroll and billing summary to Ryan (42:05)

• Talk to Abe about backlog approvals (46:51)

• *Ryan Vaspra*

• Set up meeting with Tony, Alan, Anthony, and David to update TIP portal (41:12)

• Update historical data for post-retainer cases back to 2024 (41:33)

• Create dashboard for VSS team payroll and interview data (36:15)

• *Melissa*

• Review weekly reconciliation reports from Brittany (34:49)

• *Brittany*

• Send weekly reconciliation reports to Abe and copy Melissa (34:49)

• *Anthony*

• Update new intake templates with pricing information in TIP portal (40:13)

Shorthand Bullet • 🔄 *Process Review and Automation* (01:17 - 16:45)

• Discussion on TIP invoices and billing processes

• Need for weekly reconciliation of all billable actions

• Ryan requests a comprehensive list of case types and prices from Alan

• Importance of accurate status tracking in Law Ruler for billing purposes

• 💰 *Pricing and Billing Discussion* (16:48 - 21:47)

• Discussion on VGA (Video Game Addiction) billable statuses

• Ryan explains the need for standardized statuses in Law Ruler

• Conversation about automating the billing process through a data warehouse

• Discussion on pricing for different case types and tiers

• 📊 *Financial Reporting and Targets* (23:03 - 32:55)

• Discussion on VSS (Victim Support Services) billing and profitability

• Target numbers for juvenile detention facility and Chowchilla cases

• Explanation of payroll vs. billing balance for VSS department

• Need for automated dashboard for VSS team payroll and interview data

• 🔍 *Reconciliation and *Data Management** (32:55 - 40:14)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-12 16:25:40

• Weekly reconciliation process for BSS (Business Support Services) discussed

• Need for standardized pricing scale and margin calculation

• Discussion on displaying all costs in the dashboard for accurate financial reporting

• 🛠️ *Action Plan and System Updates* (40:18 - 46:54)

• Ryan to set up meeting with Tony, Alan, Anthony, and David to update TIP portal

• Plan to update historical data for post-retainer cases

• Discussion on improving invoice payment tracking system

• Alan to provide VSS team payroll and billing summary to Ryan for dashboard creation

Gist • The meeting aimed to enhance financial processes and improve billing practices within the organization.

Bullet Gist • 🔄 Process Review and Automation: Discussed weekly reconciliations and the need for standardized case types and pricing.

• 💰 Pricing and Billing Discussion: Explored automating the billing process and establishing standardized statuses in Law Ruler.

• 📊 Financial Reporting and Targets: Analyzed VSS profitability and set target numbers for juvenile detention cases.

• 🔍 Reconciliation and Data Management: Reviewed weekly reconciliation processes and emphasized standardized pricing for accurate reporting.

• 🛠️ Action Plan and System Updates: Outlined action items for team members to enhance financial tracking and reporting.

Short Summary • The "Shield Legal Monthly Financial Review & True Up" meeting focused on improving financial processes, particularly in billing practices. Key discussions highlighted the need for weekly reconciliations of billable actions, with Ryan requesting a comprehensive list of case types and pricing from Alan. Participants emphasized the importance of accurate status tracking in Law Ruler for billing and explored the automation of the billing process via a data warehouse. Financial reporting showcased the profitability of Victim Support Services (VSS) and established target numbers for juvenile detention cases. An automated dashboard for VSS payroll and data was proposed, with action items including updating historical data and enhancing invoice payment tracking to refine overall financial management and reporting accuracy.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-13 11:42:42

Title: AI Dashboard enhancements Date: Fri Sep 13 2024 11:45:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, jamesscott@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 55

Overview • The AI Dashboard Enhancements meeting focused on several updates and refinements to the dashboard used for data analysis and visualization of drug-related cases. Key discussions included James implementing changes to improve the dashboard layout and introduce new 2024 prediction models, while Ryan emphasized the necessity of filling in blank data and filtering options. The team addressed discrepancies between historical and predicted impact rankings and created new metrics for better tracking. They also explored the incorporation of external data sources, such as the Case Search website and Westlaw, to enrich the dataset, and agreed on renaming 'member cases' to 'FDA incidents' to enhance clarity. Action items were assigned, including further development of the dashboard and refinement of metrics, with a focus on utilizing Natural Language Processing (NLP) for improved drug product categorization.

Action Items • *James Scott*

• Rename 'member cases to date' to 'FDA incidences to date' on both pages one and two (54:34)

• Use NLP to synthesize a column called 'drug product name' for better categorization (53:02)

• Continue pressing Unicorn and Westlaw for information on MDL cases and dates (54:07)

• Change the field name from 'member cases' to 'FDA incidents' (50:11)

• *Ryan Vaspra*

• Continue playing with filters and dashboard layout (51:36)

• Prepare questions for Cameron about risk tolerance and engagement preferences (51:36)

• Hold off on building the final summary page until new data points are factored in (55:27)

Shorthand Bullet • 🖥️ *Dashboard Updates and Data Cleaning* (01:22 - 16:46)

• James made changes to the dashboard, including new models for 2024 predictions

• Ryan and James discussed filling blank data with zeros

• They renamed pages and cleaned up the dashboard layout

• Discussed the need for MDL case numbers and their importance

• 📊 *Data Analysis and Visualization* (16:46 - 24:17)

• Explored the impact ranking metric and its interpretation

• Discovered discrepancies between historical and predicted rankings

• James updated the prediction ranking for 2024

• Discussed the need for filtering out blank data

• 📈 *Exploring Data* Changes and Filters** (24:24 - 36:46)

• Created a new metric to show the change in impact ranking

• Discussed the importance of identifying drugs without MDLs

• Explored filtering options based on months as MDL

• Considered removing certain columns that might not be relevant for the meeting

• 🔍 *Data Sources and Improvements* (36:46 - 48:01)

• James contacted Case Search website for MDL information

• Discussed the potential use of Westlaw for legal research

• Ryan suggested statistical analysis of the impact ranking

• Explored the meaning of 'member cases' in the current dataset

• 🛠️ *Refinements and Future Plans* (48:01 - 55:32)

• Renamed 'member cases' to 'FDA incidents'

• Discussed creating user profiles for law firms based on risk tolerance

• Suggested using NLP to categorize drug products

• Confirmed that minor and serious injury settlements use FDA incidents for estimates

Gist • The meeting focused on enhancing the AI Dashboard for drug case analysis, introducing new prediction models, and improving data clarity.

Bullet Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-13 11:42:43

• 🖥️ Dashboard Updates: James implemented changes to the layout and introduced new 2024 prediction models.

• 📊 Data Analysis: The team addressed discrepancies in impact rankings and the need for filtering blank data.

• 📈 New Metrics Created: A new metric was established to track changes in impact rankings effectively.

• 🔍 External Data Sources: Considered integrating data from Case Search and Westlaw to enhance the dataset.

• 🛠️ Future Developments: Plans were made for utilizing NLP in drug product categorization.

Short Summary • The AI Dashboard Enhancements meeting concentrated on updating the dashboard for data analysis and visualization of drug-related cases. James outlined changes to improve layout and introduced new prediction models for 2024. Ryan highlighted the need to fill in blank data and refine filtering options. The team identified discrepancies between historical and predicted impact rankings and established new metrics for better tracking. They discussed incorporating external data sources like the Case Search website and Westlaw and agreed to rename 'member cases' to 'FDA incidents' for clarity. Action items were assigned for further dashboard development and refining metrics with a focus on applying Natural Language Processing (NLP) for improved drug product categorization.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-16 14:12:23

Title: Tech Project Status Weekly Date: Mon Sep 16 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com, dschussler@shield-legal.com, ryan@shield-legal.com, dsurwill@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 10

Overview • The Tech Project Status Weekly meeting, attended by Ryan, Nick, Dustin, and Brian, was rescheduled to the following day due to McFadden's uncertain attendance and incomplete participation. Key topics, particularly related to APIs, will be addressed in the rescheduled meeting. Action items include Ryan Vaspra's responsibility to organize the new meeting time and Nicholas Ward's task to reach out to McFadden to confirm his availability.

Action Items • *Ryan Vaspra*

• Reschedule the meeting for tomorrow (04:02)

• *Nicholas Ward*

• Text McFadden to check his availability for the rescheduled meeting (03:39)

Shorthand Bullet • 🗓️ *Meeting Rescheduling* (00:16 - 04:03)

• Ryan, Nick, Dustin, and Brian are present

• McFadden's attendance is uncertain

• Meeting rescheduled for tomorrow due to incomplete attendance

• API-related topics to be discussed in the rescheduled meeting

Gist • The meeting aimed to address the status of ongoing tech projects, focusing on APIs, and was rescheduled due to attendance issues.

Bullet Gist • 🗓️ Meeting Rescheduling: The meeting was rescheduled for tomorrow due to McFadden's uncertain attendance.

• 🔑 Key Topics: API-related discussions are a priority for the upcoming meeting.

• 👥 Action Items: Ryan will organize the new meeting time, while Nick will confirm McFadden's availability.

• 🤝 Attendance Issues: Incomplete participation led to the decision to postpone the meeting.

• 📈 Project Importance: APIs are crucial for the ongoing tech projects, emphasizing their significance.

Short Summary • The Tech Project Status Weekly meeting, attended by Ryan, Nick, Dustin, and Brian, was postponed to the next day due to McFadden's uncertain attendance and incomplete participation. Key topics, particularly related to APIs, are set to be discussed in the rescheduled meeting. Action items were identified, with Ryan Vaspra tasked with organizing the new meeting time and Nicholas Ward responsible for reaching out to McFadden to confirm his availability. The focus on APIs suggests a significant interest in the integration and functionality of application programming interfaces within the ongoing tech projects, highlighting their importance to the overall project status and progress.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-16 15:46:55

Title: AI Internship Date: Mon Sep 16 2024 16:30:00 GMT-0400 (Eastern Daylight Time) Participants: jamesscott@shield-legal.com, ryan@brandlytics.io, barmazelmarc@gmail.com, cameron@shield-legal.com, marc@sunrisessm.com Transcript: See full transcript Audio: Listen to audio Duration: 19

Overview • In the AI Internship Discussion meeting, participants explored the proposal for an AI internship for Marc's 16-year-old son, with James suggesting a drug classification project leveraging AI and machine learning. Ryan provided insights into the project's reliance on natural language processing and industry research, while Cameron expressed interest but highlighted his time constraints due to his son's wrestling schedule. The meeting transitioned to project planning, where the team agreed on holding regular Friday meetings for progress updates. James was tasked with setting up the work environment and assessing the intern's capabilities, and Ryan discussed alternative, less coding-intensive project options. Key action items included preparing for a demo of the Tortilla Gents project on September 25th and deep diving into the beta version before month's end, with all participants expected to outline potential tasks for the intern in preparation for the upcoming meeting.

Action Items • *James Scott*

• Set up work environment and assess intern's starting point (12:32)

• *Ryan Vaspra*

• Send out 11:30 AM Pacific time invite for Friday meeting (13:53)

• Prepare demo of Tortilla Gents project for September 25th meeting (15:07)

• *Cameron Rentch*

• Determine son's availability for internship considering wrestling commitments (11:00)

• *All participants*

• Prepare outline of potential intern tasks for Friday meeting (13:27)

• *James Scott and Ryan Vaspra*

• Continue working on MDL docket number tracking with Unicorp (08:54)

Shorthand Bullet • 🎓 *AI Internship Discussion* (03:28 - 11:25)

• Marc proposes an AI internship for his 16-year-old son

• James suggests a drug classification project using AI/ML

• Ryan explains the project involves NLP and industry research

• Cameron expresses interest but mentions time constraints due to his son's wrestling commitments

• 🖥️ *Project Details and Planning* (11:25 - 19:07)

• Discussed potential Friday meetings for project updates

• James to set up the work environment and assess the intern's starting point

• Ryan mentions alternative projects like data engineering for less coding-intensive work

• Planned demo of Tortilla Gents project for September 25th in Vegas

• Discussed development of a risk-based dashboard for law firms

• Cameron requests a deep dive into the beta version before month-end

Gist • The meeting focused on proposing an AI internship for Marc's son, discussing project ideas and planning regular updates.

Bullet Gist • 🎓 AI Internship Proposal: Marc proposed an AI internship for his 16-year-old son, targeting a project in drug classification.

• 🖥️ Project Planning: The team agreed to regular Friday meetings for project updates and task outlines.

• 💻 James's Role: James will set up the work environment and assess the intern's starting point.

• 🔍 Ryan's Insights: Ryan suggested alternative, less coding-intensive projects like data engineering.

• 📅 Upcoming Demo: A demo of the Tortilla Gents project is scheduled for September 25th.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-16 15:46:55

• During the AI Internship Discussion meeting, participants reviewed a proposal for an internship for Marc's 16-year-old son, emphasizing a drug classification project utilizing AI and machine learning, as suggested by James. Ryan contributed by explaining the project's dependence on natural language processing and industry research. Cameron expressed interest in the project but noted his limited availability due to his son's wrestling commitments. The discussion shifted towards project planning, with the team agreeing to hold regular Friday meetings for updates. James was assigned to establish the work environment and evaluate the intern's capabilities, while Ryan proposed alternative projects that required less coding. Key action items included preparing for a demo of the Tortilla Gents project on September 25th and conducting a deep dive into the beta version by the end of the month, with all participants expected to outline potential tasks for the intern ahead of the next meeting.

Ryan (ryan@themedialab.agency)
2024-09-16 17:59:03

Shield Legal Financials Daily Numbers Workflow Steps

  1. Manual leads sold by @Mark Maniora
  2. Validate TIP DB Log, S1s and TIP Slack counts & then process Declines @Luke Fontaine & @Ryan
  3. Confirm media and agency spend submissions @Luke Fontaine and @Ryan
  4. Run numbers function
  5. Prepare TIP Revenue and Counts via Inserts and GroupBy SQL on donottouch table - Manually by @Luke Fontaine and @Ryan
  6. Note ready for adjustments with table snapshot validation - Done by CR
  7. Apply adjustments and master append to dash
  8. Post fails to Cameron

Debugging SL Lambda functions

  1. Tell Cameron ready for adjustments via Adjustments 4.0 linked here a. "Requested adjustments" goes into the adjustments_v2table. So each adjustment Cam makes will create 1 row in that table and can be used to update DONOTTOUCH in case of failure b. The ApplyAdjustments lambda combines donottouch and adjustments_v2 , and outputs to adjustedview_v2 , which can be used for manual mediarawv2 preparation if failure. MUST ONLY RUN ONCE!!! c. Review Logs for Fails, report to Cam in <#GSRMUB3PT|>
  2. Append Records: Submits into MediaRawv2 a. The MasterAppend lambda appends the rows of adjustedview_v2 to media_raw_v2 b. If CalcluatePerformance & Apply Adjustments work, but Append fails, the use adjustedviewv2 as to create mediarawv2 records and to make final Leadspedia Budget Credits. (@shield-legal-data to write a SQL to insert adjustedview_v2 into media_raw_v2
  3. Check Dashboard for Daily Summary and ping Cam
Ryan (ryan@themedialab.agency)
2024-09-16 17:59:39

Sign Up Slack Alerts Setup

  1. New Vertical must be Active in Leadspedia for the Contract and not contain any punctuations or special characters.
  2. New Contract must have proper Contract Name naming convention of a. CASE TYPE - LIT FIRM / PTR FIRM (TIP) - SALE TYPE
  3. New Contract must have Leadspedia.Contract.Settings.AlternateID setup for ISA or TIP configuration
  4. New entries into 15 sections of TypeForm for Case Type
  5. Shield Database must have Case Type name and default Cost Per Intake for Call Center Costs IS $25.00
  6. New Slack Channel must be setup with same name as Case Type and microservices should be setup: a. @IntradaySoldLeads_Microservice for Sold Leads and Signed Contracts and Slack Slash in CSV b. @TIP Signed Contracts Alert must be setup in DB
Ryan Vaspra (https://themedialaboratory.slack.com/team/UJF2W0EB1)
<p>@Cameron Rentch @Brian Hirst @Tony No matter who setups up new contracts for Contract Buyers, we need to ensure the following:</p> <ol><li>If going to TIP, we need the <em>(TIP)</em> portion in the second section of the contract name in Leadspedia, such as: <em>NEC Baby Formula - Principal (TIP) - Contract.</em> a. This ensures the Shield Financials have the TIP in the Customer Name for each morning run.</li><li>No matter TIP or ISA, we have to know when a new contract is setup so that Brian can pull the ISA.AccountID and ISA.CaseTypeID to put into the Leadspedia.Contract.Settings.AlternativeID or we can create one for TIP.<br /> a. <strong>Without them the Signed Contract Alerts will not work for ISA at all and TIP will not show the account code in Slack.</strong> FYI @shield-legal-data</li> </ol>
Original URL: https://themedialaboratory.slack.com/archives/C018VHBKSA0/p1640105982035400
Slack Conversation
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-18 11:16:04

Title: JA - mid month commission review Date: Wed Sep 18 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: jack@themedialab.agency, cameron@themedialab.agency, ryan@themedialab.agency, ryan@brandlytics.io, debora@shield-legal.com, altonese@accountingdept.net, brian@accountingdept.net, ryan@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 13

Overview • In the mid-month commission review meeting, Ryan addressed the challenges posed by Slack API rate limits on media buyer tools, proposing a new system featuring a real-time dashboard for sold leads and sign-ups to streamline operations and minimize maintenance issues. Jack concurred on the merits of the new system and Ryan outlined plans for a dedicated admin log channel to improve tracking. The meeting also included a review of Jack's dashboard, where Ryan corrected null value issues and updated vertical names. Future developments were discussed, including the creation of a mobile and desktop web app and a Shield Legal Media Buyer Portal. The meeting concluded with a commission review for Jack, highlighting his performance and resulting in a substantial commission calculation. Action items were assigned for system improvements and collaboration on fixing the Slack slash command solution.

Action Items • *Ryan Vaspra*

• Build a table to put data in and use a different API to Slack (04:45)

• Develop the new system with real-time dashboard for sold leads and sign-ups (01:21)

• Create the Shield Legal Media Buyer Portal (09:10)

• *Quint Underwood*

• Collaborate with Ryan on fixing the Slack slash command solution (05:18)

Shorthand Bullet • 🔧 *Slack API Rate Limit Issues* (00:21 - 02:56)

• Ryan discusses problems with Slack API rate limits affecting media buyer tools

• Proposes a new system with real-time dashboard for sold leads and sign-ups

• Aims to eliminate multiple breakpoints and reduce maintenance

• 📊 *Dashboard Improvements* (02:56 - 05:31)

• Jack agrees that a new system would be beneficial

• Ryan introduces an admin Shield isla MB log channel for tracking calls

• Discusses plans to build a table for data and use a different API to Slack

• 🔍 *Dashboard Review and Fixes* (05:31 - 08:28)

• Review of Jack's dashboard reveals null values for Bard Power Ports and LA County Foster Care

• Ryan identifies and fixes spelling issues causing the null values

• Updates vertical names and sets default values

• 🚀 *Future Development* Plans** (08:49 - 10:07)

• Ryan mentions upcoming new system with mobile and desktop web app capabilities

• Plans for a Shield Legal Media Buyer Portal with integrated dashboards and forms

• 💼 *Commission Review* (10:07 - 12:44)

• Review of Jack's performance: $8,633 commission, eclipsing 3.2

• Ryan calculates and sends email about Jack's commission: $8,633 base plus $15,000 rev bonus

Gist • The meeting aimed to address Slack API rate limit challenges and discuss system improvements for media buyer tools.

Bullet Gist • 🔧 Slack API Rate Limit Issues: Ryan discussed Slack API rate limits affecting media buyer tools and proposed a real-time dashboard.

• 📊 Dashboard Improvements: Jack agreed on the new system's benefits; Ryan introduced an admin log channel for better tracking.

• 🔍 Dashboard Review and Fixes: Ryan identified and fixed null values in Jack's dashboard, updating vertical names.

• 🚀 Future Development Plans: Plans for a mobile app, desktop web app, and a new Shield Legal Media Buyer Portal were discussed.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-18 11:16:04

• 💼 Commission Review: Jack's performance review resulted in a commission of $8,633 plus a $15,000 revenue bonus.

Short Summary • Ryan addressed challenges with Slack API rate limits impacting media buyer tools during the mid-month commission review meeting. He proposed a new system featuring a real-time dashboard for sold leads and sign-ups, aiming to streamline operations and reduce maintenance issues. Jack agreed on the benefits of this system, and Ryan outlined plans for a dedicated admin log channel to enhance tracking. During the meeting, they reviewed Jack's dashboard, where Ryan corrected null value issues and updated vertical names. Future developments discussed included creating mobile and desktop web apps and a Shield Legal Media Buyer Portal. The meeting concluded with a commission review for Jack, highlighting his performance with a significant commission calculation, including a base of $8,633 and an additional $15,000 revenue bonus.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-18 11:40:49

Title: ML - mid month commission review Date: Wed Sep 18 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: maximus@themedialab.agency, cameron@themedialab.agency, ryan@themedialab.agency, ryan@brandlytics.io, brian@accountingdept.net, briant@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 10

Overview • In the mid-month commission review meeting, key topics included a monthly performance update where Ryan reported positive figures totaling 68.9159, and he addressed issues with Slack commands that have been stalling, attributing problems to the LeadsPDA and Slack APIs. To enhance operational efficiency, the team proposed developing a Shield Legal portal that would facilitate real-time updates and improve dashboard functionality by refreshing every minute, eliminating the need for outdated spreadsheets and redundant Slack commands. Further discussions on API integration indicated reliance on LeadsPDA and Google Cloud, and the introduction of a dedicated Slack channel for logging command runs to monitor API rate limits. Action items for Ryan included emailing updated commission figures, setting up the new portal, adding team members to the Slack channel, and communicating proposed changes with Cameron.

Action Items • *Ryan*

• Ryan to send email with updated commission figures (02:27)

• Ryan to set up new Shield Legal portal/app with real-time dashboard (04:26)

• Ryan to add Maximus, Caleb, and Jack to the new Slack logging channel (07:35)

• Ryan to discuss proposed changes with Cameron (06:00)

Shorthand Bullet • 📊 *Monthly Performance Review* (00:12 - 02:27)

• Ryan removed null costs and closing costs

• Good month: 58 plus 2.3, another ten

• Total: 68.9159 sent to Cameron, Maximus, and Brian

• 🔧 *Slack Command Issues* (02:30 - 04:26)

• Slack slash command sometimes stalls out

• Issues due to LeadsPDA API or Slack API struggling

• Proposed future solution: Shield Legal portal/app

• Portal to include tabs for submissions, dashboard, leads, and signups

• Real-time data updates

• 💻 *Dashboard Improvement Discussion* (04:26 - 05:57)

• Maximus suggests addressing the gap in daily reporting times

• Ryan explains new solution would provide real-time updates

• Dashboard to refresh every minute

• Eliminate need for four-day spreadsheet and Slack commands

• 🔄 *API and Integration Considerations* (05:57 - 07:35)

• New system would only rely on LeadsPDA and Google Cloud

• Ryan plans to discuss changes with Cameron

• Possibility of keeping Slack alerts for Cameron only

• 📈 *Slack Channel for Command Logging* (07:35 - 08:28)

• Ryan introduces a new Slack channel for logging command runs

• Channel shows timestamps of Slack slash commands

• Helps identify potential API rate limit issues

• Max, Caleb, and Jack to be added to this channel

Gist • The meeting reviewed monthly performance metrics and addressed operational challenges, proposing solutions for improved efficiency.

Bullet Gist • 📊 Monthly Performance Review: Ryan reported a positive figure of 68.9159 for the month.

• 🔧 Slack Command Issues: Problems with Slack commands were linked to LeadsPDA and Slack APIs.

• 💻 Dashboard Improvement Discussion: A new solution aims to provide real-time data updates and refresh dashboards every minute.

• 🔄 API and Integration Considerations: The new system will rely solely on LeadsPDA and Google Cloud.

• 📈 Slack Channel for Command Logging: A new Slack channel will monitor command runs and API rate limits.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-18 11:40:49

Short Summary • In the mid-month commission review meeting, Ryan reported a positive monthly performance totaling 68.9159 and addressed ongoing issues with Slack commands, which were attributed to problems with the LeadsPDA and Slack APIs. To enhance operational efficiency, the team proposed developing a Shield Legal portal, which would allow for real-time updates and improve dashboard functionality by refreshing every minute, thereby eliminating outdated spreadsheets and redundant Slack commands. Discussions included the reliance on LeadsPDA and Google Cloud for API integration, and Ryan introduced a dedicated Slack channel for logging command runs to monitor API rate limits. Action items for Ryan included emailing updated commission figures, setting up the new portal, and communicating proposed changes with Cameron.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-18 14:37:28

Title: Shield Legal: SL dbt follow up Date: Wed Sep 18 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: chris.goodell@bytecode.io, ryan@brandlytics.io, brian@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 19

Overview • The Technical Follow-up and Planning Meeting focused on the progression of the Shield Legal project's DBT (Data Build Tool) setup, led by Chris Goodell. Key discussions included the organization of project structures with dedicated folders for AWS legacy, Copper, and Leadspedia, and the migration of financial data to an analytics folder to establish a "gold standard." Chris presented the recreated views and outlined future plans for transitioning from old Postgres data to a new GCP pipeline, including the development of a static 'golden ticket' table for historical data and strategies for integrating old and new data models. Action items assigned included Chris completing Copper-related work and Ryan preparing for deployment by reviewing progress and updating the Looker enterprise model file. The meeting underscored the need to address potential challenges in naming conventions within BigQuery and emphasized the identification of key models for analytics delivery.

Action Items • *Chris Goodell*

• Complete work on Copper-related models (14:59)

• Target Leadspedia and Copper for next steps (17:12)

• Wrap up identified analytics models (18:29)

• Inform Ryan of progress by end of day (14:59)

• *Ryan Vaspra*

• Review completed work and schedule deployment meeting (14:52)

• Update Looker enterprise model file and database connection after deployment (08:02)

Shorthand Bullet • 🔧 *DBT Setup and Progress* (01:35 - 04:11)

• Chris set up a branch in DBT for Shield Legal

• Recreated views as tables for better usability

• Chris shared his screen to walk through the work done

• 🏗️ *Project Structure and *Folder Organization** (04:11 - 06:38)

• Created models for relevant legacy views

• Established lineage for different pieces

• Set up folders for AWS legacy, Copper, and Leadspedia

• Organized into stage, workspace, and analytics folders

• 📊 *Analytics and *Gold Standard Data** (06:38 - 10:22)

• Financial details to be moved to analytics folder (gold standard)

• Copper breakout: orders list, financials, and PBS to be analytics models

• AWS legacy stuff to be placed in AWS legacy views schema in BigQuery

• Discussed potential for breaking out large models into separate models for maintainability

• 🔄 *Data Migration and Future Plans* (10:22 - 13:28)

• Discussed need for snapshot of financial details due to manual changes

• Planned for future transition from old Postgres data to new GCP pipeline

• Considered creation of static 'golden ticket' table for historical data

• Discussed joining historical and new data in future models

• 🚀 *Deployment and Next Steps* (14:00 - 18:48)

• Chris to complete Copper-related work

• Planned meeting to deploy and ensure schema matching

• Discussed potential challenges with table and view naming in BigQuery

• Identified need to update Looker enterprise model file and database connection

• Targeted Leadspedia and Copper for next steps

• Identified key models for analytics level: orders list, bi shield orders paid spent, bi shield order financials, bi copper orders list

Gist • The meeting focused on the progression of the Shield Legal project's DBT setup, addressing data migration and organizational strategies.

Bullet Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-18 14:37:28

• 🔧 DBT Setup and Progress: Chris set up a branch in DBT for Shield Legal, enhancing usability with recreated views.

• 🏗️ Project Structure and Folder Organization: Dedicated folders for AWS legacy, Copper, and Leadspedia were established for better organization.

• 📊 Analytics and Gold Standard Data: Financial details are to be moved to an analytics folder, establishing a gold standard for data.

• 🔄 Data Migration and Future Plans: Plans for transitioning from old Postgres data to a new GCP pipeline were discussed.

• 🚀 Deployment and Next Steps: Action items were assigned, including deployment preparation and updating the Looker model file.

Short Summary • The Technical Follow-up and Planning Meeting centered on advancing the Shield Legal project's Data Build Tool (DBT) setup, led by Chris Goodell. Key topics included the organization of project structures with dedicated folders for AWS legacy, Copper, and Leadspedia, as well as the migration of financial data to an analytics folder to create a 'gold standard'. Chris presented recreated views and discussed future plans for transitioning from old Postgres data to a new GCP pipeline. This transition includes developing a static 'golden ticket' table for historical data and strategies for integrating old and new data models. Action items included Chris completing the Copper-related work and Ryan preparing for deployment by reviewing progress and updating the Looker enterprise model file. The conversation highlighted potential challenges in naming conventions within BigQuery and emphasized the identification of key models for analytics delivery.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-19 12:32:09

Title: AI Dashboard enhancements Date: Thu Sep 19 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, jamesscott@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 28

Overview • The Project Status and Planning Meeting for AI Dashboard enhancements reviewed the current state of the dashboard, which was met with positive feedback for its clean design and client-friendly format, though there was confusion regarding the zero predicted impact ranking for 2023. Discussions highlighted the need to address the integration of Snowflake at a projected cost of $120,000 for the first year, as well as the potential to enrich Unicorn's dataset using Pacer data and resolving discrepancies in drug naming conventions associated with MDLs. Action items were assigned, with Ryan tasked to export drug names and enhance visual elements of the dashboard, while James will develop a matching algorithm for drug variations and compile necessary components to improve search accuracy. Overall, the meeting focused on refining data integration and enhancing the dashboard's presentation to better serve client needs.

Action Items • *Ryan*

• Export and send list of drug names to Unicorn for MDL status and member case counts (21:08)

• Add charts to the dashboard for the two-hour session with Cameron (23:51)

• Work on moving charts to improve visual presentation (23:55)

• *James*

• Develop matching algorithm for drug names and their variations in MDL data (25:07)

• Research and compile a list of components for each drug to improve search accuracy (25:34)

Shorthand Bullet • 🖥️ *Dashboard Review and Enhancements* (00:26 - 12:58)

• Dashboard looks clean and pretty, in the format the client likes

• Logo created by Jack GDB looks good

• Confusion about 2023 predicted impact ranking being zero

• Filters applied: exclude null prediction rankings, show only worsening impact

• MDL (Multidistrict Litigation) data discussion

• 📊 *Data Integration and API Discussion* (12:58 - 19:10)

• Snowflake integration costs: $120,000 first year, increasing in subsequent years

• Unicorn's potential use of Pacer data to enhance their dataset

• Lead case in MDL contains associated member cases

• Difficulty in matching drug names to MDLs due to variations in naming

• 🔍 *Data Enrichment and Presentation Strategy* (21:04 - 28:19)

• Plan to ask Unicorn for MDL status and member case counts for specific drugs

• Need to integrate Pacer data, MDL member cases, and MDL status into Unicorn's dataset

• James to develop matching algorithm for drug names and their variations

• FDA data includes active substance names, which can be used for matching

• Ryan to work on visual enhancements for the dashboard presentation

Gist • The meeting aimed to review and enhance the AI Dashboard, focusing on data integration and presentation improvements.

Bullet Gist • 🖥️ Dashboard Design Feedback: The dashboard received positive reviews for its clean and client-friendly design.

• 💰 Snowflake Integration Costs: The integration of Snowflake will initially cost $120,000, with expected increases in future years.

• 📊 Data Enrichment Opportunities: There is potential to enhance Unicorn's dataset by integrating Pacer data and resolving drug naming discrepancies.

• 🔍 Action Items Assigned: Ryan is tasked with visual enhancements, and James will develop a drug name matching algorithm.

• 📈 Focus on Client Needs: The meeting concentrated on improving data integration and the dashboard presentation for better client service.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-19 12:32:09

Short Summary • The Project Status and Planning Meeting addressed enhancements to the AI Dashboard, receiving positive feedback for its design and client-friendly format. However, confusion arose regarding the zero predicted impact ranking for 2023. Key discussions included the integration of Snowflake, which is projected to cost $120,000 in the first year, and the potential enrichment of Unicorn's dataset using Pacer data, alongside resolving discrepancies in drug naming conventions related to MDLs. Action items were assigned, with Ryan responsible for exporting drug names and enhancing the dashboard's visual elements, while James will develop a matching algorithm for drug variations and compile necessary components to improve search accuracy. The overall focus was on refining data integration processes and enhancing the dashboard’s presentation to better meet client needs.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-19 15:14:27

Title: Case Type Naming Cont. Date: Thu Sep 19 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, ryan@brandlytics.io, markmaniora@shield-legal.com, nicholas@tortintakeprofessionals.com, anthony@tortintakeprofessionals.com, david@tortintakeprofessionals.com Transcript: See full transcript Audio: Listen to audio Duration: 10

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-20 09:46:06

Title: Shield Legal // Bytecode - Project Check In Date: Fri Sep 20 2024 10:15:00 GMT-0400 (Eastern Daylight Time) Participants: javier.ramos@bytecode.io, deb.chatterjee@bytecode.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 32

Overview • The Shield Legal and Bytecode Project Check-In and Strategy Discussion meeting focused on key updates regarding project progress and future collaborations. Ryan praised Shane Koski's excellent work on Retool and acknowledged Chris Cadell's organizational contributions, while discussing ongoing efforts to develop 52 custom dashboards for partners and investors, with a priority on tackling integration challenges, particularly those posed by Microsoft throttling. New team members, Dustin and Nick, are set to expedite integration processes significantly. Looking ahead, potential collaborations were highlighted, including a prospective project for a 150+ unit healthcare business and the development of AI-driven legal case management software. Javier mentioned opportunities for Google funding for large projects. Action items included Ryan's commitment to strategize further with Chris post-Vegas and explore partnerships in the legal software domain, while Javier will provide insights on funding opportunities.

Action Items • *Ryan*

• Ryan to spend more hours with Chris next week (after Vegas trip) to determine the direction for the second part of the engagement (29:16)

• Ryan to explore potential partnership with Tulsa attorney for new legal software product (24:15)

• *Javier Ramos*

• Javier to provide more details on Google funding opportunities to Ryan via email (29:16)

Shorthand Bullet • 🚀 *Project Update and Client Satisfaction* (02:55 - 14:16)

• Ryan expressed high satisfaction with Shane Koski's work on Retool

• Chris Cadell praised for organization and cleanup efforts

• 52 custom dashboards for partners/investors being worked on

• Integrations are a priority, facing challenges with Microsoft throttling

• New team members (Dustin, Nick) working on integrations and API development

• Planning to reduce integration time from 15-30 days to 1-2 days

• 💼 *Future Projects and Collaborations* (14:16 - 27:29)

• Javier suggested Chris G. for solution architecture reviews

• Ryan discussed potential project with 150+ unit healthcare business

• Bytecode's involvement in future projects discussed, including white-labeling

• Ryan considering building AI-driven case management software for legal industry

• Javier mentioned Google funding opportunities for large-scale projects

• 🔍 *Product Development* and Industry Insights** (27:49 - 32:11)

• Discussion on existing legal software products (e.g., Litify)

• Ryan's vision for user-friendly, AI-driven legal software

• Challenges in legal software industry discussed

• Brief personal conversation about team locations and city developments

Gist • The meeting aimed to update project progress and explore future collaborations for the Shield Legal and Bytecode Project.

Bullet Gist • ✅ Project Progress: Updates on the development of 52 custom dashboards were discussed, focusing on integration challenges.

• 🚀 Team Contributions: Ryan praised Shane Koski's work on Retool and acknowledged Chris Cadell's organizational skills.

• 🤝 Future Collaborations: Potential projects include a healthcare business initiative and AI-driven legal case management software.

• 💡 Funding Opportunities: Javier mentioned opportunities for Google funding to support large projects.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-20 09:46:06

• 📅 Action Items: Ryan will strategize with Chris post-Vegas, while Javier will explore funding insights.

Short Summary • The Shield Legal and Bytecode Project Check-In and Strategy Discussion meeting involved key updates on project progress and potential collaborations. Ryan commended Shane Koski for his exceptional work on Retool and recognized Chris Cadell for his organizational efforts. The team is working on developing 52 custom dashboards for partners and investors, focusing on overcoming integration challenges, particularly due to Microsoft throttling. New members, Dustin and Nick, are expected to significantly enhance integration processes. Future collaboration opportunities include a project for a 150+ unit healthcare business and the development of AI-driven legal case management software. Javier highlighted the possibility of Google funding for large initiatives. Action items include Ryan's commitment to strategize with Chris after Vegas and Javier's responsibility to provide insights on funding opportunities.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-20 11:10:17

Title: BLX SEO Clients Date: Fri Sep 20 2024 12:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 10

Ryan (ryan@themedialab.agency)
2024-09-20 14:41:11

Impact Analysis dashboard add-ons

• Manufacturer economics • Drug insights • Legal Matter Insights • Audience Insights (from existing court data)

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-23 13:30:33

Title: Tech Project Status Weekly Date: Mon Sep 23 2024 13:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ahsan@shield-legal.com, dwight@shield-legal.com, dschussler@shield-legal.com, ryan@shield-legal.com, dsurwill@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 57

Overview • In this week's Tech Project Status meeting, team members provided updates on various aspects of ongoing projects, emphasizing the PFAS support service microservice currently 40% complete and the Bay Point Environmental Litigation Group's data architecture challenges. Notable progress included Nick’s development of the LR inbox code, capable of pulling 10,000 records in under two minutes, while challenges in extracting data from LawRuler were addressed, alongside discussions on client integration and standardizing naming conventions for layouts and reports. There was a significant focus on the development of financial and sales CRM data pipelines using DBT, new field additions, and plans for an AI dashboard featuring key metrics. Educational insights on MDLs and legal processes were shared, reinforcing their relevance to ongoing work. Action items were assigned, including the completion of the PFAS microservice, enhancement of the LR inbox code, and the modeling of data for the AI dashboard—all aimed at streamlining operations and improving integration between marketing and legal data.

Action Items • *Dustin Schussler*

• Complete PFAS support service microservice by Thursday (07:07)

• *Nick McFadden*

• Deliver LR inbox code ASAP, aim for next sprint (22:00)

• *Brian*

• Expose new fields (billable rate, effective date time) in the app (37:15)

• *Ryan Vaspra*

• Model out data for AI dashboard this week (54:11)

• *Team*

• Standardize naming conventions for LawRuler layouts and reports (26:13)

• *James Scott*

• Enhance data sets for deep learning algorithm (54:11)

Shorthand Bullet • 🚀 *Project Updates and Integration Support* (02:08 - 10:19)

• Dustin working on PFAS support service microservice, 40% complete

• Project for Bay Point Environmental Litigation Group (ELG)

• Discussing data architecture and pipeline challenges

• Nick working on LR inbox code, can pull 10,000 records in under 2 minutes

• 📊 *Data Pipeline and LawRuler Integration* (11:53 - 19:11)

• Discussing challenges with pulling question and answer data from LawRuler

• Exploring options for custom layouts and reports to streamline data extraction

• Cameron's requirements for David Diamond's dashboard discussed

• Need for LR inbox and LR statuses ASAP for financial tables and sales CRM

• 🔧 *Client Integration and Reporting* (20:38 - 27:46)

• Focus on building LR inbox and statuses pipelines

• Discussion on how to handle intake templates and questions

• Proposal to use custom layouts in LawRuler for data extraction

• Need to standardize naming conventions for layouts and reports

• 💼 *Data Warehouse and *Dashboard Development** (29:01 - 37:15)

• Working on DBT tables for financials and sales CRM

• Adding new fields like billable rate and effective date time

• Discussion on updating prices and the importance of effective dates

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-23 13:30:33

• Plans for AI dashboard and meeting with James Scott

• 🏛️ *MDL and Legal Process Discussion* (38:48 - 46:20)

• Cameron provided educational insights on how MDLs work

• Discussion on types of defective drug lawsuits and product liability

• Explanation of the Daubert standard and its importance in MDLs

• Significance of 'failure to warn' in mass tort cases

• 🔍 *AI Dashboard and Data Analysis* (47:29 - 56:48)

• Working on modeling data for AI dashboard

• Development of three key metrics: impact ranking, legal matters viability index, and forecasted economic value

• Discussion on integrating marketing data with legal data for better insights

• Emphasis on prioritizing integrations for future development

Gist • Team members updated on project statuses, focusing on PFAS microservice progress and data architecture issues in litigation.

Bullet Gist • 🚀 PFAS Microservice Progress: The PFAS support service microservice is currently 40% complete.

• 💻 LR Inbox Code Development: Nick developed an LR inbox code that retrieves 10,000 records in under two minutes.

• ⚙️ Data Extraction Challenges: The team addressed challenges in extracting data from LawRuler.

• 📊 AI Dashboard Plans: Plans were discussed for creating an AI dashboard featuring essential metrics.

• 📚 Educational Insights Shared: Insights on MDLs and legal processes were shared to enhance understanding.

Short Summary • In the Tech Project Status meeting, team members provided updates on ongoing projects, highlighting the PFAS support service microservice, which is currently 40% complete. Nick shared impressive progress with the LR inbox code, which can pull 10,000 records in under two minutes. Discussions included challenges with extracting data from LawRuler, client integration efforts, and standardizing naming conventions for reports. There was a strong emphasis on developing financial and sales CRM data pipelines using DBT, as well as new field additions and plans for an AI dashboard featuring key metrics. Educational insights regarding MDLs and legal processes were shared to reinforce their relevance to ongoing work. Action items were assigned, including completing the PFAS microservice, enhancing the LR inbox code, and modeling data for the AI dashboard to streamline operations and improve integration between marketing and legal data.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-24 13:42:23

Title: Shield Legal: dbt follow up Date: Tue Sep 24 2024 14:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, chris.goodell@bytecode.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 37

Overview • The Technical Follow-up Meeting titled "Shield Legal: dbt follow up" focused on key updates and action items related to the ongoing DBT project. Chris and Ryan reported on SQL query improvements, including the deletion of unnecessary lines, the updating of table names, and a decision to refresh data every five minutes. They addressed dashboard and view updates, noting the absence of the 'contract name' field, and opted to maintain current joins without it. Future plans were discussed, including the creation of a snapshot of order financials for validation and the incorporation of new pricing data. They also tackled complex data challenges involving lead flow from WordPress to Leadspedia, emphasizing the need for effective tracking of lead transfers. Action items were assigned, with Chris tasked to create financial snapshots and develop lookup tables alongside Ryan and Brian, while Ryan focused on updating LookML and preparing for further discussions on data formatting.

Action Items • *Chris Goodell*

• Create a snapshot of order financials and place it in the workspace layer (22:22)

• Set up hourly snapshots of order financials (23:02)

• Create lookup reference I/O tables with Ryan and Brian (24:22)

• *Ryan Vaspra*

• Update LookML to make all dashboard-level items measures (22:13)

• Work with Chris and Brian on creating lookup reference I/O tables (24:22)

• Prepare for future discussions on formatting data in lookup I/O tables (36:01)

Shorthand Bullet • 🖥️ *DBT Project Updates* (00:00 - 14:15)

• Chris and Ryan reviewed and updated SQL queries

• Deleted unnecessary lines and updated table names

• Discussed data refresh frequency, settled on every 5 minutes

• Updated database connections and view definitions

• 📊 *Dashboard and View Updates* (14:16 - 18:32)

• Ryan updated dashboard connections

• Discovered missing field 'contract name' in a view

• Discussed the relationship between Copper orders and Leads PDA line items

• Decided not to include contract name to avoid breaking joins

• 🔄 *Data Snapshot and Future Plans* (18:52 - 25:51)

• Ryan requested Chris to create a snapshot of order financials

• Discussed placing the snapshot in the workspace layer for validation purposes

• Planned to create lookup reference I/O tables for the engineering solution

• Mentioned the need to incorporate pricing data from Brian's new pricing portal

• 🏗️ *Complex Data* Challenges** (25:51 - 37:30)

• Explained the lead flow process from WordPress to Leadspedia

• Discussed the complexities of lead prioritization and distribution

• Explored challenges with lead transfers between different law firms

• Brainstormed solutions for tracking transferred leads in the data warehouse

Gist • The meeting focused on updates and action items related to the ongoing DBT project, emphasizing SQL query improvements and future data management plans.

Bullet Gist • 🖥️ DBT Project Updates: Chris and Ryan reviewed SQL queries, improving efficiency and setting a data refresh frequency of every 5 minutes.

• 📊 Dashboard and View Updates: Ryan identified a missing 'contract name' field, deciding to maintain existing joins to avoid disruptions.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-24 13:42:23

• 🔄 Data Snapshot and Future Plans: Plans were made for financial snapshots and incorporating new pricing data to enhance data validation.

• 🏗️ Complex Data Challenges: The team discussed lead flow complexities and brainstormed solutions for tracking lead transfers.

Short Summary • In the Technical Follow-up Meeting titled "Shield Legal: dbt follow up," Chris and Ryan provided updates on the ongoing DBT project, highlighting significant SQL query enhancements such as the elimination of unnecessary lines and updating table names. They decided on a data refresh frequency of every five minutes and addressed dashboard and view updates, noting the absence of the 'contract name' field but opting to maintain current joins to avoid complications. Future plans included creating a snapshot of order financials for validation, incorporating new pricing data from Brian's pricing portal, and developing lookup reference I/O tables. Additionally, they tackled complex challenges related to lead flow from WordPress to Leadspedia, emphasizing the importance of effectively tracking lead transfers among different law firms.

Ryan (ryan@themedialab.agency)
2024-09-26 10:02:17

Build Nursing Home Abuse Litigation - MRW/MRW (TIP) - Contract Datastudio

Ryan (ryan@themedialab.agency)
2024-09-26 10:02:54

Fix 9/24/24 ML Chow - 1664.05 for TikTok 0 leads

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-30 12:14:02

Title: SL Database Maintenance Date: Mon Sep 30 2024 13:00:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, nickmcfadden@shield-legal.com, zhaile@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 10

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-30 14:01:07

Title: DBT Environment & Job cleanup Date: Mon Sep 30 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: chris.goodell@bytecode.io, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 25

Overview • In the recent Technical Discussion and Planning meeting focused on DBT environment and job cleanup, key updates included bug fixes and enhancements to the codebase by Ryan, such as updating financial details, correcting table references, and improving date extraction processes. The team discussed the structure of their DBT environments, agreeing to establish distinct dev, QA (renamed from 'staging'), and production environments, along with a process for transitioning code between them. Emphasis was placed on maintaining a straightforward development workflow, with plans for Chris to tidy up models and annotate areas needing further attention. Action items were assigned, with Chris tasked to set up the release process and finalize changes before a follow-up meeting, while Ryan will review Chris's modifications upon their completion.

Action Items • *Chris Goodell*

• Set up the release process in Shield and replicate it in Tip (18:39)

• Rename DBT transforms to 'team dev' in the development environment (20:28)

• Add comments in the code for areas needing attention (23:29)

• Complete the requested changes and set up a follow-up meeting (23:35)

• *Ryan Vaspra*

• Review the changes made by Chris once completed (22:30)

• Triple-check the references away from BigQuery when new transactional components are done (23:03)

Shorthand Bullet • 🛠️ *Bug Fixes and Enhancements* (00:00 - 09:09)

• Ryan fixed several bugs and made enhancements to the codebase

• Updated financial details and query functions

• Fixed references to old tables

• Updated the way date extraction and pattern lookups were handled

• Identified the need to update the AWS legacy dashboard to the new IO customer type table

• 📊 *Environment and Job Setup* (09:48 - 18:43)

• Discussed the current setup of environments and jobs in DBT

• Ryan expressed desire to have dev, staging (QA), and production environments

• Agreed to rename 'staging' to 'QA' for clarity

• Discussed the process of moving code from team dev to staging to main branch

• Ryan requested help in setting up the release process in Shield and replicating it in Tip

• 🔧 *Development Environment and Workflow* (19:10 - 23:51)

• Decided to rename DBT transforms to 'team dev' in the development environment

• Discussed the workflow for multiple developers working on the project

• Agreed to keep the dev environment simple for now

• Chris offered to clean up models and add comments for areas needing attention

• Planned to meet again after Chris completes the requested changes

Gist • The meeting focused on updates to the DBT environment, including bug fixes and establishing distinct environments for development and production.

Bullet Gist • 🛠️ Bug Fixes and Enhancements: Ryan addressed multiple bugs and improved the codebase, enhancing financial details and query functions.

• 📊 Environment and Job Setup: The team discussed the structure of DBT environments, agreeing to rename 'staging' to 'QA' for clarity.

• 🔧 Development Workflow: Chris is set to tidy up models and add comments, aiming for a simpler development environment.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-30 14:01:07

• In the recent Technical Discussion and Planning meeting, the team concentrated on improving their DBT environment through various bug fixes and code enhancements led by Ryan. Key updates included correcting financial details, fixing outdated table references, and refining date extraction methods. The team agreed on structuring their environments into distinct development, QA (formerly 'staging'), and production settings, alongside a clear process for transitioning code between these stages. Chris volunteered to clean up existing models and annotate areas needing further attention, while action items were assigned, including setting up a release process for Shield and Tip. A follow-up meeting was planned to review Chris’s modifications once completed, ensuring a streamlined development workflow.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-30 14:29:08

Title: Tech Project Status Weekly Date: Mon Sep 30 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ryan@shield-legal.com, dsurwill@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 26

Overview • During the Tech Project Status Weekly meeting, team members provided essential updates on various ongoing projects and discussed integration strategies. Brian kicked off with personal stories, followed by Ryan's insights on a pricing audit and client integrations, while Nicholas Ward reported on the Fivetran dialer implementation progress. A significant focus was placed on the Law Ruler (LR) pipeline development, with Nick McFadden discussing the creation of new layouts for case types and strategies for data management, including the transition from spreadsheets to IO tables for more efficient lookup reference. The team outlined three critical phases for enhancing data integration and building analytics pipelines, with specific action items assigned to members to ensure accountability. Key tasks included scheduled SQL query creations, ongoing support for integration issues, and training efforts to advance the Fivetran implementation by mid-October.

Action Items • *Brian Hirst*

• Work on table scheduled queries for update and insert in tip portal with Ryan (03:57)

• Collaborate with Darrell on lead integration for Fivetran implementation (08:57)

• *Nick McFadden*

• Continue working on PFAs and VGA meadow integration issues (05:46)

• Build functions for each layout to pull data into BigQuery (10:39)

• Oversee team in building out pipeline connections for all tables into BigQuery (10:39)

• *Nicholas Ward*

• Complete Fivetran dialer implementation build-out by the third week of October (07:59)

• Conduct UAT with identified group for two weeks (07:59)

• Start training with supervisor team and training the trainer sessions (07:59)

• *Ryan Vaspra*

• Create scheduled BigQuery SQL query for IO LR Tip LR statuses table (18:24)

• Meet with Quint regarding calculate performance AWS Python Lambda fix (23:37)

• *James Scott*

• Continue working on AI project, adding objects to storyboard and visualizations (21:36)

• Develop new patent-pending metric for legal viability (21:36)

Shorthand Bullet • 🚀 *Project Updates and Personal Anecdotes* (02:03 - 08:59)

• Brian shared personal anecdotes about his haircut experience and winning a Mercedes auction

• Ryan discussed pricing audit and at tip pricing with Brian

• Nick McFadden reported on client integration support progress

• Nicholas Ward provided updates on Fivetran dialer implementation

• 📊 *Law *Ruler Pipeline Development** (08:59 - 16:32)

• Nick McFadden updated on LR statuses and layouts built

• Discussed creating new layouts per case type and per active campaign

• Plan to build functions for each layout to pull data into BigQuery

• Debate on including work-in-progress leads or only finalized leads

• Discussion on using LR statuses table for filtering and creating DBT table models

• 🔧 *Data Management* and Integration** (16:58 - 25:37)

• Discussed creating IO tables for lookup references and moving away from spreadsheets

• Plans to build manufacturer profiles, drug profiles, and a new patent-pending metric for legal viability

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-09-30 14:29:08

• Nick McFadden outlined three phases for the team: new integration method, building pipelines and dashboards, and internal analytics

• Ryan mentioned upcoming work on Google Cloud project leads media sold leads CD CI Pipe and Fivetran cloud function development

• Discussed assigning team members to various projects and the importance of managing pipelines

Gist • The meeting focused on project updates and strategies for improving data integration within ongoing projects.

Bullet Gist • 🚀 Project Updates and Personal Stories: Team members shared personal anecdotes and provided essential updates on ongoing projects.

• 📊 Law Ruler Pipeline Development: Discussion on new layouts for case types and strategies for effective data management.

• 🔧 Data Management and Integration: Plans to transition to IO tables and build profiles for better data handling.

Short Summary • During the Tech Project Status Weekly meeting, team members shared critical updates on various projects, emphasizing integration strategies. Brian opened the session with personal anecdotes, while Ryan presented insights on a pricing audit and client integrations. Nicholas Ward reported on the Fivetran dialer implementation's progress. A significant focus was on the Law Ruler (LR) pipeline development, where Nick McFadden discussed new layouts for case types and strategies for transitioning from spreadsheets to IO tables for efficient data management. The team outlined three essential phases for enhancing data integration and building analytics pipelines, assigning specific action items to ensure accountability, including SQL query creations, support for integration issues, and advancing Fivetran implementation by mid-October.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-02 14:48:41

Title: Case Type Naming Cont. Date: Wed Oct 02 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, ryan@brandlytics.io, markmaniora@shield-legal.com, nicholas@tortintakeprofessionals.com, anthony@tortintakeprofessionals.com, david@tortintakeprofessionals.com, malissa@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 41

Overview • The Strategy and Planning Meeting focused on establishing a standardized naming convention for case types across the team’s systems and integrations. The discussion began with identifying responsible team members and examining inconsistencies in naming for California juvenile halls. Ryan proposed a new naming format that includes details such as parent case type, retainer code, and billing ID, emphasizing the importance of consistency through acronyms and dropdowns. Action items were assigned, with Anthony tasked to create test case types based on this format, and Ryan to document the new guidelines. Additionally, the meeting covered clarifications on contract IDs, dashboard access, and a review of the 'live orders pacing' dashboard, with Melissa assigned to update campaign statuses accordingly.

Action Items • *Anthony*

• Create a test case type using the new naming format provided by Ryan (10:22)

• Start building new case types using the provided guidance and create a spreadsheet with concatenation formula (21:55)

• *Ryan*

• Document the new case type naming format in the Monday board (21:55)

• Check the test case type in the morning and confirm the final format (24:18)

• *Melissa*

• Follow up on updating campaign statuses in Leads PD, Monday board, and Copper (39:43)

Shorthand Bullet • 🏛️ *Case Type Naming and Structure* (00:02 - 07:18)

• Review of team members responsible for different systems and integrations

• Discussion of active California juvenile halls and variations in naming

• Identification of messy naming conventions for juvenile halls

• 📊 *New Case Type Naming Format* (07:18 - 23:12)

• Ryan proposes a new format for case type naming

• Breakdown of proposed format: parent case type, retainer code, client firm, partner firms, billing ID, and service

• Discussion of acronyms and drop-down boxes for consistent naming

• Anthony to create test case types using the new format

• 🔍 *Contract IDs and Dashboard Access* (23:12 - 31:08)

• Clarification on contract IDs and their relation to Leads PD IDs

• Discussion on accessing the Looker Enterprise dashboard

• Ryan grants Anthony access to the 'tip live orders pacing' dashboard

• 📈 *Dashboard Review and Naming Convention* (33:07 - 41:15)

• Review of the 'live orders pacing' dashboard

• Discussion on using Leads PD contract IDs in new naming conventions

• Melissa to follow up on updating statuses of campaigns in various systems

Gist • The meeting aimed to standardize naming conventions for case types across systems and assign responsibilities for implementation.

Bullet Gist • 🏛️ Case Type Naming Review: Reviewed responsibilities for systems and naming inconsistencies in California juvenile halls.

• 📊 Proposed Naming Format: Ryan proposed a new format for case types to enhance consistency and clarity.

• 🔍 Contract IDs Clarification: Clarified the relationship between contract IDs and Leads PD IDs, and dashboard access.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-02 14:48:41

• 📈 Dashboard Review: Reviewed the 'live orders pacing' dashboard and discussed updates for campaign statuses.

• ✅ Action Items Assigned: Assigned specific tasks to team members to implement the new naming conventions.

Short Summary • A Strategy and Planning Meeting was held to establish a standardized naming convention for case types within the team's systems and integrations. The discussion commenced with identifying team members responsible for different systems, focusing particularly on inconsistencies in naming for California juvenile halls. Ryan proposed a new naming format incorporating elements such as parent case type, retainer code, client firm, partner firms, billing ID, and service, stressing the need for consistency through the use of acronyms and dropdown menus. Action items were assigned, with Anthony tasked to create test case types based on the new format and Ryan responsible for documenting the guidelines. Additionally, clarifications on contract IDs and dashboard access were made, including access to the 'live orders pacing' dashboard that Melissa was assigned to update campaign statuses for.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-04 10:34:11

Title: BLX SEO Clients Date: Fri Oct 04 2024 11:15:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, kelly@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 18

Overview • During the Project Planning and Task Assignment meeting for the BLX SEO Clients, Ryan and Kelly discussed the current status of the Black Farmer Justice campaign, confirming that Kelly had already written the necessary content. Ryan outlined the strategy for upcoming organic campaigns, detailing the workflow triggered by custom microsites and paid campaigns, and decided to create a separate vertical for BLX Organic. He assigned Kelly tasks including drafting a practice area, three-pack, and blog article for the Minority Farmer Justice campaign, providing a demonstration on how to create and link tasks in their project management system. In addition, Ryan mentioned his upcoming trip to Vegas, encouraging Kelly to explore meeting the team in person and highlighting the significance of her SEO contributions. Action items were delegated to both Ryan and Kelly, with specific deadlines set for task completion and collaboration on campaign alignment.

Action Items • *Kelly Richardson*

• Draft three-pack and blog article for the Minority Farmer Justice campaign (09:47)

• Get pages drafted and send to Ryan and Adrian (14:14)

• Ask about possibility of visiting Vegas to meet the team (16:38)

• *Ryan Vaspra*

• Create clone vertical for BLX Organic (12:03)

• Clone contracts for BLX Organic (12:03)

• Add test intake docs or BLX test lead calls forms (12:03)

• Send campaign information to Uzi for social alignment (12:03)

Shorthand Bullet • 🔍 *Project Setup and Task Assignment* (03:44 - 09:46)

• Ryan shared a to-do list item with Kelly

• The item is related to Cameron's current campaign: Black Farmer Justice

• Kelly confirmed she had already written content for this campaign

• 📊 *Campaign Strategy Discussion* (09:47 - 12:05)

• Ryan explained the strategy for organic campaigns

• When Cameron builds a custom microsite or launches a paid campaign, it triggers an organic campaign

• Organic campaign includes a three-pack, blog article, and coordination with Uzi for social media alignment

• Ryan decided to create a clone vertical for BLX Organic to avoid blending with Cameron's vertical

• 🚀 *Task Creation and Assignment* (13:13 - 15:28)

• Ryan created a task for Kelly to draft pages for the Minority Farmer Justice campaign

• The task includes creating a practice area, three-pack, and blog article

• Ryan demonstrated how to create and link tasks in their project management system

• ✈️ *Travel Discussion* (16:14 - 17:12)

• Ryan mentioned he'll be in Vegas next week for work

• Suggested Kelly ask to visit Vegas to meet the team (Melanie, Adrian, Latoya)

• Emphasized the importance of Kelly's SEO work for Ben Crump

Gist • Ryan and Kelly met to discuss the Black Farmer Justice campaign and task assignments for upcoming organic campaigns.

Bullet Gist • 🔍 Project Setup: Ryan shared a task list item with Kelly related to the Black Farmer Justice campaign.

• 📊 Strategy Discussion: Ryan outlined the strategy for organic campaigns triggered by custom microsites and paid campaigns.

• 🚀 Task Assignment: Kelly was assigned to draft materials for the Minority Farmer Justice campaign.

• ✈️ Travel Plans: Ryan mentioned his trip to Vegas and encouraged Kelly to meet the team in person.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-04 10:34:11

• Ryan and Kelly conducted a Project Planning and Task Assignment meeting focused on the Black Farmer Justice campaign. Kelly confirmed that she had already written the necessary content for the campaign, while Ryan outlined the strategy for the upcoming organic campaigns, emphasizing the workflow triggered by custom microsites and paid campaigns. To streamline operations, Ryan decided to create a separate vertical for BLX Organic. He assigned Kelly several tasks related to the Minority Farmer Justice campaign, which included drafting a practice area, a three-pack, and a blog article. Ryan also provided Kelly with a demonstration on task creation in their project management system. Additionally, he mentioned his upcoming trip to Vegas, encouraging Kelly to meet with the team in person and underscoring the significance of her contributions to SEO efforts.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-04 14:38:58

Title: Brian/Cam/Ryan Date: Fri Oct 04 2024 14:30:00 GMT-0400 (Eastern Daylight Time) Participants: brian@themedialab.agency, ryan@shield-legal.com, ryan@brandlytics.io, cameron@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 65

Overview • In the Performance Review and Strategic Planning meeting, attendees Brian, Cam, and Ryan began with personal updates, including Ryan's sons' recent sports achievements and Brian's five-year work anniversary. The meeting focused on Brian's performance review, where he discussed his evolving role and contributions, specifically in LeadsPD, Five9, and Salesforce integration, and proposed an adjustment to his compensation structure. The conversation shifted to company restructuring, considering Brian's transition to a Nevada W-2 employee and the potential relocation package. A financial overview highlighted the company's significant losses and plans to consolidate staff as well as commission considerations for certain clients. The group explored the future of the TortIntelligence AI project, contemplating its separation into a new company and equity distribution among key stakeholders. The meeting concluded with discussions on outstanding client debts, software development ideas for affordable case management solutions, and action items assigned to attendees, including preparation of a revenue report and follow-ups on compensation reviews.

Action Items • *Cameron and Ryan*

• Cameron and Ryan to meet with Shelly next week to review Brian's compensation (43:35)

• *Cameron*

• Cameron to discuss with Mark about potentially making TortIntelligence a separate company (59:36)

• Cameron to follow up with Ryan once he receives missing information on invoicing (01:05:02)

• *Ryan*

• Ryan to prepare revenue report for September and send out invoices (01:04:48)

Shorthand Bullet • 🏈 *Personal Updates and Catch-up* (00:01 - 09:12)

• Ryan's son had a breakout football game

• Ryan's other son is improving in golf

• Brian reached his 5-year work anniversary on October 1

• 💼 *Brian's Performance Review* (10:48 - 24:28)

• Brian discussed his changing role and responsibilities

• Brian highlighted his work on LeadsPD, Five9, and Salesforce integration

• Brian proposed removing his bonus and increasing base salary to $113,750

• 🔄 *Company Restructuring* (24:31 - 39:02)

• Discussion about moving Brian to Nevada W-2 employee status

• Potential relocation package offered for moving to Nevada

• Proposal to review Brian's compensation next week

• 💰 *Financial Discussion* (39:11 - 46:27)

• Cameron mentioned Tip company is losing $600,000-$700,000 per month

• Discussion about moving Brandlytics employees to Shield

• Consideration of paying Ryan commissions on Ben Crump's organic work

• 🤖 *TortIntelligence AI Project* (46:30 - 52:10)

• Discussion about potentially making TortIntelligence a separate company

• Consideration of equity split between Cameron, Ryan, and James

• Emphasis on keeping James (AI developer) engaged long-term

• 💸 *Client Debts and Billing* (52:38 - 01:00:19)

• Discussion about Jeff Dubin's outstanding debt

• Review of stable clients: Dishwitz and Crump

• Consideration of billing structure for various clients

• 🖥️ *Software Development* Ideas** (01:00:49 - 01:05:18)

• Discussion about developing lean, affordable case management software

• Consideration of monetizing TortIntelligence data sets

• Cameron mentioned issues with outbound call numbers being flagged

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-04 14:38:58

• The meeting focused on Brian's performance review, company restructuring, and future projects, including the TortIntelligence AI venture.

Bullet Gist • 📈 Performance Review: Brian discussed his evolving role and proposed changes to his compensation.

• 🏢 Company Restructuring: The team considered Brian's transition to a Nevada W-2 employee and relocation packages.

• 💸 Financial Overview: Significant losses were reported, prompting discussions on staff consolidation and commissions.

• 🤖 AI Project Future: The group explored separating the TortIntelligence AI project into a new company.

• ✅ Action Items: The meeting concluded with assigned tasks, including a revenue report and follow-ups on compensation.

Short Summary • Attendees Brian, Cam, and Ryan began their meeting with personal updates before delving into a performance review for Brian. He highlighted his evolving role and contributions related to LeadsPD, Five9, and Salesforce integration, along with a proposal for adjusting his compensation structure. The conversation then shifted to company restructuring, with discussions about Brian transitioning to a Nevada W-2 employee and possible relocation packages. A financial overview revealed significant company losses and plans to consolidate staff, alongside considerations for commission adjustments for specific clients. The group also explored the future of the TortIntelligence AI project, discussing the possibility of separating it into a new company and equity distribution among key stakeholders. The meeting concluded with discussions on outstanding client debts, affordable case management software development ideas, and action items, including preparation of a revenue report and follow-ups on compensation reviews.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-04 15:02:19

Title: Dev Site training Date: Fri Oct 04 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: dustinsherin@aerongroup.com, ryan@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 23

Overview • The Training and Handover Meeting focused on equipping Dustin Sherin with the necessary skills and knowledge to manage and edit the development site using WordPress and the Beaver Builder plugin. Led by Ryan, the meeting covered essential topics including an introduction to the WordPress admin area, customization of site elements like headers and logos, and site management techniques. Key points included best practices for image quality, the process of going live, and navigating the Beaver Builder interface. Ryan also provided login information and addressed troubleshooting aspects, guiding Dustin through the editing process. Action items for Dustin include content updates, photo adjustments, and familiarization with the Beaver Builder interface, while Ryan committed to sending full login credentials for access.

Action Items • *Dustin Sherin*

• Review and update content on the dev site (05:41)

• Change photos that don't match the context or don't speak to the content (12:10)

• Improve the sharpness of the logo on the home banner (16:17)

• Familiarize himself with the Beaver Builder interface (22:44)

• *Ryan Vaspra*

• Send full login information to Dustin (17:55)

Shorthand Bullet • 🖥️ *WordPress and Beaver Builder Introduction* (00:00 - 05:02)

• Ryan explains WordPress admin login and Beaver Builder plugin

• Demonstrates global header and footer editing

• Shows how to navigate and edit pages using Beaver Builder interface

• Explains responsive design and mobile optimization

• 🎨 *Design and Customization* (05:02 - 10:13)

• Ryan discusses customization of headers, logos, and favicons

• Explains how to change colors and upload images

• Mentions the importance of image quality and resolution

• Discusses the process of going live with the site

• 🛠️ *Site Management* and Editing** (10:13 - 17:12)

• Ryan emphasizes the importance of site ownership and control

• Explains how to add new pages and make content changes

• Discusses Beaver Builder community resources

• Demonstrates how to change photos and background images

• 🔑 *Login Information and Troubleshooting* (17:12 - 23:25)

• Ryan provides login information for the dev site

• Explains how to access the Beaver Builder editor

• Discusses potential browser compatibility issues

• Walks Dustin through the editing process

Gist • The meeting equipped Dustin Sherin with skills to manage the development site using WordPress and Beaver Builder.

Bullet Gist • 🖥️ WordPress Basics: Ryan introduced the WordPress admin area and demonstrated using the Beaver Builder plugin.

• 🎨 Site Customization: Customization of headers, logos, and the importance of image quality were key topics discussed.

• 🛠️ Managing Content: Ryan taught Dustin how to add new pages and make content changes effectively.

• 🔑 Access and Troubleshooting: Login information was provided, along with troubleshooting advice for editing.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-04 15:02:19

• Dustin Sherin participated in a Training and Handover Meeting led by Ryan, aimed at providing him with the necessary skills to manage and edit a development site using WordPress and the Beaver Builder plugin. The session included an introduction to the WordPress admin area, where Ryan demonstrated how to navigate the Beaver Builder interface, edit global headers and footers, and customize site elements such as logos and colors. Key topics included best practices for image quality, the process of going live with the site, and managing site content effectively. Ryan also emphasized the importance of site ownership and provided troubleshooting tips, including addressing potential browser compatibility issues. Action items for Dustin were established, including updates to content and photos, along with the need to familiarize himself with the Beaver Builder interface.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-11 15:02:07

Title: BSS meeting - Facebook Ads - October Date: Fri Oct 11 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, francis.meram@gmail.com, chantelle@savvybrandinggroup.com, rvaspra@me.com Transcript: See full transcript Audio: Listen to audio Duration: 32

Overview • The October Marketing Strategy Meeting focused on the performance and future direction of Facebook Ads, highlighting the impact of the election on advertising costs and the need for budget adjustments due to high cost-per-click rates. Key discussions included the slow lead generation at the Vista location, prompting a suggestion to create Spanish-language ads to better engage potential customers. The team also addressed challenges in content creation at the Vista site, considering new pricing for advertising and the proposal to promote studios starting at $225 per week. It was decided to pause high-cost-per-lead ads and replace them with new campaigns, while also formulating a broader advertising strategy for Michigan studios, excluding Detroit and targeting within a 7-10 mile radius. Action items were assigned, with Francis responsible for providing lease information and Chantelle tasked with creating new ads, setting up campaigns, and collaborating with Sarah on ad content modifications.

Action Items • Francis Meram

• Provide lease information including email, phone, and location for exclusion list (31:08)

• Chantelle

• Create new ads with pricing information for Vista (20:27)

• Set up two new ad campaigns: lead form and messenger (29:07)

• Pause high-cost-per-lead ads after setting up new replacement ads (23:21)

• Work with Sarah on modifying creative content for ads (27:05)

• Create a general ad for Michigan locations (27:23)

Shorthand Bullet • 📊 Facebook** Ads Performance and Strategy (00:26 - 11:21)

• Election time impacts advertising costs and strategy

• Francis adjusted budgets due to high cost per click

• Lead generation in Vista has been slow

• Number of tours has decreased dramatically

• Suggestion to create Spanish language ads for Vista

• Francis built an AI chatbot for Instagram messaging

• 🏢 Vista Location and Content Strategy (11:22 - 22:41)

• Discussion about filming at Vista location

• Vista often empty, challenging for content creation

• Consideration of advertising pricing for Vista

• Proposal to advertise 'Studios starting at $225 per week'

• Discussion of lease terms and free rent offers

• Plan to create two ad types: lead form and messenger

• 💼 Pricing Strategy and Ad Campaigns (22:42 - 31:50)

• Decision to pause high-cost-per-lead ads

• Plan to create replacement ads with new pricing strategy

• Discussion of pricing strategy for Michigan locations

• Agreement to create a general ad for Michigan studios

• Plan to exclude Detroit from campaigns

• Suggestion to use 7-10 mile radius for targeting

Gist • The meeting focused on Facebook Ads performance and budget adjustments due to high costs, with strategies for improving lead generation at the Vista location.

Bullet Gist • 📈 Ad Performance Review: The meeting assessed the current performance of Facebook Ads and its impact on marketing budgets.

• 💬 Targeted Advertising: The team suggested Spanish-language ads to enhance engagement in the Vista location.

• :octagonal_sign: Pausing High-Cost Ads: High-cost-per-lead ads will be paused, with new campaigns to replace them.

• 💡 New Pricing Strategy: Discussion included new pricing options for advertising, promoting studios starting at $225 per week.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-11 15:02:07

• 📍 Michigan Strategy Focus: A broader advertising strategy for Michigan studios was formulated, focusing on a specific geographic radius.

Short Summary • The October Marketing Strategy Meeting centered on assessing Facebook Ads' performance, particularly in light of rising advertising costs linked to the upcoming election. The discussion highlighted slow lead generation at the Vista location, leading to the proposal of creating Spanish-language ads to better reach potential customers. The team also confronted content creation challenges and considered adjusting pricing for advertising, proposing to promote studios starting at $225 per week. A significant decision was made to pause high-cost-per-lead ads in favor of new campaigns, as well as to develop a broader advertising strategy targeting Michigan studios, while excluding Detroit and focusing on a 7-10 mile radius. Action items were assigned, with Francis responsible for providing lease information, while Chantelle was tasked with creating new ads and collaborating with Sarah on content modifications.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-14 14:35:23

Title: Tech Project Status Weekly Date: Mon Oct 14 2024 15:00:00 GMT-0400 (Eastern Daylight Time) Participants: brian@shield-legal.com, jamesscott@shield-legal.com, ryan@brandlytics.io, nickmcfadden@shield-legal.com, nicholas@tortintakeprofessionals.com, ryan@shield-legal.com, dsurwill@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 35

Overview • The Tech Project Status Weekly meeting covered important updates and planning for ongoing projects, particularly focusing on client reporting and data warehouse enhancements, with Ryan and Brian leading efforts on the rev rates table and the completion of IO table setups. A significant improvement in API performance for Law Ruler’s inbox data was discovered by Dustin, though potential fragility of the solution was noted. New naming conventions for case types were proposed to enhance data clarity, emphasizing the inclusion of contract IDs. Integration efforts are progressing, with a majority of systems transitioned to Google Cloud Platform (GCP), and a clear plan for tackling integration backlogs in the coming weeks. Positive feedback was shared regarding an AI project aimed at assessing lawsuit viability. Action items were assigned to team members, including updates on data structures, integration tasks, and preparation for upcoming dashboard sessions.

Action Items • Ryan Vaspra

• Update rev rates table with new column names and additional fields (04:39)

• Review tip status fields with Tony and Alan (07:29)

• Double-check expense categories for IO table (09:20)

• Set up code owners team in GitHub for production environments (28:19)

• Brian Hirst

• Work on data engineering for IO tables (04:39)

• Prepare for development on models, dashboards, and portals once LR inbox and sold leads data are available (19:24)

• Dustin Surwill

• Continue moving integrations from MPA to GCP (26:16)

• Complete pulling everything out of MPA by end of the week (26:51)

• James Scott

• Add data sources to beta MVP data studio before next meeting (32:04)

• Prepare for dashboard building session on Thursday (32:49)

Shorthand Bullet • 🚀 Project Updates and Planning (01:42 - 15:55)

• Ryan and Brian to focus on client reporting projects and tip data warehouse

• Updates coming to rev rates table

• Changes to column names for clarity

• Addition of new fields including cost, margin, and status-based pricing

• Scheduled queries and DBT updates required

• Tip status fields to be reviewed with Tony and Alan

• Complete IO table setup discussed

• Commission schedule table to be created

• 💻 LR Inbox and API Discussion (15:58 - 20:18)

• Dustin discovered faster API method for pulling inbox data from Law Ruler

• New method simulates user actions, resulting in faster data retrieval

• Potential fragility if Law Ruler changes filters on inbox page

• Brian interested in accessing sold leads data from LeadsPedia

• 📊 Naming Conventions and Data Structure (20:18 - 26:54)

• New naming convention proposed for case types

• Importance of including contract IDs in case names

• Example of naming structure: location, case type, contract ID, billable amounts

• Aim to improve data clarity for manual processes and data ties

• 🔄 Integration Updates and Future Plans (27:02 - 35:00)

• 21 integrations moved to GCP, with 15-20 more to be uploaded

• Full transition out of MPA expected by end of the week

• Integration backlog estimated to take 2-4 weeks to clear

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-14 14:35:23

• James working on member cases data and dashboard updates

• AI project received positive feedback, with new metric for lawsuit viability in development

• Team progress praised, with projects coming together

Gist • The meeting focused on updates and planning for tech projects, particularly client reporting and data warehouse enhancements.

Bullet Gist • 🚀 Project Updates and Planning: Ryan and Brian are focusing on enhancements to client reporting projects and the data warehouse.

• 💻 API Performance Discovery: Dustin introduced a faster method for retrieving inbox data from Law Ruler, though it may be fragile.

• 📊 New Naming Conventions: Proposals for case type naming conventions aim to improve clarity by including contract IDs.

• 🔄 Integration Progress: 21 integrations have moved to GCP, with plans for a complete transition by week’s end.

• 🤖 Positive AI Project Feedback: An AI project assessing lawsuit viability received commendations and is developing new metrics.

Short Summary • The Tech Project Status Weekly meeting, led by Ryan and Brian, covered critical updates on ongoing projects including client reporting and improvements to the data warehouse. Ryan and Brian discussed enhancements to the rev rates table and completion of IO table setups, while Dustin shared a significant discovery regarding API performance for Law Ruler's inbox data, although concerns about potential fragility were noted. New naming conventions for case types were proposed to enhance data clarity, emphasizing the importance of including contract IDs. Integration efforts are progressing well, with a majority of systems transitioned to Google Cloud Platform (GCP), and a clear plan to tackle integration backlogs in the coming weeks. Positive feedback was given regarding an AI project focused on assessing lawsuit viability, and action items were assigned to team members for updates on data structures, integration tasks, and dashboard preparations.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-14 16:08:46

Title: Tip and Finance Meeting Date: Mon Oct 14 2024 16:00:00 GMT-0400 (Eastern Daylight Time) Participants: tony@tortintakeprofessionals.com, ryan@shield-legal.com, cameron@themedialab.agency, alan@tortintakeprofessionals.com, brian@accountingdept.net, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 58

Overview • In the Financial Review and Strategy Meeting, key discussions revolved around a comprehensive analysis of the company’s financial performance, including a detailed breakdown of profit and loss (P&L), cost structures at various operational levels, and the performance metrics of the processing and intake teams. Ryan led the analysis, addressing payroll costs and operational strategies, while the team explored necessary adjustments to pricing strategies for specific case types to ensure department expenses are covered without seeking profit margins initially. The meeting highlighted the importance of setting ambitious targets to enhance departmental efficiency, considering potential shifts in operational hours to increase revenue, and outlined action items including modeling new pricing strategies into the financial forecasts and preparing for follow-up discussions on financial scenarios. Key responsibilities were assigned to Ryan, Cameron, and Tony to ensure implementation and review of the outlined strategies.

Action Items • Ryan

• Model new pricing into July-September financials (56:14)

• Complete month-end close for September using August pricing (51:10)

• Prepare financial scenarios for review with Cameron and Mark (55:16)

• Cameron

• Review financial scenarios with Ryan and Mark (55:18)

• Tony

• Adjust pricing for case types with limited work scope (56:36)

Shorthand Bullet • 📊 Financial Analysis and Pricing (00:26 - 21:28)

• Ryan presented a breakdown of P&L analysis and cost structure

• Discussed lead level, case type level, and sign-up level cost structures

• Analyzed payroll costs minus agent commissions

• Reviewed Tony's inbound (case review qualifications) and outbound breakdown

• Discussed ASA (Account Services) team costs

• 💰 Pricing Strategy (21:29 - 28:10)

• Cameron requested to see billing impact for the last three months using new figures

• Discussed not implementing changes retroactively

• Aim to cover department expenses without profit margin for now

• Need to adjust pricing for certain case types (e.g., stock fraud, ACV gummy)

• 📈 Department Performance Metrics (28:10 - 34:45)

• Calculated required performance metrics for processing department

• Discussed daily and monthly targets for employees

• Cameron suggested setting higher targets to ensure meeting actual goals

• 👥 Team Analysis (34:57 - 40:44)

• Analyzed performance metrics for pre-screeners and intake teams

• Discussed potential shrinking of screening department

• Calculated daily and monthly targets for different departments

• 🔍 Department-specific Analysis (40:53 - 47:49)

• Reviewed metrics for processing, outbound intake, outbound pre-intake screening, and inbound teams

• Discussed the need to maximize working hours and expand shifts

• Considered weekend work to capture more revenue

• 🚀 Next Steps and Financial Modeling (47:49 - 58:15)

• Ryan to model new pricing into July-September financials

• Plan to review impact on media buyer commissions and other downstream effects

• Scheduled meeting with Mark to discuss financial scenarios

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-14 16:08:46

• Need to adjust pricing for certain case types with limited work scope

Gist • The meeting aimed to analyze the company's financial performance and strategize adjustments to improve efficiency and profitability.

Bullet Gist • 💰 Financial Performance Analysis: The team analyzed the company’s financial performance, focusing on P&L and cost structures.

• 📊 Operational Strategies: Discussion included payroll costs and necessary adjustments to pricing strategies.

• 🎯 Setting Targets: Ambitious targets were emphasized to enhance departmental efficiency.

• 🕰️ Operational Hours Review: Potential shifts in operational hours were considered to boost revenue.

• 📝 Action Items Assigned: Ryan, Cameron, and Tony were tasked with implementing and reviewing strategies.

Short Summary • In the Financial Review and Strategy Meeting, the team conducted a comprehensive analysis of the company's financial performance, focusing on the profit and loss (P&L) statements and cost structures at various operational levels. Led by Ryan, the discussion included an evaluation of payroll costs and operational strategies, with an emphasis on necessary adjustments to pricing strategies for specific case types to ensure that department expenses are covered without initially seeking profit margins. The importance of setting ambitious targets to enhance departmental efficiency was highlighted, with considerations for potential shifts in operational hours to increase revenue. Action items included modeling new pricing strategies into financial forecasts and preparing for follow-up discussions on various financial scenarios. Key responsibilities were assigned to Ryan, Cameron, and Tony to implement and review the strategies discussed.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-16 11:58:48

Title: Caleb mid month commission Date: Wed Oct 16 2024 12:45:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@shield-legal.com, cameron@themedialab.agency, caleb@shield-legal.com, brian@accountingdept.net, ryan@brandlytics.io, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 10

Overview • In the "Caleb Mid Month Commission" Operational Review and Troubleshooting meeting, key issues were discussed regarding the management of paraquat leads, where Cameron identified numerous duplicates causing rejections, with a plan to investigate the DQ list. Additionally, concerns were raised about a new form launched by Caleb, which also experienced duplicate issues suspected to be linked to Zapier. The team acknowledged a significant drop in lead conversion rates, declining from 8-9% to 1%, prompting Cameron to explore potential posting issues in the leads p era and Law Ruler systems. An update on Depo Provera cases indicated the need for expanded age targeting for those diagnosed post-1992. Action items were outlined for team members, including investigating rejection reasons, examining system glitches, and addressing expansion of age criteria.

Action Items • Cameron Rentch

• Investigate the DQ list to understand rejection reasons (01:24)

• Run a report and look into potential posting issues (03:09)

• Examine possible glitches in leads p era and law ruler (03:09)

• Caleb Peters

• Consider expanding age targeting for Depo Provera cases (04:27)

• Ryan

• Complete the commission email (00:01)

• Brian

• Potentially assist in investigating system issues (02:17)

Shorthand Bullet • 🔍 Paraquat Issues and Duplicates (00:01 - 02:45)

• Cameron noticed issues with paraquat leads in the last few days

• Many duplicates showing in the system

• Leads PDF showing 'not matched' despite being duplicates

• 58 leads rejected yesterday

• Cameron plans to investigate DQ list

• 🖥️ Zapier and Form Issues (01:24 - 02:57)

• Caleb launched a new form with clean exclusion lists

• Still experiencing duplicate issues with the new form

• Suspicion that Zapier might be causing the problem

• 📊 Lead Conversion Drop (03:09 - 04:01)

• Conversion rate dropped from 8-9% to 1% over three days

• Cameron suspects a glitch in the system

• Plans to investigate posting issues in leads p era and law ruler

• 💊 Depo Provera Update (04:01 - 04:27)

• Retainers uploaded this morning

• Can take cases for anyone who used it after 1992

• Age limit: under 70 with a diagnosis

• Suggestion to expand age targeting

Gist • The meeting aimed to address issues with paraquat leads, duplicate entries, and a drop in lead conversion rates.

Bullet Gist • 🔍 Paraquat Issues and Duplicates: Cameron identified duplicates in paraquat leads, causing rejections and plans to investigate the DQ list.

• 🖥️ Zapier and Form Issues: Caleb's new form launched to clean up exclusion lists still faces duplicate issues, potentially linked to Zapier.

• 📊 Lead Conversion Drop: The conversion rate has drastically fallen from 8-9% to 1%, prompting a review of system glitches.

• 💊 Depo Provera Update: There’s a need to expand age targeting for cases related to Depo Provera, especially for diagnoses after 1992.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-16 11:58:48

• During the 'Caleb Mid Month Commission' Operational Review and Troubleshooting meeting, participants discussed critical issues surrounding the management of paraquat leads, where Cameron highlighted the presence of numerous duplicate entries causing rejections. He plans to investigate the DQ list to address these duplicates. Additionally, concerns arose regarding a new form launched by Caleb, which also faced duplication problems, suspected to be related to the Zapier integration. The team noted a significant drop in lead conversion rates, plummeting from 8-9% to 1%, prompting Cameron to explore potential posting issues within the leads p era and Law Ruler systems. An update on Depo Provera cases indicated the necessity for broader age targeting for individuals diagnosed post-1992, leading to action items that included examining rejection reasons, system glitches, and expanding age criteria.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-21 11:59:43

Title: BLX Media Buying Date: Mon Oct 21 2024 12:30:00 GMT-0400 (Eastern Daylight Time) Participants: ryan@brandlytics.io, lee@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 24

Overview • The Operations and Analytics Review meeting for BLX Media Buying focused on a comprehensive analysis of case counts and updates across various projects, including the Atlantis Forest Cove apartments and Camp of June cases, with particular attention paid to the recent spike in Drax case numbers. Ryan and Lee addressed the classification of cases, distinguishing between retainer and non-retainer categories, and reviewed current data on Shield cases along with significant incidents such as Illinois clergy abuse. They also examined qualified leads, media spending, and invoicing issues related to BLX, exploring opportunities to integrate Brandlytics services into Shield. Action items included Ryan's responsibilities to rectify naming issues and coordinate Lee's potential transition to the Shield side, while Lee is tasked with monitoring media spend and preparing for future special projects.

Action Items • Ryan

• Fix naming issue for Depot Provera BCL cases (02:13)

• Add sheet for Depot Provera cases (03:07)

• Talk to Cameron about Lee's formal move to the Shield side (22:58)

• Bill Markowitz another gram after discussing with Cameron (22:58)

• Lee

• Continue tracking media spend as negative for now (21:23)

• Prepare to potentially take on campaigns for Shades of Mass and other special projects for Cameron (23:24)

Shorthand Bullet • 📊 Case Review and Analytics (00:00 - 09:17)

• Ryan and Lee reviewed case counts for various projects

• Discussed Atlantis Forest Cove apartments, Port City BLX, and Camp of June cases

• Ryan fixed naming issue for Depot Provera BCL cases

• Reviewed Drax case numbers, which spiked from 12 to 228

• Discussed firefighting foam and hair relaxer cases

• 🔄 Case Updates and Classifications (12:41 - 17:43)

• Ryan classified cases as retainer or still (no retainer)

• Reviewed Shield cases in the dashboard

• Counted Illinois clergy abuse, juvenile hall, and Maryland cases

• Discussed Navy Federal cases

• 📈 Qualified Leads and Media Spend (17:43 - 24:20)

• Reviewed qualified leads and case reviews for various projects

• Discussed media spend and invoices for BLX

• Talked about Markowitz billing

• Ryan mentioned rolling Brandlytics services into Shield

• Discussed Lee's potential future role in Shield

Gist • The meeting analyzed case counts and updates on various projects, focusing on recent spikes in Drax case numbers and media spending issues.

Bullet Gist • 📊 Case Review and Analytics: Ryan and Lee reviewed various case counts, notably for the Atlantis Forest Cove apartments and Drax, which spiked significantly.

• 🔄 Case Updates and Classifications: Ryan clarified case classifications, addressing significant incidents like the Illinois clergy abuse cases.

• 📈 Qualified Leads and Media Spend: The team discussed qualified leads, media spending issues, and the integration of Brandlytics services.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-21 11:59:43

• The Operations and Analytics Review meeting for BLX Media Buying focused on a thorough analysis of case counts across various projects, notably the recent surge in Drax case numbers, which increased dramatically from 12 to 228. Ryan and Lee classified cases into retainer and non-retainer categories, reviewing significant incidents such as Illinois clergy abuse and cases related to firefighting foam and hair relaxers. They also examined qualified leads and addressed invoicing issues within BLX, including discussions on Markowitz billing. Opportunities to integrate Brandlytics services into Shield were explored, alongside Lee's potential future role in Shield. Action items included Ryan correcting naming issues and coordinating Lee's transition to Shield, while Lee was tasked with monitoring media spend and preparing for upcoming special projects.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-24 14:50:26

Title: BCL Next Steps Date: Thu Oct 24 2024 15:30:00 GMT-0400 (Eastern Daylight Time) Participants: andy@shield-legal.com, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, adrienne@brandlytics.io, c_2e765451188fb09489f5c7a99f8ee2792bf4f294ccff9638b6f3c336d866f50f@group.calendar.google.com, andy@brandlytics.io Transcript: See full transcript Audio: Listen to audio Duration: 20

Overview • In the BCL Next Steps Status Update Meeting, key topics addressed included Ryan's personal health update regarding his child's recovery from pneumonia, followed by improvements made to the website navigation for national practice areas and ongoing work to enhance mobile usability. Kelly provided an overview of SEO efforts, including the removal of crawlers from press releases and keyword analysis to boost rankings, while campaign updates highlighted successful launches, such as the organic minority farmer justice campaign and significant case acquisitions for Depro Provera and Drax Global. Ongoing projects were discussed, focusing on the development and launch of the ETO alongside paid campaigns, alongside the publication of multiple press releases. The team also noted unusually warm weather conditions impacting some members. Action items were assigned, including continued SEO work for Kelly, expedited multivariate testing by Latoya and Adrian, parallel ETO development by Cameron, and preparation for CRO experiments as a team.

Action Items • Kelly

• Continue working on SEO tasks, including removing crawlers and analyzing keyword rankings (13:16)

• Latoya and Adrian

• Pick up the pace on demoing multivariate testing for site conversion rate (14:48)

• Cameron

• Continue building and launching ETO in parallel with paid campaigns (15:41)

• Team

• Prepare for upcoming CRO experiments on contact us and homepage (19:13)

Shorthand Bullet • 🏥 Health Update (00:51 - 02:29)

• Ryan's oldest child had light pneumonia

• Child is recovering but still has a heavy, dry cough

• Child strained a rib due to coughing

• 🖥️ Website Navigation (02:30 - 03:16)

• Four-column navigation for national practice areas implemented on homepage

• Mobile version currently a long scrollable list

• Team working on potential taxonomy and sub-menus for mobile

• 🔍 SEO Work (03:17 - 05:40)

• Kelly working on routine SEO tasks

• Removing crawlers from press releases

• Analyzing keywords that dropped in ranking

• Creating dedicated pages for specific keywords (e.g., 'car accident lawyer')

• 📊 Campaign Updates (05:41 - 06:23)

• Launched minority farmer justice organic campaign

• Organic campaign for Depro Provera launched

• 16 cases received through organic efforts for Depro Provera

• 240 organic cases for Drax Global after criteria loosened

• 🚀 Ongoing Projects (06:24 - 10:05)

• ETO being built and launched alongside paid campaigns

• Depot Provera (birth control) campaign separate from Drax

• Team working on faster implementation of campaigns

• 12-15 press releases published on the site recently

• Organic campaigns launching in parallel with paid campaigns

• CRO (Conversion Rate Optimization) work upcoming

• 🌡️ Weather Discussion (19:19 - 20:06)

• Abnormally warm weather in Minnesota (80 degrees)

• Record-breaking temperatures (88-90 degrees) in Ryan's location

Gist • The meeting focused on updates regarding personal health, website improvements, SEO efforts, and project developments.

Bullet Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-10-24 14:50:26

• 💬 Personal Health Update: Ryan shared a personal update about his child's recovery from pneumonia.

• 🌐 Website Improvements: Enhancements to website navigation and mobile usability were discussed.

• 🔍 SEO Efforts: Kelly provided insights into SEO strategies to boost rankings.

• 🚀 Campaign Successes: The team celebrated successful campaign launches and case acquisitions.

• ⚙️ Action Items Assigned: Specific tasks were assigned for continued progress on various projects.

Short Summary • In the BCL Next Steps Status Update Meeting, Ryan shared a personal health update concerning his child's recovery from pneumonia, providing a human touch to the discussions. The team reviewed improvements to website navigation, particularly for national practice areas, and emphasized ongoing enhancements for mobile usability. Kelly outlined significant SEO efforts, including the strategic removal of crawlers from press releases and detailed keyword analysis aimed at improving search rankings. Campaign updates highlighted successful initiatives, such as the launch of the organic minority farmer justice campaign and significant case acquisitions for Depro Provera and Drax Global. Ongoing projects were discussed, with a focus on the development and launch of the ETO alongside various paid campaigns and the issuance of multiple press releases. The team also noted the impact of unusually warm weather on some members, while action items were assigned to ensure progress on SEO, multivariate testing, ETO development, and CRO experiments.

Ryan (ryan@themedialab.agency)
2024-11-12 19:24:37
File
Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-11-25 12:51:36

Title: TIPShield Dashboard Date: Mon Nov 25 2024 13:00:00 GMT-0500 (Eastern Standard Time) Participants: al@accountingdept.net, ryan@brandlytics.io, brian@accountingdept.net Transcript: See full transcript Audio: Listen to audio Duration: 39

Overview During the TIPShield Dashboard Review and Update meeting, Ryan provided Brian with access to the newly developed Shield Legal dashboard and guided him through its features, emphasizing the importance of clarity regarding costs and calculations. The meeting included an overview of the dashboard's interface, highlighting crucial pages and corresponding functionalities, as well as discussing preferred dashboard views. Financial discrepancies between Shield Legal and Tort Consulting data were addressed, particularly concerning operating expenses and the integration of Yardy numbers. The session concluded with updates to the daily operating expense table, followed by instructions on validating the updated data, which reinforced the need for consistency across different systems. Action items were assigned to Brian to validate specific dashboard numbers and inform relevant team members, while Ryan considered the creation of a combined financials dashboard for enhanced reporting.

Meeting Type Technical/Financial Dashboard Review and Update

Action Items Brian

Validate the updated numbers on page 55 of the new dashboard after 10 minutes (38:24)

Compare column K in the spreadsheet with the dashboard numbers (37:59)

Inform Al and Mark that Ryan and Brian finished everything in the dashboard (39:19)

Ryan

Consider building a combined financials dashboard (page 57) (25:15)

Shorthand Bullet 🖥️ Dashboard Access and Updates (00:25 - 14:35)

Ryan gave Brian access to the new Shield Legal dashboard

Brian added columns to a shared spreadsheet

Discussed confusion over additional costs and calculations

Ryan focused on getting Brian access to the correct dashboard

🔢 New Dashboard Overview (14:36 - 24:38)

Ryan guided Brian through the new dashboard interface

Explained various pages and their purposes (22, 23, 55, 56)

Discussed Mark's preferred dashboard views

Ryan suggested creating a combined financials dashboard (page 57)

📊 Financial Data and Calculations (24:39 - 30:15)

Reviewed differences between Shield Legal and Tort Consulting data

Discussed the confusion around operating expenses and Yardy numbers

Explained the need to match numbers between different systems

🔄 Data Updates and Validation (30:16 - 39:22)

Ryan updated the daily operating expense table in the database

Guided Brian on how to validate the updated numbers

Explained the data update process and time required

Discussed the importance of validating the updated numbers

Gist Ryan reviewed the new Shield Legal dashboard with Brian, emphasizing clarity in costs and calculations while addressing financial discrepancies.

Bullet Gist 🖥️ Dashboard Access and Updates: Ryan granted Brian access to the new Shield Legal dashboard and clarified the importance of accurate costs.

🔢 New Dashboard Overview: Ryan guided Brian through the dashboard interface, explaining the purpose of various pages and discussing preferred views.

📊 Financial Data and Calculations: The meeting addressed discrepancies between Shield Legal and Tort Consulting data, focusing on operating expenses.

🔄 Data Updates and Validation: Ryan updated the daily operating expense table and instructed Brian on validating updated numbers.

Short Summary

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-11-25 12:51:37

During the TIPShield Dashboard Review and Update meeting, Ryan provided Brian with access to the newly developed Shield Legal dashboard, guiding him through its features and emphasizing the importance of clarity regarding costs and calculations. The meeting covered an overview of the dashboard's interface, highlighting crucial pages and their functionalities, while also discussing preferred dashboard views, including suggestions for a combined financials dashboard. Financial discrepancies between Shield Legal and Tort Consulting data were addressed, particularly concerning operating expenses and the integration of Yardy numbers. The session concluded with updates to the daily operating expense table, instructions on validating the updated data, and action items for Brian to ensure consistency across different systems.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-11-27 14:09:34

Title: Seeding tables Ryan James Date: Wed Nov 27 2024 14:00:00 GMT-0500 (Eastern Standard Time) Participants: ryan@brandlytics.io, jturner@shield-legal.com, ryan@themedialab.agency Transcript: See full transcript Audio: Listen to audio Duration: 69

Overview The Technical Planning and Strategy Meeting focused on several key areas involving team dynamics, data management, and financial reporting. James provided updates on individual meetings with team members to clarify roles, while Ryan praised James for his leadership of the analytics team. The participants discussed advancements in BigQuery and ongoing projects, including Dustin’s work on PostgreSQL and the importance of centralizing data within BigQuery. Financial matters were addressed through a review of spreadsheets and expense categorization, alongside discussions on SQL query development for data insertion in BigQuery. The meeting also covered plans for creating a financial log table, aligning database structures with profit and loss documents, and establishing a data pipeline for effective reporting. Action items were assigned to team members for implementing these strategies moving forward, emphasizing the collaborative approach to improving data integration and financial logging.

Meeting Type Technical Planning and Strategy Meeting

Action Items James Turner

Add occupancy expenses to the BigQuery table (56:14)

Dig around with the DevOps insert query for LR statuses (01:05:59)

Work on building the master log and DBT models (01:00:01)

Ryan Vaspra

Confirm with Brian the components of aggregated payroll expenses (49:16)

Save the insert query in shared queries (57:40)

Unassigned

Validate the financial log every 24 hours (52:08)

Decide on the timing for Tony's commission calculation (54:33)

Shorthand Bullet 🔧 Project Updates and Team Dynamics (02:05 - 13:29)

James discussing one-on-ones with his team to understand responsibilities

Ryan appreciating James' role as team lead director of the young analytics team

Discussion on Google's approach to partnerships and product development

Conversation about BigQuery and its evolving capabilities

📊 Data Management and Integration (13:45 - 25:13)

Dustin's progress in transferring data to PostgreSQL

Discussion on centralizing data in BigQuery

Explanation of Law Ruler data structure and views

Ryan sharing SQL query for creating lead data

💼 Financial Data and Reporting (25:13 - 34:33)

Review of financial spreadsheet and chart of accounts

Discussion on aggregated payroll expenses and bonuses

Explanation of personnel expenses categorization

🖥️ BigQuery Setup and SQL Queries (34:35 - 42:03)

James and Ryan working on setting up data in BigQuery

Creating SQL queries for inserting data into BigQuery tables

Discussion on using ChatGPT for SQL query generation

📈 Data Modeling and Financial Logging (42:04 - 47:44)

Planning for financial log table creation

Discussion on case type level pricing and revenue modeling

Explanation of bonus schedule model and its integration

🏗️ Database Structure and Query Scheduling (47:45 - 57:05)

Adding occupancy expenses to the BigQuery table

Discussion on aligning BigQuery columns with P&L spreadsheet

Planning for scheduled queries and data updates

🔄 Data Pipeline and Future Development (57:05 - 01:08:47)

Explanation of DevOps and application operations

Discussion on LR case types cloud function and data pipeline

Planning for building master raw data log and DBT models

Review of project structure in BigQuery

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-11-27 14:09:34

The meeting aimed to discuss project responsibilities and strategies for the seeding tables project, focusing on team dynamics and data management.

Bullet Gist 💼 Project Focus: The meeting centered on the ongoing seeding tables project and team dynamics.

📊 Data Management: Key strategies included transitioning data to PostgreSQL and centralizing it in BigQuery.

💰 Financial Planning: Financial considerations included expense management and payroll structure.

🛠️ SQL Review: The team explored SQL query structures and possible ChatGPT integration.

✅ Action Items: Action items were assigned for expense categorization and connecting PostgreSQL to BigQuery.

Short Summary Led by James and Ryan, the meeting concentrated on the ongoing seeding tables project, emphasizing the importance of team dynamics and clarifying individual responsibilities. James shared plans for one-on-one discussions with team members to ensure clarity in roles, while Ryan commended the team's alignment and contributions. Dustin provided updates on data management strategies, particularly regarding the transition of data to PostgreSQL and its centralization in BigQuery. Financial aspects were also discussed, including expense management and the structure of monthly payroll expenses, with Melissa tasked to implement monthly placeholders. The team reviewed SQL query structures and considered using ChatGPT for query generation and validation. The meeting concluded with discussions on categorizing expenses, scheduling queries, and creating a master raw financial log in BigQuery, with action items assigned for various tasks.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-12-04 15:49:47

Title: New status Date: Wed Dec 04 2024 14:20:00 GMT-0500 (Eastern Standard Time) Participants: ryan@brandlytics.io, jturner@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 145

Overview The Technical Discussion and Training meeting focused on several key areas regarding process improvements and updates. Initially, the team discussed the ASA Transfer process, emphasizing its implications when contact with a customer is lost and the billable nature of this transfer, with James tasked to edit GitHub code related to it. Further discussions included updates from Ryan on data engineering, where he is refining metrics and cheat sheets while awaiting confirmation from David Kessler on ASA Transfer specifics. The meeting also highlighted new features in the Monday Elevate platform, particularly those inspired by video game design for enhanced CRM functionality. In addition, Ryan provided updates on database enhancements, detailing how metrics were refined and the allocation of operating expenses. A significant portion was dedicated to AI and SQL integration, where Ryan demonstrated using ChatGPT for generating SQL queries, culminating in the creation of a new performance metric, Gross Profit Margin COGS. Finally, a thorough walkthrough on developing dashboards and reports was provided, covering aspects such as BigQuery integration and the addition of new performance metrics like the conversion rate. Key action items were assigned to team members to ensure follow-through on the discussed updates and enhancements.

Meeting Type Technical Discussion and Training

Action Items James Turner

Edit GitHub code to include ASA Transfer (05:05)

Confirm with David Kessler if ASA Transfer is billable (06:15)

Ryan Vaspra

Update metrics and cheat sheets for reporting (10:00)

Refine the formula for Gross Profit Margin COGS (25:59)

Create a new dashboard for Flatirons (02:10:39)

Add conversion rate column to performance scorecards (02:22:58)

Shorthand Bullet 🔧 ASA Transfer Discussion (00:52 - 05:41)

ASA Transfer occurs when contact is lost with a customer

It happens between steps 6 and 7 in the process

ASA Transfer is billable and commissionable

Secondary interview ASA added to the process

📊 Data Engineering and Reporting (05:41 - 09:52)

James to edit GitHub code to include ASA Transfer

Ryan working on updating metrics and cheat sheets

Confirmation needed from David Kessler on ASA Transfer details

💻 Monday Elevate Discussion (07:14 - 08:33)

New features including CRM announced

Presentation style resembles a video game interface

Ryan suggests business software could learn from video game design

🛠️ Database and Reporting Updates (09:54 - 29:50)

Ryan spent 4 hours updating metrics into a cheat sheet

Net revenue removed to avoid skewing numbers

Discussion on how operating expenses are allocated in the financial rows

Explanation of external vs. internal cost allocation

🤖 AI and SQL Integration (29:48 - 38:56)

Ryan demonstrates use of ChatGPT for SQL queries

New measure 'Gross Profit Margin COGS' created using AI assistance

Discussion on formula refinement and data presentation

📈 Dashboard and Report Development (38:56 - 02:23:10)

Detailed walkthrough of creating and customizing dashboards

Instructions on cloning and modifying reports for different clients

Explanation of BigQuery integration and custom query creation

Discussion on scorecard creation and visual enhancements

Conversion rate calculation added as a new performance metric

Gist

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2024-12-04 15:49:47

The meeting focused on process improvements, updates on the ASA Transfer process, and integration of AI and SQL for enhanced performance metrics.

Bullet Gist 🚀 ASA Transfer Process: The implications of customer contact loss in the ASA Transfer process were discussed, with code edits assigned to James.

📊 Data Engineering Updates: Ryan refined metrics and cheat sheets, pending confirmation from David Kessler regarding ASA specifics.

🎮 New Features in CRM: Features inspired by video game design were introduced in the Monday Elevate platform to enhance CRM functionality.

🤖 AI and SQL Integration: Ryan demonstrated the use of ChatGPT for SQL queries, resulting in a new performance metric, Gross Profit Margin COGS.

📈 Dashboard Development: A comprehensive walkthrough of dashboard and report development was provided, focusing on BigQuery integration and new metrics.

Short Summary The Technical Discussion and Training meeting addressed key process improvements, starting with the ASA Transfer process and its implications when customer contact is lost. James was assigned to edit the relevant GitHub code. Ryan provided updates on data engineering, refining metrics and cheat sheets while awaiting David Kessler's confirmation on ASA Transfer specifics. The discussion also covered new features in the Monday Elevate platform, inspired by video game design, aiming to enhance CRM functionality. Ryan detailed database enhancements, including refined metrics and operating expense allocation. A significant focus was on AI and SQL integration, where Ryan showcased the use of ChatGPT for generating SQL queries, leading to a new performance metric, Gross Profit Margin COGS. The meeting concluded with a walkthrough on developing dashboards and reports, emphasizing BigQuery integration and new performance metrics like conversion rate, with key action items assigned for follow-through.

Ryan (ryan@themedialab.agency)
2024-12-18 13:35:49

• NAME-CHEAP.COM • FACEBK • ADOBE • Google ADS1023546037

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2025-01-09 15:51:42

Title: BCL Next Steps Date: Thu Jan 09 2025 16:00:00 GMT-0500 (Eastern Standard Time) Participants: andy@brandlytics.io, ryan@brandlytics.io, jon@bencrump.com, uzoma@bencrump.com, andy@shield-legal.com Transcript: See full transcript Audio: Listen to audio Duration: 51

Overview The BCL Next Steps meeting comprised a blend of personal updates and strategic discussions, starting with Ryan and Uzoma exchanging New Year greetings and sharing personal anecdotes. The focus then shifted to professional matters, highlighting the introduction of a new SEO project manager and ongoing initiatives such as developing a large language model analytics tool for mass torts. The team reviewed key insights from Ben Crump's 2024 Search Marketing Annual Report, noting enhancements in SEO efforts and case volumes across top-performing practice areas. Discussions on social media performance underscored the importance of mobile optimization for 2025 and considered adding a merchandise store to the website. Strategic partnerships were briefly addressed, particularly the relationship with Pintas Mullins and plans to manage their domain independently by the year's end. The meeting concluded with technical discussions around setting up a subdomain for the merchandise store, and several action items were assigned to both Ryan and Uzoma to drive progress in these areas.

Meeting Type Status Update and Strategy Discussion

Action Items Ryan Vaspra

Complete the annual report by adding social data and leads from Call Tracking Metrics (31:25)

Work on mobile optimization for the website (22:15)

Improve meta descriptions for top 10 pages (24:26)

Prepare for potential domain transfer discussion with Pintas Mullins (39:57)

Uzoma Obasi

Export social media engagement data for further analysis (32:40)

Contact William Pintas about setting up a subdomain for the merchandise store (48:18)

Work on removing the firm from Clear IT management relationship by year-end (42:53)

Shorthand Bullet 🎉 New Year Updates and Personal Life (00:26 - 07:48)

Ryan and Uzoma exchanged New Year greetings

Ryan shared about meeting a new lady he likes

Discussed personal relationships and family dynamics

📊 SEO and Analytics Updates (09:11 - 31:25)

Discussed new SEO project manager and team structure

Mentioned development of a mass torts prediction large language model analytics research tool

Reviewed Ben Crump's 2024 Search Marketing Annual Report

Highlighted improvements in case volumes and SEO efforts

Discussed top performing practice areas and geographic targeting

📱 Social Media and Website Optimization (32:40 - 43:05)

Analyzed social media performance and its impact on case generation

Discussed mobile optimization as a priority for 2025

Reviewed top performing pages and keywords

Uzoma inquired about adding a merchandise store to the website

🤝 Strategic Partnerships and IT Management (43:06 - 48:42)

Discussed relationship with Pintas Mullins and domain management

Uzoma mentioned plans to remove from Clear IT management by year-end

Ryan offered support for any internal push needed

🔧 Technical Setup and Communication (48:46 - 50:48)

Discussed setting up a subdomain for the merchandise store

Ryan provided William Pintas's contact information for subdomain setup

Gist The meeting focused on personal updates and strategic discussions, including SEO initiatives and new project management roles.

Bullet Gist 🎉 New Year Greetings: Ryan and Uzoma kicked off the meeting with warm New Year wishes and personal anecdotes.

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2025-01-09 15:51:42

📈 SEO Initiatives: The introduction of a new SEO project manager and ongoing SEO projects were key discussion points.

💻 Insights from Reports: Key insights from the 2024 Search Marketing Annual Report highlighted improvements in SEO and case volumes.

📱 Social Media Strategy: Mobile optimization for 2025 was emphasized, along with the idea of adding a merchandise store.

🤝 Strategic Partnerships: Plans to manage the Pintas Mullins domain independently were discussed, focusing on strategic partnerships.

Short Summary The BCL Next Steps meeting began with personal updates as Ryan and Uzoma exchanged New Year greetings and shared anecdotes. The conversation then transitioned to professional topics, introducing a new SEO project manager and discussing the development of a large language model analytics tool specifically for mass tort cases. Insights from Ben Crump's 2024 Search Marketing Annual Report were reviewed, noting enhancements in SEO efforts and increased case volumes in high-performing practice areas. Social media performance was also discussed, emphasizing the need for mobile optimization in 2025 and the potential addition of a merchandise store on the website. The meeting briefly touched on strategic partnerships, particularly the collaboration with Pintas Mullins, with plans to independently manage their domain by the end of the year. Technical discussions included setting up a subdomain for the merchandise store, with action items assigned to both Ryan and Uzoma to ensure progress in these areas.

Ryan (ryan@themedialab.agency)
2025-01-10 13:52:08
File
Ryan (ryan@themedialab.agency)
2025-01-12 18:27:58

gross media spend dicelllo (daily spend + agency fee + media commission) call cost total expense dicello = (daily spend + agency fee + media commissio + call cost TC - Dicello customer

Ryan (ryan@themedialab.agency)
2025-01-28 15:31:22

PVS Revenue Spent Not Paid not summing on Looker E

Fireflies.ai (https://themedialaboratory.slack.com/services/B06P6RDQ43Y)
2025-01-31 13:11:25

💡 Focus on Improvement: James highlighted Dustin's strengths and areas needing improvement.

📊 Strategic Planning: Ryan emphasized a cautious approach regarding BI system enhancements.

🤖 AI Implementation Ideas: Participants explored ways to boost efficiency through AI.

📝 Action Items Assigned: Coaching for Dustin and discussions on lead conversions were planned.

Short Summary Team members engaged in a collaborative discussion regarding performance and challenges in projects, with James highlighting Dustin's architectural expertise while noting areas for improvement in data engineering. Zeke's difficulties with data framing were also addressed, and there was a shared recognition of the complexities involved in enriching customer data. Cameron pointed out staffing challenges as the company grows, while Ryan suggested a strategic wait on BI system enhancements before pushing for further improvements. Ideas for AI implementation were explored, particularly in enhancing efficiency in lead processing, spam detection, and lead qualification. The meeting maintained a team-oriented atmosphere with personal updates and assigned action items, including ongoing coaching for Dustin and preparation for discussions on lead conversions with Cameron.

Ryan (ryan@themedialab.agency)
2025-02-25 16:09:42

Check-in Rituals • Fully Present: Electronics off • One-word Opener • Confidentiality Reminder: Any near misses? • Clear the Air: Speak or let it go • Ice Breaker: A great question • Significant and Important Updates (3 – 5 minutes each) • Parking Lot: Populate EQ and IQ topics

Ryan (ryan@themedialab.agency)
2025-03-18 13:40:40
  1. Confirmed no sign ups
  2. Confirm leads in LP from Feb 20th
  3. Update spend in SL Dashboard
Ryan (ryan@themedialab.agency)
2025-03-25 13:56:36
My Sprint
Ryan (ryan@themedialab.agency)
2025-03-25 19:54:09
Untitled
Ryan (ryan@themedialab.agency)
2025-03-25 20:31:14
Untitled
Ryan (ryan@themedialab.agency)
2025-03-27 03:45:46
Wildfires Research
Ryan (ryan@themedialab.agency)
2025-03-27 04:47:47
Google Cloud Development
Ryan (ryan@themedialab.agency)
2025-03-27 05:13:52
Ben Crump Account Management
Ryan (ryan@themedialab.agency)
2025-03-27 10:45:29
Miller BVS
Ryan (ryan@themedialab.agency)
2025-03-27 23:16:04
Internal Strategy - RKV
Ryan (ryan@themedialab.agency)
2025-03-28 05:58:41
Dicello Revenue
Ryan (ryan@themedialab.agency)
2025-04-11 09:29:59
Untitled
Ryan (ryan@themedialab.agency)
2025-04-30 13:13:52
Untitled
Ryan (ryan@themedialab.agency)
2025-05-14 10:35:39
Untitled
Ryan (ryan@themedialab.agency)
2025-05-14 19:37:51

Call Center AI Salesbots Pilot for Marc

Ryan (ryan@themedialab.agency)
2025-05-15 10:49:53
Untitled
Ryan (ryan@themedialab.agency)
2025-05-15 11:31:29
Untitled
Ryan (ryan@themedialab.agency)
2025-05-16 01:56:52
Untitled
Ryan (ryan@themedialab.agency)
2025-05-16 03:46:32
Untitled
Ryan (ryan@themedialab.agency)
2025-05-16 07:39:09
Illinois Juv Hall - BG
Ryan (ryan@themedialab.agency)
2025-05-16 18:07:16
Untitled
Ryan (ryan@themedialab.agency)
2025-05-18 16:52:54
Untitled
Ryan (ryan@themedialab.agency)
2025-05-19 00:24:07
1. CA Juv Hall Abuse
Ryan (ryan@themedialab.agency)
2025-05-19 06:48:18
Untitled
Ryan (ryan@themedialab.agency)
2025-05-20 03:37:58
Untitled
Ryan (ryan@themedialab.agency)
2025-05-22 19:53:09
Untitled
Ryan (ryan@themedialab.agency)
2025-05-23 00:41:08
Untitled
Ryan (ryan@themedialab.agency)
2025-05-23 22:37:39
Canvas
Ryan (ryan@themedialab.agency)
2025-05-24 20:37:00
Untitled
Ryan (ryan@themedialab.agency)
2025-05-28 03:32:08
Untitled
Ryan (ryan@themedialab.agency)
2025-05-28 23:41:42
Untitled
Ryan (ryan@themedialab.agency)
2025-05-29 05:58:33
Type something
Ryan (ryan@themedialab.agency)
2025-05-29 18:38:44
Untitled
Ryan (ryan@themedialab.agency)
2025-06-19 18:39:54
File
Ryan (ryan@themedialab.agency)
2025-07-25 12:42:00

1) Transcription Chat Bot: https://github.com/shield-legal/transcript-chatbot 2) Mass Employee New Legal Compliance Agent: https://github.com/shield-legal/bulk-legal-new-employees-calls-audit 3) Big Data Agent for Cleaning Address Contact tables: https://github.com/shield-legal/database-agents 4) Tort Finder & Legal Analysis: https://github.com/shield-legal/new-tort-opportunities 5) Local LLM Server: https://github.com/shield-legal/ollama-local-llm 6) Updates to Sanic for UI for transcription app and the tort finder app: https://github.com/shield-legal/internal-tools-site/tree/tort-control-panel-new-feature

Ryan (ryan@themedialab.agency)
2025-08-07 13:24:52

Just get them to run the migration scripts so we can get the newtortopportunities table live in production so we can merge the branch I have with the main sanic application and so we can switch out the local test database information. We will clone the container once we start growing. Dustin is responsible for this and Tyson can handle user administration and adding people.

Ryan (ryan@themedialab.agency)
2025-08-07 13:29:16

@Dustin Surwill, meeting with Marc & Cameron on Tuesday with Chris and James, Joe and we need that newtortopportunities for running migration scripts for the Internal Tools. Can you have that ready by EOD Monday, for our Tuesday afternoon meeting.

And @Tyson Green, I need ryan@shield-legal.com added as a User to the Internal Tools.

Ryan (ryan@themedialab.agency)
2025-08-11 11:39:43

Good morning! @Dustin Surwill, what latest on getting the AI data migration done for James & Chris K.? And any update on my user access?

Ryan (ryan@themedialab.agency)
2025-08-13 13:25:05
Untitled
Ryan (ryan@themedialab.agency)
2025-08-13 14:57:36

• @CC Kitanovski ◦ Call Center GCP ◦ ~User Access to ShieldLegal.dev and Predator & MediLens (Tortelligence)~ ◦ MediLens usage research validation ◦ Forever Chemicals ◦ MediLens usage research validation ◦ Predator Earlier than News Abuse detection sources

Ryan (ryan@themedialab.agency)
2025-08-18 13:32:48

• @CC Kitanovski ◦ Call Center GCP ◦ ~User Access to ShieldLegal.dev and Predator & MediLens (Tortelligence)~ ◦ MediLens usage research validation ◦ Forever Chemicals ◦ Predator MediLens usage research validation ◦ Predator Earlier than News Abuse detection sources

Ryan (ryan@themedialab.agency)
2025-08-18 14:04:41

• @CC Kitanovski ◦ Call Center GCP ◦ ~User Access to ShieldLegal.dev and Predator & MediLens (Tortelligence)~ ◦ MediLens usage research validation ◦ Forever Chemicals ◦ MediLens usage research validation ◦ Predator Earlier than News Abuse detection sources

Ryan (ryan@themedialab.agency)
2025-08-19 08:51:17

• HR ◦ Joshue replacement

Ryan (ryan@themedialab.agency)
2025-08-19 17:52:21

SL BI Financials and Operations

• Leadspedia sold leads + LawRuler Retainers for contract buyers + referral leads + media spend + mb commission + sales commission + agency fee + daily operation expense + call costs base table • Media Buyers Commissions • Monthly Expenses • Cameron Adjustments Portal and Function • Yan Performance Dashboards • Update and migrate to BigQuery Order Financials and dependant DBT models for Leads and Contracts SUMing • Financial Details Schema Transform • UPSERTS into old Financial Details of new Financial Details to keep historical data

Ryan (ryan@themedialab.agency)
2025-08-19 18:25:16

Call Center Problems • ~Reconciliation Reconvened~ • Malissa Pacing Report Dashboard (Google sheet) • NEW SYSTEM FOR CLIENT DELIVERY, REPORTING should be through Yesterday ONLY to avoid intraday for Brittany's team • ~Prices on SL Call Costs for Cam~

Ryan (ryan@themedialab.agency)
2025-08-19 18:33:03

Call Center Problems • Reconciliation Reconvened • Malissa Pacing Report Dashboard (Google sheet) • Billable SL Leads from TIP the Q&A so we can create a single source for Monday reports. • NEW SYSTEM FOR CLIENT DELIVERY, REPORTING should be through Yesterday ONLY to avoid intraday.

Ryan (ryan@themedialab.agency)
2025-08-19 18:46:25

Development Owner • Keep Code in Lab from Chris K. with Fonseca

Ryan (ryan@themedialab.agency)
2025-08-19 18:46:30

Call Center Problems • Reconciliation Reconvened • Malissa Pacing Report Dashboard (Google sheet) • Billable SL Leads from TIP the Q&A so we can create a single source for Monday reports. • NEW SYSTEM FOR CLIENT DELIVERY, REPORTING should be through Yesterday ONLY to avoid intraday

Ryan (ryan@themedialab.agency)
2025-08-19 18:46:37

Call Center Problems • Reconciliation Reconvened • Malissa Pacing Report Dashboard (Google sheet) • Billable SL Leads from TIP the Q&A so we can create a single source for Monday reports. • NEW SYSTEM FOR CLIENT DELIVERY, REPORTING should be through Yesterday ONLY to avoid intraday • Prices on SL Call Costs for Cam

Ryan (ryan@themedialab.agency)
2025-08-20 11:30:34

Call Center Problems • Reconciliation Reconvened • Malissa Pacing Report Dashboard (Google sheet) • NEW SYSTEM FOR CLIENT DELIVERY, REPORTING should be through Yesterday ONLY to avoid intraday for Brittany's team • ~Prices on SL Call Costs for Cam~

Ryan (ryan@themedialab.agency)
2025-08-21 13:04:31

SL BI Financials and Operations

• Leadspedia sold leads + LawRuler Retainers for contract buyers + referral leads + media spend + mb commission + sales commission + agency fee + daily operation expense + call costs base table • Financial Details Schema Transform • Profit by Month • Media Buyers Commissions • Yan Performance Dashboards • Monthly Expenses • Order Financials and dependant DBT models for Leads and Contracts SUMing • UPSERTS into old Financial Details of new Financial Details to keep historical data

Ryan (ryan@themedialab.agency)
2025-08-21 17:05:13

SL BI Financials and Operations

• Leadspedia sold leads + LawRuler Retainers for contract buyers + referral leads + media spend + mb commission + sales commission + agency fee + daily operation expense + call costs base table • Media Buyers Commissions • Monthly Expenses • Cameron Adjustments Portal and Function • Yan Performance Dashboards • Update and migrate to BigQuery Order Financials and dependant DBT models for Leads and Contracts SUMing • Financial Details Schema Transform • UPSERTS into old Financial Details of new Financial Details to keep historical data

Ryan (ryan@themedialab.agency)
2025-08-22 11:22:13

Call Center Problems • ~Reconciliation Reconvened~ • Malissa Pacing Report Dashboard (Google sheet) • NEW SYSTEM FOR CLIENT DELIVERY, REPORTING should be through Yesterday ONLY to avoid intraday for Brittany's team • ~Prices on SL Call Costs for Cam~

Ryan (ryan@themedialab.agency)
2025-08-22 15:33:21

mormon victims hair bladder sacramento riverside santa clara new jersey

Ryan (ryan@themedialab.agency)
2025-08-26 08:48:02
Untitled
Ryan (ryan@themedialab.agency)
2025-08-28 16:23:39
Untitled
Ryan (ryan@themedialab.agency)
2025-08-29 12:15:35
  1. Help CR get his Flatirons answers
  2. Help Rose learn how to enter expenses
  3. Help Malissa figure out Dupe for ACTS San Beranardino / JDC Abuse
  4. Help Marc get his leads into Page 22 to 25
  5. Get Brian to fix Status Rates, if not completed by end of week next week, I'll haver James do it.
  6. Portfolio Dashboard template for TC?
Ryan (ryan@themedialab.agency)
2025-08-29 12:27:46
  1. Help CR get his Flatirons answers
  2. Help Rose learn how to enter expenses
  3. Help Malissa figure out Dupe for ACTS San Beranardino / JDC Abuse
  4. Help Marc get his leads into Page 22 to 25
  5. Get Brian to fix Status Rates, if not completed by end of week next week, I'll haver James do it.
  6. Portfolio Dashboard template for TC?