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.
Implementation partner LG lugar de gente
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.
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.
LG lugar de gente
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.
A picture of what exists: processes, volumes, integrations and the exceptions nobody documented. This is what turns a deadline into a defensible estimate.
Employee records, history and payroll history from the legacy system to the new platform, with traceable field mapping.
The system set up with the company’s actual rules: collective agreements, pay elements, benefit policies, approval limits and organisational structure.
Every task delivered is checked, with evidence. No delivery is accepted just because it ran without errors.
The cutover run alongside you, with a contingency plan and objective criteria to proceed or roll back.
The critical period after go-live, when real operations ask the hard questions — and the first payroll close happens with us alongside.
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.
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.
What employees can resolve on their own stops becoming an HR ticket: payslips, requests, personal data and documents.
Approvals with a defined path, deadline and owner — so no request sits idle with nobody knowing where.
Eligibility, policies, deductions and vendor reconciliation, tied to what payroll actually processes.
Job architecture, salary bands and grading — the basis of any pay policy that has to be defended.
Workforce cost planning and budget-versus-actual tracking.
HR metrics that answer management questions, not just reports nobody opens.
The bridge between payroll and accounting: cost allocation, cost centres and integration with the finance ERP.
Custom development, including FPw Reports, with the logic visible to whoever maintains it later.
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.
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.
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.
The AI receives structure, never payroll data. The key exists only in process memory and the cost is measured on every call.
Mappings, data dictionary and test scripts are handed over to the client — not kept back as leverage.
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.
Discovery, redesign and standardisation of processes before configuring anything.
Module configuration, ERP integration and data migration.
Reports, automation and the project tools we use day to day.
Hypercare, advanced support, training and continuous improvement.
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.
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.
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.
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.
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.
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.
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.
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.