PROJECT 01 / ZONALYZE
A clearer way to think about location.
Opening a business involves a lot of guessing. Zonalyze is our attempt to make one part of it clearer: choosing the right location.
DEMO LOCATION PROFILE
COFFEE SHOP FEASIBILITY
SELECTED BUSINESS LOCATION
SELECTED RADIUS
EXPECTED CUSTOMERS
45PER DAYESTIMATED REVENUE
$24KPER MONTHDEMAND
HighRISK
Medium- POPULATION
- 14,200
- STUDENT / YOUNG ADULT
- 65%
- COMPETITION
- 9 nearby shops
- RATIO
- 1 shop per 1,577 people
This visual was created for the portfolio to show the project idea clearly.
01 / CONTEXT
What we were trying to solve
Choosing a business location involves population, competition, costs and expected demand. These details often sit in different places, which makes comparison difficult.
Zonalyze brings them into one location-based view so a user can change the area, business type and assumptions before comparing the result.
02 / MY PART
The part I worked on
I worked on the customer and revenue side of the platform. My part estimates demand, expected customers and possible monthly revenue based on the selected area.
The demand-level control lets the assumptions change before the customer and revenue estimates are read. Those values are presented as estimates, not guaranteed forecasts.
03 / SYSTEM
How it comes together
The result becomes easier to read when the inputs and assumptions stay visible beside it.
- 01Location and radius
- 02Business type
- 03Population and age mix
- 04Competitor context
- 05Demand assumptions
- 06Customer estimate
- 07Revenue estimate
- 08Risk and opportunity summary
04 / PROJECT VIEW
From a selected area to a usable estimate.
The supporting views separate the forecast from the inputs that shape it, then show how that information moves through the wider platform.
DEMO FORECAST / CUSTOMER + REVENUE
SELECTED AREA
- POPULATION
- 14,200
- YOUNG-ADULT SHARE
- 65%
- NEARBY COFFEE SHOPS
- 9
SYSTEM FLOW / ESTIMATE PATH
05 STEPS
- 01AREA + RADIUS→
- 02BUSINESS TYPE→
- 03DEMAND ASSUMPTIONS→
- 04CUSTOMER ESTIMATE→
- 05REVENUE + RISK
05 / REFLECTION
What I learned
An estimate is more useful when its assumptions are easier to understand than its headline number.
- 01
Several inputs have to become one result without hiding where it came from.
- 02
My module had to fit into a larger team project and keep frontend and backend data consistent.
- 03
Forecasts are clearer when uncertainty is part of the presentation.
WHERE IT STANDS NOW
An eight-month capstone project developed as a team.
The portfolio presentation uses demonstration values to explain the project idea clearly.