Point 7 of 9 · The review

What I'd use external development for

I have a deep development background, so I self-serve almost all of this myself. External support is the rare exception, not the plan.

What I handle myself

Effectively the entire marketing site: pages, components, CTAs, metadata, redirects, A/B variants (you already run VWO), accessibility fixes, front-end performance, tracking/GTM, and the reporting and monitoring build. I build, so AI is added leverage on top, not a crutch.

The two exceptions

I'd only pull in external engineering for:

A net-new build from scratch: a full site or platform rebuild, where extra hands genuinely add throughput.
Connecting directly into the company's real data or secure systems: anything that reaches production or patient data, e.g. a server-side insurance pre-check calling Sohar, or cross-domain into app.talkiatry.com. That belongs behind a reviewed, secure endpoint owned with Product/Engineering, not client-side by me.

Even then, I write the brief (problem, scope, acceptance criteria, QA), review the output critically, and own the outcome.