Future onboarding V1
How we want to onboard users onto the platform. What we need to build first. Our Mural board:
Core Principles
Ask as little as possible in initial onboarding (stay focused on user needs not ours)
Give them their identity in the product quickly
Create a dashboard that encourages them to get set up further: "The product is ready for you" (e.g. Steady dashboard)
Separate out the onboarding into small steps (e.g. Ko-fi)
Don't make it too boring
Remember the Mailchimp High5
Link to guides / more information along the way
Once in the dashboard: No step design. Single prompts. (e.g. wordpress)
Highlight most important actions (e.g. GoCardless)
Offer help, clearly and broadly
Also indicate community aspect of beabee (e.g. nextcloud)
Prio user types
Where do our first users come from?
Most will be directed to us through our contacts, talks at events, referrals.
What is their commitment level when registering/entering the product?
High commitment level at moment of sign up
Website will have main CTA to get in touch/ book a demo etc. before registering and setting up
What stage are they at?
Starters: Starting from scratch with their community/website. Getting started with beabee (see Misfit, Projekt K, Goldspirit)
Existing small newsrooms: Switching from existing solutions.
a. have payment provider set up, email provider, data across different platforms (089 Wehringhausen, Bürgerportal, Relevanzreporter)
b. have community member list but no payment set up yet (e.g. Du bist Rheinhausen/ Julia project)
Open questions
When do we want to ask for payment info?
Right at the beginning, after sign up
In e.g. a notification after entering the product (see Ko-fi)
As a lock (can't take certain steps at some point without adding payment info)
ℹ️Payment suggestion: We can prepare to have the first users registering without paying but with the info that it will be free for now (for first X users or until X) and we will charge based on member income, then it will be necessary to leave payment info.
When is the right time to ask for legal information
Legally necessary contact info etc.
Data processing agreement
As soon as we do actually transfer data. When data migration or payment is set up. Could be guided to settings/account through a notification.
Should we indicate in the product how long certain steps take?
What is the right order: Mailchimp integration setup and 2nd sign up step on consents
Once user has set up mailchimp, notification from membership builder that it can only start, once they've set up the step 2 in their sign up process?
List of information we need to gather
First suggestion for ordering
Most important actions for users
Registration phase (Double opt in)
Email
Password
Setup phase
Logo (see Ko-fi)
Newsroom/Project name
URL/ Website newsroom
Language for your users and you,
For german language: Would you like to use formal or informal language?
Needed later for legal reasons (Impressum and Privacy Policy could be part of the setting up the membership builder)
Link Impressum (for Germany)
Link Datenschutzerklärung/privacy policy
address (legal)
3. Set up membership builder (several steps)
Theming
Set colors
Set main font
Set background image
Join Page
Set Headline
Set Subheadline
Set minimum amount
Set default amount
Set three displayed amounts
Absorb processing fee "yes" or "no"
Set up payment with GoCardless (prompt in here leading to extra page)
🧐 research what it takes to connect and automise. What tasks stay witht he users?
As long as we don't have connection, what is needed to guide users.
🧐 Getting link is blocked until payment is set up?
User details page
Set Subheading
Section 1: User's postal address
Copy "Mail title"
Copy "Mail text"
Copy "Mail opt-in"
Set up mailchimp synch if they want
Section 2: Newsletter subscription
Copy "Newsletter title"
Copy "Newsletter text"
Copy "Newsletter opt-in"
Set up emails and welcome notice (just the ones with actual content)
Phrase welcome notice (or use standard template for now)
Phrase Welcome email (or use standard template for now)
Phrase Canceled contribution email (or use standard template for now)
4. Set up subdomain (Run beabee on your own url)
Users need to install DNS records at their hosting provider
We provide user with with links to copy and implement in their CMS
Link to the join page
Three links with the displayed amounts as default (if they want to offer different tiers)
5. Set up billing (extra page) for beabee
🧐 Plan what we want to start with
Questions to users to understand what in the product they need/ how they can use the product
Possible to include some of this in the onboarding if we can work with it concretely. E.g. depending on answers we send people different set-up guides (different steps) after they sign up.
Finance
Do they offer membership or recurring donations
Do they offer donations
Do they offer subscriptions
Do they already use tools to process payments (e.g. Steady, donorbox, betterplace donation widget, WooCommerce, ...)
Connecting with their community
What Email provider do they use? What do they use to send emails to their users.
Where do they keep their community member lists right now
Do they have contact lists yet for their community members
Do they use something to allow users to submit questions/ideas or survey tools etc. to ask questions
Which communications channels do they use with their community (signal/whatsapp/telegram, Email, post, phone)
Last updated
Was this helpful?