I build custom internal AI tools for teams with a specific problem — not a six-month digital transformation. The first version is working in three or four weeks, with your real documentation and your people using it.
I designed and programmed everything here myself, working solo and learning along the way. These are real systems in production, not prototypes or mockups.
A private audio channel platform for organisations and universities. A custom backend with real database-level data isolation, audio upload and processing, granular access control, and infrastructure in Germany.
A portal where my clients track their project: versioned documents, a decision history and an AI chat that answers only from their own documents — and says it doesn’t know when it doesn’t know.
Nineteen pages, bilingual, with forms, analytics and GDPR compliance. Built and deployed in two weeks.
A year ago I didn’t know how to code. I explain that in About , because it’s exactly why I can build something for you in four weeks instead of six months.
Every system documented to the same standard: architecture decisions recorded before they’re built, never after.
These are the kinds of projects that work best with me. If yours looks like one of them, I can probably help. If not, tell me anyway and I’ll be honest about whether I’m the right person.
If you’re not sure which of these is your case, that is exactly the first conversation.
Manuals, procedures, pricing, technical datasheets. It answers with the source in front of it and admits when it doesn’t have the answer.
Where they can see their project, documents and progress, without email chains.
The one somebody does by hand every week and everybody hates.
When you’ve spent months getting by with an Excel file nobody understands anymore.
Reports, announcements or classes turned into private audio, only for the people who should hear it.
To show it, test it and decide whether it’s worth pursuing before spending real money.
Explore → Understand → Build → Ship → Measure. It’s the same cycle I use in my own products and in every engagement. There’s no handoff between the person who thinks through the problem and the person who writes the code — that’s why a pilot takes weeks, not months.
01 ·
You tell me about the problem. I tell you whether it can be solved, what that solution might look like and roughly how much it would cost. If I don’t think I’m the right person, I tell you then and there.
02 ·
I build the smallest version that genuinely solves the problem, using your real documentation and with two or three people using it. Fixed scope and fixed price from the start.
03 ·
If it works, I stay: maintenance, adjustments and improvements. If it doesn’t, we stop and there is no lock-in.
A pilot starts from €3,000, depending on scope. Ongoing maintenance starts from €200/month.
I don’t charge by the hour or for consulting sessions. I charge for the thing I build, with a fixed price agreed before we start.
I’ve spent 20 years teaching innovation and strategy, and 25 in marketing and digital transformation. A year ago I decided to stop recommending tools and start building them. Since then, I’ve put two of my own systems into production.
LowOrbits is my company: I build AI software for others and for myself.
More about me →Half an hour, no obligation and no sales presentation. If I can see a way to build it, I’ll tell you how and how much. If not, I’ll tell you what I would look for in your place.