S.01 / INTERNAL
A custom web application is a browser-based tool built for one specific process your team runs. I build the screen, the record and the report that replace the shared spreadsheet, the email thread and the one person who knows everything.
02 / PROBLEM
The best internal applications don’t need to be huge. They need to fix exactly the bottleneck.
In almost every company there’s an important process held together by a spreadsheet, a shared inbox and someone’s memory. It works until that person goes on holiday, the file gets corrupted or the volume doubles.
The temptation is to look for a platform that does everything. It’s almost never the answer. What changes the daily routine is usually a small tool, built for that specific step, that stores the data once and puts it in front of whoever needs it.
03 / SIGNALS
Each one costs little on its own. Together they add up to hours every week and mistakes nobody sees until it’s too late.
04 / FIT
When you can point at the bottleneck.
05 / WHAT I BUILD
Back offices, daily work screens, approval workflows and reports. Small, well-made pieces, each already in use in a real tool.
A structured database instead of versions of a spreadsheet: each piece of data is entered once and everyone sees the same one.
EvidenceRocio.com
Tables with filters, side panels and bulk actions designed for the ten things the team does every day.
A back office to run content or operations without depending on a technician or on a tool built for something else.
EvidenceRocio.com
Who changed what and when. A snapshot before every save so you can roll back without drama.
EvidenceRocio.com
The report someone used to prepare on Monday is generated automatically, with the actions that need attention first.
EvidenceAtalayaIQ
Who proposes, who approves and what the system checks before accepting anything. Each person sees and changes only what they should.
06 / ARCHITECTURE
The application starts at the step that hurts and only grows where it proves necessary.
The exact step where time is lost or mistakes are made.
The data in a structured database, validated on entry.
The view the team uses to deal with that step.
Who can see, change or approve, and what was logged.
What used to be prepared by hand, already prepared.
07 / EVIDENCE
A report for management and an editorial panel for one person who approves everything.
Business intelligence
The report management needed every day, generated from the real data instead of assembled by hand.
STACK Nuxt / Vue / MySQL
Case study: AtalayaIQ
Editorial platform
A custom editorial panel that makes a huge archive manageable when one person approves everything that gets published.
STACK Nuxt / Vue / MySQL
Case study: Rocio.com08 / DON'T BUILD
Sometimes the best internal tool is a well-configured one you already pay for.
09 / QUESTIONS
A tool that runs in the browser, built for a specific process in your company instead of adapted from a generic product. When your team uses it rather than your customers, it’s an internal application: a management panel, a back office, an internal CRM, an approval workflow or an automated report, with authenticated access and running on your data.
A web application isn’t installed: it opens in the browser on a computer, tablet or phone, and updates for everyone at once. For internal tools it’s usually the best option; a native app only pays off if people need to work offline for hours or use device features the browser doesn’t offer.
Excel is excellent for thinking and poor for operating across several people: it has no fine-grained permissions, doesn’t validate input, keeps no useful history and breaks with one badly copied formula. When a spreadsheet holds up a critical process, it’s already a system, just without a system’s safeguards.
They’re a good option for prototypes and simple processes. They make sense while the process fits their building blocks; once you have your own rules, volume or delicate integrations, they tend to become another workaround.
The minimum that removes the bottleneck. The best internal applications often don’t need to be large: one table, one record view and one action done well already change the daily routine. The rest is added when it proves necessary.
Yes, if they offer a way in: an API, a database or exports. Often the internal application is exactly the missing piece between two tools that already work.
Custom software and integrations10 / SAME SYSTEM
A business problem rarely lives in a single piece. These usually appear in the same project.
Tell me the process, who does it, where it gets stuck and what would happen if that person weren’t there tomorrow. That’s enough to know what tool you need.