Strategic technical guidance for founders and senior teams.
Architecture, security, AI strategy, and scaling from someone who has built and launched products from pre-seed to growth stage. Strategy for reality, not fantasy scale: preparing for chaos on your best day.
Advice from an engineer who has also run the business side: fundraising, financial models, and go-to-market at a VC-backed startup, so the technical call is weighed against runway and GTM.
AI & LLM Strategy
Where AI fits, RAG, verification, evals
Architecture for real scale
Ledgers, audit logs, multi-tenant isolation
Technical due diligence
Honest codebase and architecture assessment
Security audits & hardening
Adversarial review, auth, defense-in-depth
Advisory services.
Strategic guidance tailored to your stage. Past security reviews have surfaced real issues (account takeover, privilege escalation, rate-limiting gaps) with fixes that hold up.
AI & LLM Strategy
Clear thinking on where AI actually helps and where it does not. From opportunity identification to implementation, with the verification and guardrails that keep it trustworthy.
Ideal for:
Technical Strategy
CTO-level technical direction without a full-time hire. Direct guidance to your team on architecture, stack choices, and execution, weighed against runway and go-to-market.
Ideal for:
Technical Due Diligence
A senior read on a codebase and team before you invest, acquire, or commit. Architecture, security, and scalability, with a clear list of what to fix before you raise or scale. Runs as a fixed-scope audit, usually 1 to 2 weeks.
Ideal for:
The smallest way to start. From €2k.
A fixed-scope review of your codebase and architecture, usually 1 to 2 weeks. I find the risk early, then give you exactly what to fix, how to fix it, and in what order, plus a target architecture to build toward. It stands on its own, and it is often how a build or a rescue begins.
Adversarial by method
I go looking for the risk you cannot see from the inside: auth and access holes, data-isolation gaps, and the paths that break under load or concurrency.
Evidence, not opinions
Severity-ranked findings you can reproduce yourself, explained in plain terms for the founder and in technical detail for the dev.
A fix plan, not a teardown
For each finding: what to fix, how to fix it, and how much it matters, in priority order, plus a target architecture. The genuinely strong parts get verified too.
How advisory works.
Weekly calls, async, or project-based, whatever fits.
Discovery
30-min call to understand your challenges and goals.
Engagement
Choose weekly calls, async support, or project-based.
Value
Actionable guidance you can implement immediately.