CPI Software Engineering Consultancy Vol. 01 · 2026

We engineer the critical path.

Every system has one — the longest sequence of dependent decisions that determines whether you ship. We help you find it, then walk it with you.

“The longest path determines the schedule.” Kelley & Walker, 1959

Fig. 01 The shape of a sound engagement — five surfaces on one path, with shorter routes for partial scopes
T₀ wk 2 wk 4 wk 6 wk 8 wk 10 Tₙ brief-only build-only B brief 01 consult 02 lead 03 build 04 ship 05 extend D deliver critical path — full engagement slack — partial scope
  1. B brief
  2. 01 consult
  3. 02 lead
  4. 03 build
  5. 04 ship
  6. 05 extend
  7. D deliver
§ 01 Manifesto

In project management, the critical path is the longest sequence of dependent tasks — the one that decides whether a project ships.

Miss any of those tasks and the whole thing slips. Critical Path Initiative was founded to find that sequence inside engineering organizations and walk it alongside the people who own it.

We work with founders, CTOs, and engineering leaders who can feel a slip happening but cannot quite point to where the slack vanished. We start there. We read the codebase, sit in the standups, talk to the senior engineers — and then we tell you the truth about what we find.

Slack is harder to see than dependency. We look for both.

Then we either hand the report back, or we stay until the path is walked. Engagements are short by default and extend by mutual choice.

§ 02 Nodes on the Path

Five surfaces of engagement. Each one a node — pickable on its own, more useful in sequence.

  1. 01 T-01

    Engineering Consultation

    Embedded review of architecture, delivery, and team velocity. We map your current path, identify the bottleneck, and recommend the smallest set of changes that move it.

    Inputs
    codebase access · leadership interviews · recent retros
    Outputs
    written diagnosis · prioritized recommendations · optional follow-through
    Duration
    2–6 weeks
  2. 02 T-02

    Engineering Leadership Coaching

    One-on-one and team coaching for engineering managers, staff engineers, and founders moving into technical leadership. Frameworks where they help — but mostly judgment.

    Format
    1:1 sessions (60–90 min, biweekly) · staff cohorts · leadership offsites
    Themes
    delegation · technical credibility · running standups that matter · saying no
    Duration
    quarterly engagements, renewable
  3. 03 T-03

    Application Development

    Net-new builds, complete rebuilds, and rescues of stalled internal tools. We bring senior engineering and the discipline to scope it correctly the first time.

    Stack
    chosen for the work, not the résumé — typed, tested, boring where it can be
    Cadence
    two-week sprints, demoed work weekly, no surprises
    Duration
    8 weeks–6 months
  4. 04 T-04

    Web Construction

    Marketing sites, landing pages, and content systems. Fast, hand-tuned, accessible by default. No template bloat. No tracking soup.

    Tooling
    static-first when possible · headless CMS when needed
    Performance
    sub-second median first-paint or we redo the build
    Duration
    3–10 weeks
  5. 05 T-05

    Specialized Engineering

    If your problem doesn't fit a column above — DevEx, infrastructure, refactors, integrations, post-mortems, mentorship — open a brief. Most of our best work has lived here.

    Examples
    pipeline rescues · platform consolidations · org-wide RFC processes
    Approach
    scoped to the specific shape of the problem
    Duration
    variable — defined in the brief
§ 03 Method

How a path gets walked. Five phases — the same shape every time; the work inside is yours.

  1. P-01

    Triage

    Read the codebase. Listen to the team. Observe a release. Withhold opinions for a beat longer than is comfortable.

  2. P-02

    Diagnose

    Map the work as a graph. Find the longest dependent chain. Name what isn't being said.

  3. P-03

    Sequence

    Identify the critical path — and the slack you didn't know you had. Decide what to keep, drop, and reorder.

  4. P-04

    Walk

    Implement, advise, ship. Pace by mutual decision. Adjust the plan when the plan stops being true.

  5. P-05

    Hand-off

    Document what we learned. Train whoever owns it next. Step out cleanly. The work belongs to your team.

§ 04 Coordinates

Channels,
forthcoming.

Critical Path Initiative is currently provisioning its public coordinates. Direct contact details — email, calendar, intake — will appear here shortly.

Check back, or expect them to find you if a path crosses.

⤷ Filed § 04.a · provisional · updating soon