Emerging Trends | SunMatrix Ramble

Runway Characters: Real-time AI avatars

A real-time AI avatar is a video-based conversational agent that can listen, respond, and show synchronized facial movement during a live interaction.

Runway Characters is not just another image-to-video feature. It points to a bigger shift: interfaces that talk back, maintain expression, and sit inside websites, apps, support journeys and training environments as an interactive layer.

From chatbot box to embodied interface

For years, the consumer web has treated conversation as a text box. Runway Characters pushes the interaction into a more human-shaped format: a visual character with a voice, a defined personality, domain knowledge and live responsiveness.

The enterprise value is not the avatar; it is the controlled interaction layer around the avatar.

A controlled interaction layer is the set of rules, knowledge sources, permissions, actions, escalation paths and measurement signals that determine what the avatar can say and do.

This is why the product is more interesting for operators than for novelty-watchers. A branded face is easy to demo; turning it into a trusted, scalable and measurable service interface is the hard part.

The mechanism: image, voice, knowledge and action

The mechanism is straightforward: a single reference image defines the character, voice and personality shape the interaction, a knowledge base keeps the response inside a domain, and API actions allow the character to do work rather than just talk.

For enterprise teams, this turns the avatar from a creative asset into a governed service surface that sits between consumers, content, data and workflow.

A governed service surface is a customer-facing interface whose content, permissions, actions, analytics and escalation rules are deliberately controlled.

Because the avatar can combine expression, domain knowledge and actions in the same interaction, the experience can move from navigation to guided execution.

That is the commercial hinge. The avatar is not valuable because it smiles; it is valuable when it helps someone finish a task faster, with less confusion and fewer handoffs.

Where Runway Characters could create real utility

The obvious use cases are the ones Runway highlights: tutoring and education, customer support, training simulations, and interactive entertainment or gaming. Those are credible because the value depends on response, patience, expression and repetition.

The stronger enterprise use case is guided commerce and product selection. A character that understands a product range, asks clarifying questions, checks fit, explains trade-offs and hands off to the right next step could reduce decision friction in categories where consumers need guidance.

Brand and marketing experiences are another useful path, but only if they avoid becoming mascot theatre. A brand character should answer, guide, qualify, educate or convert; otherwise it is just a high-cost animation layer with weak business intent.

The real question is not whether the avatar looks impressive; it is whether the interaction reduces effort, shortens a service path, or improves a decision.

The operating model matters more than the character

The failure mode is predictable: teams launch a polished avatar before defining ownership, content governance, privacy boundaries, escalation logic and measurement. That creates a visible interface with unclear accountability.

For consumer experience platforms, the hard work sits behind the face. The avatar needs approved knowledge, consent-aware data access, clear action limits, analytics events, brand controls, QA scripts and a fallback path when confidence is low.

This also changes the content model. Product information, policy content, service scripts and training material need to be structured enough for a live character to use safely, not just published as static pages for humans to browse.

Runway Characters takeaway for enterprise teams

Runway Characters should be evaluated less like a creative tool and more like a new front-end pattern for service, learning, commerce and brand interaction. The adoption question is not “can we make a character?” but “which consumer or employee journey deserves a live conversational interface, and can we govern it?”

Takeaway: Treat real-time AI avatars as governed service surfaces, not animated brand assets. The winning teams will connect character design to knowledge governance, journey ownership, action permissions, measurement and fallback logic before scaling the experience.

A few fast answers before you act

What is Runway AI?

Runway is an AI company building generative media tools and world-simulation research systems. Runway describes its mission as building AI to simulate the world through the merging of art and science.

What is Runway Characters?

Runway Characters is Runway’s real-time avatar product for creating conversational video characters with customizable appearance, voice, personality, knowledge and actions.

Why does it matter for brands?

It matters because it can turn static content, support flows and training material into live guided interactions that feel more natural than a chatbot.

What are the best first use cases?

The best first use cases are narrow, repeatable journeys where guidance reduces effort: product advice, customer support triage, onboarding, training practice and education.

What is the main enterprise risk?

The main enterprise risk is launching a convincing avatar without clear governance over what it knows, what it can say, what it can do and when it must escalate.

How should teams measure success?

Teams should measure task completion, deflection quality, conversion support, time saved, escalation rate, user satisfaction and the cost of maintaining the knowledge base.

Manus AI: Action Engine for Marketing

Manus AI is interesting because it changes the unit of AI adoption in marketing. The useful question is no longer whether AI can write better copy, but whether it can safely execute repeatable marketing work across tools, accounts and output formats.

Vaibhav Sisinty, founder of GrowthSchool, frames the hype in the video, but the useful part is the work pattern: browser shopping, download cleanup, Meta ads analysis, Slack triage, influencer research, prototype building and Telegram-based task handoff.

These are not glamorous use cases. They are the small operational gaps that make marketing teams slower than they should be: extracting data, checking dashboards, comparing options, building lists, scanning messages, formatting outputs and turning loose requests into usable artefacts.

The operating shift: from answer to action

Most marketing teams still use AI as an answer layer. They ask for ideas, summaries, drafts, research angles, prompt variants or campaign copy, and then people still move the work manually through browsers, spreadsheets, CMS workflows, ad platforms, project tools and approval chains.

Manus describes itself as an action engine. An action engine is an AI layer that can plan, execute and package work across tools, rather than only generate recommendations.

The mechanism is straightforward: Manus combines planning, browser operation, connectors, file access, code generation and output packaging, so a marketing request can move from prompt to finished artefact without being manually rebuilt in five separate tools.

For marketing teams, that puts the pressure point on operating model design, not on prompt novelty.

This mechanism matters because execution creates real business value only when the system can reach the right tools, use the right data, follow the right rules and hand back something a team can trust.

The marketing question: control before scale

The real question is whether a marketing organization can give any agent safe enough access, clear enough tasks and strong enough controls to make the output usable.

The stance here is clear: treat Manus as a workbench for bounded execution, not as a replacement for marketing judgment.

In a real marketing stack, that distinction matters because the work crosses content systems, asset libraries, product data, CRM, analytics, ad platforms, consent, identity and approval workflows.

The Meta angle matters, but not as gossip

Manus still presents itself as part of Meta, while recent reporting says China has blocked the acquisition or ordered the transaction unwound. That tension deserves a brief mention, but it should not dominate the argument.

The business signal is not the takeover drama. It is that the market is moving from AI tools that advise marketers to AI systems that can sit closer to actual work.

That is why the Meta connection is relevant: ads, creators, messaging and business pages are workflow surfaces, not just media surfaces.

If an execution agent can sit near those surfaces, the commercial value is not another content generator. The value is shorter distance between insight, action, packaging and follow-up.

Governance decides whether this scales

An agent that can open browsers, read accounts, analyze campaigns, create files, draft replies and ship prototypes is useful only when access rights, approval steps and logs are explicit. Before scaling it, marketing teams need to define which accounts can be touched, which actions are read-only, which outputs require human approval, which data is excluded and which records prove what happened.

Without this, the failure mode is obvious. The agent becomes another shadow workflow, fast enough to bypass controls and persuasive enough to hide weak evidence.

That is also where adoption gets decided. People will not use an agent because it is magical; they will use it because it removes low-value work without making them responsible for invisible risk.

What marketing teams should operationalize

The practical move is not to connect everything at once. Start with bounded, reversible work: campaign monitoring, reporting summaries, initial lists of potential creators and influencers, content calendars, competitive scans, meeting follow-ups, prototype briefs and internal workflow cleanup. These jobs have enough friction to matter, enough structure to test, and low enough downside if a human reviewer stays in the loop.

Takeaway: Offerings like Manus AI are useful for marketing when they are treated as execution layers for controlled workflows, with clear access rules, human approval points, source checks, output QA and measurable time saved.

A few fast answers before you act

What is Manus AI?

Manus AI is a general-purpose AI agent designed to execute tasks, not just answer prompts. In marketing, that means it can support research, reporting, campaign analysis, workflow automation and prototype creation when access and review are controlled.

How is Manus different from ChatGPT or Claude?

ChatGPT and Claude are usually used as reasoning and drafting interfaces. Manus is positioned closer to an execution environment because it can use browser operation, connectors and output generation to turn a request into a finished artefact.

Should marketing teams connect Manus to real accounts?

Not without data governance and security review. Start with read-only access where possible, confirm what data leaves your environment, exclude sensitive customer or employee data, require human approval before external actions, and keep logs for every workflow that affects campaigns, customers or brand assets.

Does the Meta acquisition story change the marketing argument?

Only slightly. The ownership story is unstable, but the operating lesson is stable: AI agents are moving closer to ads, creators, messaging, commerce and business workflows.

What is the best first use case for Manus in marketing?

Start with recurring analysis and packaging work. Weekly campaign summaries, potential creator and influencer lists, competitor scans and meeting-to-action-plan workflows are easier to govern than live publishing or customer-facing execution.

Nas.com: Photo to Full-Funnel Marketing

From lead capture to full-funnel self-service

In December, I used Nas.io as an example of AI shrinking one specific acquisition job: describe the offer, generate a simple lead-capture page, and give a non-technical user a working front door to demand. Four months later, the proposition is materially bigger and rebranded as Nas.com, which now presents a workflow that starts with a photo and expands into storefront setup, listing creation, marketing content, ad creation, and customer acquisition support from the same system.

The mechanism is more important than the brand story. Nas describes onboarding from a prompted idea or photo, then layers in content generation for visuals, ads for campaign creation, lead discovery, and direct outreach, so the user is not just building a page but moving from product image to market-facing execution inside one operating environment. Its own documentation frames that environment as the place to create products, set up the website, run marketing tools, and manage the business in detail.

That is a meaningful expansion from their narrower self-service example from December.

It lands because it compresses several steps that normally sit across separate tools and handoffs. The same workflow helps a user move from product image to storefront, assets, and first activation steps, which is exactly what the live demo below shows.

What Nas is really signaling

What Nas is really signaling is a photo-to-market self-service workflow in which a simple image or prompt triggers page creation, asset generation, activation setup, and early demand capture inside one platform.

That is the important shift. The story is no longer that AI can make content. The more important move is that work which normally sits across separate tools and specialist queues, storefront setup, creative production, ad launch, lead discovery, and outreach, is being compressed into one connected operating layer. On Nas’s own marketing assets, the promise is clear: build the store, generate the listings and content, help with marketing, and move directly into customer acquisition from the same environment. That same positioning is paired with a scale claim that 350,000 people across 150+ countries are already selling on the platform.

Enterprise teams should treat this as an operating-model signal about how marketing work will increasingly be expected to function.

The real question is whether your brand, content, CRM, and commerce stack can let non-technical teams do the equivalent safely, quickly, and with governance.

No serious enterprise is going to replace its CMS, PIM, DAM, CIAM, consent layer, analytics stack, or media controls with a creator platform. That would miss the point. The real enterprise implication is expectation shift. Once people see more of the path from offer to activation compressed into one guided flow, they stop accepting ticket queues, repeated re-entry, and tool switching as normal for work that should already be semi-automated.

Why this matters for consumer experience platforms

For enterprise teams, this is less about storefront software and more about workflow design. A consumer experience platform only becomes commercially useful when it can turn brand intent into live, measurable market activity without making every step depend on specialist mediation.

That is why the Nas example matters. It does not just simplify creation. It pulls creation and activation closer together. The page, the assets, the ad setup, the lead discovery, and the outreach logic sit near each other in the same operating layer. That proximity matters because every extra handoff slows launch speed, raises coordination cost, and makes self-service impossible in practice.

This is where many large organisations are still weak. They may own all the component systems, but the systems do not behave like one usable operating model for non-technical teams. Capability exists. Flow does not.

What the enterprise should copy, and what it should not

The lesson is not to let anyone prompt anything. The lesson is to package complexity behind automated, governed workflows.

That means approved prompts, approved source data, brand-safe templates, channel rules, claims controls, embedded legal checks, human review thresholds, role permissions, and measurement wired into one non-technical, low-friction flow. If that wiring is missing, self-service becomes rework, inconsistency, and compliance debt dressed up as speed.

The practical target is not more AI content. The target is governed prompt-enabled execution across the journey, asset creation, landing-page setup, product-page enrichment, lead capture, paid activation, and performance measurement, all with clear ownership and auditability built in.

The move to make now

If you run a consumer experience platform, start by choosing one repeatable workflow where speed matters, governance is manageable, and value is visible. Product-detail enhancement, campaign landing pages, local paid-social creative, and email variant creation are better starting points than broad AI transformation programmes because they force workflow clarity, ownership, and measurable outcomes.

Takeaway: remove tech complexity and enable brand teams to create and activate their own assets through AI prompts inside governed workflows now, or be ready to play catch-up when competitors make this level of self-service feel normal.

A few fast answers before you act

Is Nas.com just another storefront builder?

No. Nas is positioning the product more broadly than storefront hosting. Its own marketing assets describe store setup plus content generation, ad launch, lead discovery, and outreach from the same environment.

What is the most important shift in this example?

The shift is that creation and activation are being compressed into one guided workflow, which reduces the gap between having something to sell and being able to put it in front of demand.

Is this fully automatic marketing?

No. The help documentation describes tools that simplify creation, ad setup, lead finding, and outreach, but the user still chooses goals, reviews outputs, and decides what to run.

What should enterprise teams copy first?

Copy the workflow logic first. Pick one repeatable use case where a non-technical team should be able to move from idea to approved market output with minimal handoffs.

What has to be true for this to work in an enterprise?

You need approved data sources, prompt guardrails, template logic, review thresholds, permissions, and measurement embedded in the workflow, not bolted on later.

Why act now instead of waiting?

Because once this interaction model becomes normal outside the enterprise, internal teams will stop accepting fragmented execution models as inevitable. The firms that win will be the ones that hide complexity without giving up governance.