Dribbble Finance Site

About the Authors:
Garik Avetisyan, Davit Gabrielyan, and Anastasia Saroka are co-founders of Flexy Global, a design and development partner for startups and global enterprises. Garik built and successfully exited a consumer app used by millions. Davit brings 15 years of experience leading complex projects and operations at international companies including Orange (France Telecom) and Coca-Cola Hellenic. Anastasia, Design Director at Flexy Global, brings experience designing products for large corporations and startups in the fitness industry. Together, they explore how better design systems and development practices can help teams build complex technology more clearly and efficiently.

On a recent enterprise software project, we were working with a Figma file that needed to support both traditional developer handoff and AI-assisted development. One section alone contained dozens of screens documenting a single part of the product.

Each screen made sense on its own. The difficulty was understanding how they belonged together.

For the designers and developers who had worked on the project for months, much of that context was already familiar. We knew which screens represented the starting point, what action caused each change, which states were alternatives, and which details were still under discussion.

A coding agent coming to the file had none of that background. An individual screen did not provide enough context to explain the complete behavior, while the full canvas introduced too much unrelated information. We needed a way to organize the relevant frames, states, and decisions around a single interaction so they could be understood and used more effectively in AI-assisted development. That need became the basis of our Box Design System.

What is the Box Design System?

The Box Design System is our method for organizing complex product behavior into bounded sections of the Figma canvas. Each box contains the screens, states, transitions, annotations, and implementation context needed to understand one part of the product. This makes the file easier for people to navigate while also preparing its structure for AI-assisted development.

In the enterprise platform we were designing, navigation alone included several connected behaviors. Users could interact with a floating bar, select assets, explore the map directly, or move through a hierarchy. All of these actions occurred within the same broader interface, but they did not belong to the same flows.

Placing every screen in one large sequence would have made the file look complete while leaving its logic ambiguous. Instead, we grouped related states into separate boxes such as “Floating Bar,” “Select Assets,” “Direct Map Exploration,” and “Hierarchy.” Each box represented one coherent part of the experience.

At first, this was a way to make a complicated canvas easier for people to navigate. As AI agents became part of the development workflow, the boxes gained another purpose: they created clearer units of context for implementation.

Here are four principles that shaped the system.

1. Organize boxes around behavior, not pages

A page is a visual container. It is not always a useful development boundary.

One page may contain several independent interactions. A single interaction may also extend across panels, overlays, menus, and several screen states.

In our project, selecting an asset and exploring the map took place within the same primary interface. Visually, the screens shared most of their structure. Functionally, however, they represented different behaviors.

Treating them as one group would require a developer or agent to determine which changes belonged to asset selection and which belonged to map exploration. That distinction was obvious to the team because we had discussed it repeatedly. It was not necessarily visible in the pixels.

We therefore organized the boxes as a hierarchy rather than treating every box as an equal unit. The system has three levels:

• Feature boxes represent a complete product capability, such as Navigation.
• Flow boxes sit inside the feature box and separate interactions such as “Select Assets” and “Direct Map Exploration.”
• Screen-state boxes sit inside each flow and name the specific action or state shown on every screen.

This structure allows someone to move from the broader feature to an individual flow and then to the exact screen behavior without losing the relationship between them. It also means that an implementation task can be scoped around the behavior the team needs to build, rather than every element visible on the page.

2. Make each box understandable on its own

A useful box should not require a guided tour from the designer who created it.

Someone opening the file should be able to understand what the interaction does, where it begins, and what changes as the user moves through it.

That does not mean duplicating every piece of product documentation inside Figma. It means including enough context to remove the most consequential ambiguity.

Depending on the feature, a box may contain:

• The default or entry state
• The action available to the user
• The resulting state
• Expanded and collapsed variations
• Selected, disabled, empty, loading, or error states
• Short notes explaining behavior that cannot be understood visually
• References to existing components or patterns

This self-contained structure matters for human teams, especially when people join a project late or return to a feature after several weeks. It matters even more for coding agents.

An agent does not have the memory of the workshop where the interaction was discussed. It does not know which Slack message changed the requirement or which visual difference was intentional. It can only work with the context it is given.

If critical information sits somewhere else on the canvas, remains buried in a comment thread, or exists only in the team’s memory, the agent must infer what is missing.

And inference is where avoidable mistakes begin.

3. Make interactions and transitions visible

Individual screens show different interface states, but they do not always explain how the user moves between them.

In our design files, we use simple arrows to connect an interaction with the screen or state it produces. If clicking a button opens a sidebar, we connect that action to the designed sidebar state. If an interaction takes the user to another screen, the arrow shows exactly where they will arrive.

Not every interaction needs this treatment. Adding arrows to simple or obvious actions can create unnecessary visual noise. They become particularly useful when one screen contains several possible interactions, each leading to a different state or part of the flow.

For someone who has worked on the product for months, these relationships may already feel obvious. Developers and AI agents do not necessarily have that context. Without a visible connection, an agent may recognize all the individual screens but still misunderstand which action produces which result.

Combined with the box hierarchy, these connections make both the structure and sequence of the experience easier to follow. The boxes show which screens belong to the same feature and flow, while the arrows explain how users move between them. It is a simple practice, but it reduces how much developers and agents need to infer from the designs.

4. Give the AI agent a bounded unit of context

AI coding tools can now access much more than a screenshot. When connected through tools such as the Figma MCP server, an agent can retrieve structured design information, visual references, variables, components, and layout data from a selected part of a file. However, in AI-assisted development, access to more information does not automatically lead to a better understanding of what needs to be built.

An isolated frame may leave out the surrounding states required to understand a behavior. At the other extreme, a large page or full canvas may introduce unrelated screens, unresolved concepts, and several versions of the same feature. The Box Design System creates a practical middle layer between these two extremes.

Instead of asking an agent to “build this page,” a developer can direct it toward a bounded interaction containing the relevant states, transitions, and supporting context. This gives the agent enough information to understand the intended behavior without requiring it to interpret the entire product.

The boundary of a box does not need to match a single code component. Some boxes may translate into one component, while others may involve several components and application states. The box is there to define the product behavior being implemented, not to dictate the final code architecture.

The quality of the generated code still depends on the codebase, prompts, design-system implementation, and the agent’s access to existing components. Figma also recommends semantic naming, variables, Auto Layout, reusable components, annotations, and Code Connect to improve consistency. The boxes complement this infrastructure by organizing those elements into a coherent piece of product behavior that the agent can understand and act on.

What boxes cannot solve

A clean Figma canvas cannot compensate for an undefined product.

If the team has not decided how an interaction should behave, placing its screens inside a box will not resolve the underlying uncertainty. It may simply make that uncertainty easier to see.

That is still valuable.

When related states are placed together, inconsistencies become more visible. The team may discover two competing versions of the same behavior, an exception with no recovery path, or a state that was discussed but never designed.

Boxes also do not replace the platform’s design system. While the main design file uses boxes to organize screens, flows, and product behavior, the design system lives in a separate Figma file containing the shared components, variants, and variables used across those designs.

The design system does not need to follow a box-design hierarchy, but it should be structured and detailed enough for agents to understand exactly what they need and where to find it in the file. Clear naming, logical grouping, and consistent component structures help both developers and AI agents find and reuse the correct elements. Without that structure and the corresponding code, an agent may understand the intended behavior while still selecting the wrong component or creating unnecessary one-off elements.

The box defines the scope and behavior. The design system defines how the interface should be constructed. The codebase defines how it must function in production.

Why Figma file structure now matters for AI-assisted development

For years, design-file organization was often treated as an internal concern. A tidy file was easier to navigate, easier to hand off, and kinder to the next designer who had to work in it.

That is no longer the full story.

As design files become direct inputs to AI-assisted development, their structure begins to influence what an agent understands, what it overlooks, and how much it must infer.

The canvas is no longer only a place where the team presents the final interface. It is becoming part of the system through which software gets built.

Our box-based approach began with a practical need: make a complicated enterprise product easier to understand. Its value grew when the same structure helped divide that product into clearer units for implementation and review.

The boxes themselves are not the innovation. The clarity they create is.

Components define what the interface is made from. Frames capture individual moments. Boxes explain how those moments belong together and what the team is trying to build.

In a development process increasingly shared with AI agents, that context is no longer optional documentation.

It is part of the product.

About the Author:
Aaron Swinton is the Founder and CEO of MAVRK Studio, where he handles business strategy, client partnerships, and the agency’s growth. He has experience in brand building, venture investing, fundraising, and operations, and he uses it to help CPG brands launch and grow.

Most consumer packaged goods (CPG) launches don’t last. Somewhere between 70% and 85% fail, and it’s rarely because the product was bad. 

More often, the launch itself is the problem. There’s a logo from one shop, packaging from another, a website from a third, and nobody owning the whole picture. Along the way, teams end up testing the new product instead of the consumer need, the category, or the retail plan. 

An integrated CPG launch strategy fixes that by lining up product, brand, packaging, eCommerce, and marketing in one plan. That’s the idea behind MAVRK’s 90-day launch system, where Day 90 means “shelf-ready and launch-ready.” 

Why Most CPG Launches Fail (and How a 90-Day Plan Fixes It)

• Fragmented vendors: Brand, packaging, and digital are split across separate teams, and nobody owns the whole launch.
  The Fix: One team building all three in parallel.
• Unvalidated positioning: Design starts before anyone has confirmed demand, price, or the competition.
  The Fix: Validate all three before design begins.
• Weak execution: Wrong labels, bad dimensions, and missed retailer requirements derail a good product.
  The Fix: A week-by-week calendar with owners, approvals, and checkpoints.

One honest note: 90 days is the target, and it assumes timely feedback. Plan a few extra days for each round of revisions.

Inside the 90-Day CPG Launch Plan

Our plan runs on six overlapping workstreams instead of one long list of tasks. Across them, the work moves through four phases: foundation, build, pre-launch, and launch. 

• Weeks 1–2, Validate & Position: the product and launch strategy
• Weeks 2–4, Build the Brand: identity and messaging system
• Weeks 3–7, Design for the Shelf: compliant, retail-ready packaging
• Weeks 5–10, Build the Launch Engine: website, eCommerce, email capture
• Weeks 7–11, Create the Content: photo, video, social, launch creative
• Weeks 9–12, Get Shelf & Launch Ready: sales materials and retail readiness 

It all lives in a week-by-week calendar with clear owners, approvals, and go/no-go checkpoints. Because the workstreams overlap, packaging and photography can share one creative brief, and creator outreach can start before creative is finished. 

Weeks 1–2: Validate and Position

Prove Demand Before You Launch a CPG Brand

Design is the fun part, so it’s tempting to start there. But a CPG product needs category validation first: is the need real, where does the price sit, and who are you up against? 

The right research depends on how much the brand has already decided. For a brand with a clear product and launch direction, we review the category, competitors, and audience to sharpen its positioning before design begins. If the opportunity itself is still open, a deeper Opportunity Sprint can come first.

Depending on the scope, that work may include:

• A shelf and competitor review to understand the category and identify gaps
• Customer research and interviews to test assumptions and hear how people describe the need
• An assessment of the audience, differentiation, and best channels for launch

The goal is to make the key decisions early, so the brand, packaging, website, and launch content can move forward with a shared direction.

For instance, take our work for REALI. We redid branding, packaging, web design, social media and directed their go to market into colleges & gyms vs traditional retail. They’ve since gotten into 30+ stores in 5 months.

From Consumer Language to a Clear Promise

Research only helps if it turns into a promise people understand. Your positioning is that bridge, and it shapes everything after it. 

A positioning section of your launch plan should include:

• Frame of reference (the category you’re competing in)
• Target consumer
• Key benefit
• Reason to believe
• A promise and brand story in real consumer language
• A one-line concept statement everyone can defend 

These decisions ripple into recipe choices, pack size, pricing, channels, and the retail pitch. 

Weeks 2–4: Build the Brand

Positioning tells you who the brand is for. Now it needs a look and a voice people recognize. 

• Naming exploration, checked for trademark, domain, and social handles early, ideally in week 2 
• Logo, color palette, typography, and core visual language
• A brand voice brief: three personality words, plus “we are / we are not”
• A documented brand system: promise, personality, voice, messaging pillars, visual direction 
• A brand guidelines doc, even a single page, so every vendor works from the same reference 

Weeks 3–7: Design for the Shelf

Packaging, Compliance, and Operations

Plenty of launches stumble at the execution layer: wrong labels, bad dimensions, missed routing guides, or claims that don’t comply. 

This phase turns your positioning into a full SKU architecture, label system, and production files. 

Your packaging and operations checklist:

• Front-of-pack hierarchy, with a clear benefit
• Nutrition and regulatory compliance
• GTIN/UPC and case pack structure
• Co-packer alignment, lead times, and freight
• Retailer documentation confirmed before launch 

A quick shelf test: does it stand out at thumbnail size, and would a creator want to hold it? 

Retail-ready doesn’t mean retail-first. Build a few months of online sales (or community) proof before pitching buyers. 

Weeks 5–10: Build the Launch Engine

Website, eCommerce, and Email

Even retail-first brands need a strong digital engine for education, storytelling, lead capture, and proof for buyers. In Weeks 5–10, we build a conversion-focused website, eCommerce setup, store locator, and email flows.

• The Rice Cream: branding, packaging, web design, and launch content built to tell the product story and drive early interest.

• REALI: eCommerce-ready web design and launch messaging aligned with packaging and photo/video. 

What your plan should include:

• Landing pages and lead magnets
• A pre-launch waitlist
• Abandoned-cart flows and post-purchase emails 
• A pre-launch email list goal of 500+ subscribers 

Weeks 7–11: Create the Content

Photo, Video, and Social

Content turns a launch plan from strategy into visible momentum across social, email, and paid channels. In Weeks 7–11, we produce product photography, lifestyle imagery, recipe or usage content, and launch videos. 

Folkland’s social launch campaign shows what consistent visuals and storytelling can do. 

The Rice Cream and REALI paired photo, video, and social content that matched their packaging and websites. 

Map content to each phase:

• Pre-launch: teasers, behind-the-scenes, a countdown series 
• Launch: reveal content, how-to clips, UGC prompts, retailer-specific creatives 
• Post-launch: put more behind what worked, and feed real customer content and reviews back in

Creators can support each phase of the launch, from early product introductions to launch-day content and customer reviews. Depending on the brand, we may build a broader affiliate program where creators earn a commission on sales, or work with a smaller group of carefully chosen influencers to reach a specific audience.

Weeks 9–12: Get Shelf & Launch Ready

Go-to-Market Execution: Launch Week to Post-Launch

Build your launch calendar across pre-launch, launch, and post-launch, with inventory, media, and in-store support all lined up. 

In launch week, point every channel at one clear call to action, concentrate spend in the first 2–4 weeks, and check velocity and feedback daily. 

We treat the first 90 days in market as a commercial test, with success metrics and go/no-go or pivot points built into the plan. 

Track:

• Velocity: how fast the product sells
• Repeat rate
• ROAS: return on ad spend
• Email opt-ins 

When a message or creative performs well, we put more budget behind it and use what we learn to brief the next round of creators. When results are weak, we review the data, adjust the approach, and shift spend toward what’s working.

Alongside the launch, the sales side gets ready with a retail pitch built on your online sales data, plus sales materials and retailer documentation.

Growing After Launch: Community and Revenue

A strong launch strategy connects to a growth plan. It doesn’t stop at Day 90. MAVRK Grow picks up where launch leaves off. 

• Community growth: organic social, content, email, creator activation, and IRL activations. 
• Revenue growth: paid media, performance creative, and conversion optimization to scale what worked. 

Early signals, like top creatives, strongest audiences, and best regions, feed straight into performance campaigns. 

Putting It All Together: A 90-Day Checklist

• Days 1–30: validate, position, name, and build your brand identity and guidelines
• Days 31–60: packaging, online store, photography, creator outreach
• Days 61–90: content, email list, ad setup, soft launch, creator launch day, public launch 

The steps that prevent failure: validation, coherent branding, retail-ready packaging, a digital launch engine, and aligned marketing. We swap a pile of vendors for one accountable team. 

Your next step: audit your current launch plan against this checklist, or sketch your own 90-day roadmap before you talk to designers, agencies, or co-packers.

You can also talk to us about your brand’s starting point and launch goals, and we’ll help you work out what your first 90 days should look like.

About the Author:

Zlatina Petrova has spent 13 years shaping brands and digital products across Silicon Valley and Europe. As Founder and Design Director of Brandly, she works with tech startups, VCs, global brands and government institutions including work on Bulgaria’s national design system. Her work sits between branding, product design and UX/UI, with a belief that design should do more than look good: it should help businesses grow, products work better and brands mean something to people.

When Brandly started, clients weren’t buying the company. They were buying the people behind it. I already had a solid reputation of my own: I had led product design at an LA-based startup, worked as a creative director in Florida, and won one of Europe’s most prestigious design awards.

The media were dying to interview me. Nobody was dying to interview Brandly. Same with the clients. They trusted me first, and the company second. Trust lived in the founder before it lived in the brand. This is the core of effective executive personal branding. Only later did Brandly accumulate enough history, language, and systems to carry that trust independently.

In that transition, one truth became obvious: people don’t experience companies first. They experience people.

In the early stages, a founder’s personal brand is not a vanity project sitting next to the company brand. In a founder-led business, it is often the first interface through which people decide whether your company deserves attention at all.

Before they understand your product or mission statement, they are asking much simpler questions:

• Do I trust this person?
• Do I believe what they believe?
• Do I want to listen to them?
• Do I want to work with them?

The personal brand becomes so closely attached to the company that the founder eventually becomes the bottleneck for trust. If they step away, clients become nervous. If they move on to something new, the company suddenly feels different. If they want to sell the business, part of its value is still sitting inside one person’s relationships, reputation and way of thinking.

The founder’s real job goes far beyond visibility. The job is to turn personal conviction into something the company can eventually carry without you. Here is how the founder shapes the brand around them, and how that personal equity eventually becomes company equity.

Establishing Brand Identity and The Founder’s Role In Corporate Branding

Inevitable brands rarely begin as systems. They begin as conviction. Before there are guidelines, culture decks, and campaigns, there is usually one person who sees something that does not yet fully exist.

That person has to believe in it long enough for everybody else to catch up.

This is what I mean by devotion. Not founder mythology, and definitely not “hustle culture.” I mean feeling the brand deeply enough to sense when something strengthens it and when something quietly weakens it.

In the beginning, you notice the wrong tone in a sentence, the product that makes money but weakens positioning, or the impressive partnership that simply does not belong in the world you are building. Over time, your instinct teaches the rest of the organization what the brand actually is.

When the founder cares deeply about the details, employees start making better decisions without constant approval. What started as one person’s conviction slowly becomes something shared.

If the founder carries the brand internally, the personal brand makes that worldview visible externally. But this is where many founders get personal branding wrong.

Your personal brand is not a diary of everything you think, eat, or do. It is the clearest public expression of the parts of you that give the company meaning: your judgment, beliefs, standards, taste, expertise and way of seeing the world.

The public version of you should still be true. Just edited. You do not need to publish every private detail to feel human; you just need to make the part of you that explains the company legible to others.

Takeaway: The founder shapes the brand from the inside first. Personal branding makes that worldview visible from the outside.

Core Value Alignment and Strategic Brand Development for B2B Founders

There is a strange ritual happening in branding workshops everywhere, including plenty of B2B brand strategy consulting sessions we’ve run ourselves. Someone opens a Miro board. Everyone gets virtual sticky notes. Forty-five minutes later, almost every company on Earth discovers its values are innovation, integrity, excellence and customer-centricity.

If your competitors can copy your values without changing a word, they are not your values.

Real values are inconvenient. They come from your experience: the managers you never wanted to become, the moments that made you proud, the clients you instinctively protect, and the compromises you refuse even when money is on the table.

This is where founder branding begins. Not with “What should I post about?” but with “What do I believe so strongly that it repeatedly changes my decisions?”

Founders encode their values into the company whether they intend to or not. Those values dictate:

• Who gets hired
• How fast the product ships
• Whether difficult conversations are had
• What the company quietly tolerates

Repeated decisions become culture. Culture becomes user experience. Experience becomes reputation. Reputation becomes a brand.

Try building a founder value map. Take five important moments from your professional life, especially the frustrations and failures. Ask: What did this teach me that I now believe very strongly?

Look for repetition. You may discover that five apparently unrelated stories express the same principle. “Care” is not a value until it changes how you price projects or communicate bad news. A brand becomes credible when values create visible trade-offs.

Takeaway: Your founder brand should be built from beliefs with consequences, not values that simply look good on a wall.

Thought Leadership Strategy and Elevating Your Executive Personal Brand

Founders often tell me they “should be posting more.” I’m not convinced.

The internet does not urgently need another founder sharing seven lessons from waking up at 5 AM. What people need from experts is not more content. They need judgment.

A strong founder brand gives people a sense of how you think, what you challenge, and what matters to you before they ever buy.

A brand identity designer can post: “Five branding trends for 2026.” Or they can say: “Most early-stage companies redesign their visual identity too early, because the real problem is they haven’t decided what they want to be remembered for.”

The first gives me information. The second gives me perspective. Perspective is invaluable in businesses where clients buy trust: consulting, law, venture, architecture, or complex B2B software. A case study tells me what you did; a point of view tells me how you’ll think when we hit a problem neither of us has seen before.

A true thought leadership strategy begins with three questions:

• What do I believe?
• What observation made me believe it?
• What do I do differently because of it?

A belief that never changes your behavior is just positioning copy. For example, we believe brand consistency shouldn’t depend on designers policing assets. So, what do we do differently? We treat governance and contribution rules as part of the design itself, not an afterthought.

Now, you aren’t just claiming expertise; you are showing how it changes your work.

Takeaway: Don’t use your personal brand to prove that you are visible. Use it to make your thinking visible. 

Brand Cultivation and Hiring for Corporate Brand Alignment

Who is helping you build this thing?

Customers experience your brand through a salesperson, support agent, designer, freelancer, and sometimes a vendor. Every one of them translates the brand through hundreds of micro-decisions. A brilliant person who repeatedly makes choices that feel wrong for the company can weaken the brand more than an average logo ever will.

The best teams develop a shared instinct. They know which compromise the company will make and which it won’t. They know when something is technically correct but still not right.

You can call this cultural fit or brand alignment. The outcome is what matters: the person amplifies the signal rather than introducing static.

This must influence hiring. Assess skill, but also ask questions that reveal taste and judgment:

• Show candidates real scenarios.
• Ask what they would protect when time runs out.
• Ask what they refuse to compromise on.

Look at your existing team with the same honesty. Who strengthens the brand? Who is excellent at their job but consistently pulls the company toward a different identity? Alignment cannot be ignored forever.

Takeaway: Skills determine whether someone can do the job. Alignment determines whether they strengthen the brand while doing it.

Enterprise Brand Architecture: Scaling from Founder to Corporate Entity

As the brand grows, the founder’s role changes. Early on, trust travels through the person. Clients use your reputation as a shortcut to decide if the business is credible. But growth demands a new question: where should that trust travel next?

This brand equity transfer is crucial. Brand architecture dictates how much of the founder’s reputation transfers to the company, how much remains with the founder, and which new offers borrow from either.

Founders are tempted to capitalize on momentum. If people trust you, it’s tempting to endorse every new service or product you launch. Sometimes that is smart. Sometimes it is simply logo slapping. Accumulated trust should only travel where the promise and experience justify it.

Navigating this is why companies hire a specialized brand architecture agency, but you can start with three core paths:

• The Unified Brand: If a new offer delivers the same core promise and experience, it belongs inside a unified brand. The goal is to move trust away from the founder and deeper into the company.
• The Endorsed Brand (Brand Extension): If the experience belongs to the same world but the promise is different, it’s a brand extension. A visible association (“From the founder of…”) reduces perceived risk without pretending the new venture is just another version of the parent company.
• The Individual Brand: If the new offer has a completely different promise and audience, forcing the founder’s name onto it creates confusion. Founder equity shouldn’t be permission to attach the same reputation to everything.

The strategic goal is to make the founder an endorsement layer, not a permanent dependency.

Early on, use your personal brand. Let your name open doors and reduce risk. But simultaneously, the company must accumulate its own evidence: recognizable methodologies, systems, and a consistent experience.

The founder says, “This is what I believe.” The company proves, “This is how we operate.” Eventually, the customer concludes, “I trust this organization, even when the founder is not in the room.”

Many founder-led companies fail to reach this point, and Brandly was no exception early on. If the founder remains the ultimate source of reassurance, it becomes a massive problem the moment they want to step back, launch something new, or sell.

The best transition is gradual:

• Give visibility to your team.
• Turn personal know-how into company methodology.
• Move recurring ideas from your LinkedIn posts into the company’s language.
• Let clients form relationships beyond you.

Make the experience consistent enough that your personal reputation becomes the introduction, not the entire argument.

In maturity, the founder brand and company brand stop competing for attention and start endorsing each other.

Takeaway: In the beginning, the founder lends trust to the company. During growth, convert that borrowed trust into company equity. Use brand architecture to decide where that trust should compound, endorse, or stop.

People may buy the founder before they buy the company. That is not a weakness to hide; it is an advantage to design deliberately. But the founder’s real job is to build a world compelling enough that, eventually, people no longer need them standing at the entrance.

About the Author:
Vicente Reyes Montealegre, heads Afternow’s Brand and Web teams to guide SaaS companies, enterprises, and fast-growing startups in their digital journeys. The agency’s work spans strategy, brand, website, product and development, all under one roof, all connected to one vision.

Access to care was the whole point of Kinetik’s business. Non-emergency medical transport gets patients to dialysis, to chemo, to appointments they’d otherwise skip. So, the actual brief for this patient coordination platform design ran much deeper than logos and layouts. We needed to build a comprehensive product people could trust their care to.

The American healthcare system doesn’t make that simple. Riders, providers, and insurers all operate on different timelines and different systems, and getting them to coordinate can be exhausting for everyone involved, patients included. Kinetik exists to make that coordination actually work.

That’s a different problem than what most HealthTech faces. Kinetik’s users weren’t optimizing a workflow. Many were older, managing a condition, coordinating a ride they couldn’t afford to miss. Every decision, on the brand, the site, the products, had to hold up under that weight.

Warmth as a design compass in healthcare branding

We moved away from the clinical, high-tech blue and aqua gradients the old identity relied on. Most health tech platforms reach for a look that leans too much on the tech and not so much on what health means. It’s a common pitfall you’ll notice when browsing portfolios of even highly rated brand identity designers.

It makes sense because that is where innovation sat ten years ago. Today, we can argue that audiences are craving for digital experiences that feel tangible, genuine, with more texture and life in them.

The inspiration point started with a very concrete moment of Kinetik’s users journey: the feeling of looking out a window on a ride, watching the city go by as they travel to their medical appointments. That image is where the painterly, almost impressionistic illustrations of the urban landscape came from.

The palette followed the same instinct, pulled from the organic rather than the artificial: deep and vivid greens against gold, salmon, lavender, and a purple that reads like the last light of a sunset. Nothing else in the category looks like this.

Typography carries a similar weight. An elegant serif, used large, gives the brand a voice instead of blending into the next healthcare login screen. Used small, it steps back and lets the content do the work.

The photography direction stays close to that same idea, people in ordinary moments, at home, in the city, living their lives. Access to care isn’t confined to a hospital visit, it shows up in every part of someone’s day.

The refreshed logo carries this story as well. A capital K, drawn in one curved stroke, with a dot sitting at the end like a destination marker, because getting somewhere is what Kinetik actually does.

Structuring medical website navigation for complex audiences

The marketing site had one real problem before the rebrand: articles, case studies, and news all sat in one undifferentiated pile. We split it apart, and built the site’s structure and navigation around the three groups Kinetik actually serves: health plans, transportation providers, and state and government agencies, each with a clear path through the site instead of one menu trying to work for everyone.

The website does more than tell the story here. The same visual language that sets the mood on the landing page also gets used inside the product screen visualisations, to flag a trip, a claim waiting on review, or a step someone shouldn’t skip. Same system, pulling double duty: telling the story, and pointing at what matters.

HealthTech products solving opposite users at once

Inside the products, the same question got harder. Coordinators needed dense, fast interfaces, real-time visibility across thousands of trips, quick assignment, no wasted motion. Patients using the Kinetik Health app needed almost the reverse: large touch targets, few steps, a calm interface that doesn’t rush them.

That tension sits at the center of the patient app. Real-time tracking and recurring scheduling are genuinely sophisticated features. They had to live inside something simple enough for someone managing a visual or cognitive impairment to use without a second thought.

Contrast, focus states, type size, motion, none of it was a checklist item added at the end. It shaped the product from the start, proving exactly why companies must look beyond aesthetics when vetting UI/UX designers. Confusion on this screen costs someone their ride to treatment.

What it takes to build a healthcare product patients can rely on

The brand is the part people notice first, the color palette, the painterly illustrations, the typographic voice. It’s the part that makes Kinetik stand out on a shelf full of competitors that forgot about the people they’ll be affecting the most. That matters. But a harder, quieter work sits underneath: the architecture, the user flows, the structure that holds four different products together for four very different users. That work is the proof point, and the reason a patient with a ride booked for 7am can actually get there.

About the Author:
DD.NYC^® Creative Director & Managing Partner Anjelika Lours’ Kour specializes in corporate branding, web design, and video storytelling. Beyond working with powerhouse clients, she actively shapes the wider creative industry as a global judge for the International Academy of Digital Arts and Sciences (IADAS) and the Scholastic Art & Writing Awards.

Hiring a real estate web designer for their portfolio without screening for project complexity is an easy trap. You scroll through case studies, land on a beautiful single-property site, and assume they’re the one for you. 

Let me share the challenge we faced with SJP Properties, an NYC real estate developer with more than 40 years in the mixed real estate space, spanning commercial and residential buildings across the metro.

SJP isn’t a single-category business. It’s an established brand with a legacy, an existing logo, and decades of buildings that quite literally shape the Manhattan skyline. 

That combination puts a very specific kind of pressure on a web design brief. The client isn’t looking for a revolution. They’re looking for an evolution. 

We were brought on for the website design, development, animation and motion graphics for SJP. We had to build something best-in-class, featuring the buildings and the legacy of a well-known developer rather than override it with a design trend.

Here’s what actually separates the web design agencies specializing in real estate from the ones with a nice Instagram feed, based on a successful project.

How to evaluate a real estate web design agency

1. Check their range across property types, instead of focusing on one polished example.

A single gorgeous luxury condo site tells you an agency can execute a mood for a certain audience. It doesn’t tell you what happens when your business lives in more than one address. 

Look at SJP’s profile: office, residential, industrial, and mixed-use. These aren’t visual variations on a theme, they’re different audiences with different expectations. An agency worth hiring should be able to show you they’ve designed for range, not just for polish. 

2. Ask how they’d unify a business that doesn’t behave like one category.

Our job for a real estate brand like SJP was to build one system flexible enough to hold an office tower, a luxury residence, and an industrial asset without any of them feeling like an afterthought or a bolt-on. 

Ask a prospective agency, “If my business serves more than one audience, how do you keep that from turning into a fractured brand?”

3. Weigh their ambition against usability at scale.

A 40+ year developer with 20 buildings and a multi-billion-dollar portfolio isn’t a project you can approach the way you’d approach a single boutique listing site. 

As real estate businesses grow, the build has to hold up under real usage, real content volume, and real institutional stakeholders reviewing it, while still looking like it belongs to a company operating at that level. 

If an agency can’t describe how they’d handle that kind of scale, consider your brand goals before signing anything.

4. Find out how they’d evolve an established brand without erasing its equity.

Not every real estate client is starting from zero. SJP already had a logo, a legacy, and decades of buildings that helped define the Manhattan skyline. The job wasn’t to hand them something unrecognizable, but to build something best-in-class that still felt unmistakably like SJP. 

If an agency’s answer to “how would you approach an established brand” is indistinguishable from their answer for a brand-new startup, that’s worth noting. 

5. Define what “success” looks like before the project starts.

For a single-property site, success might be one clear conversion path. For a company like SJP, success has to mean something broader. 

The site launched in 2024, and within days it was ranking on the top pages of search results for multiple non-branded, highly competitive terms, with several sitelinks picked up along the way. 

That’s the kind of outcome that’s easy to promise and much harder to deliver. It’s worth asking directly how a prospective agency would define and measure success before the project starts, not after it launches. 

What makes an effective real estate web design portfolio

Look for signs of systems-thinking over single-project polish. Does their work suggest they can hold a brand together across multiple offerings, or does every project look like a standalone exercise in making one thing pretty? 

A web design portfolio that only proves an agency can nail one mood is a narrower asset than it looks like at first glance, especially if your business doesn’t fit neatly into one category, typical of real estate projects.

Range matters in real estate

Real estate businesses are rarely one thing, and they’re rarely starting from a blank page either. The agency that’s actually right for you is the one that can prove they’ve handled that kind of complexity before, and that they know the difference between evolving a legacy and erasing one.

And if you’re a web designer or agency reading this, it’s worth asking yourself the same questions before you pitch: can you show range, not just polish? Can you evolve a real estate brand instead of overriding it? Knowing these could help you win projects in the real estate industry.

About the Author:

Klym Yevtushenko is the Founder & CEO of VibeStyle. He works with startups and growing companies to turn ideas into clear, engaging digital experiences: from high-converting websites, landing pages and mobile apps to SaaS platforms and digital products. 

When we worked on a B2B website redesign site for NestiFi, we put family finance ahead of the banks and credit unions who were paying for the platform.

This is because before we touch layout on any redesign, we figure out who’s deciding and what order they need information in.

I’ll walk you through what that process looks like and how we start every website redesign project that delivers results.

How We Approached NestiFi’s B2B Website Redesign

NestiFi is a family finance platform. Credit unions, community banks, and wealth firms use it to offer branded financial experiences to their own customers, from family investing and teen money to financial planning, education, and AI-powered guidance.

That means the FinTech platform had two audiences with very different questions. These are the institutions that buy, and families that use it.

Founder and CEO Niall Dennehy shared with us the moment his mother took him to a credit union in Cork to open his first account. Years later, he’s asking what a child’s first meaningful financial experience should look like today.

This story reflects the human purpose behind NestiFi, which is helping families build better financial relationships. And for us, the challenge was translating that vision into a B2B website.

The scope covered website strategy and information architecture, UX/UI and responsive design, brand identity and visual direction, product positioning, and the Webflow design itself.

The website had to address both perspectives without becoming overly technical or looking like a purely consumer-focused finance app.

If you’re faced with a similar challenge, here’s what we recommend you evaluate before designing: 

1. Your audience’s decision-making process

Our designer suggested a simple exercise. That is to pretend we’re bank executives seeing NestiFi for the first time. 

Instead of discussing colors and layouts, we started asking different questions: Would we understand the business value? Would we trust the platform? Would we know what to do next?

This helped us look beyond visual design and evaluate the website from a potential buyer’s perspective.

We also wrote down what each of NestiFi’s audiences needed to know. 

• Institutions needed to understand the business value, how it fit into their existing offering, the functionality, how reliable it was, and what it could integrate with. 
• Families needed to know how it would change the way they manage and understand money together.

2. Your homepage information hierarchy

In an early design review, we realized we were trying to explain almost everything on NestiFi’s homepage: family investing, financial education, AI features, institutional benefits. Someone on our team even joked we were fitting the entire product presentation onto one screen!

We simplified the homepage and spread the information across the journey, so visitors could discover the product step by step.

3. Your website user journey

We organized NestiFi’s site as: 

Family finance → Value for families → Value for institutions → Product capabilities → Trust and implementation → Demo.

This structure was also what let us connect the emotional purpose behind NestiFi with the practical information institutional buyers actually need, rather than treating those as two competing stories.

A clearer value proposition, better hierarchy, and more visible calls to action all contributed to demo-request conversion rising 38%, and average engagement time to 31%.

4. Your mobile UX and platform

Responsive design and simplified mobile navigation cut NestiFi’s mobile bounce rate by 24%.

We built NestiFi in Webflow, giving it a flexible foundation for future capabilities, including new integrations, without overcrowding the homepage.

Key takeaways for your next B2B website redesign

The biggest lesson from NestiFi, for me: web designers should start with the audience and how it makes decisions, not with visual improvements.

Beyond the numbers, the real win was giving NestiFi a clearer way to talk about a genuinely complex business model. Have one story that institutions and families could each find themselves in.