Clients rely on research information to stay ahead of the game. Wonder’s recurring and monitoring services are an excellent fit for this partnership level. These services benefit our clients and Wonder by increasing retention and creating habituation.

• Recurring Projects serve as a continuous revenue source for Wonder and a means for lasting collaborations.
• These collaborations increase engagement with our product.
• Increased engagement leads to habituation and, subsequently, more referrals for new clients due to word-of-mouth.

Research Managers will screen projects for potential cadenced updates, recurrences, and event triggers we can monitor to recommend research that keeps our clients at the top of their game.

Associated Resources:

1. Cadenced Tigger Frequency Reference Sheet and Tracker
2. 30-day Google Calendar (Aerial View) -
3. How to Create Google Alerts using keywords for trigger event monitoring.

Process for Identifying and Communicating Potential Recurring and Monitored Projects

1. Screening New Projects - The RM will read the chat submission notes and chats to determine the potential for continuing recurrence or monitoring.

   1. Cadenced-based - components of the project that are best updated on a cadenced schedule (weekly, monthly, quarterly, semiannual, annual, etc.).
   2. Trigger or event-based - components that are to be updated on an on-demand basis based on important happenings that affect the information already presented (significant changes in stock price, funding rounds, changes in regulations, lawsuits, changes in leadership, etc.).

2. Communicating Potential Recurring or Monitoring Components - the RM will communicate the following, based on pre-search and data availability, in the initial project post in the #projects-in-process channel:

3. The format for posting is in our Cheat Sheet, so it is easily accessible.

   1. Potential Recurring - Yes/No - If yes:
      1. Component #1 - recommended cadence /trigger event
      2. Component #2 - recommended cadence and so on
      3. If you are using a trigger event, include what you are monitoring and a short description of what could be included in the update for the client.
   2. Example:
      1. Update competitors’ financial metrics - quarterly
      2. Update new competitor product offerings - semiannually.
      3. Update with any new key players - trigger event - every time we are alerted by news articles or press releases that a new competitor enters the market.
   3. Tag Ganiyu in the project post so he can record the recurring project on the tracker.

   <aside> 💡 Example Posting:

   Wonder Proposal Launch- Toha- Bob Wonder

   Strategy

   Proposal

   ZD Thread

   Quire

   Use Case: Channel Insights

   Status Update: Proposal sent to the client, waiting on a reply

   Potential Recurring- Yes or No

   Cadence OR Trigger: quarterly, monthly, trigger event, etc. (Select either cadence or trigger for this).

   </aside>

   1. NOTE: We are currently working on developing mechanisms to create and centralize alerts across a team-wide function. For now, each RM can create a Google Alert that will be triggered and sent to their askwonder email address using keywords related to what we are monitoring for the client.
      1. Before recommending a monitored trigger event, be sure you can create a suitable alert for the triggering event.
         1. Are there enough sources or news sites that would likely report that information?
         2. The keywords for your monitor are accurate and clear, and the wording is most likely to yield the expected alerts (e.g., stock price vs. price).
         3. If you cannot set an adequate monitor, you can also recommend a news round-up on a recommended cadence as an alternative.

Process for creating the cadenced or monitored recurrence.

1. Creating the cadenced recurrence: The client will reply to the CSM in one of several ways: The CSM will post the client’s reply in the thread.

   1. They are interested and ready to move forward with scoping -
      1. Create a proposal for the recurring or monitored components and flag Jonah with the scope for thoroughly researching the cadenced components.
         1. If we have clearance to email the recurrence
         2. This gives us a maximum parameter for launching the recurrence.
   2. If the client is interested and open to iteration and/or has questions or comments, proceed as usual, continuing to iterate in the project thread or via email, if requested, until we are ready for the proposal.
   3. They are not interested in the cadenced or triggered action - no further action is required.
   4. If the client has expressed interest or we have prepared a proposal, tag Ganiyu in the project thread for monitoring and tracking.
   5. Update the quire card, including the approval date and recurrent launch date.
   6. Update the monthly calendar for an aerial view of all recurring project launch dates.

2. Creating the trigger monitor - (WIP/in production) - Similar to approving cadenced monitors, the client will respond in the following ways:

   1. They are interested and ready to move forward with a plan.

      1. Create the proposal as if we had enough information to run the entire scope for that trigger event. Prepare alternatives should information specific to that trigger not be enough.

      <aside> 💡 Example: We may only have a short, direct update to provide, but the trigger event affects another part of the project, or the update leads to additional research we could recommend to fill in the gap or add to the scope, as determined during your evaluation of the event.

      </aside>

   2. The RM can set their own Google Alerts to monitor the web for triggered occurrences based on keywords. When triggered, these alerts will send emails to the RM’s askwonder email address with applicable web content.

      1. The RM monitors the alerts and kicks off or flags the CSM in the project thread when we have updates.
      2. Present the most efficient recommendation for providing value. This includes recommending, drafting a proposal, or kicking off research based on how the client approved the parameters.
         1. Run ROS1-hour vetting job.
         2. A simple update to the original deliverable and an email explaining the update to the client.
         3. Full 3-hour increment
         4. Note: If the update is simple and lasts fewer than 10 minutes (e.g., a quick change in revenue, etc.), the RM will make any updates directly to the deliverable and email or email the client directly with CSM on CC.
         5. Flag CSM with any recommendations for any additional research surrounding the update. If instructed by leads or CSM, the RM may email the client any recommendations directly or create a proposal if needed.
         6. When using trigger events: Update the quire card with the proposed/approved trigger event and preapproved scoping parameters.
            1. Update the card with each recurrence and launch date to ensure we regularly monitor the trigger events.

3. Best Practice Guidelines for creating proposals for recurrences and monitoring.

   1. Historically, we have always kicked off the full scope of the recurring project because the only way to know how much information was available was to start the research.
   2. We now have numerous tools to quickly determine if enough information is available to run the full scope, recommend alternative courses of action, prioritize other components, or run at a partial scope.
      1. Multiple single and custom AI agents. Check out the Roster, ***linked here.***
      2. ROS with agent report to send to verification or vetting—then directly to the client as indicated. Peek Under the Tent—The vetting job (coming soon) will allow us to create a one-hour project for instances where we do not need a full three-hour increment.
   3. The purpose of sending the full scope of the recurrence in the proposal is to have blanket approval for those hours. However, we now partner with our clients on how to best use or not use those hours. The research manager is the key person to effectively set these monitors up for success.
   4. Keep in mind that when working with triggered events, the OG RM is the person who will set up alerts and recommend or kick off research. However, detailed documentation of the recommended research paths and any proposals is needed in case we have approval with a time-sensitive ETA, and someone else must kick-off.