About Jiding Technology: a software team you can audit

Suzhou Jiding Network Technology Co., Ltd. designs, builds and operates internet products (software). Built on enterprise informatization and centered on a multi-product development framework, we deliver "Internet+ / Mobile Internet+ / IoT+" solutions together with implementation and operations. This page skips the vision statement and covers four concrete things: how we define requirements, how we staff a team, how many times you need to be present in an iteration, and what we don't do.

WHO WE ARE

Who we are: turning business processes into systems that keep running

Jiding Technology (Suzhou Jiding Network Technology Co., Ltd.) is a custom software company, not a packaged-product vendor. Our job is to translate your business processes — who acts on which document, under what rules, what gets recorded, and who to call when something goes wrong — into a system that keeps running for years, and then hand you the source code.

Most of our clients are in the Yangtze River Delta: discrete manufacturing shop floors, food and agricultural production lines, warehouses and logistics, pharmaceutical and laboratory compliance scenarios, and trading and retail ordering systems. What they have in common is very concrete: Excel can no longer hold the business, and off-the-shelf software cannot change the last mile.

We do two kinds of work, usually within the same factory: one is clarifying the relationships between people, orders, materials and machines (management software such as ERP / WMS / MES / CRM); the other is connecting equipment, data and dashboards (data acquisition, edge computing, IoT platforms, shop-floor displays). So the team is a single delivery system, not two unrelated outsourcing groups.

  • A requirements specification and itemized quote before you sign — never "price on request"
  • Acceptance criteria at every stage, written into the contract rather than agreed verbally
  • Full delivery of source code, database schema and deployment documentation, with no platform lock-in
  • Warranty period, response times and maintenance model all set out in the contract
Jiding Technology team reviewing a system prototype and business processes in front of a glass wall
Requirements review: every prototype screen is walked through so that "we'll deal with it later" gets resolved up front. Illustrative scene, not a photograph.
100+Enterprise clients served
50+Large projects successfully launched
80+Proven industry solutions

DIFFERENCE

How we differ from traditional outsourcing, big vendors and low-code platforms

Everyone is "building a system", but the four supplier types work very differently. The table below isn't self-promotion — it lays the differences out so you can compare them with the quote in your hand.

ItemTraditional staff augmentationLarge software companyLow-code / packaged productJiding Technology
How pricing worksPackaged per person-month, renegotiated whenever requirements changeFixed project price, long discovery phaseAnnual fee per account, customization billed separatelyModule × person-days × unit price, listed line by line, with written estimates for changes
Who defines requirementsThe client writes the spec, the vendor follows itConsultants analyze, but often trim to a product templateYou adapt to the product's existing processesWe go on site, map the process and confirm every prototype screen
Who owns go-liveEnds when the code is deliveredHanded over to operations after go-liveThe platform only guarantees the software runsGo-live, training and the observation period are all in scope
Source code and IPUsually provided, but documentation is often missingOften licensed rather than ownedSource code not providedSource code, database and documentation all belong to you
Requirement changesExtra quote, easy to argue overChange process, long lead timeYou wait for the product roadmapWritten estimate plus impact scope; you decide whether to proceed
Minimum project sizeNo limit — the more people, the betterUsually starts in the millionsFrom a few thousand, but hard to changeSmall tools from 50k, phased delivery above 800k

In one sentence: outsourcing sells person-days, big vendors sell brand, platforms sell accounts — we sell "getting the process running and leaving you able to maintain it yourself". That is why every quote includes an effort estimate and a source-code delivery clause.

TEAM

How a project team is staffed: who invests how much at which stage

The two questions clients ask most are "how many people do you have" and "who is responsible for my project". Headcount isn't the answer — staffing is. The chart below shows how a typical 8-person team is committed across five stages.

ResearchDesignBuildTest & launchSupportProject manager1 personBusiness consultant1 personSystem architect1 personBackend developers2 peopleFrontend & mobile1 personImplementation consultant1 personQA0.5 personOperations0.5 personCore involvementInvolvedLimited supportHeadcount = typical 8-person team (QA and operations at 0.5 each)
Who invests how much at which stage. The project manager runs throughout, the business consultant and architect are heavier up front, and QA joins once the build is handed over for testing — this chart is where the roles in our quotes come from.
RoleMain responsibilitiesWhat we need from you
Project managerSchedule, risks, changes and acceptance, plus a written status report every weekOne contact person who can make decisions
Business consultantOn-site discovery, process and document mapping, prototype designThe people who actually do the work, from each role
System architectSystem layering, database design, API and integration designA list of existing systems and interface documentation
Backend developersBusiness logic, APIs, reports and the permission modelTest data and sample documents
Frontend & mobileAdmin UI, shop-floor and store terminals, mini programs and appsDevice models and on-site network conditions
Implementation consultantData initialization, role-based training, go-live cutoverHistorical data exports and cleaning rules
QATest case design, defect tracking, regression verificationRole-based staff available during UAT
OperationsDeployment, monitoring, backup, incident responseServers or cloud resources, network access

Headcount isn't fixed. Small projects of 50–200k usually take 2–3 people: a project manager who also acts as business consultant, one backend developer and one frontend developer; platform-level projects grow to 12 or more, with QA and operations scaled proportionally. Every role that appears in a quote can be matched to a person and a scope of work in the table above — you can use this to check any quote you receive.

CADENCE

The two-week rhythm: you only need to show up three times per iteration

The most common way custom projects go off track isn't technical — it's "we only found out the direction was wrong once it was finished". The fix isn't more meetings; it's a fixed rhythm that forces deviation to surface within two weeks.

D1MonPlanningD2TueD3WedD4ThuD5FriMid-sprint demoD6MonD7TueD8WedQA handoffD9ThuD10FriAcceptanceWeekendIteration planning · 45 minYour product owner sets prioritiesMid-sprint demo · clickable buildSee half the progress, log issues liveDemo & acceptance · against criteriaSign off item by item on the stage checklistOur weekly routines (no involvement needed)Daily stand-up at 9:30, 15 minutesCode merged to trunk daily, always runnableClickable build every Friday, with a change log
One iteration every two weeks, and only three moments need you present (planning, mid-sprint demo, acceptance); the rest of the time we are running. A demo environment and issue list are published the day an iteration ends — progress is never communicated through weekly reports.

A one-page weekly status

What was done this week, what is planned next week, current risks and the decisions you need to make — four sections, one page. You know where the project stands without opening any system.

Changes must be in writing

Who requested it, which modules are affected, how many extra days, how much extra cost — one page for your signature. No signature, no work, and nothing gets quietly buried in the code along the way.

Demos use a clickable build

We don't present progress in slides — we hand you a demo environment and an account. Only what you can see counts as progress; everything else is just a description.

Issues enter the defect tracker the same day

Anything raised in a meeting is logged that day with severity and owner. Whatever was agreed in a chat message is superseded by the defect tracker.

About meetings: we keep meetings to an absolute minimum — a 45-minute planning session, a 30-minute mid-sprint demo and a 60-minute acceptance meeting; everything else is in writing. If your side misses two demos in a row, the project manager will proactively move to a monthly cadence and record the risk in the status report.

QUALITY

Three quality gates: no gate passed, no next step

We split "acceptance" from a single event at the end of a project into three checkpoints that must be passed along the way. The cost is a slower start; the payoff is not having to work through the night on go-live day.

01Requirements baselineProcess · Documents · Roles02Design reviewArchitecture · Schema · APIs03ImplementationTwo-week sprints · Daily builds04Integration testingAPI integration · Performance05UATReal data · Real roles06Go-liveCutover · Training · Hypercare1Gate 1 · Requirements baselineSpecification signed by both partiesPrototype confirmed screen by screen, no “we’ll deal with it later”Every quote line maps to a module2Gate 2 · QA entryAll self-test cases passNo P1 defectsDeploy script runs in a clean environment3Gate 3 · Go-live entryUAT passed and signed offHistorical data migration reconciledRollback plan rehearsed once
Three gates sit between the six steps: if a gate isn't passed, the next step doesn't start and the next payment isn't released. The cost is a slower start; the payoff is not having to "fight fires all night" on go-live day.
GateWhat it checksWho signs offIf it fails
Gate 1 · Requirements baselineSpecification, prototype and itemized quote are consistent, and every screen is clickableYour project owner + our project managerBack to discovery to complete it; no extra charge, but the schedule shifts
Gate 2 · QA entrySelf-test pass rate, zero P1 defects, deploy script runs in a clean environmentOur QA + development leadNo entry into integration testing; development resolves it internally first
Gate 3 · Go-live entryUAT signed off, historical data reconciled in both directions, rollback plan rehearsedYour business owner + our implementation consultantGo-live postponed; a new cutover window is scheduled

Six things we always check before go-live

  • After historical data migration, document counts and amounts reconcile in both directions
  • Key roles complete a round of hands-on training, with attendance recorded
  • Backup and rollback scripts rehearsed end to end in pre-production
  • Permission matrix verified line by line: who can see what, who can change what, who must not export
  • Print templates, document numbering rules, tax rates and precision confirmed item by item
  • On-call staff and contact details confirmed for the 3-day observation period after go-live

ENGINEERING

Tech stack and engineering standards: choose what will still be maintainable in five years

We don't chase new technology. Selection comes down to three criteria: whether your IT team can support it, whether anyone will still maintain it in five years, and whether a problem can be diagnosed within two hours. Anything only we could maintain is ruled out.

CategoryOur default choiceWhy
BackendJava / Spring Boot, with .NET as an alternativeMature enterprise operations, easy to hire for, and maintainers will still exist in ten years
FrontendVue / React with progressive enhancement in vanilla JSForm-heavy admin interfaces have a mature component ecosystem; key pages remain readable without JS
Mobile & mini programsuni-app / native mini programsOne codebase covers WeChat and the app, avoiding double maintenance cost
DatabaseMySQL / SQL Server, TDengine for time-series dataAligned with your existing DBA skills, with clear backup and permission models
Cache & queuesRedis / RabbitMQThe buffering layer for document concurrency, async jobs and device data
Industrial protocolsOPC UA / Modbus / MQTT / Siemens S7Broadest coverage, replaceable gateways, no lock-in to a single hardware vendor
DeploymentLinux + Docker + Nginx, offline intranet supportedFactory networks often have no internet access, so offline deployment and upgrades are essential

Engineering standards (written into the delivery documentation): code review before anything enters the repository, database changes always through scripts, four separate environments for development / test / pre-production / production, 90-day log retention, and every API versioned with an error-code table. These aren't nice-to-haves — they are what makes you willing to touch the system five years from now.

COVERAGE

Service radius: when we can be at your site

The question "can you send someone" comes up again and again on projects, so we would rather define the boundaries from the start: what distance means same-day, what means next-day, and when we work remotely only.

Suzhou1 hr radius2 hr radius1-hour radiusKunshan · Taicang · Changshu · Zhangjiagang · WujiangSame-day on-site, resident during implementation2-hour radiusWuxi · Changzhou · Nantong · Shanghai · JiaxingNext-day on-site, present at key milestonesRemoteNationwideVideo calls + remote assistance, travel when neededSchematic only, not to geographic scale; remote projects are not limited by these radii.
With Suzhou as the origin: within a one-hour drive we can be on site the same day, within two hours the next day; for more distant projects we implement remotely and travel for key milestones. With the boundaries written down, neither side has to keep probing "can you come over".
ZoneCities coveredOn-site ruleTypical arrangement
1-hour radiusKunshan, Taicang, Changshu, Zhangjiagang, WujiangSame-day on-siteResident during implementation; arrive one day before cutover
2-hour radiusWuxi, Changzhou, Nantong, Shanghai, JiaxingNext-day on-siteOn site 2–5 days at key milestones; remote otherwise
RemoteNationwideVideo calls + remote assistanceDiscovery and demos online; travel as needed for go-live, billed at cost

Why we emphasise this: on-site costs always end up in the quote. Stating "how far, how many visits, how many days" up front is what lets you compare suppliers fairly — a proposal that quotes remote-only rates and only mentions on-site charges at implementation time will always end up costing more.

INDUSTRIES

Industries we have served and typical systems

Different industries mean completely different documents to untangle and equipment to connect. Below are six areas we work in most, each with its core challenge spelled out.

Discrete manufacturing

Many product variants, small batch sizes, frequent changeovers. The core challenge is work-order splitting and the granularity of production reporting — too fine and operators won't fill it in, too coarse and you can't calculate cost.

Typical systems: MES, APS scheduling, equipment connectivity and OEE

Food & agriculture

Batches, grades, weighing and traceability are the main threads. The difficulty lies in the many-to-many relationship between raw-material batches and finished-product batches, and in grading standards that shift with the season.

Typical systems: sorting-line control, batch traceability, procurement settlement

Warehousing & logistics

Bin locations, waves, stocktakes and carrier reconciliation. The difficulty is keeping records consistent with physical stock when the same goods share bin space across different owners.

Typical systems: WMS, TMS transport, owner reconciliation portal

Pharma & laboratories

Compliance records, retention samples and audit trails. The difficulty is that every change must be traceable — who changed what, and when, with nothing omitted.

Typical systems: sample management, inspection records, audit trails

Energy & environment

Equipment monitoring, energy cost allocation and regulatory reporting. The difficulty is aligning meter conventions with the time windows used by the platform data.

Typical systems: energy monitoring, equipment maintenance, data reporting

Trade & retail

Ordering, shared inventory, membership and settlement. The difficulty is reconciliation once multi-tier pricing and overlapping promotions are applied.

Typical systems: ordering mini programs, chain-store back office, settlement centre

CONTACT

Contact and visits

The first conversation usually takes 60–90 minutes and no slides are needed. Bringing screenshots of your current system or exported documents is ten times more useful than a verbal description.

ItemInformation
Company nameSuzhou Jiding Network Technology Co., Ltd
AddressRoom 707, Innovation Building, Suzhou Advanced Research Institute, Hohai University, Xiangcheng District, Suzhou
Phone15862549539
Emailzhy@jidingkeji.com
Enquiry processInitial call or form → on-site or online requirements discovery → requirements specification + itemized quote → you decide whether to proceed
Visit tipsBook one day in advance and we will have a consultant from your industry present; bring sample documents and screens of your current system
Jiding Technology office area with workstations and meeting rooms
Office area: meeting rooms sit next to the workstations, so requirements discussions and development don't require running back and forth. Illustrative scene, not a photograph.

What we will ask at the first meeting

Not about budget — we ask four things: who does this work today, how many times a day, what happens when it goes wrong, and who reads the report at month end. Once those four are answered, the skeleton of the system is basically in place.

  • Bring one real document from the past month
  • Describe the single most painful step — no need to cover everything
  • Tell us about your current systems and interfaces
  • If you have already spoken to other vendors, bring their quotes so we can look at them together

Send your requirements — written proposal within 48 hours

FAQ

Eight questions about working with us

These come from real project kick-off meetings; the answers are as specific as we can make them.

What should we do if the requirements change halfway through the project?

The change process must be followed in writing: who proposed it, which modules are affected, how many additional man-days are required, and whether it affects the launch date. A one-page document will be provided for your decision. We will proceed only after you sign it. If you do not sign, we will not proceed, and we will not sneakily embed the changes in the code during implementation. Typically, a 10%–15% change allowance is reserved in the contract to avoid having to go through approval every time a small change is made.

How should confidentiality be handled?

A confidentiality agreement can be signed before signing the contract. The development environment is separated from the production environment, and customer data is not stored on individual developer devices. Fields involving formulas, process parameters, and customer lists can be desensitized, and desensitized data is uniformly used in the testing environment. After the project is completed, data copies in our environment will be cleaned up as agreed.

Can you send someone to be stationed on-site for development?

Suzhou and its surrounding areas are acceptable. It is a common practice to have on-site personnel during the implementation and go-live transition periods. On-site personnel are priced per person-day and included in the quotation. For remote projects, we adopt a combination of remote development and on-site presence at key milestones. The cost of on-site presence will be clearly calculated and provided to you in advance, with no hidden surcharges.

How long is the warranty period, and how quickly will you respond to any issues that arise?

The default warranty period is 12 months, covering defect repairs but excluding new requirements. The response time is graded according to severity: system unavailability requires a response within 2 hours, with a disposal plan provided within 4 hours; major functional blockages require a response within 8 hours; and general issues require a response within 2 working days. The terms are written into the contract, not relying on verbal commitments.

Who owns the source code and intellectual property rights?

It shall belong to Party A and be included in the contract. The delivery content includes source code, database structure and initialization scripts, deployment documents, interface documents, and test accounts; there shall be no encryption lock, no runtime authorization verification, and no restrictions on data export. Subsequently, Party A's IT team can maintain it independently or hand it over to a third party.

Can we only work on a part of the project, such as just the frontend or just the interface?

Yes, provided that the boundaries are clear. When only working on the front end, the interface documentation needs to be provided and frozen by your side or a third party; when only working on the interface, both parties need to agree on the field specifications and error code standards. The clearer the boundaries, the lower the cost of interface joint debugging, and this part will be directly reflected in the man-day quotation.

What is the minimum size of a project that can be accepted?

We also develop small tools of the order of magnitude of 50,000, such as a QR code scanning and work reporting mini-program, a set of reconciliation tools, and a device dashboard. Such projects are usually completed by 2-3 people within 3-6 weeks. For projects smaller than this scale, it is generally recommended to use existing tools for a period of time to clarify the requirements before customizing - customizing a small tool that hasn't been fully thought through is usually more expensive than buying an existing one.

Is Jiding Technology an outsourcing company or a product company?

Neither. We do not have packaged products to sell, nor do we rent engineers by person-month. We deliver by project: first, we go to the site to sort out the processes and documents, create prototypes and provide itemized quotations. After signing the contract, we conduct acceptance checks by stages. Upon delivery, the source code, database structure, and deployment documents are all owned by the client.

Need custom development? Read how we price before we discuss the solution

Cost breakdown, technology comparisons and acceptance approach — all stated openly.