mstibbard

Is the long-term pricing model seat/usage based? Value based?

Consider how much you want/need to be charging customers in 3-5 years time and work backwards from there. Be open with early customers on these prices. Offer discounts (sometimes even permanent) against these target prices for early customers/design partners.

This appears to be true remote (I.e., globally remote) as long as you are willing/able to have 4 hours overlap with US working hours per day

I’d really like to hear more about this

OpenAPI predates OpenAI by quite some time. OpenAI has adopted usage of OpenAPI.

I do find myself accidentally saying one and meaning the other, in both directions too!

I think that was their point - the rest of the world solved this long ago, it is just the USA that lagged

I would estimate a senior staff engineer to be an L5 or L6 at Google

If you don't already know a tech stack, I'd recommend Elixir & Phoenix (incl. LiveView).

If you DO already know a tech stack then use that one!

Forcing consistent language, runtime, tooling etc is generally a good thing as it reduces ongoing operational burden as well as some retention & hiring dilemmas.

Have you tried supabase?

It looks fantastic, as does the whole product. I’ve been hoping for someone to make a good bank-in-a-box for a long time. Good luck!