CrewPay Whatupdate No. 2
Hello, crew.
Rolling into a long weekend here in the US. Here is a quick update for the week.
Team Accomplishments & News
- No major news this week
Product Accomplishments & News
- Marty, David and Darrien met this week to work through Admin stories. Designs and wireframes are in progress
- The team continued working on bug fixes and new onboarding
- Experiencing issues with Dwolla., including errors connecting certain bank accounts
Sales, Marketing & Customer Success Accomplishments & News
- Working on updated website and email sequence
- Product demo development
Revenue & New Clients
Last week: -12 transactions ($6 earned) -$44,837 sent -1 new company, 4 new contractors added
Totals:
-MRR: TBD
-ARR: TBD
-RPC: TBD
(not charging right now but it’s est. $195 based on 39 active x $5/mo, this is a correction from last week)
Closing Thoughts
We on-boarded a new customer this week. We hope to continue the trend for as long as possible, until there are too many to do personally. The experience confirmed we’re on the right track with the onboarding updates we’re making. It also uncovered a new feature request.
The request was for businesses to have the ability to schedule payments for a future date.
At this stage of the business new feature requests can derail progress and cause startups to lose focus. When new requests come in, we can handle one of three ways:
- We’re not going to do it
- We’d like to do it
- We don’t know yet
Requests that fall into #1 are pretty easy.
Ones that fall into #2 and #3 are more nuanced. What if it’s a really cool idea? What do you do when the feature aligns directly with the mission and key problems your software is solving?
The answer — we need more information.
Over the next week we’ll investigate to gather facts and search for patterns. We’ll then hand what we find over to the product team to work through options.
From here, we’ll see if the feature makes into a user story and assigned to a sprint to be deployed.
-David Horne