What do you actually need from our people?
We need two things from you: a little time with the people who do the work, and access to the work product your firm already trusts.
Through short interviews, we design the automation and turn that design into your Blueprint. You choose what to build from it. From there, the build is on us. Your approved forms, exemplars and finished work show us what good looks like, so the system learns your standards instead of guessing at them.
How long until something is actually running?
The Blueprint takes one to two weeks. A first automation goes live in weeks rather than quarters, and the exact timeline is in the Blueprint before you approve it. If we cannot say when it will be live, we have not understood the work well enough to build it.
Do we have to leave the software we already use?
No. We build into the case management, email, document, and billing systems you already run, and bridge the ones without an API. Adoption fails when the tool sits outside the workflow, so we put it inside.
Where does our data go, and does it train anything?
Your systems of record stay where they are, and your Blueprint specifies whether the custom environment runs in your cloud account or Dodonai’s. Generating output means sending the relevant material to the model providers you approve, under your agreements with them. Your work product is never used to train models for anyone else.
What happens when the output is wrong?
A workflow that fails a defined check stops and routes for review rather than proceeding, and consequential output waits for a person at the firm to approve it. Corrections feed the structured record, so the same mistake gets rarer instead of recurring.
What does it cost?
Three things, matching how we work: a fixed fee for the Blueprint, a fixed Build price per automation approved before development starts, and an optional Run fee for operating and improving what is in production. Model usage is passed through at cost. Exact numbers come with your Blueprint.
What if we want to stop?
You keep the system. Full source, with the hosting arrangement and handover agreed in your Blueprint. No long-term contract to exit. Stopping after one automation that works is a perfectly good outcome.
SOC 2 certified
