dorgtech / docs Goto Github PK

Set up a compliant and tax-ready bookkeeping system to

• Classify transactions (income, compensation, reimbursement, transfer between accounts)
• Identify counterparties
• Generate financial statements (Income Statement, Balance Sheet)

Other considerations:

• be able to reconcile and track transactions between Mainnet and xDAI
• to what extent can we rely on Airtable vs. traditional bookkeeping software (Quickbooks) vs. crypto tools (Cointracker, TokenTax, Gilded, Cryptoio)

Consider vistaprint.com as provider

Establish budget ($50 per bag, paid by builder?)

Contents

• Branded dOrg T shirt
• Brand Sticker Pack
• • dOrg Logo x3
• • Web3API Logo x3
• • Ethereum Logo x3

Should be Available for purchase by EOY

All legal agreements that member's agree to upon joining should be updated, simplified and synthesized into one master "Builder Terms & Conditions".

Currently this includes

• Operating Agreement
• Contractor Term Sheet
• Participation Terms & Conditions
• Privacy Policy (drafted, never ratified)

The Member T&Cs will be hosted on IPFS and agreed to in the Activation Proposal.

There will also be a title page which summarizes the key points, as was done in the Dxdao Participation Agreement.

Create a dashboard on our website for clients to...

• View project metadata (info from Airtable -> proposal, cost, timeframe, etc.)
• Track deliverables in real-time (Github Project board)
• Pay:
  • Payment schedule with status of each payment
  • Web3-enabled: they just hit pay and app fills out the amount
  • Fiat-options: allow for bank transfer or credit card that purchases crypto and automatically sends it to DAO address (Ramp, Wyre)

We have this form setup in Airtable, but we don't have a regular/automated system for collecting it.

I think we should automatically send this or a similar feedback form to clients either with every invoice or at the end of every engagement.

List all of the other DAO's community calls and have a representative there

Using this template
https://github.com/dOrgTech/Ops/blob/master/proposals/dsp-1.md

Summary

Three roles

• Accounting
• Facilitation
• Communication

Why should we fund this?

This will be a new approach to tackle the internal ops resposibilities by assingin lead roles to avoid the diffusion of efforts and separate in specific operation areas.

Anything else you'd like to add?

The tasks will be recorded at the Ops Repo
The leads for each role will be as follows

• Accounting: Magenta
• Facilitation: Ori
• Communication: Roberto

Accounting : Maintain and improve systems for keeping dOrg’s finances and transactions healthy and transparent

Facilitation:

Focus on ways to continuously enhance the dOrg builder experience

Communication:

Keep dOrg’s external relationships and communication channels lively and growing

Set a timeframe:

• 9 weeks (Until January 4th)

Cost

$900 / week ($300 / week per role)

Consider migrating our Ops stack from admin-dependent 3rd party services to tools that are...

1. Autonomous. Resilient to external interference (not reliant on closed-source corporate software)
2. Decentralized. Resilient to internal malfeasance (not reliant on trusted admins)

Quickly fix line numbers not incrementing properly in activation from 5d04e7d

Utilize AIrtable (API, embedded views and blocks) to create a comprehensive builder dashboard with sections for:

• Stats

  • Revenue (over time, by client, total)
  • Compensation (over time, by builder, total)
  • Specializations (by builder, by project)

• Finding Projects

  • Enter and visualize work commitments
  • View active and upcoming opportunities
  • View confirmed project timelines

• Sourcing Projects

  • Instructions with links to outreach message, meeting agenda, and proposal template
  • Sales Pipeline Kanban
  • Form for adding a new opportunity
  • Form for closing a project
    • generates Services Agreement (SoW, T&Cs, link to proposal) and all client invoices in a .zip
    • generates DAO proposal in Alchemy
    • updates entry in Airtable

• Working & Getting Paid

  • Builders can enter, edit and view payment claims and work logs
  • Project lead can make payments:
    • calculates payment, rep and token amounts based on current claim distribution
    • generates multiple DAO proposals in Alchemy
    • adds multiple entries to Airtable

https://www.eventbrite.com/o/dorg-20010113112

These have been happenning quarterly. The first was on June 4 and then September 3. So the next one should be in the first week of December.

Users find friction when filling the W8 and W9 Tax forms,

The instructions to fill up the fields should be linked in the process.

• Example for W8 Ben> https://www.irs.gov/pub/irs-pdf/iw8ben.pdf

Consider adding pre-filled examples of these forms with 'john doe' placeholders

• Collect W8-BENs (non-US) and W9s (US) as part of the post-activation onboarding flow.
• Figure out custody solution for the forms (professional 3rd party? trusted DAO members?)
• Generate and distribute 1099s

Deadline for collecting and generating these forms is Jan 31, 2021.

Consider migrating dOrgX to Alchemy 2.0: https://xdai.alchemy.do/

Currently the Savings page shows how savings accumulate but not how we struture decisions around spending them.

I think this is also an opportunity to develop a more robust process for this..

90 days of no passed proposal makes a builder inactive (which means they are removed from all internal spaces).

We should automate a 10 day warning so that builders have a chance to submit a reactivation proposal before this happens.

• Delphidigital.io
• EthHub
• Top of the Block
• Bankless

Expectations around..

• personally taking equity, tokens, or titles in the client
• going to work for the client without dOrg

• https://en.wikipedia.org/wiki/DOrg

Currently, tracking and executing payouts is cumbersome and error-prone. It requires lots of copy-pasting between Zoho Sheets (to calculate amounts), the compensation request form on Airtable (to log the payment), the Builders Airtable view (to lookup each builder's ETH address), and Alchemy (to make the payment proposals).

In addition to improving this entire flow, the Zoho template for calculating payments should be improved and possibly migrated into Airtable:

• include breakdown of sourcing incentives in addition to builder breakdown
• include a field for work logs
• standardize the allocation algorithm -> hours*impact? hours? FTE points?

• Try align with DAO Rush Week
• Event Schedule
• Define speakers
• Promotional schedule (min 2 weeks)
• Prepare testimonials and review membrane activation funnel

I've suggested a new structure for our landing page here: https://docs.google.com/presentation/d/1P7jeGETFRJBKlyXUjk9j9-QUUa8BctjFVSwMaIyev6M

I think we should contract 99designs to get this design to completion and implement it with a website builder.

We'd need to decide on a budget (I think $2-3k would be enough) and make a dOrg Spending Proposal.

• Tweet
• Case Study
• Demo videos

https://www.figma.com/file/5JMAyjRhvxREqXGHJTt6jN/Flows-and-organization-PUBLIC?node-id=64%3A35

This structure is used by many successful companies to outline their internal ops, and we would benefit greatly from having it outlined and being able to show it to both internal and external stakeholders.

The first step is to create a Value proposition canvas:

Which then expands into the Business model canvas:

AGENT PAYMENT FLOW

This same flow applies both to internal work and client work:

1. Enter claim into budget spreadsheet

2. Once everyone in your claim has filled in and agreed to distribution, move details into the compensation request form

3. Form will redirect to alchemy proposal. Make sure to enter your ETH address, payment, token, and Reputation amount in the proposal form.

• Review current roles in the organization
• ....

Currently it entails

1. add each expected client payment to the transaction table here https://airtable.com/shrupfH519vJW9836
2. send proposal to the DAO linking to the project's airtable entry
3. add the alchemy proposal URL to the project's "DAO proposal" field
4. export the SoW for the project from here
   https://airtable.com/tblMrDMxVayppGF9m/viwSrPziC5aU92reN?blocks=blisfwa1VO6K0w9p0
5. download the Client Terms & Conditions here
   https://airtable.com/tblS16OeUmjCQ0RBv/viwrHXKG783AXUhGX/recZ1UwLbgeanDoqw
6. append these two pdfs together
7. send to client and ask them to sign

Looking into possibilities for dOrg freelancer benefits

Tax Deductible

• Allowances for conference travel, co-working, up-skilling
• Health insurance
• Low-cost branded items like t-shirts
• Free seminars (tax guidance?)

Partially Tax Deductible (portion used for work)

• Housing
• Computer
• WiFi & mobile data

Taxed

• Gym, mental health, other wellness
• Spotify, Netflix, other entertainment
• PTO, vacation bonus, sabbatical, parental leave, bereavement

Dividends

• Patronage dividends (tax deductible)
• Capital stock dividends (capital gains tax)

Relevant Links

• Taxable vs. Non-taxable Fringe Benefits
• What fringe benefits are taxable
• How does expense reimbursement work
• Fringe Benefits for Independent Contractors (See 22)

test

• Extend xDAI documentation here: add xDAI, DAI, Gen, xGEN proposal process
• Fix minor typos resolved

Embed a video that walks through the activation process

Tracked here :

https://github.com/dOrgTech/landing-page/issues/72#issuecomment-729163899

dOrg Workflows: https://www.figma.com/file/5JMAyjRhvxREqXGHJTt6jN/Flows-and-organization-PUBLIC?node-id=50%3A2

Quickly fix missing line breaks in activation resulting from eeaaf39

The link currently takes users to https://dorg.tech/membrane , which is fine, but we should be able to measure how many clicks we're getting from this channel.

Consider updating the url and using a utm link instead
https://en.wikipedia.org/wiki/UTM_parameters

similar to ..

https://dorg.tech/membrane?utm_content=buffercf3b2&utm_medium=social&utm_source=deepdao.io&utm_campaign=buffer

• Monday internal ops call
• Bimonthly sync
• Quarterly openhouse

Add all these forms into a "Builder Dashboard" on the landing page.
https://docs.google.com/document/d/14bFQcFYjChYaECYzSdLermOi7RHBK9MLoh7Qc8kDJG4/edit

The bi-monthly dOrg chat on 5 November shed light on many deeply insightful topics, including the possibility of gathering more knowledge of types of work that dOrg members would be especially interested in. If there isn't already an existing post-engagement survey, It would be great to introduce a method (survey) of collecting information on how team members felt about projects. This could help to quicken the process of learning more about team members' preferences as it relates to projects.