Capture role-specific BATCHXPLORER feedback.

Use these focused survey tracks after a reviewer watches the demo, explores the pre-alpha account, or completes a guided walkthrough. Each submission is emailed to sales@batchxplorer.live with a PDF-style report attachment.

Start a survey → Request demo account → Open live demo →

Locked downRequires the private pre-alpha / partner access code on submit.

Role-specificPartner, validation, admin, QA, and engineer/operator tracks.

Email reportSubmissions are sent as structured email plus attached PDF report.

Survey tracks

Choose the reviewer lens.

Prospective partner journey
Validation journey
Admin journey
QA journey
Engineer / operator journey

Best practice: keep surveys short, then use follow-up calls for detail.

Reviewer survey

Submit pre-alpha feedback.

This form is not GMP validation, UAT, or formal acceptance testing. It is private pre-alpha product feedback to improve BATCHXPLORER Live.

Survey track Access code Full name Business email Company / organization Title / role Review context Would you join a follow-up call?

Choose a track to reveal role-specific questions.

Core BATCHXPLORER feedback

Overall value Clarity of product story Workflow fit GMP-oriented trust

Which capabilities felt most valuable? Live batch visibility Controlled reports Process Insight Audit trail / e-signature Equipment and room context MES/SFC workflow preview Validation-aware governance Partner services model

What felt most valuable? What was confusing, weak, or missing? What would block adoption or pilot approval?

Prospective partner journey questions

Best partner fit Partner model clarity Where would you introduce BATCHXPLORER first? What sales material, pricing detail, or objection handling is missing? What would make deal registration / partner participation easier?

Validation journey questions

Validation readiness impression Most important package item What would you need before recommending a pilot in a GMP-oriented environment? Where do you see validation, Part 11, audit trail, or data-integrity risk? What validation deliverables should Theloris provide versus partner/customer provide?

Admin journey questions

Admin setup clarity Highest admin concern What would an administrator need to configure before users can be successful? What admin controls, logs, or reports are missing? What support or onboarding process would reduce friction?

QA journey questions

QA confidence level QA priority area Would the controlled report concept help QA review or oversight? Why or why not? What language or boundaries should be clearer so this is not confused with automated QA release? What would QA need to see before allowing a pilot or non-production evaluation?

Engineer / operator journey questions

Ease of use Most useful daily workflow Where would this save time during or after a run? What screen, workflow, label, or action would confuse an operator or engineer? What process data, equipment context, or operator action is missing?

Commercial and follow-up signal

Pilot interest Expected buyer/sponsor What would make BATCHXPLORER worth paying for? Any other comments?

I understand this is private pre-alpha product feedback and Theloris may use my feedback to improve BATCHXPLORER Live and related Theloris products. I confirm I did not include confidential customer batch data, PHI, trade secrets, passwords, or regulated production data in this survey response.