Contact

How can we help?

Tell us what you want to evaluate, see or implement. We aim to reply within two business days in Japan (excluding weekends and Japanese public holidays), in English or Japanese.

  • Evaluate independently

    Download Kurahi and follow the evaluation path on your own machine: install, configure a model, run a sample workflow and verify its evidence. No sales contact is needed, and the Free plan has no time limit.

    Go to the evaluation path
  • See a workflow demonstration

    A workflow demonstrated on a process like yours, with fictional data, and a conversation about the systems involved and who approves what.

    hello@kodasoken.com

    Workflow demonstration
  • Get help implementing a workflow

    Help choosing the first workflow, connecting your systems, setting approvals and autonomy, and training approvers and reviewers. Quotations for Enterprise and enterprise evaluations too.

    partners@kodasoken.com

    Implementation help

Please do not include passwords, confidential source code, or sensitive personal data.

Send an enquiry

Tell us what you want to evaluate, see or implement. We aim to reply within two business days in Japan (excluding weekends and Japanese public holidays), in English or Japanese.

Please do not include passwords, confidential source code, or sensitive personal data.

When you submit this form, KODA SōKEN stores your name, email, optional company, enquiry, chosen intent, language and consent record in Supabase. Vercel processes the submission. A salted hash of your IP address helps prevent abuse; the enquiry database does not store the raw IP. These details are used to answer your enquiry, not for marketing. Contact hello@kodasoken.com to request deletion. Privacy notice

You can also email hello@kodasoken.com. JavaScript is needed to send this form. hello@kodasoken.com

Is Kurahi a good fit?

A good first workflow is easy to recognise. Some situations need a closer look before we start.

A good place to start

  • Work that recurs every day or week, such as invoices, requests or inquiries
  • Source information Kurahi can read: a mailbox, a SaaS system, a file share or source code
  • Named people who review and decide
  • A result someone can check: a case, a draft, a document

Worth assessing together first

  • Systems without a Kurahi connector
  • Approval ownership that is not yet clear
  • Specialised document formats
  • Expectations that high-risk decisions run unattended; Kurahi leaves those to a person

From first conversation to running agents

  1. Conversation

    We learn the work, the systems involved and who approves what.

  2. Demo

    Kurahi on a process like yours, with fictional data.

  3. Evaluation

    One workflow on your own infrastructure, measured against criteria you agree.

  4. Rollout

    Training for approvers and reviewers, and the level of autonomy you choose.