AIMY: A Three-Tier Circle.so Community Built and Launch-Ready Without a Tech Background

The Challenge

AIMY's founder had created a Circle.so account but could not work out how to structure it, so the platform sat untouched while the launch stalled. A complex three-tier product model had nowhere to live.

Client Background

Three-Tier Offer

A GBP 59 per month membership, a GBP 1,992 eight-week programme, and GBP 2,495 three-month 1:1 coaching, all to be housed in a single community platform.

Solo Founder, No Tech Support

One person, a clear vision, a 35-page brand document, and a warm lead list managed in a manual spreadsheet.

Pre-Launch Platform

Circle account created, sitting in default onboarding, with no spaces, no structure, and nothing built.

Key Challenges Faced

No Community Architecture

A complex product model with nowhere to put it. Amy had created the Circle account but could not work out how to structure it, so the platform sat untouched while the launch stalled.

Content Overwhelm Blocked Progress

Exercises, recipes, eight programme modules, and three tiers of content to create, impossible to approach without a structure to build into.

No Onboarding or Email Flow

Amy knew she wanted a welcome journey and an email sequence, but had no idea how to build it inside Circle. The onboarding section was blank and the drip campaign had never been configured.

The Solution

TekConnected built the community architecture around AIMY's actual product model rather than a generic template, giving the founder a structure to build into instead of a blank platform.

What Was Built

20 Spaces Across 8 Space Groups

A full architecture ready to receive content across all three tiers.

Onboarding Flows

New members are guided from signup to first engagement, replacing the default Circle onboarding that had been left untouched.

Email Go-to-Market Foundations

Three live native email templates covering a welcome sequence and an upsell framework triggering on member join, built natively in Circle with no third-party tools required at this stage.

Tier-Based Access Structures

Configured with clear upgrade pathways between membership levels, so members can see what sits above their tier.

The build was scoped intentionally to validate first, with CRM, Make.com, and website integration planned for a second phase rather than bundled into the initial launch. The underlying principle is that a community should run on systems, not on the founder's time.

Technology Stack

Results & Outcomes

Structured Member Activation From Day One

A welcome journey, a structured start point, and an email sequence built and ready, the foundation the founder could not figure out how to create herself.

20 Spaces Across 8 Space Groups

Full architecture built and ready to receive content across all three tiers.

3 Native Email Templates Live

Welcome sequence and upsell framework triggering on member join, with no third-party tools required at this stage.

Warm Lead List Finally Had a Destination

Manually tracked prospects could be invited into a real, structured community instead of a holding pattern.

Strategic Impact

• Scalable content structure: repeatable space formats so new exercises, recipes, and modules can be added without rebuilding layout each time.
• Handover-ready platform: logical enough for a future community manager to onboard without the founder being the single point of knowledge.
• Phase 2 automation ready: build scoped intentionally to validate first, with CRM, Make.com, and website integration planned for the next phase.

Who This Applies To

This build pattern fits an organisation that:

• Runs an unstructured community that loses members fast because the experience is broken from the moment they join
• Has the vision and the content planned, but without a platform structure nothing moves forward
• Offers multiple membership tiers without distinct access zones, so members cannot see what they are missing and do not convert up
• Depends entirely on the founder to hold the platform knowledge