legalese / legalese.github.io

Static assets for legalese.com
https://legalese.com/
70 stars 27 forks source link

Getting V2 (MVP) Launch Ready #255

Open wabisabiyo opened 6 years ago

wabisabiyo commented 6 years ago
  1. Landing Page – due 2 Oct 2017

  2. Form – first cut of full form due 20 Oct 2017

    • [x] UI layout (alexis, @teeragit)
    • [x] fields on vertical accordion cards being linked to back-end (proteus) <-- finish. already in testserver
    • [x] copywriting for user input fields (alexis)
    • [x] interactive captable pop-up (proteus) <-- Finish, already deploy to testserver
    • [ ] mailchimp waitlist (alexis + jobchong)
    • [ ] QuestNet data - need feedback to tell user to move onto the first card (proteus, jobchong) <-- the first card is expanding after search. How do you want the user MSG to move on to next card?
    • [x] set up some mechanism to ensure that questnet auto tops-up / or we do, when the credits run low when v2 is live (@jobchong)
    • [x] shopping cart and preview (proteus) <-- finish. already in testserver
    • [ ] unit tests (@jobchong)
  3. Form submission – first cut due 20 Oct 2017

    • [ ] generation of document dependency graph (@mengwong, proteus) <-- Proteus is waiting for document's dependency and where to display it.
    • [ ] Legalese sending the incomplete forms to investors / other parties for their input (proteus) <-- this is not for end of October.

      So. We need to discuss whether we want to build the "viral" signature workflow for the October launch or stick to what @jandetlefsen had in mind.

      what proteus has been building (please correct me if i get any parts wrong)

      • User Leslie goes to legalese.com, clicks on the CTA, populates the form, generates the documents
      • Leslie is brought to a page where ze has to tell us the email addresses of the signatories
      • on our end, Adobe sends the documents to these signatories and Leslie's legalese dashboard is updated with the status of the execution workflow (i.e. who hasn't signed, where the bottleneck is)

      This is simple. That's usually a good thing. And it may very well be good enough for the Oct launch. Nonetheless, my reservations about this approach:

      • From the signatories' (investors and other founders/directors in Leslie's company) perspective, they do not have ready access to Leslie's dashboard on Legalese. This means that they cannot see what's the hold up on the completion of the entire fundraising round unless Leslie shares the login details with them. They only know that they have signed one or some documents (they do not even know that they are signing 1 of XX documents for the entire workflow). Typically, this means status checks via email to the startup founders and within the investor's own work routine to ascertain the progress on the fundraising round. Cumbersome and tedious.
        Moreover, if Leslie's running multiple legalese workflows for different fundraising rounds for different companies, ze may not like or want that)
      • There isn't in-built virality in this execution model as the signatories (investors who usually also execute other fundraising documents for their other investments; other founders of Leslie's company who may have other startups they need fundraising docs for, or who themselves may be investors) interact only with the document they have to execute, and that's done on Adobe. They do not interact with Legalese (save where Leslie shares zir login credentials), and consequently, do not get to track the execution progress of the round or fiddle with our product offerings/ other functionalities like the interactive captable.

      the immediate goal for Oct launch Legalese manages the order in which documents are sent out (not everything will be sent out for signature at the same time). We will do this via AdobeSign. We will manually manage this if we have to, but ideally it's at least a little step up than v1.

the goal, within the next 3 months

  • Leslie goes to legalese.com, clicks on the CTA, populates the form, generates the documents
    • Leslie is brought to a page where ze has 2 options: (1) Leslie could download the PDFs, and then go on to get them executed by each signatory in the correct order (we could even be cheeky and send them lengthy instructions on how they're supposed to get this done); or (2) Leslie could tell us the email addresses of the signatories. What happens then is that the signatories get an email telling them that for Leslie's angel fundraising round, said investor will need to execute X document now and Y and Z document after the others have signed X2, for example. Each signatory will also get a link to Legalese telling them that with their email, or some code or whatever, they can log in to Legalese to access the dashboard for that round in Leslie's company. This allows them to fiddle with the captable, track the progress of the round, and affords them the opportunity to generate independent and new rounds of investment docs for other investments they probably have. In fact, one of Legalese's tranche I investors had initially passed on our idea, but took an about turn when he used us to generate a round of fundraising docs for another investment of his
wabisabiyo commented 6 years ago

Comments on latest check-in on the test server:

TO FIX

UI colours

title bar of the page

'first tell us...' section -- @teeragit to give comments?

mailchimp waiting list

give this round a name section

left menu bar & presentation of the forms

drawer on the right

interaction fixes

cart

wabisabiyo commented 6 years ago

More comments based on changes checked in on 19 oct 2017:

wabisabiyo commented 6 years ago
DustinWehr commented 6 years ago

Don't know what CTA for investor popup should be "ADD" means.

wabisabiyo commented 6 years ago

oh it means that after you fill in the new investor's details in the popup, the call-to-action button to complete the entire action should say "ADD"

DustinWehr commented 6 years ago

Need a more specific recommendation here:

captable should not be formatted as a section -- it is more a side window within that card

If the captable is not affected by anything in the first of the three sections of that card, can we just merge the 2nd and 3rd sections?

DustinWehr commented 6 years ago

smart defaults that we chose for them should have a clear colour or symbol to tell users that we picked these for them

Check out https://github.com/legalese/v2-web/blob/9ba669c2a3d70086f3339a42bee6e55ea8454408/src/modules/common/schema/round.js#L670 Is this everything that constitutes a smart default?

DustinWehr commented 6 years ago

when i delete a director box (which is pulled from acrA), there should be a warning popup -- deleting the director here doesn't update ACRA of the change. please confirm that you wish to proceed even though this change is not updated with ACRA.

Jursidiction -- modal popup for wait list for other countries

@wabisabiyo is there a modal popup in use by the app already that we should reuse for consistency?

wabisabiyo commented 6 years ago

Need a more specific recommendation here: captable should not be formatted as a section -- it is more a side window within that card If the captable is not affected by anything in the first of the three sections of that card, can we just merge the 2nd and 3rd sections?

this is something that @jobchong was already working on. @jobchong do you want me to guide dustin on this, or have you got it?

wabisabiyo commented 6 years ago

when i delete a director box (which is pulled from acrA), there should be a warning popup -- deleting the director here doesn't update ACRA of the change. please confirm that you wish to proceed even though this change is not updated with ACRA. Jursidiction -- modal popup for wait list for other countries @wabisabiyo is there a modal popup in use by the app already that we should reuse for consistency?

@DustinWehr yeah it's the same popup to mailchimp that is under the search bar right at the start of the form.

jobchong commented 6 years ago

@wabisabiyo upon second thoughts I can do that.