Luabase is the modern data stack for web3 teams. We make it easy to query any blockchain with SQL, analyze it in notebooks, and embed the data in your app with our API. You can learn more about the product here or read our post here.

We are looking for a Head of Growth & Ops to help us grow Luabase and build our company infrastructure.

What youll be doing at Luabase

• Owning the top of funnel (quality and quantity) for Luabase
  • Running growth experiments that drive users to trial Luabase
  • Doubling down on experiments that work
• Manage our pipeline
  • Book demos / sales calls with promising companies
  • Handle the back-office for closing customers
  • Understand and analyze blockers for customers to convert to paid
• Establishing and expanding partnerships
  • We already have one promising, major partnership in the works and its looking like we can run this playbook with at least 3 or 4 other large partners
• Operations
  • Building and manage our internal tooling (e.g. CRM)
• RevOps
  • Manage plans and pricing in Stripe
  • Analyze product usage and shape our pricing strategy
• Finance
  • Set and manage accounting thru a partner like Pilot

Requirements

• You know SQL (or will learn it) and you like it. Both because our product is so heavily depended on it and because its the best way to understand whats happening with our customers.
• You understand working at a seed stage startup requires wearing a lot of hats and you're not afraid to roll up your sleeves and destroy problems. We don't say thats not my job here, we get shit done.
• You're comfortable hiring and delegating for areas outside your expertise or that are low leverage

Not requirements

• This is not a sales role, but see the thats not my job note above
• Knowledge of SEO at a deep level (e.g. should the H1 for this post be x or y), but you need to be able to hire and manage people that do
• Write a lot of technical content (we have people here at Luabase that can help here)
• Write production code (we don't expect you to be a python dev, but as noted above, you'll be writing a healthy dose of SQL)