Learn what an internal tool is and how companies from different industries use Superblocks to create internal applications for their mission-critical use cases.
An Internal Tool is any internally-facing software developed to support business operations at a company.
On Superblocks, internal tools are built by developers, commonly to enable customer-facing teams to operate more efficiently such as Customer Support, Customer Operations, and Customer Success. Other teams inside the organization like Sales, Marketing, Finance, Engineering, and more can make use of custom internal tools to accelerate their specific workflows tied to their CRM, Marketing Automation, Finance Tooling, or even Git or CI/CD systems.
An internal tool can take many forms. As an Application with a user interface, an internal tool can be a dashboard, a CRM, or a ticketing system. While as a Workflow that automates recurring tasks an internal tool can be used for reporting jobs, to send messages to customers or to update data sources. And as a Scheduled Job that runs on an interval an internal tool can be used to run daily database cleanup jobs, to generate weekly marketing reports, or to send out monthly billing statements.
Use Cases by Industry
Fintech companies need many internal tools to help them comply with the multitude of regulatory mandated processes. Examples of these are tools for underwriting loans, reviewing credit applications with KYC, managing credit cards and reducing Fraud with risk scoring. An Application in Superblocks could be used as an internal tool to check new customers against KYC requirements as part of the onboarding process. Other examples include:
- Credit Card Approval Application to reduce manual effort for Customer Operations
- Customer Compliance Dashboard combining data from different databases for Compliance teams
- AML Monitoring Dashboard for Risk Management teams to comply with regulatory requirements
- Weekly job that updates customer risk scoring data for Fraud Prevention teams
Insurance companies need internal tools to review customer applications, manage claims, and process payouts. A Workflow could be used to process payouts whenever a support agent approves a claim. Other examples include:
- Application to manage claims across different internal tools and databases for Claims Management teams
- Daily email to Operations teams with an overview of all claims received in the last 24 hours
- REST endpoint that sends claim approval notifications to customers when triggered
E-Commerce companies need internal tools to process refunds, manage inventory, track revenue, or to chart growth in orders. A Scheduled Job could be used to send order data to a fulfillment center each day at 6AM. Other examples include:
- Application for Customer Operations teams to refund orders that integrates with Zendesk, Salesforce, and Snowflake
- Scheduled Job resetting coupon codes for Marketing teams every Sunday at 11 p.m.
- REST endpoint that that generates a sales report for Finance teams over different sales channels when triggered
SaaS companies need to aggregate customer data to manage account info, issue invoices, and calculate usage metrics. Support teams could build a Customer Success Dashboard with an Application in Superblocks that gives them quick access to customer account data for a fast and excellent customer support experience. Other internal tools that SaaS companies can build with Superblocks include:
- Customer Success Panel that integrates with various internal APIs to change a billing plan and view customer usage
- Daily Report that pulls data from Slack, Salesforce, and Segment to help the Sales team track Deal progression
- Scheduled Job that notifies Customer Success teams of expiring trials daily at 8 a.m.
DevOps teams need internal tools to track deployment status and monitor versions as they’re deployed to production from a single pane of glass. Other internal tools that DevOps can build with Superblocks include:
- Deployment Tracking Dashboard that unifies data from various external APIs like JIRA, Launch Darkly, and Rundeck
- REST endpoint that sends out a Jenkins pipeline report to Slack when called
- Scheduled Job that triggers CircleCI jobs on a predefined schedule to rerun flaky tests
Instead of wrestling with CLIs, Database Admins can quickly build admin panels for their datastores to read, write, and update their customer data with Tables, Forms, and Charts. With Superblocks, Database Dashboards and CRUD Apps can be built among other things:
- Postgres admin panel with granular permissions to control access across teams
- Dashboard to view the expensive queries across multiple database instances
- REST endpoints with validation rules to prevent direct writes to production databases