Skip to main content
The localized /pitch page is a 32-slide presentation about Tuturuuu’s ecosystem, workforce decision support, and long-term intelligent-partner vision. It is excluded from search indexing. Existing product foundations, proposed pilot work, and long-term research are explicitly distinguished; product availability varies.

Present

Use arrows or previous/next controls to navigate. Home and End jump to the first and final slides. Space toggles twelve-second autoplay. Playback pauses when the browser tab is hidden, notes open, or the presenter navigates manually. The overview lists every slide. Fullscreen shows a translated error when unavailable. Motion and optional closing-slide confetti respect reduced-motion preferences. Stable hashes such as /pitch#workforce, /pitch#simulation, and /vi/pitch#pricing support sharing. Existing slide hashes remain valid after reordering. Print renders every slide with landscape page breaks. Presenter notes are included in the public payload: they are not a private channel. Never include confidential opportunities, private partner briefs, or unpublished commitments. The capacity sandbox is a deterministic, synthetic illustration. It multiplies team size by available hours and compares that result with estimated weekly work. It does not run an AI model, persist inputs, collect telemetry, or recommend staff allocation. Its limitations and baseline are visible. Interaction tracking in the pilot narrative describes proposed development, not tracking performed by this page.

Evolve

Edit the pitch namespace in apps/web/messages/en.json and vi.json, then run bun i18n:sort and format the owned locale files. Keep locale shapes aligned with PitchCopy. Each slide has a chapter, headline, narrative, public presenter note, maturity label, and visual panels. Stable identifiers live in pitch-model.ts. The presentation uses official branding tokens through pitch-brand.ts; specialized art and the synthetic simulation live in the adjacent components and CSS modules. The pricing slide and subscription calculator use the same public catalog API as the pricing page. They refresh every five minutes and show an unavailable state instead of a fabricated fallback. Distinguish current prices from proposed allowances, annual charges from monthly equivalents, and subscriptions from custom prototype scope. The engagement slide presents a budget structure, not a quote. Do not republish legacy traction, fundraising amounts, partner endorsements, certifications, savings, or delivery dates without current supporting evidence. Pilot timelines are indicative, require scoping, and are not delivery commitments. Workforce decision support must retain transparent assumptions and human review; it is not a promise of autonomous employment decisions.

Verify

Run focused pitch tests, bun check, and the real web build through ttr resources run. Inspect both locales at desktop and mobile sizes, keyboard navigation, deep links, overview, notes, simulation, reduced motion, and print. Keep /pitch public in apps/web/src/constants/public_paths.ts. Route ownership changes also require updating the TanStack migration manifest.

Product scenes and company portfolio

The /portfolio route is the public company capability profile. It includes interactive product illustrations, the shared application registry, engineering capabilities, and open research collaboration directions. Both English and Vietnamese content live in the portfolio and capabilities message namespaces. Keep the app directory derived from LAUNCHABLE_APPS; every registered slug requires a translated description. The directory test catches missing descriptions. A registry entry does not imply every integration is complete or publicly accessible. Pitch slides use labeled product flows, decision diagrams, and journey diagrams in product-diagrams.tsx, decision-diagrams.tsx, and journey-diagrams.tsx. The remaining editorial illustrations live in the geometry modules. The Tasks and Meet scenes are shared with the portfolio. They are local, synthetic illustrations: they do not call AI, create tasks, join meetings, or process real participant data. Research and grant-funded collaboration can be described in general terms on the portfolio. Keep confidential opportunities and unpublished partner details out of both public pages and presenter notes. Do not claim awarded funding, validated outcomes, or institutional endorsements without published evidence. The portfolio and deck also cover smart Chat, Mail, Calendar, realtime whiteboards, collaborative documents, multi-agent simulation research, and Tuturuuu product ownership. Keep Mira mail action extraction labeled as a development direction until the underlying product supports that full workflow. The 32-slide story is organized into six chapters: why now, product foundations, connected intelligence, trust and validation, sustainable delivery, and user ownership. External statistics link to primary sources from Stanford HAI, Microsoft, WEF, and OECD, with dates and sample limitations on the reference slide. Update source details when changing a statistic. Full independence remains a roadmap; do not imply external infrastructure or model dependencies are gone. The ecosystem strategy slide explains the investment in shared architecture, ongoing engineering, and operations as AI-assisted app creation becomes more accessible. This is presented as a strategic thesis, with expansion tied to customer value and reuse rather than breadth alone.

Diagram and product-mark maintenance

Keep diagram labels, icons, and connectors in the same SVG coordinate system. Use explicit unfilled paths for line art, route connectors to node boundaries, and draw opaque node surfaces over connection paths. Scope responsive SVG rules to the outer data-pitch-diagram element, never embedded product icons. product-mark.tsx uses approved local brand assets for Tuturuuu, Mira, Tasks (TuDo), Nova, and Rewise, with application icons for other products. It is shared by the deck, product illustrations, and portfolio directory. Short diagram labels live in both locales under pitch.visuals; do not position separate HTML labels over a scaled SVG. Workload and skills figures are explicitly synthetic, and evaluation cells stay empty until a real pilot provides measured results.

Editorial imagery and responsive storytelling

The portfolio uses two optimized AI-generated concept illustrations under apps/web/public/media/story: a Vietnam-to-starward panorama and an imagined research observatory. Captions explicitly identify concept art; neither represents an existing facility or geographic footprint. Keep text in HTML, retain image alt text in both locales, and preserve mobile cropping. Generation prompts are recorded beside the assets. The pitch consolidates overlapping topics into 32 slides. Historical fragments redirect through CONSOLIDATED_SLIDES in pitch-model.ts so shared links survive editorial changes. The portfolio catalog chart derives its counts from the same app list as the directory; it never represents adoption or revenue. Its selectable workflow is a conceptual walkthrough, not a live AI action.

Motion and the innovation story

The portfolio’s innovation explorer uses shared @tuturuuu/ui tabs and buttons, with icons from @tuturuuu/icons. Its three chapters connect useful products, maintained foundations, and long-term intelligence research. The Google comparison is explicitly an ambition, not a claim of equivalent scale or market position. StoryMotion provides a reader-controlled motion switch. Use a single short opacity transition per scene; do not animate full sections, stack parent and child entrances, or run decorative loops. Chapter panels share a grid cell to reserve the tallest panel, with inactive content inert and hidden from assistive technology. Use SVG icons from @tuturuuu/icons for every button icon, never emoji or text glyphs. Reduced-motion preferences disable scene animation; print removes motion and keeps all pitch slides visible. Essential content is rendered without waiting for an animation or observer. Check keyboard tab navigation, the pause control, EN/VI mobile layouts, and print whenever these compositions change.