HEISO · How We Work
Heiso's project process
Every step
visible and adjustable.
Map the process, review mockups, then build in small batches. No need to define everything up front.
Interview
Process Analysis
Mockup
Phased Development
Launch & Improve
Why a different approach
Too many software projects
turn out to be the wrong thing.
Requirements get locked in on day one, and clients see nothing until the end.
Traditional Approach
Everything fixed up front
Dozens of pages of specs,
signed off before anyone has seen a screen
Months of development,
with little visibility into progress
The product appears at final acceptance,
and every change costs extra budget and time
Result:
You get what the spec says, not always what your team needs.
Heiso's Approach
Adjust as you go
Map the current process first
to find where work really gets stuck
Mockups first,
code only after the screens are agreed
Requirements in batches,
each one usable as soon as it's done
Result:
Every step is visible, so a wrong turn gets fixed early.
Project Management Process
Five steps, each with a real deliverable
Every phase ends with something you can see and discuss.
Deliverable
Requirements Interview
Your goals, users and current tools.
Interview notes and preliminary scope
Process Analysis
Map the current process and find the bottlenecks.
AS-IS / TO-BE process flowcharts
View example ↓
Mockup
Clickable screens to discuss and refine.
Interactive, operable prototype
View example ↓
Phased Development
Small batches, each one ready to use.
One usable version per batch
See how it works ↓
Launch & Improve
Keep improving based on real use.
Live system with continuous iteration
Step 02 · Process Analysis
Understand the work first,
then decide what system to build.
We map how work happens today, so everyone can see what really needs fixing.
Who does what
Who owns each step and who it goes to next
What tools are used
Excel, email, LINE, paper: where the data lives
Where are the bottlenecks
The slowest, most error-prone steps
Purchase Request Process
AS-IS
Staff fill in a paper form
Paper form routed to manager for sign-off
1–2 days on average
Purchasing re-types it into Excel
Slow · Error-prone
Requester notified by email
TO-BE
Request submitted online
Manager approves on mobile
Instant notification
Data compiled automatically
No manual entry
Requester sees live status
Example illustration. Actual content depends on interview results for each project.
Step 03 · Mockup
See the screens first,
then decide what to build.
Before writing code, we build a clickable prototype and refine it with you until it's right.
No imagining
Try it instead of reading a spec
Find problems early
Fixing a screen costs far less than fixing code
Easy internal alignment
Everyone discusses the same screen
Client comment
Can we filter by sales rep here?
Add a “Waiting for documents” status?
Step 04 · Phased Development
Add requirements as you go.
No need to know everything up front.
Many needs only appear once people use the system, so we build in small batches you can adjust or pause.
Raise a need
Anything that comes to mind. One sentence is enough
Estimate & prioritize
We estimate time and cost per item and pick what goes into this batch
Build & deliver
A small scope, ready to use as soon as it's done
Use & give feedback
Real use shows what the next batch should be
Batch done, back to A
How the system grows batch by batch
Example
Batch 1
Core workflow
goes live and the team starts using it
Batch 2
Improvements from feedback:
reports, notifications, permissions.
Batch 3
Wider scope:
integrate with existing systems, roll out to other departments.
You don't need every requirement up front.
See it, use it, then decide.
HEISO PROJECT PRINCIPLE
Who does what
Your part in each phase is small
You explain how your business works. Heiso handles design, development and testing.
Phase
What you need to do
Heiso handles
Requirements Interview
Share business goals, current situation, and challenges (approx. 1-2 hours).
Summarize interview highlights, propose preliminary scope.
Process Analysis
Confirm if the flowchart accurately reflects the actual process.
Draw current and improved process flows, identify bottlenecks.
Mockup
Interact with the prototype, leave feedback on the screens.
Design screens, modify based on feedback until finalization.
Phased Development
Propose requirements for each batch, collaboratively prioritize.
Develop, test, and regularly demonstrate progress.
Launch & Improve
Use the system, report issues and new ideas.
Deploy, maintain, and continuously improve.
Pricing
Every batch is quoted first,
and work starts only after you approve.
Each batch is quoted before work starts. When it's done, you decide on the next one.
Once approved
After launch
Phase One
Discovery & planning
Interview + process analysis + mockup
[NT$__]
Fixed Price
Delivers process maps and a clickable prototype
Credited toward the first batch if you continue to development
Ends with a recommended batch plan and budget range
Phase Two
Batch development
Split by requirement, each batch quoted separately
Quoted per batch
based on scope
Quote within [1–2] business days of receiving a request
Scope, price and timeline confirmed before work starts
New requests raised mid-batch go into the next batch
Each finished batch can be accepted and used right away
Phase Three
Ongoing maintenance
Hosting, monitoring and small day-to-day changes
[NT$__]
/ month
Includes [__] hours of changes per month
Larger new features are quoted as new batches
Example:
Core workflow in 3 batches, about [NT$__]–[NT$__]. Start with batch 1 and decide from there.
If requirements keep growing, will costs get out of control?
No. Each batch is priced before work starts, and new requests are quoted as a separate batch.
Can we pause partway through?
Yes. You can pause after any batch, and everything delivered keeps working.
Can we know the total budget in advance?
Yes. Discovery ends with a batch plan and budget range.
What if we find a bug after launch?
Each batch has a [30]-day warranty. Fixes in that period are free.
Why it works
Small steps are safer than one big leap
Lower Risk
Small batches catch a wrong turn early.
Visible Progress
Every batch gives you something you can use.
Budget where it counts
The most valuable features come first.
Ready to get started?
Let Heiso be your digital transformation partner for the AI era.
Contact Us
https://www.heiso.io/contact