How to Decide on Your First Consulting or Agency Hire

Your first consulting or agency hire should address a clear delivery constraint and have a credible case for covering its true costs. Start by defining the outcome you need, the work the person will own and their authority—not by choosing a job title. Record the evidence behind the decision and how you will judge whether it is working.

Start with the constraint, not the job title#

Feeling busy is a reason to investigate capacity, not sufficient evidence to hire. The central question is: which role would make delivery more repeatable while covering its true costs?

Hiring to make the business look more established is different from hiring to improve delivery. Before writing a job description, identify the constraint: completing client work, maintaining quality, coordinating delivery or protecting time for business development.

Define who owns the hiring decision, the period it needs to support and the consequences of getting it wrong. Consider both the cost of committing before demand supports it and the cost of leaving a genuine delivery problem unresolved.

Identify the work the first hire should take ownership of#

Map recurring work rather than collecting everything you dislike doing. For each activity, record the intended result, who currently handles it and why it needs their attention.

Look beyond tasks to the decisions within them. Preparing a client deliverable might involve interpreting requirements, resolving conflicting feedback and deciding when to escalate a problem. A role built around tasks alone can leave those decisions with the founder.

Separate your observations into three groups:

• Verified facts: evidence traceable to delivery records, client commitments or financial information.
• Hypotheses: explanations you believe but have not tested.
• Unknowns: information you still need before committing.

“The founder spends too much time coordinating delivery” is a hypothesis until you establish what coordination involves and whether someone else could own it. Define the intended outcome before choosing a delivery, operations or other role.

Test the capacity and economic case#

Compare the proposed hire with the current way of delivering work. What would change, what would remain with the founder and what additional management work would the hire require?

Use two practical review questions:

• Capacity released: what work or decisions would the founder no longer need to handle, after allowing for supervision and review?
• Retained margin: what margin would remain from the relevant work after accounting for the hire and associated delivery costs?

These are working definitions, not universal hiring thresholds. Define them consistently for your business and establish a baseline before the role begins.

Assess the cash, time and capacity implications. As a practical check, consider pay or fees alongside applicable employment costs, tools, training, management time and the effort needed to hand work over. Verify which costs and requirements apply to your arrangement.

Keep evidence that challenges the case. Uncertain demand, unclear responsibilities or a continuing need for substantial founder review belong in the decision, not outside it.

Turn the case into a role scorecard and hiring decision memo#

Two short records can make the reasoning clear. The scorecard describes what the role is for; the memo explains why you should make the commitment.

The structures below are practical adaptations of the decision framework, not fixed templates.

The role scorecard#

Focus the scorecard on ownership and outcomes:

• Purpose: the delivery constraint the role should address.
• Intended outcome: what should become more reliable or repeatable.
• Recurring responsibilities: the work and operating decisions the person will own.
• Boundaries: what remains with the founder or another approver.
• Evidence of progress: how you will assess quality, capacity released and retained margin.
• Review date: when you will revisit the role’s scope and effectiveness.

Avoid making the first hire responsible for every unresolved problem. If the scorecard combines unrelated responsibilities, ask whether it describes a coherent role or merely the founder’s backlog.

The hiring decision memo#

Record:

• The proposed decision and its accountable owner.
• How the role is expected to improve delivery.
• Available evidence and its sources.
• The main unresolved assumption.
• Expected cash, time and capacity implications.
• The next commitment and who can approve it.
• The evaluation signal and review date.

The memo need not be lengthy. It should distinguish what you know from what you expect, so you can revisit the reasoning when circumstances change.

Define authority before handing over work#

Responsibility for doing work does not automatically include authority to change price, accept risk or make client commitments. Make those boundaries explicit before delegation begins.

A simple table can help:

Set escalation conditions as well as a review cadence. Decide which issues require immediate approval and which can wait for a scheduled discussion.

Important facts and policies need a source of record, an owner and a clear indication of whether they are current. Give the person access to the information needed for their decisions, with appropriate permissions. More dashboards will not resolve conflicting assumptions about scope or client commitments.

Review the hire against the original case#

Identify the smallest useful next commitment before assuming a full-time role is justified. A bounded test might validate the work package or test a limited handover, where legally and contractually appropriate. It should address the main uncertainty, not simply postpone the decision.

For illustration, consider a consultancy contemplating its first full-time hire. Its hypothesis is that transferring recurring delivery preparation would release founder capacity. Mapping the work reveals that some preparation is repeatable, while interpretation and client approval still require the founder.

That distinction could support a narrower role—or further investigation before hiring. This scenario is hypothetical, not a customer story or measured result.

At review, compare outcomes with the baseline. Combine early signals, such as whether work is being handed over successfully, with later evidence about capacity released and retained margin. Include qualitative observations. Account for changes in clients, work and conditions rather than attributing every change to the hire.

Decide in advance what evidence would justify continuing, changing the role or stopping expansion. Positive initial evidence supports further investigation; it does not establish that the same approach will work in other circumstances.

This framework addresses the hiring decision, not the complete recruitment process. Candidate sourcing, interviews, references, offers and onboarding require separate planning. Check employment, contractual, privacy and intellectual-property requirements against applicable official guidance.

Keep the decision connected to delivery#

The scorecard and memo should remain operating references after hiring. They explain why the role exists, what the person owns, which decisions require approval and when the arrangement needs review.

Within an appropriate Dainin CEOS configuration, Work & Delivery, Organisation Double and Decision Authority can help preserve that context, connect supporting evidence to subsequent work and route consequential actions through the appropriate authority. Their purpose here is to support judgement and retain learning.

Before making the commitment, draft a concise role scorecard and hiring decision memo. Name the outcome, supporting evidence, main unresolved assumption, approval owner and review date. Resolve gaps in the case before committing to the role.