Molded

The description states that Molded is a platform for creating interactive product demos using:

• A Chrome extension (Manifest V3) that records browser activity using rrweb, capturing DOM snapshots, clicks, scrolls, and interaction events.
• A dashboard to display recorded sessions.
• A visual Studio where creators can place, resize, and lock spotlight targets over the recorded experience.
• An interactive demo player based on rrweb replay in interactive mode, allowing prospects to follow a guided path and interact with the product interface.
• A publish flow that embeds direction and includes a lead-capturing form.
• Optional OpenAI-powered tour suggestions, with a local fallback for core functionality.

The author claims Molded helps teams capture real browser sessions rather than rebuilding UI as mockups, and aims to make demos feel less like presentations and more like proof of product value.

Inference: The platform appears to be designed to bridge the gap between a polished marketing site and the actual product experience by enabling guided exploration instead of passive video or call-to-action flows.

The author states that Molded is built to address two main issues:

1. Timing of demos: Product demos are often too late in the funnel — by the time someone sees the product, they have already booked a call or dropped off.
2. Gap between marketing and product: There's a disconnect between a polished marketing site and the real product; Molded aims to close this gap by capturing genuine browser sessions.

The core positioning is that “your product is often your best salesperson,” and Molded helps it do that job earlier in the buying journey.

Inference: The platform positions itself as an alternative to traditional demo tools, focusing on immediacy, interactivity, and lead generation through real product exploration rather than passive media or scheduling.

The description states that Molded is intended for sales teams at companies who want to record, build, and deploy interactive demos that turn passive viewers into qualified CRM leads.

It also implies a use case where the demo lives directly on a company’s website, suggesting B2B SaaS or enterprise software companies as likely customers.

Inference: The target customer is likely B2B SaaS firms with product-led growth strategies, sales teams looking to improve lead capture, and organizations that rely heavily on product demonstrations during early-stage engagement.

There is no evidence in the description of a business model or pricing structure. The author does not mention any revenue streams, monetization methods, or pricing tiers.

Not evidenced: No indication of whether Molded intends to charge customers, how it plans to make money, or what kind of pricing model it might adopt.

The project is built using:

• TanStack Start
• React
• Chrome extension (Manifest V3)
• rrweb for recording browser activity
• Supabase for optional cloud storage
• OpenAI API integration for tour suggestions (with fallback)

The author notes technical challenges such as:

• Chrome extension injection timing and tab restrictions.
• Handling navigation, delayed event batches, and unexpected recording ends.
• Making replay fit cleanly into UI components like cards and dashboards.
• Keeping spotlight targets fixed after locking.

They also mention learning how to turn raw sessions into persuasive experiences without making them feel like videos.

Inference: The platform is technically complex but built with modern web tooling. It shows early-stage engineering maturity, though it lacks production-grade reliability or scalability features noted in the "What’s next" section.

The project was submitted to a hackathon (OpenAI 2026), indicating an early-stage prototype.

There is no evidence of:

• Revenue
• Customers
• Usage metrics
• Product adoption
• Any form of traction beyond the author’s own description

Not evidenced: No data on user engagement, retention, or business impact.

The description does not mention specific competitors. However, based on the stated functionality — capturing browser sessions and turning them into interactive demos — Molded likely competes with:

• Traditional demo platforms (e.g., Loom, Vimeo, Screencastify)
• Product-led growth tools (e.g., Productboard, Gainsight, Crisp, Intercom)
• Demo creation tools that allow guided walkthroughs or embedded experiences

It also overlaps with AI-powered demo tools or conversational interfaces, though no such tools are named.

Inference: Molded appears to be in a niche between generic screen recording and full-fledged product experience platforms. It may differentiate itself by combining real browser capture with interactive editing and lead generation.

1. No verified traction or revenue: The project is described as a hackathon submission, with no evidence of market validation.
2. Single founder team: Only one member listed (Dilmi Kottahachchi), which raises questions about execution capacity and scalability.
3. Prototype nature: Built for a hackathon, not production-ready; lacks features like authentication, analytics dashboards, or durable cloud storage.
4. Dependency on Chrome extension and rrweb: These technologies may not scale well or be reliable in enterprise environments.
5. AI layer is described as future work: The OpenAI integration is currently optional and not core to the workflow.

Inference: The risk of failure is high due to lack of product-market fit, limited team size, and unproven commercial viability.

1. Has Molded moved beyond the hackathon prototype stage? If so, what changes have been made?
2. Are there any early adopters or pilot customers currently using the platform?
3. What is the current technical architecture and how does it handle reliability issues like unexpected recording ends or tab navigation?
4. How do you plan to monetize this product — is there a pricing model in mind?
5. What are the key assumptions about user behavior that drive your design decisions?
6. How do you intend to scale beyond a single developer’s effort?