Skip to content

ADR-0007: connectsoft.me Product Introduction

  • Status: accepted
  • Deciders: ConnectSoft Architecture Team
  • Date: 2026-01-15

Context and Problem Statement

ConnectSoft is building a comprehensive product portfolio spanning Core Platform, AI Factory, horizontal SaaS, vertical solutions, and marketplaces. We have established a five-cycle structure for organizing products, and we need to introduce a new B2C/B2Solo product line that targets individuals rather than organizations.

The question: Should we introduce connectsoft.me as a distinct Personal Agents Platform, and how should it be architected to leverage existing Core Platform and AI Factory infrastructure?

Decision Drivers

  • Need for consumer-facing entry point to ConnectSoft's agent technology
  • Requirement to test agents and workflows in consumer context
  • Need for experimentation lab that feeds learnings back into enterprise products
  • Requirement for upgrade path from personal to organizational use
  • Need to reuse Core Platform and AI Factory infrastructure
  • Requirement for personal-tenant patterns distinct from organizational tenants

Considered Options

Option 1: Extend connectsoft.io with Personal Tier

Approach: Add personal/individual tier to existing connectsoft.io B2B SaaS products.

Pros:

  • Single domain to manage
  • Shared infrastructure
  • Simpler branding

Cons:

  • Confuses B2B and B2C positioning
  • Different pricing and business models
  • Different user journeys and onboarding
  • Rejected - Mixes B2B and B2C concerns

Option 2: Separate Product on connectsoft.me (Selected)

Approach: Create distinct connectsoft.me product as Personal Agents Platform, using same Core Platform and AI Factory but with personal-tenant patterns.

Pros:

  • Clear B2C/B2Solo positioning
  • Separate branding and user journey
  • Can experiment with consumer patterns
  • Clear upgrade path to connectsoft.io
  • Reuses Core Platform and AI Factory
  • Personal-tenant patterns distinct from organizational

Cons:

  • Additional domain to manage
  • Need to handle personal-tenant patterns
  • More complex portfolio

Decision

Introduce connectsoft.me as a distinct Personal Agents Platform:

  • Architecture: Uses same Core Platform (Identity, Config, Audit, Documents, Communications, Billing, AI Gateway) and AI Factory (Agent Template, workflow orchestration)
  • Tenant Model: Personal-tenant patterns (individual user accounts) distinct from organizational tenants
  • Product Positioning: B2C/B2Solo product line for individuals, freelancers, students, and families
  • Strategic Role: Consumer-facing brand, experimentation lab, upgrade funnel to connectsoft.io
  • Cycle Position: SaaS Cycle 3, after horizontal SaaS (Cycle 2) and before vertical solutions (Cycle 4)

Rationale

  • Clear Separation: Distinct B2C product separate from B2B products on connectsoft.io
  • Infrastructure Reuse: Leverages existing Core Platform and AI Factory investments
  • Strategic Value: Provides consumer-facing entry point and experimentation lab
  • Upgrade Path: Natural progression from personal to organizational use
  • Learning Loop: Consumer usage feeds learnings back into enterprise templates and patterns

Consequences

Positive Consequences

  • Clear B2C/B2Solo product positioning
  • Consumer-facing entry point to ConnectSoft technology
  • Experimentation lab for agents and workflows
  • Upgrade funnel to connectsoft.io
  • Reuses Core Platform and AI Factory infrastructure
  • Validates personal-tenant patterns on Core Platform

Negative Consequences / Risks

  • Additional domain and product to manage
  • Need to handle personal-tenant patterns in Core Platform
  • Privacy and data control requirements for personal users
  • Cost management for freemium model
  • Potential confusion between .me and .io products

Mitigation

  • Clear documentation of product positioning and upgrade path
  • Personal-tenant patterns implemented in Core Platform
  • Strong privacy controls and transparent logging
  • Cost-based tuning of usage limits
  • Clear cross-linking and messaging between domains

Architecture Implications

Core Platform

  • Identity Platform: Support personal-tenant patterns (individual user accounts)
  • Config Platform: Per-user preferences and settings
  • Audit Platform: Personal data logging and audit trails
  • Documents Platform: Personal file storage and management
  • Communications Platform: Personal email and notifications
  • Billing Platform: Freemium tiered subscriptions (Free, Pro, Family, Creator)

AI Factory

  • Agent Template: Used for personal agent implementation
  • Workflow Orchestration: Multi-agent workflows for personal use cases
  • Template Generation: Personal-tenant aware generation patterns

Data and Privacy

  • Personal Data Ownership: Users can export and delete their data
  • Transparent Logging: "See what this agent did" per run
  • Suggestion-Based Actions: All external actions start as suggestions
  • Privacy Controls: Per-agent and per-workflow privacy settings