“Every morning I was burning hours browsing freelance platforms and writing tailored applications before I could touch billable work. Cortension set up an agent that knows my portfolio, filters for real fit, and drafts proposals the client wants to read. I got my mornings back and my win rate went up.”
What our clients say
“Cortension helped us run AI entirely on our own infrastructure. Local models, fine tuned for our use case, no data leaving the building. Full control, full compliance.”
“Cortension set me up with Hermes Agent and it completely changed how I work. It remembers my projects across sessions, auto generates skills the more I use it, and I can reach it from Telegram, Slack, wherever I am. One coaching session and the thing just runs.”
“With Claude Code and one cloud provider, Cortension helped us replace everything. Calendly, Shopify, analytics, email automation. All of it, built and owned by us. No more monthly fees stacking up, no more depending on tools that can change their pricing overnight.”
“Cortension showed me how to use Claude Code to build my own website, set up fully automated cold email outreach, and get everything running. I went from paying for a dozen SaaS tools every month to handling it all myself. No Calendly, no Mailchimp, no Webflow. Just Claude Code and one cloud account.”
Meet the Founder
Benito Exner
Founder & CEO
Cloud DevOps Engineer turned Agentic AI specialist. I built Cortension because I saw teams struggling with tools that should be making them faster.
Sound Familiar?
Claude Is Strong. The Right Implementation Is Not Obvious.
A ticket, a repository, a handover, a website, a content workflow, or an internal process do not all need the same setup. The real decision is what belongs in a Skill, a script, a tool connection, a project rule, memory, or a simpler workflow.
Repeated Work Should Not Stay Repeated
If Claude has to do something again and again, the behavior should often become a Skill, command, script, or project rule. That is how work becomes easier to repeat instead of being explained from scratch every time.
You Should Not Have to Test Every New Trick Yourself
Claude Code, Claude Desktop, Skills, MCP, memory, browser use, hooks, scripts, plugins, and new models keep changing. We stay close to what is actually useful so you do not waste your time wiring in things that do not help your case.
What We Actually Do in a Session
Whether you are just starting, already have a concrete task, or want to improve your existing setup: we meet you where you are. We help you set the tool up sensibly, understand current best practices, and avoid unnecessary detours.
We Find Your Best Starting Point
You do not need to bring a perfect task. If you have one, we use it. If not, we look at your work, your tooling, and your goals, then choose the first useful use case.
We Do Not Just Set It Up. We Explain Why.
Installation alone is not the value. We show you which decisions matter: model, Skills, scripts, tool access, project rules, memory, review steps, and what you can leave out at the beginning.
We Bring Current Expert Knowledge
We know the new patterns, plugins, Skills, MCP servers, memory approaches, provider options, and common mistakes. You do not have to test everything yourself to get a good start.
We Build or Improve Your Real Setup
Fresh installation, existing setup, concrete task, or review of your workflow. We work directly on your case, not on a generic tutorial.
After One Session, You Know What Makes Sense and What You Can Skip
We set up, check, explain, and test as much as is realistically useful in 60 minutes. Afterwards, you know better which parts of your AI setup really matter and which ones you can ignore for now.
One Session. Real Progress.
Flat rate, no surprises.
Claude Setup Session
1 hour · Remote · 1 on 1
€149 per session
- Questionnaire before the session and a plan built around you
- Live hands on setup for 60 minutes
- One real task or workflow as the base
- Claude Code, Claude Desktop, Skills, scripts, tool access, or project rules where useful
- Custom instructions, commands, checks, or setup notes for your project
- Session recording and written action plan
- 30 day follow up by email
- Discount for 3 or more sessions
Frequently Asked Questions
What people ask before booking their first Claude setup session.
Do you help with Claude Desktop, Claude Code, or both?
Both. We treat it as one Claude setup around your work. Claude Desktop includes Code powered by Claude Code, and Claude Code can also be used from the terminal or IDE. We help you understand what belongs in chat, what belongs in Code, what needs a Skill, script, MCP connection, memory, or review step.
Are you just teaching prompt tips?
No. Prompting is only a small part. The real value is the setup around Claude: project rules, Skills, scripts, tool access, memory, permissions, and review steps. We show you what makes sense, set it up with you, and explain how to keep using it.
What should I bring to the session?
Bring one real thing you want Claude to help with: repeated work, a ticket flow, a writing task, research, a code project, documentation, handovers, or a tool setup that feels confusing. We use that as the base instead of showing random features.
What do you actually set up?
The useful parts only. That can mean Claude Desktop, Claude Code, project instructions, Skills, scripts, MCP or extensions, memory, permissions, review steps, or a simpler workflow. Not everything needs automation. Not everything needs a Skill. We show you the right path.
Can this replace tools I currently pay for?
Sometimes. Some subscriptions can be replaced with self-built, open source, or cloud based solutions that you control. We first look at what the tool actually does for you, then decide what should stay, what can be replaced, and where replacing it would add more complexity than value.
Do I need to be technical?
No. The session is as technical as your goal requires. If you bring a business workflow, we stay close to the workflow. If you bring a codebase or tool setup, we can go deeper into commands, files, MCP, and review.
What do I leave with?
A working Claude setup around your real work, written notes, a recording, and clear next steps. You leave knowing when to use chat, when to use Code, when to create a Skill or script, and where a human review step should stay.
What if Claude is not the right tool for my task?
Then we say that. Sometimes Claude is right. Sometimes ChatGPT, Codex, OpenCode, a local model, a script, or classic automation fits better. The point is not to force Claude everywhere. The point is to build the setup that actually helps.
Make Claude Useful for the Work You Actually Repeat.
Bring one task that should become faster, cleaner, or easier to repeat. We show you whether it should become a Skill, script, tool connection, project rule, or something simpler, and set it up with you.
Keep Up. Without the Noise.
New tools, skills, and breaking changes drop faster than anyone can keep up with. We cut through it and send you what actually matters, when it matters. No hype, no fluff. Subscribe now and get our free guide: 16 Best Practices for Agentic AI.
Something went wrong. Please try again.
Almost there. Check your inbox for a confirmation link and your free guide. (Check spam if you don't see it.)
No spam. Unsubscribe anytime.