Service
Bespoke operational tools
Design and build of tools focused on real processes: beneficiaries, projects, contacts, time tracking, administration, permissions, auditing and exports.
Expected outcomes
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.
Related experience
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.
Related work
Anonymised examples
Go deeper
Related articles
Working with AI assistants without losing the thread: rules and memory in the repository
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.
Working method with AILayered security for small internal tools: identity at the edge and failing closed
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.
Security of internal toolsFrom PDF to reviewed data: fingerprint, evidence and review queue
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.
Document automationDoes this fit your situation?
Briefly describe the operational, data or AI problem. The first reply can help to guide the type of diagnostic.