#agency #astro #cold-outreach #design.md #hermes #landing-pages #lead-generation #local-seo #stripe #web-design

About this template

Local Web-Design Agency — in a box (Hermes)

Fork this and your Hermes agent is a one-person local web-design agency. It runs the whole loop:

find → design → preview → cold-email → get paid → serve.

Designs a real, branded Astro + Tailwind landing page for a local business (HVAC, legal, dental, contractors), grounded in Google's design.md token protocol — not generic AI slop.
Cold-outreaches with the "build-first" playbook: it builds the site before pitching, then emails a live preview link from Hermes's native mailbox — personalized, low-volume, with a real unsubscribe.
Weekly drip until reply or unsubscribe, on Hermes-native cron.
Charges via Stripe Payment Links and serves the site live on the client's domain once they pay (Caddy on your own box, or Vercel).
One git repo per client, with a status ladder (prospect → preview → live → paid).

What you bring (BYOK — nothing is baked into the template)

Set these in ~/.hermes/.env after forking:

OPENROUTER_API_KEY — your Hermes model key (hermes config set OPENROUTER_API_KEY …, then hermes model).
Email: hermes gateway setup → your dedicated sending mailbox (address + app-password + IMAP/SMTP hosts).
STRIPE_SECRET_KEY — your own Stripe account (charges your clients).
A hosting target — a Caddy VPS you control (SSH) or a Vercel Pro token. See the host-deploy skill.
Optional GH_TOKEN to push each client repo to your GitHub.

node + headless-Chrome ship in the image; per-client npm install runs at build time.

The undeniable demo

Tell it: "Build a landing page for Phoenix Desert HVAC." It writes a DESIGN.md, generates a branded Astro site (blue brand, orange CTAs, tap-to-call, trust bar, reviews, quote form), builds a preview, and drafts the outreach email with the preview link — end to end.

Skills: design-site, cold-outreach, stripe-billing, host-deploy, client-repo, screenshot.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

Hermes Agent agent
The upstream harness, pre-installed — same version the creator ran.
Starter VM
1 vCPU · 2 GiB RAM · 10 GiB disk.
Creator's /persist data
The captured persist volume is copied byte-for-byte into your fork.
BYOK — your keys, your VM
Add your model API keys after forking; they live only inside your microVM.

What this agent can do

client-repo
One git repository per client — the convention that keeps 500 clients organized, versioned, rollback-able, and handoff-ready. Each repo holds that client's Astro project, its DESIGN.md, and a client.json (domain, status, contact, price). Use when onboarding a new client, tracking an iteration, rolling a site back, or wiring a repo to deploy and to status transitions. The template ships this WORKFLOW only — real client repos are the forker's runtime data, created post-fork.
cold-outreach
Run the "build first, sell after" local-agency playbook — pre-build a landing page for a local business, email them a live preview link via the native Hermes mailbox, and convert. Use when finding prospects, writing outreach, or chasing follow-ups. Pairs with host-deploy (makes the preview URL) and stripe-billing (gets paid).
design-site
Design and build a high-converting landing page for a local service business (HVAC, dentist, lawyer, contractor) as a real static Astro + Tailwind v4 site, driven by a Google design.md token spec so the visual choices are grounded, not invented. Use when the user wants a site built or redesigned for a client, or a preview to send a prospect.
host-deploy
Host every client's static site on its own custom domain with automatic HTTPS, operated entirely by the agent over shell. Primary path is OSS self-host (Caddy + per-client Astro builds on one BYOK VPS, scales to 500+ sites); fallback is Vercel Pro. Also stands up the per-prospect preview URL that cold-outreach links to. Use when deploying, previewing, re-pointing, or scaling client hosting. Pairs with client-repo (source) and stripe-billing (pay-gate the go-live).
screenshot
Capture a clean desktop + mobile screenshot of a rendered site — for warm-reply previews, the "your site is live" email, and a visual record per client. Headless Chrome system libs are baked into the golden image; the browser binary auto-downloads once per fork on first run. Use when you need a PNG of a site (live URL or a local dist/ build) to attach via Hermes MEDIA:.
stripe-billing
Charge the client through the forker's own Stripe account and gate "serve the live site" on payment clearing. Use when proposing pricing, issuing a payment link, detecting that a client has paid, or handing off to go-live. Pairs with cold-outreach (warm reply) and host-deploy / client-repo (the go-live).

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

DEPLOY_TARGET
EMAIL_ADDRESS
EMAIL_IMAP_HOST
EMAIL_PASSWORD
EMAIL_SMTP_HOST
GH_TOKEN
OPENROUTER_API_KEY
STRIPE_SECRET_KEY

Local Web-Design Agency

What's inside

About this template