One pane of glass. Everything Oleo is doing, right now.
When all 7 ops modules are running, the natural output is this view: real-time module status, HPRA filing calendar, prescriber pipeline, OleoCare adherence aggregate, pharmacy stock, supply chain heartbeat. Built for someone running Oleo and truMED in parallel - so a glance tells you whether to dive in or trust the loop.
https://oleo.io/cockpit · Tuesday 28 April 2026, 09:14Richard Creagh · Co-Founder
07:22Yellow card draft for adverse-event flag #42. Routed to M4 Q1 pack.
06:58Customs delay flagged: shipment B-2245. ETA pushed +2 days. M5 buffer ok.
06:30Daily admin AI summary ready in your inbox. 14 emails triaged.
Supply chain
In transitB-2247 Schiphol -> CorkETA 2 May
DelayedB-2245 customs hold+2 days
StockBedroflo 30g pots in country142 units
StockBedrocan 20g pots in country87 units
NextB-2249 dispatch from Bedrocan14 May
Mockup. Real numbers and feed wired in once the modules ship. Designed to fit a single screen so you can scan it in 30 seconds while running truMED on the other monitor.
Is this worth building?
The honest answer.
Yes, if
You're already running 4+ of the ops modules. The dashboard is the natural output.
You want to delegate execution but keep oversight without diving into each system.
You split your time between Oleo and truMED, so a single-pane Oleo cockpit lets you check in and move on.
You're preparing for a bigger team or external scrutiny (HPRA audit, Department of Health review, investor diligence) and need clean operational visibility on demand.
You want to demonstrate operational maturity to MCAP review committee or any future expansion bid.
Skip it, if
You're running fewer than 3 modules. Premature.
You prefer email + per-system check-ins. Some operators are wired this way and the cockpit becomes noise rather than signal.
You'd rather invest the build budget into the next ops module instead. Honest tradeoff.
The team running ops day-to-day already has views they like. Don't fix what isn't broken.
Our recommendation: not the lead pitch. Build it AFTER 3-4 modules are live and you've validated the working pattern. At that point it's a 2-week wrap. Build it before the modules and it's a glorified static page.