Form-First Playbooks for Agencies: From Discovery to Retainer Renewals in Google Sheets

Agencies don’t lose clients because they can’t do the work. They lose them because the work feels chaotic:

Discovery notes scattered across email and Notion
Scope changes buried in Slack
Approvals hiding in comment threads
Retainer renewals driven by gut feel instead of clear outcomes

A form‑first playbook, wired into Google Sheets, gives you a different operating model:

One consistent intake → one shared source of truth → one visible pipeline from first conversation to renewal.

Tools like Ezpa.ge make this pattern actually usable day to day: you can ship beautiful, responsive forms with custom URLs, keep them fully on‑brand, and sync everything into Sheets in real time—without waiting on dev or design.

This post walks through a full, end‑to‑end playbook for agencies:

Discovery
Scoping & proposals
Onboarding
In‑flight work & approvals
Reporting
Retainer renewals

All run on forms + Google Sheets.

Why a Form‑First System Matters for Agencies

Before diving into the playbook, it’s worth grounding on why this matters.

1. You reduce chaos and context loss

Every client interaction that isn’t structured ends up as:

A DM you can’t find later
An email thread that only one account manager sees
A half‑filled doc with no clear owner

Form‑driven flows:

Force the right questions at the right time
Standardize how you capture requirements, decisions, and approvals
Make everything searchable and filterable in Google Sheets

If you’ve read our piece on running agencies on forms instead of heavy PM tools, you’ve seen how powerful this pattern can be for everyday work: Form UX for Agencies: Building Client Intakes, Briefs, and Approvals Without a PM Tool.

2. You get a real pipeline, not just a list of projects

With every step—from discovery to renewal—captured via forms into a single Sheet, you can:

See how many opportunities are in discovery vs. proposal vs. onboarding
Track conversion rates between stages
Spot bottlenecks (e.g., approvals always stall at legal; onboarding questionnaires sit unanswered)

Google Sheets becomes your ops brain, not just a passive log. If you want to go deeper on that idea, we break it down in Google Sheets as Your Ops Brain: Advanced Form-Driven Workflows Beyond Simple Syncing.

3. You make renewals a data‑backed conversation

Retainer renewals are much easier when you can say:

“Here’s what you asked for in discovery.”
“Here’s what we scoped and you approved.”
“Here’s what we actually delivered, by month.”
“Here’s the impact we measured.”

A form‑first system gives you that continuity without a complex CRM or project tool.

The Core Stack: Ezpa.ge + Google Sheets

You can implement this playbook with almost any form tool, but Ezpa.ge is designed for exactly this combo:

Custom themes so every client‑facing form feels like your brand (or even your client’s brand)
Custom URLs for each stage (e.g., /acme-discovery, /acme-onboarding, /acme-qbr-feedback)
Real‑time Google Sheets syncing so every submission lands in your ops brain instantly

On top of that, Google Sheets gives you:

Filters and views for each stage (discovery, onboarding, active, at‑risk, renewal)
Simple formulas for SLAs, utilization, and renewal signals
A low‑friction way for the whole team to collaborate without new logins

Stage 1: Discovery – From Vague Interest to Structured Opportunity

Discovery is where most chaos starts. A prospect says, “Can we talk?” and you end up with a loose conversation, a couple of notes, and a lot of assumptions.

Build a Discovery Intake Form

Create a client‑facing discovery form in Ezpa.ge and wire it to a Discovery tab in your Google Sheet.

Include fields that:

Identify the account
- Company name
- Primary contact (name, email, role)
- Industry and approximate company size
Clarify goals and constraints
- Primary goal (multi‑select: lead gen, brand, product launch, lifecycle, etc.)
- Time sensitivity (e.g., “fixed launch date vs. flexible”)
- Budget range (bands, not open text)
Capture current state
- Channels they’re already using
- Internal team capacity (e.g., in‑house design/dev?)
- Existing assets (brand, copy, analytics, CRM)
Surface risks early
- Compliance or legal review required?
- Stakeholder count (how many approvers?)

Pro tip: Use conditional logic so the form adapts. If they choose “Product launch,” show questions about launch date, messaging hierarchy, and success metrics. If they choose “Retainer,” ask about cadence, preferred communication, and decision‑makers.

Wire Discovery into a Live Pipeline View

In Google Sheets:

Create a Discovery tab that receives all form submissions.
Add a Status column with a data‑validation dropdown:
- New
- Qualified
- Not a fit
- Proposal sent
Use filters or views to give sales and leadership a live list of active discovery opportunities.

If you want to turn this into a real‑time queue (e.g., so someone always owns the next discovery call), the patterns in From Form to Live Queue: Building Real-Time Triage for Support, Sales, and Ops with Google Sheets map almost 1:1.

Overhead view of an agency team around a large table, laptops open, with a big wall screen showing a

Stage 2: Scoping & Proposals – Turning Discovery into a Clear Offer

Once discovery is done, the risk is that scope lives in a doc no one reads or a slide that never gets updated.

Instead, build a scope confirmation form that:

Reiterates what you heard in discovery
Lets the client confirm or correct details
Captures structured data for pricing, timing, and risks

The Scope Confirmation Form

Key fields to include:

Reference to the discovery record (e.g., Discovery ID or company name + date)
Project type (campaign, retainer, audit, etc.)
Deliverables list (checkboxes with quantities where possible)
Timeline expectations (kickoff date, major milestones)
Budget confirmation (chosen from your pricing bands)
Success metrics (choose up to 3 primary KPIs)
Approval contact (who signs off on scope and changes)

You can send this as:

A link after your proposal meeting
A follow‑up to a proposal PDF, asking them to “lock in” the version they’re approving

Once submitted, the scope confirmation:

Lands in a Scopes tab in Google Sheets
Links back to the original discovery row via Discovery ID
Can be used to auto‑populate your proposal template or contract (via Sheets add‑ons or no‑code tools)

Why a Form Instead of Just a Doc?

Consistency: Every project is scoped using the same structure.
Traceability: You know exactly which options the client selected and when.
Reporting: You can analyze which scopes close fastest, which deliverables are most common, and which budget bands convert best.

Stage 3: Onboarding – Teaching While You Collect Data

Onboarding is where you either set the relationship up for success or guarantee a stream of “quick questions” and misunderstandings.

A well‑designed onboarding form can:

Collect all the access, assets, and context you need
Educate clients about how you work
Set expectations on timelines, communication, and approvals

We go deeper on this concept—forms that teach while they collect data—in Forms as Lightweight Onboarding Academies: Teaching While You Collect Data.

Designing an Onboarding Form That Feels Like a Guided Tour

Structure your onboarding form into sections:

Access & Accounts
- Logins, permissions, analytics access, ad accounts, CMS, etc.
- Use help text to explain why you need each item and how it will be used.
Brand & Messaging
- Brand guidelines upload
- Voice & tone preferences
- Words/phrases to avoid
Decision‑Making & Communication
- Who signs off on creative?
- Preferred channels (email, Slack, project tool)
- Meeting cadence (weekly, bi‑weekly, monthly)
Risks & Constraints
- Legal/compliance requirements
- Hard dates (events, launches)
- Internal dependencies (e.g., “We’re waiting on product to ship X”)

Each submission flows into an Onboarding tab in Google Sheets, linked to Discovery and Scopes via a common client ID.

Split-screen illustration showing on the left a messy desk with scattered sticky notes and emails, a

Stage 4: In‑Flight Work & Approvals – Keeping Work Visible and Decisions Traceable

Once projects are live, forms can keep approvals and change requests structured instead of buried.

Approval Forms for Creative and Strategy

Instead of “Looks good” in Slack, send clients to a simple approval form for each major deliverable.

Fields might include:

Project / campaign name
Deliverable type (concept, wireframe, ad set, email sequence, etc.)
Link to the asset (Figma, GDrive, etc.)
Decision:
- Approved as is
- Approved with minor edits
- Not approved – needs revision
Required edits (short text)
Priority and due date for revisions

Submissions land in an Approvals tab, giving you:

A history of who approved what, and when
A way to track revision cycles by client, project, or deliverable type
Inputs you can feed into workload planning and pricing (e.g., clients who always need 3+ rounds)

If you’re curious how this pattern can replace a lot of what a ticketing or support queue does, Forms for Service Teams: Replacing Support Queues with Smart Intake and Real-Time Routing explores that angle.

Change Request Forms

Scope creep is inevitable. The problem isn’t that clients ask for more; it’s that you don’t have a structured way to evaluate and price the “more.”

Create a change request form with:

Project reference (lookup from your Scopes tab)
Description of requested change
Reason (new requirement, missed in discovery, external dependency, etc.)
Impact area (timeline, budget, both)
Desired deadline

Internally, your team can:

Review requests in a Change Requests tab
Tag them as billable or non‑billable
Track how often changes come from unclear discovery vs. genuine new opportunities

Stage 5: Reporting – Turning Sheets into a Client‑Ready Story

If every step of the relationship is captured in Sheets, reporting becomes less “assemble a deck from scratch” and more “pull the right views.”

Build a Reporting View per Client

In Google Sheets, create a Client Summary tab that pulls from:

Discovery (goals & constraints)
Scopes (what was promised)
Onboarding (assets, access, decision‑makers)
Approvals (how smoothly work is moving)
Change Requests (how often scope is shifting)

Use FILTER, QUERY, or simple lookups to:

Show work delivered by month
Surface approval cycle length (average days from submission to approval)
Highlight change request volume
Track KPI progress where you have the data

From there, you can:

Export charts for QBR decks
Share a live Sheet view with the client
Use this as the backbone for your renewal conversation

If you want to go further and treat these Sheets as ops dashboards, Forms as Source-of-Truth Dashboards: Turning Google Sheets Views into Live Ops Cockpits shows how to do that in more detail.

Stage 6: Retainer Renewals – Making “Should We Renew?” an Easy Yes

The payoff for a form‑first system is felt most clearly at renewal time.

Instead of scrambling for proof, you can:

Pull the original discovery goals.
Show the scoped work and approved deliverables.
Summarize what actually shipped, including change requests.
Share impact metrics where available.

Then you layer on one more form: a renewal feedback & alignment form.

The Renewal Feedback Form

Send this 30–45 days before renewal:

Overall satisfaction (1–10)
Perceived impact on key goals
What’s working well
What’s not working well
Where they want to invest next cycle (channels, initiatives, experiments)
How they prefer to work with you going forward (cadence, communication, involvement)

This gives you:

Early warning if a renewal is at risk
Clear direction on where to focus the next proposal
Quotes and language you can use to frame your value

Using Sheets to Prioritize and Forecast Renewals

In your main Google Sheet, add a Renewals tab or view that:

Lists all active retainers with end dates
Pulls in satisfaction scores and qualitative feedback
Flags accounts as Healthy, At Risk, or Churn Likely based on a simple scoring model

Now you have:

A renewal pipeline you can manage like sales
A way to forecast revenue and resourcing
A feedback loop you can feed back into discovery, scoping, and onboarding

Making It Real: Implementation Checklist

If this feels like a lot, start small. You don’t have to rebuild your entire agency in a week.

Here’s a pragmatic rollout path:

Pick one client or one new opportunity to pilot with.
Build a discovery form in Ezpa.ge and sync it to a new Google Sheet.
Add a simple scope confirmation form that references that discovery data.
Create a lightweight onboarding form for once the deal is signed.
Set up one approvals form for major deliverables.
Add a renewal feedback form for existing retainers.
Iterate:
- Trim questions that never get used
- Add fields that would have saved you from a recent headache
- Improve themes and copy so forms feel like part of your brand, not an afterthought

As you get comfortable, you can layer on more advanced patterns: URL‑level personalization, AI‑ready field structures, and theme systems that keep everything on‑brand at scale.

Summary

A form‑first playbook for agencies isn’t about more bureaucracy. It’s about:

Clear, consistent discovery so you stop guessing what clients want
Structured scoping and onboarding so projects start with alignment, not confusion
Traceable approvals and change requests so scope creep becomes a choice, not a surprise
Live reporting views in Google Sheets so you always know what’s happening across accounts
Data‑backed retainer renewals that feel like a natural extension of the work, not a last‑minute scramble

With Ezpa.ge and Google Sheets, you can build this system without new headcount, heavy tooling, or long implementations. You’re likely already using forms and Sheets; this is about using them deliberately as the backbone of your client lifecycle.

Your Next Step

You don’t need a grand transformation to get value from this.

Pick one of these to do this week:

Ship a new discovery form in Ezpa.ge for your next prospect call.
Turn your current onboarding doc into a guided onboarding form that teaches while it collects.
Add a renewal feedback form for one retainer that’s 60–90 days from renewal.

Wire it into a Google Sheet. Share the link with your team. Use it for a single client.

Once you see how much smoother that relationship feels, you’ll have your own proof that a form‑first playbook is worth rolling out across the agency.

And when you’re ready to go further—theme systems, URL‑level personalization, AI‑ready fields—you’ll already have the most important piece in place: a habit of running your work through forms that your team (and your clients) actually enjoy using.