If you're working on a startup, chances are you've got a lot of internal tools that you've built or are in the process of building. And if you're like most startups, those tools are probably a hot mess.
That doesn’t mean that you’re doing anything wrong. After all, startups are by definition chaotic places. But it does mean that there's a lot of room for improvement when it comes to the way we build and use internal tools.
In the next few years, I expect we'll see some major changes in the way startups approach internal tooling. Here are a few trends I think we'll see:
1. More focus on collaboration and communication
Internal tools have traditionally been single-player experiences, focused on individual productivity. But as startups grow, they need to start paying more attention to collaboration and communication between team members.
This was the original unique value-prop for @Basedash. Traditional database tools are single-player and technical. Basedash is multi-player and non-technical. These multi-player features come in the form of real-time collaboration, shared views & queries, and a team-based activity log.
2. More use of artificial intelligence and machine learning
As artificial intelligence and machine learning become more sophisticated, we'll start to see more internal tools that make use of these technologies. For example, we might see tools that automatically build reports and dashboards before you know you need them, or tools that can perform complex ops workflows with minimal human input.
3. More integration with external data sources
Internal tools are often siloed off from the rest of the company's data, making it difficult to get a complete picture of what's going on. I expect we'll see more tools that integrate with external data sources, such as customer support platforms or financial data providers, to give startups better control over their businesses.
4. More focus on security and privacy
As startups increasingly store sensitive data in the cloud, security and privacy will become more important considerations in the design of internal tools. We'll see more tools that offer features like role-based access controls and user activity logs to help companies keep their data safe from prying eyes.
The trend toward more collaboration-focused, AI-powered, data-driven, and secure internal tools is already well underway. These are all areas that we’re focusing on at @Basedash, where we’re trying to build the future of internal tools. I expect we'll see even more progress in the years to come as startups increasingly recognize the importance of having well-designed and effective internal tooling.
What trends do you think we'll see in the future of internal tools for startups?
Technical database knowledge can be a hurdle. Education can go a long way, but the solution primarily lies in creating user-friendly databases.
A no-code SQL GUI is a user interface that allows you to interact with a database without using code—in the case of most relational databases, this would be Structured Query Language (SQL). No code SQL GUIs are an excellent way for both newbies and SQL veterans to speed up and simplify the process of querying data.
We’re no longer in the times when database manipulation, management, and interpretation were only to be done by admins. It's the 21st century, and both technical and non-technical users should be accommodated when planning database design and access.
An index is a data structure you can add to your SQL database that allows for quick retrieval of certain information. For example, if you have a database of names and phone numbers, an index might be created on the name column so that the database could quickly be searched for a particular student's phone number. You can think of this in the same way that a physical phone book works.
Refactoring our tables to be virutalized was a huge undertaking, with a huge upside. It sped up table performance by 500% and allowed Basedash to load tables that had previously caused the app to crash.
Internal tooling can be a quick solution to satisfy requirements for colleagues that lack the technical knowledge to build their own custom software. Let's look at how we can beyond simply viewing admin panels, audit logs, and simple CRUD operations -- and into the world of building for the end users that work alongside us each day.
There are many different types of internal tools that you can build. You might want to create a reporting tool for your marketing team, or maybe you need a way to quickly get customer data visible for your customer support team. Or, any number of business apps to help your colleagues manipulate data.
Inheritance is a design pattern commonly used in object-oriented programming which allows you to model entities that inherit certain properties or functions from a parent class. This can be incredibly useful for modeling entities which have multiple types, such as different types of activities to show in a feed.
You've built a solid DB, but your colleagues need to edit data without knowing SQL. Here's how to enabler them to make edits:
How we wrote our own utility with Typescript to take the Date primitive and transform it into a string for use inside of Basedash.
In customer support cases, we use Basedash to help get to the bottom of issues. With a bit of browsing, we can pull up Views, find user details, schema, table information, and take a look to see what the issue is.
A breakdown of the process of how the engineers at Basedash added the feature to allow workspaces to restrict signups based off of user email address.
Using our own product to query our databases speeds up our development time and gives us more opportunities to spot new ideas for features and improve our user's experience.
We recently added an easter egg to Basedash which shows ASCII art of our logo in the browser console. Here's how we we able to style our console.log message with CSS.
At Basedash we use Basedash itself for managing, adding, and removing feature flags for our product. These help use beta test new features, catch bugs, and get feedback before shipping new features.
I had the opportunity to chat with Liau Jian Jie, CTO & co-founder of Mobbin and talk about their migration from Firebase to SQL on Supabase earlier this year. Mobbin is a tool for designers to see and track UI flows from mobile applications to help with real-world inspiration for their own design work. I used it personally...
There aren’t many designers out there who would advocate for working with less or no information about the product they’re building. We want to know who is using our product, what their motivations are, what kind of frustrations they might have, what work environment are they in, and what other tools...
Recently, we refactored our codebase at Basedash to fetch our server data with React Query and optimize our REST API calls in the process. The transition to React Query allowed for better code readability and the optimization of our API calls resulted in half the number of data fetching API calls...
Startups can use whatever tools they want to do their job. We're not burdened by legacy contracts, enterprise-wide procurements, existing monolithic workflows, or the burden of training hundreds or thousands of staff for a new tool. We can change workflows on a dime. We can try something new...
See how removing barriers can change the way your team works.
No credit card required