01
Tool blindness
Teams manage tickets and updates, but no one is asking whether the work is still aimed at the right business outcome.
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.
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.
David Alan Crump · 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
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.
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 engagements. Different industries, same underlying patterns. Client names withheld, numbers rounded.
The Situation
The platform had a strong concept, live-streamed real-time bidding on cars, antiques, art, and collectibles, and twenty-eight people working on it. From the outside, it looked like a funded startup hitting its stride: full dev team, in-house legal, marketing spend, management layers. From the inside, the owner was self-funding a roughly $1M annual burn with no path to break-even that anyone had actually calculated. They were celebrating individual high-ticket sales while the unit economics quietly said the business needed a hundred of those sales a month just to stand still.
What I Found
The company was spending for the appearance of a serious business, not the function of one. A full-time senior corporate attorney for a company that needed legal advice a few times a year. Managers supervising teams of two. Sales staff who weren't selling. Roughly $1.5M and twenty-four months already invested in a custom platform, when the business model behind it had never been pressure-tested. Spending that nobody was reviewing closely. And the most important number, how many sales a month it would take to be profitable, had never been put in front of the owner in a form he couldn't ignore.
The Decision
I built the unit economics in plain numbers on one page: at the current cost structure, the platform needed roughly a hundred high-ticket sales a month to break even. They were doing a handful. The recommendation was an 80% reduction in fixed cost across staffing, legal, and management overhead, and a narrowing of categories to where the platform actually had traction. The owner pushed back on every line. Eventually the math became undeniable. The money drains were stopped within two months, and the business reached profitability within six.
Organized-looking chaos. Every function looked busy and professional. None of it was tied to the one number that decided whether the business survived.
The pattern
The Situation
A nonprofit publisher with a loyal paying audience and a stack that had grown one tool at a time: the newsletter on a rented platform, the store and memberships on WordPress, a new publishing system on Ghost, and email broadcasts through a marketing platform. Each piece worked on its own. Readers juggled separate logins, and the organization didn't control the platform its audience actually lived on.
What I Found
The real exposure wasn't any single tool. It was the seams between them, and the fact that the audience relationship sat on someone else's platform. Every handoff between tools was a place where a login, a payment, or a subscriber could fall through, and no vendor was watching those handoffs.
The Decision
Move the publication onto infrastructure the organization owns. Migrate the newsletter to self-hosted Ghost, connect store and publication logins with single sign-on, tie paid membership tiers to the payment processor, and send each new article to the email list automatically the moment it publishes. Then design for failure: primary and secondary DNS, a failover server, and separate providers for transactional and bulk email, so no single vendor outage or policy change can take the publication offline. All of it documented in a full handoff guide.
Vendor breakdowns don't always look like vendor breakdowns. Nothing was broken on any single platform. The risk lived between them, where no vendor was responsible.
The pattern
The Situation
The founders wanted a Netflix-style home for independent film: pay-per-view premieres, subscriptions and rentals, global streaming, native apps for phones and smart TVs, anti-piracy protection, AI-driven discovery, and a "watch and earn" rewards currency. A strong vision with a long list, and a real question underneath it: build custom from day one, or launch faster on proven tools?
What I Found
The vision mixed launch features and year-two features in one list. Native apps, multi-DRM, and AI discovery are real costs that don't prove anything until there's an audience to protect and recommend to. The rewards idea carried a hidden risk too: any "earn while you watch" system gets farmed by bots and idle tabs unless it's designed against that from the start.
The Decision
Split the roadmap into a launch tier and a wishlist tier, with milestones at months 2, 5, and 9 so investors could see exactly what ships when. Go with a proven platform for the MVP instead of a custom build, and cost delivery with a Philippines-based team at roughly 71% below US rates. For the rewards currency, set a fixed exchange value and build in four separate anti-farming protections.
Stalled launches usually start as scope. The fastest way to ship was deciding, in writing, what wouldn't be in version one.
The pattern
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."
"The launch date 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.
The launch date 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.
David Alan Crump · 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.
David Alan Crump · 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 00Free/ written reply
Send a short note about what's stuck. I'll tell you whether a paid call makes sense. 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 within 24 hours
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
10-Day Recovery Audit
Step 02 · Most-fit$5,000/ engagement
A deeper diagnosis when a project is stuck between stakeholders, vendors, or its own scope.
- Stakeholder & vendor interviews
- Full timeline & budget review
- Truth Map & 30/60/90-day recovery plan
- Clear continue / pause / restructure recommendation
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
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 24 hours.
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.