Why there is no total price before scope is confirmed
- Scope drives effort: whether business systems must be integrated, whether permissions need rework, and whether an evaluation set must be built all multiply the work.
- Data preparation is usually the largest part: document cleaning, chunking, building evaluation sets and validating output quality often take longer than installing the inference stack.
- A premature number misleads: too low suggests the project is simple; too high turns away the scenarios that fit best.
- Hardware prices move: GPU and accessory pricing changes with the market, so a fixed figure ages badly and damages credibility.
What drives the cost
Which model you need
Models have different equipment requirements. We compare answer quality and hardware needs. If a compressed model can save resources, check that its answers remain useful.
How many people use it, and how much text they send
More simultaneous users and longer documents can require more resources. Test real tasks and waiting times before choosing equipment.
How much document preparation is needed
Incomplete files, duplicates, poor scans and access rules all affect the work. We also need real questions to check whether the answers are useful.
Which systems need to connect
Running a model alone takes less integration work than connecting office systems, a CRM or company documents. Connections to tools such as Microsoft 365, Teams or SharePoint depend on their interfaces and your account permissions.
Who may see which documents
Department, role and document access rules need configuration and testing, as do records of who used the system and when.
What you need to check before launch
Tests may cover answers, simultaneous use, long documents, waiting times and continuous operation. The agreed checks determine the testing and adjustment work.
Remote work or site visits
Remote support, site installation, offline environments and resident support require different amounts of staff time and travel.
Existing equipment or a new purchase
Use your current hardware, ask us to help plan equipment, or choose your own supplier. New equipment is listed separately using the actual configuration and current quotation.
Pricing approach
- Staged quotation: scope definition, deployment, integration and acceptance are quoted as separate phases, each with its deliverables and acceptance criteria written into the project plan.
- Day-rate metering: on-site work, resident support and out-of-scope changes are metered in person-days, with the day rate agreed in the contract.
- Validation separated from production: validate model quality and document permissions at small scale before expanding to production, avoiding a large one-off commitment.
- Annual operations priced separately: post-launch support is priced annually and is not bundled into the initial delivery.
- Changes confirmed individually: out-of-scope requests are assessed for impact and schedule, then implemented and priced after confirmation.
- Hardware and software listed separately: hardware and accessories are itemised by actual configuration, separately from software delivery.
Scale and prerequisites
A common departmental starting point is a 20–50 person company or internal team with around 10–15 concurrent users, where keeping data inside the network, document analysis, knowledge retrieval and internal digital employees matter. Final capacity still depends on model version, precision, context and workload testing.
As concurrency, context length or model size grows, the compute tier must be reassessed. We can complete a capacity assessment first, confirm the hardware configuration and deployment shape, and then move to quotation.
What to tell us when you get in touch
The list below is the starting point for scope definition. Once the items are confirmed, we provide a staged quotation and schedule rather than a total price detached from the scenario.
- The work: who will use AI, what they want it to do, current problems and what a useful result looks like.
- The documents: where they are, who may read them and whether they may leave your network.
- Equipment and timing: what you already have, systems to connect, approximate user numbers and when you want to start.
Next step
Tick what you already know below; you do not need every answer yet. Copy the list, add your details, and send it to us to discuss the work, cost and timing.
Phone: +86 139 2521 1225 Email: tianjun@jsle.cn
Tick what is already clear to build a requirement list
Tick what you already know. You do not need every answer yet. Copy the list, add your details and send it to us to start the conversation.
Tick any item to build the list.