Terry

Laatste bericht

Hi,

Interesting product, and a smart sequencing choice: getting the mechanical side validated first with hospitals and therapists before investing in software means v1 can be built against real workflows instead of assumptions.

What you describe maps to a clear architecture: therapist accounts with end user sub accounts, a guided assessment flow with step by step ergo therapeutic instructions, structured measurement input, a visual representation of the device configuration, and report generation. I would build this as a web application (works on any tablet or laptop in a clinical setting, no app store friction) with a strict data model from day one, so that the sensor data and AI capabilities you mention for later versions slot in without a rebuild. That second phase is actually my core specialty: I build production grade AI systems for businesses, so I would design the v1 database with that future in mind.

One thing worth addressing early since you are working with therapists and end user data: this touches health related personal data under the GDPR. Privacy by design, clean data separation per therapist and a sensible consent flow are easy to get right at the start and painful to retrofit. I would bake that into v1.

Relevant recent work: a multilingual conversational AI advisor for an international consumer brand (Next.js, Supabase, 5 languages), an autonomous document processing agent handling roughly 99 percent of cases without human intervention, and several assessment and workflow style applications for SMEs.

A longer term, flexible arrangement suits me well. For the engagement we can work per hour or with a fixed price per version or milestone, whatever works best for you. Happy to share a short outline of how I would scope v1, just let me know!

Have a great day!
Wesley