Web design / development shops Operations Questions

The questions that recur in web shops share one shape: the highest-margin work is sold as an afterthought and the riskiest work is sold fixed. Fixed-price projects overrun by almost exactly 30 percent regardless of size, discovery predicts success yet gets discounted first, and hosting carries the margin while the proposal buries it. The answers below reprice the mix around where value actually sits.

• Does our tech stack serve the client or our hiring pipeline. Could the client tell?

  Check your stack choices against client needs: if you are building marketing sites in the framework your developers want on their resumes, the stack serves hiring. Clients cannot tell today. They discover it at handoff when nobody local can maintain it. Match stack to client maintainability.

  §1.1 ProcessTechnology decision, §13 principal-agent, §0.3 specifiedBy

• Why do redesign clients take their next redesign to a different agency. What happened at handoff?

  The relationship ended at launch: no maintenance contact, no performance reviews, no roadmap conversation. Three years of silence, then a fresh RFP. The next redesign is seeded the day this one launches. Own the post-launch lifecycle or forfeit the next cycle.

  §2.3 retention, §8.2 blueprint, §11.2

• Discovery predicts project success better than portfolios, yet we discount it first. What signal are we selling cheap?

  The certainty signal: discovery is where the client learns you understand their problem. The actual purchase decision happens there. Discounting it says "the thinking is free, the typing costs money," inverting your value. Price discovery as a product (it de-risks both sides) and conversion improves.

  §1.1 OrderWinner, §2.3 pricing, §6.1

• When the client's team cannot update their site six months post-launch, whose failure contractually and commercially?

  Contractually theirs (you delivered what was specced). Commercially yours (their frustration finds your name at every future RFP). Training and admin UX are NNVA only until the client calls them broken. Bake handoff training and a 90-day support window into the spec.

  D3 NNVA, §0.3 specifiedBy, §8.2 blueprint

• Fixed-price projects overrun by almost exactly 30% regardless of size. Which scope variable drives it?

  Content: client-provided copy, images, and approvals arrive late and wrong-sized in every project, independent of site size. The 30% constant is the content-and-feedback loop you never bound. Contract for content deadlines with schedule consequences, or price the 30% in as the content-risk premium.

  §9 critical chain/buffers, §11.2 client dependencies, §13

• When we lose maintenance clients, is it to cheaper providers or their new in-house hire, which should change pricing?

  Diagnose per exit: losses to in-house hires are structural (they outgrew the product). Respond with escalation-tier services. Losses to cheaper providers mean your maintenance tier is over-served (cut scope/price). Two different churns need two different responses. Exit-interview the difference.

  §2.1 churn segmentation, §1.1, §2.3

• Why quote hosting/maintenance as afterthoughts when they carry highest margin and lowest cost-to-serve?

  Because sales focuses on the visible project (the site) while the annuity (hosting, care plans) is where the business model actually lives. Recurring revenue is a different product with a different sale. Attach it at proposal as a designed tier, not a checkbox.

  §1.1 StructuralDecisions, §2.3, §8.2 subscription

• Our best developer generates our worst client satisfaction. Does staffing route them correctly?

  No: technical excellence and client-facing patience are different resources, and your routing treats them as one. Put the best dev on architecture and internal escalation, shield them from client calls, and staff client contact with communicators. Role-fit beats hierarchy.

  §4.4 job design/skill matrices, §6.3 SERVQUAL, D5

• Clients who approve designs fastest request the most revisions in development. What is fast approval telling us?

  That they did not evaluate: fast approval means the client deferred judgment until the design became real (clickable, in-browser). The revision flood is the evaluation happening late. Add a structured design-walkthrough gate that forces decisions before sign-off.

  §9 stage gates, §13 behavioral, §6.3 acceptance criteria

• Are accessibility/performance sold as risk mitigation or features, which framing survives the budget meeting?

  Risk mitigation: features get cut when budgets tighten. Lawsuit exposure and SEO/conversion penalties survive. Frame accessibility as legal-risk reduction and performance as revenue protection (conversion loss per second of load time), and both stop being optional line items.

  §2.3 framing, §11.4 risk, §6.1

How these answers work

Each answer names the operational mechanism the question is circling, then states the directive that follows from the ontology in Part One of the book. Bracketed citations point to the ontology sections and axioms that produced the answer.

Related industries

• SEO / digital agencies operations questions
• Staffing / recruiting agencies operations questions
• HR / payroll services operations questions
• Management consulting operations questions
• Business coaching operations questions

Keep reading

• All 100 industries and the full book
• Download the PDF
• Free diagnostic tool
• Methodology