# Roseram: consumer features, product direction and marketing ideas

Reviewed 2026-10-12. 69 distinct capability/workflow entries, grouped into five product areas. This is a sourced product reference, not a certification that every workflow is available in every account or deployed in its latest form.

## Contents

1. [Consumer proposition and audiences](#the-consumer-proposition)
2. [Status definitions](#how-to-read-this-inventory)
3. [Current authored-library snapshot](#current-authored-library-snapshot)
4. [Plans, learning products, shop and connections](#product-packaging-and-catalog)
5. [Workspace capabilities](#workspace-understand-create-and-improve)
6. [Delivery and connections](#delivery-keep-publish-and-connect-your-work)
7. [Business and referrals](#business-and-referrals-connect-activity-to-outcomes)
8. [Knowledge and community](#knowledge-and-community-make-a-better-next-decision)
9. [Account and supporting products](#account-access-plans-and-supporting-products)
10. [Campaign angles and messaging boundaries](#campaign-angles-to-elaborate)
11. [Development record and direction](#development-record-and-direction)

## The consumer proposition

**Roseram brings project-aware AI assistance, editable source, previews, delivery controls, practical learning and business context into one application.** Start with an idea or existing source, choose whether to ask, plan or build, inspect the result, and deliberately decide what to publish.

The strongest distinctive story is the continuity of that workflow. These are product characteristics, not independently verified claims of world-first invention, universal compatibility or superiority over every competing tool.

### A short product description

Roseram is an AI-assisted workspace for building and improving software, supported by practical guides, product research and business/referral tools. It connects a project’s purpose, source, language and preview state to the agent’s working context. Valid Build changes can update the working copy automatically, with recovery and reversion controls. Account, provider, browser and runtime requirements apply to individual features.

### Who it can help

| Audience | Starting problem | Relevant workflow | Marketing seed |
| --- | --- | --- | --- |
| Independent builder | A useful idea without a clear first implementation | Plan → clarify → Build → preview | “Make the first version understandable, then make it work.” |
| Existing-project maintainer | Changes require rediscovering an unfamiliar codebase | Import → source discovery → focused edit → verification | “Work with the project you already have.” |
| Small business | A site needs improvement and a clearer customer journey | Project/site management → scoped edits → publication → available analytics | “Keep the application connected to the business it serves.” |
| Designer or creative builder | A visual brief and implementation need to stay related | Source-aware building plus configured image generation | “Bring the brief closer to the interface.” |
| Learner | Generic AI advice is hard to put into practice | Task guide → adaptable brief → checklist → Workspace | “Learn a method you can use on your next project.” |
| Responsible affiliate | Visits, leads, sales and earnings get conflated | Private attribution → activity ranking → eligible revenue ledger | “See the relationship develop, with the numbers explained.” |
| Technology evaluator | Launch announcements and AI claims lack context | Reviewed profile → primary references → fit/limitations | “Discovery is a starting point; evidence helps you choose.” |

Enterprise procurement, compliance certification, guaranteed native support and unrestricted automation are not established by these audience examples.

## How to read this inventory

- **Implemented in source:** a concrete implementation or documented local verification exists. This is not blanket production certification.
- **Provider / runtime / browser / payment dependent:** the workflow needs its stated services, permissions, compatible browser or runtime. A button alone does not establish readiness.
- **Editorial in source:** authored content exists in the application. Indexing, rankings and the deployment of the latest revision are separate states.
- **Limited / preview / development / planned:** retain that label in marketing. Do not turn a product direction into an available capability.
- **Live data checked previously:** a dated implementation report records a read-only provider check. This audit did not repeat authenticated payments, signup, generation, native release or referral events.

Prices, allowances, trials, registration policies and release packages can change. Use the current checkout or release page before a promotion. This guide does not promise a release date, ranking, financial return or error-free operation.

## Current authored-library snapshot

| Collection | Current source count | Definition |
| --- | ---: | --- |
| Practical guides | 112 | Individual authored guide records; approximately 70,344 counted article words |
| Case studies | 100 | Editorial analyses, not all Roseram customer stories |
| AI public-record case files | 15 | Cases distinct from the 14 separately labelled provider buyer guides |
| Researched launch profiles | 8 | Completed editorial records, separate from the imported research catalog |

These counts describe source collections as reviewed, not indexed URLs, traffic, paid customers, demand or rankings.

## Product packaging and catalog

### Workspace access plans

The following is the **local pricing configuration reviewed on 2026-10-12**, not a verified live checkout quote. Promotions should use the actual current checkout price, eligibility, renewal and cancellation terms. All four configured trials are 24 hours; earlier conversation requests for 48 hours are not the current pricing configuration.

| Configured plan | Monthly USD | Included usage USD |
| --- | ---: | ---: |
| Plus Starter | $5 | $5 |
| Pro Starter | $20 | $20 |
| Plus Super | $20 | $20 |
| Pro Super | $200 | $200 |

Usage is metered. Do not convert an allowance into a claim of unlimited inference, images, video, support or third-party compute. Optional credits and external provider costs have their own terms.

### Learning products

The source catalog contains 13 individual learning programs and one suite. These are distinct from the currently full Training offering and its waitlist. Current purchase eligibility, lesson access, plan inclusion and digital fulfillment need a live check. Prices below are source-catalog USD one-time amounts, not a promise that checkout is open.

| Source-catalog learning product | Configured USD | Product page |
| --- | ---: | --- |
| Traffic foundations | $19 | [/learn/foundations](https://roseram.com/learn/foundations) |
| SEO | $39 | [/learn/seo](https://roseram.com/learn/seo) |
| PPC · Google Ads | $49 | [/learn/ppc](https://roseram.com/learn/ppc) |
| Article marketing | $29 | [/learn/articles](https://roseram.com/learn/articles) |
| Banner advertising | $29 | [/learn/banners](https://roseram.com/learn/banners) |
| Outreach | $29 | [/learn/outreach](https://roseram.com/learn/outreach) |
| Video marketing | $39 | [/learn/video](https://roseram.com/learn/video) |
| Content creation | $29 | [/learn/content](https://roseram.com/learn/content) |
| List building & email marketing | $49 | [/learn/email](https://roseram.com/learn/email) |
| Affiliate marketing | $39 | [/learn/affiliate](https://roseram.com/learn/affiliate) |
| Social & community growth | $29 | [/learn/social](https://roseram.com/learn/social) |
| Conversion & analytics | $39 | [/learn/conversion](https://roseram.com/learn/conversion) |
| Online income models | $39 | [/learn/income](https://roseram.com/learn/income) |
| Super Intelligence Suite | $129 | [/learn/suite](https://roseram.com/learn/suite) |

The suite describes all 13 current-edition programs, 52 lessons, exercises, prompt labs and project notebooks. AI usage credits, advertising spend, live coaching and an accredited qualification are excluded from that product description. Do not imply income, employment, placement or certification guarantees.

### Physical storefront and preorder families

The Shop source catalog lists Morning Being, Evening Being, Cell Being, Clean Being in the VERSO Being collection. It also contains these proposed Roseram preorder families:

- **Super Intelligence Vitamins:** 16 catalog variants.
- **Super Intelligence Water:** 5 catalog variants.
- **Super Intelligence Coffee:** 18 catalog variants.

A listing does not establish inventory, an enabled checkout, fulfillment capacity or verified label claims. Earlier operations notes record paused ordering; current availability must be checked. Do not infer improved intelligence, health or cognition from branding.

### Connection scope

These connection options appear in the current integration catalog. Authentication configuration and account permissions still need to be supplied and verified; a connected account is not proof of every downstream action.

| Provider | Connection surface | Scope stated in the catalog |
| --- | --- | --- |
| GitHub | OAuth or token | Repositories, branches, commits, and pull workflows. |
| GitLab | One-click OAuth | Account connection available; repository import and push are not yet supported. |
| Bitbucket | One-click OAuth | Account connection available; repository import and push are not yet supported. |
| Azure DevOps | Microsoft OAuth | Account connection available; repository import and push are not yet supported. |
| Supabase | OAuth or Management API token | Postgres, Auth, Storage, and realtime services. |
| Neon | API key | Serverless Postgres projects and branches. |
| Vercel | Access token | Projects, deployments, domains, and environment variables. |
| Netlify | OAuth or personal access token | Sites, deploys, domains, and build configuration. |
| Cloudflare | Sign in (recommended) or scoped API token | Pages, Workers, zones, DNS, and edge services. |
| HubSpot | OAuth or private app token | Contacts, companies, deals, campaigns, and customer operations. |
| X | OAuth 2.0 + PKCE | Plan original posts and monitor conversations through X’s own search. |

GitHub is the established repository delivery path. GitLab, Bitbucket and Azure DevOps account authorization must not be promoted as functioning repository import/push. Generic database, CRM, hosting and social connections do not automatically reproduce a project's production secrets or enable arbitrary external actions.

## Workspace: understand, create and improve

### 1. Build, Chat and Plan

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Build can apply validated working-copy edits. Chat stays conversational. Plan returns requirements, questions and a practical roadmap.

**Marketing hook:** “Choose whether today calls for an answer, a plan or a working change.”

### 2. Project-aware indicator

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

A compact badge exposes detected project purpose, source, languages and runtime state on hover, focus or tap. The same guidance enters agent context.

**Marketing hook:** “Your project has a context. Your coding assistant should share it.”

### 3. Website and mobile source detection

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Framework and path signals distinguish web and mobile source. Other languages use a general code-project path; native device support is not certified.

**Marketing hook:** “An existing app deserves an assistant that starts by understanding its shape.”

### 4. Marketing and creative intent detection

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Request signals can classify marketing, image, video and voice intent and change the agent guidance. Classification does not activate an unimplemented service.

**Marketing hook:** “The direction follows the task you are actually doing.”

### 5. New project creation from a brief

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Generation can create a saved account project with complete source. Missing decisions can trigger focused clarification instead of inventing requirements.

**Marketing hook:** “Turn a useful idea into source you can keep improving.”

### 6. GitHub repository context

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Connect a repository and branch, index its tree and load relevant text source on demand. Credentials, permissions and import limits apply.

**Marketing hook:** “Bring the project you already have.”

### 7. Approved local-folder import

**Status:** Browser dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Supported browsers import selected local files into a bounded working copy. This is not a complete physical duplication of every file or permission to edit nearby folders.

**Marketing hook:** “Start with your own folder, with your original files under your control.”

### 8. Relevant source discovery

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

The agent can request missing source inside the active project. Path, branch, scope and bounded-repeat checks constrain retrieval.

**Marketing hook:** “Less rebuilding context; more working on the actual problem.”

### 9. Code editing and file navigation

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Browse loaded source, edit files and manage working-copy creates/deletes. Editor recovery includes a simpler fallback when the rich editor fails.

**Marketing hook:** “Read the source, change the source, understand the result.”

### 10. Automatic Build application

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Valid Build changes update the working copy after static and baseline checks. This is not automatic Git push or automatic production deployment.

**Marketing hook:** “The edit lands in your workspace, with a route back.”

### 11. History and reversion

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Snapshots and change history support restoring work. Conflict checks prevent a reversion from silently replacing newer edits.

**Marketing hook:** “Experiment with a recovery path.”

### 12. Previous/current comparison

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Optional dual preview columns help compare before and after. This is a visual review aid rather than evidence of a successful deployed release.

**Marketing hook:** “See what changed without reconstructing what came before.”

### 13. Live preview routing

**Status:** Runtime dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Static output, compatible browser execution and a paired local runtime use different preview paths. A running preview does not establish every backend feature works.

**Marketing hook:** “Close the loop between a request, a source change and an interface.”

### 14. Preview preparation progress

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Preparation exposes source-loading and runtime stages, bounded waits, useful failures and retry paths instead of an indefinite placeholder.

**Marketing hook:** “Know what the preview is waiting for.”

### 15. Responsive preview choices

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Fit, desktop, tablet and mobile preview sizes support responsive inspection. These are not native-device certification.

**Marketing hook:** “Review the small-screen experience before it becomes a customer problem.”

### 16. Improve findings and internal actions

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Readiness, diagnostics and suggestions can become a structured internal agent action after a Yes/No summary. Normal generation and usage rules apply.

**Marketing hook:** “See the issue. Confirm the intent. Let the workspace handle the instruction.”

### 17. Application metadata assistance

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Source-based metadata suggestions offer title, description, canonical and other scoped improvements with manual overrides. Useful metadata does not guarantee ranking.

**Marketing hook:** “Make the next release easier for people and search engines to understand.”

### 18. Favicon studio

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Generate three monogram variants or normalize a supported uploaded image. Choose an icon and export common sizes; wiring it into source remains a verified Build task.

**Marketing hook:** “Give a new application a recognizable first impression.”

### 19. Session environment values

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Settings accepts project-scoped environment values in memory. Only names enter model context. Values clear on scope change or reload; durable encrypted storage is not yet implemented.

**Marketing hook:** “Give the runtime what it needs without pasting secrets into a prompt.”

### 20. Generation stages and cancellation

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Owner-scoped jobs expose context, reasoning, tools, validation and saving stages. Bounded execution and cancellation reduce ambiguous hanging requests.

**Marketing hook:** “A longer task should still tell you where it stands.”

### 21. Usage and reasoning controls

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Requests use the selected routing/effort policy and metered allowance. The Roseram label is a product interface, not evidence of a proprietary foundation model.

**Marketing hook:** “Match the effort to the work and keep usage visible.”

### 22. Activity and diagnostics surfaces

**Status:** Implemented in source · **Entry:** [/workspace](https://roseram.com/workspace)

Project activity, runtime output, request errors and slow-operation observations support troubleshooting. Collection is bounded and not comprehensive surveillance.

**Marketing hook:** “A failure should leave something useful to investigate.”

### 23. Provider-backed image generation

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

An authenticated, metered image route returns usable image data when the configured provider succeeds. Provider configuration, allowance and availability are required.

**Marketing hook:** “Move from a visual brief to an image in the working context.”

## Delivery: keep, publish and connect your work

### 1. Saved account projects and recovery

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Account projects preserve eligible source and conversation; browser recovery helps retain work around interruptions. Remote persistence requires configured account services.

**Marketing hook:** “Return to the project rather than begin the conversation again.”

### 2. Roseram site/subdomain publication

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Publish supported project output through the hosting workflow, including a Roseram site identity. Review configuration and verify the live result.

**Marketing hook:** “Give a working idea a destination people can visit.”

### 3. Existing GitHub publication

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Review eligible source for commit, branch and available merge workflows using the connected account. External writes remain explicit.

**Marketing hook:** “Keep the workspace connected to your delivery workflow.”

### 4. New GitHub repository creation

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Create a reviewed repository with explicit visibility, private by default. The publication payload covers eligible loaded text, not an implicit full clone of every unloaded or binary file.

**Marketing hook:** “Start in the workspace; keep the result in your own repository.”

### 5. Explicit local save-back

**Status:** Browser dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Supported folder/file writes check baselines and use scoped permissions. Original disk files are changed through deliberate save actions rather than every agent edit.

**Marketing hook:** “Keep a clear line between trying a change and replacing your original files.”

### 6. Projects and site identity in Business

**Status:** Provider dependent · **Entry:** [/business](https://roseram.com/business)

Business links account-owned projects and sites with publishing and management views. Existing site identity is reused where supported.

**Marketing hook:** “Build it once; manage the same project as it grows.”

### 7. Domains and hosting connections

**Status:** Provider dependent · **Entry:** [/business](https://roseram.com/business)

Domain and deployment interfaces connect eligible sites to configured providers. Provider permissions and DNS/hosting verification still apply.

**Marketing hook:** “Bring the published work closer to your own brand.”

### 8. Paired local runtime helper

**Status:** Runtime dependent · **Entry:** [/workspace](https://roseram.com/workspace)

A Node companion runs compatible projects in a temporary copy through a paired loopback connection. Local scripts and dependencies still require trust and a usable development command.

**Marketing hook:** “Run supported source close to the machine you control.”

### 9. Optional hosted preview

**Status:** Provider dependent · **Entry:** [/workspace](https://roseram.com/workspace)

Configured hosted execution is a separate explicit destination and can incur provider charges. It is not the default proof that all repositories can run.

**Marketing hook:** “Choose the runtime that fits the project and the cost boundary.”

### 10. Desktop, mobile and extension clients

**Status:** Limited / development · **Entry:** [/download](https://roseram.com/download)

Desktop and extension internal packages and mobile source exist. Production signing, native auth/device checks and store or managed distribution are separate release gates.

**Marketing hook:** “The same workspace, with more ways to reach it as releases mature.”

## Business and referrals: connect activity to outcomes

### 1. Business desk

**Status:** Provider dependent · **Entry:** [/business](https://roseram.com/business)

Account-scoped views organize sites, email setup, audiences, campaigns, analytics, billing and referrals. A navigation item does not prove a provider is connected.

**Marketing hook:** “Your application and its business context can grow together.”

### 2. Audience, list and form tools

**Status:** Provider dependent · **Entry:** [/business](https://roseram.com/business)

CRM/email surfaces organize consent-aware audiences and capture forms through configured services. Third-party delivery and account permissions remain prerequisites.

**Marketing hook:** “Build a relationship with people who chose to hear from you.”

### 3. Campaign and automation controls

**Status:** Provider dependent · **Entry:** [/business](https://roseram.com/business)

Configured email/campaign operations have preparation and confirmation paths. No unrestricted outreach, guaranteed delivery or automatic external send is implied.

**Marketing hook:** “Prepare the message with its audience and purpose in view.”

### 4. Private referral dashboard

**Status:** Provider dependent · **Entry:** [/business?section=earnings](https://roseram.com/business?section=earnings)

Account-linked referral links, click activity, conversions and ledger states keep a user’s own results separate from other affiliates.

**Marketing hook:** “Know what your introductions actually produced.”

### 5. Lifetime referred-account association

**Status:** Implemented; live data checked previously · **Entry:** [/business?section=earnings](https://roseram.com/business?section=earnings)

A confirmed referred account keeps its first recorded affiliate association. Later cookies or links do not replace that ownership; historical sales are not fabricated.

**Marketing hook:** “A customer relationship can outlast a browser cookie.”

### 6. Private lead attribution

**Status:** Implemented; live data checked previously · **Entry:** [/business?section=earnings](https://roseram.com/business?section=earnings)

Accepted Roseram opt-ins and account events use a private identity ledger with reconciliation. Unconfirmed requests and external merchant forms are not inferred as qualified leads.

**Marketing hook:** “See the relationship develop from an introduction to a recorded lead.”

### 7. Activity-based leaderboards

**Status:** Implemented; live data checked previously · **Entry:** [/business?section=earnings](https://roseram.com/business?section=earnings)

A shared Roseram board defaults to 24 hours, with 7- and 30-day choices and multiple ranking metrics. Unique clicks, leads, sales and revenue contribute to points.

**Marketing hook:** “Momentum deserves visibility before the first sale.”

### 8. Opt-in public aliases

**Status:** Implemented in source · **Entry:** [/business?section=earnings](https://roseram.com/business?section=earnings)

Public ranking participation is optional. Generated aliases and aggregate results avoid publishing complete names, emails, wallets and referral codes.

**Marketing hook:** “Share the performance you choose, with your identity under your control.”

### 9. Revenue, spend and earnings columns

**Status:** Provider dependent · **Entry:** [/business?section=earnings](https://roseram.com/business?section=earnings)

Recorded plan/credit sales, referred spend, usage and earnings are separate measurements. Public financial aggregates require deliberate visibility choices.

**Marketing hook:** “Clicks, leads, sales and earnings each tell a different part of the story.”

### 10. Net-proceeds commission model

**Status:** Settlement dependent · **Entry:** [/how-to-make-money](https://roseram.com/how-to-make-money)

The displayed Roseram policy is 50% of eligible positive settled net proceeds after attributable costs and verified deductions. Points, visits and gross revenue are not payable commission.

**Marketing hook:** “A referral model with an explained calculation.”

### 11. Marketplace discovery

**Status:** Limited / provider dependent · **Entry:** [/marketplace](https://roseram.com/marketplace)

Public browsing provides search and bounded records. Business marketplace submissions and related merchant operations include preview/waitlist states and must be checked separately.

**Marketing hook:** “Find what others are creating, then evaluate what is ready to use.”

### 12. Advertising and tailored learning ideas

**Status:** Preview / planned · **Entry:** [/business](https://roseram.com/business)

Advertising placement workflows are in private preview. Optional tailored business learning emails are labelled planned and are not available for enrollment from the suggestions view.

**Marketing hook:** “A future path from building to reaching the right audience.”

## Knowledge and community: make a better next decision

### 1. Practical AI guide library

**Status:** Editorial in source · **Entry:** [/guides](https://roseram.com/guides)

Distinct task guides address website building, agentic coding, debugging, security, data, mobile, performance and marketing, with original examples and primary references.

**Marketing hook:** “An answer is more useful when it comes with a way to act on it.”

### 2. Reusable briefs and checklists

**Status:** Implemented in source · **Entry:** [/guides](https://roseram.com/guides)

Guide controls support copying an adaptable agent brief and tracking a device-local checklist. These are not publicly verified completion records.

**Marketing hook:** “Take the method into your next project.”

### 3. Website cost calculator

**Status:** Implemented in source · **Entry:** [/guides/ai-website-builder-cost](https://roseram.com/guides/ai-website-builder-cost)

An editable hypothetical ownership budget separates launch costs and recurring costs. Estimates are user assumptions rather than a quote or guaranteed saving.

**Marketing hook:** “Budget for the application after the first exciting demo.”

### 4. Product reviews and reader feedback

**Status:** Editorial / account dependent · **Entry:** [/reviews](https://roseram.com/reviews)

Source-linked product assessments and filtered discovery share account-based reader voting/review flows where durable storage is available.

**Marketing hook:** “Compare the claims, the context and the reader experience.”

### 5. AI business and engineering case studies

**Status:** Editorial in source · **Entry:** [/case-studies](https://roseram.com/case-studies)

Research-based analyses distinguish publisher/customer claims, independent findings and original recommendations. They are not all Roseram customer success stories.

**Marketing hook:** “Learn the mechanism behind a headline, including what the numbers leave out.”

### 6. AI public-record investigations

**Status:** Editorial in source · **Entry:** [/reviews/scams](https://roseram.com/reviews/scams)

Case files distinguish allegations, regulatory actions, settlements and outcomes. Provider buyer guides are separately labelled and do not accuse every listed company of fraud.

**Marketing hook:** “Before trusting the pitch, inspect the evidence.”

### 7. Product launches and reviewed profiles

**Status:** Editorial in source · **Entry:** [/product-launches](https://roseram.com/product-launches)

A multi-source discovery directory uses source/product-name routes. Reviewed profiles add publisher references, branding, fit analysis and limitations; raw imports remain research candidates.

**Marketing hook:** “Discovery starts with a name. Evaluation goes further.”

### 8. News and contextual learning

**Status:** Editorial in source · **Entry:** [/news](https://roseram.com/news)

Dated AI stories and contextual links connect public developments to practical learning and evaluation. Currency requires ongoing source review.

**Marketing hook:** “Understand what an AI announcement changes for your own work.”

### 9. AI tools and task discovery

**Status:** Editorial in source · **Entry:** [/ai-tools](https://roseram.com/ai-tools)

Tools and task-oriented content connect research queries to relevant guides and product pages. Candidate keyword counts do not establish search demand.

**Marketing hook:** “Start from what you need to accomplish, then choose the tool.”

### 10. Documentation and getting started

**Status:** Editorial in source · **Entry:** [/docs](https://roseram.com/docs)

A public documentation hub explains workflow, access, usage, troubleshooting and comparisons. Exact product behavior should be verified against current releases.

**Marketing hook:** “A useful starting point for the whole workflow.”

### 11. Forum and founder discussions

**Status:** Account / storage dependent · **Entry:** [/forum](https://roseram.com/forum)

Forum and letters provide community discussion surfaces. Sign-in can preserve a pending discussion action; persistence depends on the configured data services.

**Marketing hook:** “Ask a question where the context can continue.”

### 12. Verified-source video embeds

**Status:** Publisher / browser dependent · **Entry:** [/guides](https://roseram.com/guides)

Approved video sources use a shared click-to-load player with failure handling and direct publisher links. These are learning embeds, not Roseram video-generation output.

**Marketing hook:** “Watch a primary source without losing the written workflow.”

### 13. Public metrics with interval choices

**Status:** Collection dependent · **Entry:** [/status](https://roseram.com/status)

Public aggregates support recent and historical intervals where retained readings exist. Missing data remains unavailable; samples are not audited user counts or guaranteed uptime.

**Marketing hook:** “See a reading with its time window and its limits.”

### 14. Waitlist and opt-in updates

**Status:** Consent / provider dependent · **Entry:** [/mission](https://roseram.com/mission)

The existing opt-in form, mission handoff and configured follow-up sequences capture consent. Eligibility/frequency controls and unsubscribe handling apply; provider delivery was not exercised in this audit.

**Marketing hook:** “Stay connected to product developments on your own terms.”

### 15. Controllable product-introduction audio

**Status:** Browser dependent · **Entry:** [/home](https://roseram.com/home)

The shared announcement popup attempts to play the supplied audio introduction. Playback has pause/replay, session mute and seeking controls, and stops on dismissal. Blocked autoplay presents a play button.

**Marketing hook:** “Listen to the introduction, at your own pace.”

## Account access, plans and supporting products

### 1. Email and configured social sign-in

**Status:** Provider dependent · **Entry:** [/account](https://roseram.com/account)

Account entry, verification and recovery use configured authentication services. Each social provider needs its own working setup.

**Marketing hook:** “One account connects your work and your access.”

### 2. Ethereum and Solana wallet sign-in

**Status:** Provider / browser dependent · **Entry:** [/account](https://roseram.com/account)

Compatible injected wallets authenticate with a signed message. Branded options include MetaMask, Phantom, Coinbase Wallet, Solflare and Brave; no wallet transaction is required for the sign-in flow.

**Marketing hook:** “Prove control with a signature rather than a transaction.”

### 3. Plans, included usage and credits

**Status:** Payment / access dependent · **Entry:** [/billing](https://roseram.com/billing)

The local pricing configuration has Plus Starter, Pro Starter, Plus Super and Pro Super tiers. Usage is metered; displayed prices and trial eligibility must be verified at the current checkout.

**Marketing hook:** “Choose an allowance that fits how you use the workspace.”

### 4. Personal workspace preferences

**Status:** Implemented in source · **Entry:** [/account](https://roseram.com/account)

Style, light/dark appearance, transitions, dual preview, explorer/community/live-chat visibility, popup preferences and the promotional-bar toggle personalize the interface.

**Marketing hook:** “Keep the workspace as focused as your work needs.”

### 5. Language and public navigation

**Status:** Browser dependent · **Entry:** [/home](https://roseram.com/home)

Shared navigation and language controls support discovery across the public application. Translation availability and quality depend on its provider and the browser.

**Marketing hook:** “Find your next step across the product without losing your place.”

### 6. Support and issue reporting

**Status:** Delivery dependent · **Entry:** [/support](https://roseram.com/support)

Support surfaces collect requests and connect users with the existing assistance path. A rendered form does not prove successful message delivery.

**Marketing hook:** “Give the team the context needed to investigate the problem.”

### 7. AI receptionist phone option

**Status:** Phone / provider dependent · **Entry:** [/support](https://roseram.com/support)

Live chat and support provide the confirmed +1 (415) 853-0998 call link. It opens the visitor’s calling app; browser voice calling and call-to-chat synchronization are not implemented by this link.

**Marketing hook:** “Choose a phone conversation when that is the easier way to ask.”

### 8. Training and learning products

**Status:** Access limited · **Entry:** [/training](https://roseram.com/training)

Training is presented as full with a consented waitlist. Learning-product and course surfaces exist; current enrollment, membership inclusion and fulfillment must be checked before promotion.

**Marketing hook:** “Build practical AI skills as access and programs become available.”

### 9. Shop and preorder catalog

**Status:** Purchasing availability unverified · **Entry:** [/shop](https://roseram.com/shop)

Physical-product and preorder catalogs exist. Availability, merchant-confirmed terms, fulfillment and checkout status must be verified; AI names do not establish medical or cognitive benefits.

**Marketing hook:** “A supporting storefront with product-specific terms.”

## Campaign angles to elaborate

These are creative seeds. Use real demonstrations and current access terms before publishing advertisements.

| Angle | Seed headline | Content or demonstration | Appropriate next step |
| --- | --- | --- | --- |
| Project awareness | Your assistant should know what you are building. | Show the badge, source origin and detected web/mobile signals, then explain what the agent receives. | Getting-started guide |
| Existing source | You do not need a blank canvas to make progress. | Import a small owned repository and show one verified change. | Import guide / Workspace |
| Working-copy ownership | Try the change. Keep the choice. | Show automatic validated Build edits, preview and Revert; explain explicit disk/Git writes. | Workspace |
| Three kinds of work | Ask it. Plan it. Build it. | Demonstrate one goal in Chat, Plan and Build and the different outputs. | Workspace |
| Actionable diagnostics | Turn a finding into the next step. | Show the readable Yes/No overlay and internal action lifecycle. | Workspace |
| Runtime clarity | A preview should tell you what it needs. | Show source loading, runtime stages, an actionable configuration failure and recovery. | Preview troubleshooting guide |
| Source delivery | From a useful brief to a repository you own. | Record a reviewed, authorized GitHub publication on a test project; mention text/source limits. | Publication guide |
| Brand finishing | Give your first version a recognizable tab. | Show icon variants, manual selection and verified metadata integration. | Workspace Improve |
| Secret handling | Configure the runtime without making a secret part of the conversation. | Demonstrate with a harmless placeholder and explain session scope and redaction. | Workspace settings |
| Learning that travels | Take a practical method into your next build. | Show a guide’s brief, acceptance checks and original example. | Guide library |
| Evidence over hype | A launch is a claim. A researched profile gives it context. | Walk through publisher identity, source references and untested limitations. | Product launches |
| Careful AI evaluation | Before believing the pitch, follow the record. | Explain one public-record case with its exact legal/outcome status. | AI case files |
| Affiliate momentum | The first useful introduction matters too. | Explain click/lead/sale/revenue activity points, aliases and separate payable earnings. | Business referrals |
| Relationship continuity | A referred account can outlast a cookie. | Explain first-account lifetime association and eligible purchase routing without exposing identities. | Referral documentation |
| Interface choice | Make room for the way you work. | Show style, preview columns, explorer, transitions and promotional-bar preferences. | Account preferences |
| Transparent progress | See the product take shape. | Explore the evidence-based milestones, source counts and readiness gates. | Roadmap |

### Six story outlines

1. **“I brought my own repository.”** Begin with a real small project, explain source loading, make one focused edit, inspect preview and decide separately whether to publish. Show an actual rollback. Do not imply the original repository was changed merely by importing it.
2. **“The indicator understood the project.”** Compare a detected web dependency, a mobile dependency and a generic-language folder. Open the indicator. Explain that project classification guides work but does not certify a native build or activate a media provider.
3. **“I fixed a finding without writing another prompt.”** Use a genuine source-backed finding, show the summary and Yes/No decision, then the real progress and resulting diff. Generation is metered and can require clarification.
4. **“My first launch had a complete customer journey.”** Start from a service business brief; test its form and routes, choose a destination and inspect the deployed result. Avoid claiming the hosting step works until the demonstration actually completes.
5. **“Learning became an implementation brief.”** Answer a real user question with a guide, copy the adaptable brief and apply its acceptance criteria to a test project. A worked fictional example is not a customer testimonial.
6. **“My referrals became a visible story.”** Use authorized aggregate results; distinguish activity points, accepted leads, attributed paid sales and settled commission. Never expose full identities or create fake leaderboard entries for a screenshot.

### Messaging boundaries

- Prefer **AI-assisted workspace**, **agentic coding**, **project-aware assistance**, **reversible changes** and **source-backed learning** when supported by the demonstration.
- Do not claim a proprietary AGI/superintelligence foundation model, universal autonomous engineering, every model benchmarked per request, unlimited usage, fixed token savings or guaranteed superiority.
- Image generation has a configured-provider execution route. Video and voice classification/planning do not establish rendered video or generated speech services.
- GitHub has implemented repository workflows. GitLab, Bitbucket and Azure DevOps account connections do not establish import/push support.
- Session environment memory is not durable encrypted secret storage. A local import is not an unlimited complete disk clone.
- A responsive browser preview is not a native mobile/desktop build certification. Internal client packages are not production store releases or an active VPN service.
- Referral activity points are not cash. The 50% policy concerns eligible positive settled net proceeds after deductions, not half of every gross payment. Payout eligibility and delivery require separate checks.
- Keyword relevance, formatting, schema, long articles and a sitemap do not promise 100/100 SEO, specific search volume, zero competition or a first-place ranking.
- Training, advertising, marketplace submission and physical-shop availability must be checked separately. Do not promise a seat, ad delivery, fulfillment or a medical/cognitive benefit from a product name.

## Development record and direction

The earliest retained Git snapshot is dated 12 December 2025. A renewed development conversation is recorded on 5 September 2026. Neither date is asserted as the company’s founding date. Milestone dates describe recorded work, not proof of a production release.

| Recorded date | Milestone | Product area | Record state |
| --- | --- | --- | --- |
| 2025-12-12 | The first recorded foundation | workspace | Historical development record |
| 2026-09-05 | A renewed product direction | experience | Historical development record |
| 2026-09-14 | From a working project to a published site | delivery | Historical development record |
| 2026-09-15 | A searchable review and discovery layer | knowledge | Historical development record |
| 2026-09-18 | More consistent presentation and discovery | experience | Historical development record |
| 2026-09-21 | Community and commercial workflows expand | growth | Historical development record |
| 2026-10-02 | A clearer way to begin a project | workspace | Historical development record |
| 2026-10-07 | Client applications enter development | delivery | Historical development record |
| 2026-10-10 | The agent works from the active project | workspace | Historical development record |
| 2026-10-11 | A small indicator with useful context | workspace | Historical development record |
| 2026-10-11 | Findings become guided actions | workspace | Historical development record |
| 2026-10-11 | Practical learning becomes a product layer | knowledge | Historical development record |
| 2026-10-12 | Referral activity becomes more transparent | growth | Latest implementation; deployment separate |
| 2026-10-12 | Reliability and resource use get sharper controls | experience | Latest implementation; deployment separate |
| 2026-10-12 | Launch listings become researched product profiles | knowledge | Latest implementation; deployment separate |
| 2026-10-12 | The case-study library grows to 100 authored stories | knowledge | Latest implementation; deployment separate |
| 2026-10-12 | Product listening and phone support gain clear controls | experience | Latest implementation; deployment separate |

The public [roadmap](https://roseram.com/roadmap) offers area filters, a cumulative documented-milestone curve, expandable boundaries and future-priority filters. Its curve counts the entries above; it is not engineering velocity or product-completion percentage.

### Forward direction

Priorities are inferred from recorded requests and implementation gaps, with no promised schedule.

- **Now: Reliable previews for imported projects.** Broaden framework and monorepo handling while preserving source, understandable progress and recoverable failures. Readiness: Representative repository and folder imports must complete edit → preview → recovery checks.
- **Now: Prove the complete customer journey.** Validate mobile controls, sign-in, builds, publication and recovery against the deployed application. Readiness: Authenticated device checks and observed production behavior, with regressions added for confirmed faults.
- **Now: Expand the researched library.** Prioritize distinct useful topics and reviewed launch profiles with attributable sources and better intent coverage. Readiness: Identity, originality, evidence, layout and overlap review before additional pages become indexable.
- **Next: Durable project environment management.** Extend session-scoped environment values into an encrypted, account-controlled project service. Readiness: Access controls, deletion, secret redaction and secure runtime delivery must be independently exercised.
- **Next: More repository delivery destinations.** Evaluate full import and publication workflows beyond the existing GitHub implementation. Readiness: A connected provider account must support reviewed reads and writes before it is marketed as repository support.
- **Next: Activate additional business services carefully.** Advance marketplace submissions, advertising and tailored learning workflows beyond their current preview or planned states. Readiness: Working customer journeys, permissions, delivery terms and operational ownership must precede general availability.
- **Next: Production client releases.** Progress from internal desktop and extension builds and mobile source to signed, tested distribution. Readiness: Platform signing, native authentication, update behavior and device acceptance checks.
- **Later: Richer media creation.** Evaluate real video and voice execution alongside the existing provider-dependent image route. Readiness: Configured providers, clear usage accounting, authorized assets and working generation/export journeys.

## Learn more

[Workspace](https://roseram.com/workspace) · [Documentation](https://roseram.com/docs) · [Guides](https://roseram.com/guides) · [Business](https://roseram.com/business) · [Roadmap](https://roseram.com/roadmap) · [Support](https://roseram.com/support)