Marketing

What does a Marketing person need to know if they've been asked to provide brand assets for Coassemble?

A plain-language starting point for someone who owns brand assets like logos, colours, and guidelines, and needs enough context to hand them over correctly for a training project they don't yet understand.

Companies that build software often embed training directly inside their own product or website, so a customer or user learns without ever leaving the experience. Coassemble is the tool that powers that training behind the scenes. When a project like this comes together, someone usually needs to supply the actual brand material, logos, colours, fonts, tone of voice, so the training looks and sounds like it belongs to the company showing it, not like a separate tool bolted on. This page is for that person: enough context to understand what's being asked and why, without needing to learn the product itself.

Marketing's involvement can span several touchpoints across an Embed project, not just a single handover of a logo file. Courses need branding applied consistently. Any video included in training, whether that's a product demo, a customer testimonial, or footage supplied by the business, may need editing or trimming to fit properly, and someone needs to sign off that it reflects the brand correctly. Images used throughout a course need approving, whether they're pulled from an existing library or sourced fresh for this project. Depending on how the project is structured, marketing might be looped in once at the start, or repeatedly as new courses get built and each one needs the same checks applied. Knowing which of these applies to a given project is worth clarifying early, rather than assuming it's a single one-off request.

What is Coassemble?

Coassemble is a training layer that other companies build into their own products, websites, or internal systems. It covers the full path from creating a course to getting it in front of the right audience, whether that's onboarding a new employee, teaching customers how to use a product, training partners or resellers, or running compliance-style courses staff need to complete. Courses can be built quickly, including with AI that turns a prompt, an existing document, or even a PowerPoint into a finished course, and then delivered however suits the audience: as a standalone link, shared through everyday tools like Slack, or shown directly inside another company's own product or website. That last option, training appearing inside somebody else's product rather than as a separate link, is what "Embed" refers to, and it's the focus of the rest of this page.

What does "Embed" mean?

Normally, a course built in Coassemble lives on its own, standalone page. "Embed" means that course is instead shown inside somebody else's website or product, so it feels like a native part of that experience rather than a separate site a learner gets sent to.

There are two different ways a company's developers might actually build this, and it's worth knowing which one applies to your project, since it changes who's doing the work and how directly your brand assets get used:

• Ready-made pieces. Coassemble provides drop-in components that developers can place directly into a page: a course player (the full interactive course), a course card or list (a preview tile or browsable list), or the same for a collection of courses. These come with the visual structure already built, so branding gets applied through them directly.
• A fully custom interface, built on the API. Instead of using the ready-made pieces, a company's developers can pull course content, translations, and tracking data directly from Coassemble using something called an API, and build their own completely custom-looking interface around it from scratch. In this case, there's no pre-built visual component at all. The developers are constructing the entire look and feel themselves, using your brand material as their reference, rather than dropping your branding into something Coassemble already built.

Some projects use a mix of both, ready-made pieces for most of it, with a custom-built piece for one specific part. Either way, your brand material (colours, logo, fonts, tone) is what gets used, whether it's applied through Coassemble's own branding tools or built directly into custom code by the company's developers. It's worth asking which approach is being used for your project, since it affects who you're actually handing assets to and how much control you have over the final look.

Why brand assets specifically are needed

For training to feel like part of a company's own product rather than a separate tool, it needs to carry that company's branding: logo, colours, fonts, and tone. That branding has to come from somewhere, which is usually why marketing gets asked to supply it. Depending on the project, this might mean logo files and brand colours, approved images or video, fonts, or written guidance on how the brand should sound. What's actually needed varies project to project, so it's worth confirming directly with whoever raised the request rather than assuming.

What's typically needed

If ready-made pieces are being used, branding is usually applied through something in Coassemble called the Brand kit, which is just the tool's name for the place where all of this gets set up. Direct access to it usually isn't necessary. If a custom interface is being built instead, the same material gets handed to developers to build directly into their own code. Either way, what matters is supplying the raw material:

• Logo files. Ideally in a few formats and sizes, the same kind of thing you'd give any partner or vendor who's putting a logo somewhere.
• Brand colours. Hex codes if available, or a link to existing brand guidelines.
• Fonts. Which typefaces are used for headings and body text, and whether actual font files exist or just the names.
• Tone of voice guidance. How the brand talks, if documented. This shapes the language inside the course itself, not just the visuals.
• Approved images. Any photo or illustration library already in use, so course content pulls from images already signed off on rather than generic stock.
• Video assets, if any are involved. Product demos, testimonials, or other footage may need editing, trimming, or re-formatting before they're suitable for a course, and someone needs to confirm the final cut is brand-appropriate.
• A cover image. Whatever should represent this course visually before someone opens it, similar to a thumbnail.

A full brand guidelines document, if one exists, often answers most of the above in a single file.

Other things that might come up

A few extra questions may surface depending on the project. None of these require understanding how the product works, just knowing the brand and business well enough to answer:

• Is this being built with ready-made pieces, or a fully custom interface? Worth asking early, since it changes whether your assets get applied through Coassemble's tools or built directly into custom code.
• Should the logo be the only one visible, or is it fine if Coassemble's name shows too? Some setups can hide the "built with Coassemble" mark entirely, so courses look fully native. This depends on which plan is being used, so it's a question for whoever owns that vendor relationship, not something that needs chasing down independently.
• Does this need to look different for different customers? If the company serves multiple customer brands through the same setup, each one can be made to automatically show its own branding rather than someone manually swapping it per course. Worth flagging if this applies.
• Does this need to exist in more than one language? If so, mention it early. It's easier to plan for translation upfront than to add it after content is finished.
• What should someone see or do the moment they finish the course? This is a small but valuable piece of design, often a thank you message or a link back to the product. A specific page to send people to, or a specific message, is worth deciding early rather than leaving as an afterthought.
• Will this be a single review, or ongoing sign-off? Some projects need brand and asset approval once upfront. Others involve new courses being added over time, each needing the same checks repeated.

A few questions worth asking back

Since this request usually lands partway through a project already in motion, these help make sure the right material goes over the first time, and that expectations about ongoing involvement are clear from the start:

• Is there a deadline to work towards?
• Is this being built with Coassemble's ready-made pieces, or is it a custom interface built by our own developers?
• Which of the pieces described above (course player, card, list, collection) are actually being used, so it's clear what needs branding?
• Is this a one-off course, or an ongoing programme where more courses will be added later? If ongoing, it's worth handing over full brand guidelines once, rather than answering the same questions course by course.
• Will there be video content involved, and if so, who's responsible for the actual editing versus who's just approving the final version?
• Has anything already been built? If so, this may be a case of retrofitting branding onto something that already exists, which is worth knowing upfront.

Frequently asked questions

Do I need to log into Coassemble myself?

Not necessarily. In many cases, the brand owner is just the source of material, logos, colours, fonts, guidelines, video, and image assets, and someone else, whether that's through Coassemble's own tools or custom code, applies it.

What's the difference between a course player and a course card?

A course player is the full course someone clicks through and completes. A course card or course list is a smaller preview or browsable list pointing to available courses. Both can carry branding.

What does it mean if developers are "using the API" instead of the ready-made pieces?

It means they're pulling the underlying course content and data directly from Coassemble and building their own custom-looking interface around it, rather than using Coassemble's pre-built visual components. Your brand assets still get used, just built in more directly by the development team rather than dropped into an existing template.

Can a company's logo be the only one visible, with no mention of Coassemble at all?

In many cases yes, though it depends on the specific setup being used. Whoever owns the account or vendor relationship can confirm this.

What if a company works with multiple customers or brands?

It might matter. If the same underlying setup serves more than one customer brand, each one can potentially be configured to show its own branding automatically. Worth flagging early if it applies, since it changes how the branding gets set up.

Do I need to edit video myself?

Not necessarily; that depends on how the project is set up. Sometimes marketing supplies raw footage and someone else edits it. Other times, marketing is expected to hand over an already-edited, ready-to-use version. Worth clarifying which applies before assuming either way.

What if brand material isn't all ready yet?

Sending what's available is fine. Logo and colours are usually the highest priority; tone of voice and approved imagery can often follow shortly after without holding up the project.