Custom Internal Tools for Operations Teams

What operations teams actually need from an internal tool

Operations teams rarely ask for software. They ask for the spreadsheet to stop breaking, the approval email chain to go away, and a screen that shows what is happening right now without exporting three reports. Internal tools are the software that answers those requests, and Tepia builds them for companies whose workflows have outgrown the general purpose tools they started with.

The recurring patterns Tepia sees are an operations dashboard pulling from two or more systems of record, an approval workflow with rules (purchase orders, time off, discounts, credit holds), an inventory or asset tracker with barcode scanning, a scheduling tool for crews, rooms or equipment, and an admin panel that sits behind a customer facing mobile app. Most companies need two or three of these, connected to each other and to the CRM, ERP or accounting system they already run.

Tepia approaches an internal tool the way it approaches a consumer app: the people using it all day deserve software that is fast, clear and engineered for retention. An internal tool that staff route around in a spreadsheet has failed no matter how complete its feature list.

Low code platforms versus custom internal tools

Tepia is direct about this: Retool, Airtable, Softr, Glide and similar platforms are the right choice for a large share of internal tools, and you should try one before commissioning custom software. The question is not which is better in general but where each stops fitting. The table below reflects what Tepia tells buyers in the first conversation.

Tepia’s rule of thumb: if the tool serves one team, touches one or two systems and has no external users, start on low code. If it serves three or more departments, enforces rules that change by role or region, needs to work on a phone in the field, or will be used by customers or vendors, build it. The low code versus custom page goes deeper on thresholds.

Internal tool modules Tepia builds most often

Internal tools are assembled from a small set of modules. Tepia scopes each one during Discovery so you pay for the workflows you have, not a generic platform.

• Operations dashboards. Live views combining orders, tickets, inventory or field status from your existing systems, with drill down and export. Built in React with a Node.js, .NET or Python backend on PostgreSQL.
• Approval workflows. Configurable chains with thresholds, delegation, escalation timers and a full audit trail. Notifications by email through SendGrid, SMS through Twilio, or Slack and Teams.
• Inventory and asset tracking. Barcode and QR scanning from a phone, cycle counts, transfers between locations, reorder alerts, and sync to QuickBooks or your ERP.
• Scheduling. Crews, rooms, vehicles or equipment with conflict detection, capacity rules and a mobile view for the people being scheduled.
• Tepia built this pattern for Maximum Controls, pairing iOS and Android apps with an admin portal for gate control and access.
• Reporting. Scheduled reports, saved views and exports your finance team can reconcile.

When a tool needs AI, Tepia adds it as a service alongside the core workflow: document extraction, ticket classification or natural language search over your records using OpenAI or Anthropic model APIs with retrieval augmented generation. See AI integration services.

How Tepia approaches custom internal tools development

Tepia’s six phase process is built for this kind of work because internal tools live or die on whether they match the real workflow. Discovery starts with a system investigation of the spreadsheets, forms and systems your team uses today, then user interviews with the operators, approvers and managers who will use the tool. Tepia also reviews every third party integration (CRM, ERP, accounting, messaging). Deliverables are an Investigation Summary, an Interview Summary and User Stories that describe each workflow in the operators’ own terms.

Design produces wireframes for every screen and role before any code is written, plus a style guide so the tool looks like it belongs to your company. For internal tools Tepia keeps design lean and spends the time on information density, keyboard flow and the handful of screens staff will open fifty times a day.

Development and Testing runs on Alpha and Beta schedules with a test plan that includes user acceptance testing by the actual operations team. Training is hands on, in person or remote, built around user story scenarios. Launch covers data migration from spreadsheets or the outgoing tool, the transition period, and Tepia support reps on the rollout.

Every engagement has an assigned Tepia project manager, with US based design and engineering leadership and engineers working in US hours. The full process is at tepia.co/process.

What to prepare before you talk to Tepia

You will get a sharper estimate from Tepia if you bring four things to the first call. First, the spreadsheet or tool you are replacing, with a sense of how many records and how many people touch it. Second, a list of systems the tool must read from or write to. Third, the roles involved and who approves what. Fourth, the one metric you expect the tool to move, such as hours of manual entry per week, approval turnaround time or inventory accuracy.

Tepia clients report roughly 20% revenue increase after adding mobile to their operations, and internal tools are often where that starts, because the data an ops team cleans up becomes the foundation for customer facing products later. Examples of Tepia’s work are at tepia.co/our-work, and the complete service list is at tepia.co/services.

Frequently asked questions