Map the process, review mockups, then build in small batches. No need to define everything up front.
Why a different approach
Requirements get locked in on day one, and clients see nothing until the end.
Result: You get what the spec says, not always what your team needs.
Result: Every step is visible, so a wrong turn gets fixed early.
Project Management Process
Every phase ends with something you can see and discuss.
Your goals, users and current tools.
DeliverableInterview notes and preliminary scope
Map the current process and find the bottlenecks.
DeliverableAS-IS / TO-BE process flowcharts
View example ↓Clickable screens to discuss and refine.
DeliverableInteractive, operable prototype
View example ↓Small batches, each one ready to use.
DeliverableOne usable version per batch
See how it works ↓Keep improving based on real use.
DeliverableLive system with continuous iteration
Step 02 · Process Analysis
We map how work happens today, so everyone can see what really needs fixing.
AS-ISPurchase Request Process
TO-BEPurchase Request Process
Example illustration. Actual content depends on interview results for each project.
Step 03 · Mockup
Before writing code, we build a clickable prototype and refine it with you until it's right.
Client commentCan we filter by sales rep here?
Client commentAdd a “Waiting for documents” status?
Step 04 · Phased Development
Many needs only appear once people use the system, so we build in small batches you can adjust or pause.
Anything that comes to mind. One sentence is enough
We estimate time and cost per item and pick what goes into this batch
A small scope, ready to use as soon as it's done
Real use shows what the next batch should be
How the system grows batch by batchExample
You don't need every requirement up front.
See it, use it, then decide.
HEISO PROJECT PRINCIPLE
Who does what
You explain how your business works. Heiso handles design, development and testing.
| Phase | What you need to do | Heiso handles |
|---|---|---|
| 01Requirements Interview | Share business goals, current situation, and challenges (approx. 1-2 hours). | Summarize interview highlights, propose preliminary scope. |
| 02Process Analysis | Confirm if the flowchart accurately reflects the actual process. | Draw current and improved process flows, identify bottlenecks. |
| 03Mockup | Interact with the prototype, leave feedback on the screens. | Design screens, modify based on feedback until finalization. |
| 04Phased Development | Propose requirements for each batch, collaboratively prioritize. | Develop, test, and regularly demonstrate progress. |
| 05Launch & Improve | Use the system, report issues and new ideas. | Deploy, maintain, and continuously improve. |
Pricing
Each batch is quoted before work starts. When it's done, you decide on the next one.
Phase One
Interview + process analysis + mockup
[NT$__]Fixed Price
Phase Two
Split by requirement, each batch quoted separately
Quoted per batchbased on scope
Phase Three
Hosting, monitoring and small day-to-day changes
[NT$__]/ month
Example: Core workflow in 3 batches, about [NT$__]–[NT$__]. Start with batch 1 and decide from there.
No. Each batch is priced before work starts, and new requests are quoted as a separate batch.
Yes. You can pause after any batch, and everything delivered keeps working.
Yes. Discovery ends with a batch plan and budget range.
Each batch has a [30]-day warranty. Fixes in that period are free.
Why it works
Small batches catch a wrong turn early.
Every batch gives you something you can use.
The most valuable features come first.