Case study · Enterprise systems

Custom Internal ERP System and Multilingual Corporate Website Development

Introduction

SLAtech developed its own internal ERP system to manage business operations, alongside a multilingual corporate website to present the company's services. Development of the internal system began in 2008, driven by the need to manage projects, employees, tasks, working hours, financial obligations, payments, and client website hosting and maintenance within a single environment.

The system was designed around the actual workflows of a software development company rather than adapted from an off-the-shelf product. It combined operational and financial management, role-based permissions, automation, accounting integration, client website monitoring, and email communication.

Alongside the internal system, SLAtech developed a corporate website in Hebrew, English, and Russian, featuring service information, company content, a contact form, and content management capabilities.

The project demonstrates SLAtech's approach to custom business software: connecting everyday operational requirements with business logic, structured data, user interfaces, and external services.

The Challenge: Bringing Business Operations into One System

Running a software development company requires continuous coordination between clients, projects, tasks, employees, working hours, financial obligations, payments, and recurring services.

When this information is distributed across spreadsheets, emails, and separate tools, maintaining a complete picture of business operations becomes difficult.

The goal was to create a centralized environment capable of:

  • Managing clients and contact persons.
  • Creating projects, tracking statuses, and assigning employees.
  • Managing tasks, deadlines, and work estimates.
  • Recording actual working hours by employee and project.
  • Tracking financial obligations, outstanding balances, and payments.
  • Integrating operational data with accounting software.
  • Managing website hosting services and recurring renewals.
  • Monitoring client websites and identifying technical problems.
  • Generating alerts for critical errors.
  • Sending emails and processing delivery events and incoming messages.
  • Giving clients access to their own project information.

The project also required a multilingual public website to present SLAtech's services and receive inquiries from prospective clients.

The Solution: A Custom ERP System and Integrated Corporate Website

SLAtech built a dedicated management system combining interfaces for managers, employees, and clients with project management, task tracking, time recording, financial management, hosting administration, and website monitoring.

The application was developed using a layered architecture that separates data access, business logic, user interfaces, and shared services.

The public website and internal management interface used common software infrastructure while supporting different workflows and audiences.

Client and Contact Management

The system maintains company records containing contact information, addresses, telephone numbers, websites, and related details.

Each company can have multiple contact persons, with their names, telephone numbers, and email addresses.

Client records provide a common reference point for projects, tasks, financial obligations, payments, and hosting services.

This structure connects operational and financial information to the relevant client instead of distributing it across unrelated tools.

Project and Task Management

Project Creation and Status Tracking

Each project can contain information such as the associated company, project name, payment method, price, estimated working hours, and current status.

Supported project statuses include:

  • Negotiation.
  • Not started.
  • In development.
  • Waiting.
  • Development completed.
  • Cancelled.

When a project is completed or cancelled, the system automatically closes the associated employee assignments.

Employee Assignments

Managers can assign employees to projects, add notes, and control whether assignments are active.

Employees can access the projects assigned to them.

The system displays each employee's project list and accumulated working hours.

Task Management

Projects can contain individual tasks with:

  • A responsible employee.
  • A planned completion date.
  • Estimated working hours.
  • A monetary amount.
  • Task details.
  • A status.

Administrators can update task statuses, manage task records, and retrieve detailed information when needed.

This connects project-level planning with the individual activities required to complete the work.

Real-Time Working Hours Tracking

One of the system's central features is a time-tracking mechanism integrated directly into the management interface.

An employee selects an active project and clicks a button to start working.

The system records the starting time and displays a running timer.

When the work session ends, another click closes the time entry.

Time Summaries by Employee and Project

The system calculates accumulated working hours and displays them within employee and project records.

These summaries help managers review actual work performed, understand the distribution of employee time, and monitor project activity.

Integrating time recording into the working interface eliminates the need to switch to a separate time-tracking application.

Role-Based Permissions and Client Portal

The system provides access based on user roles and project associations.

Managers can view all projects and manage operations.

Employees can view the projects assigned to them.

Clients can sign in to a dedicated area showing projects belonging to their company.

This structure allows employees, managers, and clients to use the same underlying platform while restricting access to information according to their roles.

Financial Obligations, Outstanding Balances, and Payments

The system includes tools for tracking financial information associated with clients and projects.

Outstanding Balance Records

Each debt record can be associated with a company, project, and task, together with an amount, VAT information, and notes.

The management interface displays outstanding balances and financial totals, including totals before VAT.

Financial Obligations and Recurring Payments

The system includes a data structure for tracking client financial obligations and recurring subscription payments.

This allows recurring financial commitments to be represented alongside one-time project-related charges.

Payment Records

Payment entries can include the company, date, amount, tax document number and date, associated project or task, working hours, and notes.

The system provides payment lists and accumulated totals.

Accounting System API Integration

Accounting and the issuance of accounting documents were handled through an external accounting system.

SLAtech integrated its internal management system with that system through an API, connecting operational and financial records with the external accounting platform.

The internal ERP was designed to manage business operations and financial tracking rather than replace the dedicated accounting system.

Automated Payment Reminders

The system supports automatic reminders for unpaid balances.

This reduces the need to manually follow up on every outstanding financial obligation.

Client Website Hosting Management

SLAtech also developed functionality for managing hosting services provided to its clients.

Each hosting record contains information such as:

  • Domain name.
  • Associated client.
  • Monthly hosting price.
  • Billing currency.
  • Active status.
  • Additional service details.

The system supports pricing in Israeli shekels and US dollars.

It also generates automatic reminders for hosting renewals.

This makes it possible to manage ongoing hosting and maintenance services alongside individual development projects.

Client Website Monitoring and Critical Error Alerts

Beyond project administration, SLAtech developed a centralized technical monitoring infrastructure for client websites.

The monitoring system combined automated availability checks, error collection, website status monitoring, and critical error alerts.

Centralized Error Collection

Client websites could send error reports to a central service.

The collected information included technical details such as:

  • The page where an error occurred.
  • The error message.
  • The location of the error in the application code.
  • Relevant request and user information.

The system also filtered recognized background events that did not require action.

Automated Availability Checks

In addition to receiving error reports, the platform performed automated checks of client website availability.

These checks supported proactive monitoring rather than relying exclusively on errors reported by individual websites.

Critical Error Notifications

When critical errors were detected, the system used alerting mechanisms to support timely investigation and response.

Error Management Interface

Managers could select a domain, review error records, inspect technical details, refresh the list, and clear records.

SLAtech's own corporate website also used the centralized reporting service for unhandled application errors.

Email Infrastructure and Incoming Mail Processing

The system included communication mechanisms supporting everyday business operations and automated processes.

Outgoing Email

The email infrastructure supported multiple recipients, email address validation, attachments, and both right-to-left and left-to-right text direction.

Messages were sent through an external email service, with activity recorded in the application.

Email Delivery Event Processing

A dedicated receiver handled notifications and events from the external email service, including delivery statuses, delivery failures, and other messaging events.

The events were recorded in application logs for tracking and operational review.

Incoming Message Processing

The system also included a fully utilized component that connected to the company mailbox for automatically reading and processing incoming messages.

Together, outgoing email, delivery-event processing, and incoming message handling extended the platform's communication capabilities beyond basic email sending.

Multilingual Corporate Website Development

Alongside the internal ERP, SLAtech developed a public corporate website to present its services and receive inquiries.

Services and Company Information

The website included pages describing services such as:

  • Website and portal development.
  • Custom software development.
  • E-commerce solutions.
  • Application development.
  • Database development.
  • Hosting and infrastructure.
  • Additional digital services.

It also included information about the company, clients, and areas of expertise.

Three-Language Support

The public website supported three languages:

  • Hebrew, with right-to-left layout.
  • English.
  • Russian.

The internal ERP and administrative interfaces, by contrast, operated exclusively in Hebrew with RTL support.

Contact Form

The corporate website included an inquiry form with sender details and a message subject.

Submissions were stored in the system and sent by email, along with information about the originating page and referral source.

The form also incorporated protection against automated submissions.

Content Management

The administration interface allowed website content to be updated through a visual editor without modifying application code.

This enabled the team to maintain public-facing content as part of the company's existing management environment.

Technical Implementation

The solution was developed as custom software with a clear separation between data access, business logic, user interfaces, and shared services.

Data Management

The data layer included entities for companies, contacts, users, employees, projects, tasks, working hours, debts, obligations, payments, hosting services, inquiries, and application events.

Business Logic

The business logic layer handled operations such as employee assignments, status changes, time calculations, financial records, reminders, and permissions.

Shared Services

The system included reusable components for caching, configurable value lists, files, images, email, website addresses, and security.

Lists such as project statuses, payment types, and currencies were stored in the database and loaded into cache.

File and Image Management

File management components supported structured storage using identifiers, together with image resizing and cropping operations.

Security

The application included email-and-password authentication, a remembered sign-in mechanism, and redirection to secure addresses.

External Integrations

The system incorporated:

  • Accounting system API integration.
  • An external email delivery service.
  • Email delivery and failure notifications.
  • The company mailbox for automated incoming message processing.
  • Centralized website monitoring and error collection.

System Architecture

The architecture was organized into separate layers.

User interface layer: The corporate website, manager and employee interfaces, and client portal.

Business logic layer: Project and task management, time tracking, financial records, reminders, and authorization.

Data layer: Business entities, operational records, client information, and application event logs.

Shared services layer: Email, files, images, caching, security, and supporting utilities.

Integration layer: Accounting software, external email services, the company mailbox, and website monitoring mechanisms.

This separation enabled common infrastructure to be reused across the corporate website and internal management application while maintaining workflows and permissions appropriate to each audience.

The Result: A Unified Environment for Business Operations

SLAtech developed an internal management system that brought operational, technical, and financial workflows together.

For managers, the system provided centralized information about clients, projects, tasks, working hours, outstanding balances, and payments.

For employees, it provided access to assigned projects and integrated working-hours tracking.

For clients, it provided a dedicated area for viewing their company's projects.

For technical operations, it introduced hosting administration, automated availability monitoring, centralized error reporting, and critical error alerts.

For marketing and business communication, SLAtech built a three-language corporate website with content management and an inquiry form.

Over time, the experience and development of the internal system contributed to the evolution of a separate SaaS product, SLAtech Vantage.

This case study focuses on the original internal ERP system and corporate website, not the later SaaS product.

SLAtech Expertise Demonstrated

Custom ERP development: Designing business management software around actual operational workflows.

Project and resource management: Combining employees, assignments, tasks, project statuses, and time tracking.

Operational financial management: Tracking outstanding balances, obligations, and payments with accounting system integration.

Business process automation: Automated reminders, recurring operations, and email processing.

Website monitoring: Availability checks, error collection, and critical error notifications.

API integrations: Connecting internal business software with external services.

Modular software architecture: Separating data access, business logic, interfaces, and shared components.

Multilingual website development: Building a corporate website in Hebrew, English, and Russian, including RTL support.

Frequently Asked Questions

What kind of internal ERP system did SLAtech develop?

SLAtech developed an internal management system covering clients, projects, tasks, employees, working hours, financial obligations, payments, website hosting, and technical monitoring.

When did development of the system begin?

Development began in 2008.

How does the system track working hours?

Employees select a project and start time recording with one click. When work is completed, they close the entry, and the system calculates hours by employee and project.

Was the system integrated with accounting software?

Yes. The internal system was integrated through an API with an external accounting system, which handled accounting and the issuance of accounting documents.

Did the system support recurring financial obligations?

The system included a data structure for managing client financial obligations and recurring subscription payments.

Did the system monitor client websites?

Yes. It included automated availability checks, centralized error collection, event logging, and critical error alerts.

Did the system process incoming email?

Yes. A dedicated component was used to automatically read and process incoming messages from the company mailbox.

Which languages were supported?

The public corporate website supported Hebrew, English, and Russian. The internal management system and administrative interface operated exclusively in Hebrew.

Is SLAtech Vantage the same project?

No. The internal management system later evolved into a separate SaaS product called SLAtech Vantage. This case study describes the original ERP system and corporate website.

Does SLAtech develop custom ERP systems?

Yes. SLAtech develops business management software combining workflows, permissions, automation, integrations, structured data, and tailored user interfaces.

Need an ERP System Built Around Your Business?

Effective business software should reflect the way an organization actually operates, from managing clients and projects to handling payments, automated workflows, and external integrations.

SLAtech designs and develops custom ERP systems and business software with an emphasis on practical workflows, maintainable architecture, and future extensibility.

Have a business process that requires a dedicated software solution?

Tell us what your organization needs to manage, and we can explore how to turn those requirements into a purpose-built system.