Head of Delivery

Craft Digital; United States; Remote; USD 95,000 - 135,000; Full time

Job summary

Craft Digital AI is seeking a Head of Delivery for a fully remote role across the United States. The successful candidate will own delivery from project initiation to client deployment, guiding developers, and ensuring outcomes align with business goals.

You will lead client engagements, write briefs, prioritize work, and maintain strong relationships while steering projects toward measurable impact using AI-powered systems.

Qualifications

• Experience leading technical delivery teams.
• Ability to translate client needs into actionable briefs for developers.
• Strong communication with clients and internal stakeholders.

Responsibilities

• Own delivery from agreement to client deployment.
• Lead developers, set priorities, review work, remove blockers.
• Maintain client relationship through delivery and assess requests against goals.
• Own technical onboarding and project status across integrations, testing, and launch.

Skills

Delivery leadership

Developer management

Client relationship

Communication

Tools

Slack

Claude Code

Cursor

Job description

Craft Digital AI · Full-time · Remote, anywhere in the U.S.

$95,000 to $135,000 per year

Head of Delivery

Craft Digital AI · Full-time · Remote, anywhere in the U.S.

$95,000 to $135,000 per year

About Craft

We build AI-powered systems that help businesses work better and grow. We don't start with the technology. We start with what's getting in the way. Some clients get a system we've already built and run in production. Others need software no standard product covers, so we build it. Either way, they own what we build.

We're a small team with more than 30 systems in production, and we're growing on referrals and repeat work. We want to stay small and very good.

The role

You own delivery: everything between the moment we agree to build something and the moment the client is using it.

When our founders meet a client, they're not taking an order. They're working out what's actually slowing the business down, what has to be built, and what has to be replaced or worked around for it to matter. Every project starts from that outcome. Your job is to keep it pointed there.

That means two things. First, you run our developers. They're good at building. They shouldn't have to guess what a client meant, and they shouldn't decide on their own what the client needs. You set priorities, write the brief, review the work, and clear what's in their way. Second, you own the client relationship through delivery. When a client comes back with \"can you also…\", you're the one who decides whether it serves the goal we were hired for, and you're the one who says so, either way.

Today our CTO does this on top of his own job. It's the job we need most. You'll report to him, and work with our CEO on the commercial side of every account.

What you'll do

• Run discovery on custom work with our founders. Ask the questions that find the real problem, and shape what gets built around the outcome, not the request.
• Own the developers' week: priorities, assignments, review, unblocking. Our CTO sets technical direction and takes the hard problems. You run the board.
• Turn what the client needs into a brief and checklist the developers can build from, with no gaps left for them to fill in on their own.
• Be the client's point of contact through delivery. Our developers don't meet clients. You do.
• Hold the line on scope. When a request doesn't serve the goal, you say \"that's not what we set out to solve\" to the client, and to a developer who's about to build it anyway.
• Review the work against the ask and the goal. Catch drift early. Bring real problems to our CTO before they reach the client.
• Own technical onboarding from day one: access, credentials, and how the client's business actually works.
• Know where every project stands: integrations, testing, what launch needs. When scope changes, you go back to the client with what it means.

What this role isn't

• It isn't a developer job. You won't write production code. You need to understand what it does, how the pieces fit, and when something's wrong.
• It isn't project management that passes messages along. If you relay what the client said without judging it against the goal, things get built wrong.
• It isn't sales. Our founders price and close. You make sure what was sold gets built right, and that nothing gets built that wasn't.

You'll do well here if

• You've managed developers, or led a technical delivery team, and been the one accountable when it landed or didn't.
• You have hands-on development in your past, and you can sketch how a system works (where the data comes from, where it lives, who can see it) and explain it to a developer and to a client.
• You think in business outcomes. You can look at a feature request and say what problem it solves, or that it doesn't solve one.
• You write clearly. A developer can act on your brief without calling you, and a client can read your update without a call either.
• You're comfortable telling a client \"that's a change\" or \"that won't get you what you want,\" and keeping the relationship.

How you work

• You'd rather find the real problem than build exactly what was asked for.
• You stay steady when a client is frustrated, and you don't pass the stress on to the developers.
• You'll tell a developer, or a founder, \"that's not what the client needs,\" and keep it about the work.
• You ask before you assume. If something hasn't been confirmed, you confirm it before anyone builds it.
• You make decisions in writing. Most of your calls should be readable by someone who wasn't in the room.
• You use AI tools every day to move faster: drafting, summarizing, reading code. You check what they give you, and the judgment is always yours.

This probably isn't for you if

• You want to code most of the day.
• You want a large company with a project office and set process. We're building ours, and you'll help shape it.
• You need a detailed brief before you start. Clients usually don't arrive with one.
• You'd rather keep a client happy today than tell them something they don't want to hear.

Tools we use

You don't need to be an expert in all of these, but you should be fluent in most and quick with the rest.

• Slack is where the company runs. Decisions, client updates, and developer questions all live there.
• AI coding assistants every day. Claude Code, Cursor or similar is how our developers build, and how you'll check their work: point it at a repo and ask \"does this do what the brief says?\" or \"where does this page get its data?\", then judge the answer. If you've set up an MCP connector or a CLAUDE.md, say so.
• Our build stack: