
Offline Investor Relations App for a Global Pharmaceutical Company
- Client
- Pharmaceutical company · Global · one of the world's largest, app used from the CEO down
- Industry
- Life Sciences
- Department
- Finance & Accounting
- Region
- Europe
At an investor conference, the CEO's answer depended on finding the right slide in a 350-slide deck that was out of date the moment anyone changed it. Now the same content lives in a Power Apps app that works offline on five platforms, kept current by the teams that own it.
A working model of the approach on sample data. It plays on its own and pauses when scrolled away; nothing here touches a live system.
The results
- ~350
- slides migrated into structured data
- About 350 hyperlinked slides, extracted by a Node.js engine. Scope of the build, not a measured saving.
- 5
- platforms, online and offline
- iOS, macOS, Android, Windows and web. Scope of the build.
- Day 1
- content loaded from the existing deck
- Used from the CEO down. No time or usage figures recorded.
The challenge
Our client is one of the world's largest biopharmaceutical companies. Every quarter its investor relations teams in several countries work with the research centres to update the material leadership uses with investors: company performance, R&D, the state of each medicine in the pipeline, what is heading to market and what is being discontinued.
The result was a single PowerPoint of about 350 slides, used as an application: hyperlinks between slides let presenters jump between therapy areas, medicines and pipeline stages.
What it was costing them
- One file, many authors. Contributors in several countries edited one deck, with no structure behind the content and no record of who changed what.
- Always slightly out of date. A pipeline that moves every quarter, captured in a file that had to be rebuilt and redistributed.
- Hard to find the answer. Navigating 350 slides by hyperlink in front of an investor or at a conference.
- No offline guarantee. Leadership travelling to conferences needed the material on any device, with or without a connection.
- No room for feedback. The people preparing the material had no way to comment, review and agree content inside the tool.
- 350 slides one hyperlinked deck
- Records structured and searchable
- Owners update their own content, and it works offline
The approach
We built a Power Apps canvas app that turns the investor deck into structured, searchable content, maintained by the people who own it and available offline on every device leadership uses.
What the app does
- Content as data, not slides. Therapy areas, medicines and pipeline status held as structured, categorised records instead of linked slides.
- Navigation and search. Category navigation that mirrors how leadership talks about the business, plus full search and retrieval of structured information.
- Comments and feedback by role. The people who prepare and collect the information for the investor relations directors comment and give feedback inside the app, according to their role.
- Every device, online and offline. Runs on iOS, macOS, Android, Windows and the web, and works offline for conferences and travel.
- Built for the top of the company. Used by the CEO, investor relations and other directors and departments to prepare and steer conversations with investors and other third parties.
Day-one content
A Node.js engine read the existing PowerPoint, extracted the semi-structured content, tables repeated in the same format across slides, into a structured dataset and loaded it as the app's initial data. The app opened full on its first day, not empty.
- Navigation by therapy area
- Full search of the content
- Works offline on a tablet
- Runs on all five platforms
Technology
| Layer | What we used |
|---|---|
| App | Microsoft Power Apps canvas app, Power Apps mobile and web |
| Platforms | iOS, macOS, Android, Windows, web; offline mode |
| Data and connectors | Power Platform |
| Migration | Node.js extraction engine for PowerPoint (PPTX) content |
| Content model | Therapy areas, medicines and pipeline status, with role-based comments |
The outcome
Leadership opens an app instead of a deck: the right answer is a search or two taps away, on whatever device is at hand, with or without a connection.
| Before | After | |
|---|---|---|
| Investor material | One 350-slide PowerPoint | Structured, categorised records |
| Finding an answer | Hyperlinks between slides | Category navigation and search |
| Without a connection | No guarantee | Works offline |
| Keeping it current | Rebuild and redistribute the deck | Owners update their own content |
| Feedback | Outside the tool | Comments by role, inside the app |
| Initial content | Not applicable | Migrated automatically from the deck |
- A 350-slide navigational PowerPoint replaced by a structured app on every platform leadership uses: iOS, macOS, Android, Windows and web.
- Investor material available offline at conferences and meetings.
- Content kept current by its owners, with comments and feedback in one place.
- Existing content migrated automatically, not retyped.
- Used from the CEO through investor relations to other directors and departments.
- No time or usage figures were recorded, so we do not quote any.
The risk most teams miss
Moving a deck into an app is easy to promise and hard to land. If the first version opens empty, nobody uses it; if it needs a connection, it fails in the conference hall. Day-one content and offline behaviour decide adoption. Extracting the existing deck into structured data before launch, and designing the app offline-first with synchronisation when a connection returns, is what made it the tool leadership opened instead of the PowerPoint.
Built with
The tools this ran on, by the layer each one carried.
Next step
Start the same conversation
Tell us the process that keeps breaking. We will come back with what it would take to fix it, what it would cost, and what we would measure.
Or write to us directly: •••••@•••••••.•••
- A reply from a partner within one business day
- Fixed scope and fixed fee, agreed before we start
- The maps and the backlog are yours either way




