This is bigger than housing
The challenge is not simply whether housing exists. Families need a way to navigate multiple disconnected systems together.
NeuroNiche Hub · November 1 and beyond
NeuroNiche is building more than a program and more than a housing model. You are building an integrated ecosystem where neurodivergent adults and families can move through adulthood with stronger coordination across housing, employment, education, wellness, community, and support.
The NeuroNiche Hub can become the digital infrastructure behind that vision. But you do not need to build everything at once.
You do not need the entire future of NeuroNiche built by launch day. You need the right foundation for where NeuroNiche is now and a clear path for what can come next.
Explore first. Decide what fits later.
Before we talk about software
Natalie Beeser’s vision connects individual lives with a broader community. The strongest system is not the one with the most features. It is the one that reflects how NeuroNiche actually plans to operate.
The challenge is not simply whether housing exists. Families need a way to navigate multiple disconnected systems together.
As school-based supports change, families take on the work of coordinating adult services, benefits, employment, transportation, and community.
Autonomy, support, family involvement, and belonging can coexist. There is no single definition of a meaningful adult life.
Housing, employment, education, wellness, and family support are connected. Technology should strengthen those relationships, not create another silo.
The NeuroHub demonstration is creating knowledge: what is tested, what changes, what participants and families experience, and what begins to work.
Documented practices can grow into a framework that helps NeuroNiche learn, improve, and thoughtfully inform future communities.
The technology should follow the mission. Not the other way around.
Your next chapter
NeuroNiche’s soft launch marks the beginning of implementation. The better question is: what does NeuroNiche need first so the organization can launch, learn, grow, and build from a strong foundation?
Before / around launch
Leadership, volunteers, partners, outreach, funding, tasks, documents, calendar, and basic program coordination.
After launch
Participant coordination, family support, transition planning, employment, education, community, and outcomes.
Later
Demonstration learning, a practice library, model documentation, advanced reporting, and replication readiness.
These are examples, not a prescribed roadmap. NeuroNiche will choose its own priorities below.
The possibility explorer
This is not me telling you what to buy. This is you deciding what belongs in the NeuroNiche ecosystem.
You do not have to decide everything today.
Give leadership one place to understand what is happening across NeuroNiche.
Who could use it: Leadership · program management · authorized staff
Coordinate goals, responsibilities, schedules, and progress around the individual.
Who could use it: Authorized staff · participants and families where appropriate
Bring the major areas of adulthood into one coordinated view.
Who could use it: Participants · families · coordinators
Organize the transition from school-based services to adult life.
Who could use it: Young adults · families · coordinators
Connect housing goals and living supports to the larger ecosystem.
Who could use it: Coordinators · families · housing partners
Help authorized people coordinate responsibilities across providers and settings.
Who could use it: Authorized staff · designated family
Care coordination only, not medical advice or a medical record system. Sensitive information requires a privacy review before inclusion.
Support employment from exploration through retention.
Who could use it: Participants · coaches · employer partners
Make space for individualized education and lifelong learning.
Who could use it: Participants · educators · coordinators
Connect people with the broader community through shared interests.
Who could use it: Participants · community coordinators
Reduce the coordination burden on families and caregivers.
Who could use it: Families · caregivers · authorized staff
Clarify who is responsible for each part of a person’s support.
Who could use it: Authorized support team members
Connect strategic volunteers with projects that match their strengths.
Who could use it: Volunteer coordinators · volunteers
Turn expertise and introductions into meaningful strategic contribution.
Who could use it: Leadership · advisory members
Support governance, financial oversight, and recruitment for two open board seats.
Who could use it: Leadership · board members
Build lasting relationships across the systems that shape adult life.
Who could use it: Leadership · partnership coordinators
Build funding relationships, not just a list of applications.
Who could use it: Leadership · fundraising team
Coordinate conversations that bring the mission to more people.
Who could use it: Leadership · outreach volunteers
Strategic future capability
Turn day-to-day NeuroHub experience into documented organizational learning.
Who could use it: Authorized program staff · leadership
Give successful practices a permanent organizational home.
Who could use it: Program staff · advisors
Understand progress and tell an aggregate, privacy-aware impact story.
Who could use it: Leadership · authorized staff
Build institutional knowledge behind the NeuroHub model.
Who could use it: Leadership · authorized contributors
Determine when parts of the model are ready for other communities.
Who could use it: Leadership · advisors
Give each next step an owner and a clear follow-up.
Who could use it: Staff · assigned contributors
Coordinate commitments across people, programs, and partners.
Who could use it: Authorized users by role
Keep important resources organized with intentional access permissions.
Who could use it: Authorized users by document
Make organizational progress visible without exposing private records.
Who could use it: Leadership · board · approved audiences
Offer each person the information and actions appropriate to their role.
Who could use it: All users with defined permissions
Share intentional updates and resources with families.
Who could use it: Authorized family members
Offer a simple, age-respectful experience without administrative complexity.
Who could use it: Participants
Help more people understand what NeuroNiche is building.
Who could use it: Public communications team
Explore how people, support teams, daily coordination, and demonstration learning could connect. The live concept uses fictional sample information; it is not a finished production system.
Experience the Live ConceptLeadership, staff, volunteers, board, families, participants, and partners do not need the same view. Individual accounts, restricted pages, private notes, document permissions, deactivation, and activity history should be scoped deliberately.
NeuroNiche does not need to collect information just because the software can store it. Decide what belongs in the hub and what should remain elsewhere.
Individual records stay separate from public impact reporting. Private example: a participant completed four activities. Aggregate example: participants completed 37 activities this quarter. These examples are illustrative.
Leadership, program team, family, participant, board, and partner access should be defined for each kind of document. Access is based on responsibilities, not convenience.
Before launch, the final privacy and security architecture will be based on what information NeuroNiche chooses to store, who needs access to it, and any applicable organizational, contractual, insurance, funder, or legal requirements.
Privacy is not something we add after the system is built. It is something we decide while defining the system.
One-time project cost
The initial development price is based on the final scope NeuroNiche selects: design, modules, forms, workflows, role setup, configuration, testing, launch preparation, and agreed integrations.
Separate recurring cost
Hosting, routine maintenance, monitoring, minor fixes, technical support, and updates depend on the support level selected. The monthly amount will be determined after the final build scope and support needs are clear.
Scoped as needed
Monthly maintenance does not automatically include unlimited new development. New modules, portals, major workflow changes, advanced integrations, automations, and custom reports may be separately scoped.
You are deciding what NeuroNiche needs first.
The full vision can be large because the mission is large. The first build does not have to be. NeuroNiche can grow the platform as the organization grows, instead of paying for every possible feature on day one.
Phase 1
What helps us operate now?
Phase 2
What grows with participation?
Phase 3
What helps the model travel?
Shape our version
November 1 is the launch of the mission, not the deadline for every future feature.
Step 1 of 12
November 1 starts the next chapter.
The NeuroNiche Hub only needs to give the organization the right place to begin.