Fragmented stack
Members, events, payments, email, video hosting, merchandise and analytics all lived in different tools that did not talk to each other.
Case study · Lovable Done For You
Welling.co: a full member platform, shipped with Lovable.
We built Welling.co a single platform that replaced six disconnected tools and now runs a member-led professional community end-to-end. Members, groups, events, content, mentorship, commerce and merchandise — all on one stack, built in months with Lovable and a layered set of integrations, and run by one small team.
- 150+
- public-facing surfaces
- 60+
- backend functions
- 4
- Team Members Operating it
Who
Who is Welling.co
Welling.co is a member-led professional community founded by Bella Lively. It is mentorship-driven, with free and paid membership tiers, and a culture built around its in-person and online events — the “Wellingings”.
The platform spans a member directory, library content, mentorship matching, local group meetups and a merchandise storefront — all sitting on top of one single source of truth on people.
The audience is operators, founders and creatives. The bar for the platform is correspondingly high.
“Everything I need to participate in the community lives in one place. I find the people, the events and the replays in the same place I check in.”
Before
The problem space when we started
Manual ops
Welcoming new members, sending event reminders, chasing RSVPs, batching attendee emails and reporting on engagement were all human jobs.
No single source of truth on people
Knowing who a member was, what groups they joined, whether their membership was active required pulling several tabs.
Content sprawl
Event replays, library articles, newsletters and member posts all needed publishing, gating, search and re-use, with very little time.
Events at scale
Group leaders needed to run their own meetups without breaking the brand or the data. Ticketing, RSVPs, reminders, replays and post-event communications all had to be near-zero-touch.
Knowing what is working
No clean view of engagement, attendance, membership revenue or community health. Decisions were vibes-based.
The build
What we built, by area
Twelve surfaces, one platform. Each area below is a capability list — what the platform does for members, group leaders, staff and the public.
Stack
Integrations we wired in
Best-of-breed where it counts, glued together so members and staff never feel the seams.
Custom-domain email
Branded transactional and authentication email — scalable and deliverable.
Batch delivery
Newsletter and event-communications delivery to segmented audiences.
Payments & billing
Stripe
Core commerce backbone — Products, Prices, Subscriptions, Customers, Promotion Codes and webhooks kept in sync with the platform.
Video & media
Wistia
Managed video hosting for event replays and library content.
Calendar & scheduling
ICS calendar
Calendar exports across the platform with UTC-correct timing for any client.
Maps & places
Geo context
Venue and city context for in-person Wellingings.
AI
Unified AI gateway
Matching, drafting and structured tasks. One helper, one key, one error surface.
On a schedule
Automations and scheduled jobs
Recurring work runs without anyone touching a keyboard.
- 24-hour and 1-hour automated event reminders with calendar attachments.
- Daily scheduled newsletter delivery from the editor’s queue.
- Subscription state reconciliation from Stripe webhooks.
- Post-payment account provisioning and welcome flow so new members land already signed-in.
- Inactive-account suppression sweeps on every community broadcast.
- Mentorship intro emails and feedback prompts on cycle milestones.
- Version-update banner that prompts members to reload on every deploy.
- Welcome emails on first sign-in and on manual membership grants.
Outcomes
Results
Result
6+
disconnected SaaS tools replaced with one platform
Result
~70%
weekly community ops time reclaimed
Result
150+
public-facing surfaces shipped in months, not years
Group leaders run their own meetups end-to-end. Members find replays and people in one search. Staff send batch communications in minutes rather than days. And checkout creates accounts so nobody falls through the cracks.
The offer
How we work — Done For You
Discover
We map your real workflow, your members and your stack in a single working session.
Build
We ship a working surface in days, not quarters, using Lovable as the build engine and the integration playbook we refined on Welling.co.
Operate
We hand over a system your team can run, with the automations and content tools already wired in.
FAQ
Frequently asked questions
Is this just a no-code site?
- No. It is a full application with a database, authentication, payments, scheduled jobs, integrations and a content layer.
Do we own the platform at the end?
- Yes. You own the code, the data and every integration.
Can we extend it after handover?
- Yes. The same workflow you saw works for ongoing changes.
How long does a first version take?
- Typically two to six weeks for a working core, depending on scope.
Do you only build communities?
- No. The same engine works for associations, B2B SaaS customer communities, marketplaces, ops tools and internal platforms.
