Research
Validate audience, process pain points, and buying triggers in Finnish housing management.
Arki Partner Plan
Research to Product Tiers: Rollout and Subscription Framework
Practical planning model for Arki: research, data operations, prototype iteration, packaging, pricing logic, and license model per person.
Phase Plan
End-to-End Delivery Path
Data Work
Map baseline workflow data: ticket volume, SLA delays, handoff bottlenecks, closure proof gaps.
Prototype Iteration
Ship weekly prototypes, collect stakeholder feedback, and simplify based on adoption behavior.
Packaging
Define tier structure by function depth, governance needs, and number of active users.
Commercial Rollout
Launch subscriptions by contract period and per-license pricing model with expansion rules.
Research Framework
Questions We Must Answer Before Pricing
Market & Buyer Questions
- Who owns the final decision: founder, ops lead, or board liaison?
- What is the highest-friction process today?
- Which role suffers most from fragmented communication?
- What proof is required for board-level trust?
Operational Data Inputs
- Average issue closure time (current vs target).
- Number of channels per issue (email, calls, chat, tools).
- Number of stakeholders involved per issue type.
- Frequency of rework due to missing context.
Prototype Cycle
Iteration Cadence (4-Week Loops)
| Week | Focus | Output | Decision Gate |
|---|---|---|---|
| Week 1 | Problem framing + success metrics | Scope, flow, role assumptions | Are we solving the highest-value pain? |
| Week 2 | Interactive prototype | Role-specific UI journey | Does each role understand next steps quickly? |
| Week 3 | Pilot data collection | Adoption + friction evidence | What blocks daily usage? |
| Week 4 | Refinement + pricing implication | Tier-ready feature grouping | Can this be sold and delivered repeatedly? |
Tier Architecture
Proposed Product Tiers by Function Depth
| Tier | Ideal Customer | Included Functions | License Model |
|---|---|---|---|
| Tier 1: Core Operations | Small management teams starting connected workflows | Capture/Assign/Update, role views, basic notifications, simple reporting | Per active internal user + limited external viewer seats |
| Tier 2: Governance | Teams needing board-ready visibility and close-out proof | Everything in Tier 1 + governance reporting + audit-ready closure evidence | Per active user + board viewer packs |
| Tier 3: Portfolio Scale | Multi-building operations with higher coordination complexity | Everything in Tier 2 + portfolio analytics + advanced workflow templates + SLA controls | Per active user + volume seat discount model |
Subscription Structure
Contract Periods and Billing Logic
Monthly Plan
- Highest flexibility.
- Best for pilots and short-cycle onboarding.
- Standard per-license rate.
Quarterly Plan
- Commitment with moderate discount.
- Recommended after first successful month.
- Allows predictable rollout planning.
Annual Plan
- Best unit economics and retention.
- Includes quarterly optimization reviews.
- Recommended for full portfolio adoption.
Pricing formula framework:
Total subscription = base tier fee + (active licenses × seat price) + add-on modules.
Keep list prices internal until pilot proof is mature.
License Definition
Per-Person License Rules
| License Type | Typical Role | Access Scope | Billing Rule |
|---|---|---|---|
| Manager License | Property manager / operations lead | Full workflow control and assignment rights | Full paid seat |
| Coordinator License | Back-office support | Case updates, communications, documentation | Standard paid seat |
| Board Viewer License | Board member | Read-only governance and status visibility | Lower-cost viewer seat or bundled pack |
| Vendor Access License | Service provider | Assigned case context and completion evidence upload | Seat or usage-based (per active vendor user) |
Decision Board
What Partners Need To Approve
Before Tier Launch
- Tier boundaries are clear and non-overlapping.
- Each tier has one strong “reason to upgrade”.
- License rules are simple to explain on a sales call.
- All plans map to real delivery capacity.
After 90 Days
- Review activation by role and license type.
- Track expansion from Tier 1 to Tier 2/3.
- Measure churn by contract period.
- Refine packaging based on observed usage, not assumptions.