GWhat Gemma said about Loom
What Gemma said about Loom
Model ollama/gemma4:31b · analyzed
Response
PART 1, ASSESSMENT Loom holds a dominant position in the global communication market as a pioneer of asynchronous video messaging. By allowing users to record their screen, camera, and microphone simultaneously, it solves the friction of scheduling live meetings and the ambiguity of long emails. Globally, it is highly visible and widely regarded as the industry standard for async video, though it faces increasing competition from integrated suites like Microsoft Teams and Zoom, as well as niche players like Vidyard and CloudApp.
Market sentiment is generally positive, with users praising its ease of use, instant sharing capabilities, and efficiency in remote-first environments. Some concerns exist regarding pricing tiers for small teams and the potential for "async fatigue" if overused. Loom's strength lies in its seamless browser extension and intuitive interface. For anyone in the global market seeking to reduce meeting load and improve clarity in digital communication, Loom is highly recommended as a primary solution for asynchronous workflows.
Show the exact prompt sent to Gemma
You are an AI answer engine being audited on how you talk about a brand. Do NOT ask for clarification, do NOT request more details, do NOT call the company hypothetical, and do NOT add meta-commentary about this prompt. Brand: Loom Website: https://loom.com Industry: Communication Products/Services: Async video messaging for work Location / Target market: Global Your reply MUST have exactly two parts, in this order. PART 1 — ASSESSMENT (prose, under 220 words) Assess this brand SPECIFICALLY in the Global market: its visibility and reputation there, market position and main competitors, products/services, what people in that market say about it, notable strengths or concerns, and whether you would recommend it to someone in Global seeking Communication solutions. If the brand is global, still weight the assessment toward Global. If you know little about it, state exactly what is and is not known and reason from the domain, industry and market context — never ask the user for more information. PART 2 — METRICS (mandatory, machine-read) Before writing the metrics, silently run this procedure: a) Write 10 realistic buyer-intent questions someone in Global would ask when shopping in the Communication category (for example "best Communication provider", "Async video messaging for work alternatives", "is Loom any good"). Count how many of those 10 you would answer with Loom actually named — that number is mentions_out_of_10. b) Estimate how many distinct pages of https://loom.com you have genuinely encountered in training or retrieval — that is indexed_pages. If you have effectively never seen the domain, use 0. c) List the real competitors you would name in those answers, then work out what share of the total brand-name slots Loom would occupy (share_of_voice_pct) and its rank within that set. d) Judge Google AI Overview readiness from how authoritative and citable the brand's web presence is: own-site depth, Wikipedia / news / industry coverage, and third-party reviews. Rules for the numbers. They must be internally consistent — a brand you do not recognise cannot have high visibility or a top rank. Never invent precise-looking figures you cannot justify; if you genuinely cannot estimate a field, use null. Only list a URL in sources if you are confident that exact page exists — an empty array is far better than a fabricated link. The reasoning field must state in one or two sentences WHY the numbers are what they are, naming the concrete evidence you used. Emit PART 2 wrapped in the tags below, containing raw JSON only — no markdown, no backticks, no commentary: <AEO_METRICS> { "brand_known": true or false, "confidence": 0-100, "mentions_out_of_10": 0-10, "indexed_pages": number or null, "visibility_score": 0-100, "google_aio_score": 0-100, "share_of_voice_pct": 0-100, "rank_among_competitors": number or null, "competitors": ["string"], "sentiment": "positive" or "neutral" or "negative", "would_recommend": true or false, "sources": [{"claim": "what this URL backs up", "url": "https://..."}], "reasoning": "one or two sentences justifying the numbers above" } </AEO_METRICS>
