One agent team, every association.
Tenant-aware via Postgres Row-Level Security — not per-customer forks, not per-customer prompts to maintain. Aggie answering Mel at WDAA never sees the data sitting in another association’s row.
Not bolted on. Not a chatbot in the corner. AI is woven through every one of our 20 apps — generating courses, drafting emails, matching capabilities, scoring engagement, and watching for trouble — so the people running associations like WDAA can stop juggling tools and start leading their members.
15 apps. One AI core. Each app uses the layer differently — same audited, tenant-scoped pipeline underneath.
One stack from app to model. One contract for every association. One audit trail for every query.
Tenant-aware via Postgres Row-Level Security — not per-customer forks, not per-customer prompts to maintain. Aggie answering Mel at WDAA never sees the data sitting in another association’s row.
Claude → Gemini → OpenRouter → local Ollama, all behind one interface. Pricing changes? Latency spikes? New frontier model lands? We flip a flag — the apps don’t care.
The MCP tool layer logs who asked what, when, on whose tenant, with which model. Compliance officers love it. Pavan loves it more — she can show the APVB exactly what AI touched the CPD record and when.
“If we change a model tomorrow, no association even notices.”
Sixteen distinct AI capabilities, shipped or in flight, across the platform.
Generate logos, banners, and social cards in WDAA’s exact brand — colours, type, voice — without firing up Photoshop.
Why: comms teams own the schedule, not the design backlog.
A vision model captions and folders every uploaded asset so a five-year archive is searchable in seconds, not weeks.
Why: members’ faces and conference moments are findable, not lost.
From PDF to lesson outlines, quizzes, and learning objectives — aligned to whatever framework your accreditation body insists on.
Why: the bottleneck is editorial review, not authoring from scratch.
Aggie, Scout, Beacon, Atlas, Lumen, Sentinel. They live inside Loop channels and answer in your team’s tone.
Why: one conversation, six specialists, no tab-switching.
Renewal-risk plus engagement scoring across CRM, Events, LMS, and Loop — one view of every member’s temperature.
Why: silent members are the ones who churn first.
Sponsorship tier analysis, pricing scenarios, corporate-account targeting — with the deal history baked into every recommendation.
Why: the right call on Tuesday saves the renewal on Friday.
CPD posture, Code-of-Conduct watch, escalations — before the regulator even asks.
Why: audits are painful only when they’re a surprise.
Workshop transcripts and tender PDFs become structured requirements with confidence scores — so reviewers spend time on the 70%, not the 100%.
Why: the proposal deadline doesn’t care that you only got the brief on Friday.
Each requirement is matched against the platform capability registry with reasoning — gaps surface before they become commitments.
Why: a clear “we already do that” vs “we’d need to build that” in minutes.
Approved requirements turn into stories with plain-language UAT steps a board member can read — no PM round-trip.
Why: the people approving the spec must understand the spec.
New workflows are tagged Quality / Compliance / Operations on the fly — the dropdown nobody filled in is now answered for them.
Why: dropdowns are the silent killers of every QMS adoption.
Catches duplicate workflows and over-allocated owners before they ship as confused processes to members.
Why: two CPD-renewal flows is one too many.
Embedded chat with full account context plus tool calling — new staff don’t need a 40-page induction PDF.
Why: onboarding is the most expensive workflow you have.
Tone-controlled follow-ups grounded in the deal history — warm, professional, urgent, choose your register.
Why: the blank-page problem is half the reason follow-ups don’t happen.
Bullet trajectory of every deal — what happened, what’s next, where the energy is — in a glance.
Why: the cost of a bad handover is a lost deal.
Find members by intent, not exact phrase, with graceful fallback to keyword when the embedding model is offline.
Why: nobody types the exact phrase that’s in the database.
Western District Veterinary Association. 230 members. Three-person admin team. Here’s how AI changes their morning.
Aggie has already drafted her morning brief: 3 deals progressing, 1 at risk (a $42K renewal — Western District corporate sponsor — 14 days quiet), platform green, 12 at-risk members surfaced, Pavan’s CPD post ready to review.
Mel didn’t ask. The brief was waiting.
Lumen has flagged the 12 vets on her at-risk list. Each has a “what changed” note: career shift, surgery downtime, moved practice. Three are tagged “high-value, intervene this week.”
Louise has 30 minutes of focused work, not 3 hours of spreadsheet hunting.
Beacon writes a personalised invite for each member tier: senior vets get the keynote angle, nurses get the CPD-credit angle, students get the bursary angle. Sentinel reviews for compliance language before the send.
3 hours of writing becomes 20 minutes of review.
A 50-page PDF. ScopeSync extracts each new competency, maps to existing LMS modules, flags gaps. Pavan reviews the gaps, accepts the rest.
No more reading the PDF twice and second-guessing.
ScopeSync runs requirement extraction and capability matching while Mel makes coffee. Draft proposal lands in her inbox before she’s back.
48-hour turnaround, no Friday-night scrambling.
The hard part isn’t the prompts. It’s the plumbing that makes them safe to ship to a hundred associations at once.
RLS at Postgres, not in agent code. WDAA’s data never touches another association’s session — even by mistake.
Claude today, Gemini tomorrow, local Ollama for embeddings. Swappable behind one interface — pricing and latency stay our problem, not yours.
Every tool call logged with account, user, agent, inputs. Compliance officers love this — the regulator-friendly answer is always one query away.
Token usage tracked per agent per tenant. Budget alerts before surprises — nobody wakes up to a five-figure inference bill.
The shape of the platform today.
AI woven through every one
One team, shared across every association
Each tenant-scoped, audited, opt-out aware
Claude, Gemini, OpenAI, OpenRouter, Ollama — flip with an env var
AI woven through every part of the operation. One platform. One conversation. Your data, your tenant, your team.