A return-home business taking on small digital projects
The October 18 Baoding Daily report on Baoding News focused on Li and Baoding Qimei Information Technology. A reporter saw him working with a colleague in Gaoyang on October 14. He designed products before using AI to assist code and assets, offering an example of organizing business around specific tasks.
The report described Nuanyangyang, a tourism and public-service question app based on local material, with separate development and annual-maintenance charges. A pet mini-program still involved coordination and unreleased work, while textile services awaited research. Distinguishing these stages clarifies what was actually happening.
Customer projects and independent products share the same time
Commissions usually have agreed scope and deadlines; independent products need continuing reasons for use. A small team pursuing both must decide where to spend today's attention, not merely whether code is possible. Maintenance, projects awaiting approval and unvalidated features compete for capacity.
A one-page portfolio could record users, current stage, next investment and reasons for deferral. Technical feasibility does not make something worth starting now, and deferral need not mean technical failure. Identify the actual blocking condition before rescheduling.
Development and annual upkeep solve different problems
The reported fee structure invites comparison of distinct work. Development creates a usable system; maintenance keeps it aligned with changing material, tools and usage. Tourism descriptions, service entry points and opening arrangements can change, making previously correct answers obsolete.
After a hypothetical local event ends, pages and question-answering material need synchronized updates. This is our scenario, not a reported fault. Continuing service can cover updates, issue handling and adaptations; annual maintenance should not be a fee without a work definition.
Local-industry knowledge may matter more than extra features
Industrial-cluster customers care about products, customers and operational problems. Before entering a sector, ask which information is hardest to organize, which steps involve waiting, who will try a sample and why existing methods are insufficient. Answers may change the original product direction.
Research also helps choose a charging unit: one preparation job, an application build, a period of updates or continuing tool use. Different units carry different costs and customer responsibilities even when tools are shared.
Define a next step more concrete than a vision
A customer project may next require approval of source material and a use case; an independent product may need a few target users completing a task; a new industry may warrant a visit followed by a decision not to proceed. Each needs observable progress to guide further investment.
Reported compute fees, development quotes and personal efficiency cannot be converted directly into profit. Two people seen on site do not establish all collaboration costs. The useful lesson is to compare tool capability, business stage and time capacity, then use real usage and maintenance records to decide what to retain.
Further reading: independent maintenance capacity; a company's first FDE task.