Agency Website Templates

The expensive part of agency work is rarely the design. It is the fourth time you set up the same build tooling, the plugin update that breaks a client site the week you are on holiday, and the slow drift of fifteen codebases that all started from the same starter and now share nothing. Amrify Pro is the system one developer built to stop paying that cost, and it is sold as the boilerplate an agency would otherwise write for itself.

A note on scope before anything else. The agency-specific template, meaning a site to sell your own services, is not in the launch set. It ships to owners as a free update. What is in the box at launch is the multi-site machinery and ten trade templates, which happens to be exactly the part an agency serving local businesses needs first.

Where Agency Margin Actually Goes

Take a shop with fifteen client sites on eight stacks. A security advisory means eight update procedures. A change to a shared pattern, say a new cookie banner, means fifteen implementations that were each a little different to begin with. None of that is billable. Clients do not pay for the work of keeping your own house in order, so it comes out of margin or out of evenings.

The second leak is quality variance. When each site is its own snowflake, the one built in a hurry in March loads in four seconds and the one built carefully in June loads in one. Both carry your name. The client with the slow site does not know it was a Tuesday-afternoon problem; they know your work is slow.

Shared code fixes both. Components, layouts, schemas and the lead API live in packages. A client site is a config directory plus content. A fix is one commit, and the next build of every site inherits it.

What an Agency Gets on Day One

Amrify Pro is a pnpm and Turborepo monorepo. Astro 7 and Tailwind CSS 4 underneath, SolidJS islands only where a widget genuinely needs to run in the browser, TypeScript throughout.

Ten trade templates at launch. Roofing, HVAC, plumbing, electrical, landscaping, cleaning, pressure washing, pest control, garage door and painting. If your client list is local service businesses, most of your pipeline is covered before the agency template even lands.

The lead engine. A serverless form API that writes every submission to DynamoDB, emails it through SES, pings a phone through Telegram or SMS, and fires a webhook if the client runs a CRM. Spam defenses are built in, Cloudflare Turnstile is optional, and the form accepts up to four photos. This is the piece agencies usually rebuild per client with a different form service each time.

The local SEO engine. Service-area and service-in-city pages generated from a city list, with a build gate that fails any page whose content is too thin to deserve a URL. A client who serves twelve towns gets twelve real pages, and adding a thirteenth is one line.

Conversion widgets. Estimate calculator, quote wizard, reviews carousel, before/after gallery, sticky call bar. Each is a SolidJS island a client can switch on from config.

Fleet tooling. A new-site scaffolder, a cross-site verifier that checks every site in the repo, an AWS S3 and CloudFront deploy, and a leads CLI. This is the operational layer, and it exists because the same codebase already runs Amrify’s own live sites.

The agent setup. CLAUDE.md, AGENTS.md and four Claude Code skills, so Claude Code, Cursor or Copilot can scaffold a client site from a plain-English brief. A trade site is about an hour of work that way. Seventeen docs cover the rest.

Tools You Can Use Before You Buy

Three of Amrify’s free tools are useful to an agency whether or not you ever buy the boilerplate.

The website grader runs Google’s own Lighthouse test on any URL in about thirty seconds, no account and no email. Run a prospect’s site during the sales call.

The comparison tool puts a prospect’s site next to the two competitors that outrank them. That side-by-side is a better pitch deck than most agencies carry.

With a free account, the website monitor tracks up to thirty client sites on one watch list and keeps their score history. Re-tests run on demand when you click, up to two recorded per site per day, with the last ten results kept. It is not scheduled and it sends no alerts; those are on the planned list. For a monthly client report, it is enough.

If you want to see the architecture before spending anything, the free Amrify Starter is a two-site monorepo with five shared packages and the same Lighthouse 100 CI gate, with no JavaScript framework at all. Its license covers unlimited client work; it just cannot be resold as a template. The public repo opens at launch.

Onboarding the Sixteenth Client

The scaffolder creates a new site directory. You fill in config files with the client’s business name, phone, hours, service area and brand colors. Content goes into typed collections: services, service areas, blog, FAQ, about, contact. Turn on the widgets the client wants. Build, and the CI gate confirms the four Lighthouse scores are 100 before anything ships.

Deployment is per site. Netlify, Vercel and Cloudflare Pages host static output for free at the traffic a local business sees, or you push to a client’s own AWS account with the bundled deploy. There is no multi-tenant server and no shared runtime, so one client’s traffic spike is nobody else’s problem.

Pricing is one payment, not a per-client fee: the first 5,000 buyers pay the $249 founding price and everyone after pays $399. The license covers unlimited sites with updates for life. Checkout is not open yet; a free account holds the founding price. When Pro ships, the private GitHub repo shows up in your dashboard, and one seat means one person with that access.

Frequently Asked Questions

How many client sites can I run?

As many as you can sell. The license covers unlimited sites and there are no per-site fees. The same codebase runs Amrify’s own live sites today and is built to run hundreds of sites, and soon thousands.

Do client sites share a hosting plan?

No. Each site builds to its own static output and deploys on its own: Netlify, Vercel or Cloudflare Pages for free, or your own AWS account with the bundled S3 and CloudFront deploy.

Can I white-label the templates?

Yes. The built HTML carries the client’s name, colors and content and nothing of Amrify’s. One seat is one person with repo access, so a team of three needs three seats.

How do I onboard a new client site?

Run the new-site scaffolder, fill in the config files with the client’s business details, drop in their content, and deploy. With Claude Code or Cursor doing the typing, a trade site is roughly an hour of work.

---

The showcase lists live sites you can put through the grader yourself; that is the only proof Amrify publishes.

If a client is currently on WordPress or Wix, the WordPress comparison and the Wix comparison are written to be forwarded to them.

Hold a founding spot above, or write to us with your client mix and we will tell you honestly which of them the launch templates cover. Solo operators may prefer the freelancer page; shops pitching software companies should read the SaaS page; anyone serving single-location clients should start with small business.