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.
WHO WE ARE
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.
DIFFERENCE
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.
| Item | Traditional staff augmentation | Large software company | Low-code / packaged product | Jiding Technology |
|---|---|---|---|---|
| How pricing works | Packaged per person-month, renegotiated whenever requirements change | Fixed project price, long discovery phase | Annual fee per account, customization billed separately | Module × person-days × unit price, listed line by line, with written estimates for changes |
| Who defines requirements | The client writes the spec, the vendor follows it | Consultants analyze, but often trim to a product template | You adapt to the product's existing processes | We go on site, map the process and confirm every prototype screen |
| Who owns go-live | Ends when the code is delivered | Handed over to operations after go-live | The platform only guarantees the software runs | Go-live, training and the observation period are all in scope |
| Source code and IP | Usually provided, but documentation is often missing | Often licensed rather than owned | Source code not provided | Source code, database and documentation all belong to you |
| Requirement changes | Extra quote, easy to argue over | Change process, long lead time | You wait for the product roadmap | Written estimate plus impact scope; you decide whether to proceed |
| Minimum project size | No limit — the more people, the better | Usually starts in the millions | From a few thousand, but hard to change | Small 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
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.
| Role | Main responsibilities | What we need from you |
|---|---|---|
| Project manager | Schedule, risks, changes and acceptance, plus a written status report every week | One contact person who can make decisions |
| Business consultant | On-site discovery, process and document mapping, prototype design | The people who actually do the work, from each role |
| System architect | System layering, database design, API and integration design | A list of existing systems and interface documentation |
| Backend developers | Business logic, APIs, reports and the permission model | Test data and sample documents |
| Frontend & mobile | Admin UI, shop-floor and store terminals, mini programs and apps | Device models and on-site network conditions |
| Implementation consultant | Data initialization, role-based training, go-live cutover | Historical data exports and cleaning rules |
| QA | Test case design, defect tracking, regression verification | Role-based staff available during UAT |
| Operations | Deployment, monitoring, backup, incident response | Servers 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 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.
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.
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.
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.
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
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.
| Gate | What it checks | Who signs off | If it fails |
|---|---|---|---|
| Gate 1 · Requirements baseline | Specification, prototype and itemized quote are consistent, and every screen is clickable | Your project owner + our project manager | Back to discovery to complete it; no extra charge, but the schedule shifts |
| Gate 2 · QA entry | Self-test pass rate, zero P1 defects, deploy script runs in a clean environment | Our QA + development lead | No entry into integration testing; development resolves it internally first |
| Gate 3 · Go-live entry | UAT signed off, historical data reconciled in both directions, rollback plan rehearsed | Your business owner + our implementation consultant | Go-live postponed; a new cutover window is scheduled |
ENGINEERING
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.
| Category | Our default choice | Why |
|---|---|---|
| Backend | Java / Spring Boot, with .NET as an alternative | Mature enterprise operations, easy to hire for, and maintainers will still exist in ten years |
| Frontend | Vue / React with progressive enhancement in vanilla JS | Form-heavy admin interfaces have a mature component ecosystem; key pages remain readable without JS |
| Mobile & mini programs | uni-app / native mini programs | One codebase covers WeChat and the app, avoiding double maintenance cost |
| Database | MySQL / SQL Server, TDengine for time-series data | Aligned with your existing DBA skills, with clear backup and permission models |
| Cache & queues | Redis / RabbitMQ | The buffering layer for document concurrency, async jobs and device data |
| Industrial protocols | OPC UA / Modbus / MQTT / Siemens S7 | Broadest coverage, replaceable gateways, no lock-in to a single hardware vendor |
| Deployment | Linux + Docker + Nginx, offline intranet supported | Factory 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
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.
| Zone | Cities covered | On-site rule | Typical arrangement |
|---|---|---|---|
| 1-hour radius | Kunshan, Taicang, Changshu, Zhangjiagang, Wujiang | Same-day on-site | Resident during implementation; arrive one day before cutover |
| 2-hour radius | Wuxi, Changzhou, Nantong, Shanghai, Jiaxing | Next-day on-site | On site 2–5 days at key milestones; remote otherwise |
| Remote | Nationwide | Video calls + remote assistance | Discovery 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
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.
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
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
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
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
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
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
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.
| Item | Information |
|---|---|
| Company name | Suzhou Jiding Network Technology Co., Ltd |
| Address | Room 707, Innovation Building, Suzhou Advanced Research Institute, Hohai University, Xiangcheng District, Suzhou |
| Phone | 15862549539 |
| zhy@jidingkeji.com | |
| Enquiry process | Initial call or form → on-site or online requirements discovery → requirements specification + itemized quote → you decide whether to proceed |
| Visit tips | Book one day in advance and we will have a consultant from your industry present; bring sample documents and screens of your current system |
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.
FAQ
These come from real project kick-off meetings; the answers are as specific as we can make them.
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.
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.
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.
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.
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.
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.
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.
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.
Cost breakdown, technology comparisons and acceptance approach — all stated openly.