We start from a proven foundation
The platform is already there. The work we do together is getting your community right, before it goes live — and you stay in charge afterwards.
Configured, not built from scratch
Every Thiscovery community starts from the same proven foundation — a growing library of capabilities we have already tested, some of which we built ourselves for earlier clients. That means we are never starting from zero on the technology.
Getting a community right for your members takes more than switching things on. It takes a proper look at who you are bringing together, what they need from each other, and how the rooms should be structured to support that. Most of our time together goes there.
Two kinds of flexibility
From first conversation to live community
-
DiscoveryWe learn who you are bringing together, what you need the community to do, and where momentum currently gets lost.Current
-
Co-design workshopWe work through the rooms, who belongs where, and how moderation should work — with your team, before anything is built.Upcoming
-
Wireframes and prototypeA working draft you can see and react to, tested internally before we configure the live version.Upcoming
-
Your reviewYour feedback shapes the build directly. This is where we catch the changes that would otherwise surface after launch.Upcoming
-
Staff trainingYour team learns to run and moderate the community day to day, so you own it fully once it is live.Upcoming
-
Launch and reviewWe go live together, then keep meeting. Technical support stays with us; the community stays with you.Upcoming
Why this takes the time it takes
Getting the technology right is fast. Getting your community right takes a proper conversation.
Most of the cost and time in any community project is not the platform. It is the many small decisions that shape how it works for your members: who sees what, how rooms relate to each other, what “done” looks like for joining and moderation. Get those right up front, with your input, and you avoid paying for them twice — once in the build, and again in a string of changes after launch. That is what the co-design and prototype stage is for.
See how a live community is run
Questions people ask
If the platform is already there, why isn’t this quicker and cheaper?
The technology is configured, not built from scratch. What takes real time is getting the structure right for your members. That up-front work is a small investment compared with unpicking the same decisions after launch. You are paying for the conversation, not for us to invent a platform.
Do we have to use everything in the library?
No. We switch on what you need. You can add more later without a rebuild. Unused capabilities stay off, so the community does not feel crowded with tools nobody asked for.
What if we need something that is not there yet?
Most projects need nothing beyond what is already in the library. Where they do, we can scope and build new functionality. That development is quoted separately, so you only pay for genuinely new work — not for rebuilding what already exists. Some of the capabilities we run today started that way, for earlier clients, and then became part of the library.
Who runs it once it is live?
You do. Your staff moderate, approve members, and decide how groups work. We train them before launch, stay on for review meetings, and look after the platform behind the scenes. Run the community shows the admin tools. Governance covers data, conduct, and hosting.
Can it stay small, or grow?
Both. The same foundation can hold a closed group of a dozen people and a network of thousands. The rooms, not a different product, are how you keep those conversations apart.
Want to talk about a community of your own?
Tell us who you want to bring together and what they currently lose between meetings. A short conversation is usually enough to see whether this is the right fit.
Send email