By Paul GosnellThe Consultant Pattern (And Why It Fails)
What You're Sold
"AI Strategy Consulting Package"
- Discovery workshops (2-3 weeks)
- AI readiness assessment
- Use case identification
- Technology recommendations
- Implementation roadmap (12-18 month plan)
- Cost: $15k-50k
What You Actually Get
- 50-page PowerPoint deck
- High-level recommendations (no working code)
- Roadmap you can't execute yourself
- Follow-up proposal ($200k+ for "implementation")
What You DON'T Get
- Working code
- Deployed product
- Validated solution
- Real user feedback
- Production-ready system
Why Consultants Don't Ship
Reason 1: Business Model Requires Recurring Work
The Consultant's Dilemma:
- If they solve your problem completely → you don't need them anymore
- If they provide advice (not solutions) → you need ongoing consulting
- Result: Incentivized to NOT ship final solutions
Example:
- Month 1: "We need to assess your AI readiness" ($20k)
- Month 3: "Here's your strategy roadmap" ($30k)
- Month 6: "Let's do a pilot study" ($40k)
- Month 9: "Implementation requires Phase 2 engagement" ($200k)
- Month 12: Still no working product, $290k spent
Reason 2: They're Not Builders
Consultant Background:
- MBA or strategy background (not engineering)
- Frameworks and presentations (not code)
- Research and analysis (not shipping products)
- Comfortable with ambiguity (not production systems)
Builder Background:
- Engineering or CS degree + 10-20 years shipping
- Working code (not slide decks)
- Launched products (1000+ in production)
- Comfortable with constraints (ship despite imperfect info)
Reason 3: Risk Averse (No Accountability)
Consultant Deliverable: Advice and recommendations
- If advice fails → "You didn't execute correctly"
- If advice works → "Our strategy was sound"
- No accountability for outcomes
Builder Deliverable: Working product
- Either works or doesn't (binary outcome)
- Full accountability for results
- Reputation tied to shipped products
The Real Cost of Consulting
Scenario: Startup Wants AI Chatbot for Customer Support
The Consultant Path ($290k, 12 months, no product)
| Phase | Timeline | Cost | Deliverable |
|---|---|---|---|
| Discovery | 4 weeks | $20k | Assessment report |
| Strategy | 6 weeks | $30k | Roadmap deck |
| Pilot Planning | 4 weeks | $25k | Pilot plan document |
| Vendor Selection | 8 weeks | $35k | Vendor comparison matrix |
| Phase 2 Proposal | 4 weeks | $20k | Implementation proposal |
| Implementation (quoted) | 24 weeks | $160k | Working product (maybe) |
| Total | 50 weeks | $290k | Lots of docs, no product |
The Builder Path ($30k, 4 weeks, working product)
| Phase | Timeline | Cost | Deliverable |
|---|---|---|---|
| MVP | 1 week | $7k | Working chatbot (basic) |
| Validation | 1 week | Included | Real user feedback |
| Production | 2 weeks | $23k | Production-ready system |
| Total | 4 weeks | $30k | Deployed, working product |
Savings: $260k, 46 weeks faster, actual working product
Red Flags: You're Dealing with a Consultant (Not a Builder)
Red Flag 1: Selling "Strategy" Before Solutions
Consultant says: "First, we need a 6-week discovery phase to understand your needs"
Builder says: "Let me build a quick MVP in 6 days so you can see if this works"
Red Flag 2: No Code in Deliverables
Consultant delivers: PowerPoint decks, PDFs, frameworks
Builder delivers: GitHub repo, deployed product, working demo
Red Flag 3: Vague Timeline ("12-18 Month Roadmap")
Consultant timeline: "Phase 1 is 3 months, then we'll assess Phase 2"
Builder timeline: "MVP in 6-8 days, production in 3-5 weeks"
Red Flag 4: Expensive "Assessment" Phase
Consultant: "We need $20k-50k just to assess if AI is right for you"
Builder: "Let's build a small MVP for $5k-10k and find out"
Red Flag 5: No Accountability for Outcomes
Consultant contract: "We'll provide recommendations based on best practices"
Builder contract: "I'll deliver a working product that handles X, Y, Z"
Red Flag 6: Endless "Phases"
Consultant: Phase 1 → Phase 2 → Phase 3 → Phase 4 (never ends)
Builder: MVP → Production (done, you own it)
When Consultants ARE Useful
Valid Use Cases for AI Consultants
1. Large Enterprise Strategy
- Multi-department AI transformation
- Organizational change management
- 100+ person team coordination
- Multi-year roadmaps with board buy-in
2. Compliance & Risk Assessment
- GDPR/CCPA compliance review
- AI ethics and bias auditing
- Regulatory compliance (healthcare, finance)
3. Expert Witness / Third-Party Validation
- Independent assessment for board/investors
- Technical due diligence (M&A)
- Expert testimony (legal cases)
When NOT to hire consultants:
- You need working software (not advice)
- You're a startup or SMB (too expensive, too slow)
- You want to move fast (consultants are slow)
- You need accountability for results
What to Do Instead: Hire Builders
Builder Characteristics
- Ships production code (not presentations)
- 10-20+ years building real products
- Portfolio of launched products (not case studies)
- Accountable for working deliverables
- Fast iteration (MVP in days, not months)
- Challenges and improves your brief
- Transparent pricing (fixed or clear hourly)
Questions to Ask Potential Builders
"Show me something you've built"
- Good answer: Live demo, GitHub link, production URL
- Bad answer: "I worked on a team that built..." (consultant red flag)
"How long to get a working MVP?"
- Good answer: "6-8 days for basic functionality"
- Bad answer: "We need 6 weeks for discovery first" (consultant red flag)
"What's your accountability if it doesn't work?"
- Good answer: "I'll fix it or refund you"
- Bad answer: "Results depend on your execution" (consultant red flag)
"What's the deliverable?"
- Good answer: "Working code, deployed to production, documentation"
- Bad answer: "Comprehensive strategy document" (consultant red flag)
The p0stman Approach: We Ship, Not Consult
What Makes Us Different
- We ship code, not PowerPoint decks
- MVP in 6-8 days, not 6-week discovery phases
- Production in 3-5 weeks, not 12-month roadmaps
- Accountable for results, not "best effort recommendations"
- 20+ years building, not consulting experience
- 1000+ products shipped, not case studies
Our Philosophy
"Your success is our portfolio"
- We only make money if we ship working products
- Reputation based on launched products (not presentations)
- Incentivized to solve problems (not extend engagement)
- Fast, accountable, transparent
Real Founder Stories
Story 1: The $180k Consulting Trap
Founder: Series A SaaS startup
Hired: Big-name AI consulting firm
Cost: $180k over 8 months
Outcome: 200-page strategy doc, vendor comparison matrix, implementation roadmap
Result: Still no working product, CTO quits out of frustration
What they should have done: Hired builder, shipped MVP in 3 weeks for $30k
Story 2: The Builder Alternative
Founder: E-commerce company
Hired: Experienced solo developer
Cost: $35k
Timeline: 4 weeks
Outcome: Working voice AI agent handling 100 calls/day
Result: $75k savings in Year 1, product launched, customers happy
Key Takeaways
- Consultants sell advice ($5k-50k for decks), builders ship code
- Consulting model requires recurring work, not one-time solutions
- Consultants aren't builders (MBA vs engineering backgrounds)
- Red flags: "strategy phase," no code deliverables, vague timelines
- Consultants useful for: Enterprise strategy, compliance, not product development
- For startups/SMBs: Hire builders who ship (faster, cheaper, accountable)
- Ask: "Show me something you built" - if no working code, it's a consultant
- Builder approach: MVP in days, production in weeks, working product guaranteed