The lived-experience reviewer
Does the workflow respect the practical reality of MDI?
Controlled peer review
Looking for people who will question the workflow.
Bolus Master is entering a small, invitation-only review focused on the MDI use case, usability, calculation transparency, data integrity, privacy, and places where the product could be misunderstood.
Why your perspective matters
Your careful question may prevent someone else’s confusion.
Early products often fail quietly: a label is misunderstood, a setting is easy to overlook, a record is hard to find, or a reassuring sentence says more than the software can support. A reviewer who pauses, questions, and explains what they expected can help us find those problems before the cohort grows.
The clarity reviewer
Can a new person explain what the product does, what it records, and what it does not know?
The trust reviewer
Are privacy, access, data integrity, and safety boundaries visible and believable?
Who can help
Different reviewers should challenge different parts.
The first cohort will remain deliberately small so each observation can be followed up and early issues can be addressed responsibly.
Experienced MDI users
Clarity, burden, real-world language, and moments where the workflow does not match lived experience.
Diabetes professionals
Clinical communication, foreseeable misunderstanding, educational boundaries, and safety escalation.
Digital-health reviewers
Usability, accessibility, onboarding, information hierarchy, and product positioning.
Privacy & security reviewers
Data minimization, account boundaries, integrations, access controls, and incident handling.
What reviewers examine
A focused review—not an unstructured feature tour.
Reviewers receive a consistent agenda and sample workflows so feedback can be compared and prioritized.
Purpose and boundaries
Can the reviewer accurately explain what the app does and does not do?
Input and calculation transparency
Are settings, context, IOB handling, and the final breakdown understandable?
Meal and exercise workflows
Do optional timing and context tools behave intentionally without creating stale state?
History, sync, and later review
Do recorded actions remain accurate, findable, and consistent across signed-in devices?
Safety, privacy, and misunderstanding
Where could language or behavior create a false assumption?
What your hour looks like
A consistent review path keeps feedback useful.
The review is structured so participants can focus on what they noticed rather than trying to cover every feature.
Orient
Read the purpose and safety boundary.
Trace
Follow one fictional or retrospective workflow from input to later review.
Question
Identify anything confusing, overstated, missing, or difficult to verify.
Reflect
Explain what you expected, what happened, and what should change first.
You are not being asked to change treatment, prove an outcome, or share more health information than the review requires.
How feedback is used
Your review should lead to a clear next step.
Feedback is grouped into four categories: confusion, data integrity, privacy and access, and future ideas. The first three receive priority during controlled review because they can affect whether the product is understood and used responsibly. Feature requests may be recorded without being promised.
The early cohort is small so observations can be reviewed individually. A comment may lead to a wording change, a workflow fix, a new test, a documentation clarification, or a decision not to proceed. Reviewer comments will not be presented as evidence that the product improves clinical outcomes.
Named access with an intentional review path.
Approved reviewers receive a personal, single-use invitation, review the current beta agreement and privacy notice, and receive time-limited account access that can be paused or ended individually. A protected reviewer guide provides the same preparation and evaluation agenda to each participant.
Named reviewers
Individual access
Focused follow-up
Tell us how you could contribute Approved reviewer guide
Submitting a request does not create an account or guarantee access.