Services

We work on software that has to keep running after we hand it over. Most engagements are one of the seven below — and if your problem is not a fit, we will say so in the first conversation.

Enterprise platform integration

Messaging, approval flows, data sync and automation on the platforms your team already uses:

  • Lark / 飞书, DingTalk / 钉钉, WeCom / 企业微信 and Lark Base
  • Notifications, approvals and internal tools wired into existing systems instead of replacing them

B2B SaaS product development

From 0→1 design and build through to running the product in production: data model, service boundaries, deployment, monitoring and iteration. See the products we already operate this way.

Large-model applications

Models connected to real business processes — retrieval over your own knowledge base, prompt engineering, workflow orchestration, permissions and evaluation. In production, not in a demo.

Garmin app development

Watch faces, data fields and widgets for Garmin watches on the Connect IQ platform — from design and device compatibility to publishing in the Connect IQ Store. See our Garmin apps.

Race and running club watch faces

Branded Garmin watch faces for marathons, trail races and corporate running clubs: a pre-race countdown, a finisher keepsake after the race and sponsor logo slots. The organizer pays once and runners download for free. Race plans start at CNY 3,800 and go live in 14 working days. See plans and pricing.

WordPress plugin development

Custom WordPress plugins: AI provider integrations for the WordPress AI Client, payment and subscription flows, notifications to chat tools and editor extensions — built to WordPress.org standards. See our 16 published plugins.

Self-hosted PaaS consulting

Hands-on CapRover help for teams running their own VPS: hourly pairing on a live incident, platform landing, stack migration, CI/CD, backups and production hardening.

How an engagement runs

  1. Intake — a working interview: what exists today, what "done" looks like, and who operates it afterwards.
  2. Plan — the approach, the modules, and an explicit out-of-scope list. You confirm before work starts.
  3. Implementation — landed in the order the platform requires: install and HTTPS before apps, registry before CI, backups before cleanup.
  4. Drill — a rollback, restore or migration rehearsed rather than handing over an untested box.
  5. Handover — a short runbook, a training session, and a follow-up window for questions.

Tell us about your project.