An 8-week, hands-on engagement designed to validate one defined customer use case. Pilot scope and pricing are confirmed after a technical discovery call.
· Eight-week pilot
· One defined validation use case
· Up to five customer participants
· Up to three mutually compatible devices from one device family
· Workflow mapping and configuration
· Up to ten agreed test procedures
· Measurement and timestamped evidence capture
· One branded report/export template
· Weekly checkpoints
· Final findings and implementation recommendations
· Thirty days of post-pilot bug-fix support
RigMettle is designed for engineering teams that need a focused path from fragmented validation work to repeatable, traceable evidence.
• Startup hardware and connected-product teams
• Wearable and sensor developers
• Engineering validation groups
• Product verification and quality teams
• Teams replacing manual spreadsheets and fragmented evidence
Engineering teams often work across spreadsheets, screenshots, logs, and disconnected tools. RigMettle brings procedures, measurements, results, and evidence into one repeatable workflow.
Run defined engineering tests in a consistent order with clear status, timing, evidence, and failure details.
Capture sensor and device measurements with timestamps, units, source context, and session history when those sources are available.
Review results and create user-initiated evidence exports that preserve test, device, and session traceability.
A focused three-step workflow from technical discovery to reproducible results and a deployment decision.
Select one valuable validation workflow and agree on measurable success criteria.
Connect supported devices or exposed interfaces, configure procedures, and run the workflow with traceable evidence.
Receive reproducible results, a findings report, and a recommendation for broader deployment.
Potential pilot interfaces include BLE GATT, serial or USB CDC, HID, TCP/UDP, REST, WebSocket, vendor SDK or CLI access, and structured log or CSV data. Each interface is a pilot candidate subject to available documentation, customer authorization, platform support, and technical feasibility confirmed during discovery.
· Android: Available through controlled internal testing.
· Windows: In active development; pilot availability depends on the agreed scope and readiness.
When an authorized, documented interface is available and technical feasibility is confirmed during discovery, RigMettle can develop a customer-specific adapter without requiring access to the product’s proprietary source code.
A RigMettle pilot does not provide regulatory certification, guarantee compatibility, or guarantee a specific business outcome. Custom drivers and unsupported integrations require separate scoping.
RigMettle is designed around local-first processing, explicit user-initiated exports, transparent records, and repeatable procedures.
Core workflows execute locally on the device. RigMettle does not automatically upload locally generated engineering evidence to RigMettle-operated servers.
Evidence export occurs only when initiated by the user, preserving device, test, session, and timestamp context.
Android is available through controlled internal testing. Windows is in active development; pilot availability depends on the agreed scope and readiness.