How I Help Startups Scale: My Consulting Approach

After founding five technology companies and advising dozens more, I’ve developed a consulting approach that focuses on practical, actionable guidance rather than theoretical frameworks. This post explains how I work with startups, what makes my approach different, and how to determine if we’d be a good fit.

My Consulting Philosophy

I believe effective startup consulting requires someone who has been in the founder’s seat. Having built companies from zero to acquisition, navigated failed ventures, and invested in early-stage startups, I bring pattern recognition that comes only from direct experience.

The Problem with Traditional Consulting

Most startup consulting falls into two problematic categories:

Theoretical frameworks without execution experience: Consultants who have MBA training but haven’t actually built companies. They provide sophisticated frameworks that look great in presentations but fall apart when facing real constraints—limited runway, imperfect information, team dynamics, and market timing.

Generic advice that ignores context: One-size-fits-all guidance that doesn’t account for your specific situation. The advice that works for a well-funded Series B company is often wrong for a bootstrapped pre-seed startup. What works in enterprise SaaS doesn’t apply to consumer apps.

What I Bring to Engagements

Technical Depth: With a background in software engineering and architecture, I can dive into technical discussions about system design, API architecture, and technology stack decisions. This isn’t abstract advice—I’ve built production systems and understand the tradeoffs.

When a CTO explains their architecture, I can identify where it will break at scale. When a founder debates build vs. buy, I can share specific examples of both paths and their consequences. This technical credibility changes the nature of the advisory relationship.

Startup Operations Experience: From hiring first engineers to managing runway, from pivoting products to negotiating term sheets, I’ve navigated the operational challenges that founders face daily.

I’ve made the difficult decisions: shutting down a product that wasn’t working, letting go of team members who weren’t the right fit, accepting bridge financing on unfavorable terms, and walking away from acquisition offers that weren’t right. These experiences inform how I advise founders facing similar situations.

Ecosystem Connections: Through programs like the Startup Leadership Program and Westerwelle Foundation, I’ve built relationships across the global startup ecosystem that I leverage for my portfolio companies.

This means warm introductions to investors, connections to potential customers, and access to other founders who’ve solved similar problems. The value isn’t just advice—it’s network access that would otherwise take years to build.

Pattern Recognition: After 17+ years across multiple companies and many more advisory relationships, I’ve seen what works and what doesn’t across different contexts. This pattern recognition accelerates decision-making.

When a founder describes a challenge, I often recognize it from previous experience. Not the exact same situation, but similar enough that I can share relevant lessons and help avoid common mistakes.

How I Work With Startups

Strategic Advisory Relationships

For ongoing engagements, I typically work with founders through regular advisory relationships. These are structured partnerships, not one-off calls.

Typical Structure:

• Bi-weekly or monthly working sessions (60-90 minutes)
• Async access for urgent questions (Slack, email)
• Quarterly business reviews
• Ad-hoc calls for critical decisions

What We Cover:

Product Strategy: Validating product-market fit, prioritizing features, and planning roadmaps. This includes customer development methodology, how to interpret user feedback, when to stay the course vs. pivot, and how to balance vision with market feedback.

I help founders think through questions like: Are you building what customers say they want, or what they’ll actually pay for? How do you separate signal from noise in customer feedback? When is a feature request an opportunity vs. a distraction?

Technical Architecture: Reviewing system designs, identifying scalability concerns, and planning technical debt reduction. I can go deep on specific technology decisions while also zooming out to consider business implications.

Questions I help with: Should we build this ourselves or use a third-party service? How do we structure our system for the scale we’re planning? What technical debt should we prioritize? How do we balance speed with quality given our current stage?

Fundraising Preparation: Refining pitch narratives, preparing for due diligence, and making investor introductions. I’ve been on both sides—raising capital and evaluating investments—which provides useful perspective.

This includes: How do you structure your narrative for different investor types? What metrics do investors actually care about at your stage? How do you handle tough questions about competition, risk, or past failures? When should you accelerate or slow down your fundraising process?

Go-to-Market: Developing launch strategies, pricing models, and early customer acquisition approaches. Particularly for B2B and enterprise companies, I can help think through sales motions, channel strategy, and positioning.

We work through: Who is your ideal customer and how do you reach them? What’s the right pricing model and where should you start? Should you pursue product-led growth, sales-led growth, or a hybrid? How do you learn from early customers without over-fitting to their specific needs?

Focused Engagements

For specific challenges, I offer targeted consulting on discrete problems:

Technical Due Diligence for Investors: When VCs or angels are evaluating a technology investment, I assess the technical capabilities, team, architecture, and risks. This typically involves code review, team interviews, and a written assessment with investment recommendation.

Architecture Reviews: Before major scaling initiatives or technology migrations, I conduct deep dives into current architecture and provide recommendations for evolution. This is particularly valuable before significant fundraising or when technical debt is impeding velocity.

Fundraising Strategy: Concentrated engagement around preparing for and executing a fundraising round. This includes pitch refinement, narrative development, investor targeting, and process management.

Product Pivots and Strategic Repositioning: When startups need to make significant strategic changes, I help think through options, validate new directions, and execute transitions. This draws on experience with both successful pivots and ones that didn’t work.

My Methodology

The First Month

When beginning an advisory relationship, I focus the first month on deep understanding before offering significant guidance.

Week 1-2: Discovery

• Extended sessions with founders to understand history, vision, and current challenges
• Review of key documents: pitch deck, financials, product metrics, technical architecture
• Customer interviews or review of customer feedback
• Competitive analysis

Week 3-4: Synthesis and Initial Recommendations

• Prioritized assessment of challenges and opportunities
• Initial strategic recommendations with rationale
• Alignment on working relationship and focus areas
• 90-day plan with specific goals

Ongoing Engagement

After the initial month, ongoing advisory follows a rhythm:

Regular Working Sessions: Bi-weekly or monthly deep dives on priority topics. These are working sessions, not status updates—we actively problem-solve together.

Async Communication: Slack or email access for time-sensitive questions. Founders often face decisions that can’t wait for the next scheduled session.

Quarterly Reviews: Stepping back to assess overall progress, adjust priorities, and update our working focus.

Ad-Hoc Deep Dives: When major decisions arise—acquisition offers, funding decisions, key hires—we schedule additional sessions as needed.

What I Don’t Do

Being clear about scope is important:

I’m not a fractional executive: I advise and guide, but I don’t execute day-to-day. You need your own team to implement.

I’m not a recruiter: While I can advise on hiring strategy and evaluate candidates, I don’t source or screen talent.

I’m not an outsourced function: Advisory works best when founders and teams own the work. I accelerate their thinking, not replace it.

I don’t take on too many engagements: To provide meaningful value, I limit active advisory relationships. This means I’m sometimes unavailable for new engagements.

Areas of Expertise

AI and Machine Learning Implementation

Having advised companies like Leena.ai (now enterprise HR AI), founded Octo.ai (ML analytics), and worked with numerous AI-first startups, I understand how to practically deploy ML in products.

My AI/ML guidance covers:

• When to build vs. buy ML capabilities
• How to structure ML teams and infrastructure
• Practical approaches to data collection and labeling
• Model deployment and monitoring
• Avoiding common AI product mistakes

I’m particularly useful for startups adding AI capabilities (not pure AI research companies) who need to ship functional ML features without over-engineering.

Web3 and Blockchain Strategy

Through founding Boom Labs and advising multiple Web3 startups, I gained hands-on experience with multi-chain infrastructure, tokenomics, and Web3 go-to-market.

My Web3 guidance covers:

• When tokenization makes sense (and when it doesn’t)
• Chain selection and multi-chain strategy
• Smart contract architecture approaches
• Web3 go-to-market and community building
• Regulatory considerations and structuring

I’m most useful for Web3 startups that are building real products, not pure speculation or DeFi protocols.

Fintech and Financial Inclusion

My work with the Financial Inclusion Lab and advisory relationships with fintech startups shaped my understanding of technology for financial services.

My fintech guidance covers:

• Product design for underserved markets
• Regulatory navigation and compliance strategy
• Partnerships with financial institutions
• Unit economics of financial products
• Scaling financial technology responsibly

Enterprise Technology

From SaaS architecture to B2B sales motions, I’ve seen what works in enterprise:

My enterprise guidance covers:

• Product design for enterprise buyers
• Enterprise sales process and deal structure
• Security, compliance, and procurement navigation
• Expansion and account management strategy
• Pricing and packaging for enterprise

Who I Work Best With

I’m most effective with certain types of founders and companies:

Technical Founders

I work best with founders who have technical backgrounds or strong technical intuition. We can have substantive discussions about architecture, technology decisions, and engineering tradeoffs. My technical credibility adds value rather than creating translation overhead.

B2B and Infrastructure Companies

While I’ve worked with consumer companies, my deepest experience is in B2B SaaS, enterprise software, and infrastructure. The sales cycles, buyer psychology, and growth patterns in these areas are where my pattern recognition is strongest.

Early-Stage Startups

I’m most impactful at pre-seed through Series A, where strategic decisions have outsized impact and the right guidance can change trajectory. At later stages, companies typically need specialized functional expertise rather than generalist advisory.

Domain Match

Founders building in fintech, AI/ML, or Web3 benefit most from my domain expertise. I can speak substantively about the specific challenges and patterns in these areas.

Coachable Teams

I provide direct, sometimes uncomfortable feedback. Founders who want validation rather than challenge won’t enjoy working with me. The best engagements involve founders who value honest perspective and engage actively with feedback.

What Clients Say

The engagements I’m proudest of share common themes in founder feedback:

“You helped us avoid a major mistake”: Often the most valuable guidance is what not to do—technologies not to build, markets not to pursue, hires not to make.

“You connected us to the right people”: Introductions to investors, customers, and other founders that would have taken years to make independently.

“You pushed our thinking”: Challenging assumptions and forcing rigor that made our strategy better.

“You gave us confidence in our direction”: Sometimes founders need external validation that they’re on the right track.

How to Engage

If this resonates with how you work and what you need, let’s have an initial conversation.

Initial Call: 30-minute call to understand your situation and determine fit. No charge.

Trial Month: For ongoing advisory, we start with a trial month to ensure the relationship works before committing long-term.

Focused Projects: For specific engagements (due diligence, architecture review, etc.), we scope and price based on the specific need.

If you’re building something ambitious and looking for a startup consultant who combines technical depth with operational experience, I’d welcome a conversation about how I might help.

Get in touch to discuss your situation.