Skip to content

connectsoft.me Domain Strategy

This document defines the strategy for connectsoft.me as the personal agents brand in the ConnectSoft family. It is written for marketing, product, GTM teams, and anyone creating content for the .me domain.

connectsoft.me is the personal agents brand: where individuals discover and use personal AI agents and multi-agent workflows for daily life automation. It's positioned as a lighter-weight SaaS for life & work automation for individuals, distinct from the B2B focus of connectsoft.io.

Note

Brand Positioning: connectsoft.me is the "personal agents" brand in the ConnectSoft family. It uses the same Core Platform as enterprise products but targets individuals, freelancers, students, and families rather than organizations.

Role of connectsoft.me

connectsoft.me is the Personal Agents Platform for individuals. It represents:

  • Personal Automation - AI agents and workflows for personal life tasks
  • Consumer-Facing - Where individuals discover, evaluate, and use personal agents
  • Self-Service - Low-touch, simple onboarding and usage
  • Life Workflows - Focus on personal productivity, not software engineering

Key Characteristics:

  • Personal Tenants - Individual user accounts, not organizational tenants
  • Life-Focused - Email management, calendar coordination, budget tracking, learning, family logistics
  • Simple Pricing - Freemium model with clear tiers (Free, Pro, Family)
  • Consumer-Centric - Focuses on individual outcomes and value

See: connectsoft.me Overview for product details.

See: connectsoft.me Business Model for pricing and business model.

Relationship to Other ConnectSoft Domains

connectsoft.ai

Relationship:

  • connectsoft.ai provides the Core Platform & AI Factory (the "brain" and infrastructure)
  • connectsoft.me uses the AI Factory and Core Platform services
  • Technical architecture and Factory story live on .ai

Cross-Linking:

  • .me links to .ai for "Built on ConnectSoft AI Factory" story
  • .ai links to .me as example of consumer-facing product using the Factory

connectsoft.io

Relationship:

  • connectsoft.io hosts B2B SaaS products and solution bundles
  • connectsoft.me is the consumer-facing parallel line
  • Upgrade Path: Personal agent recipes can be promoted into organizational workflows on connectsoft.io

Positioning:

  • .me = Personal use, individual accounts, simple pricing
  • .io = Team/organizational use, multi-user, enterprise features, higher pricing

When to Upgrade:

  • Multi-user orgs
  • Custom domains
  • Compliance & advanced integrations
  • Enterprise features (SSO, RBAC, advanced audit)

connectsoft.dev

Relationship:

  • connectsoft.dev provides developer portal, API docs, SDKs
  • Technical integration details for developers building on or integrating with connectsoft.me

Cross-Linking:

  • .me links to .dev for API documentation and developer resources
  • .dev includes connectsoft.me API documentation

Subdomain Strategy

Subdomain Patterns

Subdomain Pattern Usage Example
app.connectsoft.me Main application UI app.connectsoft.me - user dashboard and agent management
api.connectsoft.me API endpoint (if separate from .net/.io APIs) api.connectsoft.me - REST API for integrations
www.connectsoft.me Marketing/landing page www.connectsoft.me - product marketing and sign-up

Application:

  • app.connectsoft.me - Main application UI where users manage agents, packs, and workflows

API (if needed):

  • api.connectsoft.me - API endpoint for integrations (may use shared API infrastructure)

Marketing:

  • www.connectsoft.me or root connectsoft.me - Product marketing, pricing, sign-up

Important

Naming Rules: 1. Use lowercase, hyphen-separated names for subdomains 1. Keep subdomain structure simple and clear 1. New public subdomains must be approved by platform owner 1. Update DNS Subdomain Map when new public subdomains are created

See: DNS Subdomain Map for complete subdomain mapping.

Target Audiences and Journeys

Audiences

  • Busy Professionals - Knowledge workers managing email, meetings, and tasks
  • Freelancers / Solo Founders - Lightweight CRM, follow-ups, invoices, admin
  • Students / Learners - Summarizing materials, quizzes, learning plans
  • Families / Couples - Shared schedules, shopping, reminders

User Journeys

Journey 1: Discover Product → Understand Value → Start Free Trial

  1. Discovery: User finds product via search, referral, or marketing
  2. Evaluation: Reviews product page, features, pricing, use cases
  3. Trial: Signs up for free tier and tries a prebuilt pack
  4. Adoption: Upgrades to Pro after experiencing value

Journey 2: Existing User Manages Agents and Workflows

  1. Login: User logs into app.connectsoft.me
  2. Dashboard: Accesses agent dashboard, sees suggestions and approvals
  3. Management: Manages packs, agents, workflows, and settings
  4. Usage: Reviews agent runs, approves suggestions, exports data

Journey 3: Upgrade to connectsoft.io

  1. Need: User needs multi-user org, custom domains, or compliance features
  2. Discovery: Learns about upgrade path to connectsoft.io
  3. Promotion: Promotes personal pack to organizational workflow
  4. Migration: Seamless transition to team/organizational use

Guardrails and Non-Goals

What .me Should Not Host

  • Deep Architecture Explanation - That's .ai (link to .ai for Factory story)
  • Enterprise Features - That's .io (link to .io for team/organizational features)
  • Low-Level SDK/API Docs - That's .dev (link to .dev for technical docs)

Risks to Avoid

Warning

Risk 1: Mixing Personal and Organizational Use Cases - Don't confuse personal agents with organizational workflows - Keep .me focused on individual use cases - Use clear upgrade path to .io for organizational needs

Warning

Risk 2: Duplicating Content from .ai or .io - Don't duplicate Factory story from .ai on .me - Don't duplicate B2B SaaS features from .io on .me - Link to appropriate domains for detailed information - Keep .me focused on personal agents story

Warning

Risk 3: Over-Complicating Navigation - Don't create complex navigation between personal and organizational features - Use clear upgrade path messaging - Keep navigation simple and intuitive