Agents Makers
Capability of Client Delivery CoordinatorDefault at launch

Project Intake

Scopes new engagements against the intake checklist.

  • Activation complexity

    Medium

  • Time to activate

    10-14 days

  • Volume share

    25-35% of role volume

  • Impact range

    50-65% faster

Inherited pricing

€1.00 – €3.50 per Project event handled

This capability inherits the Client Delivery Coordinator's pricing model. The role's launch fee + monthly retainer + role-level usage cover every capability under the role. Adding this capability to an active deployment does not change the price.

What this capability handles

How it works in detail.

Project Intake is the front door of every engagement, and a sloppy front door costs the whole delivery team. For services, SaaS, subscription, marketplace, and eCommerce operators between 100 and 1000 employees, the failure pattern is familiar: scopes drift, assumptions go unwritten, and the delivery lead spends the week chasing what was actually promised. This capability gives that lead a scoped, consistent brief on every new request, so coordination starts clean instead of catching up. It is built for delivery leaders who own engagement quality and cannot afford intake to be the bottleneck. It works by walking a fixed sequence. First it reads new engagement requests, whether they arrive from sales, the CRM, or a direct client ask. Then it checks each request against your documented intake checklist. Next it drafts a scoped brief, pulling on engagement records, the sales handoff, prior scopes, and the checklist itself. It then flags assumptions and gaps so nothing is silently assumed. Finally it surfaces the brief to the delivery lead. It runs inside your existing project tool, CRM, document store, and messaging, so the output lands where the team already coordinates. What it produces per request is one structured brief with assumptions and open gaps made explicit. The decision logic is deliberately disciplined. It applies intake-checklist logic, precedent-matching rules, and scope-ambiguity thresholds to decide whether to auto-scope a clean request, flag a gap, or route to the lead. The conservative path is the default: scope ambiguity, a net-new engagement type, or a client-commitment flag goes to the delivery lead for review rather than being resolved on its own. That keeps commitments to clients under human control. Every action is logged and reviewable, so any brief can be traced back to the request and the checks behind it. Typical fit is straightforward: the intake checklist is documented, the CRM-to-project handoff is current, and the precedent-scope library is accessible. Because every new engagement passes through intake, it carries 25-35% of the role's volume, and 30-40% of the role's impact comes from intake-cycle compression with scope discipline. On its primary measure, the engagement-intake cycle, this capability targets 50-65% faster.

Workflow summary

Reads request, runs checklist, drafts brief, surfaces gaps.

Stages

  1. 01read
  2. 02check
  3. 03draft
  4. 04flag
  5. 05surface

Decision logic

Uses intake-checklist logic, precedent-matching rules, and scope-ambiguity thresholds to auto-scope, flag-gap, or route-to-lead.

Systems and data

{"project tool",CRM,"document store",messaging}

{"engagement records","sales handoff","prior scopes","intake checklist"}

Exceptions & human handoff

Scope ambiguity, client-commitment-sensitive asks, or net-new engagement types route to the delivery lead for review.

Scope ambiguity, net-new engagement type, or client-commitment flag.

Readiness

Intake checklist documented, CRM-to-project handoff current, precedent-scope library accessible.

Owner on client side · Head of Client Services

Impact contribution

30-40% of role impact is intake-cycle compression with scope discipline.

Primary KPI · Engagement-intake cycle · 50-65% faster

When this capability shows up

Real-shape scenarios.

Patterns where project intake is part of the launch set, with volume and pricing anchored to each company profile.

  • Mid-market services firm with project-tool backbone

    Services · 200-500

    500 / mo

    A 300-person services firm runs 500 project events a month across intake, staffing, and reporting. Scopes drift between sales and delivery. Staffing conflicts surface in standup not in planning.

    Client Delivery Coordinator activates intake and resource allocation. Scopes land with disciplined checklists; staffing proposals surface with conflicts pre-flagged; delivery leads shift time to client-sensitive calls.

    Expected outcomes at this volume: engagement-intake cycle down 50-65%, staffing lead time 50-70% faster, delivery-lead hours recovered weekly.

    Monthly cost

    €500€1.8k

    vs human anchor

    €2.9k€9.9k

    Savings

    03%

  • Professional-services arm of a SaaS business with tight milestone rhythm

    SaaS · 300-800

    1,200 / mo

    The professional-services arm of a 600-person SaaS business runs 1200 events a month across implementations. Client reports lag milestones. Time entries miss the invoicing window. Utilization reporting is always a week stale.

    Client Delivery Coordinator activates all four capabilities. Intake runs disciplined; staffing lands on time; client reports ship on cadence; time-tracking nudges and approvals clear the invoicing window.

    Expected outcomes: cycle-time reduction 50-65%, client-report on-time rate above 95%, time-entry compliance rising, invoicing window held.

    Monthly cost

    €1.2k€4.2k

    vs human anchor

    €7.1k€23k

    Savings

    03%

  • Small digital agency juggling retainer and project work

    Services · 20-80

    200 / mo

    A 40-person digital agency runs 200 project events a month across retainer clients and new builds. Intake scopes drift between sales and delivery. Weekly client reports get assembled by hand in slide decks the night before.

    Client Delivery Coordinator activates project intake and client reporting. Scopes land with disciplined checklists; weekly client reports ship on cadence against milestones; delivery leads move time to client-sensitive calls.

    Expected outcomes at this volume: engagement-intake cycle down 50-65%, client-report on-time rate above 95%, delivery-lead hours recovered weekly.

    Monthly cost

    €200€700

    vs human anchor

    €1.3k€4.1k

    Savings

    03%

  • Upper-mid consultancy with shared resource pool and tight utilization target

    Services · 500-1000

    2,000 / mo

    An 800-person consultancy runs 2000 project events a month across twelve practices sharing a single resource pool. Staffing conflicts surface late. Time-entry compliance swings with the week. Utilization reports are always a cycle behind.

    Client Delivery Coordinator activates all four capabilities. Intake runs disciplined; staffing proposals surface with conflicts pre-flagged against the shared pool; client reports ship on cadence; time-tracking nudges and approvals clear the invoicing window.

    Expected outcomes: cycle-time reduction 50-65%, staffing lead time 50-70% faster, time-entry compliance rising, utilization reporting current to the week.

    Monthly cost

    €2.0k€7.0k

    vs human anchor

    €12k€39k

    Savings

    03%

All scenarios and cost ranges come from the Client Delivery Coordinator role page.

Capability-specific integrations

Additional systems for Project Intake.

Beyond the Client Delivery Coordinator's base stack, this capability plugs into:

More Client Delivery Coordinator capabilities

Last reviewed

Activate Project Intake as part of a Client Delivery Coordinator deployment.

Your free Agent Opportunity Audit opens with Client Delivery Coordinator and Project Intake pre-selected. We map the fit and the cost against the equivalent hire, with no obligation.