Internal software
Files, projects, documentation, tasks, approvals and dashboards with your organisation's permissions and statuses.
04 · Bespoke development
Internal tools, field applications and mobile products designed around the way your company works, not the other way round. Engineers who understand the project file, the site and the contract, writing the software that manages them.
Developed by Civiltek
The software we developed for the photovoltaic sector replaces spreadsheets, folders and emails with a single system: from the cadastral reference to the design, the permitting file, the installation works and the finances of each installation.
Sample with example data, with no client files and no connection to the production system.
Developed by Civiltek
We built it to survey a public lighting network while preparing a tender. Today it is the base of the field applications we adapt for concession holders and operators.

Published on the App Store
A nutrition app for iPhone, designed and developed end to end: product, interfaces, data logic, camera capture and publication on the store.
What we develop
We define screens, flows, rules and integrations together with the people who will use the system.
Files, projects, documentation, tasks, approvals and dashboards with your organisation's permissions and statuses.
For internal teams or end customers, with accounts, notifications, camera and publication on the App Store and Google Play.
Classifying documents, answering with sources or preparing drafts, always with human review of decisions.
Copilots →3D scenes, walkthroughs and data on the web, fast on mobile and readable by search engines. This website is the example.
Explore the home page →How we work
We validate the workflows with real users before adding features.
Users, processes, data, integrations and acceptance criteria.
Clickable screens reviewed with the people who will use them.
Working releases with agreed tests for each one.
Data, permissions, training, deployment, support and evolution.
Frequently asked questions
Code ownership, hosting, licences and data export are agreed in writing at the start of the project.
Yes, and that is what we recommend: a first version that solves one specific process, followed by extensions based on actual use.
We review their interfaces and authorisations before committing to the integration; synchronisation and conflict resolution are defined in the scope.
Yes. We agree platforms and devices, prepare the testing and support publication on the App Store and Google Play.
Support, backups, maintenance and evolution under the agreed contract.
Your project
Tell us about the process and who uses it. We will propose a first version with a fixed scope and timeline.