Here's the whole thing, built and ready to be yours. The Digital Health page and the AI Readiness Scorecard are designed, working, and good to go. The one piece you'll wire up is the scorecard's email, and that's Phase C, with your own account, walked through step by step. All you're doing is moving a finished thing onto SalesSparx's accounts and giving it an EisnerAmper address.
Here's the part that matters most. No developer built this. I built every bit of it with Claude Code as my co-pilot, one step at a time, and you'll do it the exact same way. The files are one click below, and Claude Code walks you through each step right on this page. Does that sound doable? It is. You've got this, and I'm not going anywhere.
Everything's inside. Then start with Phase A below.
How this page works: one page, one download, one Claude Code session kept open the whole way. The email I sent is just a pointer ... this page is the real handoff, and everything you need is right here. Nothing else to dig up.
The Digital Health homepage and the AI Readiness Scorecard already work. They live today on PitchKitchen's hosting. This page moves that exact setup onto SalesSparx's own accounts, then gives it an EisnerAmper web address. Think of it as moving a finished house onto SalesSparx's land, then assigning it an EisnerAmper street number.
Does almost everything: creates the accounts, uploads the files, sets it live. Owns it from here on.
Does exactly one small thing: adds a single DNS record. Two minutes, then never involved again.
Gave you this clean copy, then takes down the old one so there are no duplicates and no loose ends.
I'm not a developer, and I built all of this. You can do every stage the same way I did: paste the step into Claude Code, ask it to walk you through slowly, and paste back any error you hit. There are ready-made prompts for each phase further down this page.
This is also why it's safe. EisnerAmper.com runs on Optimizely (a large enterprise CMS) on Microsoft servers. Every folder-style address like eisneramper.com/digital-health is owned and rendered by that system, so putting our page there would mean rebuilding it inside their CMS or routing live traffic through their production servers ... weeks of approvals, and their IT stays in the loop forever.
A subdomain like digitalhealth.eisneramper.com sidesteps all of that. It's a single DNS record that points the name straight at SalesSparx's hosting. It never touches their CMS or servers. Their IT adds one record once and is done, and you control everything past that point. It keeps the EisnerAmper brand without tangling you up in their CMS.
"We'd run it as a subdomain, digitalhealth.eisneramper.com, pointed at our own hosting with a single CNAME. It doesn't touch your Optimizely environment or your servers ... your team just adds one DNS record, and we own everything past that point."
This one ZIP is the entire website ... the homepage, the scorecard, the email function, the logo, all of it in a single folder. Save it somewhere you'll find it again, like your Desktop. You'll upload it to GitHub in the very first step, and you won't need to open or understand a single file inside it to do that. Claude does that part with you. Inside you'll also find a HANDOFF.md ... these same steps saved offline, in case you ever lose this link. Ready? Let's go.
Download the website files (one ZIP)Here's the part that changes everything: you don't do most of these by hand. Open Claude Code in your project folder and ask it. The steps below are tagged so you can see at a glance who does what.
A step marked Claude Code does it is one you don't type, upload, or run yourself. You ask Claude Code and it does the work in your project: creating the repo, putting the files in, deploying, editing the pages, wiring the email, and testing. A step marked SalesSparx is one only a human can do: create an account, click "approve" when Claude Code asks to connect each one (GitHub, then Cloudflare), paste in a key, or pick your booking link. That's the whole division of labor.
Claude Code runs on your computer, so the first time it may need to install a few free helper tools (things like Git and the GitHub and Cloudflare helpers). It does this for you ... just say yes if it asks. If your Mac or Windows pops up a system box asking permission to install something, that's normal, click Install or Allow. After that first time, it just works.
GitHub is where the files live online so Cloudflare can serve them.
SalesSparx Create a GitHub account and an empty repository
If you don't already have GitHub, sign up (free), then create a new private repo, e.g. salessparx/eisneramper-digital-health. A "repo" is just an online folder for the website's files.
Claude Code does itYou start it Get the files into your repo
Download the ZIP above, unzip it, then open Claude Code in that folder and ask it to create the repo and put the files in. It keeps the functions/api structure intact for you. You just approve the GitHub connection once when it asks. Prefer to do it by hand? You can still drag the unzipped folder into GitHub's "Add file → Upload files".
Cloudflare is what serves the page to the world. This step is just connect-and-deploy.
SalesSparx Create a Cloudflare account
Sign up at cloudflare.com (free tier is fine).
Claude Code does itYou start it Deploy it to Cloudflare
Once your Cloudflare account exists, ask Claude Code to deploy the site to Cloudflare Pages. It handles the deploy and tells you the temporary name.pages.dev address it's live at. You create the account and approve the connection when it asks. (Rather click through it yourself? In Cloudflare: Workers & Pages → Create → Pages, then upload your folder or connect your repo.)
The scorecard emails results to the prospect and a lead alert to the owner. This makes that owner you.
SalesSparx Create a Resend account
Resend is the email-sending service. Sign up, verify a SalesSparx sending address, and copy the API key it gives you. Heads up: to send from your own domain, Resend gives you a couple of DNS records (SPF/DKIM) to add to the SalesSparx domain. That's separate from the EisnerAmper record, and the Phase C prompt below has Claude Code walk you through it.
Claude Code does itYou paste the key Wire the scorecard email
Paste your Resend key to Claude Code and ask it to set the three values below and redeploy. It does the wiring; you just hand it the key. Now every lead emails you.
RESEND_API_KEY = (the key from Resend) SCORECARD_FROM = Scorecard <noreply@your-salessparx-domain> SCORECARD_NOTIFY_TO = the inbox that should get lead alerts
This is the only phase that involves EisnerAmper ... one DNS record.
SalesSparxEisnerAmper Agree the subdomain
Pick the address, e.g. digitalhealth.eisneramper.com. This is a marketing conversation, not a technical one.
You (one click)Claude Code reads the record Add the custom domain
In your Cloudflare project: Custom domains → Set up a domain, and type digitalhealth.eisneramper.com. Cloudflare shows the DNS record needed ... usually one CNAME, sometimes a short TXT to verify ownership. Ask Claude Code to read it back to you in plain form so you can forward the exact record to EisnerAmper IT.
SalesSparxEisnerAmper IT Add the one DNS record
Forward Cloudflare's record to EisnerAmper IT. They add it in their DNS. This does not touch Optimizely or their servers. Example of what they'll add:
Type: CNAME Name: digitalhealth (the subdomain part) Value: name.pages.dev (Cloudflare gives the exact target)
SalesSparx Wait for it to turn green
Cloudflare automatically issues the security certificate and activates the subdomain, usually within minutes to a couple of hours.
Final polish, a real test, and you're done.
Claude Code does itYou give the link Add your booking link
Give Claude Code your booking link and ask it to drop it into the pages. You provide the link; it makes the edits. Good news on search: the pages already ship index-ready, with the right SEO tags pointed at digitalhealth.eisneramper.com, so there's nothing to un-hide. Google can find it as soon as the subdomain is live.
Claude Code does it Test it for real
Ask Claude Code to submit a test scorecard and confirm the email lands in your inbox ... it can run the test for you. When it passes, you're fully live.
PitchKitchen Greg takes down the old copy
When step 12 passes, text me and I'll take the old hosting down within a day and archive the old repo, so no duplicate is left running. If the current scorecard link already went to anyone, tell me first and I'll redirect the old address to your new subdomain so no one hits a dead page.
The files are ready to go, with just seven spots marked for you. That's the entire editing surface, and Claude Code can do all of them with you. Search the files for each:
In index.html and ai-readiness-scorecard.html, including the "Book a 30-Min Discussion" button on the scorecard results screen (the highest-intent button on the whole page). This is your "book a meeting" link, e.g. your Calendly. Until you set it, those buttons won't go anywhere, so this is the one to not forget.
These are only safety fallbacks. The real email settings come from the environment variables you set in Step 6, so once those are in, you can leave the code alone.
Use Claude Code, not the Claude.ai chat. The chat can only tell you what to click. Claude Code works right inside your project folder, so it can actually run the steps with you ... connect to GitHub, deploy to Cloudflare, and edit the files. It's how I built all of this. The easiest way in is the Claude Code desktop app for Mac or Windows, at claude.com/claude-code. Open it, point it at the folder with your files, and paste this page in first so it has the full picture. Then paste the matching prompt below. If anything errors or confuses you, paste the exact message back and ask "what does this mean and what do I do?"
I'm using Claude Code in the folder with my unzipped website files (HTML pages plus a Cloudflare Pages function in a /functions folder). I've never used GitHub. Help me get these files into a new private GitHub repo. Do the parts you can from here, and walk me through anything I need to do in the browser, like creating the GitHub account and authorizing access. Keep the functions/api folder structure intact. One step at a time.
I'm in Claude Code in my project folder, and my files are already in a GitHub repo. Help me deploy this folder to Cloudflare Pages. Walk me through creating the Cloudflare account and authorizing access, then deploy it for me and tell me the temporary address it's live at. One step at a time.
I'm in Claude Code. My site has a function at functions/api/submit-scorecard.js that sends email through Resend using three environment variables: RESEND_API_KEY, SCORECARD_FROM, and SCORECARD_NOTIFY_TO. Help me set up Resend (create the account, verify my sending domain with the DNS records it gives me, get the API key) and add those three variables to my Cloudflare Pages project, then redeploy. Do what you can and walk me through the browser parts. One step at a time.
I'm in Claude Code. My site is live on Cloudflare Pages and I want it at digitalhealth.eisneramper.com. Walk me through adding that custom domain in the Cloudflare dashboard (Custom domains, Set up a domain), then read me back the exact DNS record I need to send to EisnerAmper IT, since they manage the domain's DNS. One step at a time.
I'm in Claude Code in my project folder. Confirm the site is set up to be found by Google: no noindex anywhere, and the canonical, description, and sitemap all point at digitalhealth.eisneramper.com. Then help me test that the scorecard form (it posts to /api/submit-scorecard) sends its emails. One step at a time.
Tip: keep the same Claude Code session open for the whole project so it remembers where you are.