• Menu About Connective
  • Menu Core Values
  • Menu Reviews
  • Two person giving high five

Kayaku Advanced Materials

Specialty materials manufacturer unifies three brands and launches an AI-powered mascot

Founded in 1992 and backed by parent company Nippon Kayaku Group, Kayaku Advanced Materials had built more than thirty years of differentiation in specialty photoresists and polymer coatings. The website needed to catch up with the company. We consolidated three sub-brands into one platform, clarified manufacturer authority across the product hierarchy, and built an AI-powered mascot that gave the brand a differentiator competitors in the category do not have.

Kayaku Advance Material website showcase

At a glance

Here’s the short version for those evaluating whether this project is relevant to their situation.

Situation

Three sub-brands across patchwork sites. Product hierarchy that did not surface manufacturer authority. A fixed fiscal-year deadline that could not move.

What we did

Multi-brand consolidation with audience-driven information architecture, a custom 3D mascot, an AI chatbot built on the mascot's persona, and a custom quote system that handles a complex hidden product hierarchy.

Key outcomes

Three sub-brands unified on one platform. Manufactured and distributed products clearly separated. AI assistant launched with the site rather than deferred to Phase 2. Site shipped before the fiscal-year deadline.

Core insight

In dry technical categories, warmth and humanity differentiate harder than another future-tech aesthetic. Most competitors lean austere and impersonal. Kayaku went bright, human, and approachable.

The challenge they faced

Kayaku Advanced Materials makes the materials that make modern technology possible. Photoresists, polymer coatings, dielectrics, and adhesion layers used inside semiconductors, medical devices, microfluidic chips, sensors for AR and VR, and packaging for the next generation of electronics. Their products are not the things you see. They are the things that make the things you see work.

Three sub-brands sit under the parent organization. StructSure for the structural photoresist line that semiconductor manufacturers depend on. Design Fabrication Services for the microfluidics and life sciences side, where biocompatible patternable coatings enable lab-on-a-chip diagnostics. Paratronix for the emerging-tech and defense side, including dielectrics and protective coatings for sensors and flexible electronics. The company also distributes complementary products from partners like DuPont (rebranded as Qnity during the project) to give customers a more complete materials offering in one place.

The reputation in the industry was strong. The website needed to start matching it.

In the client’s own words from discovery: “The current website was built with the intention of being a guide to academia audience. The current site feels outdated and doesn’t clearly communicate our capabilities, technical expertise, or the industries we serve.”

In practical terms, here is what the new site needed to start doing.

The three sub-brands had to come together. They had been built at different times, lived on different properties, and never connected as one experience. A visitor researching photoresists for a semiconductor application would land in one place. A visitor researching coatings for a medical device would land in another. Bringing the sub-brands together while letting each one keep its own identity was the structural challenge underneath everything else.

The product hierarchy had to make manufacturer authority visible. Kayaku designs and produces the bulk of what they sell and distributes complementary products from partners. The structure itself had to communicate that distinction before a visitor read a single word.

The product catalog needed reorganization around how customers actually search. The previous structure organized products by SKU and model number, so an engineer searching for a coating that fit a specific application or industry had to already know the Kayaku product code. Application-led navigation barely existed.

Two distinct audiences pulled the site in different directions. The legacy academic audience, who had been ordering 500ml bottles of SU-8 for graduate research projects for years, made up a meaningful share of current traffic. The industry audience the company wanted to grow into (mid-to-large semiconductor manufacturers, medical device companies, and emerging-tech innovators) needed an entirely different conversation about manufacturing scale, supply chain readiness, and partnership capacity. Serving both without forcing one through the other’s experience was the design challenge.

And the deadline could not move. The launch had to land before the end of the fiscal year.

For a company that had built genuine differentiation since 1992 and was actively repositioning itself for industry growth, this was a foundational moment. The website was the surface where the next chapter of the company’s positioning had to start.

How we approached it

What discovery revealed

We started with research. Stakeholder interviews across the Kayaku leadership team. Competitive analysis across direct competitors (JSR, TOK, Merck, DuPont, MicroChemicals) and adjacent providers (DJ MicroLaminates, SCS, HZO). An audit of the existing properties and content. Mapping of how the two audience types actually moved through the site.

Three insights shaped everything that followed.

The category itself was the wrong place to differentiate on technical authority alone. Every competitor in this space leads with technical authority. The category visual default is also remarkably consistent: dark backgrounds, futuristic aesthetics, abstract circuitry imagery, clinical photography. The differentiation opportunity was not more authority. It was more humanity.

Manufacturer authority needed structural separation, not just messaging. Telling visitors Kayaku is a manufacturer in the copy was not going to do the work if the site continued to mix manufactured and distributed products in the same visual hierarchy. The fix had to be architectural.

The two audiences needed different paths through the same site. The academic researcher who knows they need SU-8 and just wants to reorder it has nothing in common with the procurement manager at a semiconductor manufacturer evaluating long-term supply partnerships. One audience needs to get to a quick reorder. The other is in a longer conversation about which materials fit their development process. Two paths, surfaced without forcing either audience through the wrong one.

How services integrated

This is where integrated work matters. The project touched strategy, UX, design, development, custom illustration, content, AI implementation, and CRM. If any of those disciplines had treated their part as a separate handoff, the project would have fractured. The chatbot would not have matched the brand. The quote system would not have reflected the product strategy. The deadline would have been harder to protect.

Seventeen people on our side touched the work at various points. The mitigation against fragmentation was making sure everyone consumed the same discovery materials, the same competitive analysis, the same audience research. Not filtered briefs. The actual research. When designers developed visual concepts, they understood why warmth was the differentiation play. When developers built the quote request system, they understood why ancillary products needed to behave a certain way. When the AI chatbot got trained, the persona reflected the brand voice already established for the rest of the site.

That shared foundation also made it possible to absorb scope evolution without losing the deadline. The mascot was not in the original scope. The chatbot moved from a Phase 2 nice-to-have to a launch-day deliverable. The interactive city map emerged from the work. Fifty-plus custom icons replaced generic stock iconography. None of it moved the launch.

The mascot story is worth pausing on, because it shaped more of the project than any other single addition. It started as an illustration problem. The client had existing 2D “clean room dudes” that did not match the new visual direction. They were flat, cartoony, and inconsistent with the warmth and modernity we were aiming for. Our designer took inspiration from the Dexter’s Laboratory aesthetic and developed 3D renderings that carried the warmth of the original idea into a more polished, ownable character system. The result landed. But that surfaced a question: if Kayaku has this mascot, what does the mascot do? Custom 3D illustration across every page was not realistic at scale, so we proposed building out the mascot as a full character package the client could use across the site and other materials. The client agreed. Then a separate conversation about the chatbot started, and the question came up: what if the mascot is the chatbot? Suddenly Dex Litho had a job description that made the whole investment compound on itself.

Technician in protective clothing inspecting industrial equipment
Engineers discussing equipment in a manufacturing facility

Audience-led navigation, not product-category navigation

Instead of organizing the site around how Kayaku internally categorizes products, we organized around how the two audience types actually search and decide. Industry-and-application paths for procurement and engineering buyers. Direct product paths for the researchers who already know what they need. The "Who We Serve" section, surfaced near the top of the homepage, lets visitors self-identify into the path that fits their journey.

Structural separation between manufactured and distributed products

Decision: Structural separation between manufactured and distributed products We built a hierarchy that makes it instantly clear which products Kayaku makes and which they distribute. Sub-brand pages get visual prominence. Distributed products appear in dedicated sections that read as supportive offerings. The catalog itself communicates Kayaku's actual position in the value chain without the visitor having to read a single word.

Build Dex Litho as both mascot and AI assistant

The original scope included chatbot discovery and recommendation, with implementation potentially deferred to a Phase 2. Once the mascot existed and the technology stack was reviewed (HubSpot Breeze AI was already in their existing tools), we made the call to push for launch-day inclusion. The trade-off was a tighter implementation window. The benefit was launching with one of the strongest differentiators already in place rather than as a follow-up announcement.

What we built together

Information architecture and navigation

A complete restructuring of how Kayaku’s offerings get organized. Audience-led entry points let industry and academic visitors self-select into the right journey from the homepage, with a “Who We Serve” section near the top that names buyers before they have to go looking. Industry-and-application content moved into primary navigation, with traditional product categorization preserved for visitors who already know what they need. Manufactured products are structurally separated from distributed products so the visual hierarchy itself communicates manufacturer authority.

Colleagues reviewing a kayakuam website on a laptop
Kayaku Advance Materials — Homepage
Kayaku Advanced Materials product categories and product list
Product Sub-menu

Visual identity and design system

A unified design system that lets the parent brand and three sub-brands coexist without competing. Strategic color assignments by business unit anchor each sub-brand visually: Kayaku Blue for StructSure and the parent, green for Design Fabrication Services, and a third color introduced for Paratronix. Over fifty custom icons were designed specifically for the project, replacing generic stock iconography that did not match the visual direction. The custom illustration style developed for the homepage and supporting pages breaks from the impersonal industry default, with application-area imagery that visualizes what Kayaku’s materials actually do in environments people can recognize, rather than relying on abstract circuit-board metaphors.

Grid of industry applications with technology category icons
Custom Iconography

Dex Litho mascot and AI assistant

A 3D mascot that appears across the site in branded uniform with the Kayaku logo on the chest, in multiple poses and contexts ranging from product education to the FAQ page. The chatbot version of the same character lives on every page, built on HubSpot Breeze AI and integrated directly into Kayaku’s existing tech stack so there were no new vendor dependencies. Its knowledge base is trained on Kayaku’s technical data sheets, application notes, and product documentation. Visitors can ask Dex about photoresist properties, get help identifying the right material for an application, or request a technical data sheet, which is gated through email capture so the conversation enriches the CRM rather than handing over assets anonymously.

The visible part of the chatbot is only a small part of the implementation. Most of the work was making sure it behaves safely and consistently in the cases the visitor never sees. Adversarial testing made sure it does not release gated technical documents without email capture, does not make unsupported technical claims, does not contradict source documentation, does not respond outside its intended role. Training documents had to be reviewed and in some cases sent back for client updates because the AI struggled to read them accurately as written. Guidelines that shape how Dex responds had to fit within tight character limits across multiple categories. Short-answer prompts had to be developed for technical specifics where the AI would otherwise drift.

The chatbot also enriches Kayaku’s CRM. Conversations get categorized based on context and routed to the right team. When a salesperson follows up with a contact, they have summary chat logs to work from. The AI is not just answering questions. It is feeding the sales process.

Dex Litho Model
Dex Litho Model
Kayaku Advanced Materials building sign with a waving mascot
Dex Litho as Brand’s Mascot

Quote request system with hidden product hierarchy

Roughly forty percent of Kayaku’s business runs through ancillary products: developers, removers, adhesion promoters, and other supporting materials that sell alongside the primary products. Ancillaries do not have individual product pages. They live as recommended add-ons on the products they support. We engineered a custom backend solution that lets ancillary products exist as data entities visible to the quote system without appearing as their own pages. The quote system runs on a Yith plugin for the request-list functionality, integrated with Gravity Forms for submission, with HubSpot feeds carrying the data into the CRM. The hidden relationship between primary products, sub-products, and ancillaries was one of the harder technical problems on the project, and one of the ones that mattered most because it touched a substantial share of what the business actually sells.

Person requesting a product quote through a website form on a laptop
Request a Quote Page

Multi-language and SDS document handling

For a global technical manufacturer, language handling is not a usability feature. It is a trust and compliance requirement. The site supports four primary languages through GTranslate (English, Chinese, Japanese, and Korean) for site content, plus regulatory document support for SDS (Safety Data Sheet) downloads in additional languages including French, German, and Italian where regulatory requirements demand specific country versions. We considered automatically switching SDS downloads based on the visitor’s selected site language. The decision came down to consistency. If a French visitor selected English on the site but needed the French SDS for regulatory compliance in their region, automatic switching would either give them the wrong document or create inconsistent behavior across files. SDS documents now use manual language selection with each version clearly labeled. Predictable beats automated when consistency matters more than personalization.

Kayaku website homepage promoting materials for future technology
Multi-Language: Japanese
Multilingual website language selector and call-to-action buttons for kayakuam website
Multi-Language Options

Interactive city map

A visualization of how Kayaku’s materials show up in the world. Hospitals, schools, semiconductor fabs, research facilities, manufacturing plants. The map lets visitors click into each environment to see which Kayaku products and applications support it. For a company whose work is largely invisible, the map gives visitors a tangible sense of where Kayaku actually lives in everyday technology. It is also one of the strongest answers to the “what do you actually do” question that B2B technical manufacturers often struggle to answer in a way non-specialists can grasp quickly.

Kayaku AM interactive map feature
Kayaku Advance Materials — Interactive Map

Where they ended up

Three brands, one platform

StructSure, Design Fabrication Services, and Paratronix unified under the Kayaku parent brand, each keeping its own identity while contributing to a single coherent experience.

Manufacturer authority, structurally

Manufactured products visually separated from distributed products. The product hierarchy itself now communicates Kayaku’s position in the value chain.

Mascot live, chatbot active

Dex Litho launched as both a brand mascot and a working AI assistant on day one, in place at launch rather than deferred to a Phase 2 release.

Shipped on the deadline

The site landed before the end of the fiscal year, with scope additions including the mascot, chatbot, and interactive map absorbed without moving the launch date.

Within weeks of launch, the early signals were encouraging. The Kayaku team posted to their own social channels about Dex Litho the day after launch, a campaign we were not running for them. Kayaku’s chief growth and technology officer sent a launch-day message expressing how good the site looked and how eager he was to interact with Dex. The chatbot has been steadily used by visitors in the weeks following launch.

The strongest improvement is structural. The site no longer asks visitors to figure out how Kayaku’s offerings fit together. It does not force one audience through the other audience’s path. It does not look smaller than the company actually is. The visual differentiation in a category most competitors render austere and impersonal means Kayaku now shows up externally with the same depth and clarity they have always had internally.

For Kayaku’s internal team, the site is also easier to run, update, and grow. The brand voice and visual system are codified well enough to extend into other marketing channels. The mascot can carry into future campaigns. The phase two enhancement list gives the team a clear path for continued improvement.

For B2B manufacturers reading this and recognizing themselves in it, the lesson is simple: your digital presence is either clarifying your value or making buyers work too hard to understand it. Kayaku had built genuine differentiation over more than thirty years. The new site lets that differentiation finally show up at the surface where buyers, partners, and prospects look first.

Frequently asked questions

Common questions about multi-brand B2B website consolidation,
AI chatbot integration, and managing complex builds against fixed deadlines.

You build the team and the process around that constraint from the start. For Kayaku, we shifted from our standard “develop everything, then review everything” model to a rolling agile approach where pages got shipped for review individually as they finished. We pushed feedback into rapid cycles instead of batching it, and we made deliberate calls about which scope additions could be absorbed and which had to be deferred to a phase two list. What we usually find is that fixed deadlines do not actually fail because of any single scope change. They fail because process does not adapt fast enough. Process adaptation is the real work.

It depends on the technology stack and the content readiness. For Kayaku, we were able to because they were already paying for HubSpot Breeze AI as part of their existing tools, which removed vendor selection and procurement timeline from the critical path. The training content (technical data sheets, application notes, product documentation) was largely ready, though we did need to send some documents back for updates to make them more readable to the AI. The persona and brand voice work got shared with the chatbot configuration so the AI sounded like the rest of the brand from day one. When the conditions are right, launching together creates a stronger story than launching separately.

You map the actual relationships before you design the structure. For Kayaku, discovery surfaced that ancillary products (developers, removers, adhesion promoters) make up roughly forty percent of the business but do not exist as standalone product pages. They live as recommended add-ons on the products they support. That meant the quote request system needed to be able to add ancillaries to a quote even though they were not standard catalog entities. We built a custom backend solution where ancillaries exist as data entities visible to the quote system but not displayed as their own product pages. The lesson worth generalizing: most product catalogs have these hidden relationships. Surface them in discovery, design around them, do not let them surprise you in development.

You give each audience its own clear path and let visitors self-identify into the right one. For Kayaku, the legacy academic audience needs to find products they already know they want and get to ordering quickly. The industry audience needs application-led content, technical depth, and clear pathways to partnership conversations. The “Who We Serve” section near the top of the homepage lets industry visitors self-select into their applications. Direct product navigation serves visitors who already know what they need. Neither audience has to navigate through the other audience’s content to get to their own.

More guardrails than you think, and more testing than you expect. The “happy path” is easy to demonstrate. The chatbot answers a reasonable question, the visitor is delighted. The hard work is everything around the edges. Adversarial testing to make sure the chatbot does not give away technical data sheets without capturing an email, does not make claims it should not make, does not contradict source documentation. Refining guidelines that shape responses within tight character limits across multiple categories. Sending source documents back for updates when the AI cannot read them accurately. The visible part of the chatbot is only a small part of the work. Most of the implementation is making sure it behaves safely and consistently in cases the visitor never sees.

You make the inconsistency intentional rather than accidental. Kayaku’s site supports four primary languages through GTranslate (English, Chinese, Japanese, Korean). Their SDS documentation, governed by regulatory requirements, exists in additional languages including French, German, and Italian. We considered automatically switching SDS downloads based on the visitor’s site language, but that creates inconsistent behavior across documents (some auto-switch, some do not, depending on language availability) and risks giving the wrong regulatory document to a visitor who needs a specific country version for compliance. We landed on manual language selection for SDS documents, with each version clearly labeled. Predictable beats automated when consistency matters more than personalization.

Shared discovery materials, shared research, shared decisions. Everyone who touched the project consumed the same competitive analysis, the same audience research, the same brand work. Not filtered briefs. The actual research. When a designer made a visual call, they understood why warmth was the differentiation play. When a developer built the quote system, they understood why ancillaries had to behave a certain way. When the AI specialist trained the chatbot, they understood what voice the mascot was supposed to embody. Coordination at this scale is its own discipline, and it is most of the work.

You do not flatten the differences. You give each sub-brand the room it needs to speak to its own audience while making the parent relationship clear and consistent. For Kayaku, that meant strategic color assignments per business unit, distinct content treatments where the audience’s needs differ, and a shared design system that holds the whole thing together. Sub-brands kept their identity. The parent brand became the connective tissue. What we usually find is that the failure mode is either over-flattening (everything looks the same and sub-brand value gets lost) or under-unifying (each sub-brand reads as a separate company). The middle is where the work lives.

Want to learn more about complex B2B website builds?

Explore our insights on multi-brand consolidation and AI integration

Illustration of a person writing notes while holding a phone beside a calculator and desk items

Explore more case studies

See how research-driven methodology delivers measurable outcomes across different industries and challenges.

Or if you’re ready to discuss your situation, let’s have a conversation about whether this approach fits your needs.