This page is my application for the Technical Marketing Specialist contract. Every link below is a live system I designed, built, and deployed myself — not slideware. Includes a live SEO + AI-search audit of thecareside.com.au, a concrete 2-week paid trial proposal, and downloadable CV + cover letter.
16 specialised agents, server-side proxy through OpenRouter (Claude · GPT-4 · Gemini fall-back), deployed to 3 hosting platforms from one codebase. This is the exact pattern your voice-agent and lead-follow-up automations will need.
↗ Open live on Vercel ↗ Open live on Firebase
What this proves for your role: the marketing/sales-relevant agents (Maestro Producer · Maestro Publisher · Affiliate Maestro · Google Growth Agent · Customer Concierge · OASIS Strategist) plus the integrations with WhatsApp Business · SMTP Email · Telegram · GA-adjacent analytics map directly to "deploy AI across the full marketing and sales stack — from voice agents to lead follow-ups."
Sensitive-sector engagements. Each one built end-to-end by me — design, content, deployment, post-launch. Same discipline you'll want for healthcare-adjacent marketing.
Brand-assets system built and hosted on Firebase. National disability + employment services provider — handle-with-care client base.
23-asset brand portal with 3-video gallery + infographic tabs. Enterprise telco-grade requirements.
Australian, New Zealand & Asian Creative Arts Therapies Association. Curated content + sector-specific brand platform.
BRACE Intelligence Platform — $46.7M programme focus. Sensitive-data discipline transfers directly to home-care.
Pulled live on 18 May 2026. I ran a quick technical and AI-search-readiness check on your homepage. Five real findings below — three quick wins, two structural fixes. This is a sample of how I'd report inside a working engagement.
en_USYour homepage og:locale is en_US — for an Australian aged-care audience this should be en_AU. Tiny change, real impact on Google's geographic relevance signals and on how the page surfaces in AU-focused AI summaries (Perplexity, ChatGPT Browse, Gemini Search).
The og:image on your homepage is full-resolution. Compress to ~1200×800 WebP under 150 KB — improves social-share previews, page speed, and Core Web Vitals (which feed AI-search ranking systems).
Server response time is on the slow side for a WordPress home-care site competing nationally. Investigate caching layer + image preload hints. AI-search systems weight crawl-cost when deciding which pages to index deeply.
For aged-care queries ("how to apply for home care package," "what does in-home care cost"), FAQPage and HowTo structured data are the single biggest unlocks for AI-Overview citations. Adding 6–8 schema-marked Q&As to your top pages is exactly the kind of "build systems, not meetings" project I'd own in week one.
Current: "As Australia's best value for home care, The CareSide provides the highest quality care at the most affordable prices. We give you more." Strong brand line, but no specifics that AI summarisers can cite. Adding measurable proof points ("1M+ care hours since 2017 · proprietary GEMS platform · government-subsidy navigation included") makes you quoteable in AI answers.
Good news — your social-card metadata is properly configured. Title + description + image + URL + site name all set. Many WordPress competitors don't have this. Build on this foundation.
How I generated this: live HTTP fetch of thecareside.com.au · header inspection · structured-data probe · social-meta extraction · TTFB measurement. Same tooling I'd wire into Screaming Frog + SEMrush + GA4 inside week one of an engagement. Full 12-finding report (with prioritised tickets) available on request — I deliberately kept this preview short.
No long sales cycle. Two weeks. Real deliverables. Decision at the end.
All three documents below were generated for this application. Truth-verified, mid-level expert positioning.
CareSide-specific · quotes 3 lines from your job post · honest gaps + trial offer
Download PDFI'm on AEST. Quickest response window: weekdays 9 am – 8 pm Melbourne time. Async-by-default — Loom, Slack, email all work.