Scroll Top

Web Design, Development and Management

Updated September 2026 · Written and maintained by the Progression Agency strategy team

A website engagement covers three separate jobs — designing it, building it, and keeping it working afterwards. Buyers concentrate on the first, which carries the smallest share of lifetime cost, and neglect the third, which carries the largest. This covers what management actually involves, how to scope a project so it does not run late, what belongs in the contract, and why improving usually beats redesigning.

The short answerTest your contact form yourself once a month. A form that silently stopped delivering, or conversion tracking that stopped recording, is the most expensive fault a business website can develop — entirely invisible, and capable of running for months. And check right now who owns your domain: registrations held by a former developer or employee are a recurring and wholly avoidable emergency.

Progression Agency is based in New York City and works with clients across the United States. Costs, contract terms and technical requirements vary widely by project; the material here describes how these engagements generally work rather than prescribing terms for any specific one. Nothing here is legal advice.

Website engagements in short
A silently broken contact form is the most expensive fault a business website can develop, and testing it takes one minute a month.

What does a website engagement actually cover?

Three different jobs that get sold as one: designing it, building it, and keeping it working afterwards — and the third is where most of the lifetime cost sits.

Separating them is the most useful thing a buyer can do, because they have different skills, different costs and different failure modes.

Where attention goes versus where cost goes
The gap between the two lines on the right-hand category is the single most useful thing on this page.

Why does separating design, development and management matter?

Because a proposal that covers all three at one price hides which part you are actually paying for, and because the ongoing part is what gets neglected.

Most website disappointments trace to the third job, not the first: a site that was fine at launch and has not been maintained since.

Design, development and management compared
ConsiderationDesignDevelopmentManagement
What it producesHow it looks and worksThe working siteA site that stays working
When it happensBefore buildDuring buildContinuously afterwards
Main riskCommittee decisionsScope driftNeglect
Cost shapeProjectProjectRecurring
SkillsVisual and UXEngineeringOperations and content
What buyers focus onMostSomeAlmost none
Where lifetime cost sitsLeastMiddleMost
Failure looks likeBland or off-brandLate and over budgetSlow, broken, out of date

The two bottom rows are the argument. Buyers concentrate attention on the part with the smallest share of lifetime cost and least attention on the part with the largest.

What does website management actually involve?

Updates and security patching, backups that are tested, uptime monitoring, performance, content changes, and fixing things when they break.

None of it is glamorous and all of it is the difference between a site that is an asset after three years and one that is a liability.

Patch and update — Management. Unpatched sites get compromised..
Test a restore — Management. An untested backup is a belief..
Monitor uptime — Management. Learn it before a customer does..
Watch performance — Management. Sites slow down over time..
Test the forms — Management. The most expensive silent fault..
Prune access — Management. Remove people who left..

Software and plugin updates

Unpatched sites are the most commonly compromised, and the fix is routine maintenance rather than anything sophisticated.

Backups that have been restored at least once

An untested backup is a belief rather than a backup.

Uptime and error monitoring

So you learn from your own systems rather than from a customer.

Performance

Sites get slower over time as content, images and scripts accumulate.

Content changes

Small, frequent edits. The commonest reason a site goes stale is that changing it is awkward.

Forms and tracking checked periodically

A form that silently stopped sending is one of the most expensive faults there is, and it is invisible.

Security and access hygiene

Removing accounts of people who left, and keeping administrative access minimal.

What is the most expensive silent failure?

A contact form that stopped delivering, or conversion tracking that stopped recording — both invisible, both capable of running for months.

Testing the form yourself once a month costs nothing and catches the single most damaging fault a business website can develop.

How should you scope a website project?

By deciding what the site must achieve, how many templates it genuinely needs, who supplies the content, and what happens after launch — before discussing design.

Content is the item that delays most website projects, and it is almost always the client’s to supply.

Scoping a website project properly
Step three is where most projects lose their timeline, and it is almost always the client’s item rather than the developer’s.

Define the job the site does

Generating enquiries, supporting sales, selling directly or informing. These lead to different sites.

Count the templates, not the pages

Cost tracks templates. Two hundred pages using six templates is a smaller job than thirty pages using twenty.

Decide who writes the content

The commonest cause of delay, and it is usually the client.

Agree what happens after launch

Who maintains it, at what cost, with what response time.

Decide what migrates and what does not

Old content, URLs and redirects. Getting redirects wrong loses search visibility that took years to build.

Agree how success is measured

Enquiries, not compliments.

Name one decision-maker

Website projects are where design-by-committee does the most damage.

What goes wrong in website projects?

Content arriving late, scope growing quietly, too many decision-makers, and no plan for redirects or maintenance.

Three of those four are the client’s to prevent, which is worth knowing before blaming a developer for a late project.

Why website projects run late, and whose problem it is
CauseWhosePrevention
Content not readyClientAssign it, with dates, at the start
Scope grew during buildBothWritten change process
Too many decision-makersClientName one
Approval cycles slowClientAgree turnaround up front
Requirements unclearBothWrite them down before designing
Third-party integrationsBothIdentify and test early
No redirect planDeveloperMap old URLs before launch
No post-launch planBothAgree it before the project ends

The redirect row is the one with lasting consequences: a site launched without redirects can lose search visibility that took years to accumulate, and recovering it is slower than building it was.

Should you redesign or improve what you have?

Improve, in most cases. Full redesigns are expensive, risky and frequently address a problem that was never the design.

A site that does not convert usually has a clarity or offer problem. Rebuilding it in a new visual style preserves that problem at considerable cost.

Improve — Fix clarity first. Usually the real problem..
Improve — Speed on mobile. Cheaper than a rebuild..
Improve — Better pages, not more. Depth beats volume..
Redesign — Only with a real reason. Not because it feels dated..
Redesign — Plan redirects first. Protects search visibility..
Redesign — Keep what converts. Do not discard evidence..

How much does a website cost?

It varies with the number of templates, how much content is being produced, how many integrations exist, and whether ongoing management is included.

The variable buyers underestimate is content, and the one they forget entirely is the recurring cost of keeping the site current after launch.

What actually drives website cost
Relative weighting, not prices. The final bar recurs every year while the others happen once.

What should be in a website contract?

Scope in detail, who supplies content and by when, a change process, hosting and ownership terms, and what happens after launch.

Ownership specifically: the domain, the hosting account, the code and the content should all be yours or transferable, and that is easiest to establish at the start.

What to settle before signing
ItemWhyCost of getting it wrong
Who owns the domainIt is the business’s identitySevere; hard to recover
Who controls hostingAccess during a disputeHigh
Who owns the codeReuse and portabilityMedium to high
Who owns the contentReuse elsewhereMedium
Content responsibility and datesThe main cause of delayTimeline
Change processScope creepBudget
Post-launch support termsNeglect otherwiseCompounds over years
Redirect and migration planSearch visibilitySevere, and slow to recover

The first row is worth checking on any existing site right now. Domains registered by a former developer or employee are a recurring and entirely avoidable emergency.

How do you judge whether a website is working?

Enquiries, conversion rate by page, speed on a phone, and whether the pages that receive traffic are the ones you intended.

Compliments about the design are not evidence. A site that people like and that produces nothing is a well-received failure.

What platform should a business website be built on?

Whatever the people who will maintain it can actually use — which is a different question from which platform is technically best.

A powerful platform nobody in the business can update produces a site frozen at launch, which is the outcome the platform choice was supposed to prevent.

Choosing a platform for who will actually maintain it
If the maintainer isPrioritizeAvoid
A non-technical ownerSimple editing, few moving partsCustom builds needing a developer
An in-house marketerFlexible page buildingRigid templates
An internal developerWhatever they know wellAn unfamiliar stack
An external agency, ongoingTheir standard stackOne-off bespoke choices
Nobody, realisticallyManaged hosting and few pluginsAnything needing patching attention
A team that changes oftenDocumentation and common skillsNiche technology
An ecommerce operatorPurpose-built commerceGeneral CMS plus plugins
Somebody with strict compliance needsAuditability and access controlLoose plugin ecosystems

The row that reads ‘nobody, realistically’ is the honest answer for a lot of small businesses, and it should drive the decision rather than being treated as a temporary state.

How often should a website actually be replaced?

Far less often than it is. Most sites need continuous small improvement and occasional structural work, not a replacement every three years.

The replacement cycle is largely a habit of the industry that sells replacements, and each one discards accumulated search visibility and conversion evidence.

Website that looks fine and does nothing?

We work with clients across the United States on websites judged by enquiries rather than compliments — and we will usually recommend fixing what you have before rebuilding it, because the problem is rarely the design.

Talk to Progression Agency

Video: web and marketing practice

A general library on marketing practice. The website material is written out in full above.

Websites and design

Frequently asked questions

What do website design and development agencies include that designers do not?
Engineering, testing and deployment. Website design and development agencies carry the build as well as the visuals, which matters because a design handed to a separate developer loses fidelity at exactly the points nobody documented. Single-supplier delivery removes that gap.
What do web design and management services include after launch?
Hosting, updates, security, backups and content changes. Web design and management services differ from a build-only engagement in that the relationship continues, which matters because an unmaintained site accumulates plugin and security debt within months.
What does chapel hill web design typically cost?
Commonly five to thirty thousand for a small business site. Chapel hill web design pricing sits close to the Triangle average, and the range is driven by page count and custom functionality rather than location — a template build and a bespoke one differ by an order of magnitude.
How do I choose web design chapel hill firms from Durham or Raleigh ones?
Only by whether in-person work matters. Web design chapel hill studios serve the same regional market as Durham and Raleigh firms, and the build is remote work. Proximity helps for photography, stakeholder workshops and university-affiliated projects with on-campus meetings.
Is web development durham distinct from the wider Triangle market?
Slightly, in client mix. Web development durham skews toward startups, biotech and non-profits because of who is headquartered there, so local developers are practiced at those requirements. The technical work is not geographically distinct.
What does website design chapel hill include as standard?
Discovery, design, build, content migration and launch. Website design chapel hill quotes vary most in whether content writing and migration are included, and migration is the item most often assumed rather than scoped — it is usually the longest unglamorous task in the project.
Which web development companies in north carolina serve statewide clients?
Most of them, since delivery is remote. Web development companies in north carolina based in the Triangle or Charlotte routinely serve Wilmington, Asheville and the coast without difficulty; only on-site discovery and photography are constrained by geography.
How do you choose a web dev agency?
On what happens after launch as much as on the build. A web dev agency that quotes design and development without a maintenance position is quoting for the smaller share of the lifetime cost, and the neglected part is where most sites decay.
What does a website engagement actually cover?
Three separate jobs: designing it, building it, and keeping it working afterwards. The third carries most of the lifetime cost and gets the least attention.
Why separate the three?
Because a single price hides what you are paying for, and because the ongoing part is the one that gets neglected.
What does website management involve?
Software updates and patching, tested backups, uptime and error monitoring, performance, content changes, form and tracking checks, and access hygiene.
Is an untested backup a backup?
No. Until a restore has actually been performed once, a backup is a belief rather than a recovery plan.
What is the most expensive silent failure?
A contact form that stopped delivering, or conversion tracking that stopped recording. Both are invisible and can run for months.
How do I catch that?
Submit the form yourself once a month and confirm it arrives where it should. It costs nothing and catches the most damaging fault a business site develops.
How should I scope a website project?
Define the job the site does, count the templates it needs, decide who writes the content, plan redirects, identify integrations, and agree what happens after launch.
Why count templates rather than pages?
Because cost tracks templates. Two hundred pages using six templates is a smaller job than thirty pages using twenty.
What delays website projects most?
Content arriving late, and it is almost always the client’s item rather than the developer’s.
Whose fault are late website projects usually?
Three of the four common causes — content, too many decision-makers, and slow approvals — sit with the client rather than the developer.
Why does a redirect plan matter so much?
Because a site launched without one can lose search visibility that took years to accumulate, and recovering it is slower than building it was.
Should I redesign or improve what I have?
Improve, in most cases. A site that does not convert usually has a clarity or offer problem, and rebuilding it in a new style preserves that problem at considerable cost.
When is a full redesign justified?
When the underlying platform genuinely cannot do what the business needs, or the structure prevents the site from being usable — not because it feels dated.
What drives website cost?
Number of distinct templates, content production, integrations and custom functionality, depth of design exploration, migration work, and ongoing management.
Which cost do buyers underestimate?
Content production. Which cost do they forget entirely: the recurring cost of keeping the site current after launch.
What should be in the contract?
Detailed scope, who supplies content and by when, a change process, hosting and ownership terms, and what happens after launch.
Who should own the domain?
The business, always. Domains registered by a former developer or employee are a recurring and wholly avoidable emergency.
Who should own the code and content?
They should be yours or transferable, and that is far easier to establish at the start than to negotiate at the end of a relationship.
Why does a change process matter?
Because scope grows quietly during a build, and without an agreed way to price and approve changes it becomes a dispute rather than a decision.
How many decision-makers should a project have?
One. Website projects are where design-by-committee does the most damage, and averaging everybody’s preferences produces work nobody wanted.
Should the developer handle third-party integrations?
Whoever handles them, identify and test them early. They are a common source of late-stage surprises.
What should happen at launch?
Redirects in place and verified, forms tested, tracking confirmed, and a named person responsible for the site the following week.
How do I judge whether the site is working?
Enquiries, conversion rate by page, speed on a phone, and whether the pages receiving traffic are the ones you intended.
Are compliments about the design evidence?
No. A site that people like and that produces nothing is a well-received failure.
How often should content change?
Small changes frequently. The commonest reason a site goes stale is that changing it is awkward, which is a setup problem rather than a discipline problem.
What about security?
Routine patching, minimal administrative access, and removing accounts of people who have left. Most compromises exploit neglect rather than sophistication.
Should management be a retainer?
It is a recurring cost either way. A retainer makes it explicit; the alternative is paying for it in emergencies at higher rates.
What is the single best thing to check today?
Who owns your domain, and whether your contact form actually delivers. Both take minutes and both are expensive to discover late.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. Google Ads: location targeting settings
  24. Google Ads: about negative keywords
  25. Google Ads: about Quality Score
  26. Google Ads: importing offline conversions
  27. Google Ads: about Smart Bidding
  28. Google Ads: about Performance Max
  29. Google Local Services Ads: eligibility and screening
  30. Google Ads: keyword match types
  31. Google Analytics 4: about conversions
  32. Google Analytics 4: attribution models
  33. US Census Bureau QuickFacts: New Jersey
  34. US Census Bureau: American Community Survey
  35. US Census: Statistics of US Businesses
  36. Bureau of Labor Statistics: New Jersey data
  37. BLS: Occupational Employment and Wage Statistics
  38. NJ Department of Labor: labor market information
  39. New Jersey Business Action Center
  40. US Small Business Administration: New Jersey district
  41. USA.gov: business resources
  42. web.dev: Core Web Vitals explained
  43. web.dev: Largest Contentful Paint
  44. web.dev: Cumulative Layout Shift
  45. web.dev: Interaction to Next Paint
  46. Google PageSpeed Insights
  47. Google Rich Results Test
  48. Google Search Console
  49. W3C Markup Validation Service
  50. Schema.org: LocalBusiness type
  51. Schema.org: Service type
  52. Schema.org: FAQPage type
  53. Schema.org: HowTo type
  54. W3C: WCAG 2.2 quick reference
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.