Questions we answer
Start from the question you're actually asking.
Each of these is a question a founder or manager types into a search engine at eleven at night. Each page gives an honest answer, then hands you into the diagnostic with that question already on the table.
Should I hire another person?
Sometimes. Whether a hire is the proportionate answer depends on how durable the need is, whether anyone owns the work today, and what a new person would actually add.
My team is overloaded. What should I do?
Start by finding out whether the overload is volume, design or ownership. Each has a different fix, and only one of them is more people.
Do I need a new hire or a better process?
Usually the process first, because it is cheap to try and tells you how much of the load is design rather than volume. Sometimes both.
Can AI help my team?
Often, but the useful question is where. AI that helps a person draft, summarise or analyse is a different decision from AI that runs a process.
Should I automate this work?
If it is repeatable, frequent, low-judgement and written down, quite possibly. If any of those is missing, fix that first.
Too much depends on one person. What are my options?
Reduce the fragility before it becomes a crisis: write the work down, develop a second person, move adjacent work off them, or decide it is acceptable for now with a date to look again.
We have a skills gap. Should I train, hire or bring someone in?
It depends on how long you need the skill, how soon, and whether anyone in the team is close to it. Each answer points at a different route.
Should I outsource or hire?
Outsource when the work is a definable outcome that does not need to live in your team. Hire when it is core, durable and needs to be owned by your own people.
Should I offshore part of my team's work?
Only if the work is well documented, repeatable and definable, and you have the management time for hand-offs. It is not automatically cheaper or better.
How should I structure my small team?
Most structure problems in small teams are ownership problems. Decide who owns what before you draw a chart or add a layer.
Nobody owns this work. What do I do?
Give it an owner. That is almost always the first move, and it is faster and cheaper than anything else on the list.
Should I use a freelancer or hire?
A freelancer or specialist fits a defined piece of work or a temporary need. A hire fits a durable, growing one. The diagnostic asks which you have.
Quality is slipping in my team. Is it people, process or workload?
More often process than people. Slipping quality is usually a sign that the work has outgrown the way it is done, not that anyone has stopped trying.
Should I hire or automate this role?
It depends on what the work actually is. Repeatable, frequent, low-judgement work can often be automated; durable, growing, judgement-heavy work usually needs a person. Most real roles are a mix, and the honest answer is often to automate part of it first.
Do I need a CTO?
Not always, and not always yet. The question is what technical leadership the business needs over the next year or two — and whether that is a permanent seat, a fractional or interim leader, or capability grown from inside.
Do I need an AI agent, or just better tools?
Usually better tools first. An agent runs a defined workflow inside boundaries; a tool helps a person do their own work faster. The diagnostic tells you which the evidence supports.
Should I hire another salesperson?
Only once you know whether the constraint is demand, conversion or capacity. Another salesperson adds capacity; it does not on its own create a pipeline or fix a way of selling that is not working.
Is this a process problem or a people problem?
More often process than managers expect. If your most capable person would struggle in the same seat, the work is badly shaped. If one person struggles where others do not, the answer is about that person.
Everything comes back to me — what do I do?
Decide which decisions genuinely need you, hand the rest over with the authority to go with them, and write down what only lives in your head. Most founders are the bottleneck because nobody has been told where the line is.
How do I know if my team needs more headcount?
Look for a gap that is durable, growing and visible in outcomes rather than in how busy people feel. Missed commitments, work that has quietly stopped and an inability to absorb anything new are better evidence than hours.
Should I hire a graduate?
A graduate fits where the work is learnable, somebody has time to teach, and the capability is needed for years rather than months. You are buying potential and paying for it in supervision rather than salary.
What should my next hire be?
Start from the constraint rather than the wish list. The right next hire is the one that releases the most work or removes the largest risk — which is often not the role that feels most overdue.
Should I fix the process before hiring?
Usually yes, at least far enough to know what the new person would own. It is cheap and quick, and it either removes the need or tells you exactly what to recruit for. It stops being sensible once it becomes a reason never to decide.
Do I need another manager?
Only if the problem is span of attention rather than unclear ownership. A manager helps when there are more people than one person can support properly; added to fuzzy roles, a manager adds a layer to the confusion.
Repetitive admin is eating the week
Work out how much of it should exist at all before automating any of it. Some repetitive admin is a process nobody has simplified, some is a good candidate for software, and a little of it genuinely needs a person.
Should I hire now or wait?
Timing is a real decision, not a delay. Hire now when the need is durable and fundable and the role is defined; wait when any of those is still a guess.
Should I hire full-time or contract?
Contract buys speed and information; permanent buys accumulation. The right answer depends on how durable the need is and whether you need the knowledge to stay.
Should I replace someone who left?
A departure is the cheapest chance you will get to ask whether the role should exist in the shape it did. Replacing like for like is a decision, not a default.
Should I hire a junior or a senior?
Seniority is a decision about how much definition the role comes with. A senior defines the work; a junior needs it defined, and someone with time to do that.
Can I afford to hire right now?
Affordability is not the salary. It is the salary plus recruitment, onboarding, management time and the months before the person is productive — against what happens if you do not.
When should a startup hire its first engineer?
When there is durable technical work, someone who can judge technical quality, and enough definition for an engineer to own something rather than wait to be told.
Is my team too small?
Team size only means something against the work. The useful question is whether what is being asked of the team is achievable by the people in it, arranged the way they are.
Do I need a management layer?
A layer is justified by the number of decisions and people one person can hold, not by headcount milestones. Added to unclear ownership, it makes the ambiguity more expensive.
Should I promote internally or hire a manager?
Promotion keeps context and risks losing a good contributor; hiring brings experience and starts from zero context. The deciding factor is usually support, not talent.
When should a startup hire a COO?
When operational load is genuinely holding the business back and there is a defined remit to own — not when a founder wants to stop doing the parts of the job they dislike.
Do I need a chief of staff?
A chief of staff multiplies one leader's capacity across whatever matters that quarter. It works where the bottleneck is genuinely that leader — and disappoints where the problem is missing functional ownership.
Do I need a CTO or a lead developer?
One sets technical direction and builds a team; the other builds the product well. Most early companies need the second and advertise for the first.
Is this a busy period or a real capacity problem?
A peak has a shape and an end; a capacity problem does not. Telling them apart before you commit to a salary is the single most valuable thing you can do here.
How do I reduce workload without hiring?
Three levers in order: stop doing some of it, change how the rest flows, and automate what is genuinely repeatable. Most teams reach for the third and skip the first two.
My best people are doing low-value work
Expensive people doing cheap work is a real and quantifiable loss. The fix is usually to move or remove the work, not to hire someone junior to absorb it.
Who should own this work?
Ownership is accountability for an outcome plus the authority to decide. Anything less is a task list with someone's name on it, and it will not hold.
Projects keep slipping — what should I do?
Repeated slippage is information. What matters is where it slips: consistently in the same place is a process problem, everywhere at once is usually over-commitment.
How do I fix handoff problems?
Work fails at the joins more often than in anyone's hands. Fixing it means agreeing what "ready" means at each boundary — and having someone own the outcome across it.
Should I document the process before automating it?
Yes, and not because documentation is virtuous. Writing it down is how you find the steps that should not exist — which is most of the value automation ever delivers.
Is my process ready to automate?
Four things have to be true: the steps repeat, they are written down, it happens often enough to pay back, and someone can say what a failure costs.
What should I automate first?
The most frequent, most repeatable, best-understood, lowest-stakes thing you do. Not the most annoying one, and not the one with the best demo.
Should I use AI or hire someone?
They answer different problems. AI reduces the effort in work that repeats; a person absorbs work that needs judgement, relationships and context.
When is an AI agent the wrong answer?
When the process is undocumented, the work is rare, the judgement is high, the stakes are serious without a design to match, or a system you already pay for does most of it.
Can AI handle customer enquiries?
Part of them, well, with a person holding the line. The split that matters is between enquiries with known answers and those needing judgement, empathy or authority.
Should I automate reporting?
Usually yes, and usually after asking which reports anyone actually uses. Automating a report nobody reads makes it permanent.
Is it cheaper to hire or outsource?
Outsourcing is usually cheaper over months and more expensive over years. The comparison that matters includes management time and what you are left holding at the end.
Should I hire in-house or use an agency for development?
An agency is right for a defined build with a specification and an end. In-house is right when the product is continuous and the context has to stay.
Should I use a fractional executive?
Fractional works where you need senior judgement rather than senior capacity, and where someone internal can carry the execution between sessions.
Should I hire my first employee?
The zero-to-one hire is different from every hire after it: it creates a fixed cost you cannot switch off, and it makes you a manager the same week.
Should I hire part-time or full-time?
Size the role to the work, not the budget. Part-time suits work that batches; it breaks on work where somebody has to be reachable.
Do I need an HR person?
Usually not as an employed role at this size. What gets called HR is three different jobs, and only one of them is a person you hire.
Should I hire a virtual assistant or an employee?
Often neither yet. A VA works on work that is documented and hands over cleanly; an undocumented mess delegated remotely comes back with more email attached.
How many people should report to one manager?
There is no correct number. The limit is set by how much of that manager's week is actually management, and by how different the reports' jobs are.
Should I hire a generalist or a specialist?
Count the days of genuine specialist work first. Below about a day a week, a full-time specialist drifts into work they are not good at and leaves.
Should I hire a marketer or use an agency?
Also asked as whether to outsource marketing or hire in-house. Marketing is strategy plus execution, and they rarely arrive in the same affordable person.
Should I hire more staff or pay overtime?
Overtime is the right tool for a spike and the wrong one for a trend. If you have run hot for a quarter with no end date, you are deferring a decision rather than making one.
Is my business too small for a CRM?
Often yes, for now. A CRM solves a handoff problem, not a memory problem — and a half-adopted one is a worse record than the spreadsheet it replaced.
We have too many tools. What should we cut?
Count problems, not tools. Ten tools each doing one job cleanly are fine; three holding the same customer list are not.
Should we build custom software or buy something off the shelf?
At this size, almost always buy. The cost that sinks small-business builds is not the build — it is owning it in year two without a developer.
Nobody has written our processes down. Is that a problem?
Only where a process runs regularly and one person knows it. Documenting everything is a project small teams abandon; documenting a broken process makes the bad version official.
Why do new starters take so long to get up to speed?
Usually because the knowledge is in one busy person's head and nobody owns the first month — not because the induction is thin or the person is slow.
Should I hire a bookkeeper or use software?
It is a three-way choice, not two. Software alone, software plus an outsourced bookkeeper, or somebody employed — and for most small teams the third never arrives.
Who maintains our automations when they break?
Whoever built it — and if they have left or are too busy, you do not have an automation, you have a liability nobody is watching.
Should I let AI write proposals and client-facing work?
Split the document. Structure and boilerplate, usually yes. Pricing, scope and anything you would be held to, no — and expect drafts to converge with your competitors'.
Should I hire an AI consultant or an automation agency?
Neither, until you can name the process and what better looks like. A consultant sells a decision; an agency sells a build. Buying the build first is how you end up with workflows nobody can maintain.