51–60 of 75 posts
I do have some concerns on pricing. $30-40/editor/month is pretty steep! Unless there are good tools for managing swapping users in and out of "reader" vs "editor" states across billing cycles, I think a lot of orgs will balk at this pricing. I know mine will if 98% of our ENG team isn't editing except maybe once a year.
Wow! I absolutely love this! I will have to try it! Better C4 tooling has been something in the back of my mind for a while and this looks pretty polished. I do have some concerns on pricing. $30-40/editor/month is pretty steep! Unless there are good tools for managing swapping users in and out of "reader" vs "editor" states across billing cycles, I think a lot of orgs will balk at this pricing. I know mine will if 9…
We have ideas to increase the capability of readers to make edit suggestions, that can be accepted by an editor. This way you can have some of the more junior team members included in the reader count.
How would this sound for you?
Wow! I absolutely love this! I will have to try it! Better C4 tooling has been something in the back of my mind for a while and this looks pretty polished. I do have some concerns on pricing. $30-40/editor/month is pretty steep! Unless there are good tools for managing swapping users in and out of "reader" vs "editor" states across billing cycles, I think a lot of orgs will balk at this pricing. I know mine will if 9…
Awesome, let us know your thoughts/feedback! We have ideas to increase the capability of readers to make edit suggestions, that can be accepted by an editor. This way you can have some of the more junior team members included in the reader count. How would this sound for you?
Ultimately, I'm not just not sure what the right billing model here is. Obviously, I want to pay a "reasonable amount", but I understand you need that model to have some kind of payment floor. :)
Some major components of usage/pricing that I can think of:
- Domain Owners - some users will be subject matter experts or DRIs that have ownership over parts of the overall model. These are more likely to be editors, but even other engineers may have small tweaks (edit suggestions) for a domain someone owns
- Any given engineering user will probably not be editing for the vast majority of the time. This + your existing pricing model + edit suggestions would lead to "editors" functioning more as just "approvers". It pushes an org to have a handful of approvers and the rest of their users as commenters.
- high price anchoring - $40/user/month sounds like a lot, even if it's for only a few users. It's also a more complicated user model that makes it more difficult to integrate into IT organizations. It is easier to integrate all users uniformly at a lower price per seat. And if I have 10 people on my team, $4/user/month is the same as having one editor but far more palatable (to me).
Earlier quoted context omitted.
Awesome, let us know your thoughts/feedback! We have ideas to increase the capability of readers to make edit suggestions, that can be accepted by an editor. This way you can have some of the more junior team members included in the reader count. How would this sound for you?
That's a good start! Ultimately, I'm not just not sure what the right billing model here is. Obviously, I want to pay a "reasonable amount", but I understand you need that model to have some kind of payment floor. :) Some major components of usage/pricing that I can think of: - Domain Owners - some users will be subject matter experts or DRIs that have ownership over parts of the overall model. These are more likely…
It would probably be much easier to understand if it was a system I worked on every day.
I found the interactive demo overwhelming and very difficult to unpack. It would probably be much easier to understand if it was a system I worked on every day.
Is the next step creating and updating these diagrams automatically? That dream seems to come up and die in cycles over the years, but it may be possible now depending on the compute platform and network appliances you use. This push to automate by doing interesting things, like reading your network traffic ( https://www.akitasoftware.com/ ), could work here. I'm unsure, as is, how you fix the organizational and huma…