Partnerships

Get the scope clear first, then talk schedule and price. This page carries no default promise.

Four reasons to write

We take all four. Each one starts with the scope agreed before anything is put on paper.

Our software and sites already serve everyday users. We want them on more devices.

Open to pre-install, app stores, download sites and hardware makers
What we bring: installable packages with an update channel, agreed customer-service wording, and result data kept separate by channel
A small test first, then volume. We do not sign a locked full-year quantity up front

The same in-house capability, recombined around your business.

Custom delivery in three kinds: desktop tools, internal website platforms, mini programs
From sorting out the requirements to launch, done by us. No subcontracting
Scope and schedule are confirmed in person or by mail. This page carries no default promise

Product material, screenshots or a description of a use case: we can send them directly.

On request: product positioning, feature boundaries, interfaces you can actually screenshot
Reviews and trials get no pre-publication review, and we do not pay for a conclusion
Where something is written wrong, we point it out and ask for a correction

General components that grew out of internal tools, placed in the community. Feedback and pull requests are welcome.

Welcome: problem reports, bug reports with steps to reproduce, patches for edge cases
Open an issue before proposing a feature so the design intent is agreed, instead of two versions of the same thing
Repository addresses by mail for now. They go on this page once they are live

These three apply to every intent: made clear first, then we start.

From sorting out the requirements to launch, the people who build it are the people who talk to you. No extra layer, no second-hand problems.

Scope, schedule and fees are written down before work starts. What we cannot do, we say so directly, and the price never changes midway.

The unified account, payment and release channels come from our own products, so delivery is faster and the boundaries are proven.

Write these three things and we can send a plan that works. If you cannot cover all three, send what you have and we will ask for the rest.

The thing you want solved, and who is carrying it by hand today.
Where it gets used: how many people, when, and whether it can reach the network.
The form you expect: website, desktop software or mini program, and any hard deadline.

Every step has something in writing. A step that cannot hold gets flagged first instead of being skipped.

Plan confirmed: scope, schedule and fees go on paper, and work starts after you confirm.
Build and communicate: progress and half-finished work are shared at each checkpoint, interface and data together.
Accept and deliver: acceptance follows the standard written down before the start, and the deliverable has to work in real use.
After launch: release notes and issue reports go to the same mailbox, and the software supports background updates and version rollback.

The mailbox goes straight to partnership talks. We read it on business days and usually reply within one or two business days.