DocsFDE delivery

FDE budgets, estimation and billing

Estimate effort, complexity and resources with adjustable CNY budget references.

Basis and assumptions

These DigitalHe planning examples, dated November 2026, are illustrative estimates, not market averages, fixed packages or binding quotes. They assume remote delivery, an 8-hour person-day and CNY 2,000–4,000 per person-day. Final pricing reflects staffing, complexity, data quality, access, acceptance and support. Formal quotes state tax treatment.

Indicative project budgets

Person-days measure total effort, not calendar duration. Each row is an independent scope example. Quotes must identify overlap or credits between discovery, pilot and later stages; do not simply add rows. Multiple workflows, strict isolation or large migrations may exceed these ranges.

Remote delivery budget examples, CNY
Direction and assumptionsEffort / elapsed timeEngineering budget
Discovery: one workflow, samples, technical plan and estimate2–5 person-days / about 1 weekCNY 4,000–20,000
Bounded pilot: one workflow, existing connections, no complex migration8–15 person-days / about 2–3 weeksCNY 16,000–60,000
Workflow rollout: 1–2 flows, 1–2 standard integrations and handover20–40 person-days / about 4–8 weeksCNY 40,000–160,000
Multiple systems or dedicated environment: custom connectors, deployment and recovery60–120 person-days / about 8–16 weeksCNY 120,000–480,000; assess larger work separately

Example effort breakdown

For a read-only weekly report using two existing standard APIs, assume clean samples, test accounts and agreed definitions. Exclude full historical migration, write-back and dedicated networking. Use this breakdown for discussion and revise it after sampling.

Example read-only report project
Work packagePerson-days
Discovery and definitions3
Two standard connectors and mapping8
Knowledge, roles and workflow setup5
Access, business samples and recovery5
Documentation, training and handover3
Total24 person-days, about CNY 48,000–96,000

Costs outside engineering effort

Software and Agent subscriptions, model APIs, compute, storage, networking, devices, connector services and licenses are purchased separately. Agree travel and special-environment costs in advance. Define defect cover and ongoing support separately. For uncertain work, discuss a customer-held 15%–25% contingency, used only after an approved change rather than charged automatically.

Billing and payment options

Billing may use actual person-days with phase caps, or milestone prices once scope is clear. A discussion example is 30% at kickoff, 40% at pilot acceptance and 30% at handover. Contracts define actual percentages, invoicing, termination and settlement of unfinished work. Time-based work includes periodic records and advance approval of added fees.

Ongoing support budget

A remote support planning allowance of 2–5 person-days per month implies roughly CNY 4,000–20,000 monthly, subject to agreed allowance and rates. It may cover checks, small integration repairs, configuration and training; it does not imply a dedicated engineer or 24/7 service. Estimate new workflows, major adaptations and on-site work separately.

What changes the estimate

Undocumented interfaces, changing UIs, poor data, cross-team approvals, multiple isolated environments, concurrency and strict recovery targets increase effort. Test environments, stable APIs, clear owners and reusable samples can reduce it. Quotes should state assumptions, dependencies, validity, deliverables, support and spending or stop limits.

All documentationNext guide

Still have a question?

Explore expert support