Accepting Q3 engagements COO / CTO-level advisory, without the headcount
Boutique Advisory · Business Operations Recovery

Order out of chaos.

I help founders, owners, and operators get control of launches, systems, vendor relationships, and operations that are late, over budget, or quietly bleeding money across retail, e-commerce, wholesale, and services.

The status reports look fine. The team is busy. The tools are full of activity. But leadership has a quiet, growing sense that something is off. My job is to figure out what is wrong, fast, and turn it into decisions you can actually make.

Background COO / CTO
Specialty Finding what's wrong
First call Within 72h

A project can have tickets, charts, meetings, and reports, and still be broken. More admin is not the answer. Someone needs to step back and ask the hard questions.

Crump & Co. · On the problem with project management theater
01 · The Problem

The danger is organized-looking chaos.

The tools say the project is on track. The team is working hard. Status reports get sent. And yet leadership still has a quiet, growing sense that something is wrong. Here is the gap, and what fills it.

What management tools track

Motion, not direction.

  • Tasks completed without proving business progress.
  • Gantt charts that hide bad assumptions.
  • Project boards that show effort, not outcomes.
  • Status meetings where everyone avoids the hard decision.
  • Vendor updates that sound reasonable, but create no real accountability.
What recovery asks

Truth, then decisions.

  • Is this project still worth doing?
  • What is the real blocker, not the stated one?
  • Who owns the next decision, and by when?
  • Which assumptions are quietly wrong?
  • What must change this week to restore control?
02 · The Approach

I'm strong at one specific thing: finding where things are quietly going wrong.

David Alan Crump
David Alan Crump Founder

Most consultants run a process. I look for the pattern.

My background spans operations, technology, and consulting across startups, retail, e-commerce, wholesale, and services, online and offline. That breadth matters more than it sounds. The same five or six failure modes show up in radically different industries, and I know what they look like from the inside before they ever appear in a status report.

I don't sit on top of your team and ask for more dashboards. I sit alongside leadership, vendors, and operators, listen for what isn't being said, and pull the underlying problem into the open. Then we make a real decision about it.

The value isn't another layer of reporting. It's getting to the truth fast, simplifying the decision set, and getting the project moving again, or stopped, if that's the right answer.

What I bring into the room
  • Pattern recognition from operating across industries, not from theory or templates.
  • Translation across owners, technical teams, vendors, finance, and operators without losing the practical thread.
  • Calm assessment when the team is reactive, defensive, or politically stuck.
  • Clear prioritization: what matters now, what waits, what should stop entirely.
  • Recovery plans that get acted on in days, not after six more weeks of planning.
03 · Where I Help

Six places projects quietly go off the rails.

The industries change. The failure modes don't. These are the patterns I see most often across retail, e-commerce, wholesale, services, and operations.

01

Tool blindness

Teams manage tickets and updates, but no one is asking whether the work is still aimed at the right business outcome.

02

Founder bottlenecks

Every important decision still depends on one overloaded person, so the team waits, guesses, or fragments.

03

Stalled launches

Product, location, service, or campaign launches that should have shipped months ago and now feel like they're moving sideways.

04

System rollouts

POS, CRM, ERP, e-commerce replatforms, websites, integrations that are behind schedule, under-defined, or poorly owned.

05

Vendor breakdowns

Outside providers are not delivering, but replacing them may create more damage than fixing the relationship.

06

Growth choking

The business is scaling, but the scale is creating breakage faster than results. Operations can't keep up with what was sold.

04 · Recovery in Practice

What it looks like when a project gets unstuck.

Three recent engagements. Different industries, same underlying patterns. Numbers and details have been anonymized where needed.

Case 01
Lorem ipsum dolor · sit amet consectetur
Outcome Lorem ipsum Dolor sit amet

The Situation

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.

What I Found

Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim.

The Decision

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto.

"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."

Lorem Ipsum
Placeholder testimonial
Case 02
Lorem ipsum · consectetur · adipiscing elit
Outcome Lorem ipsum Dolor sit amet

The Situation

Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est.

What I Found

Qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem.

The Decision

Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur. Quis autem vel eum iure reprehenderit.

"Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua."

Lorem Ipsum
Placeholder testimonial
Case 03
Lorem ipsum · dolor sit · amet consectetur
Outcome Lorem ipsum Dolor sit amet

The Situation

At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate.

What I Found

Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus.

The Decision

Temporibus autem quibusdam et aut officiis debitis aut rerum necessitatibus saepe eveniet ut et voluptates repudiandae sint et molestiae non recusandae.

"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis aute irure dolor in reprehenderit in voluptate velit."

Lorem Ipsum
Placeholder testimonial
Placeholder content. Replace with real anonymized engagements before public launch.
05 · How I Think

The first thing recovery changes is how the project is seen.

Most stalled projects don't suffer from a lack of activity. They suffer from a gap between what's being said in status reports and what's actually true. A typical excerpt from a Truth Map, the diagnostic document I deliver in week one:

Truth Map · Day 6 · Project Recovery Diagnostic Excerpt / 3 of 12

What the status reports said

"We're 80% done."
"The vendor is unresponsive."
"We just need two more sprints."
"Everyone is busy with this project."
"Q3 launch is still realistic."

What the audit actually found

50% done on a scope that has grown 40% since signing.
The vendor is responding to an incomplete spec.
Two of the next four sprints have unresolved dependencies.
Three people are doing 80% of the work. The rest are blocked, not busy.
Q3 launch is realistic only if three decisions are made this week.

The point of a Truth Map isn't to embarrass anyone. It's to give leadership the same picture the work has actually been showing for months, so a real decision can finally be made.

Crump & Co. · Document 02
06 · The Process

From noise to decisions, in five steps.

A focused process to replace confusion with facts, priorities, decisions, and accountable next steps.

i

Triage

Identify what is broken, what is unclear, who owns what, and where the project is bleeding time, money, or trust.

ii

Truth map

Create a clear view of timeline, budget, vendor status, dependencies, risks, assumptions, and missing decisions.

iii

Options

Give leadership practical choices: continue, pause, narrow scope, replace vendor, rebuild plan, or stop.

iv

Control

Install weekly accountability, decision logs, vendor commitments, and visible progress tracking.

v

Stabilize

Move the project from crisis mode into a manageable operating rhythm with fewer surprises.

07 · Diagnostic Tool

Take the project's pulse before you book anything.

A short checklist for projects that look organized in the tools, but still don't feel under control.

Use it to decide whether the project just needs better management, a serious review, a recovery audit, or a direct intervention.

No email required.

Crump & Co. · Document 01

Project Recovery Checklist

Status reports sound acceptable, but confidence is dropping.
Vendors give updates but not measurable commitments.
The dashboard looks organized, but the outcome is not closer.
Leadership needs a continue / pause / narrow / stop decision.
Every important decision still depends on one overloaded person.
The same risks have appeared on the last three status updates.
08 · Engagements

Four ways to start.

Start with clarity. Expand only if the project is worth saving, and there is a real mandate to fix it.

Free Inquiry

Step 00
Free/ written reply

Send a short note about what's stuck. I'll tell you whether a paid call makes sense — and if I don't think I can help, I'll say so.

  • No payment, no long sales process
  • Honest read on whether we're a fit
  • Where possible, a referral if I'm not
  • Reply usually within 72 hours
Send inquiry

Triage Call

Step 01
$500/ 30 min
Money-back if we decide we're not a fit in the first 15 minutes

A focused first conversation where we look at what is really going on, whether I can help, and what needs attention first.

  • 30-minute working call (not a sales call)
  • Same-day one-page risk snapshot
  • Immediate next-step recommendation
  • No follow-up sales pressure
Book triage

Fractional Advisor

Step 03 · Ongoing
$8,500/ month

Ongoing oversight to stabilize the project and keep leadership, vendors, and teams accountable.

  • Weekly recovery meetings
  • Vendor accountability framework
  • Decision and risk tracking
  • Direct leadership reporting
Ask about oversight
09 · Free Inquiry

Not sure if you need a paid call yet?

Send a short note first.

I'll look at what you write and tell you whether a project recovery call makes sense. If I don't think I can help, I'll say so. Where possible, I'll suggest who might.

  • No payment for the inquiry.
  • No long sales process.
  • If I do not think I can help, I will say so.
  • Reply within 2 business days.

I'll read your note and reply if a recovery conversation makes sense.

10 · Fit

Good fit / bad fit.

This works best when leadership wants the truth more than comfort.

Good fit

This will work for you if

  • You're founder-led or owner-led with messy growth.
  • You have a launch, system rollout, vendor relationship, or operations project that's gone sideways.
  • Leadership suspects the status reports aren't telling the full story.
  • There is real authority to change scope, vendors, budget, priorities, or decisions.
  • You'd rather know the truth than be reassured.
Bad fit

This won't work if

  • The project only needs a scheduler or administrator.
  • Leadership wants reassurance, not diagnosis.
  • No one is willing to make hard decisions.
  • The goal is to assign blame instead of fix the project.
  • You need someone to write or debug code. That's not where I'm strongest.
11 · Questions

Things people ask before the first call.

No. In most cases, the project manager is still useful. I work above or beside the project structure to see what the current process isn't showing.

Retail, e-commerce, wholesale, and services, online and offline. The industry matters less than the project shape. If it's a launch, a system, a vendor relationship, or an operational rollout that's gone sideways, the underlying patterns are usually similar.

I have a CTO-level background and can speak the language of technical teams and vendors fluently, but I'm not the right person to write or debug code. I'm the person who tells you whether the technical work is aimed at the right business outcome, and where the vendor relationship is breaking down.

If there's a fit, the next step is usually the 10-day recovery audit. The goal is a clear diagnosis before committing to ongoing work, not a 90-day proposal.

Then you should know that quickly. Recovery doesn't always mean forcing a bad project forward. Sometimes the best recovery is narrowing, pausing, or stopping, before more money is lost.

A first call usually happens within 72 hours of inquiry. An audit can typically start within 7 to 10 days, depending on stakeholder availability.

Before you spend more, get a clear view of the problem.

If the status reports stopped matching the reality on the ground, start by seeing whether a recovery call makes sense.