WeChat mini program budget: split certification from three-year operations
Certification, domain, and hosting are a fixed entry ticket. Cost actually moves with custom depth, payments and category review, plus API changes, resubmission, and on-call.
The first line items on a mini program are annual certification, a domain, and cloud resources. Those are access costs, not the project. Templates or SaaS can cheapen a first demo; once process, approvals, and integration with existing systems leave the template, a second custom round appears, and the sum is often higher than customizing the primary path from the start.
Split the budget into three layers
- Must-have to go live: login (including enterprise identity if needed), core documents, payments or subscriptions if required, privacy text, and category qualifications.
- Growth features that can wait: campaigns, complex membership, multi-store boards. They should not block a v1 that runs on its own.
- Yearly run cost: WeChat API and review-rule changes, rejected builds and resubmits, content and permission edits, incident coverage. In-house teams must count headcount, not only VM quotes.
Payments, location, and sensitive user fields stretch review. The statement of work should name who submits, how fast a rejection is handled, and the default lead time for a change. Without that, the product looks cheap to start and expensive every time the queue resets.
Choosing custom, template, or SaaS
Stable processes that must reconcile with ERP or an internal platform belong on a custom primary path so template fields do not lock you in. Campaign or brochure apps that can live with a standard flow fit templates or SaaS—if you can export data and leave when the contract ends.
The cost curve is low to start, continuous as the business changes. Price a three-year horizon, not the first demo build.