All projects
Cover image coming soon

Industrial real estate · Product design · Design system · July 2025 to September 2026

Investtal

From July 2025 to September 2026, I was Investtal's product designer, responsible for five products for a three-sided industrial real estate marketplace: the public website, the broker CRM, a mobile app, an admin console, and the design system they share.

Role Product Designer
Timeline July 2025 to September 2026
Tools Figma · Design tokens · React · Storybook
Platform Web · iOS and Android
Scope of work 5 products · 60+ feature areas
5 languages · 1 design system
01 · Context

A marketplace with three sides and long deals

Investtal is an industrial real estate marketplace in Vietnam for land, factories, and industrial parks. It connects three groups: businesses looking for space, brokers who market it, and the investors and owners who supply it. A single deal can run for weeks.

Each side works in a different place. Businesses browse the public website; brokers work in a CRM built around tables, filters, and quick actions, and in a mobile app away from the desk; owners manage their projects and decide what goes public.

My scope covered five products: the website, the CRM, the mobile app, the admin console, and the design system that keeps them consistent. As of September 2026, the product was still in development and had no users.

5products
60+feature areas
5languages: English, Vietnamese, Chinese, Japanese, Korean
The public website's project page, the CRM dashboard and project list, and the broker app on mobile.
02 · Discovery

Decide what to test before building more

Define activation for each side. Before adding features, I wrote down what a first sign of value looks like for each group, with a time window: a business sends an inquiry within 48 hours, a broker posts a first listing or claims a lead within 72 hours, an owner publishes a listing that gets at least one view within seven days.

The baselines and targets are marked as assumptions, to be replaced once there is a real funnel to measure.

Map the opportunities, then name the riskiest assumption. For each side I listed the needs and fears behind a drop-off, chose one opportunity, sketched three solutions, and wrote a small proof of concept with criteria to continue or stop. For owners, the riskiest assumption is that fear of exposing the price, not usability, is what stops them publishing.

Seed supply first. The three trees depend on each other: businesses leave when listings are empty, and brokers need real listings to work with. So the tests start with owners, letting them publish with the price hidden, then turn listings into inquiries, then show brokers real leads.

Activation for the three groups: the event, its time window, an earlier signal, and assumed targets.
The opportunity tree for owners: the outcome, four reasons they give for not posting, three solutions for the one chosen, the riskiest assumption, and the first test.
The overall priority: supply before demand, and the order of the three tests.
03 · Supply side

Give owners control over what goes public

Choose what goes public. Each section of a project page is tagged live or unpublished, and a panel counts the changes not yet made public. When publishing, the owner picks the sections that appear on the website and confirms the figures, while sensitive data such as cost price and internal notes stays private. Stopping takes the page offline but keeps its data.

Match the interface to permissions. A broker who adds a project or an asset can view it and add documents; editing, asset management, and authorization open only after an admin or the project owner approves. The completion screen says so up front and names who will review.

Hand lots to brokers, and keep the handover visible. Owners authorize brokers lot by lot, for sale or rent, whole or in parts, with a price and a time limit. The project page then shows each lot's broker and days left, warns when fewer than ten remain, and flags a lot that has been authorized for 18 days without a listing.

Two alternatives for this overview, and the reasons for dropping them, are kept in the decision notes.

Publishing a project: each section shows whether it is live or unpublished, the owner picks which sections go public, and can stop publishing.
After a broker adds a project or an asset, they can view it and add documents; editing opens once an admin or the owner approves.
The authorization overview with assigned brokers, time remaining, and expiry warnings, beside one lot's authorization detail.
04 · Activation and deals

Point each role to a first step, then carry the deal through

A first step for each role. Right after sign-up, a popup points each role to its activation event: businesses describe what they need, brokers take on an authorized project, owners add a project. Until there is data, the empty dashboard leads with the same step.

One screen for the whole deal. A deal moves through seven stages, from creation to handover. The deal screen stays the same; the banner at the top changes with the stage and names the next action, such as updating the broker contract or recording the deposit.

Show where the money stands. At the payment stage, a deal lists each milestone with its due date, amount, and status (completed, awaiting confirmation, awaiting payment) and shows the balance left, so both sides can see what has been paid and what comes next.

What each role sees after sign-up: one activation popup per role, and the empty broker and owner dashboards.
One deal on mobile across six of its seven stages, from consultation to handover.
A deal at the payment stage: its value, each milestone's due date, amount, and status, and the balance left to pay.
05 · Design system

One system for web and mobile

Shared tokens, different density. The website, CRM, and mobile app use the same semantic colors, type scale, and light and dark values. The website stays open and image-led; the CRM uses compact controls, aligned numbers, and status colors for scanning tables.

Keyboard and states before handoff. Handoff requirements include keyboard operation, visible focus, names for icon-only buttons, and dialogs that close with Escape. The quick-action palette shows its keys, states carry cues beyond color, and mobile touch targets are specified at 44px.

Semantic colors in light and dark mode, and the type scale, from the shared foundations.
Keyboard support in the CRM: the quick-action palette with arrow, Enter, and Esc hints, and list-item states from default to selected.
06 · My role

From Figma to a native app and shared code

I was responsible for product design from the start and kept the Figma files and decision notes current across more than 60 feature areas. The broker app has its own Figma file, designed for native iOS and Android rather than shrunk from the web. Its AI listing drafts come as numbered versions with a limited number of generations and a history, and nothing changes until the broker applies one.

I also contributed code to the design system, where tokens sync into a React component library documented in Storybook. When I left, the product had no users yet, so there are no outcome figures; the next step I handed over was running the three proofs of concept from discovery.

The broker app: an AI listing draft with versions and history, a client's profile, and a project page.

Get in touch

Need design help with your project?

Tell me about your product, your team, and where you need support. We can start there and see how I can help.