Recurring revenue on the trust you’ve already earned.
Wegenty is the only governed, sovereign-by-default AI assistant an SME can adopt without an engineer — because a trusted local consultant runs it for them. Sell a product you didn’t build, keep the customer relationship, and earn a recurring share. The platform carries the liability.
You already advise the Mittelstand. Now advise it on AI.
If you hold a recurring, trusted relationship with small and mid-sized businesses, you are exactly who Wegenty grows through — DACH first, channel-first.
Energy-efficiency advisors
The ~20,000 dena/BAFA-certified experts already running iSFP and BEG/BAFA/KfW advisory. The same SMEs, the same trust — now a recurring AI line.
Steuerberater & advisors
Tax and business advisors with a roster of Mittelstand clients who ask, every quarter, what they should do about AI. Now you have a sovereign, compliant answer.
MSPs & IT shops
Managed-service providers who already own the network and the help desk. Add a sealed, governed local AI core to the stack you maintain — local by default, with Cloud Shield when a client goes public.
Trade-association advisors
Chamber and Verband advisors serving a whole sector. One trusted recommendation reaches hundreds of members who would never self-serve a cloud agent.
Beachhead: energy-renovation advisory (Energieberatung / iSFP) under BEG, BAFA and KfW funding — a sector that already runs on trusted advisors and a flood of paperwork.
Agents you can trust.
You are selling on a reputation you spent years building. The assistant has to be one you can stand behind — controllable, explainable and accountable, by design rather than by promise.
Controllable
A governed projection plus scoped access means you decide exactly what a customer can ever see. You set the policy once; the boundary holds without you babysitting it.
Explainable
Every answer is grounded in cited sources, and an audit trail records why it was said. When a client asks how the assistant reached an answer, you have one to give.
Accountable
Cloud Shield carries the live regulatory posture and certification, and a human consultant — you — stays in the loop. The buck stops with named accountability, not a black box.
Controllable is the governed projection and scoped access. Accountable is Cloud Shield plus a human consultant — you. The trust spine is the product you actually sell.
A product to sell, not a project to staff
The hard parts — the model, the governance, the compliance — are already built and carried. You bring the relationship.
Sell what you didn’t build
A sovereign, governed AI assistant arrives finished. No model to train, no retrieval to tune, no infrastructure to babysit. You bring the relationship; the platform brings the product.
Install in an afternoon
The pre-imaged appliance plugs into the office network and runs sealed — no inbound ports. One droppable file — a readable certificate wrapping a machine manifest — pairs any assistant to the customer’s knowledge over REST+OpenAPI or MCP.
The platform carries the liability
Cloud Shield holds the live regulatory posture, audit trail and certification under DSGVO and the EU AI Act. You are not the compliance department — and you never have to self-insure one.
Keep the relationship, earn a share
You own the customer. You earn a recurring share for as long as they run it. The model is defensible because you cannot fork liability — the certification umbrella only comes through Wegenty.
Built on three principles you can promise without an asterisk: sovereign by default, open by principle, human by design. A connection artifact is one droppable file — a readable certificate wrapping a machine manifest — that pairs any assistant over REST+OpenAPI or MCP.
Customer accounts & a sovereign CRM — the recurring fee, justified
The assistant stops being a deflection bot and becomes a concierge that recognises returning customers and tends the relationship over time. Passwordless customer accounts (magic-link / OTP, scoped to one core) plus a CRM that lives on the client’s own core — one contact record, one merged timeline, never a foreign cloud. At answer time the agent injects only that customer’s own context: default-deny, never another customer’s data or the internal corpus.
- Returning customers are recognised — continuity, follow-up, re-engagement instead of starting from zero each time
- A clear retention ROI you can put in front of the owner: it helps them keep their own customers
- Relationship data gravity makes the account harder to churn — and the recurring share more durable
PII-heavy by nature, so it stays sovereign on the customer’s box — reinforcing the moat, not straining it. The clearest line to a recurring fee the owner is glad to pay. Customer accounts, a sovereign on-core CRM and identity projection carry the concierge promise.
The open core can be copied. The liability cannot be forked.
Certification under DSGVO and the EU AI Act flows only through Cloud Shield, and the customer relationship flows only through you. Distribution and compliance reinforce each other — which is exactly why the recurring share is durable rather than something a competitor can undercut.
From partner to recurring revenue in four steps
No build phase, no integration team. A path you can run inside an existing client engagement.
Become a partner
A short onboarding gets you platform access, the partner economics, and a demo instance you can put in front of clients the same week.
Qualify a client
Pick an SME in your book that runs on knowledge in people’s heads. Show them their own questions answered in the live demo — sovereignly, with citations.
Install & curate
Drop in the sealed appliance, point it at their knowledge base, and set the projection policy that decides what a customer can ever see. Switch on public exposure — Cloud Shield — only if and when they need it.
Earn on the relationship
You stay the trusted face. The platform handles updates, compliance posture and certification — you collect a recurring share and grow the account.
Configure three layers per client — sovereignty is the floor
The hardware is a constant: a pre-imaged, sealed AI core appliance, the trust boundary that never changes. On top sit three layers you choose per client. Local access is always the baseline; everything else stacks.
Who stands it up?
You run the install yourself, hand it to Wegenty, or let the client DIY. As the consultant you keep the relationship — the in-person setup is yours to bill, the box arrives pre-imaged either way.
Who can reach it? (combinable)
Pure local is the baseline. Public exposure is optional and additive: a core can stay local, add a DIY public API, and/or sit behind Cloud Shield — these coexist, they are not either-or. Most public clients pick Shield so nobody has to run a compliant edge.
Who tailors it?
DIY, you as the consultant, or Wegenty premium — and Wegenty lists its rate above yours on purpose, to keep you the attractive default. Tailoring is a project fee on top of the recurring share.
See how each layer is priced on the pricing page — then assemble the configuration that fits your next client.
The questions consultants ask first
How does the recurring share work, and why is it defensible?
You own the customer relationship and earn a recurring share for as long as they run it. It is defensible because you cannot fork liability: the open core can be copied, but the Cloud Shield compliance umbrella — live regulatory posture, audit trail and certification — only comes through Wegenty. The relationship and the certification both flow through you.
Who carries the compliance and legal risk?
The platform does. Cloud Shield is the one closed component — a compliance umbrella that maintains certification under DSGVO and the EU AI Act, which is fully applicable on 2 August 2026. You are not the compliance department and you never self-insure one.
Do I need to be technical to deliver this?
No. The whole point is that a trusted advisor — not an engineer — can run it. The appliance is pre-imaged and sealed, public exposure is an opt-in setting (Cloud Shield takes the compliant edge off your plate), and a single droppable connection file pairs the assistant to the customer’s instance. You curate knowledge and set policy; the platform handles the plumbing.
What do I configure for the client?
Not a choice between three boxes — one sealed box, three layers. The hardware is constant: a pre-imaged, sealed AI core appliance that is the trust boundary. On top you choose ① who sets it up (you, Wegenty or the client), ② the run mode — pure local is always the baseline, and public exposure is additive: a DIY public API and/or Cloud Shield can coexist on the same core — and ③ who tailors it. Sovereignty is the floor, not an upsell.
What does the customer actually get?
One locally-hosted LLM serving many knowledge bases. The internal knowledge base is the superset; the public customer-facing agent is a governed projection of it — default-private, with sensitivity labels and per-base policy deciding what a customer can ever see. When the agent is unsure it escalates to a human, and that answer is captured back into the knowledge base.
Turn the trust you’ve built into a recurring line of revenue.
Become a Wegenty partner. We handle the product, the compliance and the certification — you stay the trusted advisor, and earn for as long as your customers run it.