Case 02 — AI Local Search Optimization
Sinal
Local search fixes humans can trust, review, and scale.
Role
Product Design — end-to-end (0→1)
Scope
0→1 product design · AI recommendation UX · Review and approval flows · Multi-location workflows
Year
2025
$1M
ARR within 90 days of launch
71
Enterprise accounts actively adopted
+130%
Local adoption vs. accounts without the workflow
● Play with a live prototype of this project
Filter recommendations, select location groups, approve or reject profile updates.
Search optimization
Recommendations
Needs review
6
Current view
6
Approved locations
0
Context
Sinal is the anonymized version of a 0→1 AI-powered local search optimization product designed for a B2B SaaS platform for multi-location brands.
Enterprise brands manage hundreds or thousands of locations across search, listings, reputation, social, and local marketing. Corporate teams needed visibility across every location, while local teams needed simple, actionable guidance without becoming SEO experts.
Problem
Local search optimization was high-value, but too manual, fragmented, and technical to scale.
Teams had to find issues across many locations, understand which business fields needed to change, and manually update details like hours, services, categories, and attributes. The design challenge was turning AI recommendations into clear, trustworthy actions that enterprise teams could review, approve, and scale.
Process
- 01Made AI explainableEvery recommendation had to show what was wrong, why it mattered, which locations were affected, and exactly what would change before anything went live.
- 02Kept humans in controlBecause Sinal affected public business information, the workflow supported review, edit, approve, and reject states instead of treating AI as an auto-publisher.
- 03Designed for multi-location scaleThe product had to work for one location, a regional group, or an account-level fix without forcing users to approve the same change hundreds of times.
- 04Positioned it as a workflow, not a reportRecommendations moved from insight to action through grouped opportunities, affected-location context, editable proposed changes, and scalable approval patterns.
Insight
Trust — not accuracy — was the real barrier to AI adoption.
Teams didn't hesitate because the AI's suggestions were wrong; they hesitated because the changes touched public business data and they couldn't see what would go live. That reframed the work from "make smart recommendations" to "make every recommendation explainable, reviewable, and reversible."
Trade-offs
- 01Human-in-the-loop over full automationAuto-publishing would have felt faster and more magical, but a single wrong change to a public profile erodes trust permanently. I chose review, edit, approve, and reject states — less automated in feel, far safer to adopt at enterprise scale.
- 02Grouped bulk approval over per-location reviewReviewing each location was the most precise option but couldn't scale across hundreds of profiles. Grouping identical issues into one decision traded some granularity for the scale enterprise teams actually needed.
- 03Explainability over a leaner UIShowing what's wrong, why it matters, and current-vs-proposed values added visual weight — but without it, teams wouldn't trust a change enough to approve it.
Proposal
AI finds the local search gap; people decide what goes public
- Opportunity list
- Affected locations
- Current vs proposed fields
- Edit / approve / reject
- Bulk approval
- ↑ Prototype above
Result
- 01Explainable recommendations teams could trustEvery recommendation showed what was wrong, why it mattered, and exactly which fields would change — so enterprise teams understood each fix before it went public.
- 02Human control at every stepEdit, approve, and reject states kept AI under human review instead of auto-publishing changes to live business profiles.
- 03One decision, hundreds of locationsGrouped opportunities and bulk approval let teams fix identical issues across a whole location group without approving the same change hundreds of times.
- 04Workflows for centralized and local teamsAccount-level and local-level flows supported corporate oversight and distributed on-the-ground teams from the same product.
- 05Delivered a major AI product milestoneThe 0→1 product reached $1M ARR within 90 days of launch, with +130% local adoption among accounts using the workflow versus those without.
Next case
Aura
Fast answers, with the source one click away