A screenshot of the hero section from Bucket's home page

Announcing Bucket 2.0 and our $2m pre-seed round

10 months ago, I released Bucket 1.0, which I was bootstrapping at the time. I got a handful of early customers (<3), but it quickly became obvious that my (somewhat dubious) code wouldn’t be able to handle the load and that Bucket had to mature in order to serve its customers going forward.

The great news, though, was that I was getting product validation and lots of positive feedback, especially from larger organizations. It turns out, once your product team grows past a size of 10, feature evaluation and resource planning becomes a huge pain - and it only compounds as you scale.

During the past decade, the pre-deployment workflow has improved dramatically. Kanban-boards, GitHub PRs, continuous integration, push to deploy, and much more.

But, who owns the features, post-deployment? Are the features successful with its customers, or do they need another iteration to stick? Or do they need to be merged or removed?

Enter Bucket — automated feature evaluation.

Bucket 2.0

Today, we’re thrilled to announce the Early Access launch of Bucket 2.0! We’re just getting started, but Bucket is already the best way to measure and iterate on any feature until it’s successful. It’s built for product managers, engineering managers, engineers and designers.

Bucket works because it’s:

  1. Feature focused
    There’s no “feature” in “product analytics”. Product teams work in the scope of features - not the entire product. Bucket is making the feature a first-class citizen, finally.
  2. Consistent feature engagement tracking
    The Bucket Feature Report is consistent and streamlined, making it simple to track, measure and compare the success of any feature.
  3. Automated and integrated
    Having a dedicated feature report is a big step forward, but evaluating features can take weeks or months. That’s why Bucket plugs into your existing development workflow, so you can keep track of live features, without ever leaving Slack.

If you and your team would like an automated, repeatable approach to evaluating features, please let us know on bucket.co/early-access. We’re keen to work closely with early customers to make sure we get everything right before launching publicly later this year.

Our $2m pre-seed round

We’ve raised a venture round to grow the team, build the best possible product and to support larger organizations. We’ve partnered with the great folks at Creandum, who we were fortunate to work with at Opbeat, and we’ve gotten participation from terrific product and engineering leads from around the world: Justin Gallagher (Trello), Simon Willnauer (Elastic), Johannes Schickling (Prisma), Moritz Plassing (Immuta), Kenneth Auchenberg (Stripe), Manuel Weiß (thisisgoodmarketing), Nick Bruun (EverQuote), Niels Tindbæk (Segment), Phil Chambers (Workday), Deani Hansen (Productboard), Anders Bo Pedersen (Meta), Morten Just (Otato), Gregor Belcec (Synthesia), Jakob Marovt (Synthesia) and Andreas Klinger (Remote First Capital).

Onwards!

PS, we’re hiring! If you’d like to work on Bucket with a small, passionate and experienced team, please reach out!