Skip to content
← Back to Blog

You Do Not Need a Fractional Web Developer. You Need a Fractional Web Department.

The job posting has been open five months because it is not a job, it is a department written as one line in an org chart. What a fractional web department covers and what the arithmetic says.

The job posting has been open for five months. Web Manager, or Digital Manager, or Manager of Web and Digital Communications. Read the responsibilities and it wants someone who can write front-end code, design a page, run the AMS integration, produce content, manage SEO, handle accessibility remediation, apply security patches, and sit in the strategy meeting. Salary band, low six figures if the board was generous.

Nobody has applied who can do all of it, because that is not a job. It is a department, written as one line in an org chart because that is the only shape the budget would take.

Where the numbers come from. The figures below come from the Bureau of Labor Statistics, the occupational handbook for the wage and the Employer Costs for Employee Compensation release for the benefits share. We have used them to do arithmetic rather than to make a point, and the arithmetic is in the post so you can check it.

Fractional Reached Your Finance Office Years Ago

Associations already buy this way. A fractional CFO is unremarkable in this sector, and so is a fractional general counsel or a fractional HR director. The logic was accepted a long time ago: the organization needs the function continuously, does not need a full-time person, and would rather have senior judgment part of the time than junior coverage all of the time.

Why web was left out. Web work never got that treatment, and the reason is a category error. Finance was always understood as a function, so it could be sized. Web was understood as a project, because the thing that hits the board agenda is a redesign with a start date and an end date. A function gets staffed. A project gets procured, finished, and forgotten, which is why the site is in the state it is in by year three.

And the term that did emerge undersells it. Search the term and you will find fractional web developer offered by a handful of small firms. It is the right idea with the wrong noun. A developer is one seat in the department, and it is usually not the seat an association is missing.

What Is Actually in a Web Department

When we take over the web function for an association, these are the seats that have to be covered. Not all full-time, but all covered by somebody with a name:

  • Front-end development. Templates, components, responsive behavior, and the accessibility work that lives in markup rather than in a policy document.
  • Back-end and integrations. The AMS connection, single sign-on, the payment processor, the event platform, the email system. This is where association sites are genuinely harder than commercial ones.
  • Design and user experience. Not a redesign. The ongoing work of making a new landing page look like it belongs to the same organization as the old ones.
  • Content operations. Publishing, migrating, pruning, redirecting, and keeping the navigation honest as the content grows.
  • Search and analytics. Structured data, index coverage, the reporting that tells you whether any of it worked.
  • Security and maintenance. Core and plugin updates, backups that have been restored at least once, certificate renewals, and the user list nobody has read in three years.
  • Direction. Somebody who decides what gets built, what gets refused, and what the platform is for. This is the seat associations most often leave empty, and the one that decides whether the other six compound.

Seven seats. The open job posting is trying to hire one person to sit in all of them, which is why it is still open.

The Arithmetic on Doing It In-House

The Bureau of Labor Statistics puts 2025 median pay for web developers and digital designers at 99,520 dollars a year. That is the median across all experience levels, so it describes a competent mid-career developer rather than a senior one or a beginner.

Then add what the salary does not include. Wages are not the cost. The BLS Employer Costs for Employee Compensation release for June 2026 puts total compensation for civilian workers at 49.46 dollars per hour worked, of which 33.85 is wages and salaries and 15.61 is benefits. Wages are therefore about 68 percent of what an employer actually spends. Apply that ratio to the median wage and one web developer costs an association in the neighborhood of 145,000 dollars a year before recruiting, equipment, software licenses, or the months the role sits vacant.

What that actually buys. One hundred forty-five thousand dollars buys one and a half of the seven seats. It does not buy design, it does not buy content operations, it does not buy search, and it does not buy direction. It also gives you a single point of failure, which is a problem we have written about separately and see constantly.

To be fair to the in-house option. This is not an argument that hiring is wrong. It is an argument that the budget line and the job description have never matched, and that the gap gets absorbed by whoever on staff is willing to learn WordPress at night.

What Outsourcing the Whole Function Looks Like

Fractional here does not mean a fraction of one person. It means a fraction of each of the seven seats, which is the only way a mid-size association gets all seven.

What changes operationally. In practice your organization stops holding a web headcount and starts holding a web capability. Requests go to one place. The roadmap is maintained by somebody whose job it is. Patches happen on a schedule rather than after an advisory. When the AMS vendor ships a breaking API change, the person who handles it already knows how your integration was built, because they built it.

What you keep. You keep the decisions. What the organization says, who it serves, what the site is for, and what gets built next are yours, and any firm that wants those is selling you a dependency rather than a service. You keep the content voice and the relationships with your members. What moves is execution and the calendar.

What has to be true for it to be safe. The failure mode of outsourcing anything is that the knowledge leaves with the contract. So documentation, credentials, the repository and the deployment pipeline stay in your name and in your accounts throughout. If you end the arrangement, another firm can pick it up from what exists. We would rather compete on the work than on how hard we are to leave.

When This Is the Wrong Answer

We turn this arrangement down more often than people expect, and these are the cases:

  • You have forty hours a week of work. If your website genuinely consumes a full week every week, with continuous building rather than continuous operating, hire. A large association with a publishing operation, an LMS and a busy events calendar can justify real headcount.
  • The job is mostly internal. Some organizations need the web person in the room for reasons that have nothing to do with the website: internal politics, cross-department negotiation, a board that wants a face. An outside firm does that badly.
  • You are not willing to delegate the calendar. If every decision still routes through a staff member who is not accountable for outcomes, you have added a supplier rather than removed a burden, and the cost goes up without the function improving.
  • Your site is genuinely simple. If the site is five pages, has no member portal and no integrations, this is more structure than the problem deserves. Pay somebody hourly when something breaks.

How the Handover Actually Runs

The transition is the part that worries people, and it is the part with the least drama in it.

  • First, the inventory. Everything that exists gets written down: hosting, domains, certificates, the CMS and its version, every plugin or module, every integration and who maintains it, and every account with its owner. Most organizations have never had this document.
  • Then, ownership. Access moves into accounts owned by your organization, not by us. If any of it currently sits in the personal login of a former employee, that gets fixed here, and it usually needs fixing.
  • Then, the backlog. The backlog that has accumulated gets triaged into what is urgent, what is maintenance, and what was never actually worth doing. The third category is usually larger than anyone expects.
  • Then, the rhythm. Requests, response times, the maintenance schedule, and the quarterly review. After that it is a function running rather than a project happening, which is the whole point.

Start With the Job Description You Could Not Fill

If there is an open posting, send it to us. We will map it against the seven seats and tell you which ones it was actually asking for, which ones it left out, and what the honest cost is of covering all of them, both as a hire and as an outsourced function. If the answer is that you should hire, we will say so, and we have said so before.

That comparison is the basis of our partnership plans, which exist because this is a function rather than a project and pricing it as a project is what produced the rebuild cycle in the first place. The plans are on our site with what each level covers. If you would rather start by finding out what you are currently running and what it is costing you across every vendor, that inventory is a fine first step on its own and it belongs to you either way.

83 Creative

We're a web development studio that works exclusively with trade associations, professional societies, and membership organizations.

← Previous Article Your Drupal Site Now Needs Two Upgrades a Year. Budget for Them Like a Subscription, Not a Project.