When should a company run growth-driven design in-house versus hiring an agency?

Growth-driven design keeps improving a site after launch. The method's continuous improvement cycle has four steps: plan around a focus metric, build in a cross-functional team, learn from the experiments and the data, and transfer what was learned to marketing, sales and service. Whoever runs it is responsible for all four.

"Cross-functional" describes the skills in the room. The cycle needs four kinds of work: reading analytics and customer research, writing and designing the change, building it in the CMS, and deciding what ships. One person can hold more than one of those. None of them has to be a full-time role.

This is why headcount is a poor guide to the decision. A company can employ a designer, a developer and a marketer and still not be able to run the cycle, because their weeks are full of campaign pages, sales requests and product launches. What the cycle needs is capacity, meaning hours that are set aside for it and aren't the first thing given up when something urgent arrives.

Suppose a 40-person software company has one marketing manager, a contract designer and a developer shared with the product team. The skills are all present. But the developer's website time is whatever is left after the product sprint, and in this company that's a few hours a month. So a plan gets written and half built, and the result goes unread.

Your own people start with access to customers and product knowledge, which an outside team has to be given. Good hypotheses come from sales calls, support tickets and conversations with the people who build the product. An internal team can reach those sources directly. An agency needs recordings, introductions and time with your subject experts before it can use them, and its work will follow the quality of that access.

Your team can also sit closer to approval. A change that needs three sign-offs across two departments can move slowly whoever builds it. When the person who owns the site also runs the cycle, there are fewer handoffs between a finding and a decision.

So in-house fits when the skills exist, the hours are protected, and the site matters enough to the business that those hours will be defended in a busy quarter. If the website is where most of your sales conversations start, that case is easier to make internally, and the understanding the team builds up stays inside the company.

What you're buying from an agency is capacity that's already assembled: research, design, development and analysis skills that work together, with hours reserved for you. Those are the things to get in writing, because an agency's name on the contract doesn't supply them automatically. In the example above the skills were present and the hours were missing, so the thing that company would be buying is reserved build time.

Lean Labs' growth-driven design program is a documented example of the arrangement. The agency runs the improvement work in 30-day cycles on HubSpot CMS. The work draws on page behavior, form results, CRM lifecycle data and feedback from the client's sales team, and the candidate changes are ranked by expected effect on pipeline, by buyer relevance and confidence, and by effort. The agreement renews each quarter.

The inputs include CRM data and sales feedback, so the client still has work to do: someone on your side has to open the CRM and make the sales team available. The term is a quarter. When you compare an agency with a hire, or one agency with another, compare the actual terms on the table, including how long each commitment runs and what it takes to end it.

Platform knowledge is a fair reason to look outside when your site runs on a CMS your team doesn't know well. Ask for evidence of it, such as recent work on that platform and the names of the people who would do yours.

Price the hours as well as the fee. Knowmad's published tiers for its ongoing design service start at $800 a month for 4 hours, $1,400 for 7 hours and $1,800 for 9 hours. That's one firm's starting price for its own service, and it shows what a monthly figure alone doesn't: the amount of work it reserves. With any agency, ask how many hours the fee covers, which skills fill them, and what scope of planning, building and measurement fits inside them each cycle.

In a mixed arrangement, each part of the cycle is assigned to whoever can do it with the least friction. Customer access and decisions are the two that need an owner named on your side. Someone at your company has to choose the focus metric, approve what ships, and make sure customer input reaches the people doing the work. An agency can still do the gathering if you arrange the access. Lean Labs' account of the strategy stage names customers, sales reps and support staff as the people to talk to.

Design, development and test setup can go outside when you lack those skills or can't protect the hours. Outsourcing isn't the only answer to a missing skill. You can hire for it, train someone, or narrow the program to what your current team can cover. Which is right depends on how long you expect to need the skill and how soon you want to start.

The split can also change over time. One version has an agency build the first site and run the early cycles, with your team taking over the parts it can staff later. If you want that option, plan for it in the first contract.

Three terms make any of these arrangements easier to change. Your company should own the CMS, analytics and testing accounts, with the agency added as a user. The backlog and the experiment log should live somewhere you can open without asking. And the agreement should say what gets handed over when it ends: design files, templates, documentation and the record of what was tested. These are our recommendations for the negotiation. We go through them in what a growth-driven design contract and retainer should include.

The transfer step in the method is a different thing from that handover. Transfer means sharing what the site taught you about buyers with marketing, sales and service. It happens every cycle, under any arrangement.

Start by writing a name beside each skill the cycle needs, and beside each name the weekly hours that person has for the site. The gaps on that page are what you have to fill. A missing name can be filled by an agency, a hire, a contractor or a smaller program. Zero hours beside a name is a capacity problem. Either that person gives up other work, or the same options apply.

Then settle who decides what ships. Slow approval hurts under either arrangement. It can cost more with an agency, since reserved hours can pass while a decision waits. If approvals run through a committee today, consider giving one person the authority to approve routine changes before the first cycle starts. For a team covering the skills with few people, how a three-person growth-driven design pod is structured shows one way to divide the roles.

Last, think about what happens when people change. An internal team can lose the one person who held the knowledge. An agency arrangement can end with a budget cut, or the people on your account can move on. The experiment log helps in both cases, because it lets the next person continue from where the last one stopped. If you do go outside, the services a growth-driven design agency should provide is a useful list to hold a candidate against.