Comparison between traditional consulting with PowerPoint stacks and modern AI-native workspace with live code

Build > Advise: How We Deliver in 4 Weeks What Others Present in 4 Months

30. März 20264 min read

TL;DR: „Traditional consulting sells recommendations. We sell working systems. In 4 weeks. No PowerPoint."

— Till Freitag

The Problem with Recommendations

I've been on both sides. As a consultant who wrote decks. And as a builder who inherited the results of those decks. And I can tell you: the gap between recommendation and implementation is the most expensive place in consulting.

A typical consulting project looks like this:

Phase	Duration	Output
Discovery & Stakeholder Interviews	4–6 weeks	Interview summaries
Analysis & Benchmarking	6–8 weeks	Market comparisons, frameworks
Strategy Development	4–6 weeks	The Big Deck™
Presentation & Alignment	2–4 weeks	Workshops, feedback loops
Total	16–24 weeks	A PDF and open questions

Then what? The real work begins. Implementation. With a different team. With different budget. With different priorities. Months after kick-off, the market has changed and the deck is outdated.

Our Counter-Model: 4 Weeks, Working Code

At Till Freitag, there's no strategy deck. Not because we can't think strategically – but because we consider it disrespectful to keep clients waiting for months before anything tangible exists.

Our 4-week rhythm:

Week 1: Understand & Decide

No discovery marathon. One day onsite or remote. We ask the right questions, prioritize together, and define a clear scope. By end of day one, we know what will be live in three weeks.

No 80-page requirements document. A Miro board with clear swim lanes.

Weeks 2–3: Build

This is where we do what traditional consultants consider "out of scope": we build. With AI-native development. With Vibe Coding. With tools like Lovable, Cursor, and Claude.

An MVP that doesn't "theoretically work" but that a real user can test. Not a prototype as in a Figma click dummy – a working system with a real backend, real data, real workflows.

Week 4: Iterate & Hand Over

Incorporate feedback. Smooth the edges. Documentation. Handover. Not as a 200-page PDF, but as a working system with clean code and clear architecture.

The result after 4 weeks: a system that runs. Not a recommendation gathering dust in a drawer.

Why This Is Possible Now

This model wasn't feasible two years ago. What makes it possible is the AI-native stack:

Claude & Cursor for code generation that delivers senior-level quality
Lovable for full-stack apps in hours instead of weeks
Supabase for backend infrastructure without a DevOps team
React & Vercel for production-ready deployments

The combination of these tools means: what previously required a 6-person team over 3 months, we accomplish with two people in 4 weeks. Not because we're smarter, but because the tools have gotten exponentially better.

The Uncomfortable Truth About Consulting

Let's drop the politeness:

Traditional consulting has an incentive problem. The longer the project, the higher the revenue. The more complex the recommendation, the longer the project. The more intangible the deliverable, the harder it is to measure.

This isn't an accusation against the people in the industry – it's a structural critique of the model. A model that rewards prolonging problems rather than solving them.

We flip that:

Traditional Consulting	Build > Advise
Success = long projects	Success = fast results
Deliverable = deck	Deliverable = working code
Team = junior consultants	Team = senior builders
Measurement = client satisfaction (survey)	Measurement = system works (yes/no)
Lock-in = dependency	Ownership = your code, your system

What This Means for Clients

You Own Your Code

Everything we build belongs to you. No vendor lock-in. No subscription model for support. Clean code in a Git repository your team can continue developing.

You Pay for Results

Our projects have a fixed scope and a fixed price. No surprises in month three. No "change requests" that double the budget.

You Save Months

4 weeks instead of 4 months. That's not just time saved – it's a strategic advantage. You're faster to market, get feedback faster, iterate faster.

When Build > Advise Doesn't Fit

Honesty is part of the deal: this model isn't for everyone.

It doesn't fit if you need a 500-page compliance document. If 17 stakeholders need to approve before a single line of code is written. If the organization isn't ready to make decisions in days rather than months.

It fits perfectly if you actually want to build something. If you know the problem is real. If you're ready to take a working system as a starting point and improve iteratively.

The Next Step

If you've read this far and think "this sounds like what we need" – let's talk. Not in a 90-minute sales call with a demo deck, but in an honest 30-minute conversation.

We'll tell you what we can build for you in 4 weeks. And if it doesn't fit, we'll say that too.

→ Get in touch