Guides
How a web design agency handles client requests after launch
How web design agencies triage, scope and bill client requests after launch, from intake forms to retainers, support desk tiers and renewals.
What to take away
- A single intake form and a ticket number are the backbone of any post-launch support workflow for design agencies.
- Triage every request into one of four tiers so a broken checkout never waits behind a copy tweak.
- Bill small fixes by time and materials, hold a retainer for maintenance, and quote new pages as separate projects.
- Write response times into the contract before launch, using a service level agreement the client has already read.
- Keep the request log for ninety days and use it as evidence when the renewal conversation opens.
Intake: one doorway, one ticket
A request that arrives by phone, text and email at once will be handled twice. Give clients one doorway, usually a short form, and a ticket number in return.
Intake to first response
- Log ticketclient, URL, requester
- Ask for single outcome defining done
- Assign tier and first response target
- Reply with fix window or scoping question
The form should ask for the page URL, the browser, the device, and one sentence describing the result the client wants to see.
The web design agency client request process begins with that written record. Anything not written down cannot be triaged, timed or billed.
- Log the ticket with client name, URL and requester.
- Ask for the single outcome that defines done.
- Assign a tier and a first response target.
- Reply with either a fix window or a scoping question.
Time tracking keeps the record honest. Wikipedia's overview of time tracking shows how professional services convert minutes into invoices and estimates.
Triage tiers for a small studio
Not every request deserves the same clock. A four tier model keeps the queue readable for a team of three. Client request triage for small studios works best when each ticket has one owner and one tier.
Four triage tiers
Tier 1
- Request
- Broken form, checkout
- Response
- Same business day
- Billing
- Retainer
Tier 2
- Request
- Copy swap, image
- Response
- Two to three days
- Billing
- Hourly or retainer
Tier 3
- Request
- New template, integration
- Response
- Quoted project
- Billing
- Fixed fee
Tier 4
- Request
- Strategy, redesign
- Response
- Scheduled call
- Billing
- Discovery
| Tier | Typical request | Response target | Billing |
|---|---|---|---|
| 1 | Broken form, checkout error, site down | Same business day | Retainer |
| 2 | Copy swap, image change, new section | Two to three days | Hourly or retainer |
| 3 | New template, integration, second language | Quoted as a project | Fixed fee |
| 4 | Strategy, analytics, redesign talk | Scheduled call | Discovery |
Tier one requests get a same day answer even if the fix lands later. Tier four requests belong on a call, not in a ticket thread.
A service level agreement defines those windows in writing. Wikipedia's page on service level agreements describes the response and resolution targets that maintenance contracts usually carry.
A retainer is not a discount. It is a reservation of hours the client has already paid for.
Scoping a change that touches code
- Confirm which template or component the request touches.
- Check the change against mobile and tablet breakpoints.
- Ask whether content, translations or redirects move with it.
- Add QA time to the estimate, not just build time.
Managing change requests web design work means separating a corrective fix from an enhancement. A copy swap is corrective. A new pricing calculator is adaptive work that changes what the site can do.
Scoping a code-touching change
- Confirm template or component touched
- Check mobile and tablet breakpoints
- Ask if content, translations, redirects move
- Add QA time to the estimate
Maintenance budgets fall into corrective, adaptive and perfective buckets, and only the first is a promise the agency already made.
Billing models for ongoing work
Time and materials suits unpredictable small fixes. A retainer suits steady maintenance. A fixed fee suits a defined scope with a clear end.
Retainers trade a lower hourly rate for guaranteed volume. Clients get predictable costs and the agency gets a forecast it can staff against.
When volume passes the team's capacity, agencies hire or outsource. U.S. rules on independent contractor classification matter here. The IRS definition of an independent contractor explains the control and behavior tests.
Example: a plugin update becomes three tickets
A client's booking plugin updates and the confirmation email stops sending. That is tier one. Same day triage, and the retainer covers the fix.
The next morning the client asks for a new field on the booking form. That is tier two, roughly two hours of work.
By Friday the client wants a second booking flow for another service line. That is tier three, a quoted project with its own scope document and QA window.
When compliance or a second language shapes the ticket
Support requests from regulated clients carry documentation duties. Agencies working with Ontario organizations that have 50 or more employees face accessibility reporting. The AODA web design Ontario rules page sets out what designers must disclose and record under WCAG 2.0 AA.
Two language markets double the content workload. Bilingual web design work in Miami and Los Angeles explains how one codebase can serve two keyword sets and two trust narratives.
From tickets to renewals
A quiet month is not always a happy month. Churn after launch has four repeatable causes, and this explanation of why clients vanish after kickoff is worth reading before the silence stretches.
The support log becomes the renewal argument. The guide on expiring contracts and renewals starts ninety days early with measured results and a written scope for the next project.
Most studios also keep a support desk tool. A shared inbox plus a tracker such as Help Scout or Zendesk handles a team of three without extra process.
