# Bespoke operational tools

> Small internal applications for when Excel, forms and disconnected SaaS no longer support the daily work.

- URL: https://www.enter20.com/en/services/bespoke-operational-tools/
- Español: https://www.enter20.com/servicios/herramientas-operativas/
- enter 2.0 — Practical AI, governed data, dashboards, automation and information systems for organisations that need to make better decisions.

Design and build of tools focused on real processes: beneficiaries, projects, contacts, time tracking, administration, permissions, auditing and exports.

## What can remain after the work

- Internal applications with roles, modules and access controls.
- Workflows for creation, editing, review, closure and reporting.
- Integration with existing databases and systems where appropriate.
- User documentation and handover to the team.

## Technical and operational proof

- Modular platforms with Firebase Auth, Supabase/PostgreSQL, React, Vite and React Admin.
- Work on managing people, projects, employees, groups, activities and permissions.
- Practice with Cloudflare and Firebase Hosting deployments and automated Linux environments.

## Anonymised examples

- [Modular operations platform for a foundation](https://www.enter20.com/en/work/foundation-operations-platform/): Design of an internal platform to organise people, projects, modules, permissions and operational reporting without exposing sensitive data.

## Related articles

- [Working with AI assistants without losing the thread: rules and memory in the repository](https://www.enter20.com/en/blog/working-with-ai-assistants-rules-memory-in-repository/) (2026-10-23): If a project's context lives in a tool's chat, it is lost when the tool is closed. If it lives in the repository, any assistant or person can carry on from where the previous one left off.
- [Layered security for small internal tools: identity at the edge and failing closed](https://www.enter20.com/en/blog/layered-security-internal-tools-identity-at-edge-fail-closed/) (2026-10-06): An internal tool does not need a VPN or an exposed server. It needs identity before anything can be reached, a service that fails closed when configuration is missing, and tunnels instead of open ports.
- [From PDF to reviewed data: fingerprint, evidence and review queue](https://www.enter20.com/en/blog/from-pdf-to-reviewed-data-fingerprint-evidence-review-queue/) (2026-09-18): Extracting data from invoices, payslips or calls for proposals is easy to promise and hard to make reliable. Reliability comes from the document's fingerprint, the evidence kept alongside each data point and a review process that does not get in the way.
- [Permissions live in the database, not on the screen](https://www.enter20.com/en/blog/permissions-live-in-the-database-not-the-screen/) (2026-08-13): When several departments or companies share a tool, who sees what must be decided in the database. The interface can fail; a rule on the server does not.
- [From Excel chaos to useful indicators for foundations and SMEs](https://www.enter20.com/en/blog/from-excel-chaos-to-useful-indicators/) (2026-03-24): Excel is not the problem. The problem arises when each spreadsheet defines reality in a different way and nobody knows which figure is authoritative.
- [Dashboards are not the starting point: they are the visible part of the data system](https://www.enter20.com/en/blog/dashboards-are-the-visible-part-of-the-data-system/) (2025-06-20): A useful dashboard depends on processes, definitions, data quality, ownership and review routines that usually sit outside the screen.

## Does this fit your situation?

Briefly describe the operational, data or AI problem. The first reply can help to guide the type of diagnostic.

Contact: [contacta@enter20.com](https://www.enter20.commailto:contacta@enter20.com) · [Contact form](https://www.enter20.com/en/contact/) · [Diagnostic questionnaire](https://evaluo.enter20.com)