From Idea to Launch in 9 Steps

1. 1
   1

   Discovery

   1–2 daysBefore contract

   Tell us your idea. We help you pin down what to build, a rough budget and a timeline.

   Your part

   • Tell us about your business and the problem to solve
   • Share whatever you have: spreadsheets, workflows, reference sites or apps, existing systems

   Our part

   • Reply within 1–2 days
   • Understand the business and clarify anything vague
   • Judge honestly whether we are the right fit, and say so if not

   You receive

   • An initial feasibility opinion
   • A rough budget range and timeline
   • An NDA first, if you need one
2. 2
   2

   Proposal

   3–7 daysBefore contract

   Before paying anything, you see the requirements and a clickable prototype, and confirm this is what you want.

   Your part

   • Read the requirements document
   • Click through the prototype and point out what is wrong or missing
   • Answer the open questions

   Our part

   • Map the business: background → problems → solution → workflow → value
   • Write the requirements and build a clickable prototype
   • Prepare the proposal (workflows, roles, architecture) and revise with your feedback

   You receive

   • Requirements document (features + open questions)
   • Clickable prototype that opens in a browser
   • Proposal deck

   Why it mattersYou get to use the future system before paying, and confirm it is exactly what you need.

   Approve proposalSee proposal samples
3. 3
   3

   Estimate

   1–2 daysBefore contract

   Effort and cost for every feature, listed line by line, so you can scale to your budget.

   Your part

   • Review the price of each feature
   • If over budget, decide what to cut or move to phase two

   Our part

   • Estimate effort and cost for every feature
   • Quote a fixed total, listing third-party costs such as servers and domains
   • Propose a schedule and payment milestones

   You receive

   • Itemized estimate
   • Schedule and delivery plan
   • Payment milestones

   Why it mattersYou know exactly what each feature costs and can adjust the scope to your budget.

   Approve budget
4. 4
   4

   Contract

   1–3 days40% deposit

   Features, price, acceptance criteria and payment milestones all go into the contract.

   Your part

   • Review and sign the contract
   • Pay the 40% deposit

   Our part

   • Draft the contract with appendices: feature list, estimate, schedule, acceptance criteria, payment milestones, warranty, source-code ownership and confidentiality
   • Set up a project group and assign a project manager

   You receive

   • Signed contract
   • A project manager and group chat
   • Detailed schedule
5. 5
   5

   Development

   2–8 weeks30% midpoint · core features demonstrated

   UI designs first for your approval, then phased development with weekly reports and a test environment you can open anytime.

   Your part

   • Approve the UI designs
   • Check progress weekly and try the test environment
   • Prepare what we need: payment merchant accounts, mini program accounts, domain filing, historical data

   Our part

   • Deliver UI designs first and build after approval
   • Develop in phases with weekly progress reports and an always-on test environment
   • Demo each phase; estimate any new request first and add it only with your consent, or move it to phase two

   You receive

   • UI designs
   • Weekly progress reports
   • Test environment link
   • Phase demos

   Why it mattersFull visibility instead of waiting months to see anything, and a clear rule for changing requirements.

   Approve design
6. 6
   6

   Testing

   1–2 weeks

   We test thoroughly first; then you go through the acceptance checklist. Everything is fixed before launch.

   Your part

   • Work through the acceptance checklist
   • Log any issues in the shared issue list

   Our part

   • Test functionality, desktop / mobile / WeChat compatibility, performance and security
   • Fix every issue and run regression tests

   You receive

   • Test report
   • Acceptance checklist
   • Fix log

   Accept build
7. 7
   7

   Launch

   1–3 days

   Servers, domain and HTTPS set up; mini programs and apps submitted for review.

   Your part

   • Provide business credentials and open the required accounts
   • Confirm the launch date

   Our part

   • Purchase or configure servers, domain and HTTPS
   • Deploy and import initial data
   • Submit mini programs and apps for review

   You receive

   • A live system and its address
   • Administrator accounts

   Mini program review takes about 1–7 days and app store review about 1–2 weeks, depending on the platform
8. 8
   8

   Pilot

   1–4 weeks30% final · after the pilot is accepted

   Real business runs on the system while we stand by and respond the same day.

   Your part

   • Use the system for real work
   • Report issues anytime
   • Sign off at the end of the pilot

   Our part

   • Stand by throughout and respond to issues the same day
   • Make small refinements based on real use

   You receive

   • A stable, running system
   • Acceptance sign-off

   Final sign-off
9. 9
   9

   Handover

   1–3 days

   Training, documentation and source code are all handed over. The system is entirely yours.

   Your part

   • Attend administrator and operator training
   • Receive source code, documents and accounts

   Our part

   • Train on-site or remotely, with recordings
   • Compile all documentation
   • Hand over the repository, servers and every account and key

   You receive

   • Training and recordings
   • Requirements, design, API and deployment docs plus user manual
   • Complete source code and all accounts

   Why it mattersThe system is fully yours. Any team can maintain it, so you are never locked in.

Durations assume a mid-size project with about 30 days of development; the contract schedule governs.

After launch