Our House Roadmap
Logged in as
Our House Roadmap
Logged in as
Our House is a centralized, digital ecosystem designed to bridge the gap between Central Ohio residents and the resources, jobs, and tools they need to thrive. Here is where we stand today, and how we launch tomorrow.
We have successfully architected and deployed the core pillars of the platform, utilizing a modern cross-platform component-based architecture, noSQL & postGress data operations, an employer-facing REST API, and a custom LLM Model, Merlin.
Standardized intake forms that capture HMIS-required data points immediately. We assign a unique digital identity to every resident, allowing them to carry their history, certifications, and progress with them.
A QR-Code and NFC-Tag smart checkin system allows residents to scan their ID or mobile app for painless entry. Daily reports are generated automatically and transmitted to HMIS Systems with zero mental overhead.
Autonomous aggregation of bed nights, meals served, and support hours into formats pre-approved for Ohio reimbursement grants. We have eradicated the need to burden staff with spreadsheets.
A secure, immutable log of all facility incidents. By digitizing these logs, we help organizations identify patterns, improve safety protocols, and maintain the high standards required for city contracts.
A live, geocoded map connecting users to free meals, shelters, and health centers. Includes integrated routing and a community-driven Rideshare board open to the public as a helpful utility.
Trained on the stories of our founders, Merlin generates comprehensive business plans, acts as a career coach, creates shareable, cinematic vision boards, and exalts self-belief as the most primary objective.
A fully functioning resume builder that outputs PDF files. Backed by a custom API allowing local employers to bypass traditional job boards and push jobs directly to our platform.
Front-end dashboard for local small businesses to log in, view structured JSON resumes, manage applicant statuses, and become involved in hiring residents for social impact.
A custom-built Audiobook library and Video player with comment-threads, offering free educational and entertainment resources. Food and shelter does no long-term good if we do not stimulate the mind.
Integrated training system for staff-onboarding and continuous education. From de-escalation protocols to career growth tracking, the system ensures staff is supported and immediately notified across all departments
Robust Identity & Access-Management(IAM) backend with role-based access control (Resident/Staff, etc.), secure data subcollections, and automated Cloud Functions for tasks like geocoding.
A one-on-one chat system allowing users to safely communicate with staff and case-workers without exposing personal phone numbers. Staff may communicate with staff and organize all correspondence efficiently.
Before we open the doors to the public, the following engineering tasks remain in the sprint queue.
A major barrier to work is getting there. We are building an automated integration with the COTA Reduced Fare system. Users and staff will be able to plan trips and access fare assistance instantly within the interface.
Final QA passes on smaller mobile screens (iPhone SE size) and older Android devices to ensure the UI remains unbroken and accessible.
A strategic, phased rollout ensures stability, safety, and community buy-in before a mass public launch.
Deployment to the core team and investors. Focus on breaking the app, testing security rules, verifying database reads/writes, and ensuring the Gemini AI prompts yield safe, high-quality results.
The feedback and data we gather during Alpha-testing will help us devise the most optimum and least-offensive implimentation of in-app tours, walk-throughs, and feature guides. This is vital that we do not speak down to users or assume they need help until they actually do. This is not the implimentation phase, merely the general model.
Onboard 50-100 real users through a trusted local partner (e.g., a local shelter or community center). Gather initial analytics on how residents interact with the Map, Jobs, and Merlin. Seed the platform with initial content.
Open registration to Central Ohio. Begin marketing outreach, onboard multiple enterprise employers to the API, and officially remove the "Beta" tag.
You might notice a lack of initial "App Tours" or "Tooltips." This is intentional.
Pre-building documentation and onboarding guides requires us to guess where users will get confused. In an app designed for accessibility, guessing leads to cluttered, annoying pop-ups that users instantly skip.
During the Phase 2 Closed Beta, we will monitor analytics to see exactly where users stall, click the wrong buttons, or abandon workflows.
Based on that actual data, we will surgically inject helpful tooltips, in-app tours, and documentation only in the exact places they are proven to be needed. This lean approach saves development time and creates a vastly superior user experience.