Small service businesses
Founder-led agencies, consultancies, studios, and boutique service teams that coordinate client work across too many disconnected tools.
Poketo v3 alignment
Build your productivity team.
Poketo Core is the modular suite foundation. Users select mascot-backed modules, start with Work, and gain shared context as their suite grows.
Strategic Frame
Modular suite foundation
Poketo Core owns organization context, module activation, mascot identity, shared activity, and the agent/sidebar model.
Adopt one module first
Users can start with Work instead of migrating into a full suite on day one. The suite expands only when adjacent pain appears.
ICP Ranking
| Segment | Score | Role | Reason |
|---|---|---|---|
| Small service businesses | 25 | Primary ICP | Direct client-work pain, reachable buyer, multiple-module need, low procurement. |
| Growing SMB operations leads | 15 | Expansion ICP | High value but expects mature permissions, admin, integrations, and reliability. |
| Solo operators and micro-teams | 15 | Lower-end PLG wedge | Easy to reach, but lower ACV and more sensitivity to suite complexity. |
| Productivity system builders | 9 | Community audience | Strong modularity resonance, weaker urgent business buying signal. |
Build Sequence
Poketo Core
Organization, workspace, module catalog, mascot-backed module identity, shared shell.
poketo.work
Boards, lists, cards, and basic project execution as the first activated module.
Client Context
Shared project/client objects so Work reflects the service-business reality.
Agent Sidebar
Human-in-the-loop summaries, stale work, next actions, and card operations.
Second Module
Likely CRM/client pipeline or client portal, depending on research validation.
What Must Stay Aligned
Decision rule
Every v3 decision should make one selected module more useful while increasing shared context for the future suite.
Guardrails
- Do not rebuild the archived v2 app list by default.
- Do not make Work carry suite-wide decisions that belong in Core.
- Do not let mascots become decoration; they must clarify module roles.
- Do not sell abstract agents before the workflow value is concrete.
- Do not force all modules on every customer.
Open Questions
Module activation
How should users discover, select, configure, and remove modules without setup anxiety?
Mascot credibility
How does each mascot communicate role and capability while staying credible for business buyers?
Second module
Should the next module be CRM/client pipeline, client portal, chat, or reporting?
Source Artifacts
Use these files as the current alignment baseline for Poketo Core and the first Work module.