# Why do software engineers keep using embedded BI tools instead of abandoning them after rollout?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Most internal tools decay. Someone builds it, it works for a quarter, then people quietly go back to spreadsheets. <a class="a a--md" elv="true" href="https://www.g2.com/categories/embedded-business-intelligence">Embedded BI</a> seems to survive that more often than it should, and I'd like to understand why.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"><strong>What appears to keep these tools alive past rollout:</strong></p><ul>
<li>Access to data without leaving the application already open and no separate destination to remember</li>
<li>A measurable drop in ad hoc analytics requests, which makes the data team the tool's advocate</li>
<li>Dashboards a business user can adjust without filing a developer ticket</li>
<li>No more rebuilding the same numbers by hand each reporting cycle</li>
<li>The tool being part of the product rather than adjacent to it, so abandoning it isn't an option</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Platforms where this pattern comes up:</p><ol>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/jaspersoft/reviews"><strong>Jaspersoft</strong></a> — Reduces the reporting burden on development teams, which is a durable reason for engineers to keep it running.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/reveal-2022-05-24/reviews"><strong>Reveal</strong></a> — White-label analytics reduce developer workload while improving engagement, and flat-rate pricing that doesn't punish growing usage.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/sigma-computing-sigma/reviews"><strong>Sigma</strong></a> — Self-service that stays inside IT-approved permissions, so engineers aren't choosing between enabling users and keeping control.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/domo/reviews"><strong>Domo</strong></a> — Distribution through embedded apps, mobile, and assistants keeps it in the path of work rather than requiring a visit.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/amazon-quick/reviews"><strong>Amazon Quick</strong></a> — Already part of the AWS estate for many teams, so it survives by being infrastructure.</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">If your embedded BI tool is still in use a year on, is it because it's good or because removing it would be expensive?</p>

##### Post Metadata
- Posted at: 15 days ago
- Author title: Marketing Executive
- Net upvotes: 1




## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4