Four ways to work together,
one delivery standard.
Some clients need a long-term team that works on their product and nothing else. Some need to fill a single seat. Some would rather hand a clearly scoped project over in one piece. We adapt to the way you already work, but the delivery discipline never changes: the same technical vetting, the same iteration rhythm, the same acceptance criteria, the same transparent billing.
Dedicated team
An engineering team assembled for you alone, long-term and working only on your product. You set the goals and the priorities; we take care of the people and the process.
See how it worksStaff augmentation
Engineers embed directly into your existing team, process and toolchain, adding capacity when you need it and scaling back when you do not.
See how it worksProject delivery
Fixed scope, fixed price, milestone acceptance. A complete package that already includes the project manager and the test team.
See how it worksQA & testing
Layer manual and automated test coverage onto your release process. Available on its own or alongside any delivery team.
See how it worksA team of your own,
without the hiring.
We assemble an engineering team for you alone. Its members work on your product and nothing else, and are never rotated between clients. Teams range from three engineers to twenty or more, usually covering backend, frontend and QA, with mobile, DevOps or data engineers added as the work requires. Every team is anchored by at least one senior engineer with 7+ years in the relevant stack, who owns architecture decisions and code review.
The split of responsibility is clear. Product direction, priorities and sign-off are yours, and the team reports directly to your product owner. Recruitment, performance, training, replacements, equipment and payroll are ours. We work in your repositories, your boards and your communication tools, join your stand-ups and reviews, and keep hours that overlap fully with your own team. Three months in, most clients find it hard to remember which engineers are “ours”.
-
Best forTeams with a long-lived product of their own, a need for steady engineering capacity, a reluctance to keep handing over context, or a local hiring cycle that takes too long.
-
What you getDedicated engineers, a named technical lead, two-week sprints with something to demo, fully open code and boards, and a monthly capacity and risk report.
-
BillingBilled monthly per engineer against one rate card, with no billing for bench time. Team size can be adjusted month to month, and there are no hidden fees.
One seat to fill,
not three months of waiting.
When your team structure is already settled and you are simply short of capacity in one role, staff augmentation is the least disruptive option. We shortlist matching engineers from our talent pool; you interview them and you make the call. Once someone is approved they go straight into your repositories, your boards and your stand-ups, managed day to day by your own technical lead, with no procedural difference from an internal hire.
Within 5 working days of a clear brief we provide a shortlist of engineers who have passed three rounds of technical vetting, each with a skills matrix, project history and coding-test results. While they are with you our mentorship model stays in place: every engineer has a named technical lead for one-to-one support, so nobody is left to push through a blocker alone. If someone is not the right fit for your team, we replace them within two weeks at no extra cost.
-
Best forTeams with an established engineering organisation and process that need to cover a gap, absorb a release peak, add a specialist skill, or fill a vacancy left by a departure.
-
What you getA shortlist you interview yourself, engineers you manage directly, a technical lead supporting them behind the scenes, and headcount you can scale up or down at any time.
-
BillingBilled monthly, with a three-month minimum engagement. Candidates within 5 working days. If someone is not the right fit, we replace them free of charge within two weeks.
Scope fixed, price fixed,
risk on our side.
If what you want is an outcome rather than a set of CVs, project delivery is the most direct route. We spend one to two weeks on discovery, working with your business and technical leads to turn goals, scope, boundaries and acceptance criteria into a requirements baseline both sides sign. Only then do we quote a fixed price and a milestone plan. That quote already covers the project manager, the test engineers and the documentation, so no extra staffing cost appears halfway through because something was “out of scope”.
Our delivery project manager owns the project outright: scheduling, risk, coordination and reporting all sit with them, and you need only one point of contact. Every milestone ships a build you can demo, a test report and an acceptance checklist, and payment for that stage is triggered only once it passes. When requirements genuinely have to change, we raise a written change request and re-estimate schedule and cost before the work starts, rather than absorbing it on a verbal promise. After acceptance and go-live the system enters a warranty period, during which defect fixes are free.
-
Best forSystem builds with a clear goal and scope, tender-based projects, self-contained modules of an existing product, or situations where you do not want to add internal headcount.
-
What you getA requirements baseline and prototype, a fixed schedule, a demonstrable build and test report at every milestone, the complete source code, and deployment and operations documentation.
-
BillingA fixed price paid by milestone, with the project manager and QA already included. After acceptance the system enters a warranty period in which defect fixes carry no extra charge.
Catch it before release,
not after.
Most teams do not skip testing on purpose; it simply keeps getting squeezed out by the release schedule. So we offer testing as a capability you can buy on its own. Test engineers take over your regression checklist, fill in the missing unit tests and API automation, and wire smoke and happy-path cases into CI, so that every commit produces a clear quality signal instead of three frantic days of manual checking before a release.
The scope is cut to fit your pain points: test strategy and case design, API and end-to-end automation, performance and load testing, security and compliance checks, pre-release acceptance testing and defect tracking. What we hand over is not just a report but testing assets that keep running afterwards: a case library, automation scripts, CI pipeline configuration and defect analysis, all transferred to your team at handover.
-
Best forRegression costs that keep climbing, a release cadence that will not improve, production defects that keep coming back, or a need for traceable test evidence ahead of acceptance or audit.
-
What you getA test strategy and case library, automation scripts that keep running, a quality gate wired into CI, a performance baseline report, and defect analysis for every release.
-
BillingBilled per engineer-month on its own, or quoted as a one-off for the project. Bought alongside a dedicated team or project delivery, testing is already included in that quote.
Eight roles,
one full delivery chain.
Whether you are filling one seat or standing up a whole team, everyone comes from the same talent pool: three rounds of technical vetting, senior mentorship, and a free replacement within two weeks.
Backend engineers
Business systems, APIs and data models, with strength in high concurrency, distributed architecture and legacy modernisation.
Frontend engineers
From component libraries to complex admin consoles, balancing maintainability, accessibility and real-world performance.
Mobile engineers
Native and cross-platform alike, at home with offline-first design, push notifications, Bluetooth peripherals and app-store release processes.
QA & test engineers
Case design, automation scripts and quality gates, so that every commit carries a clear quality signal.
DevOps & SRE
Build and deployment pipelines, container orchestration and observability, turning a release from an event into a routine operation.
Data engineers
Data pipelines, warehouse modelling and real-time processing, giving reporting, risk control and business analytics a dependable foundation.
UI/UX designers
From information architecture and interaction flows to a design system that can actually be built, sharing one component language with the frontend.
Delivery project managers
Scheduling, risk, stakeholder communication and acceptance. In project delivery, this is the only person you need to deal with.
A proven delivery method,
not luck.
Every project and every team follows the same clear path. At any stage you can see progress, cost and risk.
Discovery
We work with your business and technical leads to define goals, scope and constraints, producing a requirements baseline and acceptance criteria both sides sign off.
Team assembly
A vetted shortlist within 5 working days; every team is anchored by at least one senior engineer with 7+ years in the relevant stack.
Iterative delivery
Two-week sprints, each ending in something you can demo. Code, boards and documentation are fully open to you.
Quality acceptance
Automated and manual testing run in parallel; performance, security and compliance checks happen early. An acceptance report ships with every milestone.
Operations & improvement
Go-live is not the finish line. We provide operations support, knowledge transfer and continuous iteration until the system runs steadily inside your business.
Turn what must not go wrong
into process, up front.
Four baselines apply to every engagement model, and they do not flex with the size of the project.
Code standards & review
One coding standard and one branching strategy. Nothing merges without review, and architectural changes are signed off by a senior engineer.
CI/CD & automated testing
Every commit triggers a build, static analysis and automated cases. Failing tests block the merge, and any release can be rolled back in one step.
Data security & compliance
Masked test data, least-privilege access and complete audit logs. We work alongside clients through assessment and remediation under China’s Multi-Level Protection Scheme.
The IP is yours
The contract assigns copyright in every deliverable to you. Everyone signs a non-disclosure agreement, and at the end of the project data is destroyed or handed over as agreed.
The questions clients ask
before they sign.
Not finding your answer? Write to us directly and you will usually hear back within one working day.
How do you charge?
Dedicated teams and staff augmentation are billed monthly per engineer against one rate card, with prices banded by role and years of experience, and no billing for bench time. Project delivery is quoted once for a fixed scope and paid by milestone. QA and testing can be billed per engineer-month or packaged as a project quote. Every price is written into the contract, and there are no hidden fees.
What is the minimum engagement?
Staff augmentation and dedicated teams have a three-month minimum, which is the least time it takes for an engineer to genuinely learn your business and your codebase. After that it renews monthly, and one month of written notice is enough to change headcount or end the engagement. Project delivery has no minimum term; it follows the milestone plan, and the smallest module-level projects usually finish within six to eight weeks.
What if an engineer is not the right fit?
Every candidate passes three rounds of assessment before entering our talent pool: CV screening, an online coding test and a senior-engineer interview. You are welcome to run a round of your own on top of that, and the decision is always yours. If an engineer turns out not to fit your team after they start, we replace them within two weeks at no cost and handle the handover to their replacement. This applies to both staff augmentation and dedicated teams.
Who owns the code and the IP?
You do. The contract states explicitly that all intellectual property in the source code, designs, documentation and data produced by the project belongs to the client, and that we retain no right to reuse any of it. Everyone working on the project signs a non-disclosure agreement, code is hosted in the repository you nominate, and when the project ends local copies are handed over or destroyed as you instruct. If you would rather we signed your own NDA or data-processing agreement template, we are happy to.
Can your engineers work on site?
Yes. We have delivery centres in Shanghai and Hangzhou and support on-site placement, hybrid working and fully remote arrangements. Clients in the Yangtze River Delta usually place part of the team on site and keep the rest remote; clients further away work mainly remotely with on-site support at key points. In every model, working hours overlap fully with your team. On-site placement incurs travel and workspace costs, which are itemised separately in the quote.
How do you communicate and report?
We use your tools rather than asking you to adopt ours: WeCom, DingTalk, Lark, Slack, Jira and Zentao all work. The standing rhythm is a daily stand-up plus a sprint review and demo every two weeks. Dedicated teams deliver a monthly capacity and risk report; project delivery submits a progress report, test report and acceptance checklist at every milestone. All repositories, boards and documents are fully open to you, so you can look for yourself at any time instead of waiting for us to report.
Ready to build a team that actually delivers?
Tell us what you are building and the skills you need. We will come back within a week with a team proposal and a quote.