LaprasBuild your professional AI operating system
Tailored to you and your team. A system that knows your work, goals, responsibilities, and priorities.
What this means for you
One AI system. Built around how you work.
Not a chatbot. Not a template. A system designed around your workflows, your tools, and the way you actually work.
What AI can do for your business
Apply it to every part of your business.
One system, applied wherever you spend time. Each domain compounds with the others because the context is shared.
These are common starting points. Your version can grow to include any domain that matters to you.
Inside your existing tool stack. Not on top of it.
Clients
Working with founders, operators, and teams.
Mallorca to Stockholm, and beyond. Solopreneurs to scale-ups. Across tech, interior, media, gaming, design, and film.
How it works
A sprint, or an ongoing engagement.
Every engagement starts with understanding your business. From there, two shapes typically fit: a focused sprint if you’re a solopreneur or small business, or a team engagement if you’re a larger team across multiple functions.
Sprint
Your own AI system, configured and running.
- 1Discovery session to map your workflows and tools
- 22–3 hands-on setup sessions to build your system
- 3Review session to fine-tune and hand off
3–4 sessions over ~2 weeks
Team engagement
Ongoing collaboration, scoped together.
- 1Kickoff workshop with the team
- 2Weekly sessions across the domains that matter
- 3Continuous prep between sessions
- 4Iteration as your needs evolve
Weekly rhythm, ongoing
You leave with the system, and the skills to keep building it.
Built on Claude & Copilot
What’s included
What you get from me.
Whether sprint or team engagement, the offer is the same shape. What scales is how deep we go and how many people are in it.
Architecture
The technical foundation (repos, context, integrations, security) plus the strategic focus on where AI gives your business the biggest lift.
Onboarding
I teach you how to think about the system and work with it, tailored to each person. Hundreds of hours of trial-and-error compressed into a pragmatic flow, so you don't have to learn the hard way.
Roadmap, with ready tasks
Built session by session. Between sessions I push tasks into your system, preloaded with context, ready for Claude to execute when you approve. You always know what to work on next.
About
From building companies to building AI systems.
Johan Stubert
AI Implementation Expert
I started at BCG in management consulting and spent the last decade building and scaling tech companies across logistics, e-commerce, healthcare, and energy. I've always been obsessed with operational efficiency and building systems that scale.
Everything I teach, I run on myself first. My own business sits on this exact system: connected tools, daily briefings, pipeline tracking, memory that compounds. Every workshop, every engagement, I pass on what I use every day.
I help you build your own AI system. You drive, I steer.
FAQ
Common questions
What do you actually deliver?
A working AI system and the skills to keep building it. The system runs inside your existing tools from day one: drafts in your voice, briefings before your day starts, pipeline that updates itself. The skills come from building it together, side-by-side, so you can take over after.
Who do you work with?
Solopreneurs, small businesses, and larger teams. So far: design, media, film, climate, wellness, gaming, finance. The common thread is real operations that benefit from AI thinking with you, not for you.
How long does a typical engagement take?
Two shapes: a focused sprint (3-4 sessions over 2-3 weeks) for solopreneurs and small businesses, or an ongoing team engagement (weekly rhythm) for larger teams. We scope which one fits in our first conversation.
What about data and privacy?
Your files stay on your machine. Nothing is uploaded, nothing trained on. Claude drafts in chat, it never sends or shares without your sign-off. Your instructions, your tenant, your rules.
Do I need to be technical?
No. The shape adapts: I drive more of the technical setup for non-technical operators, you drive more if you're a builder. Either way, the goal is the same: by the end you can keep building it yourself.
What happens after the engagement?
You own the system, the workflows, the context, every file. Nothing is locked behind my access. Most people keep building on their own. An optional retainer is available if you want me to stay involved.