Agency, contractor, or in-house: who should own your B2B website?

Separate the project from the operating responsibility

Start with two lists. The first contains bounded deliverables: a redesigned homepage, a product launch, a set of comparison pages. The second contains continuing responsibilities: publishing, form monitoring, technical maintenance, measurement, and deciding what happens next.

A proposal can cover the first list beautifully while leaving the second without an owner. Ask who will answer a request three months after launch, who can publish an urgent correction, and who maintains the system when the original builder is unavailable. These questions reveal whether you are purchasing an asset, ongoing capacity, or both.

Include your own time in the comparison. A lower invoice is not necessarily a lower total commitment if the marketing leader must write every ticket, reconcile conflicting feedback, and coordinate every handoff.

Use four questions to narrow the choice

1. How much work must happen at once? Identify deadlines that genuinely overlap. Three tasks in a backlog do not automatically require three people, but a simultaneous brand rollout, migration, and content program may.
2. How many specialties are essential? Distinguish capabilities needed every week from expertise needed for one review.
3. How much context must the owner retain? List the product knowledge, internal relationships, and recurring decisions that matter.
4. Who will manage the work? Name the person who sets priorities, approves scope, and resolves disagreements. Outside help still needs an internal decision maker.

Write answers in sentences rather than scoring everything with invented precision. The useful output is a visible constraint, such as needing two production tracks during a launch while having only one weekly review slot.

Choose an agency when the team structure earns its cost

An agency is worth considering when the assignment needs several specialties working concurrently, formal project management, or coverage beyond one person's availability. Verify that the proposed team actually supplies those things. The agency category alone guarantees none of them.

Ask who will do the work, how much access you have to those people, and which responsibilities are subcontracted. Request a sample delivery plan for your actual brief. Look for dependencies, review points, content responsibilities, and post-launch ownership.

Clarify whether your everyday requests will reach the original team or a separate support queue. A strong launch process and a suitable ongoing service are separate buying decisions.

Choose an independent partner when continuity matters

An independent partner can fit a focused backlog where design, implementation, and day-to-day judgment benefit from staying with one person. This arrangement is especially useful when your team has a marketing owner but needs someone to turn priorities into working pages.

Evaluate the person's actual range. Someone who builds excellent interfaces may still need help with positioning, complex integrations, or specialist accessibility evaluation. Defined boundaries are useful information, not a weakness.

Ask about reserved capacity, planned absences, documentation, and access ownership. Confirm what happens when two urgent requests arrive together. If the answer depends on an unlimited amount of one person's time, the operating model needs revision.

Choose an employee for a sustained internal role

An in-house hire deserves consideration when you have enough durable work to support the role and the person needs to participate deeply in planning across teams. Describe a normal month after the initial redesign. If you cannot, the immediate need may be a project rather than a permanent position.

Plan for management and specialist support. Hiring one web owner does not remove the need for prioritization, feedback, or occasional outside expertise. Write a realistic role around the responsibilities that dominate, instead of combining a brand designer, developer, analyst, content strategist, and marketing operations team into one job description.

Test the relationship with a bounded assignment

Hypothetical example: a software startup needs two product pages each month, quarterly launch support, and a functioning inquiry path. Its marketing director owns positioning, while an internal engineer can review unusual integrations. An independent partner could be a reasonable starting model. If the company adds a simultaneous rebrand and platform migration, a separately staffed project may be appropriate.

Use a paid pilot with a concrete deliverable, an agreed review process, and a definition of done. Evaluate whether the partner surfaces risks, translates feedback, and leaves maintainable work. Judge the working relationship as well as the final screen.

Before extending the engagement, turn what you learned into a clear retainer scope or a revised internal role. The decision should follow the work you can actually observe.