RTMify Live

Know your product.

Live builds a connected graph from your requirements spreadsheet, your source code, your Design BOM, your SOUP register, your SBOM, and your test execution records. One binary on your laptop. From user need to shipped serial number, queryable by AI.

See pricing →

RTMify Live · MCP

Ask your product anything.

Connect your AI assistant once and your entire product realization history becomes conversational.

Claude Code — ~/Projects/security-system

❯ How many user needs do we have?

⏺ rtmify-live · get_user_needs (MCP)

⏺ You have 12 user needs (UN-001 through UN-012).

Breakdown by priority:

· High (6): UN-001, UN-002, UN-005, UN-006, UN-010, UN-011

· Medium (4): UN-003, UN-004, UN-007, UN-009

· Low (2): UN-008, UN-012

❯ Which user needs have no requirements?

⏺ rtmify-live · get_rtm (MCP)

⏺ Only UN-010 has no requirements linked to it:

"The system shall provide an audible alarm > 85dB at 3 meters."

Priority: High · Source: Safety

⚠ High priority Safety need — worth addressing soon.

❯ I know you don't have enough context to get why, but I have goosebumps. I'm literally talking to my requirements. Jama, Polarion... nobody has this feature. This is game changing.

⏺ That's the whole point of rtmify — your RTM isn't a static document

you query with a form. It's a live knowledge graph you can just talk to.

You can ask things like:

· "What's the impact if UN-002 changes?"

· "Who last touched the code linked to REQ-001?"

· "Which requirements have no code implementation yet?"

No form. No export. No pivot table. Just ask.

❯ What's the impact if UN-002 changes?

⏺ rtmify-live · get_impact (MCP) (id: "UN-002")

⏺ If UN-002 changes, here's everything affected:

Directly derived:

· REQ-014 — "The sirens SHALL produce a sound level of 90dB."

Cascading into testing:

· TG-005 — the entire test group

· T-005-01 through T-005-04 — all 4 tests

Blast radius: one requirement, one test group, four tests.

What Live does

Keeps your design controls current

Connect Live to your Google Sheet and it polls every 30 seconds. When anyone edits a requirement, test, or risk, Live re-evaluates the full traceability chain and writes the result back: a color-coded status column on every row. Green means covered, yellow means gaps, and red means errors. Your team keeps working in the spreadsheet they already use. Live runs in the background.

Reads your source code

Point Live at your working tree and it scans for inline requirement tags: a // REQ-047 comment in your C file, an annotation in your Python module, or a tag in your VHDL. No tooling changes are required. Every sync cycle, Live re-reads your source as it exists on disk right now and maps each tag back to its requirement. Git attribution (author, commit, and date) is available as metadata. The engineers already did the work. Live captures the proof.

Ingests your test evidence

Live accepts CI output, ATE logs, ATP results, and design verification records. Drop a JSON file in the inbox or POST to the API and Live matches each test case ID back to your requirements and each serial number to your product. The verification status on every requirement updates automatically. No spreadsheet maintenance is required and no manual cross-referencing is needed. The test ran, the evidence exists, and the graph knows.

CI / unit tests ATE / ATP design verification environmental qual

Consumes your Design BOM, SOUP register, and SBOM

Export your hardware BOM from your PLM, ERP, or CAD tool as CSV, connect a secondary Design BOM workbook, or upload a grouped .xlsx Design BOM workbook. For software, either export CycloneDX or SPDX JSON from CI or connect the dedicated SOUP workbook when you need anomaly evaluation and safety-class fields. Live builds the product structure tree and connects it to the design controls graph, including explicit requirement and test references carried on BOM or SOUP rows.

Hardware BOM (CSV) Design BOM (.xlsx) SOUP (.xlsx) CycloneDX SPDX

Download the Design BOM template Download the SOUP template Read the Design BOM ingestion guide

Queryable by AI

Live runs a native MCP server. Connect Claude, Cursor, or any MCP-compatible client and the entire graph becomes conversational:

→ "Which requirements have no test coverage?"
→ "Show me every serial number verified against REQ-047."
→ "What's the blast radius if supplier X has a quality notification on lot 2024-0847?"
→ "Which software dependencies are in ASM-1000 Rev C?"
→ "REQ-047 changed last week. Which test executions used the old version?"

Knows your standard

Pick a profile and Live enforces the right traceability chain for your regulatory context.

Medical

ISO 13485 / IEC 62304 / FDA. Live enforces the Design Input to Design Output to source code chain. Risk mitigation linkage is required.

Aerospace

AS9100 / DO-178C. Live requires HLR/LLR decomposition and structural coverage evidence. DAL annotation is tracked.

Automotive

ISO 26262 / ASPICE. Live checks ASIL assignment and inheritance. HARA linkage is enforced.

Generic

No required chain is enforced. Live tracks User Needs, Requirements, Tests, and Risks. Start here and add constraints as your process matures.

Live · Real session output

This is what it actually looks like.

Three questions from a single Claude Code session connected to a VS-200 medical device workbook.

Claude Code showing requirements ranked by source code surface area — REQ-001 touches spo2_module, motion_filter, nibp_module, temp_sensor across 4 commits — "Which requirements have the largest surface area of source code implementation?"

Claude Code showing all 10 risks with severity, status, and mitigating requirements — RSK-010 flagged Open as the only unmitigated risk — "Which requirements are derived from risk mitigation?"

Claude Code explaining chain gaps versus implementation gaps — 0 chain gaps, 8 implementation gaps, with a summary table — "Explain the difference between a chain gap and an implementation gap."

The product realization graph

Every tool in your stack produces data exhaust. Your engineers write code with requirement annotations. Your CI pipeline produces test results. Your test station logs every serial number it touches. Your PLM exports a BOM. Your mechanical team exports a workbook. Your build system generates an SBOM. That evidence already exists. Nobody connects it.

Live connects it. One binary parses what your team already produces and builds a graph. The graph links user needs to requirements, requirements to tests, requirements to source code, products to Design BOMs, Design BOMs to components, test executions to serial numbers, and serial numbers to products. The chain from "why we built this" to "did this specific unit pass" is one query.

Evidence type	Source	How it enters
Design controls	Your spreadsheet	Google Sheets sync / local .xlsx
Implementation claims	Source code annotations	Git repo scan
Test evidence	CI, ATE, ATP, design verification	JSON inbox or HTTP API
Hardware Design BOM	PLM / ERP / CAD export	CSV inbox or API, grouped XLSX upload, or secondary Design BOM sync
Software BOM	CI pipeline	CycloneDX / SPDX JSON
SOUP register	Engineering workbook	SOUP XLSX upload, SOUP Sync, or SOUP JSON API
Product configuration	Product tab in spreadsheet	Google Sheets sync

Why not just use Jama?

Jama does requirements. MasterControl does manufacturing records. Arena does BOMs. Nobody does all three. Nobody connects all three. You pay for enterprise software and your engineers still maintain a spreadsheet on the side because the ALM tool doesn't know about their test station output or their Design BOM trace links.

RTMify Live reads the artifacts your team already produces and builds the connected graph that no single tool provides. The spreadsheet stays. The PLM stays. The CI pipeline stays. Live runs alongside all of them, on your laptop, connecting the evidence that's already there.

Capability	Legacy ALM	RTMify Live
Requirements	Yes (in their tool)	Yes (in your spreadsheet)
Code traceability	Plugin, if it exists	Git repo scan, every cycle
Test evidence	Manual entry	CI/ATE/ATP via API or inbox
BOM / SBOM	Separate PLM system	CSV, SOUP workbook, CycloneDX, SPDX ingestion
Connected graph	No	User need → requirement → test → serial
AI-queryable	No / "Beta"	Native MCP server
Data privacy	Cloud or complex on-prem	100% local, your machine
What engineers use	Excel (on the side)	Excel (that's the whole point)

One inbox. One binary.

Live watches a single directory on your machine. Drop a file in and Live reads it. Test results, hardware BOMs, and software BOMs all go in the same folder. Live detects the file type, routes it to the right parser, and updates the graph. Processed files move to processed/. Failures move to rejected/ with a diagnostic. Your CI pipeline can push directly to the HTTP API instead if you prefer.

There is no installer to run, no dependencies to manage, no account to create, and no internet connection required. The binary runs on your laptop and the data never leaves your machine. For engineers at defense contractors, medical device companies, and regulated financial firms, this is the difference between "let me check with IT" and "it's already running."

Ready to buy?

Perpetual license starting at $599, with a 30-day money-back guarantee.

See Live pricing →

The RTMify product ladder

RTMify Template

Build your RTM in a spreadsheet. Free download, no account.

RTMify Trace Available now

Generate a complete traceability artifact from your spreadsheet. Local, offline, no account.

RTMify Live You are here

Maintain traceability continuously. Live sync to your Google Sheet.