User Archetypes

These archetypes describe global early users who may benefit from Prox OS. They are product discovery inputs for Growth Admin, App Store bundles, workspace templates, and future Prox Cloud experiments.

Market Entry Rule

Early Prox OS should not target broad mainstream consumers first, and it should not start by selling heavy enterprise pilots before the runtime, permissions, privacy posture, and app ecosystem are clearer.

The first users should already understand at least part of:

agent + data + app runtime + privacy + GitHub/source workflow

Templates, marketplace loops, native clients, and AI onboarding can later lower the learning curve.

Early Adopters

Persona	Why they fit	What they need	Prox OS promise
Indie hackers / AI builders	They understand agents, workflows, micro-apps, and distribution.	A visible workspace for many tools and agents.	Build, summon, and wire AI-native apps faster.
Developers / GitHub users	They can test manifests, templates, SDKs, and runtime boundaries.	A developer-friendly app/agent runtime.	Bring GitHub-native apps into a personal OS surface.
Personal knowledge management / data sovereignty users	They already care about Notion, Obsidian, Airtable, Baserow, export, and local-first posture.	Ownership, export, delete, structured data, and local-first direction.	Own the data, not only the interface.
Solo founders / technical creators	They need to manage many tasks with few people.	Agent ops, dashboards, business docs, launch workflows, and evidence.	Run a small AI-native company from one workspace.

Mid-stage Users

Persona	Why they become relevant	Needed maturity
Agencies and studios	They operate many client projects and templates.	Shared Spaces, permissions, reviews, and export.
App builders and plugin developers	They can extend the platform once manifest and review rules stabilize.	Developer Console, SDK/CLI direction, app review, and distribution.
Community builders	They can publish public or semi-public resource Spaces.	Public profile, UGC gates, abuse reporting, and trust posture.
Data-heavy creators	They need structured personal datasets and reusable views.	Data vault, connector scopes, import/export, and privacy controls.
Open-source maintainers	They can turn repos, docs, issues, releases, and community context into Spaces.	GitHub-first source flow, public docs, badges, and contributor workflows.
Privacy-focused prosumers	They care about control but may need simpler onboarding.	Export/delete flows, clear privacy copy, and local runtime direction.
Small technical teams	They can test shared operating workspaces.	Team Spaces, scoped access, audit basics, and support boundaries.

Later Users

Persona	Why later	Needed maturity
Education and research teams	They need stable templates, sharing, data boundaries, and support.	Cohort/workspace templates and institutional posture.
Enterprise pilots	They require security, compliance, procurement, and support.	Auth, audit, DPA, subprocessor list, retention, and SSO direction.
Local-first AI users	They need private inference and local data.	Local companion, local vault, provider adapters, and permission prompts.
Marketplace sellers	They need real commercial infrastructure.	App review, creator identity, tax, payouts, refunds, and fraud review.
Privacy/legal/compliance-heavy organizations	They can validate data-sovereign positioning only after real controls exist.	Compliance automation, policy workflows, and enterprise support.
Regulated teams	They need clear boundaries before production use.	Region, retention, access, audit, and security controls.
SaaS vendors building Prox OS apps	They need distribution and durable customer workflows.	Marketplace, install flow, app contracts, and developer support.

AI-native Developer

Core job-to-be-done: turn repos, docs, APIs, and local tools into one inspectable Studio workspace.
Pain points: scattered dashboards, brittle context switching, local tool setup, weak AI context handoff.
Why Prox OS helps: app bundles, admin iframes, command/search, AI context, activity, and package-aware developer surfaces.
Suggested app bundle: Developer Bundle with Docs, UI Workshop, API Explorer, Nx Graph, Search, AI UI, Activity, and Command.
Early monetization signal: pays for hosted developer workspace, team package visibility, or AI context automation.

Solo Founder

Core job-to-be-done: keep product, pricing, roadmap, launch, and investor context in one operating cockpit.
Pain points: fragmented strategy docs, no single launch workspace, weak prioritization loops.
Why Prox OS helps: Founder Suite resources, Growth Admin, workspace dashboard, AI planning, files, and activity summaries.
Suggested app bundle: Founder Bundle with Growth, Founder Suite, Files, Search, Workspace, AI UI, Notifications, and Activity.
Early monetization signal: pays for founder workspace templates, hosted private OS, or launch bundle support.

Indie Creator

Core job-to-be-done: publish a personal creative operating space with assets, apps, notes, and community links.
Pain points: portfolio tools are static, file organization is separate from publishing, and context is hard to reuse.
Why Prox OS helps: creator space model, app bundles, media resources, files, and public/private workspace boundaries.
Suggested app bundle: Creator Bundle with Media, Files, App Store, Workspace, Moments, Search, and Activity.
Early monetization signal: pays for creator profile, app bundle publishing, or media workspace hosting.

Open Source Maintainer

Core job-to-be-done: coordinate repos, docs, issues, releases, examples, and contributor context.
Pain points: project context lives across GitHub, docs, chat, CI, and dashboards.
Why Prox OS helps: developer tools, package graph, activity timeline, contributor-friendly app bundles, and search.
Suggested app bundle: Maintainer Bundle with GitHub Radar, Docs, Activity, Search, Notifications, Workspace, and Security UI.
Early monetization signal: pays for public project workspace, contributor onboarding, or hosted docs/app bundle.

Researcher / Lab Builder

Core job-to-be-done: organize papers, datasets, notebooks, lab artifacts, and reproducible research spaces.
Pain points: datasets and context are separated from notes, code, and review.
Why Prox OS helps: files, data contracts, search, AI summaries, workspace resources, and activity history.
Suggested app bundle: Research Bundle with Files, Search, Data Table, Data Viz, AI UI, Workspace, and Activity.
Early monetization signal: pays for private dataset workspace or hosted lab bundle.

Remote Team Operator

Core job-to-be-done: keep team dashboards, docs, decisions, and operational activity visible.
Pain points: work is split across SaaS tabs, knowledge bases, chat, and ad hoc spreadsheets.
Why Prox OS helps: workspace dashboard, members, resources, notifications, search, security summaries, and activity feeds.
Suggested app bundle: Team Workspace Bundle with Workspace, Search, Notifications, Activity, Security UI, Files, and Collaboration.
Early monetization signal: pays for team workspace seats or hosted internal operating cockpit.

Digital Nomad

Core job-to-be-done: keep personal work, travel documents, projects, and private memories portable.
Pain points: personal data is scattered across cloud drives, notes, photos, and browser tabs.
Why Prox OS helps: personal OS home, files, moments, search, workspace bundles, and private activity history.
Suggested app bundle: Personal Archive Bundle with Moments, Files, Search, Workspace, Activity, and Notifications.
Early monetization signal: pays for private hosted personal OS or archive workspace.

Educator / Cohort Builder

Core job-to-be-done: run cohorts with resources, projects, examples, and student-facing workspaces.
Pain points: learning materials, assignments, community, and project examples live in separate tools.
Why Prox OS helps: workspace templates, resource grids, files, search, activity, and future creator/community spaces.
Suggested app bundle: Cohort Bundle with Workspace, Files, Search, Activity, App Store, and Collaboration.
Early monetization signal: pays for cohort templates or hosted class workspaces.

Personal Data Archivist

Core job-to-be-done: preserve personal documents, bookmarks, media, and searchable context.
Pain points: cloud drives are storage-first, not context-first.
Why Prox OS helps: files, search, activity, workspace resources, metadata, and private OS home.
Suggested app bundle: Archive Bundle with Files, Search, Activity, Notifications, and Workspace.
Early monetization signal: pays for private storage, richer search, or archive import tools.

Family Memory Keeper

Core job-to-be-done: organize memories, media, stories, and private family spaces.
Pain points: photos, messages, documents, and stories are scattered.
Why Prox OS helps: moments, media, files, private workspaces, search, and gentle activity summaries.
Suggested app bundle: Memory Bundle with Moments, Media, Files, Search, Workspace, and Activity.
Early monetization signal: pays for private family workspace or memory preservation bundle.

Community Curator

Core job-to-be-done: collect resources, apps, links, datasets, and community context into a public or semi-public space.
Pain points: curation is split across lists, docs, social posts, and newsletters.
Why Prox OS helps: creator/community workspace model, app bundles, resource cards, public profiles, and activity.
Suggested app bundle: Community Bundle with Workspace, App Store, Search, Files, Activity, and Security UI.
Early monetization signal: pays for community space hosting or curated bundle publishing.

Data Journalist / Public-interest Dataset Builder

Core job-to-be-done: collect, explain, visualize, and publish datasets with context.
Pain points: data, narrative, provenance, and visuals often live separately.
Why Prox OS helps: data contracts, tables, visualization, files, search, activity, and shareable workspaces.
Suggested app bundle: Dataset Bundle with Data Table, Data Viz, Files, Search, AI UI, and Activity.
Early monetization signal: pays for dataset workspace hosting or publication tooling.

Workflow Automation Builder

Core job-to-be-done: compose tools, actions, scripts, triggers, and AI assistance into reliable workflows.
Pain points: automations are hard to inspect, share, and reason about.
Why Prox OS helps: actions, command, AI UI, activity, workspace context, and future connector surfaces.
Suggested app bundle: Automation Bundle with Command, Actions, AI UI, Activity, Notifications, Workspace, and Security UI.
Early monetization signal: pays for workflow templates, connector bundles, or hosted automation cockpit.

Designer / Interactive Portfolio Creator

Core job-to-be-done: publish a living portfolio with apps, case studies, assets, and interactive previews.
Pain points: portfolios are often static and separate from working assets.
Why Prox OS helps: creator space, media, files, app bundles, visual Storybook-style previews, and public/private resource boundaries.
Suggested app bundle: Portfolio Bundle with Media, Files, App Store, Workspace, Search, and Activity.
Early monetization signal: pays for custom portfolio OS, creator profile, or interactive app bundle publishing.

User Archetypes

On this page