Data foundation

Good agents need good data. We build that first.

Most organisations hold three versions of every vendor, customer and asset. We set the strategy, build one golden record, and keep it clean — so agents act on facts, not guesses.

Golden record · VendorsIn sync
Where vendors live today
Tally export
1,204 records
SAP vendor master
1,087 records
Procurement spreadsheet
642 records
SharePoint list
310 records
Golden record
Meghna Textiles Ltd
Trade licence
TRAD-014532
Tax number
001234567-0101
Bank
Islami Bank, Gulshan
Found in
3 of 4 systems
Approvedby Farhana Rahman
3,243
source records
2,611
golden records
41
waiting for a steward
Data strategy

Decide what matters, who owns it, and what AI may touch.

Before any agent goes live, we agree which data matters, who is accountable for it, where it must live, and which parts a model may see. The result is a plan your board and your regulator can read.

  • An owner for every domain. A named person, not a department.
  • Rules for AI use. What is allowed, what is masked, what never leaves.
  • A sequence. Start with the domain that unblocks the most work.
Data strategy · Manufacturing groupDraft v3
DomainOwnerMay AI use it?Lives in
VendorsHead of ProcurementYes, bank fields maskedDhaka
ProductionPlant managerYesDhaka
CustomersHead of SalesRules and lookups onlyDhaka
FinancialsChief Financial OfficerSummaries onlyDhaka
Employee recordsHead of HRNoDhaka
How a data strategy runs
  1. 01InventoryWhere each domain lives today.
  2. 02RankWhich gaps block the most work.
  3. 03DraftOwners, rules for AI, residency.
  4. A personSigns off the policy and owners.
  5. 05BuildOne domain at a time.
  6. 06ReviewQuarterly check against real use.
Master data model

One golden record for assets, people, vendors and customers.

A master data model gives every system, app and agent the same definition of a property, a supplier or an employee. It is in production today: a commercial real-estate model for Menkes, version 2.7.9, with 155,000 reference rows, bound to Groundfloor.

Master data model · Commercial real estate (example)v2.7.9
Core entities
Portfolio
Property
Building
Unit & asset
People and parties
People & roles
Vendors
Tenants
Reference data
155k
reference rows in the live Menkes model
Asset classLease typeRegionStatus codesUnits of measure

Entity layout shown here is an example. Names and screens are illustrative.

Defined once

Every field has one meaning, one format and one owner — in English and, where needed, Bangla.

Bound to the apps

On Groundfloor, the model feeds the apps teams use daily: asset inventory, property forms, people and roles, a task inbox.

Versioned

Changes to structure are proposed, approved by a person, and recorded, so you can see what changed and why.

How a master data model is built
  1. 01DiscoverWalk the systems and spreadsheets in use.
  2. 02ModelEntities, fields and reference data.
  3. 03MatchRules find the same thing in different places.
  4. A personApproves the model and each change to it.
  5. 05BindConnect apps and agents to the model.
  6. 06VersionEvery release recorded and reversible.
MDM Manager

Stewards review, merge and approve. In one screen.

Rules find likely duplicates. A data steward sees both records side by side, with the reason for the match, and decides. Nothing changes the master record without sign-off.

MDM Manager · Vendor review41 to review
Queue
Meghna Textiles Ltd
Padma Foods PLC
Rangpur Agro Ltd
Sylhet Tea Estates
Karnaphuli Packaging
Possible duplicate vendor
Matched by rule: same trade licence and tax number
Needs review
TallySAPProposed
NameMeghna Textiles LtdMeghna Textile LimitedMeghna Textiles Ltd
Trade licenceTRAD-014532TRAD-014532TRAD-014532
Tax number001234567-0101001234567-0101001234567-0101
Bank—Islami Bank, GulshanIslami Bank, Gulshan
ContactRezaul KarimR. KarimRezaul Karim
Merge proposal: keep Tally name and contact, take bank from SAP. Retire SAP duplicate V-20931.
Approve mergeRejectEdit fields Master record unchanged until approved
How a change reaches the master record
  1. 01DetectRules flag likely duplicates and gaps.
  2. 02ExplainEach proposal shows why it matched.
  3. A personSteward approves, rejects or edits.
  4. 04MergeMaster updated; old records linked, not deleted.
  5. 05SyncConnected apps and agents see the change.
  6. 06LogWho approved what, and when.
Document AI

Documents become clean data. Read, then verified.

Our File Content Extractor turns PDFs, scans, Word files, spreadsheets, CSV, text, audio and video into text, with an optional model pass for messy pages. Then rules check the result against your master data. Extracted is not the same as trusted.

  • Many formats, one pipeline. The same checks apply whatever the file was.
  • Checked, not trusted. Totals, dates and names are tested; weak fields go to a person.
  • No outside dependency. Runs without a hyperscaler extraction service.
PDFImageWordSpreadsheetCSVTextAudioVideo
Document AI · Supplier invoicesChecking
Incoming
Invoice-0412.pdf
PDF · 2 pages
Proven
Challan scan.jpg
Image · low light
Review
Supplier call.m4a
Audio · 3 min
Proven
Stock-oct.xlsx
Spreadsheet · 3 sheets
Proven
Invoice-0412.pdf
Supplier
Meghna Textiles Ltd
Invoice no.
INV-0412
Total
BDT 1,284,500
Lines add up to the total
Supplier found in master data
Challan scan: 1 field unclear
Sent to a person with the image
How a document is processed
  1. 01ReceiveEmail, upload, scan or folder.
  2. 02ExtractText out of any format; optional model pass.
  3. 03CheckArithmetic and named rules on the result.
  4. 04MatchAgainst vendors, assets and limits.
  5. A personClears anything unproven, evidence attached.
  6. 06StoreClean data to your systems; original kept.
Connect existing systems

Your systems stay where they are. Agents read and write them safely.

Dataplane is one governed layer over your databases, with 16 connectors. Agents act with the signed-in user’s own permissions, so an agent never sees more than the person it works for.

Dataplane · ConnectionsLive
Connected
Finance database
PostgreSQL
Read and write
ERP
SQL Server
Read only
Branch ledger
MySQL
Read only
Request on behalf of
FR
Farhana Rahman
Head of Ops · Dhaka
Dhaka branch rows
Allowed
Salary column
Masked for this role
Chattogram branch rows
Not permitted
What it connects to
  • PostgreSQL
  • SQL Server
  • MySQL
  • Oracle
  • SAP
  • Tally
  • Yardi
  • Salesforce
  • HubSpot
  • Microsoft 365
  • Google Workspace
  • REST APIs
How a connection goes live
  1. 01InventoryList the systems and who uses them.
  2. 02ConnectRead-only first, over a governed layer.
  3. 03MapFields to the master data model.
  4. A personApproves what agents may read and write.
  5. 05RunAgents act with each user’s own rights.
  6. 06AuditEvery read and write recorded.
Experience on both

We build on Microsoft and Google. Wherever your people already work.

Most organisations run on one or both. We have years of delivery experience across each, so your data foundation and agents fit the tools you have — not the other way round.

Microsoft

Agents and data checks that work in Teams, SharePoint and Outlook, with documents and lists feeding your master data.

  • Microsoft 365
  • Teams
  • SharePoint
  • Azure
  • Fabric
  • Copilot
  • SharePoint libraries and lists as document sources
  • Agents reachable from Teams
  • Sign-in with your existing Microsoft accounts

Google

Agents that read Drive and Gmail, and data pipelines that land in BigQuery for reporting, with Gemini as one model choice.

  • Google Workspace
  • Gmail
  • Drive
  • BigQuery
  • Gemini
  • Drive and Gmail as document and email sources
  • BigQuery as a source or a reporting destination
  • Sign-in with your existing Google accounts

Product names belong to their owners. This describes our delivery experience, not a partnership or certification.

In production

Data work you can point to.

155k
reference rows in a live master data model
99%+
processing accuracy on Westfield’s tenant sales data
21
app types delivered on Groundfloor

Groundfloor-reported results; not guarantees.

FAQ

Questions buyers ask

Something else? Ask an architect

Why fix the data before building agents?
An agent that reads three conflicting vendor records will pick one, and nobody will know it guessed. One golden record gives every agent the same facts, and gives your team one place to correct them.
Do we have to replace our ERP or move our data?
No. We connect to the systems you already run and read and write with each user’s own permissions. The master record sits alongside them; your ERP stays the system of record for what it is good at.
Who decides when two records are the same?
Rules propose the match, for example the same trade licence and tax number. A data steward sees both records side by side and approves or rejects. Nothing changes the master record without sign-off.
Can data stay in Bangladesh?
Yes. The data foundation runs on Groundfloor, which is live in Dhaka on Pico Public Cloud’s Tier-III data centre. Residency is set per workload, and outside model services stay off unless your policy allows them.
What file types can Document AI read?
PDF, images and scans, Word, spreadsheets, CSV, plain text, audio and video. Text is extracted first, an optional model pass can help with messy pages, and the result is checked against rules and your master data before anyone relies on it.
We use Microsoft 365 or Google Workspace. Does that matter?
It helps. We have delivery experience on both, so agents and data checks can work where your people already work, such as Teams, SharePoint, Google Drive and Gmail.
Where do we start?
Usually one domain, such as vendors or assets. We map where it lives today, build the golden record, and put stewards in front of the first merge proposals. Talk to an architect.

Start with one domain.
We’ll build the golden record.

Bring the messiest list you have: vendors, assets or customers. In a 30-minute call an architect will map where it lives and what one clean version would unlock.

Free. No slides unless you ask for them.