Bounded jobs, visible decisions
Start with the job, then decide whether a model makes it clearer, faster, or safer. Inputs, permissions, approvals, retention, and failure modes are product requirements from the start.
It is the same approval-first pattern Avalon Flow runs on: models prepare the work, people approve it, and every action leaves a trail.
When not to use a model
Sometimes the right answer is ordinary automation, a better interface, or a clearer process. Questili uses a model only when the job needs one, and says so when it does not.
When a model is right, Questili can run it hosted, with the client's own provider account, or on private infrastructure.
Quick answers
Does every workflow need AI?
No. If standard automation or a better interface solves the problem without a model, Questili will choose that.
Can Questili extract data from invoices and documents?
Yes. Questili builds document workflows where a model drafts the line items, a person reviews them side by side, and only approved rows move on.