---
title: Mystic Whales Weekly Sync 13-10
tags: mystic wales, sync
---
# Mystic Whales Weekly Sync 13-10

## Project Updates
**WhaleStreet DAO** `Deal closed`

- DAO launched (1st 6 members are organisations)
- DAO infographics are WIP
- Dreamverse Event are upcoming in New York
- DAO's governance model require custom development & testing - was a challenge to implement it in a clear way for WhaleStreet team & future DAO members
- [ ] DG/Yalor - Finalise scope of customisations / product integrations before setting up Labs on DAOhaus Discord
- Product Integration: Boosts vs Hard Fork
- Co-promotion (e.g. WhaleStreet on HausParty)

**Polygon DAO** `Awaiting Proposal Revisions`
- Nemo mentioned that budget seems high ($80K between DAI/MATIC) & we need to reprioritise workstreams (more help needed on tokenomics)
- On pricing, better to have MATIC tokens (more palatable for Polygon team & it's relatively stable for us)
- [x] All - Arrange a call with PolygonDAO this Thursday/Friday to run through scope
- [x] Amos - After call, Re-define scope, priorities & timelines and sync with Sydney on BD/token economics workstreams

## Process

**BD Pipeline & Process (GSheet)**
- Process
- Sales Convo
- Email / Scheduling
- 1st Meeting (Sales Template / Project Charter via Hackmd)
- Proposal V1
- Revision / Client Call
- Proposal V2
- Decision / Client Onboarding
- Roles & responsibilities
- Project Lead: After scheduling / 1st meeting, Project Lead should be in charge of client communications, project charter, planning and accountability
- Sydney: Should be the final editor across projects before sending of Proposals (esp. financials)
- Yalor: Centralised accounting function for now (Receipt of payments, Paying of members, conversion of retainer to WETH, treasury management)

**Project Charter**
- When proposing a quote, **refrain from itemising & breaking down budget to clients** as this triggers them to pick & choose to narrow down scope
- On pricing, **propose a high amount & negotiate down** (rather than the other way round)
- 1% of token supply is good for pre-launch tokens, but toom uch for existing projects
- Within couple of days, Dystopia went from pre-launch stage to launch, so 1% became more expensive after changes
- In the future, we should create process / charter templates for different types of clients
- Early-stage teams (e.g. Dystopia)
- Medium-sized teams (e.g. MetaFactory)
- Large clients (e.g. Polygon)

**General Discussion**
- What is a good communication cadence? (Case in point: We took 10 days to respond to Dystopia)
- We should aspire to daily checkins over text or 5 minute watercoolers for accountabilty
- Are there other projects in pipeline?
- Happy to onboard new clients towards end of 60/90 days but blocked now
- [ ] Amos - Document the processes out for greater clarity (as extension to note-taking)