---
# System prepended metadata

title: Summary of Wireframe Changes
tags: [opolis]

---

---
title: Summary of Wireframe Changes 
tags: opolis
---

From our findings, suggestions and initial wireframes, we now a better view of the changes we would like to propose for Opolis' onboarding. This document serves to summarise the end-state changes and how the sections and fields in the new Opolis onboarding flow. 


# General Approach 

The approach taken here is to have a multi-stage onboarding process, where users can submit and achieve success at different checkpoints. Through our user interviews and UX audit, we have identified suitable checkpoints (arising from lack of information, or user's readiness) where users will have a dashboard view to monitor and track their progress. 

We have also optimised how the forms, copy and fields to maximise clarity, succinctness and trust in the onboarding process, and Opolis as a service. 

This document will be split into the respective sections, along with suggestions and the fields that will be housed in each section. 


# 0. Pre-onboarding & General Fixes
This section contains the suggestions and fields of all the flows outside of the onboarding flow. 

|     | Flow                                            | Suggestion                                                                          |
| --- | ----------------------------------------------- | ----------------------------------------------------------------------------------- |
| 1   | Homepage                                        | Add in pricing information (as well as potential cost savings) within the home page |
| 2   | Magic Link sign in / sign up                    | Add other social sign-ins (for users who are not used to Magic Link)                |
| 3.  | Magic Link emails                               | Re-format Magic Link email to Opolis' branding                                      |
| 4.  | Magic Link sign in / sign up                    | Improve copy on why Magic Link (creation of crypto wallets)                         |
| 5.  | Member Types selection                          | Re-order Employee/Coalition and change "employee" to "freelancer" for clarity       |
| 6.  | Dashboard step after completion of each section |  Add persistent "Schedule a Call" & invitation to join Discord for each step                                                                                 |
| 7.  | Re-engagement emails between sections           | Add in contextual nudges & educational information to encourage users to complete next section of onboarding                                                                               |

#### Suggested Additions to the FAQ / Info Hub

* Why is there a requirement for minimum earnings to join Opolis? What if I just started my freelance business and don't know yet? What happens if I end up netting less than I expected?
* Why do I need to incorporate my business as an S-Corp LLC to become an Opolis member? What are the benefits?
* How does Opolis save members $$$ on health insurance premiums?
* How does payroll work? Can I earn income in USD AND cryptocurrency?
* How does Opolis handle tax compliance? What resources are available to help me with business taxes?


# 1. Eligibility check & Personal info 
This section allows potential members to check their eligibility (and exit early if ineligible), as well as collect readily-available personal information. 


**Membership Setup**
This screen gives users an overview on what steps they can expect in the flow. 

**Eligiblity Check**
This screen allows users to check whether they are eligible for Opolis or not. Currently the fields which most users are blocked out by are: 
* What is the total amount you expect to earn in the next 12 months?
* Are you legally authorized to work in the US?

**Personal info**
* First name 
* Last name
* When do you want to start your membership? 
* How do you know about Opolis? 
* Biological sex 
* Birthdate 
* Marital status 
* Street Address 
* City 
* State
* Zipcode 


> i. "When do you want to start your membership?" has been changed to month select for greater clarity. 
> ii. Address information will be saved and available for auto-fill in other address fields in the form 

When users have successfully completed this section, they will see the Onboarding Dashbord for the first time, where they can (A) proceed to Business info (B) Schedule a call and (C.) join the Discord. 

# 2. Work info 
This section asks for information about the user's work, as well as company information. If the user does not have a company incorporated, this flow should ask for information required by Opolis to help users incorporate as well. 

**Work Information**
* Please describe your nature of work in 3 to 5 sentences
* How much is available for payment and benefits in the next 12 months?

**Work Address**
* Where do you spend most of your time working from?
* Do you work in multiple states?
* How often do you travel for work?

**Company Information**
* Do you have a incorporated company with a EIN?

> i. "Where do you spend most of your time working from?" will allow users to either auto-fill their previously saved address, or add a new address.
> ii. "How often do you travel for work?" is changed from a text field to a dropdown from (Monthly/Weeky/Daily)

This is where the fork in the road lies. If user does NOT have an incorporated company, we will need to create a flow for company incorporation. If the user has an incorporated company, the following set of fields will follow. 

**Company Information**
* Business Name
* Business Type 
* Does the entity employ any other person(s)?
* Employment start date 
* Company legal address 
* Company mailing address
* Business email (checkbox: same as user login?)
* Business phone number 
* Cell phone number
* Do you have insurance for your LLC? 
* For tax purposes, will you be electing to be treated as an S-Corp or as C-Corp?
* Please upload a PDF of your Certificate of Incorporation

> Company legal and mailing address will alos be another field for user to auto-fill or add new address. 

Once user has completed the above flow, they will achieve the second stage of success and see the Onboarding Dashboard a second time. From here, they can proceed to the next stage, schedule a call or join Discord (or whatever appropriate Discord channel)

# 3. Compliance & Finance 
The next section is for users to fill in compliance and finance information. 
**Employment Eligibility**

* Are you legally authorised to work in the US? 
* Have you ever been convicted of a felony?
* (if above is yes) Please explain 

**Race & Ethnicity**
* List of all race & ethnicity options 

**W4**
* Personal address
* SSN
* Number of allowances to claim 
* Additional amount to withhold 

**I9**
* I am aware that federal law provides for imprisonment and/or fines for false statements or use of false documents in connection with the completion of this form. I attest, under penalty of perjury, that I am (choose from the following) 
* Select an applicable document from List A 
* Upload document
* Select an applicable document from List B 
* Upload document

> i. Both selection of applicable documents have been changed to simple dropdowns in order to reduce information overload

**Paycheck Deposit**
* Account name 
* Account type 
* Account number
* Confirm account number 
* Routing number
* Confirm routing number 

After this section, the user will achieve the third instance of success and be able to do the 3 actions, similar to the previous section. 

3. Benefits 
This would be the last step of the process, where users can end off the onboarding with making some meaningful choices and impact to their benefits. 

The sections below have a standardised title, subheader 1 (on the significance of the benefit), subheader 2 (on Opolis' offering) and "more information" call-to-action to the PDF. 


**Retirement**
* What is your preferred 401K contribution percentage?
* Dependents (Add / Remove)
    * First Name
    * Last Name
    * SSN
    * Gender 
    * Relationship 
    * Birthdate 
    * Checkbox: Household member? 

> The dependents here should be saved for auto-filled in the later section. 

**Health, Dental, Vision Insurance** 
* Plans selection

**DCFSA** 
* How much is your annual contribution?
* Waive contribution
> After user has entered the information, the screen should show "You will have to pay $XX for the remaining XX contributions" 

**Life & Disability Insurance**
* Checkbox: I am a tobacco user 
* Dependents (Add / Remove)
> i. The dependents here should be avaialable for auto-fill from the previous section
> ii. After user filled in or checked relevant information, the screen should show "Your full coverage cost per month is $xx.xx" 

When the user has completed this section, the user completes all 4 sections of onboarding and sees the Dashboard the last time. The Dashboard here can be adapted for future call-to-actions for onboarded users. The current screen shows an "Onboarding in progress" screen to account for operational onboarding process (which can be removed if onboarding is automated). 

# Summary 
At the end of the 4 step process, the user can now stop whenever they do not have the information and resume the onboarding session when they are ready. This gives them more flexibility and less stress, as well as a better idea of their progress throughout the onboarding. 

The smaller optimisations as observed in the fields and copy layouts helps to reduce redundancies, increase clarity and succinctness in understanding and filling out these fields. Together, this should help increase onboarding rates as well as customer satisfaction during their onboarding experience with Opolis. 


# Appendix

|     | Flow                                     | Suggestion                                                        | Work                          | PIC  | Status                    |
| --- | ---------------------------------------- | ----------------------------------------------------------------- | ----------------------------- | ---- | ------------------------- |
| 0   | Dashboard & wireframe assets             | Create dashboard & wireframe assets                               | Create screens                | Jaqi | Done                      |
| 1   | Whole flow                               | Split the onboarding flow into 2 parts                            | Re-organise flow & fields     | Amos | Done                      |
| 2   | Sign up / Log in                         | Switch to Oauth logins on Magic Link                              | Create screens                | Jaqi  |                Done           |
| 3   | Select Membership                        | Re-order Coalition / Employee Member buttons                      | Create screens + Copy         | Jaqi  |            Done               |
| 4   | Select Membership                        | Surface hard requirements  early on in the flow                   | Create screens + copy         | Jaqi | Done (eligibility checks) |
| 5   | TBD (Perhaps at Select Membership)       | Surface pricing within the flow                                   | Look at flows + Screen + copy | Jaqi  |         Done                  |
| 6   | Personal Information & Election Benefits | Save & auto-fill repeated fields (e.g. dependants, beneficiaries) | Create screens                | Amos | Done                      |
| 7   | Company Information                      | Collect information from customers for company incorporation      | Create flow + screens + copy  | Amos | Partially done (placeholders)                          |
| 8   | Benefits Election                        | Synchronise title & section progress bars                         | Create screens                | Amos |  Done                         |
| 9   | Benefits Election                        | Standardise title & paragraph copy formats                        | Create screens + Copy         | Amos |  Done                         |
| 10  | Benefits Election                        | Link to PDF should jump straight to section                       | Define sections               | Amos |    Done                       |
| 11  | Compliance                               | Provide more context & information on forms                       | Create screens                | Amos |   Done                        |
| 12  | Compliance > I9                          | Simplify form fields to a dropdown                                | Create screens                | Amos |    Done                       |
| 13  | General flow                             | Other fields & copy improvements                                  | Create flow & screens         | Amos |    Done                       |

