Go from zero
to a useful first version.
A website, mobile app, admin system, or supporting tool. Define the core users and essential flow, then deliver a first version that can be used and validated.
BUILD WITH HUOYE
Have an idea?
Let’s make it real.
A new product, an existing system, or an idea that is still taking shape. Start with the problem and the goal. Together, we’ll decide what to build first, how far to take it, and turn it into something ready to deliver.
START WHERE YOU ARE
From a problem.
To a product.
You do not need a complete brief. A goal, a difficult workflow, or a product already in use can all be the start of a useful conversation.
Go from zero
Make a product
in use work better.
Find friction in real feedback, then improve the flow, interface, and feature priorities. Focus effort where it matters most to people and the business.
Turn repetitive work
into a reliable flow.
Bring scattered information together, reduce repeated steps, and build an internal tool or automation around how the team already works.
HOW WE WORK
Align first.
Then build.
Agree on scope, stages, delivery, and acceptance first. Review real work during development, assess the impact of changes, and decide together.
- 01
Clarify the problem
Who uses it? Where are they stuck? What should change? We align on the goal, existing materials, technical constraints, timing, and budget.
- 02
Set the scope for this project
Define priorities, stages, deliverables, and acceptance. Make clear what comes first and what can wait.
- 03
See progress at every stage
Review working pages, real interfaces, or stage deliverables. You can see the direction early and adjust while the cost of change is controlled.
- 04
Accept and hand over
Check the result against the agreement, hand over the relevant source and materials, and clarify deployment, launch, accounts, and support.
BEFORE WE BEGIN
Clear answers.
Before we begin.
Can we start with only an idea?
Yes. Start with the problem, who it is for, and what is still uncertain. Sketches, references, or an existing product help, but a complete proposal is not required.
How long will it take, and what will it cost?
This depends on scope, target platforms, existing materials, and connected systems. We first confirm the conditions that affect the work, then propose suitable stages, timing, and cost.
How are source, design assets, and accounts handed over?
Source code, design assets, deployment notes, account ownership, and launch responsibilities are written into the delivery agreement and handed over as agreed after acceptance.
Can you maintain or extend it after launch?
Yes. Fixes, ongoing maintenance, and new features are scoped separately, with the response, timing, and cost agreed for each.
START WITH A CONVERSATION
Tell us
what you want to solve.
You do not need a formal proposal. Send a short email with what you already know; we can bring the remaining questions into focus together.
A short email can include
- The problem you want to solve and who it is for
- What you already have: a product, sketch, reference, or API
- When you hope to use it and a budget range, if known