Form UX for Agencies: Building Client Intakes, Briefs, and Approvals Without a PM Tool

Agencies don’t fall apart because the work is bad. They fall apart because the work is buried.

Client details live in email threads. Briefs hide in random docs. Approvals are scattered across Slack, WhatsApp, and a couple of “final_final_v3” PDFs. By the time a campaign ships, no one is entirely sure what the client actually signed off on.

You don’t always have the appetite—or budget—for a full project management (PM) rollout. But you do need structure. The good news: for a huge slice of agency operations, you can get there with something you already understand deeply:

Forms + a shared spreadsheet.

With a form builder like Ezpa.ge—where you can create responsive, branded forms with custom URLs and real-time Google Sheets syncing—you can turn messy intake and approvals into a lightweight system your team actually uses.

This post is about how to design that system for agencies: how to use form UX to run client intakes, creative briefs, and approvals without a heavyweight PM tool.

---

Why this matters for agencies

When you strip away the tools, most agency workflows follow the same pattern:

1. Capture context – What is this project? Who’s involved? What does success look like?
2. Shape the work – Turn that context into a brief, scope, and plan.
3. Get decisions – Approvals at the right moments, from the right people.

If any of those three are fuzzy, you pay for it later in:

• Scope creep and rework
• Misaligned expectations
• Slower approvals and delayed launches
• Team burnout from chasing context instead of doing the work

Thoughtful form UX helps by:

• Standardizing inputs – Every new client or project starts from the same high-quality questions.
• Reducing back-and-forth – You collect what you need the first time, in a structured way.
• Creating a single source of truth – Real-time Sheets become the log of record for who said what, when.
• Making work visible – Anyone can see what’s in intake, what’s approved, and what’s waiting.

If you’ve already explored using forms as lightweight CRMs, you’ve seen a version of this pattern in action. If not, it’s worth reading how forms can stand in for heavier systems in Forms as Lightweight CRMs for Agencies: Managing Clients, Briefs, and Approvals Without New Software.

---

The three flows every agency should systematize

You don’t need to rebuild your entire agency in forms. Start with the three flows that cause the most chaos when they’re unstructured:

1. Client intake – From lead → signed client → onboarding.
2. Project / creative brief – From vague ask → concrete, shared understanding.
3. Approvals – From “looks good” in Slack → logged, searchable decisions.

Let’s walk through how to design each one with form UX in mind.

---

1. Designing a client intake that sets projects up to win

Client intake is where small misunderstandings turn into big problems. A great intake form does two jobs at once:

• Collects the hard details (contacts, budget, timelines, constraints)
• Surfaces the soft context (goals, fears, internal politics, decision criteria)

Structure your client intake form

Think in sections, not a giant wall of fields:

1. Basics and contacts

   • Company name, website, primary contact
   • Stakeholders and decision-maker(s)
   • Preferred communication channels

2. Engagement overview

   • What type of work are they hiring you for? (Brand, performance, product design, content, etc.)
   • How did they hear about you? (Useful for routing and attribution.)

3. Goals and success metrics

   • "What would make this engagement a success three months from now?" (Free text)
   • "How will you measure that success?" (Multiple choice + free text)

4. Constraints and realities

   • Budget range (use ranges, not open text, to keep it honest)
   • Ideal timeline and hard deadlines
   • Existing assets or systems you’ll need to plug into

5. Risks and history

   • "Have you worked with an agency on this before? What worked / didn’t?"
   • "What are you most worried about with this project?"

6. Internal alignment

   • "Who needs to approve major decisions?" (Multi-select + role tags)
   • "Is everyone internally aligned on goals and budget?" (Yes/No + optional detail)

UX patterns that help

• Progressive disclosure – Don’t show everything at once. Use conditional logic so follow-up questions appear only when relevant (e.g., show “previous agency experience” questions if they say they’ve hired one before).
• Guidance in microcopy – Under each open-ended question, add a short hint: “2–3 sentences is perfect” or “Examples: increase qualified leads by 30%, launch in time for Q4 events.”
• Input formats that match the data – Use ranges, dropdowns, and radio buttons where you need clean data for routing. Use long text fields where nuance matters.

Once you’re syncing intake responses into Google Sheets in real time, you can turn that Sheet into a live intake board—filtered by stage, owner, or priority. If you want to go deeper on that pattern, Forms as Source-of-Truth Dashboards: Turning Google Sheets Views into Live Ops Cockpits is a helpful companion.

---

2. Turning vague asks into structured creative briefs

Most painful agency stories start the same way:

“The brief was… kind of a Slack thread.”

You can’t control how clients think, but you can control how their requests enter your system. A well-designed brief form acts like a conversation with a sharp strategist—guiding clients from fuzzy ideas to clear, actionable direction.

Start with one “master brief” form

Instead of separate forms for every service line, build one core brief form that adapts based on what the client selects.

Step 1: Identify the project type

Use a required multiple-choice field:

• Brand or visual identity
• Website or product design
• Performance marketing / campaigns
• Content (articles, video, social)
• Research / discovery
• Other (with a short description)

Use conditional logic to reveal relevant sections for each type.

Step 2: Define the problem and audience

Key questions that work across almost any project:

• "What problem are we solving?" (Ask for a short paragraph.)
• "Who is this for?" (Demographics, roles, behaviors.)
• "What do you want them to do after they see this?" (Primary call to action.)

Step 3: Clarify constraints and must-haves

• Non-negotiable requirements (legal, compliance, brand rules)
• Channels and formats (e.g., “Instagram + TikTok”, “desktop web”, “OOH only”)
• Required assets (logos, existing guidelines, product shots)

Step 4: Capture taste and references

• Links to inspiration (competitors, brands they like, past work they loved)
• "What should this not feel like?" (Underrated question.)

Step 5: Timelines and approvals

• Desired launch date
• Internal milestones (e.g., “need first draft before board meeting on…”)
• Named approvers for key phases

UX tips that make briefs actually get filled

• Use friendly language, not agency jargon – “Tell us about your audience” beats “Describe your ICP.”
• Set expectations on effort – At the top, add: “This takes about 8–10 minutes. The more detail you share, the fewer back-and-forth emails later.”
• Use examples generously – For open-ended fields, add a short example answer so clients aren’t staring at a blank box.
• Let them save and return – If your form tool supports it, allow partial saves or send the link as a custom URL they can revisit.

With Ezpa.ge, you can also lean on AI-powered helpers so your team isn’t starting from scratch each time. If you’re curious how to safely use AI to draft fields and logic for these flows, check out AI-Powered Field Suggestions: Letting Models Draft Your Forms Without Losing Control.

---

3. Making approvals traceable without a PM suite

Approvals are where agencies bleed time and trust.

• "Who signed off on this copy?"
• "Did legal actually approve that disclaimer?"
• "Which version of the design did the client say yes to?"

You don’t need a complex workflow engine to fix this. You need:

1. A consistent way to ask for approval
2. A reliable way to log the decision

Design a simple approvals form

Create a form that your team uses internally whenever they need a decision. This can cover:

• Client approvals (concepts, copy, design, media plans)
• Internal approvals (budget, scope changes, discounts)

Core fields to include:

• Project / client – Dropdown or autocomplete, mapped to your intake/CRM Sheet
• Approval type – Concept, copy, design, media plan, scope change, etc.
• Link to artifact – URL to Figma, deck, doc, or video
• Decision requested – Approve, approve with minor edits, or reject
• Due date – When you need a decision
• Approver(s) – Name + role + email
• Summary of changes since last version – Short text

When the approver submits the form, you capture:

• Their decision (approve / changes needed / reject)
• Any comments or conditions
• Timestamp and identity (via email or SSO)

All of this lands in a Google Sheet, giving you an approval log you can filter by client, project, or approver.

If you want to go further, pair this with lightweight auditing so you always know which form version was live when a decision was made. Ops-Ready Form Logs: Lightweight Auditing, Version History, and Change Management for Busy Teams dives into how to keep those trails clean without slowing your team down.

---

Building this without creating chaos

Putting more forms into your agency won’t help if they’re all one-offs with different looks, URLs, and question sets. The system only works if it feels coherent.

1. Standardize themes and branding

Your forms are client-facing touchpoints. They should look like you.

• Use a single, consistent theme for all client-facing forms (intake, briefs, feedback).
• Reserve a separate, clearly different theme for internal-only forms (approvals, internal requests).
• Keep typography, buttons, and error states consistent so clients feel like they’re in the same environment throughout their journey.

If you’re managing multiple brands, sub-brands, or partner programs, invest time in a reusable design system for forms. Theme Tokens, Not One-Off Styles: Building a Form Design System That Scales Across Brands walks through how to avoid “rogue logo” chaos as you grow.

2. Treat URLs as part of your operations

Form links are the front door to your workflows. A bit of URL discipline goes a long way:

• Use predictable patterns like:
  • /intake/client for new clients
  • /brief/{client-name} for project briefs
  • /approval/{project-code} for approvals
• Avoid cloning forms with random URLs that no one remembers.
• Use custom URLs for specific campaigns or partners when you need tailored logic, but keep them tied back to a core form structure.

Over time, this becomes a real system—your team knows where to send clients, and you know which link is the current one.

3. Make Sheets work like a lightweight PM board

You don’t have a PM tool, but you do have Google Sheets. Make them behave like a project board:

• Separate tabs for each flow – Intake, Briefs, Approvals, Changes.
• Status columns – Stage, Owner, Priority, Next action.
• Filtered views for each role – account managers see active clients; creative leads see briefs awaiting scoping; leadership sees approvals stuck for more than 3 days.

You can layer on color-coding, simple formulas, and filters to get 80% of what you’d expect from a PM board—without new software.

---

Practical rollout plan for your agency

If this feels like a lot, start small and iterate. Here’s a 30–60 day path:

Week 1–2: Design and pilot your forms

• Draft v1 of:
  • Client intake form
  • Master brief form
  • Approvals form
• Connect each to its own Google Sheet with real-time syncing.
• Run a quick internal review with account managers, strategists, and creative leads. Ask: “What’s missing?” and “What’s confusing?”

Week 3–4: Roll out to one team or one client segment

• Choose a single pod, vertical, or region to pilot.
• Replace ad-hoc emails with:
  • Intake form for any new client
  • Brief form for any new project
  • Approvals form for all major decisions
• Track friction: where do people get stuck or drop off?

Week 5–8: Refine and formalize

• Tighten questions based on real submissions.
• Normalize data (e.g., standardize budget ranges, channels, industries).
• Add a simple “How was this form?” question at the end to capture UX feedback.
• Document the new process in a short internal playbook: when to use which form, where to find the Sheets, and who owns each stage.

Once these flows are humming, you can expand into adjacent use cases—support intake, partner requests, or internal ops. Posts like Forms for Service Teams: Replacing Support Queues with Smart Intake and Real-Time Routing show how the same patterns apply beyond client work.

---

Summary

You don’t need a full PM stack to run a disciplined agency. You need:

• Clear entry points for work (client intake and briefs)
• Reliable decision logs (approvals)
• A shared operational brain (Sheets) that everyone trusts

By treating forms as the front door to your workflows—and designing them with care—you can:

• Reduce back-and-forth and misalignment
• Capture richer context without overwhelming clients
• Make approvals traceable and auditable
• Give your team a shared view of what’s in play, what’s blocked, and what’s done

The tools are simple; the leverage comes from using them deliberately.

---

Take the first step

You don’t have to redesign your whole agency process this week. Start with one thing:

• Pick the flow that hurts the most right now—client intake, briefs, or approvals.
• Sketch the questions you wish you had every time.
• Turn that into a single, well-designed form connected to a Sheet.
• Run it with your next new client or project.

Once you see how much smoother that one slice of work becomes, you’ll have the momentum—and the internal proof—to keep going.

If you’re ready to experiment, open Ezpa.ge, create a new form with your agency’s branding, sync it to a Google Sheet, and ship your first structured intake link. From there, you can evolve it into the lightweight, form-driven ops system your agency has been missing.