Use cases: where teams lose hours, and what changes

Five problems that slow teams down, what DataBridge changes in each, and a way to work out what the lost time costs you.

It starts with a demo on a sample of your own documents and data.

Teams told us where the hours go

An illustration of a maze of stairs, arches and spiralling paper, where people in red shirts push heavy boxes along the paths, while at the top one person walks on with a small box, a web of linked squares and dots trailing behind her. An illustration of a maze of stairs, arches and spiralling paper, where people in red shirts push heavy boxes along the paths, while at the top one person walks on with a small box, a web of linked squares and dots trailing behind her.

The biggest obstacle to using advanced data analysis isn't skill base or technology; it's plain old access to the data.

The hold-ups teams describe to us.

Five problems, and what changes

  • Projects start sooner

    Today
    Every new data or AI project begins with months of data gathering.
    With DataBridge
    Sources connect once, and the next project starts from the same record
  • Access set once, by role

    Today
    Access requests hold up new joiners and project teams.
    With DataBridge
    Access follows each person's role, set once by your administrators
  • Freedom to change tools

    Today
    Old systems decide which tools teams can use.
    With DataBridge
    Data is read where it sits and fed to the tools you choose
  • Knowledge that stays

    Today
    Know-how leaves when people move on.
    With DataBridge
    Decisions, corrections and context stay in the record, with their evidence
  • Hours back every week

    Today
    Routine emails and reports are put together by hand.
    With DataBridge
    Ask in one sentence, and a draft waits for a person to check and send

What the lost time costs, and how to work it out

Hours per person per week × people doing the work × loaded hourly rate = the weekly cost of searching, waiting and redoing work

LineValue
Hours per person per week5.3 hours
People doing the work40
Loaded hourly rateS$60
Weekly cost5.3 × 40 = 212 hours; 212 × S$60 = S$12,720
A year, at 52 weeksS$661,440 a year, about S$661,000

Take the 5.3 hours a week that Panopto with YouGov found in 2018, in a survey of 1,001 US employees at organisations of 200 people or more, and 40 people at S$60 an hour. That is 5.3 × 40 = 212 hours, and 212 × S$60 = S$12,720 a week, or about S$661,000 a year.

It is the cost of the problem today. How much of it you get back is measured in the pilot, against the baseline you set.

Count only the people who do this kind of work.

Salary plus overheads, per hour

40 people each losing 5.3 hours a week is 212 hours a week, or 11,024 hours a year. At S$60 an hour, that is S$12,720 a week, or about S$661,000 a year. 212 hours a week is the working week of 5.3 full-time people, at 40 hours each.

Customer conversations, renewals and delivery

Prepared customer conversations
Account history, open issues and past agreements in one view before every call.
Renewals and follow-ups on time
Contract dates and last contact surface the next action for each client.
Faster delivery to clients
New work starts as soon as the client agrees, with the data already in place.

Where it fits

Financial services
Finance teams work across ledgers, bank files, contracts and email; DataBridge links them into one record where each figure read from a file opens to its source.
Insurers
Policy, claims and correspondence records about one policyholder are linked into one record, and every version is kept.
Growing businesses
Each customer's invoices, payments, agreements and email sit in one record, and follow-ups arrive as drafts to approve.

Plan a pilot

Pick one task your team does every week, and we will scope a pilot on it.

Plan a pilot

It starts with a demo on a sample of your own documents and data.