SCP-149 Product Workstream Renewal


Curate and propose a product roadmap based on research, user feedback/behavior, future market opportunities, and informed vision. Align with the mission and goals of the ShapeShift DAO and other workstreams for efficient execution.


  • Goal 1 Execute on a calculated Portfolio of bets
  • Goal 2 Retention 🔂 Revenue & User growth
  • Goal 3 Mandated Metrics & Measurement
  • Goal 4 Experiment more
  • Goal 5 Talk to our users
  • Goal 6 Assist Grants Partnerships

Abstract -

As a product-centric DAO, the Product Workstream is accountable for a number of activities: cross workstream alignment on execution, retaining/acquiring users, growing the FOX ecosystem, speccing/launching new product lines, and achieving Shapeshift’s mission. A YES vote for this renewal is continuing support for the strategy of a portfolio & the bets within, plus the prioritization of the current roadmap.

We’ve included a budget renewal with only three addendums: one for team software, one for an event or two, and a FOX hedgey allocation for the work stream leader. This is a minimal cost adjustment monthly, but since it’s a 6 month budget may give some sticker shock.

Specification -

NOTE: As the workstream lead I’m humbled by the amount of passion and debate for refining processes here at the DAO. If we have the bandwidth, and it is necessary, I will post a revised set of goals when we do our roadmap and strategic vision sessions. Slated for, hopefully, September —> to be deployed in October (as possibly two proposals). This solicits more feedback so that our budget is well spent and has healthy awareness & consensus. Additionally, if things reach a more dire state on the DAO’s runway by January— through market conditions or through governance actions or through unknown factors— I will likely reduce my salary first to offset costs in the DAO. This is accountability folks, at least aspiring for some.

You can find all specifications in the posts about the Portfolio of bets under the goals post and the ratified roadmap on snapshot and more granularly on the spreadsheet for tracking these.

We track our goals at every office hours improving our documentation, rigor, and velocity. It’s worth noting that there are multiple governance proposals coming up for vote that will change the execution path of product. We’re optimistic that the holistic outcome will be beneficial for all FOX holders, our shipping velocity, the rigor of our experimentation path, and the iterations required to get us into a state of profitability.


  • Prioritize and adjust the roadmap with cross workstream alignment.

  • Analyzing and surfacing new revenue streams that are not listed yet in the roadmap, but reporting back to the community with more details.
  • Coordinating research and resourcing in partnership with the FOX foundation
  • Organizing and running the Monday afternoon roadmap and timeline meeting and coordinating with product and engineering throughout the week to remove blockers, assist with product related decisions and keep things moving through the feature development process and Product/Engineering status updates throughout the week.
  • Product/Engineering representation at the Weekly Ops Sprint.
  • Facilitate bi-weekly office hours to provide updates on progress, report on KPIs, and offer space to the community to ask questions, give feedback, and pitch ideas.
  • Draft product specs, review with Beard regarding designs, work with ENG workstream to evaluate engineering resources, and iterate the feature development process.
  • FBL will also spend a significant effort in defining core engagement loops & behaviors for users on Shapeshift, working backwards to activation moments to surface quick wins for development.
  • Orthogonal to this is identifying user buckets or personas, working with marketing and other workstreams.
  • Hosting and Leading Spec kickoffs/spikes/breakdowns between Product and Engineering.
  • Spinning up regular retros (at either phase completion or large feature completeness)
  • Leading and continuing all scheduled team syncs and 1-on-1s.
  • Managing Budget and workstream contributor payments made through Colony.
  • Coordinating strategy sessions, touchpoint, and retros for launches. Facilitating where necessary.

Budget and team

The Product workstream will consist of 4 members. 3 full-time and 1 part-time.


  • The additional addendums are a modest stipend for two events & earmarked SaaS budget:


  • current funds: [$1248] —> continue holding funds in colony until we negotiate with zenhub or linear for annual plan.
  • Additional earmarks: Figma [$69 a mo for the team—nice]
  • Events
  • ETH Chicago (this is earmarked and we will be thrifty: printed API materials for PTT to bring to builders at the hackathon; success measured by leads in the API TAM breakdown sheet and their closure by EOQ)
  • ETH Denver ( I earmarked $200 a team member for flight or stipend, up to them if they want. Also, if we don’t go, then return to DAO after the term.)

I mentioned in the last post:

I’ll be taking full stables for the first few months, at which point I’ll propose taking a portion in time-locked FOX on our next budget renewal. Skin in the game folks.

I’ve proposed a modest FOX addendum for myself, 1k a month and locked as a 6 month hedgey for each disbursal. This represents an additional 6k over the term of the team, and only a 1k FOX increase spend per month and only in FOX (about $480 per month in equity to the workstream lead ). I hope my value to the DAO has been obvious so far and this is ok!

The total budget breakdown

The monthly September - February budget breakdown will be:

$37,589.90 USDC

5,980.00 FOX

$43,569.90 TOTAL value

Totals come out to:

$225,539.40 USDC

35,880.00 FOX (including $2400 in FOX for user testing, not monthly since we haven’t disbursed all of this yet)

$263,819.40 TOTAL


This is the previous total budget:


Apple to apples in monthly cost: the change to the DAO topline is 3% per month. Comparing the cost for the 6 month original cost term versus 4 month term : 16% total increase. Primarily because of FOX for users and the workstream lead.

Benefits -

Ships the portfolio of bets, gets the next roadmap cycle iterated and into goverance, continues to build our two main focus initiatives: the API and the frontend. Unlocks new features, continues alignment with a strategic lens, and continues execution of the product team’s goals.

Drawbacks -

We’re moving with more rigor so we aren’t shipping as many shiny features.

Our team is lean so there is only so many resources to cross allocate