问HN：作为员工向我工作的公司销售软件
我在英国工作，担任部门A的软件/自动化工程师。最近，部门B从一家知名公司购买了一款软件，该软件使用YAML文件来控制自动化框架（可以理解为基础设施即代码）。我并不与部门B的任何人合作，但他们向几个不同的部门（包括我所在的部门）展示了他们的新软件，因此我了解了这款软件。在演示过程中提到，虽然通过YAML文件控制一切非常棒（得益于Git版本控制、Webhook等），但由于需要更改单个值的地方太多，管理数百个文件和代码行将会很困难。在讨论中提到，该公司并没有计划创建任何前端来管理这些文件，这让许多利益相关者感到不满。尽管软件已经购买，仍然会进行推广。
我认为这是一个介入并提出为该工具创建前端想法的机会，但我不想无偿付出。由于我并不直接在这个部门工作，我不确定该如何着手。也许我应该先创建一个最小可行产品（MVP），然后与一些利益相关者接触，看看他们是否感兴趣？
查看原文
I am based in the UK. I work as a software/automation engineer in department A. Recently, department B bought software from a big-name company which uses yaml files to steer/control automation framework (think IaC). I don't work for/with anyone in dep. B, but they showcased their new software to few different departments (including mine) - hence I learnt about that software. Now, during presentation, it came up that while controlling everything through YAML files is amazing (thanks to git versioning, webhooks etc.) it was brought up that manging 100s of files and lines of code will be difficult due to amount of places to change single value. When discussed, it was stated that there is no plans to create any frontend by that company to manage all those files and this seemed to upset a lot of stakeholders. The software has been purchased and it's going to be rolled out anyway.<p>I see this as an opportunity to step in and sell the idea of creating frontend for this tool, however I don't want to do anything for free. Since I don't work in this department directly, I don't know how I should approach this. Perhpas I should create MVP first and engage with some stakeholders and see if they are interested?