In House vs Agency: Who Should Make Your Landing Pages?

A firm can spend weeks comparing landing page proposals, negotiate a build fee, approve the design and launch. Then compliance requests a disclosure change. Marketing wants a different headline. An integration stops passing submissions. A new campaign needs a separate page for a different audience.

At which point the firm discovers that launching was the easy part. Someone has to maintain it, change it, understand how it works, and keep it aligned with the firm's marketing and compliance processes.

Which is where this decision gets more complicated than comparing proposals. A landing page is not a finished deliverable the way a video is. It is a working asset somebody owns for as long as it stays live.

That runs across the category. An adviser updates disclosures or adjusts a campaign for a particular investor audience. An insurer revises product language. A lender changes eligibility information. A bank introduces a new account offer. A fintech updates its onboarding flow as the product evolves.

Each creates an ongoing ownership requirement: who can make changes, who understands the systems, who verifies results, and who remains accountable once the original builder has gone.

This article is published by an agency, Clients Blackbox, so the agency model is part of the discussion. Hiring one is not automatically right. Internal teams hold real advantages in speed, access and institutional knowledge, and the answer depends on what the firm needs to change, what it can maintain, and how much responsibility it wants to keep.

Should You Build In House or Hire an Agency?

Choose on who can own the page throughout its working life, not who can produce the first version.

Start from the work that follows launch. A page may sit stable for months or change constantly as campaigns evolve, compliance produces edits and performance data reveals problems. Whoever handles those changes matters as much as whoever built it.

An internal team is well placed for that, already understanding the products, audiences, terminology, approval process and marketing systems, and developing direct familiarity with the page rather than relying on someone external to explain it.

An agency is better equipped to build something technically complex, diagnose conversion problems, connect multiple systems, or apply lessons from similar projects. Valuable where the internal team lacks the skills or the capacity.

Neither settles it. An agency can build an excellent page and create a frustrating relationship where every small change becomes a request. An internal marketer can edit quickly and still ship broken tracking, inaccessible forms and a conversion path nobody tested.

So compare complete operating arrangements. Who defines requirements? Who builds? Who has publishing access? Who reviews changes? Who monitors integrations? Who investigates a sudden drop in submissions? Who documents the setup? Who takes over if the owner leaves?

Write the answers down before choosing a model. If they depend on one person's memory, an informal agreement, or an agency's willingness to help when free, the arrangement needs more thought.

This also differs from video, which is produced, approved and delivered as a project. The constraint there is access to a person on camera, covered in In House vs Agency: Who Should Make Your Video Ads. Here it is ongoing control of the page and its systems.

Build Versus Maintain

The build is one part of the cost. The rest is the work to run it, the external support it needs, and the consequences of delay.

An in-house build involves strategy, copywriting, design, development, compliance coordination, integration, analytics, accessibility checks, testing and publishing. Some of those skills exist in the firm. Others need developing, contracting, or borrowing from people with competing responsibilities.

Then the ongoing work. Someone reviews requested changes, coordinates approvals, publishes updates, verifies forms, checks analytics, maintains integrations and confirms the live page still reflects the approved offer. Even a page nobody edits depends on software, tracking scripts, consent settings and third-party systems that change on their own schedule.

An agency arrangement has its own shape. The project may cover planning, design, development, technical setup and launch. Ongoing work may sit in a service agreement or be handled separately, with extra cost when a request falls outside scope or needs new integration work.

The firm contributes time either way, explaining the business, supplying information, reviewing copy, coordinating compliance and testing the result. Outsourcing production does not remove internal participation.

So identify the work each model requires and who performs it, including briefing, reviewing, troubleshooting, documenting and coordinating, plus external technical help when the internal team hits its limit.

Then weigh the cost of waiting. If a material change is needed and the responsible person is unavailable, the delay affects a campaign, an offer or a review. Not every delay carries a measurable cost, and the possibility belongs in the decision.

No universal rule says either model costs less over a page's life. For the variables in the initial project, see How Much Do Landing Pages Cost for Financial Services Firms? The relevant point here is that a build quote does not describe the ownership cost.

Is It Cheaper to Build Pages In House?

No reliable answer exists without examining the skills, workload, technical requirements and maintenance responsibilities involved.

In-house makes sense where the firm already has the people and systems. A marketing team with design and development capability reuses its process across campaigns, its employees understand the business, and the firm keeps direct access to working files, publishing and decision-makers. The benefit comes from existing capability and access, not from assuming internal labor is free.

The calculation changes when the firm needs skills it lacks. A page builder makes layout changes easy while the same team struggles with conditional forms, CRM routing, event tracking, accessibility requirements, consent management, or a problem appearing only on certain devices.

Those gaps create work. Employees need training, specialist support, or time away from other responsibilities. And the page often lands with one employee who becomes its default owner without the time or expertise to maintain it.

An agency introduces different variables: scope of service, revision arrangements, communication and separately billed work, in exchange for several complementary skills the firm does not maintain internally.

It does not remove internal work though. Where every edit needs detailed briefing and several approval rounds, the firm still spends the time coordinating, and where the contract does not address maintenance, it arranges a new engagement after launch.

So compare operating models rather than an internal labor estimate against one proposal. A firm with a capable marketing operations team, an established platform and a documented compliance workflow has a basis for internal ownership. A firm with strong campaign strategy and no development or analytics support needs outside help for the build and the complex work even while keeping routine edits.

The better question: what capabilities must the firm maintain, what work can it perform consistently, and what external support will it still need?

The Change-Request Bottleneck

A page can be technically sound and difficult to operate, which happens when routine changes pass through a vendor controlling the page or its publishing environment.

The familiar sequence: compliance identifies wording that has to change, marketing prepares the approved replacement and sends a request, the vendor asks for clarification, schedules the work, makes the edit, sends a preview, the firm reviews, requests a correction, and waits for publication.

Each step is reasonable alone. Together they turn a small edit into a coordination exercise.

It gets worse at scale. A product update affects several pages. Different segments use different offers or disclosures. Marketing needs an outdated message paused while a replacement is reviewed. A technical issue needs immediate investigation while the agency is occupied elsewhere.

Distinguish a vendor bottleneck from a necessary control though. Firms should not bypass required compliance review to publish faster. The aim is removing avoidable production delay while preserving the approvals, testing and recordkeeping the firm requires.

So before outsourcing, ask how changes get submitted, who can make them, how urgent requests are handled, and whether the firm can publish approved changes itself. Establish which edits are routine and which need technical support, how work gets prioritized, and what happens when the usual contact is away.

Ask too whether the vendor's process creates unnecessary dependency. If changing a button label requires a developer, find out whether the page could be structured so authorized marketers can do it safely. If the vendor has a good reason for keeping control, understand it before signing.

And examine the opposite risk internally. Giving everyone editing access produces inconsistent layouts, unapproved copy, accidental tracking changes and publishing errors. Fast access only helps alongside clear permissions, documented standards and a review process.

What In-House Teams Genuinely Do Better

Three things an external partner cannot fully reproduce.

Proximity to the business. Employees hear about product changes, new priorities, sales objections and internal decisions as they happen, without reconstructing the firm's context before every edit.

Direct system access. With the right permissions and knowledge, the team inspects the page, checks form behavior, reviews analytics and makes approved changes without waiting on an outside schedule. Useful where several channels share the same website, CRM, analytics or consent infrastructure.

Institutional memory. An internal owner keeps why a headline was chosen, which claims were rejected, what compliance asked to change, how leads route and which integrations the page depends on.

Internal teams also coordinate across departments more easily, speaking directly with product, sales, operations, legal and compliance. An agency participates in those conversations as an outside party and will not be in all of them.

Those advantages matter most where pages change often or connect to sensitive workflows: a lending page depending on eligibility details, an insurance page needing product and legal coordination, a fintech page tied to a product flow that keeps moving.

There are limits. Employees need time, and access does not guarantee proficiency, since a marketer who can edit copy may not be able to diagnose a tracking discrepancy or evaluate keyboard navigation. Institutional memory also disappears when documentation is weak.

So in-house works when the firm assigns real responsibility, provides training and permissions, and protects time for maintenance. Assuming marketing will handle the page whenever something comes up is not ownership. The firm should know who is accountable, who backs them up, and where the documentation lives.

What In-House Teams Underestimate

Building in a visual editor looks simple. The difficult work sits beneath the layout, where conversion design, integrations, measurement, accessibility and maintenance meet.

Conversion craft starts with the relationship between audience, offer, message and action. A page can look polished without communicating why the offer matters, and the work involves deciding what belongs on the page, how claims get expressed, what evidence suits them and how the form supports the next step. Not button colors.

Integrations create their own complexity. A form appears to work while submissions never reach the CRM. Lead-source information vanishes between systems. Duplicates create operational problems. A scheduling tool fails to pass the right information into a confirmation. Tracking events fire twice or not at all. None of which is visible in a browser preview, because testing means following the complete path through the receiving systems.

Accessibility needs deliberate attention: readable text, adequate contrast, keyboard access, meaningful labels, clear error messages, logical structure. Obligations vary by organization and law, so the firm determines its requirements rather than treating a visual review as proof.

Measurement needs the same care, since a page can receive traffic and produce submissions while providing unreliable data. The team has to know which events record, how consent choices affect measurement, where attribution lives, and whether reported conversions match the actions the firm meant to measure.

Then someone keeps it healthy. Platforms change, integrations update, scripts age, forms break after a third-party change, and content goes stale as products and processes evolve.

The most overlooked risk is ownership concentration. One employee builds the page, configures the integrations, and becomes the only person who understands the setup. When they leave, the firm inherits an asset it owns and cannot operate.

Documentation, backup access, securely managed credentials and repeatable testing reduce that. If the firm cannot explain how the page works without calling its original builder, the internal model is not finished.

What an Agency Genuinely Brings

Pattern knowledge from working across many projects, which does not transfer automatically and means the right partner has met similar conversion problems, integration failures and approval constraints before.

That experience surfaces risks earlier. A team that has built financial services pages knows to ask how forms connect to the CRM, how tracking behaves when consent is declined, how disclosures fit the design, and how the page gets maintained after launch.

Agencies also bring technical breadth. A page may need strategy, copywriting, design, development, analytics, accessibility knowledge and integration work. The firm does not need all of those continuously and needs several during a launch or major revision.

And a structured production process: requirements gathering, design review, browser testing, mobile checks, event validation and launch verification. Useful where documented, adapted to the client and carried through to handoff.

The relationship helps most where the internal team knows what it wants and lacks resources to build it, with a strong campaign concept and approved messaging that needs translating into a working page with reliable tracking.

Experience only counts if it is relevant though. A portfolio of attractive consumer websites establishes nothing about regulated financial services, sensitive customer information, complex form routing or your compliance workflow.

So examine the proposed process, technical responsibilities, access arrangements, documentation, testing and handoff, and establish whether the agency supports the page after launch and what that includes. For evaluating providers once you have chosen the model, see the buyer's guide to choosing a landing page agency. The decision to outsource comes first. Provider selection follows from the responsibilities you want someone else to hold.

What an Agency Cannot Own for You

It can learn the business, document the process and build a working relationship. It cannot replace the firm's authority over its products, claims, compliance decisions or institutional knowledge.

The firm supplies accurate information and decides which statements it will make. An external partner may flag unclear wording, and should not be treated as the final authority on whether a financial services claim is permitted.

For investment advisers subject to the SEC Marketing Rule, requirements may affect advertisements, testimonials, endorsements, ratings, performance presentations and related records depending on the circumstances, with application being fact-specific. Other businesses face different federal, state, industry or product-specific requirements.

Reviewing a page with an agency does not establish compliance. The firm's own process, counsel where appropriate, and applicable policies determine the review, approval, substantiation and recordkeeping required. See How to Make Landing Pages That Pass Compliance.

An agency also cannot promise instant availability because it understands the project. Its team works on other engagements and its agreement may exclude emergency support, so availability, response expectations, escalation and publishing authority get established in advance.

Institutional knowledge needs the same treatment. An agency keeps project notes and understands the page, and it is not the permanent repository of your internal decisions. Product details, approved claims, responsibilities and compliance interpretations stay documented in systems the firm controls.

Access matters too. If the agency holds the only administrator account, keeps source files in an inaccessible workspace, or controls a critical integration with no documented transfer, the firm cannot easily change providers or take ownership.

None of which argues against external help. They are reasons to define the relationship carefully, since a well-structured arrangement preserves the firm's authority while delegating defined production responsibilities.

Platform Choice Determines Who Can Own the Page

The technology underneath makes internal ownership straightforward or unnecessarily hard. Two pages can look identical to a visitor and have completely different requirements for editing, deployment and maintenance.

The firm's existing CMS fits naturally into current website governance, with staff who already know how to edit, manage permissions and publish. The trade-off is design constraint and development work for specialized functionality.

A dedicated page builder lets marketers create and revise campaign pages without touching the main site, useful where marketing needs a separate workflow, provided the firm understands how the platform handles access, tracking, forms, consent, integrations and data ownership.

A custom-coded page offers more control over structure and functionality and demands more specialized knowledge to maintain, test and deploy safely. The firm should know who can work on the code, where it lives, how changes get reviewed, and what happens if the original developer is unavailable.

So evaluate the platform against the ownership model before building. Can authorized employees make ordinary edits? Can the firm reach its analytics and integration settings? Are submissions handled according to its requirements? Could another provider take over? Is there a documented way to restore a previous version?

And separate access from competence. Giving an employee administrator privileges does not mean they should modify tracking scripts or production integrations. Permissions follow responsibilities, and critical changes need review and testing.

Ownership also needs a practical exit route: what exports, what depends on the platform, which third-party services stay active, and what moving the page elsewhere would take. Some platform-specific functionality will not transfer, so evaluate portability before becoming dependent on it.

A platform decision is a staffing and governance decision. Select technology the intended owners can realistically operate, or plan deliberately for the external support they will need.

The Hybrid That Usually Wins

The firm owns purpose, content decisions, approvals, platform access and business context. A specialist handles the work needing deeper conversion, design, development or integration expertise.

It starts with an explicit division. The internal owner maintains the brief, coordinates stakeholders and decides when a change is needed. Compliance reviews under its own process. The external partner handles agreed production, technical changes, testing and documentation.

Then separate routine edits from specialist work. An authorized marketer updates approved copy or replaces an image inside established design rules. A developer handles a new integration, a change to form logic, a significant layout revision, or a tracking implementation affecting measurement.

Document that distinction rather than leaving it to informal judgment, so both sides know which changes happen directly, which need review, and who verifies the page afterward.

Access follows the same principle. The firm keeps administrator access to the platform and systems it owns. The agency gets the permissions its work requires without unnecessary exposure. Critical credentials are managed securely rather than left in personal accounts.

Documentation is part of the deliverable, explaining structure, integrations, tracking events, form routing, dependencies, publishing process and testing steps, plus who to contact when a component fails.

And the arrangement needs a maintenance agreement: whether the agency provides ongoing support, works on defined projects, or takes separately agreed requests, how urgent changes escalate, and what happens if they cannot take the work.

Review it after launch. Are internal staff actually making the changes they were meant to own? Are technical requests reaching the right person? Does the agency still understand the setup?

A hybrid is not automatically right. If the internal team lacks capacity for routine work, nominal ownership creates another bottleneck. If the firm has a mature web and marketing operations function, it may need little ongoing support. The point is dividing responsibilities deliberately, so the firm neither outsources business judgment by accident nor absorbs technical responsibility simply because a page was delivered.

When Should You Bring Pages In House?

When the firm can maintain the technology, manage approvals, preserve documentation and handle routine changes without an external provider in every decision.

The clearest sign is a recurring need for changes internal staff could manage with the right access and training. Where copy, approved disclosures, calls to action or content sections change regularly, internal editing reduces coordination and returns control.

The second is an established website or marketing operations team that understands the publishing environment, owns analytics and CRM workflows, and has a review process. Adding pages extends existing work rather than creating new work.

The third is a need for closer integration with product, sales or customer operations, where a page depending on frequent product updates benefits from being maintained by the people closest to those systems.

But follow a capability assessment. Identify who maintains it, the time they have, the systems they can reach and the technical work they can do confidently, then establish backup ownership and documentation before transferring responsibility.

A sensible transition runs in stages. The agency documents the page and its dependencies. Internal staff get access and training. The team practices routine changes somewhere appropriate, verifies the result, and learns how to escalate. Then both sides agree what stays external.

Do not confuse ownership with eliminating outside support. A firm can own its page and still hire a specialist for complex integrations, a redesign or accessibility remediation. The goal is controlling the asset and making informed choices about help.

And do not bring a page in house simply because an engagement ended. If nobody can maintain the integrations, check measurement or document the setup, the firm has accepted responsibility without acquiring the capability.

The Diagnostic

Before deciding, ask questions that expose the workload rather than who can produce a design.

Who makes an ordinary change, publishes it and verifies the live page? Who owns compliance coordination, submitting changes for review and confirming the published page matches what was approved? Who diagnoses a technical failure like a broken form, a missing CRM submission or a failed integration? Who controls the platform, holds administrator access, and could maintain the page if the agency relationship ended? Who understands the measurement setup well enough to explain which events track and whether the data reflects real actions? Who documents decisions and dependencies, and could someone else use that record? What happens when the primary owner leaves? What genuinely requires specialist skills as opposed to routine maintenance? How are urgent changes handled when the normal owner is unavailable? And can the firm change providers or platforms, knowing what exports and what has to be recreated?

Then look for gaps between responsibility and capability. If marketing is accountable for page performance and cannot access the page or inspect its tracking, the model is incomplete. If an agency is expected to maintain an integration and the agreement excludes technical support, the responsibility is unclear. If compliance approves the content and nobody verifies the live version, the review has a hole in it.

The answers determine the model. Do not choose in-house or agency first and assume the missing responsibilities resolve themselves.

Decide Before the Next Page Launches

The wrong time to discover an ownership problem is after a campaign is live and a necessary change sits in somebody's queue.

So before commissioning the next page, document the work to build it, the responsibilities that continue after launch, who owns them, and the systems they need. Agree the review process, technical support, documentation and transition arrangements before the project starts.

For some firms an established internal team builds and maintains pages effectively, with the context, tools and discipline to change things without creating dependencies. For others an agency supplies technical breadth and conversion expertise that would be hard to maintain internally. Many need both.

The choice is not permanent either, since the right division shifts as the organization develops skills, changes platforms or takes on more complex campaigns.

What stays constant is clear ownership. Someone has to know how the page works, how changes get approved, how performance is measured, and how the asset gets maintained once the original builder has moved on.

A page is finished as a project when the build is complete. As a business asset it is never finished at all. Choose the model that lets your firm manage that deliberately, rather than confusing a successful launch with a sustainable operating process.