Build Agency Client Sites

Repeatable workflow for agencies building client websites. Fast delivery, clean handover, and satisfied clients.

Build client websites faster with a repeatable process. This guide covers the workflow from kickoff to handover — designed for agencies and freelancers.

The Agency Workflow

Kickoff — Gather requirements, set expectations
Generate — Create initial site with AI
Refine — Client feedback rounds
Polish — Final details and QA
Handover — Export or deploy, train client

Step 1: Kickoff Checklist

Before starting, gather:

Brand assets:

[ ] Logo (SVG preferred)
[ ] Brand colors (hex codes)
[ ] Typography preferences
[ ] Existing brand guidelines

Content:

[ ] Business description
[ ] Services/products list
[ ] Team bios (if needed)
[ ] Testimonials
[ ] Contact information

Technical:

[ ] Domain name
[ ] Hosting preference
[ ] Third-party integrations needed
[ ] Analytics requirements

Project scope:

[ ] Pages needed
[ ] Key features
[ ] Timeline
[ ] Budget

Step 2: Generate the Base Site

Create a comprehensive initial prompt:

Create a website for [Client Business Name], a [business type]
serving [target audience] in [location if relevant].

Brand:
- Logo: [will upload]
- Primary color: [hex]
- Secondary color: [hex]
- Style: [modern/classic/playful/professional]

Pages needed:
- Homepage: [describe sections]
- [Page 2]: [describe]
- [Page 3]: [describe]
- Contact: form with [fields]

Features:
- [Feature 1]
- [Feature 2]
- [Feature 3]

Footer with:
- Address, phone, email
- Social links
- Quick links
- Copyright

Pro tip: Save templates for common client types (restaurant, salon, contractor, etc.).

Step 3: First Review

Share the initial version with the client:

Publish to a preview URL
Record a Loom walkthrough
Send with structured feedback request

Feedback request template:

Here's your website preview: [URL]

Please review and note:
1. Overall impression — Does it feel right for your brand?
2. Homepage — Any sections to add, remove, or reorder?
3. Content — What text needs updating?
4. Images — Which placeholders need real photos?
5. Other pages — Notes for each page

Please prioritize: What's most important to fix?

Step 4: Iteration Rounds

Process feedback efficiently:

Round 1: Structure

Page layout changes
Section additions/removals
Navigation updates

Round 2: Content

Text updates
Image replacements
Contact info

Round 3: Polish

Color tweaks
Spacing adjustments
Mobile optimization

Batch similar feedback:

Make these text updates:
- Hero headline: "[new text]"
- Services section title: "[new text]"
- CTA button: "[new text]"

Replace these images:
- Hero image: [upload new]
- About page team photo: [upload new]

Step 5: Quality Assurance

Before final delivery, check:

Functionality:

[ ] All links work
[ ] Forms submit correctly
[ ] Mobile menu works
[ ] Images load properly

Content:

[ ] No placeholder text
[ ] No lorem ipsum
[ ] Client info is correct
[ ] Phone/email clickable

SEO:

[ ] Title tags set for all pages
[ ] Meta descriptions written
[ ] Images have alt text
[ ] Sitemap generated

Performance:

[ ] Lighthouse score 90+
[ ] Images optimized
[ ] No console errors

Step 6: Handover Options

Option A: Pagesmith Hosting

Client keeps the site on Pagesmith:

Add client as project collaborator
Transfer ownership (if on their account)
Connect custom domain
Train on basic editing

Train the client:

How to edit text
How to update images
How to publish changes
Who to contact for help

Option B: Export Code

Client takes ownership of the code:

Export the Astro project
Document the setup:
- How to run locally
- How to deploy
- Key files to edit
Deliver via:
- GitHub repository
- ZIP file
- Direct to their host

Include a README:

# [Client] Website

## Quick Start
npm install
npm run dev

## Deployment
npm run build
# Deploy 'dist' folder to any static host

## Key Files
- src/pages/ — All pages
- src/components/ — Reusable components
- public/ — Images and assets
- src/content/ — Blog/docs content (if any)

## Support
Contact: [your email]

Step 7: Post-Launch

Documentation

Create a client handoff doc:

# [Client] Website Handoff

**Live URL:** https://example.com
**Admin access:** [login details if applicable]

## Making Changes

### Simple text edits
[Instructions]

### Adding blog posts
[Instructions]

### Updating images
[Instructions]

## Technical Details

**Hosting:** [where it's hosted]
**Domain:** [registrar]
**Analytics:** [setup]
**Forms:** [where data goes]

## Support

For questions: [your contact]
For emergencies: [your phone]

Maintenance Packages

Offer ongoing support:

Monthly updates
Content changes
Performance monitoring
Security updates
Priority support

Scaling Your Process

Create Templates

Build starter templates for common clients:

Agency templates to create:
- Restaurant (menu, reservations, gallery)
- Service business (services, testimonials, booking)
- Local business (location-focused, Google Maps)
- Professional (case studies, team, services)
- E-commerce-lite (products, inquiry form)

Standardize Prompts

Save your best prompts:

Restaurant prompt:
Create a restaurant website with...

Contractor prompt:
Create a contractor website with...

Reusable Components

Build once, use everywhere:

Header/footer patterns
Contact forms
Testimonial layouts
Pricing tables

Pricing Your Work

Per-Project

Simple site (5 pages): $1,500-3,000
Standard site (10 pages): $3,000-7,000
Complex site (features, integrations): $7,000+

Retainer

Basic maintenance: $200-500/month
Active management: $500-1,500/month

Time Savings

With Pagesmith vs traditional development:

Initial build: 80% faster
Revisions: 60% faster
Handover: Simpler

Common Issues

Client wants endless revisions:

Set revision limits in contract
Batch feedback into rounds
Charge for additional rounds

Client can't provide content:

Offer copywriting add-on
Use AI to generate drafts
Set content deadlines

Client breaks the site:

Version history saves you
Provide training documentation
Offer support retainer

Next Steps

Export — Code export details
Custom Domains — Domain setup
Prompt Engineering — Faster client builds

Build Agency Client Sites

Repeatable workflow for agencies building client websites. Fast delivery, clean handover, and satisfied clients.

Build client websites faster with a repeatable process. This guide covers the workflow from kickoff to handover — designed for agencies and freelancers.

The Agency Workflow

Kickoff — Gather requirements, set expectations
Generate — Create initial site with AI
Refine — Client feedback rounds
Polish — Final details and QA
Handover — Export or deploy, train client

Step 1: Kickoff Checklist

Before starting, gather:

Brand assets:

[ ] Logo (SVG preferred)
[ ] Brand colors (hex codes)
[ ] Typography preferences
[ ] Existing brand guidelines

Content:

[ ] Business description
[ ] Services/products list
[ ] Team bios (if needed)
[ ] Testimonials
[ ] Contact information

Technical:

[ ] Domain name
[ ] Hosting preference
[ ] Third-party integrations needed
[ ] Analytics requirements

Project scope:

[ ] Pages needed
[ ] Key features
[ ] Timeline
[ ] Budget

Step 2: Generate the Base Site

Create a comprehensive initial prompt:

Create a website for [Client Business Name], a [business type]
serving [target audience] in [location if relevant].

Brand:
- Logo: [will upload]
- Primary color: [hex]
- Secondary color: [hex]
- Style: [modern/classic/playful/professional]

Pages needed:
- Homepage: [describe sections]
- [Page 2]: [describe]
- [Page 3]: [describe]
- Contact: form with [fields]

Features:
- [Feature 1]
- [Feature 2]
- [Feature 3]

Footer with:
- Address, phone, email
- Social links
- Quick links
- Copyright

Pro tip: Save templates for common client types (restaurant, salon, contractor, etc.).

Step 3: First Review

Share the initial version with the client:

Publish to a preview URL
Record a Loom walkthrough
Send with structured feedback request

Feedback request template:

Here's your website preview: [URL]

Please review and note:
1. Overall impression — Does it feel right for your brand?
2. Homepage — Any sections to add, remove, or reorder?
3. Content — What text needs updating?
4. Images — Which placeholders need real photos?
5. Other pages — Notes for each page

Please prioritize: What's most important to fix?

Step 4: Iteration Rounds

Process feedback efficiently:

Round 1: Structure

Page layout changes
Section additions/removals
Navigation updates

Round 2: Content

Text updates
Image replacements
Contact info

Round 3: Polish

Color tweaks
Spacing adjustments
Mobile optimization

Batch similar feedback:

Make these text updates:
- Hero headline: "[new text]"
- Services section title: "[new text]"
- CTA button: "[new text]"

Replace these images:
- Hero image: [upload new]
- About page team photo: [upload new]

Step 5: Quality Assurance

Before final delivery, check:

Functionality:

[ ] All links work
[ ] Forms submit correctly
[ ] Mobile menu works
[ ] Images load properly

Content:

[ ] No placeholder text
[ ] No lorem ipsum
[ ] Client info is correct
[ ] Phone/email clickable

SEO:

[ ] Title tags set for all pages
[ ] Meta descriptions written
[ ] Images have alt text
[ ] Sitemap generated

Performance:

[ ] Lighthouse score 90+
[ ] Images optimized
[ ] No console errors

Step 6: Handover Options

Option A: Pagesmith Hosting

Client keeps the site on Pagesmith:

Add client as project collaborator
Transfer ownership (if on their account)
Connect custom domain
Train on basic editing

Train the client:

How to edit text
How to update images
How to publish changes
Who to contact for help

Option B: Export Code

Client takes ownership of the code:

Export the Astro project
Document the setup:
- How to run locally
- How to deploy
- Key files to edit
Deliver via:
- GitHub repository
- ZIP file
- Direct to their host

Include a README:

# [Client] Website

## Quick Start
npm install
npm run dev

## Deployment
npm run build
# Deploy 'dist' folder to any static host

## Key Files
- src/pages/ — All pages
- src/components/ — Reusable components
- public/ — Images and assets
- src/content/ — Blog/docs content (if any)

## Support
Contact: [your email]

Step 7: Post-Launch

Documentation

Create a client handoff doc:

# [Client] Website Handoff

**Live URL:** https://example.com
**Admin access:** [login details if applicable]

## Making Changes

### Simple text edits
[Instructions]

### Adding blog posts
[Instructions]

### Updating images
[Instructions]

## Technical Details

**Hosting:** [where it's hosted]
**Domain:** [registrar]
**Analytics:** [setup]
**Forms:** [where data goes]

## Support

For questions: [your contact]
For emergencies: [your phone]

Maintenance Packages

Offer ongoing support:

Monthly updates
Content changes
Performance monitoring
Security updates
Priority support

Scaling Your Process

Create Templates

Build starter templates for common clients:

Agency templates to create:
- Restaurant (menu, reservations, gallery)
- Service business (services, testimonials, booking)
- Local business (location-focused, Google Maps)
- Professional (case studies, team, services)
- E-commerce-lite (products, inquiry form)

Standardize Prompts

Save your best prompts:

Restaurant prompt:
Create a restaurant website with...

Contractor prompt:
Create a contractor website with...

Reusable Components

Build once, use everywhere:

Header/footer patterns
Contact forms
Testimonial layouts
Pricing tables

Pricing Your Work

Per-Project

Simple site (5 pages): $1,500-3,000
Standard site (10 pages): $3,000-7,000
Complex site (features, integrations): $7,000+

Retainer

Basic maintenance: $200-500/month
Active management: $500-1,500/month

Time Savings

With Pagesmith vs traditional development:

Initial build: 80% faster
Revisions: 60% faster
Handover: Simpler

Common Issues

Client wants endless revisions:

Set revision limits in contract
Batch feedback into rounds
Charge for additional rounds

Client can't provide content:

Offer copywriting add-on
Use AI to generate drafts
Set content deadlines

Client breaks the site:

Version history saves you
Provide training documentation
Offer support retainer

Next Steps

Export — Code export details
Custom Domains — Domain setup
Prompt Engineering — Faster client builds