PlebLab / Top-Builder

Welcome to PlebLab's Startup Day, a dynamic gathering for Bitcoin startups, featuring the Top Builder competition as its centerpiece. This event is a hub of activity, offering builder sessions, workshops, announcements, and speaker panels, all aimed at fostering growth and learning within the Bitcoin community.
https://pleblab.dev
7 stars 0 forks source link

[Top Builder 2024]: BitScript #23

Open setzeus opened 8 months ago

setzeus commented 8 months ago

πŸ—οΈ Top Builder 2024 Application Form to track progress through Round 1 - 3 ~ Currently in Round 1

πŸ“ Instructions

  1. Only complete this form if you have been chosen for Top Builder, by PlebLab.
  2. Provide detailed information to assist the judges in evaluating your project.

πŸ§‘β€πŸ€β€πŸ§‘ The Team

πŸ’‘ The Idea

πŸ“š Additional Information

πŸ“Œ Submission Type

πŸš€ Current Project Progress

⏳ Round 1 Milestone

πŸ“ Submission Complete

πŸ“… Top Builder Program Structure

Registration Opens: Monday, December 18, 2023

Round 1: January 13 - February 10, 2024

Round 2: February 10 - 24, 2024

Round 3: Starting February 24, 2024

Final Round at Startup Day: March 14, 2024

setzeus commented 7 months ago

Week 1 (Jan 13th - 19th) We kicked off this by designing three different possible user-flows / features that we wanted to narrow down for the remainder of the competition. We specifically worked on the following features:

Taproot We designed a wizard for manually creating a ScriptPath tree.

Digital Signatures / PSBTs We designed & explored the idea of creating a UI for all of the steps involved in a PSBT. This turned out to be deeply complex due to it's dependencies (we'd need to design a UI for signing & message digest).

RPC A Postman-like UI for learning & interacting with core RPC.

The goal of creating these three iterations is to prepare for the next week of user interviews.

setzeus commented 7 months ago

Week 2 (Jan 20th - 26th) During this week we primarily focused on user interviews. We interview our current first customer cohort along with a handful of new additional potential customers.

The feedback was pretty universal & consistent: everything we've built so far is useful & is something users want to learn, but don't necessarily need. The reality we've learned is that most, if not all developers are actively working on the application layer. They do not need to read or write raw transactions in their-to-day.

However, whether it's directly or through an API-wrapper, every developer is interacting with RPC...

From this week we concluded to build out the RPC / Postman-like UI for interacting with core RPC!

setzeus commented 7 months ago

Week 3 (Jan 27th - Feb 2nd) This week contained two different tracks, one engineering & one marketing:

The engineering track consisted of building out the MVP for the new RPC feature. We didn't wrap it up but should have something to demo by the following week.

The marketing track consisted of kicking off our Twitter strategy. It led to our first ~400 followers & led to the first hints of a content/marketing machine to go from articles -> threads.

setzeus commented 7 months ago

Week 4 (Feb 3rd - Feb 9th) Two large updates on our end:

  1. We had the chance to demo & conduct a user interview with one of our heroes. It was extremely enlightening as he pointed out the good, the bad, & the ugly.

  2. Our RPC MVP feature was completed! As tracked above, this was the feature that we decided to build out next due to the feedback we gathered from our initial cohort of customers. It's currently in staging & we'll likely take a few more days of testing & polishing, but this will go to prod soon.

setzeus commented 7 months ago

Week 5 (Feb 10th - Feb 16th) One large update on our end:

We finally pushed the v0.1 of the RPC feature to production! You can find it here. While it's extremely simple at the moment, it's a big leap as it's the next large "developer" that we'll consistently update.

As mentioned above, some of the most consistent feedback from our first cohort of customers & prospect was always along the lines of "this is cool, I WANT to learn this but don't think we'd use it too often from day-to-day."

In short, for most the Bitcoin companies we'll be selling to, the majority of their developers will be working at the API level, not lower (which is where our current tools are the most powerful).

Captura de pantalla 2024-02-22 a la(s) 5 48 17β€―p m Captura de pantalla 2024-02-22 a la(s) 5 48 09β€―p m

setzeus commented 7 months ago

Round 2 Milestone(s)

While we slowed down our momentum a bit the last two weeks due to medical concerns, we're strapped in for a fiery next few week(s). We feel more comfortable with our product but feel like we need more work on the product, marketing & sales-side. Therefore...our next few goals are:

1. Sharpening Our Content Machine (marketing) From the metrics we're tracking, our two big developer features (deserializer & sandbox) are by far the most heavily used. Right after, however, is the series of articles we've published that reside in the "Lessons" sections. It follows that the lessons/articles themselves are a powerful source of retention.

Additionally, it's become clear from this test Twitter thread, that articles -> thread is likely a powerful, consistent distribution strategy we can run; in short, every article is a form of content marketing that we previously underestimated.

Goal: Define a process & plan out next 26 articles (w/ the idea of publishing one a week)

2. Further Segmentation Exploration (sales) Throughout the product process we've identified & tried to serve multiple marketing segments. As of late, we've identified three different markets that we still need to conduct further research on:

  1. Freelancers
  2. Educational Bitcoin Companies
  3. General Bitcoin Companies

It's clear that focusing on 1. is a mistake since the TAM is small & can be served by focusing on 2. & 3. Deciding between 2. & 3. is particularly hard & require mores work.

Goal: Reach out to 5+ BTC educational companies & 25+ general Bitcoin companies to gauge level of needs & possible next features.

3. Next Iteration of RPC Feature (product) While we launched the v0.1, it's still extremely limited for everyday use. Curenttly, the main value prop is to use our RPC as a testing sandbox. This is useful occassionally, but not something that a team would use daily.

Goal: Design out next version of RPC feature (v0.2).

setzeus commented 6 months ago

Week 6 (Feb 17th - Feb 23rd) Per our goals for the second round above, the last week focused much more on sales & marketing development than anything else (ie not as much engineering work).

Re: Lessons/Articles Our educational content powers both retention/time spent on site as well as our marketing strategy. Seen here, our first thread that was a direct downstream of an article we published led to ~12k views & 2 new customers. It's clear that we should streamline & automate this process for a weekly publishing cadence. In the next update I'll include the new articles we decided on.

Re: Segmentation Exploration I spent the last two days hammering away on outbound DMs to relevant users that already follow our twitter account. We still haven't hit the goal above of 35+ entities; however, we are very happy to announce that some of these ideal entities have already contacted us back & we've had additional user interviews.

setzeus commented 6 months ago

End of Round 2 Recap

Hi ya'll!

It's been an intense/exhilarating ~6 weeks & we're extremely grateful for the experience. The community & energy have been nothing short of electric every step along the way & pushed us forward in many ways.

Below you'll find our checklist for the Round 2 Goals:

βœ… After running a twitter poll & talking to a few community member we planned out the next 26-weeks / 6-months of articles/lessons

Captura de pantalla 2024-02-22 a la(s) 10 09 27β€―p m Captura de pantalla 2024-02-22 a la(s) 10 08 30β€―p m

βœ… We reached out & contacted 25 Bitcoin companies & 5 specifically education-oriented Bitcoin companies to again gauge PMF fit with both - received a few sign-ups but more importantly learned what educators in the space thought of the education market

Captura de pantalla 2024-02-23 a la(s) 7 01 42β€―a m

βœ… While we didn't flesh out every necessary view & state change, we did nail down what we consider to be our most useful, fitting feature based on the rounds of feedback we've done in the previous weeks. Meet the RPC Recipe-Maker (aka any developer can create & spin up their own API endpoint by chaining together multiple RPCs): RPCRecipeSandox - New Recipe RPCRecipeSandox - Blank Captura de pantalla 2024-02-23 a la(s) 10 09 56β€―a m

Further Proof of PMF And that's it! All three of our goals were reached for an intense but successful Round 2! We'd be remiss to close out this section without including other metrics we're particularly proud of. Below, we've included a few KPIs we've tracked that point to us building in the right direction:

Highlight On Time On Page

Captura de pantalla 2024-02-23 a la(s) 7 10 58β€―a m

Highlight On Time On Page

Captura de pantalla 2024-02-23 a la(s) 7 10 20β€―a m

Highlight On User Growth

Captura de pantalla 2024-02-23 a la(s) 7 09 00β€―a m

IMG_7528

In Closing Again, we can't say enough how grateful we are for the opportunity to join TopBuilders, let alone get this far in the competition. We're deeply thankful for Car, Julie, & every mentor & speaker that has come through; additionally, we're deeply thankful for the community cohort as well - best of luck to all & hope to see you in Austin!

For a working demo, please just go ahead & check out BitScript.app.