Discuss the workflow
Explain how RFQs arrive, what gets checked, where delays occur and who owns the final decision. No installation is required.
The pilot
One workflow.
A shared definition of useful.
A focused pilot tests whether an AI-assisted preparation process helps your team. Inputs, responsibilities, acceptance and delivery timing are agreed before the work begins.
From the first discussion to a decision
Agree a written scope
Define the samples, input formats, output fields, review rules, schedule and acceptance criteria. Confirm the data arrangements first.
Review the pilot evidence
Compare results with the agreed baseline. Document corrections and limitations, then decide whether to revise, stop or plan deployment.
Start with approved examples.
Use synthetic or anonymized samples for the first assessment wherever practical. Do not send confidential drawings before we agree which information can be shared and how it will be handled.
Read the data and access boundaries- 01Representative inputsExamples of normal work, incomplete requests and relevant exceptions.
- 02A reviewer’s baselineThe fields a person would prepare and the checks they would perform.
- 03A named workflow ownerSomeone who can resolve process questions and agree the acceptance criteria.
What the written scope should cover
| Area | Agree before work starts | Evidence to review |
|---|---|---|
| Inputs | Sample count, formats, languages, quality and exclusions. | A sample register and a record of unsupported inputs. |
| Preparation draft | Required fields, source references and uncertainty rules. | Structured drafts, missing-information flags and corrections. |
| Human review | Reviewer, approval responsibilities and costly error types. | A review checklist and decisions on exceptions. |
| Acceptance | Baseline, measurement method and agreed thresholds. | Results on the agreed sample set, with limitations stated. |
| Data & access | Approved data, processing location, retention, access and model providers. | The agreed handling and access arrangements. |
| Delivery | Milestones, availability, time zones and change control. | A result review and a documented next-step decision. |
Clear responsibilities on both sides
SJAITECH
Document the agreed workflow, prepare the scoped implementation and report the pilot results and limitations. Raise out-of-scope requests before changing the work.
Your team
Approve the samples and access, explain business rules, provide a reviewer and resolve questions. Retain responsibility for specification checks and all customer-facing quotes.
Questions before a pilot
How long does it take?
Timing depends on the input formats, scope, approved samples and reviewer availability. Milestones and delivery hours are confirmed in writing before work starts.
Do we need Tianshu or remote access?
Neither is required for the initial discussion. Any later software installation or access is scoped separately. The Standard preview supports communication; remote assistance requires separate approval and its plugin is not ready for production use.
What happens when the scope changes?
New document formats, systems, output fields or approval rules are reviewed as scope changes. We agree the impact on work, timing and commercial terms before proceeding.
What happens after the pilot?
We review the evidence together. Production use, integrations, operating cost, support and continued access require a separate decision. A pilot does not automatically authorize deployment.
Start with a conversation
Let’s look at your
RFQ workflow.
Tell us what arrives, what your team checks, and where preparation slows down. An initial discussion needs no software installation or confidential drawings.
Contact the SJAITECH team
[email protected]Use this address in your preferred email app.
Delivery hours, time zone and pilot scope are agreed together.