Builder dashboard

Open
#42 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

The issue names no source files, tests, or entry points. Start by reviewing the linked Airtable views and separating the Stats, Finding Projects, Sourcing Projects, and Working & Getting Paid requirements into an agreed scope. Done means the dashboard supports the listed views, forms, payment claims, generated outputs, Alchemy proposals, and Airtable updates.

Written by the indexing model from the issue text.

Description

Tech

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

  • 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
Dominant language
No language data
Stars
17
Forks
12
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dOrgTech/docs

All issues in dOrgTech/docs

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.