🤝

v3 of MWW Customer Development Framework

💡

This playbook guides MWW’s user research, sales and feedback/reviews gathering exercises and outreaches, towards learning more about our market and ultimately achieving product-market fit, adoption, and growth.

1. Context

The goal of this ongoing set of initiatives is to build a company with the product we’ve built by validating it actually meets the need of the market and they’re willing to pay for it. Over the past months, we’ve been learning with the first version of our product, after this learning process, we were able to identify the first bet towards defining a strong value proposition for Meetwithwallet, something which meets the need of the market we are looking at serving. The previous research before this can be found at:

We have been able to build out a solution out of the learning from the previous research, and we are going back to learn if this is actually a problem that users have, towards achieving Product-Market Fit. We will be deploying a proven framework for achieving this which is the Lean Product Methodology: Customer Development Framework.

2. Objective

In this phase of work, we are looking at attaining clarity in Customer Discovery, Customer Validation, Customer Creation, Achieving product market fit and Growth. We will distill these different phases of customer development into Initiatives and iteratively following through.

3. Introduction

Meetwithwallet is a scheduling tool designed to simplify and streamline meeting coordination for both individuals and teams. Whether you're organizing 1-1 meetings or managing larger group discussions, Meetwithwallet ensures a seamless experience, eliminating the UX flaws in traditional group and 1-1 meeting scheduling tools.

For teams looking to enhance collaboration and optimize time management, Meetwithwallet is looking to be an answer and a solution to the inefficiencies and challenges they experience in their process of scheduling meetings, enabling smarter coordination without the hassle. With built-in privacy and scheduling flexibility, it ensures that every meeting time is picked with ease and clarity, reducing the back-and-forth of organizing meetings.

We believe that Meetwithwallet is the definitive tool for any team that wants to take control of their time and elevate their meeting efficiency to the next level.

4. Our Target Audience

4.1 Personas

💡

Captured in these section are some hypothesis and already identified pain points we want to validate about each of our target audience.

4.1.1 Cross-org Workers (Individuals Working Across Multiple Organizations)

5. Research/Outreach Team

Patrick

Adedamola

GPee

6. User Contact

6.1 First Contact Strategies

Our initial outreach aims to engage these target audiences, understand their scheduling challenges, and introduce MWW as a potential solution.

Channels for Outreach:

Social Media Platforms: Twitter, LinkedIn, and relevant web3 Discords or forums.

Direct Messaging: Personalised messages through Discord, Twitter, and Telegram.

Community Engagements: Participation in DAO meetings, web3 conferences, and online webinars. This may work for ongoing feedback collation and not our current run.

Sample First Contact Messages:

Cross-org Workers:

“Hi [NAME], as an active contributor to [ORG NAME], how do you currently manage meeting schedules within your team or with your colleague? We’re developing MeetWithWallet, a tool designed to simplify scheduling in the web3 space. Would love to hear about your experiences and see if we can help make coordination easier for you.”

Hi [NAME], As an active contributor to [ORG NAME], I’m curious—how do you currently handle scheduling group meetings within your team or with colleagues? We’re developing MeetWithWallet, a tool designed to simplify scheduling, especially for distributed teams in the web3 space. We’d love to hear more about your experiences and challenges with scheduling group meetings. Your insights would help us create a solution that truly works for you. Would you be open to a quick chat to share your thoughts? Looking forward to hearing from you!

6.2 Contact List

💡

This is a list of people we’re reaching out to for the Interview.

7. Customer Development Initiatives

Initiative 1: Customer Discovery

💡

We will be using the JTBD User Interview technique to learn about the challenges and pain points around meeting scheduling for these people we reach out to. The goal here is to learn and only suggest a solution to them when it seems what we have can meet their needs.

User Interview Guide: Group Scheduling

Cross-org Workers Interview Guide

Data Collection and Synthesis

We’ll log all interactions and outreaches here:

Research Summary and Next Steps

After the research and synthesizing all feedbacks into insights, we should be able to have a document containing the key next steps to take. This could be:

Preparing an offer for the interviewees whose pain points matches our current solution.

Do a follow-up on the interviews to make the offer and ask for feedback and reviews subsequently or write a case study with them - More details here.

Make a list of feature ideas based on other learning to inform next phase of product development.

Keep communicating with the current users we have by collecting their email to send them subsequent updates - prepare a form for this.

Initiative 2: Customer Validation

💡

At this stage, we know a lot about our “prospective customers/users” and what they need, we should then focus on developing a scalable sales funnel. This is to ensure that the product can be profitable in the long run.

Developing a product differentiation strategy is also a part of the process at this stage.

We need to run a workshop for this to be able to develop a customer acquisition and sales strategies that work - based on previous record of working for other businesses/Units at RnDAO.

TO-DO: Ask for a Customer Validation Process workshop from Daniel.

Initiative 3: Customer Creation, Sales and Marketing

💡

— this stage is about identifying key messages, channels, platforms and marketing experiments to run based on how users have been using our product. This stage should start once we have at least 50 positive feedbacks to show product-market fit.

From here, we keep building, learning and improving.

v3 of MWW Customer Development Framework

💡

This playbook guides MWW’s user research, sales and feedback/reviews gathering exercises and outreaches, towards learning more about our market and ultimately achieving product-market fit, adoption, and growth.

1. Context

The goal of this ongoing set of initiatives is to build a company with the product we’ve built by validating it actually meets the need of the market and they’re willing to pay for it. Over the past months, we’ve been learning with the first version of our product, after this learning process, we were able to identify the first bet towards defining a strong value proposition for Meetwithwallet, something which meets the need of the market we are looking at serving. The previous research before this can be found at:

We have been able to build out a solution out of the learning from the previous research, and we are going back to learn if this is actually a problem that users have, towards achieving Product-Market Fit. We will be deploying a proven framework for achieving this which is the Lean Product Methodology: Customer Development Framework.

2. Objective

In this phase of work, we are looking at attaining clarity in Customer Discovery, Customer Validation, Customer Creation, Achieving product market fit and Growth. We will distill these different phases of customer development into Initiatives and iteratively following through.

3. Introduction

Meetwithwallet is a scheduling tool designed to simplify and streamline meeting coordination for both individuals and teams. Whether you're organizing 1-1 meetings or managing larger group discussions, Meetwithwallet ensures a seamless experience, eliminating the UX flaws in traditional group and 1-1 meeting scheduling tools.

For teams looking to enhance collaboration and optimize time management, Meetwithwallet is looking to be an answer and a solution to the inefficiencies and challenges they experience in their process of scheduling meetings, enabling smarter coordination without the hassle. With built-in privacy and scheduling flexibility, it ensures that every meeting time is picked with ease and clarity, reducing the back-and-forth of organizing meetings.

We believe that Meetwithwallet is the definitive tool for any team that wants to take control of their time and elevate their meeting efficiency to the next level.

4. Our Target Audience

4.1 Personas

💡

Captured in these section are some hypothesis and already identified pain points we want to validate about each of our target audience.

4.1.1 Cross-org Workers (Individuals Working Across Multiple Organizations)

5. Research/Outreach Team

Patrick

Adedamola

GPee

6. User Contact

6.1 First Contact Strategies

Our initial outreach aims to engage these target audiences, understand their scheduling challenges, and introduce MWW as a potential solution.

Channels for Outreach:

Social Media Platforms: Twitter, LinkedIn, and relevant web3 Discords or forums.

Direct Messaging: Personalised messages through Discord, Twitter, and Telegram.

Community Engagements: Participation in DAO meetings, web3 conferences, and online webinars. This may work for ongoing feedback collation and not our current run.

Sample First Contact Messages:

Cross-org Workers:

“Hi [NAME], as an active contributor to [ORG NAME], how do you currently manage meeting schedules within your team or with your colleague? We’re developing MeetWithWallet, a tool designed to simplify scheduling in the web3 space. Would love to hear about your experiences and see if we can help make coordination easier for you.”

Hi [NAME], As an active contributor to [ORG NAME], I’m curious—how do you currently handle scheduling group meetings within your team or with colleagues? We’re developing MeetWithWallet, a tool designed to simplify scheduling, especially for distributed teams in the web3 space. We’d love to hear more about your experiences and challenges with scheduling group meetings. Your insights would help us create a solution that truly works for you. Would you be open to a quick chat to share your thoughts? Looking forward to hearing from you!

6.2 Contact List

💡

This is a list of people we’re reaching out to for the Interview.

7. Customer Development Initiatives

Initiative 1: Customer Discovery

💡

We will be using the JTBD User Interview technique to learn about the challenges and pain points around meeting scheduling for these people we reach out to. The goal here is to learn and only suggest a solution to them when it seems what we have can meet their needs.

User Interview Guide: Group Scheduling

Cross-org Workers Interview Guide

Data Collection and Synthesis

We’ll log all interactions and outreaches here:

Research Summary and Next Steps

After the research and synthesizing all feedbacks into insights, we should be able to have a document containing the key next steps to take. This could be:

Preparing an offer for the interviewees whose pain points matches our current solution.

Do a follow-up on the interviews to make the offer and ask for feedback and reviews subsequently or write a case study with them - More details here.

Make a list of feature ideas based on other learning to inform next phase of product development.

Keep communicating with the current users we have by collecting their email to send them subsequent updates - prepare a form for this.

Initiative 2: Customer Validation

💡

At this stage, we know a lot about our “prospective customers/users” and what they need, we should then focus on developing a scalable sales funnel. This is to ensure that the product can be profitable in the long run.

Developing a product differentiation strategy is also a part of the process at this stage.

We need to run a workshop for this to be able to develop a customer acquisition and sales strategies that work - based on previous record of working for other businesses/Units at RnDAO.

TO-DO: Ask for a Customer Validation Process workshop from Daniel.

Initiative 3: Customer Creation, Sales and Marketing

💡

— this stage is about identifying key messages, channels, platforms and marketing experiments to run based on how users have been using our product. This stage should start once we have at least 50 positive feedbacks to show product-market fit.

From here, we keep building, learning and improving.