Consultations One session or regular meetings on your question: an answer in plain words and a short written summary.
Decide well before you spend.
An independent second opinion on technology, code and AI – before you commit the budget. The report is yours, whoever builds next.
The report is yours – hand it to any team. Every finding in it comes with evidence you can check.
What we do
Five ways to work with us.
Architecture and technology A written decision with the reasons: what to build, what to buy, and on what.
Code and product audits A report with a "fix / keep / don't build" list ranked by risk, and a walkthrough call.
AI strategy Where AI pays off in your processes, ranked by impact and effort, with a step-by-step plan.
Project lead A part-time technical lead from kickoff to handover, with your team or outside vendors.
Where the advice comes from
- Our own money on the lineTechnical co-founder of Koru.Farm – we make these decisions ourselves.
- Systems under real loadAn AI advisor for energy trading; a player lobby and back office for a major games supplier.
- Not a rubber stampIf you need a decision you've already made confirmed, the report may disappoint you.
- Not a penetration testFor that, we'll point you to security specialists.
Questions
Before you call.
How is a consultation different from an audit?
A consultation answers your question in one or a few meetings. An audit is work on the code or the product that ends in a written report. If a consultation shows you need an audit, we'll tell you.
Isn't this a trap to sell us the build?
No. The report is yours to give to any team. If you don't need to build, that's what we'll write.
I'm not technical. Will I understand the report?
Yes. The first part is written for the business owner – risks and decisions in plain words. The technical detail goes in an appendix for your team.
What if I disagree with the findings?
Every finding has evidence behind it – we can check it together and correct it if we got it wrong.
Do you need access to our code and passwords?
For an audit – read-only access to the code, under NDA. We don't need passwords to your live systems.
How long does it take?
It depends on the size of the product and the question. We give you the timeline after the first conversation, once it's clear what needs checking.
What are you building next?
You talk to Roman, the founder. Free, and if we're not the right fit, we'll say so.