Soruno Go

The description states that Soruno Go:

• Turns a real business photo into a brand-aware, action-ready poster.
• Uses a camera-first workflow where users capture or choose the real product/service photo.
• Asks for the channel and desired business outcome instead of an open-ended prompt.
• Builds a short Brand Capsule from a website or compact manual setup.
• Produces one art-directed poster with structured facts, message, price, dates, location, and call to action reviewable before generation.
• Saves projects as resumable with source, creative spec, facts, exports, provenance, and quality checks.

It is not a template grid but uses the photo to control composition and business purpose to control hierarchy. The result includes structured confirmation of wording and provenance, and model responses cannot silently replace them.

Inference The product appears to be a mobile-native creative workflow tool that integrates AI image generation with structured fact handling and project lifecycle management.

The author states:

• Soruno Go is a "camera-first pocket art director."
• It aims to improve small-business content creation by avoiding generic copy or design tools.
• It avoids inventing facts, flattening text into pixels, or changing the product.
• It keeps real product and owner-confirmed facts as the source of truth.

Inference The positioning evolved from a general web content platform (Soruno Lite) to a focused mobile tool for small businesses using AI to generate branded posters while maintaining factual integrity.

The description states:

• The target is small business owners.
• Content usually starts with a real, imperfect phone photo.
• It addresses the problem of rushed posters or generic copy.
• The tool is designed for owners who do not have time to learn complex design tools.

Inference The ICP appears to be small business owners who need quick, branded content creation without deep design skills or time investment. The focus is on real-world, imperfect photos and channel-specific outcomes.

Not evidenced.

The description states:

• Built with SwiftUI (iOS) and Jetpack Compose (Android).
• Backend uses Next.js/TypeScript, Neon Postgres, Drizzle, Inngest, Vercel Blob.
• Uses GPT-5.6 Luna for CreativeSpecV1 and GPT Image 2 for image editing.
• Codex with GPT-5.6 was used across the full build.
• Implements versioned cross-platform contracts, tenant-scoped generation, cancellation/retry/recovery, and idempotent jobs.
• Includes a primary Codex Session ID (019f799a-f0f2-7333-b2bd-0e38efeac535).
• The build includes 291 backend unit tests, 28 contract tests, 29 launch-guard tests, and 52 disposable-database integration tests.

Inference The technical stack suggests a modern, cross-platform mobile-first architecture with AI integration. The use of Codex and structured workflows indicates an emphasis on reproducibility and quality control.

The description states:

• This was a vertical slice built during the OpenAI 2026 hackathon.
• It passed 291 backend unit tests, 28 contract tests, 29 launch-guard tests, 52 disposable-database integration tests, TypeScript checks, Next.js build, and iOS build verification.
• A spend-bounded live GPT Image 2 canary returned a 1024×1024 JPEG.
• It is described as a tested release candidate.
• Production migration and physical-device acceptance remain release gates.

Inference The product is at an early prototype stage, with no evidence of real-world usage or customer adoption. The build is a functional prototype but not yet production-ready.

Not evidenced.

• The product is described as a hackathon prototype with no verified traction.
• No revenue, customers, or market data are provided.
• The team size is listed as one (Glo Thebeatz).
• The description does not mention any partnerships, distribution, or monetization strategy.
• The tool is described as "not a template grid" but the exact nature of its differentiation from existing tools is unclear.

Inference The lack of traction, revenue, and customer data makes it difficult to assess commercial viability. The single-person team may limit execution capacity.

1. What is the current stage of development beyond the hackathon prototype?
2. Are there any real-world users or pilot customers?
3. How does Soruno Go plan to monetize its service?
4. What are the key assumptions about user behavior and adoption?
5. Is there a plan for scaling beyond the current mobile-native approach?
6. What is the long-term vision for the platform beyond the current vertical slice?