PRODUCT DESIGN · 3 MONTHS
500+ USERS
From a request to someone you trust.
CIRCLE24
Local services, made legible.
A service marketplace should make the relationship legible—not just the listing.
Circle24 helps clients move from a need to a provider they can assess, request and return to—while giving providers a visible path from profile to completed work.
PRE-LAUNCH VALIDATION · 70+ PRIVATE-ROLLOUT TESTERS
PRODUCT DESIGN · 3 MONTHS
500+ USERS · APP STORE · GOOGLE PLAY
From a request to someone you trust.
CIRCLE24
A mobile marketplace for finding, assessing and requesting local services.
CLIENT / SERVICE DETAILS
A service marketplace should make the relationship legible—not just the listing.
Circle24 helps clients move from a need to a provider they can assess, request and return to—while giving providers a visible path from profile to completed work.
PRE-LAUNCH VALIDATION · 70+ PRIVATE-ROLLOUT TESTERS
MOBILE PRODUCT DESIGN
3 MONTHS · 500+ USERS
APP STORE · GOOGLE PLAY
From a request to someone you trust.
CIRCLE24
A mobile marketplace for finding, assessing and requesting local services.
CLIENT / SERVICE DETAILS
A service marketplace should make the relationship legible—not just the listing.
Circle24 helps clients move from a need to a provider they can assess, request and return to—while giving providers a visible path from profile to completed work.
PRE-LAUNCH VALIDATION · 70+ PRIVATE-ROLLOUT TESTERS
ENTRY / THE LANDING EXPERIENCE
Trust starts before the request.
The site explains the marketplace before someone enters the mobile service flow.
circleone24.com
ENTRY / THE LANDING EXPERIENCE
Trust begins before the request.
The landing page explains the marketplace, builds confidence and creates a clear path into the mobile product.
circleone24.com
ENTRY / THE LANDING EXPERIENCE
Trust begins before
the request.
The landing page explains the marketplace, builds confidence and creates a clear path into the mobile product.
circleone24.com
02 / THE HANDOFF
One request.
Two points of view.
The client composes it. The provider reviews it. The context stays attached as the request changes hands.
SERVICE • LOCATION • AVAILABILITY • STATUS •
ONE SHARED
REQUEST
01
02 / THE HANDOFF
One request. Two points of view.
The client composes it. The provider reviews it. Service, location, availability and status stay attached as the request changes hands.
SERVICE • LOCATION • AVAILABILITY • STATUS •
ONE SHARED
REQUEST
01
02 / THE HANDOFF
One request. Two points of view.
The client composes it. The provider reviews it. Service, location, availability and status stay attached as the request changes hands.
SERVICE • LOCATION • AVAILABILITY • STATUS •
ONE SHARED
REQUEST
01
COMPOSED / CLIENT
REVIEWED / PROVIDER
03 / CONVERSATION ANATOMY
Context. Collected in conversation.
The interface makes the need, urgency and location explicit in sequence.
01
NEED
02
CLARIFY
03
LOCATE
VISIBLE CONTEXT
BARBER • URGENT • CURRENT LOCATION
The supplied screen exposes each value before the flow continues.
03 / CONVERSATION ANATOMY
Context is collected inside the conversation.
Instead of forcing a perfect query upfront, the interface makes the need, urgency and location explicit in sequence.
01
HUMAN NEED
“I need a barber urgently”
02
CLARIFICATION
“Confirm your location”
03
EXPLICIT ACTION
“Use current location”
VISIBLE CONTEXT
The request is now specific enough to continue.
NEED
Barber
URGENCY
Urgent
LOCATION
Current location
03 / CONVERSATION ANATOMY
Context is collected inside the conversation.
Instead of forcing a perfect query upfront, the interface makes the need, urgency and location explicit in sequence.
01
HUMAN NEED
“I need a barber urgently”
02
CLARIFICATION
“Confirm your location”
03
EXPLICIT ACTION
“Use current location”
VISIBLE CONTEXT
The request is now specific enough to continue.
NEED
Barber
URGENCY
Urgent
LOCATION
Current location
Every value shown here is visible in the supplied product state.
04 / REQUEST COMPOSITION
Compose.
Then send.
Service choice and location remain visible until the request becomes a live handoff.
FIXED DEVICE / THREE STATES
01 / CHOOSE SERVICE
02 / CONFIRM LOCATION
03 / REQUESTING
CURRENT / 01 CHOOSE A SERVICE
CURRENT / 02 CONFIRM LOCATION
CURRENT / 03 REQUESTING PROVIDER
04 / REQUEST COMPOSITION
A request is composed before it is sent.
Service choice and location remain visible until the request becomes a live handoff to the provider.
FIXED DEVICE / THREE PRODUCT STATES
Choose → confirm → send
The interface changes in place while the request keeps its context.
01 / CHOOSE A SERVICE
02 / CONFIRM LOCATION
03 / REQUESTING PROVIDER
CURRENT PREVIEW / 01 CHOOSE A SERVICE
CURRENT PREVIEW / 02 CONFIRM LOCATION
CURRENT PREVIEW / 03 REQUESTING PROVIDER
04 / REQUEST COMPOSITION
A request is composed before it is sent.
Service choice and location remain visible until the request becomes a live handoff to the provider.
FIXED DEVICE / THREE PRODUCT STATES
Choose → confirm → send
The interface changes in place while the request keeps its context.
01 / CHOOSE A SERVICE
02 / CONFIRM LOCATION
03 / REQUESTING PROVIDER
CURRENT PREVIEW / 01 CHOOSE A SERVICE
CURRENT PREVIEW / 02 CONFIRM LOCATION
CURRENT PREVIEW / 03 REQUESTING PROVIDER
05 / PROVIDER READINESS
A profile that
works.
Identity, service, presentation and availability become working inputs.
01 / PROFILE
02 / SERVICE
03 / COVER
04 / AVAILABILITY
SWIPE THROUGH SETUP
01 / 04
05 / PROVIDER READINESS
A profile is the provider’s operating contract.
Identity, service details, presentation and availability are completed as working inputs—not decorative profile fields.
01 / PROFILE
02 / SERVICE
03 / COVER
04 / AVAILABILITY
05 / PROVIDER READINESS
A profile is the provider’s operating contract.
Identity, service details, presentation and availability are completed as working inputs—not decorative profile fields.
01 / PROFILE
02 / SERVICE
03 / COVER
04 / AVAILABILITY
06 / THE LIVE HANDOFF
Context survives
the handoff.
Price, distance, urgency and location remain visible as the request changes hands.
REQUEST 024 / LIVE
Four visible events.
01 CREATED
02 RECEIVED
03 ACCEPTED
04 ONGOING
PROVIDER / REQUEST RECEIVED
CLIENT / RESOLVED
Provider accepted
Same request, confirmed state.
06 / THE LIVE HANDOFF
Context survives the handoff.
Price, distance, urgency and location stay attached as the request moves from client intent to provider action.
REQUEST 024 / LIVE STATE
One request. Four visible events.
01 / CREATED
Client sends service, location and date.
02 / RECEIVED
Provider sees price, distance and urgency.
03 / ACCEPTED
Client receives a resolved provider state.
04 / ONGOING
The same job moves into active work.
PROVIDER / REQUEST RECEIVED
CLIENT / RESOLUTION
PROVIDER ACCEPTED
06 / THE LIVE HANDOFF
Context survives
the handoff.
Price, distance, urgency and location stay attached as the request moves from client intent to provider action.
REQUEST 024 / LIVE STATE
One request. Four visible events.
01 / CREATED
Client sends service, location and date.
02 / RECEIVED
Provider sees price, distance and urgency.
03 / ACCEPTED
Client receives a resolved provider state.
04 / ONGOING
The same job moves into active work.
PROVIDER / REQUEST RECEIVED
CLIENT / RESOLUTION
PROVIDER ACCEPTED
07 / SERVICE IN MOTION
Work becomes a
shared timeline.
Every service state stays visible.
01
PAID
02
ACCEPTED
03
ACTIVE
04
DONE
CLIENT / LIVE TIMELINE
PROVIDER / ACTIVE JOB
The same request is now operational.
Status can move without losing the client context.
07 / SERVICE IN MOTION
Work becomes a shared timeline.
Payment, acceptance, progress and completion remain legible while the service is underway.
01
PAYMENT COMPLETE
Funds are confirmed.
02
REQUEST ACCEPTED
The provider has committed.
03
SERVICE IN PROGRESS
Work is actively underway.
04
SERVICE COMPLETE
Closure remains visible.
CLIENT / LIVE TIMELINE
PROVIDER / ACTIVE JOB
UPDATE STATUS
07 / SERVICE IN MOTION
Work becomes a
shared timeline.
Payment, acceptance, progress and completion remain legible while the service is underway.
SHARED REQUEST STATE
One job.
Four accountable moments.
The client can see what has happened, when it happened and what remains.
01
PAYMENT COMPLETE
Funds are confirmed.
02
REQUEST ACCEPTED
The provider has committed.
03
SERVICE IN PROGRESS
Work is actively underway.
04
SERVICE COMPLETE
Closure remains visible.
CLIENT / LIVE TIMELINE
PROVIDER / ACTIVE JOB
UPDATE STATUS
08 / TRUST AFTER DELIVERY
Trust travels
forward.
A review becomes visible evidence that helps the next client decide.
02 / VISIBLE SIGNAL
01 / INPUT
REVIEW
03 / OUTPUT
TRUSTED PROFILE
08 / TRUST AFTER DELIVERY
Trust becomes visible.
A review is not decorative feedback. It becomes visible evidence that helps the next client decide.
01 / CLIENT INPUT
02 / VISIBLE SIGNAL
03 / TRUSTED PROFILE
08 / TRUST AFTER DELIVERY
Trust becomes
visible.
A review is not decorative feedback. It becomes visible evidence that helps the next client decide.
01 / CLIENT INPUT
Quality and communication are selected explicitly.
02 / VISIBLE SIGNAL
03 / TRUSTED PROFILE
Verification, jobs and reviews remain attached to the provider.
09 / AFTER THE SERVICE
The system stays
in motion.
Repeat requests and payouts stay visible.
CLIENT / COMPLETED REQUESTS
Request again.
A completed service remains actionable.
PROVIDER / WALLET
Track the payout.
Payout and activity remain visible.
09 / AFTER THE SERVICE
The system stays in motion.
Completion produces two supported next actions: request the service again, or account for the provider payout.
CLIENT / COMPLETED REQUESTS
Request again.
A completed service remains actionable.
PROVIDER / WALLET
Account for the work.
Payout and activity remain visible.
09 / AFTER THE SERVICE
The system stays
in motion.
Completion produces two supported next actions: request the service again, or account for the provider payout.
CLIENT / COMPLETED REQUESTS
Request again.
A completed service remains actionable.
PROVIDER / WALLET
Account for the work.
Payout and activity remain visible.
REFLECTION / ONE CONNECTED SERVICE
Designed for both sides of the service.
Circle24 connects request composition, provider readiness, live service states, trust and payout into one two-sided experience—so both sides can understand what happened, what is active and what comes next.
500+ USERS
LIVE ON APPLE APP STORE + GOOGLE PLAY
REFLECTION / ONE CONNECTED SERVICE
Designed for both sides of the service.
Circle24 connects request composition, provider readiness, live service states, trust and payout into one two-sided experience—so both sides can understand what happened, what is active and what comes next.
500+ USERS · LIVE ON APPLE APP STORE + GOOGLE PLAY
REFLECTION / ONE CONNECTED SERVICE
Designed for both sides
of the service.
Circle24 connects request composition, provider readiness, live service states, trust and payout into one two-sided experience—so both sides can understand what happened, what is active and what comes next.
500+ USERS · LIVE ON APPLE APP STORE + GOOGLE PLAY