Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📈 Vizualise an estimated cost model that compares the project to the status-quo model #5

Open
Tracked by #2
janhalen opened this issue Dec 18, 2024 · 3 comments
Assignees

Comments

@janhalen
Copy link
Collaborator

janhalen commented Dec 18, 2024

Vizualise an estimated cost model for accumulated costs on an investment in the collector project vs. buying tight-coupled integrations each time.

@janhalen janhalen self-assigned this Dec 18, 2024
@janhalen janhalen changed the title Vizualise an estimated cost model that compares the project to the status-quo model 📈 Vizualise an estimated cost model that compares the project to the status-quo model Dec 18, 2024
@janhalen
Copy link
Collaborator Author

janhalen commented Dec 18, 2024

@TroelsRanum: I know you are eager getting some break even graphs 📈 .. We could work on this in a couple of different ways:

  1. We guestimate some cost ranges for the current integrations and the projected costs for a "connector" investment in PoC and MvP phases. I render a arbitrary graph that is mostly illustrative of conceived scenarios.
  2. We invest time in digging out real numbers, getting supplier quotes and present a dataset and break-even graph much later in this process, but based on real historical data and supplier quotes.
  3. A combination where we correct the dataset later when we get it, and makes an effort to stress the eastimation basis for the estimates on the first version of the illustrations?

Let me know what you think, how should we move ahead?

@TroelsRanum
Copy link

TroelsRanum commented Dec 19, 2024

I would prefer number 3 that way we have something to show pretty early in the process, and we can use the version to correct as a backwards businesscase. My office really likes that.

@janhalen
Copy link
Collaborator Author

Roger!

I hope to have the first version ready for a demo at our next physical meetup in january! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants