Leaders want AI to work by next Tuesday. Most teams need to get three foundations right first — and none of them are on the conference slides. A pilot demo convinced someone. Six months later the use-case is still stranded between works on a laptop and runs cleanly in production, and nobody on the team owns the gap in between. This atlas describes six situations where closing that gap is the job.
You probably said one of these this week.
- "The prototype is cool. How do we get it into the product?"
- "We have an agent. Nobody knows how to test it."
- "The business wants it yesterday. Our stack wants it next quarter."
- "We pay five figures to a vendor and can't say exactly what for."
- "The team is strong. They've been shipping around LLMs for six months, not with them."
- "The demo landed. The compliance review didn't."
A ChatGPT wrapper shipped and nobody uses it. Management wants AI in the product by Q3 and hasn't said what problem it solves. Vendor demos keep promising the same three things. What's actually missing is the bridge — from AI is capable to AI delivers measurable value inside your product, on your codebase, maintained by your team. The bridge is engineering, not a platform.
Your developers build the product that pays the bills. They don't have ten hours a week to read about vector databases, agent frameworks, or Computation Expressions. So the gap widens: the tools move, the team holds the fort. What you need is not a replacement team — you need know-how transfer into the team you already have, so your product carries your team's fingerprints, not a consultant's.
You've seen the offshore model. You've seen the staffing agency. You end up managing more contracts than code. Quality is a lottery. The knowledge leaves with the contract. In-house stays. Boost is brought in. Software craftsmanship is not an arbitrage play. Pair-program with senior help for a quarter, keep the result forever.
You paid. Everyone was inspired. There was a deck. Then normal gravity resumed and you were back where you started — minus a budget line. A useful engagement ends with something your team owns: an architectural decision they can defend, a tooling chain they can rerun, a piece of code they wrote with help and now maintain alone. Not a certificate. Not slide 42.
Automated tests on a cold project don't revive it. Coverage dashboards are a green light on a dead engine. Unit tests around broken architecture preserve the breakage. When a project has fallen in the well, ropes from above are the answer — not more metrics. The pragmatic question is always the same: does this change produce value now, or over time? If neither — cut it.
The Agile Manifesto was seventeen developers saying one thing: trust motivated people and let understanding emerge from the work. The industry that grew on top of it sells the opposite — rigid ceremonies, certified process police, velocity dashboards, frameworks stamped onto teams that don't fit them. Consulting for agility. Not for the Agile Industrial Complex.
Five engagement shapes. Outcomes, not deliverables.
AI Adoption Review
For product teams that know AI belongs in the roadmap but aren't sure where. Output: a shortlist of AI moves that fit your product, your stack, your team — with effort and risk estimates you can defend in the next board meeting.
In-House Upskilling Sprints
Leaves your own developers able to ship the next thing without outside help. Pair-programming, reviews, dedicated spikes around a real problem — not a workshop deck. Delivered on your codebase, with your people.
Architecture Second Opinion
A neutral read of where your system is heading. You get a written argument — what's working, what's decaying, what moves next — plus a conversation with a senior voice who is neither selling a replatform nor defending the status quo.
Pragmatic Delivery Review
For teams stuck in ceremony theater. Identify the two or three practices that actually produce value. Recommend what to drop — starting from the Agile Manifesto, not the framework textbook.
Hands-on Engineering
When the problem is nested — AI plus functional architecture plus DSL plus developer tooling — a tool-hire makes sense. Take on the build, pair with your team, hand it back fully documented.
Artefacts, not testimonials.
Things already built and shipped — shown, not claimed. Evidence is public and dated.
Recognized F# Expert
F# Software Foundation — Applied F# 2019. Public peer recognition, no self-declared title.
Foundation →FsHttp
Invited by Don Syme (creator of F#) to the official fsprojects organization. 499 stars, 128 dependent packages.
Repo →TypeFighter
A research language with structural types and inference-first design. Source and write-up in the open.
Repo →PXL Clock
A 24×24 programmable LED display shipping via Cumin & Potato GmbH. Real hardware, real firmware, real customers.
Site →BobKonf 2024
Computation Expressions in F# — full tutorial track at a recognized functional-programming conference.
Talk →Community
Recurring features in F# Weekly (Sergey Tihon, Microsoft MVP). Co-host at Amplifying F# — community format with G-Research OSS.
GitHub →What you're probably asking right now.
Sounds expensive.
Less than hiring a senior full-time. Scoped explicitly; no retainer trap.
Can you do this remotely?
DACH and remote EU, both supported. Onsite workshops possible for team-facing engagements.
We already have an agency.
An agency builds more capacity. I make your existing team capable. Different job.
We don't use F#.
Good — most client work is C#/.NET, TypeScript, and the mix everyone actually has. F# is how I think; it's not a prerequisite.
We only need help for two weeks.
Then you don't need me. I'm interested in engagements that leave something standing after I'm gone.
Why me for this problem.
Ronald Schlenker — fifteen years in .NET, creator of FsHttp, TypeFighter, and several other OSS libraries the F# community uses. Recognized F# Expert (F# Foundation, 2019). Co-founder of the PXL Clock — a programmable hardware product that is itself a working example of pragmatic engineering: small team, in-house discipline, shipped without a framework textbook.
The reason this page is written the way it is: every time I see a dying software project, it died the same way — buzzword compliance replacing engineering judgement. The consulting I sell is the opposite of that. Based in Frankfurt. Work with DACH and remote-EU teams. Trading as PureState IT Consulting.
- .NET / C# / F#
- Python
- LLM Engineering
- Agents
- RAG
- Evals
- DevOps
- Azure / AWS
Let's talk through your situation.
One email is enough. A reply lands within one working day.
Start a conversation View GitHub