115 lines
3.5 KiB
Markdown
115 lines
3.5 KiB
Markdown
# Product Vision
|
|
|
|
## Status
|
|
|
|
Active
|
|
|
|
## Product
|
|
|
|
`Socialize` is a workflow application for social media content review, revision, approval, and publication readiness.
|
|
|
|
It is not a public social network. It is an organization-owned, workspace-based coordination tool for internal teams, providers, and client approvers.
|
|
|
|
## Problem
|
|
|
|
Social media approval work is still fragmented across Google Drive, email, chat, phone calls, and spreadsheets.
|
|
|
|
That fragmentation creates:
|
|
|
|
- unclear latest-version ownership
|
|
- scattered comments and decisions
|
|
- manual follow-up work
|
|
- weak auditability
|
|
- avoidable delays before publication
|
|
|
|
## Product Goal
|
|
|
|
Provide one system of workflow for drafting, revising, reviewing, approving, and handing off content for publishing.
|
|
|
|
## Primary Users
|
|
|
|
- Social media manager
|
|
- Account manager / customer success
|
|
- Client approver
|
|
- External provider / production partner
|
|
- Internal producer
|
|
- Internal employee / content contributor
|
|
- Administrator
|
|
|
|
## Core Product Shape
|
|
|
|
- organizations as the SaaS account, billing, subscription, and connector boundary
|
|
- workspaces as brand/client workflow boundaries owned by one organization
|
|
- agencies, in-house teams, and professional businesses able to manage multiple workspaces
|
|
- organization members able to inherit access across owned workspaces
|
|
- external collaborators able to access specific workspaces without organization membership
|
|
- content items as the main reviewable unit
|
|
- assets and revisions tracked against content items
|
|
- comments and approvals attached to the work itself
|
|
- notifications driven by workflow events
|
|
|
|
## What The Product Must Do Well
|
|
|
|
- centralize review state
|
|
- preserve a clear audit trail
|
|
- make “latest approved version” obvious
|
|
- support internal review before client review
|
|
- support client-facing review with low friction
|
|
- keep publication handoff clear once approval is complete
|
|
|
|
## What The Product Is Not
|
|
|
|
- not a social feed or public community platform
|
|
- not a full publishing engine in version 1
|
|
- not a full DAM platform in version 1
|
|
- not a full analytics product in version 1
|
|
- not a full billing provider or pricing/package automation product in version 1
|
|
|
|
## MVP Scope
|
|
|
|
Version 1 should focus on approval workflow rather than direct publishing.
|
|
|
|
### In Scope
|
|
|
|
- authentication and user roles
|
|
- workspace structure and access control
|
|
- content item creation and editing
|
|
- Google Drive asset linkage and asset metadata
|
|
- revision history for assets and copy
|
|
- centralized comments
|
|
- approval decisions
|
|
- activity timeline / audit trail
|
|
- review queues and dashboards
|
|
- notifications and reminders
|
|
- simple external review experience
|
|
|
|
### Out Of Scope
|
|
|
|
- full scheduling engine
|
|
- direct social publishing
|
|
- advanced third-party synchronization
|
|
- analytics suite
|
|
- full customer billing provider integration and pricing/package automation
|
|
|
|
## Current Strategic Assumptions
|
|
|
|
- Google Drive remains an important source of truth for many client-owned files.
|
|
- Internal review and client review are variants of the same workflow, not separate products.
|
|
- External reviewers should experience low-friction review access.
|
|
|
|
## Near-Term Priorities
|
|
|
|
- make the content approval workflow complete end-to-end
|
|
- harden workspace scoping and role-based access
|
|
- strengthen revision and comment traceability
|
|
- clarify external review and approval flows
|
|
|
|
## Phase 2 Opportunities
|
|
|
|
- deeper Google Drive integration
|
|
- publishing handoff integrations
|
|
- calendar planning views
|
|
- richer approval templates
|
|
- SLA reminders and escalations
|
|
- workflow analytics
|