Internal Tools & Automation · In depth
The software your business actually runs on.
For the team drowning in spreadsheets and copy-paste, and the operation that has outgrown its off-the-shelf tools. We build the dashboards, automations, and integrations that run your business behind the scenes.
What counts as an internal tool?
Every business runs on internal processes that were never really designed, they just grew. A spreadsheet quietly became the inventory system; a copy-paste routine became the weekly report. Internal tools are what happens when someone finally designs that layer: software shaped around how your team actually works, built to replace the manual steps rather than add another system nobody opens.
The same discipline covers automation: workflows and scheduled jobs that run without a person watching, and monitoring that tells you when something needs one. And when a step in a workflow calls for AI, classification, extraction, search, we run local models on hardware you control, never third-party AI APIs.
On-premise AI, in depthWhat shapes does it take?
Dashboards and admin panels
One screen that shows the state of the operation, and the controls to act on it. Custom-built, so it shows your numbers, in your terms, instead of a vendor's idea of them.
Workflow automation and scheduled jobs
The steps nobody should be doing by hand: reports that assemble themselves, records that reconcile overnight, handoffs that happen without a reminder. Scheduled, logged, and monitored.
Integrations between the systems you already use
ERP, CRM, and the APIs in between rarely talk to each other out of the box. We build the connective tissue, so data entered once is data entered once.
Data pipelines and decision tools
Real-time pipelines and monitoring for the numbers that matter, and backtesting tools that let you test a decision against your own history before you commit to it.
Why not just buy something?
Sometimes you should. If an off-the-shelf product genuinely fits how you work, buy it; a subscription is cheaper than a build, and we will tell you so in the first call.
Build when the workflow is the business. Off-the-shelf tools serve the average of everyone's process; the parts of yours that do not fit end up back in spreadsheets and manual workarounds, which is where the errors live. A custom tool bends to the process instead of the other way round.
And often it is not either-or. Keep the systems that serve you well and build the connective tissue between them: integrations, automation, and one dashboard across the lot.
What has this looked like in practice?
For a business running greenhouse growing operations and cold-chain freight, we built one platform tying physical sensors to the operational and financial software around them: lot allocation, inventory, and P&L projection on the growing side, real-time visibility of freight on the road, and sensor-driven warnings that surface problems while they are still cheap to fix.
Read the case studyThe same discipline runs our own work. Esoteric Numbers, a production SaaS in 67 languages, stands on internal machinery: Stripe payments, background jobs on Celery, PDF generation as a dedicated service, observability through Sentry and New Relic, and a local model helping maintain translations across every locale.
See Esoteric NumbersHow does a build like this start?
The same way every project here starts: a conversation, a written proposal, a build in the open, and a launch where you own everything. The first call is about 30 minutes, needs no preparation, and costs nothing.
See how we workFAQ
Common questions.
What do you build internal tools with?
We stay largely technology-agnostic and choose what fits the job: TypeScript across the stack, Vue/Nuxt, React/Next or Astro on the front end, Python/Django or Rust on the back end, GraphQL for APIs, and Cloudflare for edge and serverless. When a tool needs AI, we run local models with tools like Ollama.
Can you build on the systems we already use?
Yes. Existing systems are a common starting point: we begin by understanding what is already there, then build the integrations and automation around your ERP, CRM, and the APIs you already rely on, rather than asking you to replace them.
Who owns the tools you build?
You do. The code, the design, the accounts, and the data are all handed over to you in full at launch, so the tool never depends on us to keep running.