01 — PROJECT OVERVIEW
Yembo
Making an AI property platform clear and market-ready
I built a flexible visual language for Yembo across product, sales, campaigns, and events—turning complex AI-powered property survey workflows into stories customers could quickly understand.
ROLE
Product designer · visual systems
TIMELINE
18 months
SCOPE
Brand, product storytelling, campaigns, events
02 — CONTEXT
An AI product that was easier to build than to explain
Yembo is an AI-powered property survey platform used by moving and insurance companies to document homes remotely. The technology was sophisticated, but communicating its value required translating technical workflows into something customers could quickly understand. Over eighteen months, I supported customer-facing touchpoints as a connected system rather than isolated requests.
The creator
Drives product discovery but loses attribution, revenue, and ownership of the audience relationship.
The shopper
Moves from inspiration to screenshots, browser tabs, and uncertain product matches.
The market gap
Connect creator taste, AI-assisted product matching, and affiliate commerce in one focused experience.
03 — THE CHALLENGE
Not more assets—one flexible visual language
The company needed to explain complex technology to prospects, existing clients, sales teams, partners, and conference audiences across presentations, campaigns, social media, event graphics, web assets, and product-related interfaces. The core challenge was consistency across different audiences, channels, and levels of detail.
The creator
Drives product discovery but loses attribution, revenue, and ownership of the audience relationship.
The shopper
Moves from inspiration to screenshots, browser tabs, and uncertain product matches.
The market gap
Connect creator taste, AI-assisted product matching, and affiliate commerce in one focused experience.
04 — MY ROLE & COLLABORATION
Working across marketing, sales, product, and events
I translated technical capabilities into accessible customer stories, established reusable campaign patterns, designed sales decks and event collateral, created a structured image direction, supported selected product features, and maintained continuity between the product experience and external brand presentation.
Product stories
Campaign systems
Sales enablement
Event design
Image direction
Product support
05 — VISUAL SYSTEM
A practical visual language for customer-facing communications
VALUE PROPOSITION
Open the app—see outfits that match your style and budget, understand what each look is made of, and keep the ones you love.
Rather than a full rebrand, I established reusable rules for hierarchy, color, typography, graphic elements, and spacing—enough structure for campaigns, sales decks, social content, and event materials to feel recognizably Yembo.
01 · Looks beat garments
People respond to complete visual ideas before individual products.
02 · Two inputs are enough
Style preference and budget provide enough signal for a useful first feed.
03 · Inspiration must be actionable
Every look should break into recognizable, purchasable items.
04 · Saving drives retention
A personal collection gives people a reason to return beyond the feed.
06 — IMAGE DIRECTION
A structured image library, not decorative stock
I created a practical image direction for property categories, survey scenarios, product stories, and campaign needs. The goal was consistent subject matter, believable environments, and repeatable crops rather than one-off decorative imagery.
Feed
Discover
Saved
Profile
Core flow
Feed → Outfit detail → Product decomposition → Similar items → Save look → Saved collection → Return to feed
07 — PRODUCT STORYTELLING
Turning product complexity into a clear sales story
Sales and marketing materials needed to communicate what the technology did and how it affected the customer’s workflow. I used structured hierarchy, diagrams, product visuals, and repeatable page patterns to make technical information easier to scan and present.
01 · Onboarding → personalization → first feed
Ask only for the minimum useful signal, verify the account, set style and budget, then reward the effort immediately with a relevant feed.
02 · Discover an outfit → view details → save
Keep the look visually dominant, reveal product controls only when needed, and make saving feel like the natural next action.
03 · Outfit → product decomposition → similar items
Translate the visual look into understandable items, preserve creator attribution, and offer alternatives without losing context.
04 · Saved collection → revisit → continue browsing
Give saved looks enough structure to become a personal style library rather than a dead-end favorites list.
08 — CAMPAIGN SYSTEM
Building recognizable campaign families
Instead of treating every post as a new design direction, I developed campaign families that could expand across social, web, email, and internal sales channels while remaining recognizably Yembo.
Sketch
Prove the hierarchy and interaction order.
Wireframe
Validate content density, states, and transitions.
Screen
Apply the editorial visual system without adding friction.
09 — MANAGED SURVEY TEAM
Launching the Managed Survey Team
When Yembo introduced its Managed Survey Team offering, the launch needed a campaign that worked across recruitment, announcement, and sales enablement. A single master composition established the look; adaptations carried it across LinkedIn covers, feed posts, and hiring promotion.
Type hierarchy
A compact scale separates editorial titles, product names, price, metadata, and helper copy.
Color roles
Black anchors action and navigation; warm neutrals keep photography dominant; accent color is reserved for meaningful states.
Controls
Pills, filters, buttons, tabs, and save actions share predictable sizing and feedback.
Layout rules
Stable spacing, image ratios, and card anatomy keep the feed varied without becoming visually noisy.
10 — EVENTS
Extending the brand into conferences and live events
Event design brought its own constraints: long-distance readability, limited copy, and recognition in crowded exhibition halls. Large-format graphics, booth panels, screen displays, and event materials translated the same digital-first system into physical space.
Image hierarchy
Feed first, outfit detail second, items third. The interface always makes the creator’s visual idea legible before commerce.
Quality tiers
Hero imagery is protected from aggressive crops; lower-confidence product matches use quieter surfaces and clearer labels.
11 — PRODUCT CONTRIBUTION
Where marketing communication met interface clarity
My role occasionally extended into product-facing details where the same clarity was required: visual inventory, interface concepts, supporting diagrams, and reusable structures that connected customer-facing communication with the product itself.
Empty feed
Explain why no looks match and offer a one-tap way to broaden filters.
Loading
Preserve the layout with image and text placeholders so the feed does not jump.
Network error
Keep the user’s place, state what happened, and provide a clear retry action.
Unavailable item
Retain the outfit context and prioritize close alternatives rather than a dead end.
12 — CROSS-CHANNEL
The same system, from a 90px banner to an email signature
The visual language held together across web calls to action, display banners, email signatures, LinkedIn covers, blog promotion, and interactive tools—formats with radically different sizes, lifespans, and reading distances.
13 — OUTCOMES
What the work changed
One visual language extended across sales, web, social, events, and selected product touchpoints. Technical product information became easier for non-technical audiences to understand, while reusable campaign families and page patterns helped the team produce new materials faster.
Handoff
Annotated flows, reusable components, states, and behavior notes.
Build review
Compared implementation with intent and resolved edge cases with engineering.
TestFlight → launch
Prioritized feedback, refined onboarding, and prepared App Store assets.
14 — REFLECTION
Consistency comes from systems, not static rules
Consistency in a B2B company cannot come from a static set of brand rules alone. It has to come from systems that accommodate different audiences, product stories, content densities, and production timelines.
The strongest result was not a collection of isolated assets, but a shared visual and narrative toolkit that could scale with the company.
The project reinforced the value of designing communication and product touchpoints as one connected experience—clear enough for customers, practical enough for teams, and flexible enough to evolve.