Website builder

Make case studies the heart of your agency website
and send each brief to the right lead.

Describe your studio and Netiva’s AI builds the site: case studies, services and team pages from linked collections, a project inquiry form and code you can export when a client site is ready to hand over.

Start building free More website ideas
Starter prompt

Build a website for a 12-person design and development agency with collections for services, team members, case studies and project inquiries. Each case study links to a service and has an industry, completion date, cover image, story and client sign-off status; show only approved ones, newest first. The work page filters by industry and service. Service pages list deliverables, timeline and related case studies. The team page groups current staff by discipline. A start-a-project form collects name, work email, company, service, budget band, target launch date and an optional brief, then emails that service’s lead.

Build it in Netiva Paste the prompt into a new workspace and adjust it to your business.
Overview

Who this agency website is for

Agency sites tend to fall behind the work they’re meant to show. Case studies wait for a designer to lay out a one-off page, the team page still lists people who left last spring and the contact form drops every brief into one shared inbox. An agency website built with Netiva keeps case studies, services and team members in linked collections, so a finished project becomes a page once the client signs off. Project inquiries arrive with a budget band, a target launch date and the brief attached, and go straight to the lead for that service.

Key features

What your agency website can do

  • Case studies with client sign-off

    Each project is a row in a case studies collection with the client, industry, main service, cover image, completion date and the full story. List and detail pages render from it, and a sign-off field decides what goes public.

    • A work page ordered by completion date and filtered by industry and service
    • Unapproved or embargoed projects kept off the site
    • An “approved without name” option that shows the industry instead of the client
    • Results and approved client quotes set inside each story

  • Service and team pages that stay linked

    Services and team members are their own collections, related to each other and to your case studies. When someone joins, changes role or leaves, you edit one record and every page that mentions them follows.

    • Service pages with deliverables, engagement type and typical timeline
    • Each service page names its lead and the case studies that used it
    • A team page grouped by discipline, with alumni hidden by one status field
    • The collection assistant trims every bio to one length and voice

  • Project inquiries routed by service

    The start-a-project form saves each inquiry with the prospect’s name and work email, the service, budget band, target launch date and any brief they upload. The lead for that service gets an email, and you triage in the collection grid.

    • Budget bands and launch dates in the ranges you choose
    • Brief, RFP or sitemap files attached to the inquiry
    • An email to the service lead for every new inquiry
    • Saved views in the grid for new, qualified and not-a-fit inquiries

  • Client site handover

    Build client sites in Netiva the same way you built your own. At launch, connect the client’s domain, mark the release with a checkpoint and export the code for clients whose developers want to take it over.

    • Client domains connected from the Starter plan with the DNS records Netiva lists
    • A launch checkpoint to compare against or roll back to
    • Exported code with no proprietary runtime
    • Content kept in collections, so client editors work in a grid instead of code
Data model

The collections behind it

Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.

Case studies

One record per finished project, with the story and the client’s permission to publish it.

  • Title (required) Text
  • Client (required) Shown only when the sign-off allows naming the client Text
  • Industry (required) Healthcare, Fintech, Hospitality… Text
  • Service (required) The main service, used by the work filter and service pages Relation to Services
  • Completed (required) Sorts the work grid and picks the next project Date
  • Cover image (required) Image
  • Story (required) Challenge, approach and results, with screenshots and quotes the client approved HTML
  • Client sign-off (required) Pending, Approved, Approved without name or Declined Text

Services

What the agency sells and how each engagement is shaped.

  • Name (required) Text
  • Summary (required) One or two sentences for the service cards that link to each service page Paragraph
  • Deliverables (required) One per line, such as brand audit, logo suite and guidelines Paragraph
  • Engagement type (required) Fixed project, Monthly retainer or Sprint Text
  • Typical timeline Written as a range, such as 6–10 weeks Text
  • Service lead (required) Receives the inquiry emails for this service Relation to Team members
  • Menu order Position in the navigation and in the service cards Number

Team members

Everyone who appears on the site, past and present.

  • Name (required) Text
  • Role (required) Job title as it should read on the site Text
  • Discipline (required) Strategy, Design, Development, Content, Paid media Text
  • Headshot Image
  • Bio Paragraph
  • Work email Where inquiry emails go when this person leads a service Text
  • Status (required) Current or Alumni; alumni drop off the team page without losing the record Text

Inquiries

Every brief sent through the start-a-project form.

  • Contact name (required) Text
  • Company (required) Text
  • Email (required) Text
  • Service (required) Relation to Services
  • Budget band (required) The ranges you offer in the form’s dropdown Text
  • Target launch Date
  • Brief Brief, RFP or sitemap uploaded by the prospect File
  • Status (required) New, Qualified, Proposal sent, Won, Lost or Not a fit Text

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

A typical first version. Ask the agent for more, or annotate the preview to change any of them.

  • Work

    A grid of approved case studies, newest first, with filters for industry and service; projects approved without a name show their industry instead of the client.

    Public

  • Case study

    The full story with cover image, results and client quotes, the service behind it and a link to the next project completed in the same industry.

    Public

  • Service

    Deliverables, engagement type and typical timeline, the service lead and the case studies that used this service, with a button that opens the form with the service already chosen.

    Public

  • Team

    Current staff grouped by discipline, each with a headshot, role and short bio. Alumni are left off.

    Public

  • Start a project

    The inquiry form: name, work email, company, service, budget band, target launch date and an optional brief upload, then a confirmation email to the prospect.

    Public

  • Inquiries

    New-business triage for the team: inquiries by status and service, with the brief attached and a one-click status change.

    Your team
How it works

From prompt to a live agency website

  1. Describe your agency

    Tell Netiva which disciplines you cover, how you sell work — fixed projects, retainers or sprints — and who leads each service. The agent drafts the services, team, case study and inquiry collections and the pages that use them.

  2. Write up the work

    Add past projects in the collection grid, or give the collection assistant your project notes and have it draft case studies for review. Leave sign-off at Pending until each client approves.

  3. Review it like a prospect

    Click through the work filters in the live preview, submit a test brief and check that the right lead gets the email. Annotate anything off-brand and the agent fixes it.

  4. Launch, then reuse the process

    Publish in one click on your own domain (custom domains start on the Starter plan), then have the agent redirect your old case study URLs to the new ones so links in award entries and newsletters still land. Build client sites the same way.

Why Netiva

Netiva vs a traditional build

Building an agency website with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Publishing a new case study A new row in the case studies collection becomes a page as soon as the client signs off A designer lays out a one-off page and a developer ships it weeks after the project ends
Client handover The client’s domain connected by DNS records, a launch checkpoint and code they can export A zip of theme files, a plugin list and a shared password document
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A five-person brand identity studio

    Most projects stay under NDA until the client unveils its new brand. Case studies are written as the work wraps up and sit at Pending, then go live the day the client approves — some with the client’s name, some as “a regional credit union”.

  • A performance marketing agency on retainers

    Service pages for paid search, paid social and lifecycle email each name their channel lead. The form asks for a monthly media budget band, and every inquiry is emailed to the lead for the channel the prospect picked.

  • A 20-person integrated agency

    Inbound briefs arrive faster than anyone can read them. The new-business lead works the signed-in inquiries screen each morning, marks anything under the studio’s minimum fee as Not a fit and leaves the rest with their uploaded RFP attached for the weekly pitch review.

Good to know

Before you build

  • Client permission comes first

    Many agency contracts limit naming a client, showing its logo or sharing results. Keep the sign-off field accurate and quote only what clients actually said: in the US, the FTC’s Endorsement Guides expect a testimonial to reflect the endorser’s honest opinion.

  • Agree where client sites live

    Decide whose workspace each client site sits on and who holds the domain registration. Every site is its own workspace, so the plan follows how many you run. Custom domains need Starter, and role-based access covers people in your Netiva workspace; client editors use the grid.

  • Your CRM and proposals stay separate

    The inquiry list is a triage inbox, not a sales pipeline or proposal tool. Inquiries only reach your CRM if it offers a REST API you connect, with the key stored securely.

  • Accessibility checks are still yours

    Netiva doesn’t audit a site for accessibility. Test your own site and every client site against WCAG 2.2 before handover, and make sure every case study image has meaningful alt text.

FAQ

Questions about building an agency website

Can I build client websites with Netiva, not just my agency site?

Yes. Netiva builds marketing sites, online stores, booking systems, portfolios, docs and web apps, so the same chat-based process works for client projects. You describe each client site to the agent, steer it by annotating the live preview and invite colleagues into the workspace to comment and build together. Every change is checkpointed, so an experiment on a client site is easy to undo.

How do we move our existing case studies and team bios across?

By hand, in the collection grid — Netiva has no importer. Most studios paste each case study’s text into the story field, upload the cover image and set the industry, service, completion date and sign-off as they go. The collection assistant helps once the rows exist: ask it to trim every bio to the same length, make role titles consistent or draft a case study from your project notes for review.

Can a case study stay hidden until the client approves it?

Yes. The client sign-off field starts at Pending, and the work page only lists case studies marked Approved or Approved without name. The second option swaps the client’s name for its industry, which suits projects under NDA. You can write the story while the work is still under wraps and publish it by changing one field when the client agrees.

Can new project inquiries go to different people by service?

Yes. Each service has a lead, and when a prospect picks that service on the form, the app emails the lead with the budget band, target launch date and any uploaded brief. The team works through inquiries on a signed-in screen, filtered by status and service, with a one-click status change. If your CRM has a REST API, you can ask the agent to send each inquiry there too.

Can our designers change layouts without touching code?

Yes. Designers annotate the live preview — point at a case study card or a section of a service page and describe the change — and the agent updates it. No coding is needed. Developers on your team can still switch to the code view and edit files directly, and the output is clean, framework-standard code you can review like any other project.

Which Netiva plan suits an agency building client sites?

You can start free, without a credit card. Each site you build — yours and each client’s — is its own workspace, so the plan depends on how many client sites you run at once. The free plan and Starter each cover a single workspace, and the higher plans add many more. Connecting a custom domain needs Starter or higher, and white-labeling is an Enterprise feature. Plans change, so compare the current options on Netiva’s pricing page before you commit client work.

Keep exploring
All ideas
Compare

How Netiva compares

All comparisons

Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.

Build your agency website today

Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.

Start building free Browse more ideas