Purpose
The purpose of this article is to introduce the UNEEVO platform and explain how its different functional areas work together.
Unlike the articles found in the Functional Reference, which explain how to use specific features, this handbook provides a conceptual understanding of the platform, helping users navigate the system more effectively and understand the relationships between modules.
Whether you are implementing UNEEVO for the first time, configuring new functionality, or simply trying to understand where information originates and how it flows across the platform, this handbook should be your starting point.
What is UNEEVO?
UNEEVO is an integrated business management platform designed around specialized modules that support different areas of an organization's operations.
Rather than functioning as isolated applications, these modules share common data and business entities, allowing information to flow naturally across the platform.
This integrated approach eliminates duplicated data, improves consistency, and enables different departments to collaborate using the same source of information.
For example:
-
A Sales Opportunity may become a Project.
-
A Person may become a Resource allocated to that Project.
-
The work performed may generate Billings.
-
Billings may ultimately produce financial information for analysis.
Each module contributes to a broader business process instead of operating independently.
Understanding the UNEEVO Philosophy
UNEEVO follows three fundamental principles.
1. One Platform
All functional areas belong to a single platform.
Instead of maintaining disconnected systems for Sales, Projects, Resources or Billing, UNEEVO centralizes business information within a common environment.
This ensures that information entered once can be reused throughout the platform.
2. Shared Business Entities
Many business objects are shared between modules.
For example:
| Business Entity | Used By |
|---|---|
| Person | People Management, Resources, Projects |
| Company | Sales, Projects, Billing |
| Service | Sales, Projects, Billing |
| Contract | People Management, Resources |
| Opportunity | Sales Management |
| Project | Projects, Resources, Billing |
Understanding these shared entities helps explain why changes in one module may influence another.
3. Connected Business Processes
Business activities rarely begin and end within a single module.
Instead, they evolve across several functional areas.
For example, a typical commercial process may follow this sequence:
Lead
↓ Contact
↓ Account ↓ Opportunity
↓
Estimations ↓ Project ↓ Resource Allocations ↓ Timesheets
↓
Billing
Each stage builds upon the previous one, creating a continuous business process rather than isolated activities.
Understanding the Documentation
The UNEEVO Documentation is organised into complementary sections, each serving a different purpose.
| Section | Purpose |
|---|---|
| Uneevo Product Guide | Explains how UNEEVO is structured, how modules interact and how business information flows across the platform. |
| Functional Reference | Explains individual features, screens, fields and configuration options. |
| Business Scenarios (Future) | Demonstrates complete end-to-end business processes using multiple modules together. |
Depending on your objective, you may begin in different sections.
If you want to understand why a feature exists or how it interacts with the rest of the platform, start with the Uneevo Product Guide.
If you already know what feature you need and simply want to learn how to use it, consult the Functional Reference.
How to Use the Uneevo Product Guide
TheUneevo Product Guide has been designed to answer questions such as:
- How are the different modules connected?
- Which configurations must exist before another module can be used?
- Where does specific information originate?
- Which module owns a particular business entity?
- How does information flow throughout the platform?
- What is the recommended implementation sequence?
Rather than focusing on individual screens, the Uneevo Product Guide explains the relationships and dependencies between the various functional areas.
What You'll Find in Uneevo Product Guide
The Platform is organised into the following sections.
| Article | Description |
|---|---|
| Platform Architecture | Presents a high-level view of the entire UNEEVO platform and its main functional areas. |
| How UNEEVO Works | Explains how each major module interacts with the rest of the platform. |
| Configuration Dependencies | Identifies prerequisite configurations required before using specific modules or features. |
| Core Business Entities | Introduces the main business objects shared throughout UNEEVO. |
| Business Processes | Illustrates common end-to-end workflows across multiple modules. |
| Data Flow | Explains how information is created, shared and consumed throughout the platform. |
| Implementation Roadmap | Recommends a logical sequence for implementing UNEEVO modules. |
| Best Practices | Provides recommendations for maintaining a scalable and consistent implementation. |
| Glossary | Defines key business and functional terminology used throughout the platform. |
Where to Begin
If you are new to UNEEVO, we recommend following the articles in the order presented within this handbook.
The information has been structured progressively:
-
Understand the platform architecture.
-
Learn how the modules interact.
-
Identify configuration dependencies.
-
Explore the main business entities.
-
Understand complete business processes.
-
Dive into the Functional Reference for detailed feature documentation.
Following this approach will provide a solid understanding of both the platform and its functional capabilities before exploring individual features.
Help Center