First growth hire: define the job before you recruit

A founder I know posts a growth marketer role on a Monday. By Friday the job spec covers SEO, paid ads, outbound, lifecycle email, analytics and a content calendar. Three months later the role is still open, the product team has shipped two more releases, and nobody owns a single customer-finding task.

The problem isn't the budget or the talent pool. The job was written as a title, not as work. "Growth person" is a bundle of ten jobs, and no single human is good at all of them.

This guide is for funded seed-to-Series-B software teams who have proof of demand and nobody owning growth. It gives you a decision framework, a one-page first-month job brief, and a clear view of where a person fits better than an agent and where the reverse is true. The order matters: define the work first, then decide who does it. Do that and your first growth hire gets a lot less risky, whether it's a person, an agent, or both.

Start with the work, not the job title

Every growth tool needs someone to run it. Revnu doesn't. That's the whole reason to define the work before you pick a body to do it.

Here is the pattern behind most failed first hires. A team buys an SEO tool, an outbound tool, an ads dashboard and an analytics suite. Each tool produces advice, lists or charts. Then somebody has to read the output, decide what matters, write the page, send the sequence, adjust the bid and report back. The tools didn't remove the work. They renamed it "tool administration" and handed it to whoever got hired.

So when you write a job description that says "own SEO, paid, outbound and lifecycle," you aren't hiring a strategist. You're hiring an operator to run five tools, and paying a salary to close the gap between what the tools say and what actually ships.

Revnu is built on a different assumption. It's an agent that runs the loop a good growth hire or agency runs: try SEO, outbound, LinkedIn and ads, measure everything, kill what doesn't work, double down on what does, and report to the founder. The channels share one memory, so a winning ad headline or a sales objection feeds the other channels.

Take a position before you read further. Don't start by asking "who should we hire?" Start by writing down the three or four pieces of work that would move customer numbers in the next 30 days. If you can't name them, no hire will fix that. If you can, the rest of this guide is easy.

When should you hire your first growth person? Signs the timing is right

Most teams hire too early or too late, and both mistakes look the same from the inside: a growth role with no clear mandate.

Here are the signs the timing is right.

You have proof of demand. Real users, real revenue, or at least repeatable conversations that end in a trial. Growth work amplifies something that already works. It doesn't manufacture a product people want.

Product work keeps beating growth. If your roadmap meetings always end with "we'll do SEO next sprint," you have a staffing gap, not a prioritisation problem.

You can name the customer. A first growth hire without a defined buyer will spend two months on discovery you already did in sales calls.

You can describe a single goal. "More pipeline" isn't a goal. "Book 15 qualified calls a month from mid-market fintech" is.

And here are the signs it's too early. You're still changing the product category every few weeks. Nobody has closed a customer outside your own network. You expect the hire to also define positioning, pricing and the ideal customer profile. That's founder work, and handing it off tends to produce confident noise.

One more filter: ask whether you want a person to manage the work or the work to get done. Those are different purchases. A head of growth builds a team, a process and a point of view over 12 to 18 months. If what you actually want is outbound running, pages publishing and ads being tested by next week, you're shopping for execution, and an agent can take that today.

For a deeper look at that tradeoff, see Can AI Agents Replace a Growth Team? What Actually Changes.

Write the job brief: customer goal, job to own, out of scope

A good first-month brief fits on one page. It has three parts, and each one forces a decision you've probably been avoiding.

Customer goal. One sentence naming who you want and what they do next. Example: "Get 20 heads of finance at UK Series A to Series C fintech companies into a demo." Not "grow awareness." Not "improve the funnel." If the sentence has two goals, cut one.

Job to own. One job, not a function. "Run outbound to that audience" is a job. "Be responsible for demand generation" is a function, and functions are how first hires drown. The test: can someone tell, at the end of a week, whether the job moved? If the answer needs a debate, narrow it.

Out of scope. Most briefs skip this section, and it protects the first month. Write down what the hire won't touch: brand redesign, pricing changes, product roadmap input, a new category narrative, hiring a team. Putting those in writing stops scope from quietly tripling.

A fourth line is worth adding: what already exists. List the assets you have, such as customer interviews, a CRM export, past campaign results, a blog with some history. A first hire who starts from nothing burns a month on archaeology.

The same brief works whether you recruit a person or put an agent on the job. That's the point. A brief that only a human can read is usually too vague to be useful. If you're weighing the agent route for the SEO side of the job, programmatic SEO for SaaS founders who can't write every week shows what a single well-scoped job looks like in practice.

Write the brief before you open a single job board tab. If it takes more than an hour, that tells you how ready you are.

Access and approvals: what day one needs and what stays with you

The fastest way to waste a first growth hire is to make them wait for logins. The second fastest is to give them everything and discover later that nobody agreed who approves spend.

Split access into two lists before day one.

What day one needs: your website and CMS so pages can be drafted and published, Google Search Console, the sending inbox if outbound is in scope, any ad accounts involved, and a place to report, ideally the channel you already live in. For Revnu, that's Slack or iMessage, with Gmail or Outlook, Search Console and the relevant ad accounts connected when the job calls for them.

What stays with you: launching or raising ad spend, anything that speaks for you publicly in a new way, claims about customer results, and changes to positioning. Put these in writing as approval gates, not as trust issues. Even a great human hire shouldn't commit budget on day three.

With Revnu the gates are concrete. On Pro defaults you approve each new sequence once, and its emails and follow-ups then run. Prospect replies, new spending commitments and budget changes always wait for you. Ad campaigns are created paused, and nothing launches or spends without your approval. That's the right shape for a first month: the work moves without you hovering, and the decisions with real downside stay yours.

A practical rule: if an action is reversible and cheap, let it run. If it spends money, speaks in your name to a new audience, or can't be undone, it needs a yes. Write that rule into the brief.

If CRM data is part of day one, you don't need a migration project. You can keep HubSpot, Attio or Salesforce and run Revnu alongside, or export selected contacts as CSV or XLSX and upload them in dashboard chat. Import CRM contacts into Revnu covers both routes. It's a snapshot, not a two-way sync, and uploading alone doesn't authorise sending.

A hypothetical shared-memory loop across outreach, search and ads

The strongest argument for treating growth as one job instead of five is shared memory. Here's a hypothetical, not a customer result, to show the shape.

Say your customer goal is demos with operations leaders at mid-market logistics software companies. Week one, outbound goes to a researched list with two angles: one about reducing manual dispatch work, one about carrier onboarding time. Replies come back. The dispatch angle draws interest. The carrier-onboarding angle draws a recurring objection: "we already have a tool for that."

In a stack of separate tools, that learning lives in one person's inbox. In a shared-memory loop, it moves. The search side shifts toward pages that answer the dispatch question buyers are asking, and away from the carrier-onboarding topic. The ad copy tests the dispatch headline first and addresses the existing-tool objection head on. The next outbound batch opens with whatever phrasing the ad test showed clicks best.

That's the loop a good growth operator runs in their head: one finding, three channels updated. It's also the loop that breaks when channels belong to different people, different agencies or different tools that never talk.

Revnu is described as working this way: one memory across channels, so an angle that works in one, an ad headline or an objection from outbound replies, feeds the others. It then reports what changed and what it plans to measure next.

Two cautions. First, the loop only compounds if you give it one goal. Spread across five goals, it produces five weak signals. Second, a loop is only as good as its approvals. A winning angle shouldn't raise ad spend on its own. That still waits for you.

For how a single agent sequences this kind of work, see what an AI growth agent for SaaS can actually do today.

Set one measurable first-month outcome and a check-back date

A first month without a measurable outcome is a month of activity reports. Pick one number, pick a date, and write both into the brief.

Good first-month outcomes sit close to the work and show up within weeks. Booked calls from a defined audience. Replies from a researched list. Published pages indexed and getting impressions. Trial starts from a tested ad angle. Pick the one that matches your customer goal, and resist adding a second.

Bad first-month outcomes are lagging or fuzzy: revenue attributed to the new hire, brand awareness, "pipeline influenced." Those matter later. In month one they hide whether the job is working.

Then set the check-back date. Not "we'll review in a few weeks." A calendar date, ideally three to four weeks out, with a lighter check at the one-week mark to catch access problems or a misread brief. At the check-back, ask three questions: did the outcome move, what did we learn that changes the next month, and what should be killed.

The discipline is the same whether a person or an agent does the work. It's also how Revnu is meant to be run: pick one bottleneck, ship one concrete artifact or queue one approval, schedule the measurement, report the delta. A daily review and scheduled check-backs mean results arrive in Slack or iMessage instead of sitting in a dashboard you have to remember to open.

Keep expectations honest. A first month is for finding out what the audience responds to, not for proving a full growth engine. If the outcome moves, double down. If it doesn't, you have a cheap, fast answer about the angle, the audience or the offer. That's worth more than a quarter of polite status updates.

Where a human hire fits better, and where Revnu is faster

Neither option wins everywhere.

A human hire fits better when the job is mostly judgment and relationships. Defining positioning for a new category. Building partnerships. Leading a brand and PR push. Managing a growing team. Running in-person events and community. If your first six months need someone to set strategy and then build the organisation around it, recruit a head of growth and give them room.

A human hire also fits when your motion is heavily enterprise, with long cycles and procurement-heavy marketing operations. Those need continuity of relationships, and a software agent isn't the answer there.

Revnu is faster when the job is the execution loop across channels. It handles day-to-day execution across multiple growth channels while keeping spend gated on your approval. It starts from your website, with no recruiting cycle.

The cost shape differs too. Pro is $99 a month, self-serve, with a trial offer shown at signup and checkout and cancel-anytime terms. Managed is custom-priced, with a growth engineer from the Revnu team on the account, and the route in is a 30-minute call at revnu.com/book. A dedicated growth engineer belongs to Managed and the YC deal, not Pro.

A sensible middle path for many funded teams: put the agent on the execution job now, and recruit the human later, once you know which channel has earned a full-time owner. For a side-by-side view of how this compares with a wider agency route, see a growth agency alternative when you need the work done.

Conclusion

Before you post a role, spend one hour writing the brief: one customer goal, one job, named access, approval gates, one month-one outcome and a check-back date. Then decide who runs it. If the answer is a strategist who'll build a team over the next year, recruit that person and hand them the brief. If you want outbound, search and ad tests running this month, with you approving anything that spends, put the brief into Revnu instead. Start at revnu.com on Pro, or book the 30-minute call at revnu.com/book if you want a growth engineer on the account. My prediction: teams that write the brief first will hire later, hire better, and know exactly which channel deserves a full-time owner.