From dogfood to ecosystem.
This is direction, not a delivery schedule. At v0.1 we are honest about that: the sequence below is the path we believe in, and the order, the labels and the timing will be set with the first consultants — not promised by date. Wegenty hardens against one real channel before it generalises, then opens, one deliberate step at a time.
Four phases, in order — proof before scale
Each phase has a single outcome it has to earn before the next one begins. We would rather move one deliberate step at a time than promise four at once.
- 0Phase 0Dogfood
Prove it on a real reference case
The strongest open-source proof is “we run it ourselves.” Phase 0 ships Wegenty as the public CX agent for an existing consultant channel into the 40–60 SME demographic — energy-renovation advisory — and hardens it against a real, opinionated corpus before generalising.
The point of this phase is to prove the governed projection and the correction loop on live traffic, not a deck — to find the rough edges where it matters before anyone else has to.
Outcome it has to earn — Proof on a live energy-renovation channel.
- 1Phase 1Arm the consultants
Make a non-technical advisor productive on day one
Onboarding and provisioning, Cloud Shield, the appliance and the managed AWS high-availability option. The goal is that a trusted local advisor — not an engineer — can stand the system up and run it on day one.
This is the Consultant Network pillar: independent local distribution, self sign-up with provisioning, and a recurring share of every subscription flowing to the consultant who owns the relationship. They keep the majority; the platform carries the liability they never wanted to own. A lightweight identity and contact-capture layer ships here too, so the business starts accumulating customer relationships from day one — the first step of the concierge.
Outcome it has to earn — Non-technical advisor productive day one · identity + contact capture.
- 2Phase 2Open horizontally
A generic release and a way to extend it safely
A generic, opinionated-deployable release that reaches beyond a single channel — plus the safety-adapter SDK, so customers can extend the system without ever stepping outside the trust boundary.
Horizontal reach means broader knowledge bases and more deployment shapes, but the governance does not loosen: the safety adapter is exactly the seam that lets new capability arrive while the projection stays one-directional and the corpus stays sovereign. The full account portal, the sovereign on-core CRM and segment-based re-engagement generalise here too — turning day-one contact capture into a real retention layer, the spine of the concierge positioning.
Outcome it has to earn — Generic release + safety-adapter SDK · full accounts, CRM & re-engagement.
- 3Phase 3Marketplace
Third-party builders on the open core
Curated, gated extensions from third-party builders on the open core, with revenue share to the people who build them. Governance applied a fourth time — now over what others bring to the platform.
The same logic that holds the consultant model together holds here: the core is open, so anyone can build, but certification and the trust boundary flow only through the platform. That is what makes a curated, revenue-shared marketplace defensible rather than a free-for-all.
Outcome it has to earn — Gated extensions with builder revenue share.
Phases 1 and 3 map directly onto the consultant economics: a recurring share of every subscription in Phase 1, and revenue share to third-party builders in Phase 3. Distribution, infrastructure and research — each feeding the next.
The destination moves. The boundary doesn’t.
A roadmap is only trustworthy if some things are off the table. Whatever order the phases land in, three commitments hold — and the trust boundary holds with them. The public agent is always a governed projection of a private superset — one-directional by construction, never the reverse.
Knowledge stays under the company’s control. Whatever ships next, nothing leaves the building by default — sovereignty is the starting state, not a feature we add later.
The core stays open source — projection engine, correction loop, the safety-adapter SDK and the marketplace’s open core. Only Cloud Shield, the compliance umbrella, is ever closed.
A trusted local consultant delivers it and a person stays in the runtime loop. Every phase widens the reach of that human; none of them replaces them.
We track the hard questions openly too — credential handling in artifacts, curation at scale, and a projection-policy UX a non-technical operator can actually drive. Direction is a promise to keep moving, not a claim to have it all solved.
Help set the direction — not just read it.
The order and the timing of these phases are set with the first consultants. Become an early partner, or explore the open core that every phase builds on.