MILabs
Tools

Retool internal tools for small and mid-sized businesses

How Retool builds internal tools for small businesses, and how an AI agency in Sydney sets one up and connects it to existing systems.

Updated 2026-05-31

What Retool is

Retool is a platform for building internal tools. A team uses it to put a working screen on top of the data a business already keeps, such as a customer list, a stock file or a job schedule. Builders assemble pages from prebuilt components like tables, forms and charts, then attach those pages to databases and web services through queries. Retool offers a cloud-hosted service and a self-hosted option, so a business can choose where the application definitions run. The tool is aimed at staff who need an operational interface rather than a public website. Its strength is speed for internal work, and its limit is that every screen still depends on well-kept source data and clear permissions. Many businesses reach for it once spreadsheets become too fragile to share, or when one place is needed to approve, update or look up records. Staff can then work from one screen rather than switching between files.

Retool: official site

Retool in plain language

Internal tools are the screens a business's own staff use to read, update and approve information. Customers never see them. A stock count, a job board or an approval queue often sits in several places at once, and people end up copying figures between them by hand. An internal tool sits on top and presents one working view, so a supervisor can check a delivery without opening three files.

Behind each screen, a button usually runs a small instruction. Pressing Approve might write a status change to a database, while a page load fetches the open orders that fill a table. Retool's model makes that chain visible, which helps a team trace a wrong figure back to the query that produced it. The screen is the surface, and the queries are where the logic lives.

Two decisions shape how well this works over time. The first is which system counts as the source of truth, since the tool can only be as accurate as the records it reads. The second is who may change what, because an approval button anyone can press is a process gap that software cannot close alone.

What businesses use it for

  • Staff dashboards showing live sales, stock or job status drawn from existing databases
  • Sign-off screens for quotes, purchase orders and leave requests
  • Lookup pages where front-desk and phone staff find customer or supplier details
  • Entry forms that write tidy records into the accounting or CRM system
  • Checklists for inspections, handovers and end-of-day close-out

Who it suits

  • Operations leads who want a single screen for records held across several systems
  • Teams that have outgrown shared spreadsheets and need no public-facing app
  • Businesses with a technical person who can look after queries after handover

How MILabs sets it up

MILabs starts by agreeing with the owner or team lead which Retool plan fits the number of people who will build and use the tool. Next, the systems the business runs, such as its accounting package, booking calendar or product database, are connected, with each link tested through read-only access first. Permissions are then set so each role sees only the screens and records it needs. The team agrees who looks after the app once it is live, including who can change queries and who approves new pages. Where the business wants self-hosting, the hosting arrangements are confirmed before anything is connected. The owner keeps a short written record of the connections, roles and owners, so the tool stays understandable after the project closes.

Connects to

Builds it fits

Industries it fits

Retool in practice

In a typical arrangement, the work starts with one operations lead listing the four or five screens that staff open most often. For a wholesale business, that list might include a stock lookup for the counter, a purchase order approval list for the buyer, and a dispatch view for the warehouse lead. Each screen is traced back to its source systems, and those links are tested with read-only access before any page can write.

Building happens in layers. A first page shows data without changing anything, so the owner can check that the numbers match the source. Write actions come later, one at a time, with an approval step wherever money or stock is involved. A purchase order screen might show pending requests, let a manager approve or reject each one, and log the decision. Each new page is reviewed with the people who will use it.

Once live, the tool becomes routine work. Front-desk staff use the lookup page, the buyer clears approvals as they arrive, and the operations lead reviews which queries change. A useful test is whether a new starter can find the right screen and explain what each button does without help. If not, the handover notes need more detail.

good questions, straight answers

Frequently asked questions

Where does Retool store data?
Retool keeps the structure of each app, meaning its pages, queries and settings. The business records stay in the databases, spreadsheets or software the app connects to, so those remain the source of truth. With the self-hosted option, the app definitions run on infrastructure the business controls. MILabs confirms which option applies during setup, so the owner knows where each part lives.
When is Retool the wrong choice?
Retool is a poor fit for a public website, a customer-facing product with heavy branding, or a simple form that a free tool already handles. It also suits teams less well when nobody will own the queries and permissions after launch. In those cases a lighter option or a custom build usually serves better. MILabs says so early, so the business avoids a tool that will need rework.
Can my team use Retool without training?
Staff who use a finished Retool app, such as entering an order or approving a request, usually need only a short walkthrough. Staff who build or change apps need more time, so that work suits one or two people who learn the query and permission model properly. MILabs walks the heaviest users through each screen during handover, and written notes stay with the app for later changes.
Can MILabs build on top of Retool?
Yes. MILabs can build new screens, connect additional data sources and add automations that run alongside an existing Retool app. The work starts from the systems the business already uses and stays within the permissions the owner agrees. Where a need falls outside Retool, MILabs says so and suggests what else fits. MILabs is based in Sydney and works remotely, running sessions by video call.
What does a Retool setup need from me?
Name one owner who decides which records the app shows and who may change them. Have access to each system you want connected, with the login details or API keys ready, and a clear list of which staff roles should see which screens. Sessions by video call let MILabs review each screen with the people who will use it. Describing the daily task in plain terms keeps the first version simple.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.