Architecture & interior design since 2005
Archas brought project and workforce operations into one internal OS.
Arenyx designed and built a role-separated operating environment for the 23-person architecture practice, connecting project records, contract stages, tasks, time, calendars and selected automations without turning the system into another isolated tool. Archas estimates that the new operating structure reclaims approximately 30 hours each week.
- Discipline
- Architecture & interiors
- Firm size
- 23 people
- Duration
- 14 weeks
- Stages covered
- Architecture → Automate
- Client
- UAB Archas
One operational layer for the company, not a collection of disconnected features.
The brief covered both sides of the practice: the records behind project delivery and the daily work around people, tasks, time and availability. Managers needed company-wide control; employees needed clear, scoped views. Both had to work from the same underlying record.
A company-specific core, then the workflows that rely on it.
We built protected manager and employee environments over one shared data model. Each role sees the work it needs without creating a second version of the company record.
Project records bring together the client, team, contract parts, acts, subcontractors and the operational finance views used by management.
Employees manage assigned and personal tasks, record time and work from a shared calendar. Managers receive the corresponding workload and team-time views.
Form submissions pass through mapped workflows into the OS, where requests are validated, recorded and routed to the people responsible for approving or acting on them.
The system changed where real use exposed friction.
Release records show how specific behaviours were corrected during implementation. These are verified software changes, not estimated time savings.
Navigate through the calendar one month at a time.
Enter the exact date directly in YYYY-MM-DD format.
A management account without an employee record could not open the request.
Management access no longer depends on a linked employee record.
Completion removed the task and its working history.
Completion retains a dated record that can be queried, restored or archived.
A missed release notice could disappear before it was read.
A missed notice is presented again after a later login.
One operating environment. Around 30 hours back each week.
Archas reports approximately 30 hours of operational time reclaimed each week. The figure is presented as a client-confirmed estimate, alongside the delivered system scope rather than as a time-study measurement.
Project delivery and workforce operations share one operational foundation.
Reclaimed across recurring coordination and operational work each week.
Manager and employee views work from the same underlying company record.
Built as Archas infrastructure, not as a generic product wearing the firm's name.
The implementation is backed by a company roadmap, database design, workflow blueprints, deployment instructions and a technical handoff record. Each layer was shaped around the roles and records the practice actually uses.
Start with the operation, then build the system.
Tell us where projects, people and approvals live today. We will map the structure underneath them and show you what belongs in one dependable operating environment.
Book your audit