Live and Stay

What it is

Live and Stay is the agency's front door: the care pages, the stories and insights blog, and the forms families use to ask for a free assessment or a consultation. Behind it is an admin console the team works from every day: leads, published content, email broadcasts and drip sequences, a knowledge base, and staff training.

What I did

• Built the platform. I opened the repository in January 2024 and grew it into the agency's site and operations tool: the public pages, sign-in with Google, password, or a phone number verified by one-time code, the transactional and marketing email system, and the scripts the team runs against staging and production.
• Split one codebase into two products. By 2026 the same app was carrying two brands. Rather than prune by hand, I wrote a script that walks the import graph from Live and Stay's entry points and removes everything unreachable, then cut the remaining seams: CarePrints paths redirect to their own domain, each brand sends mail from its own verified domain, and the old Geriatric Care Solution URLs redirect in a way search crawlers actually follow.
• Hardened sign-in and service auth. Phone sign-in carries proof that a one-time code was verified before a session or a number is bound, and calls from the web app to the backend use short-lived signed tokens.
• Kept the data honest. I audited the production indexes and moved scheduled-email uniqueness onto partial indexes MongoDB can enforce, wrote a migration that scrubs engagement data belonging to the other product, and added per-deployment configuration so the two products could stop sharing settings.

AI on this surface

The blog generates cover images through Gemini behind key rotation and a circuit breaker, reader comments get an automatic reply that is classified before it is drafted, and the backend's training module turns written courses into narrated video. The heavier AI work in this family of products lives in Anaya Care and CarePrints.