A working guide for choosing web-design acquisition channels against the build, buyer, proof, sales path, and delivery capacity.
Web design lead generation goes wrong before a campaign launches. The agency sells “a website,” mixes brochure builds with ecommerce migrations, and counts every form or meeting as demand. Sales then qualifies work that production cannot finish inside the launch window.
A useful acquisition system starts with the engagement. A five-page marketing site, a Shopify replatform, a landing-page batch, ongoing maintenance, and white-label production each have different buyers, artifacts, approvals, sales lags, and acceptance milestones. Their channels cannot be judged with one blended dashboard.
This guide shows how to get more web design leads without promising volume or importing someone else's benchmarks. You will define one sellable build, map buyer alternatives, preserve every funnel stage, test a suitable channel, and reconcile the resulting cohort with accepted delivery.
Working rule: choose the engagement first, then the channel. Treat ticket range, margin, capacity, budget, bid, creative volume, and test duration as operator-supplied inputs. Keep a form, qualified enquiry, booked job, and completed job separate all the way to the decision.
Define One Web-Design Engagement the Agency Can Finish
Choose one bounded engagement before selecting an acquisition channel: a brochure site, ecommerce build, redesign or replatform, landing-page batch, maintenance retainer, or white-label package. Document its buyer, exclusions, economics, hours, capacity, gates, launch window, acceptance milestone, and pause rule using numbers supplied by your own operation.
“Custom web design” is too loose to qualify against. A brochure-site buyer may need positioning, copy, photography, and a fixed launch date. An ecommerce replatform can add catalog migration, payment configuration, integrations, redirects, QA, and security review. A landing-page batch may depend on approved campaign copy and ad launch dates. White-label work adds partner review, end-client visibility rules, and artifact ownership.
Where people go wrong is filling the economics card with a public agency benchmark. Your contract floor, typical range, gross-margin input, and delivery hours must come from completed internal work. If those values have not been calculated, enter unavailable. Do not turn a competitor's published package into your production plan.
Engagement-economics card
| Field | Agency entry | Why it changes acquisition |
|---|---|---|
| Engagement and buyer | Brochure / ecommerce / replatform / pages / maintenance / white-label: ___; buyer: ___ | Sets message, authority, and proof |
| Demand profile | Urgent or planned: ___; seasonal or launch window: ___ | Sets response and sales timing |
| Commercial model | Project / retainer / white-label: ___; contract floor: ___; ticket range: ___ | Sets the operator's spending boundary |
| Production inputs | Gross-margin input: ___; delivery hours: ___; owner: ___; open slots: ___ | Prevents selling past the team's bench |
| Buyer gates | Procurement, security, CMS, credentials, accessibility: ___ | Filters unreachable work early |
| Delivery endpoint | Acceptance milestone: ___; pause condition: ___ | Defines completed work and when ads stop |
Write the acceptance milestone as an observable event. Examples include written acceptance after launch QA, approved transfer of the landing-page batch, or partner acceptance of a white-label package. A signature, deposit, staging link, or nominal launch date alone does not establish completed delivery.
Map Competitive Density and the Buyer's Real Alternatives
Map every credible alternative for this exact build, using search results, CRM loss reasons, proposal records, and buyer interviews. A web-design buyer may compare local and remote agencies, niche specialists, freelancers, marketplaces, templates, AI or no-code tools, and an in-house hire. Local presence is evidence only when your buyers say it matters.
The dated research query returned a local pack. That proves a pack appeared for that query on that date; it does not prove every web-design buyer prefers a nearby provider. Use the SBA's market-research questions to examine demand, location, saturation, and alternatives, then ask recent wins and losses what entered their shortlist.
| Alternative | Why it enters the shortlist | Evidence to collect | Your response question |
|---|---|---|---|
| Local full-service agency | Workshops, local referrals, shared hours | Local results; buyer interview; win/loss note | Did proximity change access or approval? |
| Remote or niche agency | Sector, CMS, ecommerce, or replatform depth | Proposal shortlist; competitor portfolio | Which specialist proof mattered? |
| Freelancer | Direct access to a designer or developer | Loss reason; buyer interview | Was the choice about scope, trust, or price? |
| Marketplace or directory | Multiple providers in one comparison path | Referral field; vendor terms | Who sourced and qualified the enquiry? |
| Template, site builder, AI, or no-code option | Buyer plans to assemble internally | Discovery notes; churn or loss reason | Which integration or judgment gap remains? |
| In-house team | Ongoing control and institutional context | Hiring plan; interview; proposal note | Is the need temporary capacity or ownership? |
Segment the map by engagement. A founder commissioning a new marketing site sees different alternatives from an enterprise team replatforming an ecommerce catalog. Recheck it when a CMS partner enters your market, your portfolio shifts sectors, or repeated losses expose a missing credential. The map is a decision input, not a page of competitor logos.
Build the Full Acquisition-to-Delivery Dictionary
Give each stage its own entry rule, timestamp, system, owner, exclusions, and next evidence. An impression, click, call click, form, qualified enquiry, discovery, proposal, signed agreement, booked job, completed job, and renewal or expansion are distinct records. This separation keeps sales activity from being reported as accepted website delivery.
GA4 recommends distinct lead events for generated, working, qualified, disqualified, and converted leads. Use that guidance for instrumentation while preserving your agency's finer business stages. The practical failure is an analytics event named “conversion” feeding a slide that sales reads as a client.
| Stage | Entry rule and timestamp | System | Owner | Exclusions | Next evidence |
|---|---|---|---|---|---|
| Impression | Platform records attributable display; platform time | Channel export | Acquisition | Tests, internal, invalid traffic | Unique attributable click |
| Click | Unique attributable destination click; click time | Channel + analytics | Acquisition | Tests, duplicates, invalid traffic | Call click or form |
| Call click | Unique tap on tracked call control; event time | Event log | Sales operations | Tests, duplicates, unconnected taps | Matched call or enquiry |
| Form | Valid submission received; submission time | Form system | Sales operations | Spam, tests, duplicates | Qualification decision |
| Qualified enquiry | Meets written engagement and capacity rule; decision time | CRM | Sales operations | Vendors, applicants, unsupported builds | Discovery held |
| Discovery held | Required attendees complete agenda; end time | Calendar + CRM | Sales owner | No-shows, cancellations | Proposal decision |
| Proposal sent | Approved scope delivered; send time | Proposal system | Revenue owner | Drafts, informal estimates | Buyer decision |
| Signed agreement | Authorized signatures complete; signature time | Contract system | Revenue owner | Unsigned or expired documents | Booked-job rule |
| Booked job | Agreement plus agency's deposit or scheduling rule; booking time | CRM + billing/scheduling | Revenue owner | Unresolved conflicts, pre-booking cancellations | Production start |
| Completed job | Engagement-specific acceptance milestone met; acceptance time | Project + acceptance record | Delivery owner | Canceled, refunded, incomplete work | Closeout review |
| Renewal or expansion | New approved term or scope meets written rule; effective time | Contract + CRM | Account owner | Informal interest, unresolved change request | Separate delivery milestone |
Call clicks require special care. A tap is not a connected call, and a connected call is not automatically a qualified enquiry. Likewise, a booked discovery call can become a no-show. Keep the source event while adding later evidence; do not overwrite the first stage with the latest status.
Build an acquisition system your sales and delivery teams can both inspect. Start with one engagement and one evidence path from response to accepted work.
Match Channels to Urgency, Proof, and the Sales Path
Choose channels by the engagement's buyer access, urgency, required proof, intake coverage, and delivery capacity. Referrals, partnerships, content, outbound, communities, directories, social, Google Ads, and Meta Ads can serve different paths. Record the earliest useful stage and a stop condition; no channel is universally best for web-design work.
A planned replatform with procurement gates needs deeper proof and a longer buying path than a bounded landing-page batch tied to a launch. White-label production can depend on agency-partner access and artifact rules. Maintenance may originate after a completed build rather than from a cold campaign. This is why a ranked “top channels” list is operationally weak.
| Channel | Engagement and urgency fit | Reachable-audience evidence | Required proof | Cost/effort owner | Consent or policy gate | Intake dependency | Earliest useful stage | Stop condition |
|---|---|---|---|---|---|---|---|---|
| Permissioned referrals | Trust-heavy builds and replatforms | Named introducer network | Approved relevant artifact | Partnership owner | Permission to introduce | Fast routing by build type | Qualified enquiry | Introductions repeatedly miss scope |
| Partnerships / white-label | Repeatable production for complementary firms | Partner list and overlap notes | Process, capacity, ownership terms | Partnership owner | Contract, conflict, artifact rights | Partner-specific intake | Discovery held | Scope or review load breaks capacity |
| Owned expertise / content | Planned builds with research questions | Search and buyer-interview evidence | Original guide, teardown, or case | Content owner | Claim and artifact permission | Page-to-engagement match | Qualified enquiry | Audience or enquiry fit stays outside rule |
| Bounded outbound | Narrow trigger, sector, CMS, or migration need | Documented prospect source | Relevant observation, not a fake audit | Sales owner | CAN-SPAM and suppression process | Reply and opt-out coverage | Qualified enquiry | Consent issue or preset time cap |
| Communities / events | Trust-building for specialist work | Membership or attendee evidence | Useful workshop or answer | Founder or specialist | Community promotion rules | Manual source capture | Discovery held | Participation creates no fit evidence |
| Directories / marketplaces | Buyers comparing providers | Category and market availability | Profile and approved portfolio | Acquisition owner | Vendor source, consent, terms | Duplicate and refund handling | Form or enquiry | Provenance fails or cohort misses rule |
| Organic social | Artifact-led awareness and partner reach | Audience-role review | Approved work and informed commentary | Content owner | Client permission and platform rules | Attributed destination | Click | Wrong audience under declared cap |
| Google Ads | Declared search demand for one engagement | Keyword and query evidence | Specific offer and landing page | Paid owner | Google policy and claim review | Call/form qualification coverage | Click | Spend cap or query mismatch |
| Meta Ads | Defined audience and proof-led creative test | Audience hypothesis and placement data | Permissioned artifact or sample | Paid owner | Meta policy and claim review | Fast form and sales follow-up | Impression | Spend cap, creative fatigue, or poor fit |
Google documents ads across its surfaces, and Meta documents ads across Meta placements. Those sources establish availability, not results or fit. Set budget and bid limits from your own economics card. Build creative around one engagement, one buyer problem, one approved proof artifact, and one action. Use the broader Google Ads versus SEO decision guide when choosing the acquisition model, not platform setup.
Local Services Ads and Google Guaranteed need an explicit eligibility check before they enter a web-design plan. This research does not establish web-design category or geography eligibility, so do not budget for either or display the badge based on assumption. For lead aggregators or marketplaces such as Angi/HomeAdvisor or Thumbtack, first verify that the offered web-design category exists for your market, then run the vendor audit below. A familiar brand name is not provenance.
Vendor-supplied-enquiry audit
- Source and consent: where was the person acquired, what did the notice say, and what contact did it permit?
- Exclusivity: how many providers can receive the same record, and how is that disclosed?
- Duplicate rule: what keys and time window define a duplicate?
- Refund or replacement: which states qualify, who decides, and by what deadline?
- Qualification: does the record meet your build, buyer, timing, contract-floor, and capacity rule?
- Attribution and completion: can the source survive into CRM, project acceptance, and finance records?
Build a Proof Ledger Before Publishing Claims
Log every claim and the artifact that supports it before a portfolio page, ad, email, proposal, or social post goes live. Separate case studies, testimonials, portfolio artifacts, teardowns, samples, credentials, and founder opinions. Record permission, baseline and window where relevant, scope, exclusions, reviewer, expiry, and exact approved wording.
A screenshot of a homepage may show design craft, but it does not prove conversion, revenue, or your ownership of every asset. A client quote does not authorize an agency to publish analytics. A redesign comparison needs permission for both states and an accurate account of what your team changed. If the result record is absent, the approved result wording is unavailable.
| Claim | Artifact | Permission | Baseline/window/result rule | Scope and exclusions | Reviewer / expiry | Approved wording |
|---|---|---|---|---|---|---|
| Designed the marketing site | Contract + accepted page set | Client publication approval: ___ | Not a performance claim | Pages and contributors: ___ | Owner: ___ / date: ___ | Exact credit: ___ |
| Improved a measured outcome | Authorized analytics + change log | Metric and name approval: ___ | Baseline: ___; window: ___; rule: ___ | Other changes: ___ | Analyst: ___ / expiry: ___ | Approved or unavailable |
| Client testimonial | Original statement + identity record | Use and channel permission: ___ | Date and relationship: ___ | Editing and incentive: ___ | Reviewer: ___ / expiry: ___ | Approved excerpt: ___ |
| Original teardown | Agency analysis | Asset-use basis: ___ | Observation date: ___ | No implied client relationship | Editor: ___ / expiry: ___ | Opinion labels: ___ |
| Sample deliverable | Agency-owned mock artifact | Ownership verified: ___ | No client result | Clearly labeled sample | Creative lead: ___ / expiry: ___ | Sample wording: ___ |
| Credential | Issuer record | Display terms checked: ___ | Issue/expiry dates: ___ | Holder and covered service | Ops: ___ / expiry: ___ | Exact credential: ___ |
The FTC's reviews and testimonials guidance addresses fake or false reviews and sentiment-conditioned incentives. Treat it as a US federal floor, not legal advice. The working discipline is simple: provenance follows the artifact, permission is channel-specific, and expiry forces stale claims back through review.
Qualify Enquiries Against the Engagement Reality
Qualify a web-design enquiry against the offered build, not a generic lead score. Confirm buyer authority, contract-floor rule, launch window, content readiness, CMS constraints, accessibility or security needs, procurement, geography, conflicts, sales coverage, and delivery capacity. A good-fit buyer can still be unserviceable during a full production calendar.
Use a form for routing facts and a human review for context. An ecommerce replatform request should identify the current platform, destination constraints, catalog or integration scope, and launch dependency. A brochure build should reveal who owns copy and media. A white-label request should expose the review chain, end-client contact rule, credit, and intellectual-property terms before discovery.
Qualification gate
- Offered project: does the request match the declared brochure, ecommerce, replatform, page-batch, maintenance, or white-label engagement?
- Buyer and commercial rule: can this contact authorize the process, and does the request meet the operator-supplied contract floor?
- Timeline: is the launch window real, and can discovery, content, design, development, QA, and acceptance fit?
- Inputs: are copy, brand assets, catalog data, access, and internal reviewers ready under the scope?
- Technical gates: do CMS, hosting, integration, accessibility, security, or procurement needs match the team's capability?
- Operating fit: do geography, time zone, conflict checks, sales capacity, and delivery slots pass today?
Web-design agencies do not have one universal trade license, permit, or bond rule. Verify the agency's jurisdiction and the client's sector requirements instead of adding a generic badge to intake. Regulated-sector security, accessibility, privacy, or procurement requirements can change scope and reviewer access even when the visual brief looks straightforward.
Record disqualification reasons without deleting the source. Useful failure states include spam, vendor, applicant, unsupported service, geography or time-zone mismatch, budget or timing mismatch, no-show, declined proposal, unsigned agreement, capacity rejection, cancellation, refund, incomplete work, and an immature retainer. These states explain the channel; a single “lost” label does not.
Run One Bounded Channel Experiment
Test one channel with a written hypothesis, audience source, geography, engagement, proof, action, dates, spend or time cap, source system, owner, stage events, exclusions, lags, stop conditions, and review date. The correct duration and budget come from your build economics and evidence window, not a portable four-week rule.
A usable hypothesis reads: “For [engagement], [documented audience] will reach [earliest useful stage] after seeing [approved proof] and taking [action].” It does not claim a lead count. For paid search, add the keyword theme, negative-query review owner, budget ceiling, bid rule, landing-page version, and call/form coverage. For Meta, add audience hypothesis, placement review, creative versions, frequency review, and the same qualification path.
Bounded-experiment sheet
| Field | Required entry | Web-design check |
|---|---|---|
| Hypothesis | Audience + engagement + proof + action + stage | One build, not “websites” |
| Audience source | Origin, permission, reachable count if known | Sector, CMS, trigger, or relationship recorded |
| Market | Geography and time zone | Workshop and delivery-hour limits |
| Offer and proof | Scope, exclusions, artifact, approved wording | Launch and acceptance terms visible |
| Creative | Message, format, version, owner | Shows actual deliverable; avoids invented results |
| Cap | Start/end; spend cap; labor cap; bid rule if paid | Derived from internal economics |
| Measurement | Source system, stage events, timestamps, owner | Form and call-click remain separate |
| Maturity | Sales, procurement, delivery, and acceptance lag | Matches the chosen build |
| Stop conditions | Consent issue, mismatch, cap, capacity, or policy breach | Pauses before production overload |
| Review | Date, attendees, decision rights | Acquisition, sales, delivery, and finance represented |
For outbound commercial email, the FTC says CAN-SPAM applies to B2B messages and sets requirements around sender information, subject lines, physical address, opt-out, and suppression. Treat that as a US federal floor and obtain advice for other laws or markets. A list vendor does not transfer compliance ownership away from the sender.
Where operators lose control is changing the audience, offer, creative, and qualification rule in the same test. Keep a change log. Stop immediately for a consent or policy problem. Stop at the declared cap for wrong-service requests, unusable geography, or exhausted capacity. A quiet week does not authorize an open-ended budget.
Turn your web-design expertise into an owned acquisition asset. theStacc researches keywords, drafts, scores, queues, and publishes content while your team retains claim and engagement decisions.
Reconcile Channel Evidence With Completed Delivery
Review only mature cohorts after the chosen engagement's sales, production, and acceptance lags have elapsed. Compare qualified enquiries, booked jobs, accepted completions, cancellations, refunds, scope changes, capacity rejections, and immature retainers. Then diagnose audience, proof, intake, sales, or delivery failure before deciding to keep, change, or stop the channel.
A channel can bring suitable ecommerce replatform enquiries while the agency loses them during security review. Another can create signed brochure-site work that stalls because client copy never arrives. A third can produce landing-page requests the production team rejects during a campaign rush. Those are different failures and need different changes.
Approved cohort formulas
| Formula | Numerator | Denominator | Evidence window | Source system | Owner | Exclusions |
|---|---|---|---|---|---|---|
| Qualified-enquiry rate | Unique attributable enquiries meeting the written engagement, buyer, timing, procurement, contract-floor, sales-capacity, and delivery-capacity rule | All unique attributable call/form enquiries received in the same declared cohort | Declared acquisition cohort plus stated qualification lag | Channel export + call/form log + CRM | Sales operations owner | Tests, spam, duplicates, vendors, applicants, unsupported work/geography, unattributable enquiries |
| Booked-job rate | Unique qualified enquiries satisfying the written booked-job rule | All unique qualified enquiries created in the same cohort | Declared cohort plus stated sales/procurement lag | CRM + contract + scheduling/billing system | Revenue owner | Unsigned/expired proposals, partnerships, cancellations before the booked-job rule, unresolved conflicts |
| Cost per completed job | Direct attributable channel spend for the cohort | Unique jobs from that cohort reaching the engagement-specific accepted completion milestone | Declared acquisition cohort plus full sales and delivery/acceptance lag | Channel invoice/export + CRM + project system + finance record | Acquisition owner with delivery/finance sign-off | Owner labor unless explicitly costed, refunds, canceled/incomplete work, immature retainers, unattributable jobs |
| Completion rate | Unique booked jobs reaching the engagement-specific accepted completion milestone | All unique booked jobs in the same mature cohort | Booked-job cohort plus declared delivery/acceptance window | Project system + acceptance record + CRM | Delivery owner | Canceled/refunded/incomplete jobs, internal work, immature retainers; report excluded states separately |
Failure-state review before the decision
- Source mismatch: vendor, applicant, spam, duplicate, or unattributable record.
- Fit mismatch: unsupported service, CMS, geography, time zone, budget rule, or launch timing.
- Sales loss: no-show, declined proposal, unsigned agreement, procurement failure, or unresolved conflict.
- Capacity loss: suitable work rejected because the design, development, content, or QA calendar was full.
- Delivery loss: cancellation, refund, scope creep, missing assets, failed acceptance, or incomplete work.
- Immaturity: project or retainer has not reached its declared acceptance window.
Do not blend projects, retainers, and white-label production. A marketing-site project might complete on accepted launch; maintenance may require an accepted service period; white-label work may finish when the partner accepts the agreed artifact. Separate cohorts preserve their different delivery hours, review chains, renewal paths, and margin inputs.
Frequently Asked Questions About Web Design Lead Generation
These answers cover the decisions that sit beside channel selection: getting clients without purchased records, choosing among acquisition models, defining qualification, testing long enough, and using honest proof. Each answer preserves the line between a response, a sales event, a booked engagement, and accepted web-design delivery.
How do web-design agencies generate leads?
Web-design agencies generate leads by defining one finishable engagement, identifying buyers they can actually reach, and matching a channel to the proof and sales path that engagement requires. Referrals, partnerships, content, outbound, events, directories, and paid media can all create enquiries. The agency should judge each source through qualification and accepted delivery.
How do I get web-design clients without buying leads?
Start with permissioned introductions from past collaborators, white-label partners, and clients who can accurately describe your work. Add owned material such as approved case studies, CMS migration checklists, or ecommerce teardowns. A response becomes a client only after qualification, discovery, proposal, agreement, and your written booking rule; publication or outreach alone proves nothing.
Should a web-design agency use referrals, content, outbound, Google Ads, or Facebook Ads?
Choose by engagement fit rather than a universal order. Referrals suit trust-heavy work, content suits questions buyers research, outbound needs a narrow and lawful prospect list, Google Ads can reach active searchers, and Meta ads can expose an offer across Meta placements. Test only where audience access, proof, intake coverage, capacity, and a stop rule are documented.
Should a web-design agency buy leads?
A web-design agency can test vendor-supplied enquiries only after auditing where the record came from, what the person consented to, whether it is exclusive, and how duplicates or refunds work. Apply the same qualification rule used for direct enquiries, preserve source attribution, and reconcile the mature cohort with completed delivery before renewing the vendor.
What counts as a qualified web-design enquiry?
A qualified web-design enquiry meets the written rule for the offered build: buyer authority, scope, contract floor, launch window, content readiness, CMS constraints, procurement needs, geography, sales coverage, and delivery capacity. Spam, applicants, vendors, unsupported platforms, conflicting accounts, and requests outside the declared service or time zone stay excluded and visible.
Does a form submission or booked call count as a client?
No. A form submission records a response, while a booked call records scheduled sales activity. Either can be spam, a vendor, a no-show, or an unsuitable project. A client record follows the agency's signed-agreement and booked-job rules. Completed work requires the separate acceptance milestone for that website, landing-page batch, retainer period, or white-label delivery.
How should projects, retainers, and white-label work be measured separately?
Create a separate cohort and completion rule for each model. A brochure site may complete at accepted launch or handoff, a maintenance retainer at an accepted service-period milestone, and white-label work at partner acceptance of the agreed artifact. Keep their qualification, sales lag, delivery hours, cancellations, refunds, margin inputs, and immature records separate.
How long should a web-design agency test an acquisition channel?
Set the duration from the engagement's buying, procurement, production, and acceptance lags. Declare start and end dates before launch, then wait until that cohort can mature under the written completion rule. A landing-page batch and an ecommerce replatform need different windows. Stop early for consent breaches, unsupported demand, exhausted capacity, or a preset cap.
What proof can an agency use when it has no publishable case study?
Use an artifact you own and can substantiate: a clearly labeled sample deliverable, an original teardown, a process diagram, an approved credential, or a founder opinion presented as opinion. Do not imply client results. Record authorship, permissions, scope, exclusions, reviewer, expiry date, and exact approved wording; mark performance evidence unavailable when it is unavailable.
Put the System Into Operation
Start with one engagement and one owner, then complete the economics card, alternatives map, funnel dictionary, proof ledger, qualification rule, and experiment sheet. Run no channel until its source, consent gate, cap, capacity dependency, and stop condition are recorded. Review the cohort only after the build's acceptance milestone can occur.
If your broader agency acquisition model is still undefined, use the digital marketing agency lead generation guide for the parent operating system. If owned expertise fits your selected engagement, the Content SEO module researches keywords, drafts, scores, queues, and publishes content. Your team still owns proof approval, qualification, sales, and delivery.
The competitive move is disciplined specificity. Sell the brochure site, ecommerce build, replatform, page batch, maintenance term, or white-label package you can finish. Then let completed-work evidence decide whether its acquisition channel earns another cohort.
Choose a web-design acquisition channel around work your team can finish. Bring the engagement, proof, capacity, and measurement questions to a practical review.
Sources & references
- U.S. Small Business Administration — market research and competitive analysis
- Federal Trade Commission — CAN-SPAM compliance guide
- Federal Trade Commission — Consumer Reviews and Testimonials Rule Q&A
- Google Analytics Help — recommended lead events
- Google Ads — official product overview
- Meta — official advertising overview
Blog SEO, Local SEO, and Social Media — one dashboard, no headaches.