Software and systems delivery for Hong Kong businesses
Six services across custom software, mobile apps, websites, business systems, IoT and AI applications, quoted against the project scope. The team sits in Chengdu, in the same UTC+8 time zone as Hong Kong with fully overlapping working days, communicating in Traditional Chinese and English, with on-site meetings in Hong Kong arranged around project milestones.
The three conditions below shape every project we deliver in this region. Constraints come first; system scope and technical approach follow.
Most Hong Kong businesses are SMEs with short decision chains: scope is usually settled in one or two meetings, and a written quotation is expected to list modules, timeline and cost line by line. We quote against one feature list, separating modules, milestones and payment points so the numbers can go through internal approval and comparison.
The Personal Data (Privacy) Ordinance sets six data protection principles covering purpose and manner of collection, accuracy, retention, use limits, security, and access and correction. The 2021 amendment criminalised doxxing. Consent records, access and correction workflows and permission auditing are built as standard features rather than left to a privacy policy page.
Hong Kong has no value-added tax, invoices are issued by the company itself rather than through a tax platform, and common payment methods include FPS, PayMe, Octopus, cards and bank transfer. Systems are designed around those flows; card numbers never enter our database and are handled by a licensed payment institution.
Hong Kong teams are lean and rarely staff a dedicated technician for a single system. Handover includes an operations manual and staff training so day-to-day content and order handling stay with the business, with technical operations handled by us on agreed response terms.
All six follow the same engineering standard. Implementation adapts to local compliance requirements, payment methods, language and site conditions.
Built around your business rules, with no second build later
In Hong Kong, the competitive part of a business is often in the detail: quoting rules, commission calculation, settlement cycles. Off-the-shelf products rarely cover it. We map current spreadsheets and manual steps, turn the rules into configurable items, agree the technical design and API contracts, then build. Source code, database scripts and design files transfer on completion.
A delivery app is finished when front-line staff can use it
In retail, logistics and property management, app users are on the front line with uneven devices and connections. We design the first screen and task path around the real workflow, show a usable interface first and load data afterwards on weak networks, and treat offline operation and resumable sync as standard rather than optional.
Traditional Chinese and English maintained together, search included
Hong Kong customers switch between Traditional Chinese and English, so both sets of content need to be findable. We set titles, descriptions and hreflang per language, structure pages so search engines and generative engines can quote them accurately, and keep enquiry forms and WhatsApp entry points within reach on the first screen.
Multi-branch, multi-currency and multi-entity books that reconcile
Hong Kong businesses often run several branches or entities, or take payment in both HKD and RMB. Currency, tax treatment, entity and permissions are configuration items; reports roll up by entity and currency, and reconciliation differences are produced as a list instead of being traced by hand at month end.
Prove it on one site, then replicate
Collection requirements in property management, warehousing and retail usually span multiple locations and existing equipment. We complete device integration, data reporting and alerting on a single site first, confirm stability, then replicate. Spreading devices across every site at once makes faults hard to isolate.
Answers with sources, and a route to a human
Hong Kong customers ask in Traditional Chinese and English, and answers need to come from the company's own material. We build a knowledge base from your documents, attach sources to answers, hand over to a human when the answer is not available, and keep the transcript. Before launch we build an evaluation set from real questions and report accuracy by language.
Each case states the project name, client background, industry, business challenge, deliverables and delivery value. Client names are anonymised under confidentiality agreements.
Client: A Hong Kong retail chain (12 stores, food and household goods)
Store managers ordered on experience, so fast sellers ran out and slow lines piled up. Stocktakes were on paper and only aggregated the next day, with variances checked by hand. Head office could not see same-day stock by store, and transfers were confirmed by phone.
Ordering moved from experience to confirming suggestions, reducing both stockouts and overstock. Stocktakes moved from next-day to same-day. Inter-store transfers no longer depend on phone confirmation.
Client: A Hong Kong logistics carrier (delivery team of about 60)
Jobs were allocated by group chat and phone, so drivers reconfirmed constantly. Proof of delivery was a photo of a paper slip, sorted at the depot later, and customer enquiries meant searching for images. Exceptions such as refusals and address changes had no consistent record.
Allocation moved from phone calls to in-app acceptance. Proof of delivery returns immediately, so enquiries no longer involve hunting for photos. Exception reasons are recorded consistently and can be checked with customers.
Client: A Hong Kong estate agency (3 branches)
Listings sat in spreadsheets and personal phones with heavy duplication. Client requirements were kept in personal notes, so handovers lost context. The public website was updated by hand and often disagreed with internal records.
Listings are maintained once, with the website matching internal records. Client follow-up is traceable across handovers, and routine enquiries are answered at the first layer.
Client: A Hong Kong property management company (6 estates)
Inspections were sign-in sheets on paper that could not be verified later. Pump room and switch room faults were only found on site, with nobody on duty at night. Maintenance jobs were assigned verbally, leaving progress and ownership unclear.
Inspections became verifiable records. Equipment faults raise alerts when they happen, including unattended night hours. Work order owners and handling times are traceable.
Client: A Hong Kong education centre (4 branches)
Enrolment came through WhatsApp and paper forms, with the same slot booked twice. Payments and attendance lived in separate records, so refunds meant checking both. Parents asked the front desk to confirm remaining lesson credits.
Duplicate and over-capacity bookings stopped. Refunds and transfers are calculated by rule, reducing disputes. Parent enquiries no longer occupy the front desk.
Drag horizontally to view all cases
No cases match the current filter. Please adjust the selection.
Case note: client names are anonymised under confidentiality agreements; cases are presented to explain implementation approach and delivery boundaries, and specific figures are subject to project acceptance records.
These requirements directly affect data structures, page behaviour and deployment. We confirm each item during solution design and record it in a checklist. Formal legal advice should be confirmed with a local adviser.
The Ordinance sets six data protection principles covering purpose and manner of collection, accuracy, retention, use limits, security, and access and correction rights. The 2021 amendment criminalised doxxing. Systems are designed with consent records, retention limits and permission auditing. Section 33 on cross-border data transfer has not been brought into effect; cross-border transfers are handled according to the contract and the client's requirements.
The Ordinance gives electronic records and electronic signatures legal effect, providing a basis for electronic contracts, e-signature and online confirmation flows. Where signature is involved we follow the client's legal advice on the method, and keep timestamps and action logs inside the system.
The Ordinance prohibits unfair trade practices including false trade descriptions, misleading omissions and aggressive commercial practices, and applies to prices, promotions and performance claims on websites and campaign pages. Page copy is written against verifiable facts, with the applicable conditions of each price and offer stated.
Where cards are accepted, card numbers and verification codes never enter our database: a licensed payment institution processes them and the system stores only the transaction reference and status. Local methods such as FPS, PayMe and Octopus are integrated through their published interfaces, with callbacks and reconciliation records kept in traceable logs.
Time zones, language and acceptance criteria are the three usual sources of risk in cross-border projects. All three are agreed in writing before work starts.
Hong Kong and Chengdu share UTC+8, so working days overlap completely. Enquiries during the working day are answered the same day; urgent issues follow the agreed channel.
Traditional Chinese and English, with documents, interface copy and training material provided in the language each team uses.
Acceptance runs milestone by milestone, each with a working environment and a checklist. Releases are scheduled inside Hong Kong working hours to limit disruption.
Requirement workshops and key milestones can be held in Hong Kong where the project calls for it; day-to-day communication runs on online meetings and written records.
Roles, processes and first-phase scope are mapped into a requirement list and a prototype, confirmed before design begins.
Visual and interaction designs are completed, together with decisions on local language, compliance pages and payment methods.
Runnable builds are delivered in increments and demonstrated at each phase, so issues surface early.
Handover follows a launch checklist, monitoring and alerting, and a tested backup and restore routine. Further iterations and support are scheduled from there.
These are the questions that come up most often in real project discussions.
We issue a written quotation against one feature list, setting out modules, milestones, timeline and payment points so it can go through internal approval and comparison. If scope changes, we confirm the impact before revising the quote rather than adding unlisted charges during development.
It depends on scope. Brand and marketing sites usually go live within a few weeks. Custom systems and apps are delivered in phases, proving the core flow first and then extending by milestone. The timeline is written into the quotation after requirements are mapped.
The team is based in Chengdu, in the same UTC+8 time zone with fully overlapping working days, communicating through online meetings and written records. Requirement workshops and key milestones can be held in Hong Kong when the project calls for it. There is no Hong Kong office.
By contract, source code, database scripts and design files transfer to the client on completion. We retain the right to reuse generic components and our own tooling; your business data and business rules stay with you.
Handover includes an operations manual and training so day-to-day content and order handling stay in-house. Technical operations run on agreed response terms, either per request or as an annual arrangement, with response hours written into the contract.
Yes. Interfaces, documents and training material can be provided in both, and the website sets separate titles, descriptions and hreflang per language so each version can be indexed.
Share your current operation, existing systems and first-phase objectives. We respond with a scope recommendation and a quotation.
+86 173 6006 2006 (Chinese). WeChat is available on request. For English-language communication, please say so in your first message and we will assign the appropriate contact.
A short description of the current operation, existing systems or spreadsheets, target launch date and budget range. If the requirement is not yet defined, we help narrow the scope first.
Our delivery centre is in Chengdu, China. Working sessions are scheduled in Hong Kong time. On-site meetings can be arranged at key milestones.
Where a business spans several regions, work proceeds under one delivery standard and one documentation set.
