2021 Internal Tools Developer Survey Results
Tags: productivity, news, programming
Published: 2021-03-17 23:25:49

During my time leading growth marketing Segment, I remember a handful of engineers spending a few months building a customer dashboard to provide our sales, success, and marketing teams with visibility into product usage, billing, engagement, etc.

This dashboard vastly improved the efficiency of our go-to-market side of the business and was also beautifully designed.

*A LOT* of work went into shipping just this one of many internal tools we used at Segment. And that type of work is often unnoticed by the public.

To shed some light (and recognition) on the engineering effort that goes into building internal tools, we (Retool) asked more than 650 developers.

Here are the summarized results:

**Developers spend more than 30% of their time building internal applications**.

That number jumps to 45% for companies with 5000+ employees. And on top of that, 4 out of 5 teams plan to keep or increase this level of investment over the next 12 months.

*Why are internal tools and apps so important? And why do developers spend so much time on them?* 

We surveyed 650 developers and builders ([see full PDF report here](https://try.retool.com/hubfs/The-State-of-Internal-Tools-2021.pdf)) and they had one clear goal in mind: **making teams across the business more productive.**

> **Note:** The insights in this post were gathered from a public survey of 650 developers and technical leaders in Feb-Mar 2021. Check out our PDF report for a deeper breakdown of respondents by industry, country, and role.


### The case for internal tools
Great customer experiences are often backed by a lot of hard back office work. What might appear as effortless student loans, corporate cards, or distanced learning frequently includes a lot of manual tasks and repetitive operations to get just right.

Companies build internal applications, also known as internal tools or back office apps, to give every team the tooling they need—from static dashboards to weekly scripts—to keep the business moving. At their best, internal apps help teams work the way they want. At their worst, internal apps consume more resources than they hoped to save. In either case, developers are spending a lot of time on internal apps.
![percent of time on internal tools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/02ckqv5gfgiglebxvbts.png)


### COVID increased developer time spent on internal tools
As COVID-19 forced developers to re-evaluate their most important priorities, **87% of developers increased or maintained their time spent** on internal apps in response to the pandemic.

And it’s not strictly developer time being invested. More than **57% of companies reported at least one full-time employee dedicated to internal tools**.
![time spent on internal tools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7oeuzwbbjcyzlge2cbtj.png)

Most of that headcount (42%) ends up being engineers, with some operations, data, product, and design folks, too. As companies grow, that overall investment in internal tools also grows. **77% of companies with 500+ employees have dedicated teams for building and maintaining internal apps**.

From an industry perspective, companies in financial services are the most likely to invest fully in internal apps—**2 out of 3 financial services companies reported a dedicated headcount to internal tools**.
![full time employees](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xn8t20bwjyjfxlvpi0vq.png)

Working in finance often includes sensitive financial data and rigorous manual processes, a recipe that can lead these companies to prefer internal apps over pre-built SaaS (especially in the cloud) for better control over data and workflows.

### What exactly are they building and why?
Developers build internal apps for both technical and non-technical teams, and most of these apps help manage, edit, share, or use the data most relevant to their function—i.e. CRUD on top of your data sources.
![types of internal tools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/akymtwslle5wu3k81xy4.png)

And these internal apps are being created to support several teams. Customer support might need a refund dashboard or an admin panel to update user records in their database. Sales might need a custom CRM for data entry. Engineering might need a PR approval queue connected to GitHub.
![end users of internal tools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ryl9r3s9062v6gb8a5xw.png)

In any case, developers are building a lot of internal apps and, it turns out, they are servicing a large portion of their colleagues. **For companies with >10 employees, 1 in 3 employees are using internal apps a developer has built**. That’s super impactful!

That high usage bar means that it’s more important than ever to be able to measure how these apps are performing, and what return on investment they’re getting. Our survey shows that when it comes to measuring ROI, developers care most about improving employee productivity (54%), reducing business costs (33%), and increasing employee satisfaction (28%).

All together, these ROI metrics suggest developers want to create leverage across teams. But the top challenges they report—time, impact, ownership—reflect the struggle to find balance. Internal apps need to solve big problems across the company without weighing down the developers who build and maintain them.
![internal tool challenges](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ek3qzw1cj36y9g1jklmj.png)



### The technology choices behind internal apps
No matter the size of the company or the industry, **2 out of 3 developers default to building from scratch**, as opposed to using a spreadsheet or a SaaS tool.
![building from scratch](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bvfha4ow5dv488m4qeml.png)

While rolling your own apps (React, Django, etc.) gives developers flexibility and complete control, it’s the most time consuming and resource intensive (obviously). And given that **55% of developers struggle to find the time** to build internal apps in the first place, it’s no surprise that custom-built tooling is not the most loved option available.
![time for building internal tools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/oqm5403r1yzozk8hid43.png)

This is where low and no-code apps come in. These platforms can give developers the flexibility of something home-grown, but without the setup and infrastructure costs that take time and effort. Developers who use low/no code platforms report being more satisfied, successful, and loyal when compared to developers who chose any other technology option for building internal apps.

And while only 38% of developers surveyed actually use low/no code, the **large majority (88%) of those that built internal apps using low/no code plan to keep building this way in the future**.
![developer experience](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/45a96239oiluoyjjf603.png)


### Internal apps are deeply connected
Developers are connecting internal apps to all kinds of data sources—**75% are connected to internal databases**, 67% are connected to internal APIs, and roughly half are connected to 3rd party apps (e.g. Salesforce, HubSpot, Zendesk).
![internal tool extensibility](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/izmsvuthwixhpleeyrbe.png)

This deep integration across a variety of data sources is one of the main benefits of internal apps. By helping teams design how data comes together, developers are helping each team break from tool-centric approaches to actually work the way they want to work.

And as developers at every company continue to build and maintain more and more for internal apps, only time will tell what new technology preferences—and challenges—arise.

---

If you’re interested in seeing a more detailed breakdown of trends and technology preferences, [get the full report here](https://try.retool.com/hubfs/The-State-of-Internal-Tools-2021.pdf). And, if you're interested in building internal tools, [checkout Retool here](https://retool.com).