Why the audit mattered
The audit and the Sandbox Sessions around it gave everyone clarity before a dollar went into code. S.C.A.R. didn’t spend tens of thousands of dollars building in the wrong direction. We built the right things first, kept every next step open, and stayed budget-conscious the whole way, with milestones that let the team scale and shift the business model as real veterans came in.
How the build unfolded
- June 11, Discovery. The platform concept, competitive position and long-term direction.
- June 12, Sandbox Session roadmap. Website first, to enter the market and gather real user data; the custom application second.
- June 22, Foundations. S.C.A.R.-owned AWS and Stripe accounts, the brand starting point, project tracking and the KPIs for success.
- July 17, Mid-build review. The platform at roughly 80%, with secured storage and virus scanning on every upload.
- August 12, Pre-launch review. Editable VA forms with version history, and one veteran ID across every claim.
- Live in production, with a full closeout packet handed over.
What we built
- Separate veteran and advisor portals, each with its own permissions
- Encrypted document uploads, virus-scanned before they’re stored
- AI pre-filled VA forms, editable, with version history
- Review, e-signature and submission in one flow
- Payment-gated sign-up through Stripe, and a GoHighLevel CRM connection
- Platform email sent from S.C.A.R.’s own domain
Security and ownership
- Multi-factor sign-in required on every account
- Encryption in transit and at rest; a private database no one can reach from the internet
- A web application firewall, threat monitoring and daily encrypted backups
- HIPAA: we built and validated a complete HIPAA-compliant infrastructure tier. S.C.A.R. turned it off at launch to lower monthly costs, and it can be switched back on anytime.
- S.C.A.R. owns every account (AWS, Stripe, CRM and domain), with architecture docs, an access register and runbooks in their closeout packet