Shinsa
Shinsa is for people with a good idea but without the technical background to build it – and for everyone whose AI-generated project has stopped working. First we tell you honestly whether it is worth it. Only then do we talk about building it.
Developed and delivered by ABC Systematik
Why Shinsa exists
Ever since I started working as an application developer, I keep hearing the same sentence: “I had an AI build me something – and now I am stuck.”
Tools that program on request are remarkably good at delivering something that works at first glance. They are just as good at inventing things: functions that do not exist, libraries that never existed, security checks that only look like they check something. Anyone who can program notices. Anyone who cannot notices when it is too late – when customer data is sitting open on the internet, when the hosting bill arrives, or when one small change brings the whole building down.
I do not know this from hearsay. Before I became a developer I was on the other side myself: an idea in my head, no craft behind it, so I let the machine build it. For a while it went remarkably well. Then I was looking at code I did not understand, with errors I could not find, and nobody to ask. Giving up was the easiest way out. That is exactly what I want to spare other people.
The annoying part: these projects often rest on genuinely good ideas. People who saw a real problem and did something about it instead of waiting for someone else. They do not fail because of the idea, they fail because of the foundation.
That is what Shinsa is for. A place to go for everyone with an idea who does not know whether it holds up – and for everyone whose project is against the wall. We say what the situation is, even when the answer is uncomfortable. And what we build is built so that you can still touch it in two years without holding your breath.
Alexander Barwig · Application developer, owner of ABC Systematik
Who it is for
You know exactly what your product should do – but nobody can tell you whether it can be built and whether the effort is in a sensible relation to the benefit. That is what we clarify first, before money goes into building anything.
Tools that program on request like to invent: functions that do not exist, libraries that never existed, security checks that are only called that. If you cannot program yourself, you have no chance of finding this – all you see is that it does not work.
We look inside and tell you whether repairing is worth it or whether a clean restart is cheaper in the end.
The two options
Both options end with a written result that belongs to you – including when the answer is “not worth it”.
You describe what you have in mind. We review it and come back with a clear assessment – no jargon, no sales pitch.
You send us your project. We go through it and tell you what the problem is and what it costs to get it running again.
How it works
You describe your idea or your problem – using “Submit an idea” or by e-mail.
We get back to you, clarify what is open and name the price of the analysis.
You agree – only then does the work start, only then do costs arise.
We review it and write up the result in plain language.
Build it, cut it differently or drop it. You decide.
Once the work is finished or close to hand-over, you look at the result and tell us what should be changed. Two such rounds are included in every engagement. Coordination during the work itself does not count towards them – that is part of the job anyway. As long as it stays within reason, it costs nothing. If it turns into a permanent state of affairs, we will tell you beforehand – not afterwards on the invoice.
Any further round of revisions is charged separately. We name the cost in the quote.
What happens next
If the analysis is positive and you have a budget, we deliver the project as a regular engagement – with a quote and a fixed price. Source code and rights pass to you once the project agreement has been paid in full.
If there is no budget, Shinsa may in individual cases take on development in exchange for a stake in your project. Whether and on which terms is decided by ABC Systematik after its own review – there is no entitlement to it. All details are agreed in writing before a project starts.
Frequently asked
It stays yours. We do not use submitted ideas ourselves and we do not pass them on. If you like, we sign a confidentiality agreement beforehand – just say so before you send details.
Yes. You pay for the review, not for the desired outcome. A well-founded “not worth it” may save you many times the amount.
That cannot be said in advance – which is exactly why the analysis exists. Afterwards you receive a quote with a fixed price and a timeframe.
Yes. Describe in your own words what the result should do and for whom. The rest is our job. If something is missing, we ask.
In a regular engagement, you do. It is handed over once the project agreement has been paid in full. In the special case of a stake, the question is settled in writing beforehand.
Yes. The analysis fee depends on the scope, not on whether you ask privately or commercially.
Submit
A few sentences are enough to start. You will receive a reply within two to four business days – with questions and the price for the analysis, before anything is commissioned.
This website collects no data. There is no form, no sign-up and no tracking – your inquiry arrives by e-mail, and you decide what is in it.
