Actual deliverables from active engagements. The pattern is the same in every case: something was unclear, I structured it, then built it. Names and numbers anonymized where needed.
I build password-protected portals for founders raising capital or closing partnerships. Each portal is a branded working room with NDA gates, per-investor analytics, and ad-blocker-proof tracking.
Every engagement starts with a business case. A structured analysis that a board can act on.
| Component | What Was Delivered |
|---|---|
| Problem Statement | Clinicians spending 20-30 min per note. 20% revenue gap from undocumented services. Legacy systems universally hated. |
| Solution Architecture | Three-layer platform (between-visit support + EHR + compliance). AI-native, not bolt-on. |
| Market Sizing | TAM: $264-728M across 26K US facilities. Georgia SAM: $4-10M (365 facilities). |
| Revenue Model | Per-facility pricing (not per-seat). Three tiers: $6-18K, $24-48K, $36-60K annually. |
| Financial Projections | 4-year model. Break-even at 22 medium facilities. Y4 ARR: $1.4-2.2M. |
| Competitive Analysis | 8-vendor matrix with positioning quadrant. Clear differentiation: AI-native + mid-market + vertical-specific. |
| De-Risk Strategy | Demo-as-product model. Every failed sales engagement still advances the platform. |
Every fractional CTO engagement starts the same way: the founder has a vision, a market intuition, and no financial model. Before I write a line of code, I deploy a bundled set of interactive tools and documents that give them (and their investors) a complete picture of the business.
| Artifact | Format | What It Answers |
|---|---|---|
| Unit Economics Model | Interactive web tool | Is each customer profitable? At what scale? What are the real COGS? |
| Business Model / P&L | Interactive web tool | 36-month P&L with funding rounds, cap table, team builder, runway |
| Business Case | Document | Problem, solution, market, differentiators, pricing, competitive landscape |
| TAM Analysis | Document | TAM/SAM/SOM with sourced market data, facility counts, pricing tiers |
| Competitive Landscape | Document | Competitor matrix, positioning quadrant, moat analysis |
The interactive tools are shareable URLs—founders send them to investors, advisors, and co-founders. Everyone can play with the sliders and see the same numbers. No more emailing spreadsheets with broken formulas.
I built and open-sourced a system for creating private, shareable, trackable pages. Hash-based URLs for access control, server-synced checklists, real-time view tracking with Slack alerts, print-first design. No login, no CMS, no build step. 60+ pages shipped across 2 production domains in 6 weeks.
The idea: you send a URL to a client. They tap it. They're reading your proposal. You get a Slack alert the moment they open it. Checklists sync across devices. Every page prints clean on letter paper.
| Use Case | What It Replaces | Why It's Better |
|---|---|---|
| Sales one-pagers | PDFs emailed as attachments | Trackable, mobile-responsive, prints on letter paper |
| Interactive pricing tools | Spreadsheets emailed back and forth | Client plays with sliders, shares config via URL |
| Proposals | Google Docs with "request access" | Zero friction, no login, professional on any device |
| Contracts & BAAs | DocuSign for read-only sharing | Cross-linked deal packages, each doc prints independently |
| Meeting prep & debrief | Internal email threads | Server-synced action items, bio cards, join links |
| Outage / status pages | StatusPage subscriptions | Spin up in minutes, no monthly fee |
| Release notes | Changelog buried in docs | Shareable URL, client sees what shipped |
| Financial models | Excel files with broken formulas | 36-month P&L with scenario comparison, CSV export |
| Demo | Type |
|---|---|
| Startup GTM Financial Model | Interactive 36-month P&L with B2B/B2C/Marketplace toggles |
| Product One-Pager | Print-first, letter-size overview |
| Engagement Proposal | Phased delivery with story-point pricing |
| ROI Calculator | Share link encodes slider state in URL |
| Tracked Share Tool | Generate per-recipient links with view alerts |
| Feature | How It Works |
|---|---|
| Access control | Hash URLs -- 8-char hex (4B possibilities). No login needed. |
| View tracking | Edge function fires Slack alert on first view per recipient. Zero latency. |
| Checklists | Server-synced via Netlify Blobs / Cloudflare KV. Cross-device persistence. |
| Print design | @page { size: letter } with forced colors. Every page is a printable PDF. |
| Dark mode | CSS variables + OS detection + localStorage toggle. |
| Dual platform | Full infrastructure for both Netlify and Cloudflare Pages. |
View on GitHub → 7 templates, 4 working demos, 14 ADRs, dual-platform infrastructure. MIT licensed.
The goal is to get to something we can react to. A presentation can’t do that—people nod along to slides and then discover the problems later. A working demo gets us to a baseline fast. The client clicks through, says “yes, no, not like that,” and we’re iterating on something real. I’ve built these from my phone between meetings. If the template exists, it takes minutes.
| Metric | Value |
|---|---|
| Pages | 101 clickable screens |
| Build time | 1 week |
| Modules | Admissions, Census, Clinical Docs, Billing, Compliance, Nursing |
| Business rules encoded | 131 state-specific regulatory rules |
| Clinical instruments | ASAM screening, C-SSRS safety planning, SA assessment, PHQ-2, GAD-2 |
| AI features | Voice-to-BIRP note generation (2–3 min vs 20–30 min per note) |
| Stakeholder feedback | 8 rounds, mostly async email—less work, fewer meetings, more clarity |
| Outcome | Clinical director: “This does what FamCare was supposed to do” |
Live example: heal7h.com
Things break. Every production incident gets a formal RCA with a timeline, Five Whys analysis, and prevention plan with story-point-estimated mitigations.
Example: Production outage from an expired credential. 90-minute incident. The initial diagnosis was wrong and cost 60 minutes. That's documented in the RCA because blameless postmortems include what went poorly. Root cause: expired authentication token with no lifecycle management. Prevention plan: 5 mitigations, story-point estimated, 3 shipped within 48 hours.
Every technical decision gets an ADR. Not because process demands it, but because future-you (or the next developer, or the board) needs to know why you chose PostgreSQL over MongoDB, why you used SMS over push notifications, why the auth flow works the way it does.
49 ADRs for one project alone. Topics range from database schema to payment processing to clinical safety protocols. Each one is a decision that doesn't need to be relitigated.
Compliance in regulated industries isn't a checklist you run at the end. It's architecture you build from day one.
| Safeguard | Requirement | Implementation | Status |
|---|---|---|---|
| Administrative | Security management | 21 policies (9 active, 12 draft), incident response procedures | Active |
| Administrative | Workforce training | Role-based access, onboarding procedures, termination checklist | Active |
| Physical | Data center security | Azure SOC 2 Type II certified, BAA executed | Active |
| Technical | Encryption | TLS 1.3 in transit, AES-256 at rest, database-level encryption | Active |
| Technical | Access control | Multi-stakeholder RBAC (patient, family, clinician, admin, court) | Active |
| Technical | Audit logging | All PHI access logged with user, timestamp, action, IP | Active |
| Technical | Authentication | SSO + MFA for staff, magic links via SMS for patients | Active |
| Organizational | BAAs | Azure (executed), Twilio (executed) | Active |
Productized compliance: I built Own Your Compliance as a standalone product - AI-authored compliance policies for behavioral health facilities. Version-controlled, audit-ready, deployable per-facility.
Every client gets a live dashboard at ath.how. It's powered by Signal, a system I built where AI edits a ROADMAP.md file, commits, and the dashboard updates in minutes. No Jira. No Monday.com. No status meetings.
| Step | What Happens |
|---|---|
| 1. Work | I complete a task and commit code |
| 2. Update | ROADMAP.md is updated with new status, story points completed |
| 3. Publish | Signal reads the markdown, generates JSON, deploys dashboard |
| 4. View | Client sees live progress at their project URL |
| Metric | Before (Manual) | After (AI-Assisted) | Impact |
|---|---|---|---|
| Time per note | 20-30 minutes | 2-3 minutes | 90% reduction |
| Format compliance | Varies by clinician | BIRP format enforced | 100% compliant |
| Revenue capture | ~80% (undocumented services) | ~95%+ (prompted documentation) | 15-20% revenue lift |
| Audit readiness | Retrospective cleanup | Built-in at creation | Zero rework |
Production Readiness Assessment (302 Story Points)
| Module | Demo Status | Production Gap | SP |
|---|---|---|---|
| Admissions & Intake | Complete | Backend + API | 42 |
| Census & Bed Management | Complete | Real-time sync | 35 |
| Clinical Documentation | Complete | Voice-to-BIRP | 48 |
| Billing & Claims | Partial | Payer integration | 55 |
| Compliance & Reporting | Complete | Automated audits | 38 |
| Nursing & Medical | Complete | Med tracking | 44 |
| User Management & Auth | Complete | Azure AD B2C | 25 |
| Infrastructure | N/A | CI/CD, monitoring | 15 |
I write the content that gets founders into rooms they couldn't otherwise access. Not marketing fluff - substantive analysis backed by peer-reviewed sources that demonstrates domain expertise.
Every product needs a one-pager. Not a slide deck - a single, scannable page that answers "what is this, who is it for, and why should I care" in under 60 seconds. I build these as responsive web pages that print clean on letter paper.
| Element | Purpose |
|---|---|
| Hero statement | One sentence that captures the value proposition |
| How it works | 3-step visual flow (Enroll → Engage → Escalate) |
| Key metrics | Program duration, touchpoints per day, engagement model |
| Audience variants | Different framing for clinicians vs. administrators vs. families |
| QR code / URL | Single call-to-action for next step |
These get printed for conferences, emailed to prospects, and texted to referral partners. The web version tracks views per recipient. The print version looks professional in a folder.
Beyond one-pagers, I build feature-specific landing pages for sales teams. Each feature gets its own URL they can drop into emails and track engagement.
