COG supports ERP and enterprise software projects in Addis Ababa, Ethiopia, from requirements and implementation planning to agreed integrations, migration and training.
CLEAR REQUIREMENTS. CONSIDERED DELIVERY.
THE RIGHT START
Connect the processes behind your business.
An enterprise system needs to reflect how information moves between departments. Before choosing or configuring software, it helps to define responsibilities, approvals, reporting needs and the records that different teams share. We work from those requirements to establish a practical implementation scope, including what changes in the business process and what the software must support.
FROM REQUIREMENTS TO HANDOVER
What we can help with.
01
Requirements and workflow mapping
Document the functions and approvals your organisation needs across areas such as finance, inventory, purchasing or operations. Distinguish essential requirements from preferences and identify who will approve each workflow.
02
Implementation and integration
Plan the agreed configuration, connections and access permissions. Assess integration options before assuming that another application can exchange data, and define ownership of shared records and reporting rules.
03
Migration, training and rollout
Agree which historical records to migrate, how to clean and validate them, and who signs off the result. Include user acceptance, role-specific training and a rollout plan with appropriate support arrangements.
A USEFUL FIRST CONVERSATION
Tell us what needs to work better.
These details help us understand the scope and prepare a relevant proposal. Send a brief to info@cog.et or use the contact form.
The departments, workflows and reports the proposed system must support.
Current software, spreadsheets and data sources, including known data-quality problems.
User roles, approval responsibilities and business periods that could affect rollout.
BEFORE YOU START
Your questions, answered.
How do we know which ERP functions our business needs?+
Begin with the processes that are difficult to control or reconcile today. Map their inputs, approvals and outputs, then identify the functions needed to support them. This provides a stronger basis for selection than a long list of features.
Can our existing records be moved into a new system?+
Migration depends on the source data, target structure and quality of the records. The scope should specify what will move, what needs cleaning and how balances or record counts will be checked before approval.
What should an ERP implementation quotation include?+
Look for clear boundaries around configuration, users, integrations, migration, testing, training and support. Software licensing and recurring charges should be identified separately where applicable. Additional workflows or customisations can change the estimate.