CDBAMImplementation Projects

Implementation partner LG lugar de gente

End-to-end HR system implementation, from discovery to hypercare.

We run the whole project: we map the landscape, migrate the data, configure the modules, validate every task delivered and stay alongside you through the critical period after go-live.

Partnership

Implementation partner of LG lugar de gente

We implement the LG lugar de gente platform in end-to-end projects — from technical discovery to hypercare. Knowing the product from the inside is what allows us to configure the company’s actual rules instead of the out-of-the-box defaults, and to anticipate at design stage what usually only surfaces at the first payroll close.

  • Data migration to the LG platform with traceable field mapping and validation on every load.
  • Configuration of the LG modules in line with collective bargaining agreements, benefit policies and the client’s organisational structure.
  • Ongoing support for companies already live on LG: configuration changes, reporting and advanced support.

Discuss an LG project

Implementation partner

LG lugar de gente


  • End-to-end projectsdiscovery, migration, configuration, validation, go-live and hypercare
  • Module coveragepayroll, self-service, workflows, benefits, compensation and job structure, budgeting, analytics and finance integration
  • Companies already liveadvanced support and enhancements, even on projects started by others
The full project

Six phases, one accountable partner

HR system implementations go wrong when each phase has a different owner and nobody is accountable for the whole. We take the entire line — which is why validation is never outsourced to someone else.

Technical discovery

A picture of what exists: processes, volumes, integrations and the exceptions nobody documented. This is what turns a deadline into a defensible estimate.

Data migration

Employee records, history and payroll history from the legacy system to the new platform, with traceable field mapping.

Configuration

The system set up with the company’s actual rules: collective agreements, pay elements, benefit policies, approval limits and organisational structure.

Validation

Every task delivered is checked, with evidence. No delivery is accepted just because it ran without errors.

Go-live

The cutover run alongside you, with a contingency plan and objective criteria to proceed or roll back.

Hypercare

The critical period after go-live, when real operations ask the hard questions — and the first payroll close happens with us alongside.

See each phase in detail

Coverage

The modules we implement

We implement the system the client has already bought, module by module. Payroll is the core — where an implementation error costs the most and where we go deepest. But an HR project does not end there, and neither do we.

Payroll

Pay elements, calculation, statutory contributions, period close and the filings that do not forgive delay. This is where we go deepest — including the migration of payroll history.

Employee Self-Service

What employees can resolve on their own stops becoming an HR ticket: payslips, requests, personal data and documents.

Workflows

Approvals with a defined path, deadline and owner — so no request sits idle with nobody knowing where.

Benefits

Eligibility, policies, deductions and vendor reconciliation, tied to what payroll actually processes.

Compensation & Job Structure

Job architecture, salary bands and grading — the basis of any pay policy that has to be defended.

Workforce Budgeting

Workforce cost planning and budget-versus-actual tracking.

People Analytics

HR metrics that answer management questions, not just reports nobody opens.

Finance Integration

The bridge between payroll and accounting: cost allocation, cost centres and integration with the finance ERP.

Reporting

Custom development, including FPw Reports, with the logic visible to whoever maintains it later.

See the modules in detail

What sets us apart

Validation is not an end-of-project phase

In an HR system implementation, the cost is not in doing the work — it is in finding out weeks later that it was done wrong. That is why every task delivered comes with material proving the result, produced together with the delivery.

  • Evidence kept apart from the deliverable. What goes into production lives in one place; the proof that it checks out, in another. Delivering is not mixing the two.
  • An audit trail that outlives the project. A discrepancy found later becomes a lookup in the documentation, not archaeology.
  • Silent errors caught by design. An unmapped code, a date loaded as text — none of these complain on their own. Our tools complain for them.

See our method

EVERY TASK, TWO OUTPUTS Task delivered DELIVERABLE what goes into production loads, parameters, configuration EVIDENCE what proves it checks out worksheets, test scripts, data dictionary Filed separately, on purpose delivering is not mixing the two
Best practices and intelligent tools

A rule that depends on human discipline fails on a long project

That is why our practices became software. We build our own tools, with artificial intelligence built in, so that the right way to work is the easiest path — not the most laborious one.

  • Evidence is born with the deliverable. It is not possible to generate a data load without generating its reconciliation.
  • Automatic source tracing. One document per project answers, field by field, where every piece of data came from.
  • AI where it genuinely helps: reading logs, assisting in writing rules and resolving the ambiguous residue of tracing — without ever seeing payroll data.

See practices and tools

Silence is a defect

An unmapped code or a date loaded as text will not complain on their own. The tools complain for them, early and with the reason written down.

Intelligence with limits

The AI receives structure, never payroll data. The key exists only in process memory and the cost is measured on every call.

Knowledge that stays

Mappings, data dictionary and test scripts are handed over to the client — not kept back as leverage.

Who we are

Specialists in turning manual work into an auditable process

CDBAM works across HR, payroll and administration, from process design to support after go-live. What sets us apart is not implementation speed — it is what remains afterwards: documentation, evidence and a path someone else can retrace.

To let HR and administration teams focus on what matters, reducing legal risk and operating costs with practical, well-documented solutions.
Our mission

Mapping

Discovery, redesign and standardisation of processes before configuring anything.

Implementation

Module configuration, ERP integration and data migration.

Development

Reports, automation and the project tools we use day to day.

Support

Hypercare, advanced support, training and continuous improvement.

Frequently asked

What clients usually ask before we start

Does CDBAM only implement the payroll module?

No. We do not run our clients’ payroll — we implement the HR system the client has already bought, and we do it in full. Payroll is the core module and where we go deepest, but the scope covers employee self-service, workflows, benefits, compensation and job structure, workforce budgeting, analytics, finance integration and custom reporting.

Do you sell or build the HR system?

No. The software belongs to the platform the client has contracted — we are an implementation partner of LG lugar de gente. What we deliver is the project: discovery, migration, configuration, validation, go-live and support. The client’s own team runs it afterwards, trained by us.

Can we engage just one phase?

Yes. Many projects start with the technical discovery, which delivers value on its own — it is the picture of the landscape and the basis of the plan. We also serve companies already live with advanced support and enhancements only.

What is the hypercare period?

It is the reinforced support right after go-live, when real operations start using the system and the questions no test anticipates begin to appear. We stay through the first payroll close, with an agreed response time.

How do you handle our data?

Payroll is sensitive personal data. Data handled during the project never travels through the cloud or the internet at any stage, and is discarded as soon as it has served the purpose it was used for. We do not keep client databases as an archive, not even after delivery. Access credentials are valid for the working session only and are never written to a file.

Which systems do you migrate from?

Any system from which the data can be obtained — database access, export, text file or spreadsheet. We do not depend on an off-the-shelf connector: if the data can be extracted, it can be migrated.

How do I know the work is correct?

Every task delivered has validation material produced alongside it. For data loads, that means the reconciliation worksheet next to the file; for configuration, the test script and the expected result. Nothing is accepted just because it ran without errors.

Shall we talk about your project?

Tell us where you stand: choosing a system, midway through an implementation, or already live and needing support. We reply with a scope, not a generic quote.