Do Your Clients a Favor and Require Paid Discovery

Do Your Clients a Favor and Require Paid Discovery 🔗 **Source:** [Do Your Clients a Favor and Require Paid Discovery](https://theadminbar.com/do-your-clients-a-favor-and-require-paid-discovery/) > [!note]+ Document Notes > ```markdown > > --- > tags: [client-services, discovery, project-scoping] > author: [Kyle Van Deusen] > source: [The Admin Bar] > reference: [https://theadminbar.com/do-your-clients-a-favor-and-require-paid-discovery/] > date created: 2025-10-01 00:00 > > --- > > # 🏷️ Title: Do Your Clients a Favor and Require Paid Discovery >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened. - The author argues for paid discovery before quoting projects. - Why it matters. - Proper scoping reduces risk, delays, and resentment on both sides. - Key stakeholders. - Agencies, freelancers, clients, and project managers. - Risks and tradeoffs. - Upfront pushback vs. fewer overruns and clearer deliverables. - Bottom line. - Charge for discovery to “sharpen the axe” and improve outcomes. ## 📖 Main Content - Explain the core arguments in plain language. - Accurate quotes require a defined scope and shared understanding. - Discovery builds this foundation systematically. - Free guessing creates scope creep, delays, and unmet goals. - Add sourced context and define terms. - Discovery clarifies goals, KPIs, audience, tech, compliance, and UX. - It aligns budget, timeline, and risk planning before build. - Note uncertainties or contested claims. - Some clients resist upfront fees; conversion impact may vary by niche. ### 🗒️ Notes - Clients ask for price first, but scope must come first. - Scope needs goals, KPIs, personas, and competitive analysis. - Include compliance, data protection, and accessibility considerations. - Map integrations, tech stack, CMS, and third-party services. - Plan content inventory, creation roles, and messaging guidelines. - Define IA, navigation, and user flows. - Set UX/UI, wireframes, performance targets, and SEO strategy. - Specify QA plans, feedback cycles, and deployment approach. - Add training, maintenance, and post-launch analytics. - Align timeline, milestones, budget, and comms plan. - Assess risks and contingency strategies early. - Discovery effort can span hours to weeks. - Free pre-sales labor filters out misaligned clients. - Skipping discovery leads to: - Scope creep and cost overruns. - Delays and endless revisions. - Solutions that miss business goals. - Framing discovery as “foundation” resonates with serious clients. - Lincoln quote supports preparation value. - The Admin Bar context indicates practitioner perspective. ## 📚 References - [Do Your Clients a Favor and Require Paid Discovery](https://theadminbar.com/do-your-clients-a-favor-and-require-paid-discovery/) - [W3C Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/) - [UK NCSC: Privacy and Data Protection](https://www.ncsc.gov.uk/collection/data-and-privacy) - [Google: Core Web Vitals](https://web.dev/vitals/) ## 🗣️ Paraphrase - Paragraph A paraphrase. - You cannot price accurately without a clear scope built through discovery. - Paragraph B paraphrase. - Skipping discovery triggers overruns, delays, and unmet objectives. ## 📰 Newsletter - Paid discovery isn’t an upsell; it’s your project’s base layer. - Set goals, KPIs, personas, and tech assumptions early. - Reduce scope creep and prevent hostage-fee moments mid-project. - Align teams on content roles, SEO, performance, and QA plans. - Resource picks: - Read: preparation framing by the author. - Check WCAG 2.2 for accessibility scope. - Review Core Web Vitals targets for performance budgets. - Community note: - As Vice President of the Board for The WPCC, I support sustainable, transparent practices that respect contributor time. ## ✅ Action Items - DevRel - Publish a discovery template and workshop recording. - Create case studies showing reduced overruns. - Developer advocacy: plans, talks, demos, and measurable outcomes. - Offer a “scope-first” demo with KPI dashboards. - Track adoption and NPS changes quarter-over-quarter. - Education: workshops, curricula, office hours, mentorship programs. - Run a “Discovery for WordPress projects” series with artifacts. - Developer experience: docs, SDKs, examples, templates, quickstarts. - Provide issue templates for scope, risks, and acceptance criteria. - Developer marketing: campaigns, content, funnels, and attribution. - Lead magnet: discovery checklist with email capture. - Community management: moderation, code of conduct ops, surveys. - Host AMAs on pricing discovery ethically. - Internal/external/cross-project: align goals, SLAs, and feedback loops. - Add discovery milestones to SLAs and SOW templates. - OSPO - Policy & Governance: contribution policies, decision rights, charters. - Publish scoping charters for internal OSS projects. - License Compliance: policies, scanning, review, and training cadence. - Include compliance mapping in discovery artifacts. - Security Management: vuln intake, embargo policy, signing, attestations. - Add threat modeling to discovery for critical sites. - Software Inventory: SBOM strategy, ownership, freshness SLOs. - Require SBOM generation in build plans. - Developer Support: training, tooling, legal guardrails, consultation hours. - Office hours for scoping complex integrations. - Community Engagement: upstream funding, MoUs, operator agreements. - Budget discovery time for upstream collaboration. - Strategic Alignment: KPIs, OKRs, executive reporting, initiative roadmaps. - Tie discovery metrics to OKRs on delivery predictability. - Community - Maintainers: roadmap clinics, governance templates, release hygiene. - Use discovery to define release acceptance criteria. - Contributors: onboarding paths, “first issue” rotations, pairing sessions. - Add scoped starter issues with clear outcomes. - Sponsors: transparent budgets, milestones, deliverables, impact reports. - Show discovery outputs in reports for accountability. - Ecosystem: cross-project incident drills and coordinated disclosures. - Scope comms and roles for incident playbooks. - WordPress - Core: priorities, issue triage, performance budgets, release criteria. - Enforce scope statements on feature proposals. - Core Performance: profiling plans, metrics dashboards, perf bounties. - Define thresholds during discovery. - Core AI: responsible AI guardrails, evaluation sets, pilot projects. - Specify evaluation data and guardrails upfront. - Core Program: coordination rituals, cross-team dependencies, retrospectives. - Add dependency mapping to discovery docs. - Mobile: app backlog, telemetry review, offline UX improvements. - Scope telemetry and consent during discovery. - Playground: browser labs, reproducible bugs, education modules. - Provide discovery sandboxes for prototyping. - Community: meetup kits, WordCamp playbooks, speaker mentorship. - Include discovery workshops in meetup kits. - Training: lesson plans, learning paths, certification pilots. - Cert module on scoping and acceptance criteria. - Marketing: campaigns, narratives, social editorial calendars. - Align messaging from discovery personas and goals. - Support: response SLAs, knowledge base gaps, escalation paths. - Scope escalation flows and SLAs. - Design: UX audits, design tokens, research backlogs. - Capture tokens and heuristics in discovery. - Documentation: DevHub/HelpHub gaps, examples-first patterns, style guide. - Add discovery-derived examples to docs. - Photos: content drives, moderation guidelines, taxonomy hygiene. - Inventory assets and rights in discovery. - TV: submission guides, caption quality, content indexing. - Plan captions and transcripts at scope time. - Polyglots: translation sprints, glossary alignment, locale coverage. - Define target locales and glossary updates early. - Accessibility: WCAG reviews, tooling, issues heatmap, audits cadence. - Commit to WCAG 2.2 AA in the SOW. - Meta: .org roadmap, API reliability, contributor tools. - Scope API SLAs and monitoring. - CLI: command coverage, UX docs, plugin scaffolds, smoke tests. - Define CLI acceptance criteria upfront. - Hosting: cross-host checklists, defaults, telemetry for reliability. - Align host constraints and observability in discovery. - Tide: scoring transparency, false-positive review loops, plugin outreach. - Plan feedback loops and fixes cadence. - Openverse: ingestion pipelines, moderation policy, education tie-ins. - Scope content rights and provenance policies. - Themes: review throughput, lints, mentoring, test matrices. - Document test matrices during discovery. - Plugins: review throughput, security liaisons, provenance checks. - Require provenance and supply chain notes. - The WPCC - Programs: fellowship tracks, microgrants, maintainer stipends. - Fund discovery for community-critical initiatives. - Projects: governance clinics, documentation sprints, release teams. - Provide discovery templates for community projects. - Funding experiments: matched grants, milestone payouts, transparent ledgers. - Tie payouts to discovery deliverables. - FAIR - Technical independence: local metadata, provenance, and signature checks. - Include verification steps in discovery checklists. - Policies and covenants: funding transparency, sunset clauses, anti-capture. - Scope governance artifacts with clear decision rights. - Productized governance artifacts: charters, operator agreements, scorecards. - Publish reusable discovery-to-charter pathways. ## 🧪 Hypotheses - Paid discovery reduces scope changes by at least 30%. - Projects with discovery hit timelines 20% more often. - Client satisfaction improves when KPIs are agreed pre-build. - Profit margins increase when discovery is billed and enforced. - Accessibility compliance improves when scoped from day one. ### 📊 Methodology - Retrospective cohort of projects with and without discovery. - Track scope changes, timeline adherence, margin, and NPS. - Use regression to control for size, sector, and team. ### ❓ Questions - What discovery fee models best balance conversion and rigor? - Which artifacts most reduce rework? - How does discovery affect long-term client retention? ### 🔮 Future Research - Compare vertical-specific discovery checklists. - Test AI-assisted discovery against manual baselines. ### 💡 Implications - Practice: Standardize discovery artifacts and approvals. - Policy: Require discovery in SOWs and procurement. - Security: Integrate threat modeling and SBOM early. - Education: Teach scoping in contributor onboarding. - Funding: Budget discovery as a protected line item. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ≈ 8–9. - Visual learners - Present: Lists and structure. - Improve: Flowcharts of discovery stages. - Aural learners - Present: None indicated. - Improve: 3-minute audio overview. - Verbal learners - Present: Clear definitions and examples. - Improve: Glossary of discovery terms. - Kinesthetic learners - Present: Actionable checklist ideas. - Improve: Hands-on scoping labs. - Logical learners - Present: Stepwise scope categories. - Improve: Decision trees and RACIs. - Social learners - Present: Client–agency alignment focus. - Improve: Role-play scripts and peer review. - Solitary learners - Present: Structured notes. - Improve: Self-assessment worksheets. - Naturalistic learners - Present: Preparation analogy. - Improve: Lifecycle and sustainability tie-ins. ### 📊 Accessibility Assessment - Screen reader semantics - Present: N/A for article; general guidance listed. - Improve: Ensure headings and alt text in project outputs. - Keyboard navigation - Present: Plan logical order and focus states. - Improve: Prevent traps and ensure reachability. - Contrast and readability - Present: Set 4.5:1 targets. - Improve: Validate line-height and spacing. - Text resizing and reflow - Present: Responsive targets at 200%. - Improve: Respect reduced-motion preferences. - Media and captions - Present: Plan transcripts and captions. - Improve: Add audio descriptions and downloads. - Forms and interactions - Present: Labels and error handling. - Improve: Inline validation and forgiving inputs. - Standards reference - Map to WCAG 2.2 AA criteria. ### 🌍 DEIB Assessment - Cultural breadth - Present: Generalizable process. - Improve: Multilingual and regional examples. - Inclusive language - Present: Mostly neutral language. - Improve: Add plain-language summaries. - Neurodiversity support - Present: Chunked lists. - Improve: Predictable icon+text labels. - Representation - Present: Roles implied, not diverse examples. - Improve: Show varied users and contexts. - Psychological safety - Present: Respectful framing. - Improve: Clear escalation and feedback norms. ### ✅ Logical Validity - Strong reasoning - Inductive: Past overruns suggest discovery prevents repeats. Clear causal framing. - Causal: Defined scope reduces change requests. Aligns with industry practice. - Fallacies - Potential hasty generalization: “I’ve yet to have a client…” Consider broader data. - Fix by adding benchmarks or case studies. - Tone of voice - Direct, practitioner-oriented, and cautionary. ### 🛡️ DARVO Analysis - Deny - No denial of client concerns; acknowledges pushback. - Attack - None; calls risky choices “arrogant or ignorant,” which may feel sharp. - Reverse victim/offender - None; frames mutual risk, not victimhood. ## 🎯 Conclusion - Restate the bottom line. - Paid discovery creates clarity, reduces risk, and improves outcomes. - Note practical next steps for readers. - Productize discovery, publish artifacts, and set acceptance criteria aligned to KPIs. ```