I'm intrigued by this as it's a problem we're facing. However, I don't really understand pricing in the context of targeting multi-tenant SaaS companies.
> 3+ agents ($25 per agent/mo thereafter)
What is an agent? Specifically, how are these counted?
> 25+ active tables ($5 per table/mo thereafter)
This is clear and concise, but just doesn't resonate with me as a good lever for pricing. I'm just going to our our data team run a transformation to consolidate tables.
Number of rows/colummns ingested feels a lot more natural to me
> 15+ seats ($10 per user/mo thereafter)
How is a seat defined in the context of multi-tenant Saas?
Let's say company A has 200 employees in our system, but only 5 of them interact with the agent monthly. Are we billed:
* 1 seat - company A
* 200 seats - each employee of Company A
* 5 seats - only the users that interacted with the agent.
> 3+ agents ($25 per agent/mo thereafter)
What is an agent? Specifically, how are these counted?
> 25+ active tables ($5 per table/mo thereafter)
This is clear and concise, but just doesn't resonate with me as a good lever for pricing. I'm just going to our our data team run a transformation to consolidate tables.
Number of rows/colummns ingested feels a lot more natural to me
> 15+ seats ($10 per user/mo thereafter)
How is a seat defined in the context of multi-tenant Saas?
Let's say company A has 200 employees in our system, but only 5 of them interact with the agent monthly. Are we billed:
* 1 seat - company A
* 200 seats - each employee of Company A
* 5 seats - only the users that interacted with the agent.