Clarifies the product thesis, intended users, validation logic, and reasons to consider building a working pilot system.
Purpose: High-level project framing
Status: Discussion artifact
Concept
Government-funded support services for autistic and neurodivergent people are under pressure to reduce delivery costs while maintaining, and ideally improving, service quality. A major cost driver is face-to-face consultative support, especially where practitioners travel to participants in regional, remote, or hard-to-access locations.
The proposed project is a provider-led digital support platform that augments existing face-to-face services with structured online engagement, participant-facing tools, practitioner oversight, and configurable support-circle access.
The first objective is not to immediately replace face-to-face care. The first objective is to improve continuity, visibility, and engagement between face-to-face sessions. Over time, if participants, families, practitioners, and providers become confident that digital support improves service quality, some lower-value or travel-heavy contact may be safely shifted online.
Primary Users
Service Provider Organisations
The initial buyer and validation partner is the service provider organisation. These organisations face practical pressure to deliver more support with constrained funding, limited practitioner capacity, and significant travel costs.
Practitioners
Practitioners are the key operational users. The system must help them understand participant engagement, manage caseloads, adjust support programs, and maintain service quality without increasing administrative burden.
Participants
Participants need a mobile experience designed for neurodivergent use patterns. The app should support routines, check-ins, notes, reminders, tasks, calendar visibility, and communication in a way that can be configured to the individual.
Family and Local Support Networks
Families, carers, and local supporters may play a significant role depending on the participant's independence, support needs, and consent settings. Their access should be configurable rather than assumed.
Government and Funders
Government is not the first buyer to prove the concept with. Government becomes the later evidence audience once provider-led pilots can show service quality, engagement, cost, and delivery improvements.
Core Value Proposition
For service providers supporting autistic and neurodivergent people, the platform provides a configurable digital care layer that improves continuity between face-to-face sessions, gives practitioners better visibility across caseloads, and creates evidence for gradually reducing avoidable travel costs without reducing service quality.
Product Thesis
The system should be understood as a minimum viable service platform rather than a small standalone app. The value comes from the loop between:
participant mobile engagement
practitioner control and monitoring
scheduled online contact
family/local support involvement
continuous service feedback
pilot reporting and evidence generation
If these elements are separated, the product may not demonstrate enough operational value to change provider behavior.
Initial Feature Areas
Participant App
Daily or scheduled check-ins
Mood, feeling, or struggle feedback
Simple to-do list
Simple calendar
Routine and medication reminders
Notes or journaling
Notifications, SMS prompts, or affirmations
Visibility of upcoming face-to-face and online support
Interface settings that can be adjusted to the participant's needs
Practitioner Control System
Participant engagement overview
Missed check-ins or routine alerts
Schedule and appointment visibility
Participant-level reports and summaries
Ability to configure check-ins, routines, reminders, access, and interface complexity
Feedback capture on what is and is not working
Tools to support higher caseloads while maintaining quality
Communication Layer
One-to-one video sessions
Group video sessions
App-to-app communication
Structured support requests
Potential SMS support for reminders and engagement
Family and Local Support Access
Access should operate on a configurable support circle model:
Independent participants may require minimal family visibility.
Light-support participants may allow selected reminders and alerts.
Moderate-support participants may need family support around routines, attendance, and follow-up.
High-support participants may need family or support workers to actively assist with app use and ongoing engagement.
Configuration Principle
The platform should not be one-size-fits-all. From the beginning, the product should place a peg in the ground for configurable support across:
timing of check-ins and reminders
what information is requested
how the participant is prompted
family and supporter access
practitioner control settings
notification methods
interface complexity
level of local support involvement
Not all configuration needs to be advanced on day one, but the product architecture and pilot framing should assume customization will deepen over time.
Early Success Measures
The first pilot should not overclaim long-term outcome improvement. It should focus on evidence that the digital model is accepted, used, and useful.
Participant and Family Signals
Participants use the app consistently.
Participants respond positively to the experience.
Families understand the role of the system.
Families feel the system improves visibility or support.
Participants feel more connected between face-to-face sessions.
Practitioner Signals
Practitioners use the control system regularly.
Practitioners feel the system improves service delivery.
Practitioners trust the information enough to adjust engagement.
Practitioners feel the system helps them manage caseloads.
Practitioners identify useful improvements through feedback loops.
Service Delivery Signals
Attendance improves or remains stable.
Check-ins are completed.
Routines and tasks are used.
Missed engagement is visible earlier.
Online sessions are adopted.
Travel-heavy contact can be reviewed with better evidence.
Major Assumptions
Providers are willing to trial a digital layer before government funding is secured.
Practitioners will adopt the system if it improves visibility and does not create excessive admin.
Participants and families will accept digital engagement as an improvement, not a reduction in care.
Configurability is essential to serving a diverse neurodivergent population.
Early usage, comfort, and satisfaction data can justify a deeper validation build.
Over time, the system can support reduced travel costs without reducing quality.
Key Risks
Participants may not engage consistently without significant local support.
Practitioners may see the system as extra work.
Families may worry digital support is being used to remove human contact.
Providers may need stronger compliance, privacy, and reporting assurances before piloting.
Too much configurability too early may make the system complex to build and operate.
Too little configurability may fail to meet real participant needs.
Recommended Positioning
The project should be positioned as a digital continuity and practitioner enablement platform for neurodiversity support services.
It should not initially be positioned as a replacement for face-to-face services. The safer and stronger position is that it improves the quality and frequency of support between sessions, creates better evidence, and gives providers a pathway to reduce avoidable travel only when the evidence supports it.