For medical device innovators

Innovate freely.
Build with confidence.

Opra Start gives you the structure to move fast — capturing your users, their needs, and your product vision so you can iterate, pivot, and build without ever losing your foundation.

Free for 7 daysNo credit cardCancel anytime
PROD-001Traceability
Pulse AI Wound Monitorv0.100.000·In Review
IU · IFU5
GROUPS4NEEDS6URS6PRS7IU2IFU3
2 items outdated — downstream review required
BUILT FOR
ISO 13485IEC 62366US FDA 21 CFREU MDRUKCA
HOW IT WORKS

When one user need changes,
every downstream document knows.

The live model shows product operation (capture through notify), the User Need that constrains it, and the IU/IFU that must stay aligned. Edit the need and watch the alert path and downstream docs flag — with reasons on the audit trail. No spreadsheets, no missed updates.

LIVE · OPERATION → NEED → DOCS
product/pulse-ai-wound-monitor/operation + traceability
O
Product operation
4 steps · capture → notify
01
Capture
Wound image + patch telemetry
02
Analyze
On-device AI deterioration risk
03
Alert
Threshold breach → alert state
04
Notify
Push to assigned care team
User groups: Home Patient, Community Nurse (+2)
N
User Need
UN-002
Receive alert when wound condition deteriorates
Community nurse · home monitoring
Operational scope:Alert & Notify (steps 3–4). IU/IFU must describe this path accurately when the need changes.
Impacts:IUIFU
P
Products
1 linked
  • Pulse AI Wound Monitor
IU
Intended Use
IU-01 · 21 CFR 820.30(c)
Approved
Last reviewed Apr 12, 2026
IFU
IFU Document
IFU-01 · EU MDR Annex I 23.4
Approved
Last reviewed Apr 14, 2026
FEATURES

Not a doc repo.
A traceability engine.

Every feature exists because auditors ask for it. Everything flows from one model: needs → products → documents.

opra/structure
ISO 13485 §7.3.3

Structured User Needs

Capture what each user group needs, in what context, with what training level — not as prose in a Word doc.

user_needs · 3· · ·
UN-001Apply monitoring patch without clinical trainingHomeIU·IFU
UN-002Receive alert when wound condition deterioratesHomeIU·IFU
UN-003Review wound healing progress during clinical visitClinic visitIFU
How OPRA START works

User needs first.
Everything else follows.

Start with who you're building for and why they need it. Every decision after that — product definition, risk, planning, build — traces back to that foundation automatically.

01

Understand your users.

Who are you building for? What do they actually need? Opra Start guides you through the questions that matter — in plain language, not technical frameworks — and builds your product definition from those answers.

User needs → intended use
02

Shape your product.

Model, iterate, refine. Your product requirements trace automatically to the user needs behind them. Pivot freely — the connection is maintained. Every version of your thinking is captured, structured, and connected.

Intended use → requirements
03

Pave the way forward.

What you build in Opra Start is the foundation for everything that follows — risk, planning, build, assets, all the way to OPRA FLOW. Add each product when your work demands it. Never pay for infrastructure you haven't grown into yet.

Requirements → everything
PRICING

Priced for startups.
Built for audits.

Free Trial

Full access to explore Opra Start with your team.

£0for 7 days
Start free trial
  • All features included
  • 1 product, 10 needs
  • Full audit trail
  • No credit card required

Growth

For growing teams with multiple products in development.

£179/month
Start free trial
  • Up to 10 users
  • Everything in Team
  • Multi-product portfolio
  • Role-based access
  • Export & reporting
  • Priority support

Enterprise

For organizations with compliance-critical requirements.

Custom
Contact sales
  • Unlimited users
  • Everything in Growth
  • SSO (SAML / OIDC)
  • Dedicated account manager
  • Custom integrations
  • On-premise option
THE CONSTELLATION

Seven products. One direction.
Enter wherever you are.

Not every company starts at stage one. The constellation meets you where you are — and each product activates only when your work genuinely needs it.

OPRA FLOWThe North Star · The future of medical device operations.
OPRA FLOW · the destinationseven micro-products · ships in six weeks each

Contact us for timelines and interest in the entire collection.

Live now

OPRA START

Product definition

Guide a team from ideation to a fully traceable product definition. User groups, needs, URS, Intended Use, PRS — all linked, all audit-ready.

IEC 62366ISO 13485EU MDR
  • Unified user-group and need capture
  • Brain Dump — paste raw interview notes
  • Shall / should language enforcement
  • AI-assisted Intended Use drafting
  • Medical vs wellness decision support
  • Requirements Tree visualisation
FAQ

Questions, answered.

01What regulations does Opra Start help with?

ISO 13485:2016 (§7.3.3, §7.3.9), IEC 62366-1 (§5.1 Use Specification, §5.2 User Needs), 21 CFR 820.30 Design Controls, EU MDR Annex I, and 21 CFR Part 11 for the audit trail. We map every artifact to its specific clauses.

02What is change propagation?

When you edit a User Need or update a user-group profile, Opra Start flags linked URS entries and cascades downstream to PRS, Intended Use (IU), and IFU documents where applicable. Each flag carries a reason and is logged in the audit trail. You review, approve, and move on — no spreadsheet hunting.

03Can I use Opra Start for SaMD (Software as a Medical Device)?

Yes. SaMD teams are our core users. The model — user groups, needs, products, IU, IFU — maps cleanly to software devices. Coverage analysis is especially useful for identifying clinical workflows where needs are undefined.

04How does the audit trail work?

Every create, update, delete, approve, and propagation event is recorded with actor, timestamp, and reason. Records are append-only and cannot be edited or deleted. Export to CSV for inspection.

05Is my data isolated from other organizations?

Yes. Each organization has an isolated tenant. Access is scoped at query time; no cross-tenant reads are possible. Enterprise tier supports single-tenant deployment and on-premise.

06Can I export data for regulatory submissions?

Yes. Product traceability exports as .xlsx from the product workspace. The audit trail exports as CSV for inspection and archival.

Make your traceability audit-proof.

Start your free 7-day trial. Set up your first product, define user groups and needs, see propagation in action.

No credit card · 7 days · cancel anytime