1. Service as exchange
Arki sells operational outcomes: closure speed, ownership clarity, shared visibility.
Arki Integrated Strategy
Investor + Team Master Deck
Arki Strategy 2026: one connected operating system for housing management in Finland.
This strategy combines business model, sales motion, and marketing execution in one operating view. It is built from current Arki positioning, role-based value model, and existing strategy workstreams. Framework style follows SCQA + pyramid logic used in top-tier consulting decks and is structured on the Service-Dominant Logic model.
Service-Dominant Logic
Investor-ready narrative
Execution-linked
Partnership-convertible
Audience Lens
Switch lens: investor, operating team, or partnerships
Thesis:
Arki can become the category owner for connected housing operations by monetizing measurable operational outcomes across multi-stakeholder workflows.
Mission for execution:
Standardize one high-friction workflow first, prove adoption in live operations, and scale to role-specific visibility and governance reporting.
Partnership value:
Arki is the coordination layer that reduces handoff failures between management, vendors, and board-level governance actors.
Service-Dominant Logic
Strategic foundation: value is co-created in service, not delivered as software screens
2. Multi-actor co-creation
Managers, boards, residents, and vendors all create value in one shared workflow.
3. Value-in-use
Success is measured in live execution quality, not feature count.
4. Ecosystem orchestration
Arki becomes the trusted operating layer across organizations, not a single-team app.
Strategic implication: pricing, sales, and marketing should always lead with measurable operating outcomes and governance confidence.
S-DL Business Model
Arki Service-Dominant Logic business model canvas
Service exchange unit
The core unit is not a feature; it is a shared service case from capture to close with visible ownership.
Resource integration
Each actor brings operant resources: manager process control, board governance rules, vendor execution, resident signal quality.
Value realization
Value is realized in use: faster closure, fewer handoff failures, and stronger trust in board-level status reporting.
Institutional layer
Common definitions, role permissions, SLA expectations, and completion proof standards keep the system reliable.
Monetization logic
Pricing attaches to service capacity and governance value: base platform + active role licenses + governance package.
Expansion logic
Scale through adjacent workflows and stakeholder depth, not by pushing unused modules.
Value proposition: reduce coordination overhead and handoff ambiguity.
Participation required: assign clear owner and enforce one-thread workflow discipline.
Outcome metric: case closure cycle time and reassignment frequency.
Participation required: assign clear owner and enforce one-thread workflow discipline.
Outcome metric: case closure cycle time and reassignment frequency.
9-Block Answer Map
Service Logic Business Model Canvas: full answers for Arki with sources
This section answers each question in your canvas directly from both perspectives: Arki (provider) and customer (management companies, boards, residents, and vendors), with online source references and why each point fits Arki.
01. Customer's world and ideal value
From our point of view: target operationally complex housing portfolios where communication and ownership are fragmented across actors.
From customer point of view: managers want predictable execution, boards want trustable visibility, residents want updates, vendors want clear briefs.
Why for Arki: this matches Arki's live positioning as one hub connecting all roles in housing management.
02. Value proposition
From our point of view: we sell outcome reliability, not screens: one thread, one owner, visible status, and completion proof.
From customer point of view: they buy lower coordination overhead, fewer handoff failures, and better governance confidence.
Why for Arki: this is exactly the "one hub" promise and is consistent with service-dominant value-in-use logic.
03. Value creation
From our point of view: value is embedded in daily workflows (capture, assign, coordinate, update, close), not in one-time setup.
From customer point of view: value emerges when everyone keeps using the same case thread and governance checkpoints in real operations.
Why for Arki: Arki's workflow architecture is already built for continuous operational use and proof visibility.
04. Interaction and co-production
From our point of view: we must orchestrate role interactions, permissions, and handoffs as one service system.
From customer point of view: they need low-friction interaction patterns across channels and stakeholder roles.
Why for Arki: co-production quality is the key adoption lever in the Finnish housing ecosystem.
05. Revenue streams and metrics
From our point of view: base platform fee + role licenses + governance package, optimized with value-based pricing.
From customer point of view: willingness to pay depends on measurable operational and governance gains, not feature count.
Why for Arki: Arki can tie commercials to outcomes like closure speed, status reliability, and board confidence.
06. Key resources
From our point of view: workflow architecture, housing-domain know-how, integration capability, change enablement, and multilingual service.
From customer point of view: high-quality issue input, clear internal ownership, and vendor proof discipline are required resources.
Why for Arki: Finnish market and regulation context make language and governance capabilities essential.
07. Key partners
From our point of view: management companies, housing boards, service vendors, integration partners, and ecosystem associations.
From customer point of view: they already operate via partner networks; Arki must strengthen those relationships instead of replacing them.
Why for Arki: Arki wins by connecting existing actors into one accountable service system.
08. Mobilizing resources and partners
From our point of view: standardize onboarding, data standards, service-level rules, and role-accountability rituals across all actors.
From customer point of view: they need practical rollout support that fits real workload and current operating habits.
Why for Arki: practical rollout is a core brand promise and a major conversion differentiator.
09. Cost structure
From our point of view: core costs are product build, service onboarding, customer success, integrations, and trust/compliance operations.
From customer point of view: key sacrifices are change management effort, process discipline, and initial transition time.
Why for Arki: controlling adoption cost while proving value fast is the fastest path to scalable recurring revenue.
Source method: Service-Dominant Logic and SLBMC define the model structure; Finland legal and market sources ground the assumptions; Arki's own site aligns the model to current brand and product promise.
Business Strategy
Where to play, how to win, and what must be true
Beachhead
Finnish housing management companies managing multi-party service workflows with high coordination overhead.
Initial use cases
Issue intake, assignment, vendor coordination, board status visibility, and close-out proof.
Sales Strategy
Sales architecture: consultative land-and-expand with proof-led conversion
01
Target accounts: management companies with visible multi-stakeholder service operations and board reporting pressure.
02
Entry offer: 8-week practical rollout around one high-friction workflow with clear success metrics.
03
Expansion: additional workflows, governance reporting, and wider stakeholder adoption.
| Stage | Goal | Exit criteria | Primary proof asset |
|---|---|---|---|
| Discovery | Quantify one costly coordination problem | Economic pain + process owner confirmed | Current-state friction map |
| Design Session | Map Arki workflow to real process | Pilot scope and stakeholders locked | Capture-to-close workflow blueprint |
| Pilot Proposal | Commercial + implementation commitment | Signed pilot agreement | ROI hypothesis + rollout plan |
| Rollout | Prove value in live operations | KPI target hit and governance use confirmed | Before/after operational scorecard |
Marketing Strategy
Narrative engine and campaign system (LinkedIn + X/Twitter)
Narrative Pillar A
Connected ownership: one issue thread, one owner, one visible timeline.
Narrative Pillar B
Governance confidence: board-ready visibility without operational noise.
Narrative Pillar C
Practical rollout: high-end implementation with real operational proof.
Quarter 1: Category setup
Publish founder-led insight posts, role-based pain narratives, and "one hub" category language.
Quarter 2: Proof acceleration
Shift to screenshot-backed workflow outcomes, KPI narratives, and pilot-result stories.
Quarter 3: Partnership credibility
Publish vendor and board collaboration stories; build trust with ecosystem examples.
Quarter 4: Scale narratives
Show repeatability across account types, governance maturity, and recurring commercial value.
Economic Model
Interactive S-DL scenario model (ARR, value realization, CAC payback)
Scenario model purpose: align investor discussion and internal targets around the same commercial assumptions.
Execution Translator
Convert strategy into weekly tasks and partnership actions
Generated execution plan
Milestones
12-month value plan
| Quarter | Primary objective | Operating milestone | Commercial milestone |
|---|---|---|---|
| Q2 2026 | Pilot repeatability | 3 repeatable workflow templates validated | 5 paying accounts with live adoption evidence |
| Q3 2026 | Governance productization | Board-ready reporting package standardized | Expansion revenue from existing accounts |
| Q4 2026 | Ecosystem partnerships | Two channel partnerships activated | Partnership-sourced pipeline operational |
| Q1 2027 | Scale discipline | Operating cadence and KPI governance institutionalized | Predictable quarterly growth with controlled payback |