Oriental Nippon Development
Back to portfolio
Case studyAnalytics function in a US revenue-cycle operator

25+ Automated Workflows That Gave an Analytics Team Back 15 Hours a Week

An analytics team spent most of its time preparing, refreshing and sending reports instead of analysing. We automated more than twenty-five recurring workflows, ranked by hours consumed.

Industry
Revenue Cycle & Finance
Region
United States
Engagement
SES (specialist engineers)

Outcomes

  • ~15 hours/week recovered
  • 25+ workflows automated
  • On-time delivery, every run monitored

Stack

Power Automate · Python ETL · SQL · Power BI · SharePoint · SFTP

Written byOriental Nippon Team

The analytics team inside a US revenue-cycle operator was hired to analyse. In practice most of its week went on something else: preparing data, refreshing reports, exporting them, and sending them to the right inboxes, SharePoint folders and SFTP drops.

No single task was a problem. Each took around half an hour. There were simply a great many of them, every day and every week, and all of them had deadlines that analysis never had.

The problem

  • Deadlined busywork won. Recurring tasks always beat analysis to the top of the list.
  • Results depended on who ran them. The same report could come out slightly differently depending on the person and the day.
  • Distribution was its own manual step. Even a finished report still needed someone to send it.
  • Nobody had the full list. There was no inventory of how many recurring tasks existed or how long they took in total.
BeforeAfter
Recurring workflowsRun by hand25+ automated
Time on repetitive workLarge share of the week~15 hours a week recovered
DistributionManual email and uploadScheduled to email, SharePoint and SFTP
Failure visibilityNoticed when someone complainedEvery run reports to a named owner

What we built

  • 25+ automated workflows

    Preprocessing, report refresh, rendering and distribution, built in Power Automate (cloud and desktop) and Python.

  • Database-side preparation

    SQL stored procedures took over the data shaping that used to happen in spreadsheets.

  • Paginated report output

    Power BI paginated reports rendered on schedule and delivered to email, SharePoint or SFTP.

  • Run monitoring

    Each automation reports success or failure to the person who owns it.

Technology and the role it played

TechnologyRole in this project
Power Automate (cloud and desktop)Orchestrates each workflow and handles desktop-only steps
Python ETLData preparation that was previously done in spreadsheets
SQL stored proceduresDatabase-side shaping close to the data
Power BI paginated reportsPixel-exact report output for distribution
SharePoint and SFTPDelivery destinations alongside email

How we delivered it

Our SES specialists began with a stopwatch, not a tool. We listed every recurring task, timed it, and ranked the list by total hours per month instead of by how annoying each one felt.

  1. Inventory and rank. Every recurring task, its frequency, duration and destination.
  2. Biggest wins first. The highest-volume tasks were automated in the first wave.
  3. Run in parallel. Each automation ran alongside the manual task for a full cycle before the manual version was retired.
  4. Instrument. Every run reports its result to a named owner.
  5. Hand over the pattern. Documentation, so the team can add new automations without us.
Delivery timelineIndicative total: 12–19 weeks
  1. 01Inventory and ranking

    1–2 wks

    Every recurring task timed and ranked by total hours

  2. 02First automation wave

    3–4 wks

    Highest-volume tasks, run in parallel with the manual version

  3. 03Subsequent waves

    6–10 wks

    Remaining workflows, batched by pattern

  4. 04Monitoring

    1–2 wks

    Run reporting, failure alerts, ownership

  5. 05Hand-over

    1 wk

    Documentation and pattern transfer to the team

Risks and how we handled them

RiskHow we handled it
Automating low-value tasks firstEvery task was timed and ranked by total monthly hours before any build
A silent failure goes unnoticedEvery run reports success or failure to a named owner
Automated output differs from the manual versionEach automation ran beside the manual task for a full cycle
The team can't extend it after hand-overDocumented patterns so the team can add new workflows itself

Outcome

Over the period after delivery, the team got back roughly fifteen hours a week that had gone on repetitive work. Reports now go out on time without anyone having to remember to send them.

The recovered hours are capacity, not savings. Whether this was worth doing depends on what the team now does with them.

What the client keeps

  • Every automation definition and all pipeline code, in their own repository
  • Documented stored procedures
  • Run-monitoring configuration
  • The task inventory that set the order of work

Sources and further reading

  1. Power Automate documentation, Microsoft Learn
  2. Paginated reports in Power BI Report Builder, Microsoft Learn
  3. Power Automate adoption: planning a project, Microsoft Learn

Facing something similar? This is the kind of work our AI, Data Science & Automation team delivers every day. Talk to us about your stack.