For software companies and implementation partners
Your customers are asking for AI in the product. Your team knows exactly what should happen — and never gets to it, because the roadmap is full.
Why it keeps getting postponed
At software companies it is rarely a matter of skill. Your team usually knows exactly what should happen — there simply is no week in which the sprint stops to find out. Client work and the roadmap win every time, and rightly so: those are sold.
What happens instead is a Friday afternoon demo that impresses and then dies, because nobody can carry it to production. The problem is not the idea but the ownership: as long as it comes on top of something else, there is no owner.
That is what I come for. One to three days a week embedded, in your stack and workflow, working out the most promising idea into something that runs on your data — with your developers, not next to them.
Sound familiar?
Customers ask for AI functionality, but there is no room in the planning to work it out properly.
There has been internal experimentation, but it stayed a demo that never reached production.
You know your team could work faster with AI, but nobody has time to figure that out mid-sprint.
What I do about it
01
Proof of concepts for new features
I build the most promising feature ideas into something that works with your data, so you decide on the roadmap based on a working thing.
02
Making your own team faster
AI-assisted development in your own workflow and stack — not as a workshop, but hands-on, so it sticks after I leave.
03
Internal tooling that gives time back
The repetitive parts around development, support and onboarding where time always disappears.
I build things myself. You do not get a report with recommendations, you get something that runs.
Three things that started this way
Different problems, the same route: from idea to something you can click open.
A twin that answers your questions
Twinnio
You set it up once; after that it speaks in your voice, knows your answers, and is there at the moments you are not.
twinnio.coWhat goes unsaid
Lytmus
Meeting intelligence: analyses sentiment and team dynamics in conversations and surfaces what happens between the lines.
lytm.usProposals as a story
Propositio
Build proposals from draggable blocks instead of a price list, with AI assistance, time tracking against the quoted lines, and analytics on what the recipient actually reads.
proposit.ioWhat your team will notice
Embedded work costs you time. That is the intention — this is what to count on.
- One fixed contact who can make decisions, with a conversation every one or two weeks about continuing, adjusting or stopping.
- Regular contact with the developers and with the people who will use it. Without that you build something technically correct that nobody opens.
- Working in your own stack and workflow, so what is left does not depend on me once I leave.
- The code is yours. No IP claim, no licensing construction.
When I am not the right person
Three situations where someone else serves you better.
- The feature is already specified and approved. Then you need building capacity — hiring a developer is faster and cheaper.
- You are looking for someone to maintain and support what already runs. I build new things.
- It has to be production-ready straight away, with every edge case and an SLA. A proof of concept first proves that investment is worth making.
the sprint never stops by itself →
A working proof of concept — or that phase costs you nothing
And you can stop at any decision point — no obligations
What people ask about this
- Do you work in our own codebase?
- I prefer to build the proof of concept in an isolated environment of my own, so we do not get stuck on internal policy while we are still finding out whether something works. As soon as it proves its value it moves to your side — in your stack, with your developers involved.
- What does it cost, and is there a minimum?
- € 150 per hour on eight-hour days. Two days a week for three months comes to € 28,800 excluding VAT. No minimum: you can stop monthly, and hours worked are simply invoiced.
- How soon is something working?
- A working first version is usually there within a week. The more complex the problem, the longer it takes — but the premise is that you see something run within weeks instead of reading a report.
in closing
Want to see if this fits?
No sales pitch. One conversation to find out whether there is something worth building — and if there is not, I will say so.
€ 150 per hour · 1 to 3 days a week · you can stop at any time