Why implementation projects stall on client data

Implementation projects stall on client data when the client's systems define the same figures differently and nobody owns the decision about which definition is right. The software can be configured on schedule. The data can't be migrated, tested or trusted until those definitions are agreed. Partners who make definitions a workstream from discovery keep projects moving.

Most delays blamed on data quality are really delays in agreeing what the data means.

Where projects stall

1. Discovery. The first weeks go to explaining why the same number differs across reports.

2. Design. The new chart of accounts, product catalog or customer structure can't be finalized until old definitions are understood.

3. Migration. Every mapping call needs someone on the client side to decide, and nobody has the authority.

4. Testing. User acceptance testing finds that reports don't tie out to the old system.

5. AI pilots. A proof of concept gives answers finance won't accept, and the next phase doesn't get funded.

What it costs the partner

1. Change orders the client resents.
2. Delayed go-live dates and the margin they consume.
3. A reference that's harder to win.
4. Follow-on work that never gets approved.

How to prevent it

1. Make definitions a workstream. Scope it in discovery, not as a fix in testing.
2. Name client owners. One accountable business owner for each key figure.
3. Record every mapping decision. Who made it, when and why.
4. Test figures, not just totals. Compare key figures on old and new systems before cutover.
5. Hand over the record. Leave the client with approved definitions they can maintain.

How Preql helps

Preql's agents scan a client's systems to find how each one represents the same business concept and propose shared definitions. The client's business owners approve them, and every change is versioned with an audit trail and lineage. Preql works with existing systems, in the cloud or within the client's environment, and inherits existing access controls.

FAQ

Does this replace our implementation methodology?

No. It gives the definitions workstream a place to live and a record the client keeps.

When should it start?

In discovery, before design decisions depend on definitions nobody has agreed.

Who owns the definitions?

The client's business owners. The partner facilitates the decisions and records them.