companies running our systems in production
months of development behind Wikilook Evo
countries we are based in
years building software, half of it from Tokyo
AI Workshop
Pick the format that fits your week. The shortest takes two to three hours.
see the programme ↗see the programme ↗MINI · intro · 2–3 hours
The intro format, next up in Kyjov. Claude is installed beforehand from our guide, so the whole two hours are hands-on.
STANDARD · half day · 4 hours
Inbox, invoices and the family budget. Six hands-on blocks with a 10-minute break, each with a clear “done when” check.
FULL · whole day · 8 hours
A master skill for free content. One whole day, one organized system.
The problem
Mailbox to spreadsheet, spreadsheet to the ERP, ERP back to a confirmation e-mail. Every step is a chance to get a digit wrong.
Four years of quotes, contracts and technical notes live in shared drives. New staff ask a colleague instead, and the colleague stops doing their own job.
Licences renew, two people use them. Nobody wrote down what the tool was supposed to replace, so nobody can say whether it worked.
None of this needs a platform. It needs someone to sit with the people who do it, measure it, and remove the parts a machine can do on its own.
What we do
Custom development. We measure the process that costs you the most time, then build the system that removes it — frontend, backend, integrations — and hand over the source.
One day, six people, your own data on the table. We teach the skills that make your people self-sufficient developers of their own automations, not slide audiences.
Rent the harness we build everything on: scaffolding, evaluations, approval gates, audit logging — upgraded continuously, running on your own keys and infrastructure.
The tooling
Every workflow above runs on Wikilook Evo, our own scaffolding and test harness. It exists because the same three problems appeared in every project: nobody could reproduce a prompt change, nobody could prove a workflow still worked after a model update, and nobody could see what the thing did last Tuesday. Wikilook Evo ships with your project, not as a subscription.
One command lays down the queue, the connectors, the approval gate, the log and the deployment config. We spend the project on your process instead of on infrastructure.
Your real failing cases become the evaluation set. Change a prompt or a model and Wikilook Evo replays them, then shows exactly which cases moved and in which direction.
Input, label, confidence, prompt version, draft, human edit and sender are written for every run. A wrong output is a record you can read, not a mystery.
Model-agnostic adapters, your own accounts, self-hosted or in your cloud. Wikilook Evo is handed over with the source at the end of the build — there is no WIKILOOK login anywhere in it.
Info live on the Wikilook Evo page.
open the Evo page ↗open the Evo page ↗Who leads it
Fifteen years building software for the largest enterprises in Tokyo, and fifteen in my own research on web and data semantics.
We run WIKILOOK's own operation on the same workflows we sell. The e-mail triage, the quote drafts, the internal knowledge search — all of it is in production here first, which is the only honest way to recommend it to anybody else.
After 15 years in Tokyo, most of my work is now with Czech & Slovak companies in need of automation: accounting, legal, manufacturing, professional services, e-commerce. The pattern repeats. The bottleneck is almost never the model, it is that nobody wrote down what the process actually does.
We would rather deliver one automation that survives a year than five that need us forever. That is why the handover includes the source in repo (e.g. GitHub) and why the 30-day review period is granted free.
Where and how
NOW PLANNED: 16 Oct · 17:00–19:00
Kyjov · City Library, tř. Komenského 617, 697 01 Kyjov
FORMAT: MINI · Intro · 2–3 hours (Claude installed beforehand, per our guides.)
Workshop in Czech or English; questions in Slovak are welcome.
Run in Czech or English.
Photos: Prague and Vienna CC0 · Bratislava CC BY-SA 4.0, Ekaterina Polischuk / Wikimedia Commons
Questions / FAQ
AI CONSULTING: No. We need the person who actually does the process, and someone who can grant access to the systems it touches. If you have an IT partner we work with them directly on access and handover.
AI WORKSHOP & CONSULTING: Into your own accounts with the model provider, under your contract, with training on your data switched off. We list every processor in writing before anything is connected. If data cannot leave your building at all, say so on the introductory call — the answer is a local model and a different budget.
AI WORKSHOP & CONSULTING: Workshop: the same day, on a small process. Agent build: typically four to six weeks from the first call, of which two are ours and the rest is access, testing and your people's time.
AI CONSULTING: Not in the projects we take. The engagements that work remove hours from people who are already overloaded. If the goal is headcount reduction, we are the wrong supplier and we will say so on the introductory call.
AI WORKSHOP & CONSULTING: All three. Workshops run in Slovak or Czech by default, in English on request, and mixed rooms are common; we adapt to whatever the room prefers. Documentation, prompts and runbooks are delivered in any of the three.
Contact us
companies running our systems in production
months of development behind Wikilook Evo
countries we are based in
years building software, half of it from Tokyo
AI Workshop
Pick the format that fits your week. The shortest takes two to three hours.
see the programme ↗see the programme ↗MINI · intro · 2–3 hours
The intro format, next up in Kyjov. Claude is installed beforehand from our guide, so the whole two hours are hands-on.
STANDARD · half day · 4 hours
Inbox, invoices and the family budget. Six hands-on blocks with a 10-minute break, each with a clear “done when” check.
FULL · whole day · 8 hours
A master skill for free content. One whole day, one organized system.
The problem
Mailbox to spreadsheet, spreadsheet to the ERP, ERP back to a confirmation e-mail. Every step is a chance to get a digit wrong.
Four years of quotes, contracts and technical notes live in shared drives. New staff ask a colleague instead, and the colleague stops doing their own job.
Licences renew, two people use them. Nobody wrote down what the tool was supposed to replace, so nobody can say whether it worked.
None of this needs a platform. It needs someone to sit with the people who do it, measure it, and remove the parts a machine can do on its own.
What we do
Custom development. We measure the process that costs you the most time, then build the system that removes it — frontend, backend, integrations — and hand over the source.
One day, six people, your own data on the table. We teach the skills that make your people self-sufficient developers of their own automations, not slide audiences.
Rent the harness we build everything on: scaffolding, evaluations, approval gates, audit logging — upgraded continuously, running on your own keys and infrastructure.
The tooling
Every workflow above runs on Wikilook Evo, our own scaffolding and test harness. It exists because the same three problems appeared in every project: nobody could reproduce a prompt change, nobody could prove a workflow still worked after a model update, and nobody could see what the thing did last Tuesday. Wikilook Evo ships with your project, not as a subscription.
One command lays down the queue, the connectors, the approval gate, the log and the deployment config. We spend the project on your process instead of on infrastructure.
Your real failing cases become the evaluation set. Change a prompt or a model and Wikilook Evo replays them, then shows exactly which cases moved and in which direction.
Input, label, confidence, prompt version, draft, human edit and sender are written for every run. A wrong output is a record you can read, not a mystery.
Model-agnostic adapters, your own accounts, self-hosted or in your cloud. Wikilook Evo is handed over with the source at the end of the build — there is no WIKILOOK login anywhere in it.
Info live on the Wikilook Evo page.
open the Evo page ↗open the Evo page ↗Who leads it
Fifteen years building software for the largest enterprises in Tokyo, and fifteen in my own research on web and data semantics.
We run WIKILOOK's own operation on the same workflows we sell. The e-mail triage, the quote drafts, the internal knowledge search — all of it is in production here first, which is the only honest way to recommend it to anybody else.
After 15 years in Tokyo, most of my work is now with Czech & Slovak companies in need of automation: accounting, legal, manufacturing, professional services, e-commerce. The pattern repeats. The bottleneck is almost never the model, it is that nobody wrote down what the process actually does.
We would rather deliver one automation that survives a year than five that need us forever. That is why the handover includes the source in repo (e.g. GitHub) and why the 30-day review period is granted free.
Where and how
NOW PLANNED: 16 Oct · 17:00–19:00
Kyjov · City Library, tř. Komenského 617, 697 01 Kyjov
FORMAT: MINI · Intro · 2–3 hours (Claude installed beforehand, per our guides.)
Workshop in Czech or English; questions in Slovak are welcome.
Run in Czech or English.
Photos: Prague and Vienna CC0 · Bratislava CC BY-SA 4.0, Ekaterina Polischuk / Wikimedia Commons
Questions / FAQ
AI CONSULTING: No. We need the person who actually does the process, and someone who can grant access to the systems it touches. If you have an IT partner we work with them directly on access and handover.
AI WORKSHOP & CONSULTING: Into your own accounts with the model provider, under your contract, with training on your data switched off. We list every processor in writing before anything is connected. If data cannot leave your building at all, say so on the introductory call — the answer is a local model and a different budget.
AI WORKSHOP & CONSULTING: Workshop: the same day, on a small process. Agent build: typically four to six weeks from the first call, of which two are ours and the rest is access, testing and your people's time.
AI CONSULTING: Not in the projects we take. The engagements that work remove hours from people who are already overloaded. If the goal is headcount reduction, we are the wrong supplier and we will say so on the introductory call.
AI WORKSHOP & CONSULTING: All three. Workshops run in Slovak or Czech by default, in English on request, and mixed rooms are common; we adapt to whatever the room prefers. Documentation, prompts and runbooks are delivered in any of the three.
Contact us