Requirement
Can be turned into an acceptance item and maps to a business goal
Digital Product Solutions
Your product journey needs a companion, not a vendor
From strategy through operations, the eight stages can be taken separately. Each stage delivers documents you can accept. Billing is by actual hours throughout.
The problem is not “we cannot build it.” It is “we built the wrong thing.”
Most failed digital-product projects were finished, technically.
The break happens earlier: what the client said was treated as a requirement and work started immediately.
We keep these two things apart:
Expectation
Unconfirmed, not written down, and cannot be turned into an acceptance item
Expectations are not wrong. Every project starts as a pile of them. What is wrong is skipping the translation step and going straight to build—then both sides argue afterward that “this was obviously included.”
Our work starts by translating expectations into requirements. If it cannot be written as an acceptance item, it does not enter development.
Four mechanisms
- 1
Staged engagement
Eight stages: strategy, service flow and requirements, prototype, feasibility, system design and build, test and validation, launch, and operations.
You do not have to take all of them. You can stop after strategy and requirements and tender the documents yourself, or bring us in only for later build and test.
- 1Strategy
- 2Service flow and requirements
- 3Prototype
- 4Feasibility
- 5System design and build
- 6Test and validation
- 7Launch
- 8Operations
- 2
Every item can be verified
Acceptance items have a clear bar—another person must be able to verify them without guessing intent:
❌ Not accepted ✅ Write it like this ❌ Not acceptedThe feature works ✅ Write it like thisEntering an invalid promo code shows “Invalid promo code” and the checkout button stays disabled ❌ Not acceptedThe UI is fine ✅ Write it like thisForm error messages appear under the field and the field border turns red ❌ Not acceptedLooks OK ✅ Write it like thisThe API response matches section 3 of the specification Each item covers five states: normal, boundary, error, empty, and permission.
- 3
Billed by actual hours. Operations too.
Build is billed by actual hours. After launch, operations has no fixed monthly fee—only hours that were worked. A month with no maintenance is zero.
- 4
See progress directly. Skip the weekly recap.
You get access to the project Monday.com board—status, estimated hours, actual hours, and acceptance items for every task, anytime.
Billing by actual hours only works if hours can be inspected. We do not use a weekly recap as the source of truth, because a recap is an edited version. The board is the original.
You know what we will do, and for how long, before work starts
Whatever stages we take on, we provide:
| Deliverable | What it contains |
|---|---|
| DeliverableWork-item list | What it containsBroken into concrete items of estimable size, each with acceptance criteria |
| DeliverableHour estimates | What it containsEstimated effort per item. You see the total before work starts |
| DeliverableSchedule sheet | What it containsA timeline from available hours, for you to confirm and adjust |
| DeliverableEnvironment and handover notes | What it containsA close-out requirement covering deploy and environment setup |
The work-item list, hour estimates, and schedule are given to you to confirm and adjust. We do not decide unilaterally and then notify you.
Environment and handover notes are a close-out requirement, not an extra. Without them the project is not done—which means you can hand the product to another team at any time and are not locked in.
How we work and how we bill
Estimate first, then decide whether to build
| Item | Fee |
|---|---|
| ItemSystem development estimate and quote | FeeNT$21,200 / engagement |
From your initial brief we assess system size, complexity, and effort, and produce a written effort estimate and quote.
If you confirm development within 30 days of receiving the quote, this fee is credited in full against development. In other words: if you proceed, the estimate is effectively free. If you do not, you still leave with a complete estimate you can take elsewhere.
Hourly rates
| Item | Rate |
|---|---|
| ItemDiscovery and specification | RateNT$3,800 / hour |
| ItemUI and page design | RateNT$3,800 / hour |
| ItemFrontend development | RateNT$3,030 / hour |
| ItemBackend development | RateNT$3,030 / hour |
| ItemIntegration testing | RateNT$3,030 / hour |
| ItemConsulting | RateNT$6,700 / hour |
| ItemOperations and maintenance | RateActual hours at the matching rates above. No fixed monthly fee |
2026 rates, New Taiwan dollars, excluding tax.
Discovery and specification is billable work. We do not treat it as a free pre-sale—how well that step is done decides everything after it.
Project-size reference
We recommend splitting by phase. Each phase is about 2–3 months, around NT$600,000–700,000. Actual cost follows the estimated hours after the work is broken down.
Team mix
Staffed to project size. May include consultant, project management, frontend, backend, architect, animator, and UI/UX designer.
Then how do I set a budget?
The cost of billing by actual hours is explicit: you cannot know the total at signing.
Our approach:
- Break tasks to an estimable size. 1–4 hours is best. Over 8 hours must be split again
- Every task has an hour estimate. You see the total before work starts
- Variance has a bar: ±20% is normal, ±50% needs a reason, over 100% we revisit how the work was split
- Early warning beats later explanation: we tell you and update the schedule when variance appears, not on delivery day
A fixed quote hides risk inside the number. You pay a risk premium. Billing by actual hours puts the risk on the table. You pay for what actually happened.
Technical scope
We stay with React, React Native, Vue, and Python, covering web, app, backend, and data work. We do not chase breadth of stack. We go deep in what we know.
A good fit
- Organizations whose needs are not fully settled and who need someone to think it through with them
- Companies with an internal team that need a specific stage or role filled
- Products whose post-launch maintenance is uneven and that do not want to pay for idle months
- Organizations that care about handover documents and the ability to switch teams
- Clients who want to see project progress directly, not a polished weekly recap
Not a fit
- Procurement that must lock a total price at signing
- Projects that specify a stack outside React, React Native, Vue, and Python
- Projects whose spec is already complete and that only want the lowest-cost build
FAQ
Can we take only some of the stages?
Yes. All eight stages can be taken separately. A common mix is strategy and requirements only, then tendering the documents; or taking only build and test.
If you bill actual hours, how do I control budget?
Before work starts you get a work-item list, hour estimates, and a schedule sheet to confirm and adjust. Tasks are split to an estimable 1–4 hours. When variance exceeds the bar we warn you and update the schedule. If you want a full estimate before committing, buy the system development estimate and quote first.
Is the estimate billed separately?
Yes, NT$21,200 per engagement. If you confirm development within 30 days of receiving the quote, the fee is credited in full against development. If you decide not to proceed, the fee is not refunded. You keep the complete effort estimate and quote.
Is operations really without a monthly fee?
Yes. Only hours that were worked are billed. A month with no maintenance generates no fee.
Which technologies do you use?
React, React Native, Vue, and Python. We do not take projects outside this scope.
How is progress tracked?
You get access to the project Monday.com board and see status, estimated hours, actual hours, and acceptance items for every task. We do not use a weekly recap as the main progress sync.
Team size and roles?
Staffed to project size. May include consultant, project management, frontend, backend, architect, animator, and UI/UX designer.
How long and how much is a typical project?
We recommend splitting by phase. Each phase is about 2–3 months, around NT$600,000–700,000. Actual cost follows the estimated hours after the work is broken down.
What if we want to change teams mid-way?
Every stage has deliverables you can accept. Environment and handover notes are a close-out requirement. You can take the documents to another team at any time.
Get clear on what needs to be done
The first call confirms three things: the business problem you want to solve, your current organization and tech, and which expectations have not yet been translated into requirements. That conclusion decides which stage you start from.
Book a discovery call